1.1 Framework hangs during install on aspnet.mof on Windows 2000

16 Feb 2007 12:27 AM

WB

I've seen others with this same issue, but no replies. I did see someone with
a similar issue on XP in this newsgroup, and they got it to work by deleting
files, rebooting, and installing .NET FW 1.1 SP1. I cannot (feasibly) do this
in our automated environment.

We have hundreds of systems that need .NET FW 1.1 installed (during or after
unattended install), and we cannot have them all hanging during installation.

--
Bill Baker

13 Apr 2007 5:24 AM

Andrew Wright

Hi

I had this problem and after some messing around was able to resolve it by
recreating the WMI repository. It appeared to be corrupted on this machine.

To do this rename \system32\wbem\repository to repository.old or something.
When you run something that uses the WMI interface this should be restored. I
just right clicked on my computer and chose manage, after the computer
management screen came up the respository was recreated and I was then able
to install dotnet without any further issues.

Hope this helps.

Show quote

"WB" wrote:

> I've seen others with this same issue, but no replies. I did see someone with
> a similar issue on XP in this newsgroup, and they got it to work by deleting
> files, rebooting, and installing .NET FW 1.1 SP1. I cannot (feasibly) do this
> in our automated environment.
>
> We have hundreds of systems that need .NET FW 1.1 installed (during or after
> unattended install), and we cannot have them all hanging during installation.
>
> --
> Bill Baker

13 Apr 2007 4:18 PM

WB

Thanks. I eventually found a different tactic to resolve the issue which was
to re-arrange the order in which my MSI-based installations were being run.

Since this was only happening (for me) on Windows 2000, I was installing the
Windows Installer 3.1 update, which is required for .NET FW 2.0, and also
uses MSI. I moved the 1.1 installation prior to the Windows Installer and
..NET FW 2.0 installations, and this resolved the issue.

If I see the issue again, I'll try your suggestion.

Thanks again,

--
Bill Baker

Show quote

"Andrew Wright" wrote:

> Hi
>
> I had this problem and after some messing around was able to resolve it by
> recreating the WMI repository. It appeared to be corrupted on this machine.
>
> To do this rename \system32\wbem\repository to repository.old or something.
> When you run something that uses the WMI interface this should be restored. I
> just right clicked on my computer and chose manage, after the computer
> management screen came up the respository was recreated and I was then able
> to install dotnet without any further issues.
>
> Hope this helps.
>
> "WB" wrote:
>
> > I've seen others with this same issue, but no replies. I did see someone with
> > a similar issue on XP in this newsgroup, and they got it to work by deleting
> > files, rebooting, and installing .NET FW 1.1 SP1. I cannot (feasibly) do this
> > in our automated environment.
> >
> > We have hundreds of systems that need .NET FW 1.1 installed (during or after
> > unattended install), and we cannot have them all hanging during installation.
> >
> > --
> > Bill Baker