My issues are resolved. I let it run for a while and after an hour it
stopped. Another issues was that the SelfUpdate virtual directory was
missing. I added that back in and now WSUS 3.0 is running happily.
Steve
"Steve Gould" <steven.gould at seattle.gov> wrote in message
news:%23J1tsOUOJHA.4776[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text] >I upgraded a Windows Server 2003 SP2 server running WSUS 2.0 to WSUS 3.0
> yesterday. I have SQL 2005 Express running on the server and that was in
> use
> by WSUS 2. The install completed, but the server seemed hung. Opening the
> MMC console failed. It timed out. Looking deeper I found that W3WP.exe was
> running the server up to 100% CPU utilization.
>
> Eventually I found that it was the SimpleAuthWebService causing it. I
> moved
> that into it's own app pool and then stopped the app pool. I had to kill
> the
> w3wp.exe instance associated to it and then the server ran normal. I am
> now
> able to connect the MMC and see all the updates, groups, systems, etc.
>
> I uninstalled WSUS, IIS, and .NET 2 then reinstalled. No change.
>
> I get lots of 1309 time-out events when SimpleAuthWebService is running
> and
> w3wp.exe is hogging the cpu. The only other error messages are related to
> time-outs. I have McAfee running on the server, but I disabled it to be
> certain it is not conflicting.
>
> I assume that clients won't be able to connect with SimpleAuthWebService
> not
> running.
>
> Can anyone suggest what to look at to solve the SimpleAuthWebService
> issue?
>
>
> Thanks!
>
> Steve
>
>
>
>
|