Home
.. About WSUS Wiki

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?

1. ASPNET_WP.36 errors in Event log.

You may see the following error in the event log:

2004-11-23 15:36:14.946 UTC Warning aspnet_wp.36 SusEventLog.WriteEntry
Failed to write message to Event Log: Information, 389, Synchronization
settings were modified.
System.InvalidOperationException: Cannot open log for source {0}. You
may not have write access. ---> System.ComponentModel.Win32Exception:
Access is denied

This is a known issue with running WSUS RC1 on Windows 2000 and IIS5. WSUS runs in the context of the ASPNet account which in some cases does not seem to have write access to the System Event log.

The simplest workaround is to increase the permissions of the ASPNet account although that obviously increases your risks.

2. Update Service error on WSUS Admin site

You may see the following on the WSUS admin home page:

One or more Update Service services could not be contacted. Check your server status and ensure that the Windows Server Update Service is running. Non-running services: SelfUpdate.

This message can occur from one of two problems.

First, if you receive this message in the To Do List on the WSUS console home page, you might have an assigned IP address set to the default Web site on your WSUS server.

WSUS pings http://localhost/selfupdate/iuident.cab in order to check the health of the SelfUpdate tree. If you have set an assigned IP address to the default Web site, "localhost" in the URL will cause this error message. Client computers can still access the SelfUpdate tree (provided the GPO setting has the WSUS server name--which is usually the case).

To avoid this issue, do the following:

1. On the WSUS server, open IIS Manager. In the tree, expand Computername, expand Web Sites, right-click Default Web Site, and then click Properties.

2. On the Web Site tab, under Web Site Identification, enter (All Unassigned) in the IP address box, click OK, and then close IIS Manager.

3. Open Services (click Start, point to Administrative Tools, and then click Services). In the details pane, right-click Update Services, click Restart, and then close Services.

Second, you may see this error message if you are running Windows Server 2003 Service Pack 1. The cause for SP1 creating this problem is not yet known, but it can be remedied by uninstalling and reinstalling WSUS and IIS. Do the following:

1. In
   1. 1. Add and Remove Programs, uninstall Microsoft Windows Server Update Services. You can choose to leave your existing databases, logs, and downloaded updates in place.
      2. Click on Add/Remove Windows Components and go to the Application Server section. Remove both ASP.NET and Internet Information Services (IIS).
      3. Reverse the process. Go to the Add/Remove Windows Components and re-install both ASP.NET and Internet Information Services (IIS).
      4. Reinstall the WSUSSetup.exe package.
   2. Click on Add/Remove Windows Components and go to the Application Server section. Remove both ASP.NET and Internet Information Services (IIS).
   3. Reverse the process. Go to the Add/Remove Windows Components and re-install both ASP.NET and Internet Information Services (IIS).
   4. Reinstall the WSUSSetup.exe package.
2. Click on Add/Remove Windows Components and go to the Application Server section. Remove both ASP.NET and Internet Information Services (IIS).
3. Reverse the process. Go to the Add/Remove Windows Components and re-install both ASP.NET and Internet Information Services (IIS).
4. Reinstall the WSUSSetup.exe package.

Launch IE and go to your WSUS admin page (usually http://localhost/WSUSAdmin). The SelfUpdate error message should now be gone.

Launch IE and go to your WSUS admin page (usually http://localhost/WSUSAdmin). The SelfUpdate error message should now be gone.

Launch IE and go to your WSUS admin page (usually http://localhost/WSUSAdmin). The SelfUpdate error message should now be gone.

(skatterbrain:) It has also been suggested that if the IIS permissions on the default web are modified somehow to Integrated Authentication (not anonymous) it will do this.  Allowing Anonymous authentication might correct this problem possibly.  In any case, the suggestion above does indeed work.

 

Error: Non-running services: SelfUpdate

Reason: Installed WSUS as its own Virtual Website, no apsnet installed

Solution: C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322>aspnet_regiis.exe -i

Note: Version number of dotNet Framework may differ, ie ( path  "C:\WINDOWS\Microsoft.NET\Framework\<xxxx>" will change.)


 

3. Content download does not happen; event -log shows content download failure (EVENT ID 364) that server does not support the Range protocol header.

You may see the following in the reporting Event log:

Content file download failed. Reason: The server does not support the necessary HTTP protocol. Background Intelligent Transfer Service (BITS) requires that the server support the Range protocol header.

If you receive this error your proxy environment may not support HTTP 1.1 Range Requests. Check and upgrade your proxy, or you can manually work around this by executing the following commands:

1. “%programfiles%\Update Services\tools\osql\osql.exe” -S servername\WSUS -E -b -n –Q “USE SUSDB update tbConfigurationC set BitsDownloadPriorityForeground=1” (note: substitute your WSUS server name for servername)


2. Open Services (click Start, point to Administrative Tools, and then click Services). In the details pane, right-click Update Services, click Restart, and then close Services.

 

3. You might want to try a synchronisation after appliying this setting to kickstart the download.

 

 

4. Content download does not happen; event -log shows content download failure (EVENT ID 364) that server does not support the Range protocol header.

You may see the following in the reporting Event log:

Content file download failed. Reason: The server does not support the necessary HTTP protocol. Background Intelligent Transfer Service (BITS) requires that the server support the Range protocol header.

If you receive this error your proxy environment may not support HTTP 1.1 Range Requests. Check and upgrade your proxy, or you can manually work around this by executing the following commands:

1. “%programfiles%\Update Services\tools\osql\osql.exe” -S servername\WSUS -E -b -n –Q “USE SUSDB update tbConfigurationC set BitsDownloadPriorityForeground=1” (note: substitute your WSUS server name for servername)


2. Open Services (click Start, point to Administrative Tools, and then click Services). In the details pane, right-click Update Services, click Restart, and then close Services.

 

3. You might want to try a synchronisation after appliying this setting to kickstart the download.

 5. Event 364 in the event log

You see the following in the application log:

    Content download failed. Reason: Access is denied. Source File < snip > destination File: d:\wsus\wsuscontent......

If you receive this error, assign Network Services the Read rights to the root of the drive mentioned in destination file above (in this case D:)

Drop to a command prompt on the server and type in the following

d:
cd \
calcs .                                                                                                     <--- this provides you with the current state before you change it
cacls . /e /g "NT AUTHORITY\NETWORK SERVICE":r
cacls .

Note that you will probably find that you can't assign Network Service within the security tabs in Windows explorer - that is why you need to use cacls.exe 

To test is has worked, go to your updates, select a failed download and then choose Retry Download from the menu. The main page should update to show you the download status