WSUS Messages and Troubleshooting Tips
Applies To: Windows Server (Semi-Annual Channel), Windows Server 2016, Windows Server 2012 R2, Windows Server 2012
This topic contains information about the following WSUS messages:
"Computer has not reported status"
"Message ID 6703 - WSUS Synchronization Failed"
"Error 0x80070643: Fatal error during installation"
"Some services are not running. Check the following services [...]"
Computer has not reported status
This message is generated in the WSUS console when a WSUS client computer does not send information to the WSUS server to indicate its current update state. This issue is typically caused by the WSUS client computer, not the WSUS server.
The most common reasons are:
- The computer has lost connectivity to the network:
- The network cable is unplugged.
- An intervening network cable is faulty.
- The computer has a faulty network adapter.
- The network port to which the computer connects has been disabled.
- The wireless adapter is unable to associate with and connect to the corporate wireless access point.
- The computer is turned off. (It has been shut down or is in sleep or hibernation mode.)
Message ID 6703 - WSUS Synchronization Failed
Message: The request failed with HTTP status 503: Service Unavailable.
When you attempt to open Update Services on the WSUS server you receive the following error:
Error: Connection Error
An error occurred trying to connect to the WSUS server. This error can happen for a number of reasons. Please contact your network administrator if the problem persists. Click the reset Server Node to connect to the server again.
In addition to the above, attempts to access the URL for the WSUS Administration website (i.e.,
http://CM12CAS:8530) fails with the error:
HTTP Error 503. The service is unavailable
In this situation, the most likely cause is that the WsusPool Application Pool in IIS is in a stopped state.
Also, the Private Memory Limit (KB) for the Application Pool is probably set to the default value of 1843200 KB. If you encounter this problem, increase the Private Memory Limit to 4GB (4000000 KB) and restart the Application Pool. To increase the Private Memory Limit, select the WsusPool Application Pool and click Advanced Settings under edit Application Pool. Then set the Private Memory Limit to 4GB (4000000 KB). After the Application Pool has been restarted, monitor the SMS_WSUS_SYNC_MANAGER component status, wcm.log and wsyncmgr.log for failures. Please note that it may be necessary to increase the Private Memory Limit to 8GB (8000000 KB) or higher depending on the environment.
For additional details, see: WSUS sync in ConfigMgr 2012 fails with HTTP 503 errors
Error 0x80070643: Fatal error during installation
WSUS Setup uses Microsoft SQL Server to perform the installation. This problem occurs because the user who is running WSUS Setup does not have System Administrator permissions in SQL Server.
To resolve this problem, grant System Administrator permissions to a user account or to a group account in SQL Server, and then run WSUS Setup again.
Some services are not running. Check the following services:
Selfupdate: See Automatic Updates Must Be Updated for information about troubleshooting the Selfupdate service.
WSSUService.exe: This service facilitates synchronization. If you have problems with synchronization, access WSUSService.exe by clicking start, pointing to Administrative Tools, clicking Services, and then finding Windows Server Update Service in the list of services. Do the following:
Verify that this service is running. Click Start if it is stopped or Restart to refresh the service.
Use Event Viewer to check the Application, Security, and System event logs to see if there are any events that might indicate a problem.
You can also check the SoftwareDistribution.log to see if there are events that might indicate a problem.
Web servicesSQL Service: Web services are hosted in IIS. If they are not running, ensure that IIS is running (or started). You can also try resetting the Web service by typing iisreset at a command prompt.
SQL Service: Every service except for the selfupdate service requires that the SQL service is running. If any of the log files indicate SQL connection problems, check the SQL service first. To access the SQL service, click Start, point to Administrative Tools, click Services, and then look for one of the following:
MSSQLSERver (if you are using WMSDE or MSDE, or if you are using SQL Server and are using the default instance name for the instance name)
MSSQL$WSUS (if you are using a SQL Server database and have named your database instance "WSUS")
Right-click the service, and then click Start if the service is not running, or Restart to refresh the service if it is running.