WSUS errors in applicationlog and no computers not showing up

[mkessels]

Hi,
I'm having a hard time with my WSUS server lately. Everytime used to work fine but suddenly it stopped working for no apparent reason.
At the time I was running WSUS 2.0 and when it stopped working it said something like SelfUpdate isn't responding (not sure about the exact error) in the wsusadmin site.
I wanted to ugrade to WSUS 3 anyway so i decided to just uninstall WSUS completely and install WSUS 3 afterwards.

Ok so everything went well and I installed WSUS3. But afterwards I noticed that no computers where showing up in the console
After checking the event log I noticed that pretty much all the virtual directories gave errors in the log. I've past the errors below in this post.

After searching the internet for hours I still couldn't find a solution that would work for me so i've decided to make a post myself.
I've tried several things to fix the problem but none worked (can't remember all of the things I've tried).
I've tried resetting the password on the IUSR_computername and entering the new password in all the IIS Wsus sites and the default website.
I checked all the permissions.
I also tried completely uninstalling WSUS and IIS and reinstalling them but that didn't do the trick either.

So now I'm hoping someone can help me here.

Below are the event logs entries that wsus made.

--------------------------------------------------------------------------
Event Type: Error
Event Source: Windows Server Update Services
Event Category: Clients
Event ID: 13042
Date: 11/5/2007
Time: 9:39:53 AM
User: N/A
Computer: DCGS
Description:
Self-update is not working.

--------------------------------------------------------------------------
Event Type: Warning
Event Source: Windows Server Update Services
Event Category: Clients
Event ID: 13051
Date: 11/5/2007
Time: 9:39:53 AM
User: N/A
Computer: DCGS
Description:
No client computers have ever contacted the server.

--------------------------------------------------------------------------
Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12002
Date: 11/5/2007
Time: 9:39:53 AM
User: N/A
Computer: DCGS
Description:
The Reporting Web Service is not working.

--------------------------------------------------------------------------
Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12012
Date: 11/5/2007
Time: 9:39:53 AM
User: N/A
Computer: DCGS
Description:
The API Remoting Web Service is not working.

--------------------------------------------------------------------------
Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12032
Date: 11/5/2007
Time: 9:39:53 AM
User: N/A
Computer: DCGS
Description:
The Server Synchronization Web Service is not working.

--------------------------------------------------------------------------
Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12022
Date: 11/5/2007
Time: 9:39:53 AM
User: N/A
Computer: DCGS
Description:
The Client Web Service is not working.

--------------------------------------------------------------------------
Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12042
Date: 11/5/2007
Time: 9:39:53 AM
User: N/A
Computer: DCGS
Description:
The SimpleAuth Web Service is not working.

--------------------------------------------------------------------------
Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12052
Date: 11/5/2007
Time: 9:39:53 AM
User: N/A
Computer: DCGS
Description:
The DSS Authentication Web Service is not working.

mkessels schrieb:

> Ok so everything went well and I installed WSUS3. But afterwards I
> noticed that no computers where showing up in the console
> After checking the event log I noticed that pretty much all the virtual
> directories gave errors in the log. I've past the errors below in this
> post.

NETWORKSERVICE must have Read Rights on the Root of the Server.

> --------------------------------------------------------------------------
> Event Type: Error
> Event Source: Windows Server Update Services
> Event Category: Clients
> Event ID: 13042
> Date: 11/5/2007
> Time: 9:39:53 AM
> User: N/A
> Computer: DCGS
> Description:
> Self-update is not working.

http://wsusinfo.onsitechsolutions.com/articles/020.htm

[Errormessages]

Give NETWORKSERVICE Read Rights on the Root and restart the Server. Wait
1 or 2 hours for contacting Clients the WSUS.

Winfried
--
http://www.microsoft.com/germany/win...s/default.mspx
http://www.wsuswiki.com/Home

Hi there,

This appears to be a permissions issue. Like Winfried said, check the
NetworkService has the appropriate rights to the directory.

Cheers
Craig


