Home
.. About WSUS Wiki

RSS

WSUS
.. WSUS FAQ
.. WSUS on SBS
.. WSUS Troubleshooting
.. WSUS News Groups
.. Known WSUS Issues
.. WSUS Links
.. WSUS Wish List

WSUS Documents
.. WSUS Deployment Guide
.. WSUS Installation Guide
.. WSUS Release Notes
.. WSUS Best Practice

SUS
.. SUS FAQ
.. What Is SUS
.. SUS Troubleshooting
.. SUS Links
.. SUS Known Issues
.. SUS FAQ
.. What Is SUS
.. SUS Troubleshooting
.. SUS Links
.. SUS Known Issues

Wiki Community

 .. Wiki Contributors
.. I Love WSUS
.. WSUS Wiki Diary
.. Wiki Statistics
.. To Do Page

Miscellaneous Stuff
.. Other Resources
.. Do You Know?


Site Meter


Terms of Use
Trademarks

Privacy Statement

 

SelfUpdate Tree is Not Working

Show Menu

SYMPTOMS

You may see an event "The SelfUpdate Tree is not working" in the event log, and WSUS Clients may not be able to update to the latest WSUS client software or to communicate with the WSUS Server.

Event ID: 506
Event Source: Windows Server Update Services
Event Category: WUS Service

Description

The SelfUpdate Tree is not working. Clients may not be able to update to the latest WSUS client software and communicate with the WSUS Server. There are several reasons for this potentially happening.

Cause

One reason is that the SelfUpdate service accesses the WSUS server on 127.0.0.1:80. This does not work if you have the website bound to a specific IP address in your IIS configuration.

This can also be caused by incorrect permissions on the self update tree or possibly the entire self update tree or even IIS is corrupted.

Another possible time you see this is if the same server that is running WSUS is also running another web site.

Workaround

The specific workaround depends on the exact cause of this error.

TO resolve the issue around using 127.0.0.1, you can either to set your IIS Configuration to respond to "All unassigned" addresses or add 127.0.0.1 to the list of IP addresses used for Selfupdate.

If your issue is around permisiosns, verify that the SelfUpdate virtual folder in IIS includes anonymous access rights for IUSR account.

If you are running multiple web sites on one system, you can try adding a host header for the other web site(s) on your system.

As a final way to solve the issue, remove both WSUS, IIS and reboot. Then re-install IIS and WSUS.

Status

You can work around this in either of ways suggested above.


Last Modified 2/10/06 9:50 AM