asked on

Install of WSUS 3.0 SP2 fails during install

I am having trouble installing WSUS 3.0 SP2 on Server 2003 SP2. The install keeps failing at the same point every time, when it gets to the point of "Configuring IIS Dynamic Compression" and then the setup rolls back.

What I have tried is uninstalling and reinstalling .NET 2.0 and 3.0, SQL Server 2005, WIndows Internal DB and IIS. During the install I have also tried changing the DB that WSUS uses to a new one and also both options in the web site selection of Using the existing IIS Default Website (port 80) or the other for port 8530. This one has me whipped.

I have also included the WSUS log from the failed install.

Thanks for the help in advance!

Jeremiah
WSUS-fail-log.txt

Don

Have you come across

Error message when you use Windows Server Update Services Setup: "Error 0x80070643: Fatal error during installation"

http://support.microsoft.com/kb/920660

Wonko_the_Sane

Is there anything else in the event logs?
And you are running SQL 2005 and the Windows Internal DB on the same server? Is there are reason for this?

SOLUTION

Don

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

FCB_IT

ASKER

No there is no reason we are running SQL 2005 and Windows Internal DB. This one just one of the many things I tried in my failed attempt to fix.

I Will try to manually remove WSUS and Internal DB and then let you know what happens.

FCB_IT

ASKER

Ok I manually uninstalled WSUS and the Internal DB, some of the steps I couldnt do since WSUS was already removed. After doing this, the installation failed at the same point "Configuring IIS Dynamic Compression" as before.

What else can I try?

Thanks,

Don

Did you go over the first article I posted ?

Wonko_the_Sane

Try this
Check the 'Enable Direct Metabase edit' box in IIS global properties

Don

Also try running the command

IISreset and try the install again

FCB_IT

ASKER

I did try your first article, but am I not seeing the error messahe listed in the article.
Wonko, I tried the enable direct metabase edit and I tried iisreset and got this:

Attempting stop...
Internet services successfully stopped
Attempting start...
Restart attempt failed.
IIS Admin Service or a service dependent on IIS Admin is not active. It most li
kely failed to start, which may mean that it's disabled.

I was able to restart the IIS service from services sucessfully, but not through IISreset. Do you think this could be part of the problem? Also I tried reinstalling WSUS with the same result.

Don

When you installed IIS did you also install ASP.NET ?

FCB_IT

ASKER

Yes, ASP.NET is installed. However I did find that the ASP.NET service was disabled so I reenabled it and started the service and I tried iisreset again, and unfortunately got the same restart attempt failed message.

Wonko_the_Sane

Errors in the event log?

FCB_IT

ASKER

Under Application
Event ID 47
WMI ADAP was unable to retrieve data from the PerfLib subkey: SYSTEM\CurrentControlSet\Services\mssindex\Performance\Library, error code: 0x80041009

Event ID 40
WMI ADAP was unable to create the object Win32_PerfRawData_ASPNET_2050727_ASPNETAppsv2050727 for Performance Library ASP.NET_2.0.50727 because error 0x80041001 was returned

Event ID 35
WMI ADAP was unable to load the ASP.NET_2.0.50727 performance library because it returned invalid data: 0x0

Under System
Event ID 10119
The WinRM service is unable to start because of a failure during initialization.

Additional Data
The error code is 1300.

Don

Check if this pertains to you

http://support.microsoft.com/kb/896839

Wonko_the_Sane

run lodctr /r and try again

Don

run the command

lodctr /r

FCB_IT

ASKER

That article does not apply to us. I ran lodctr /r which ran sucessfully but WSUS install still failed at the same point. The same errors were generated in the event log.

ASKER CERTIFIED SOLUTION

Wonko_the_Sane

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

FCB_IT

ASKER

I downloaded the WMI Diagnostic Utility and ran the VBS which kicks off the program and I got 2 separate popup errors. I cant tell you what they said exactly now, but something to the effect of the program was unable to create the log files that the WMI tool creates. Now when I run the VBS it just displays the version of the script host and does not create any log files. This is a pretty important domain server so Im a little nervous to do anything that might take it down. At this point would it be safe to run this command line "rundll32 wbemupgd, RepairWMISetup"? I understand this is supposed to rebuild WMI.

Wonko_the_Sane

It shouldn't take it down, but I would be careful. Since this is about WSUS usually waiting a few days won't kill you, so I'd rather schedule this for a time when you can accept some downtime, just in case.

I'd also do a system state backup using NTBackup first.

Don

Did you ensure the Pre-requisites for WSUS 3.0 sp2 ?

http://technet.microsoft.com/en-us/library/dd939886(WS.10).aspx

When you say that you uninstalled .Net 2.0 did you use add/remove ???

Maybe using the .NET cleanup tool may have helped

http://blogs.msdn.com/b/astebner/archive/2006/05/30/611355.aspx

Don

"Under System
Event ID 10119
The WinRM service is unable to start because of a failure during initialization. "

Check your network service account rights

https://www.experts-exchange.com/questions/24994866/WinRM-Fails-To-Start-on-Windows-Server-NOT-R2.html

FCB_IT

ASKER

Where do I go in Windows to verify the network service account rights that I would need to check?

Don

In your group policy under Computer config>>>windows settings>>>security settings>>>local policies>>>user rights assignments and compare to here

http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/3648346f-e4f5-474b-86c7-5a86e85fa1ff.mspx?mfr=true

FCB_IT

ASKER

The network account rights look good in group policy. This server is about 6 years old and there's a few other wierd things that we've seen on it so I think we are going to put a new machine in its place. Thank yall very much for walking me though all the troubleshooting and making up my mind to once and for all replace an old server.

Thanks,

Don

Here's something that would be of future help

WSUS Troubleshooting Survival Guide

http://social.technet.microsoft.com/wiki/contents/articles/wsus-troubleshooting-survival-guide.aspx