The first thing you’ll probably want to do is gather up any relevant information and log files so that you’ll have them handy when you speak with a Support Engineer for the first time. The exact data we’ll request can vary depending on the issue, so for the sake of this document we’ll err on the side of gathering too much data rather than too little.
If you wish to send any of this data to the support engineer handling your case, please address any email to firstname.lastname@example.org. The files must be in .ZIP format, and the Subject line must include your case number. An example of proper case number formatting is: REG: 133322255555599. The REG: must be included.
In almost all cases we’ll ask for the Application event log from the server. The WSUS health monitoring service automatically checks the health of WSUS components as long as WSUS server components are installed on the computer and the following WSUS components are checked for potential problems:
The events generated by the health monitoring service are logged in the Application event log so chances are good we’ll ask for this.
Beyond the Application event log, the other files we’ll likely request will be determined by the exact issue you’re experiencing. Some of the more common areas are listed below:
WSUS setup creates the following four log files that can help you diagnose problems with setup. These log files are located in the %temp% directory of the user who ran the installation process.
WSUSSetup.log: The status of each of the component installations performed during WSUS setup is logged to this file. You can check this log to see whether any of the component installations failed. If you see a failure, you can check the corresponding log to see what went wrong during the installation of that component.
WSUSSetupMsi_timestamp.log: This log file is generated by MSI for WSUS component setup. Windows installer, before invoking any of the custom actions and standard actions, logs that information to this file. The return values from the custom actions are logged to this file as well. This log file is useful if there are errors invoking any of the custom actions.
WSUSCa_timestamp.log: This log file is used by custom actions. Errors that occurred while executing any of the custom actions in WSUS component or BITS setup are logged to this file.
WSUSWyukonSetup_timestamp.log: This is the log file for Windows Internal Database setup. All Windows Internal Database installation/uninstallation information is logged to this file.
Check the %windir%\WindowsUpdate.log on the client computer to see if there has been any activity or any attempts to contact the server, such as cached server pingbacks.
See KB902093 for information on how to read and troubleshoot using the Windowsupdate.log file.
If you're having client related issues, the first thing to try is our Fix It that will automatically repair most common WSUS client issues with a simple click of the mouse. For information on this visit:
A quick fix for Windows Update client issues
If the link above doesn't do the trick, if you’re seeing issues with clients updating then we'll probably need to obtain the IIS logs on the WSUS server. IIS logs are typically located in %windir%\system32\LogFiles\W3SVC1 for the default Web site. Typical errors might be 404 (file not found) 401/403 (authentication/access), and 500 (Internal server error).
When you’re troubleshooting a problem with WSUS, chances are pretty good that you’re not the first person to encounter your particular issue. With that in mind, the next thing you’ll want to do is a quick search of our Knowledge Base, our blog sites and our forums to see if anyone has already posted the resolution:
If you’re getting an error message, include parts of the exact error text in your search. The exact error message is incredibly important so don’t summarize it when searching or asking for help. Including the exact error message can mean the difference between quickly finding your answer and searching in vain.
Still can’t find anything on your issue? If that’s the case then the next step is to check the prerequisites and troubleshooting information for the particular version of WSUS you’re using.
Windows Server Update Service 3.0 SP2 Release Notes:
Windows Server Update Services 3.0 SP1 Release Notes:
Windows Server Update Services 3.0 Release Notes:
Windows Server Update Services 2.0 ReadMe
906602: How to troubleshoot common Windows Update, Microsoft Update, and Windows Server Update Services installation issues.
910341: You receive error 0x80240020 when you use Windows Update Web site, Microsoft Update Web site, or WSUS to install updates.
Note: The article above describes how to troubleshoot error messages that you may receive when you try to download updates from the Microsoft Windows Update Web site, from the Microsoft Update Web site, or from a Microsoft Windows Server Updates Services (WSUS) server.
922709: Support WebCast: Tips and tricks for troubleshooting Windows Server Update Services
Do you have a question, concern or suggestion? Your feedback is very important to us — it helps us make sure we're on track and keeps us focused on continually improving our services. If your callback is not exceeding your expectations for any reason, or if you have any other feedback on this site or out services please click the button below and let us know.
Note: This page last updated 10/21/2009