"mkessels" <mkessels.2zmlzh@DoNotSpam.com> wrote in message
news:mkessels.2zmlzh@DoNotSpam.com...
>
> Hi,
> I'm having a hard time with my WSUS server lately. Everytime used to
> work fine but suddenly it stopped working for no apparent reason.
> At the time I was running WSUS 2.0 and when it stopped working it said
> something like SelfUpdate isn't responding (not sure about the exact
> error) in the wsusadmin site.
> I wanted to ugrade to WSUS 3 anyway so i decided to just uninstall WSUS
> completely and install WSUS 3 afterwards.
>
> Ok so everything went well and I installed WSUS3. But afterwards I
> noticed that no computers where showing up in the console
> After checking the event log I noticed that pretty much all the virtual
> directories gave errors in the log. I've past the errors below in this
> post.
>
> After searching the internet for hours I still couldn't find a solution
> that would work for me so i've decided to make a post myself.
> I've tried several things to fix the problem but none worked (can't
> remember all of the things I've tried).
> I've tried resetting the password on the IUSR_computername and entering
> the new password in all the IIS Wsus sites and the default website.
> I checked all the permissions.
> I also tried completely uninstalling WSUS and IIS and reinstalling them
> but that didn't do the trick either.
>
> So now I'm hoping someone can help me here.
>
> Below are the event logs entries that wsus made.
>
> --------------------------------------------------------------------------
> Event Type: Error
> Event Source: Windows Server Update Services
> Event Category: Clients
> Event ID: 13042
> Date: 11/5/2007
> Time: 9:39:53 AM
> User: N/A
> Computer: DCGS
> Description:
> Self-update is not working.
>
> --------------------------------------------------------------------------
> Event Type: Warning
> Event Source: Windows Server Update Services
> Event Category: Clients
> Event ID: 13051
> Date: 11/5/2007
> Time: 9:39:53 AM
> User: N/A
> Computer: DCGS
> Description:
> No client computers have ever contacted the server.
>
> --------------------------------------------------------------------------
> Event Type: Error
> Event Source: Windows Server Update Services
> Event Category: Web Services
> Event ID: 12002
> Date: 11/5/2007
> Time: 9:39:53 AM
> User: N/A
> Computer: DCGS
> Description:
> The Reporting Web Service is not working.
>
> --------------------------------------------------------------------------
> Event Type: Error
> Event Source: Windows Server Update Services
> Event Category: Web Services
> Event ID: 12012
> Date: 11/5/2007
> Time: 9:39:53 AM
> User: N/A
> Computer: DCGS
> Description:
> The API Remoting Web Service is not working.
>
> --------------------------------------------------------------------------
> Event Type: Error
> Event Source: Windows Server Update Services
> Event Category: Web Services
> Event ID: 12032
> Date: 11/5/2007
> Time: 9:39:53 AM
> User: N/A
> Computer: DCGS
> Description:
> The Server Synchronization Web Service is not working.
>
> --------------------------------------------------------------------------
> Event Type: Error
> Event Source: Windows Server Update Services
> Event Category: Web Services
> Event ID: 12022
> Date: 11/5/2007
> Time: 9:39:53 AM
> User: N/A
> Computer: DCGS
> Description:
> The Client Web Service is not working.
>
> --------------------------------------------------------------------------
> Event Type: Error
> Event Source: Windows Server Update Services
> Event Category: Web Services
> Event ID: 12042
> Date: 11/5/2007
> Time: 9:39:53 AM
> User: N/A
> Computer: DCGS
> Description:
> The SimpleAuth Web Service is not working.
>
> --------------------------------------------------------------------------
> Event Type: Error
> Event Source: Windows Server Update Services
> Event Category: Web Services
> Event ID: 12052
> Date: 11/5/2007
> Time: 9:39:53 AM
> User: N/A
> Computer: DCGS
> Description:
> The DSS Authentication Web Service is not working.
>
>
> --
> mkessels
> ------------------------------------------------------------------------
> mkessels's Profile: http://forums.techarena.in/members/34436.htm
> View this thread: WSUS errors in applicationlog and no computers not showing up
>
> http://forums.techarena.in
>

[mkessels]

I changed the permissions as you suggested and rebooted the server yesterday before I went home but I still get the errors in the eventlog and still no computers showing up.

mkessels schrieb:

> I changed the permissions as you suggested and rebooted the server
> yesterday before I went home but I still get the errors in the eventlog
> and still no computers showing up.

OK, have a look:

http://www.eventid.net/display.asp?e...rvices&phase=1
http://www.eventid.net/display.asp?e...rvices&phase=1

Winfried
--
http://www.microsoft.com/germany/win...s/default.mspx
http://www.wsuswiki.com/Home

[mkessels]

I checked the posts but those settings were allready correct.

[mkessels]

Does anyone have anymore suggestions that I can try?

mkessels schrieb:

> Does anyone have anymore suggestions that I can try?

The same Eventid? Here are some solutions:
http://www.eventid.net/display.asp?e...rvices&phase=1

Winfried
--
http://www.microsoft.com/germany/win...s/default.mspx
http://www.wsuswiki.com/Home

[mkessels]

allready checked all of those solutions but unfortunately none work for me

"mkessels" <mkessels.2zmlzh@DoNotSpam.com> wrote in message
news:mkessels.2zmlzh@DoNotSpam.com...
>
> Hi,
> I'm having a hard time with my WSUS server lately. Everytime used to
> work fine but suddenly it stopped working for no apparent reason.

Hmmm.... nobody jumped on my bandwagon this time...

The diagnostic methodology, here, in such a situation where "...but
suddently it stopped working for no apparent reason..." is to find out what
the "less than apparent" reason is.

Almost always this is because some human being changed something, installed
something, or uninstalled something, without evaluating the ramfications of
those actions on an existing production server.

The key is to identify: What Changed.

> At the time I was running WSUS 2.0 and when it stopped working it said
> something like SelfUpdate isn't responding (not sure about the exact
> error) in the wsusadmin site.

"Selfupdate not responding", in a "working, but not working now" scenario,
almost always means that somebody changed something on your Default Web
Site.

> I wanted to ugrade to WSUS 3 anyway so i decided to just uninstall WSUS
> completely and install WSUS 3 afterwards.

That won't solve anything. :-(

> Ok so everything went well and I installed WSUS3. But afterwards I
> noticed that no computers where showing up in the console

Most likely for the very same reason your WSUS 2.0 quit working.

> After checking the event log I noticed that pretty much all the virtual
> directories gave errors in the log. I've past the errors below in this
> post.

Additional confirmation that somebody mucked with the IIS
configs/permissions.


> I've tried resetting the password on the IUSR_computername and entering
> the new password in all the IIS Wsus sites and the default website.
> I checked all the permissions.
> I also tried completely uninstalling WSUS and IIS and reinstalling them
> but that didn't do the trick either.

Or.... perhaps somebody changed GROUP permissions on the server (or domain
if this machine is a DC).

But, given all that you posted, the most likely cause is that the Default
Web Site does not have anonymous access permissions enabled.


--
Lawrence Garvin, M.S., MCTS, MCP
MVP - Software Distribution (2005-2007)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

[mkessels]

Well if something was changed in the permissions I wouldn't know what :(
I checked all the stuff i can think off.

I double checked the default website and anonymous access is checked and the 4 options below are unchecked.