WSUS setup Troubleshooting

[Pabloa]

I am trying to install the Microsoft Windows Server Update Services. But after few minutes it gets freeze and dont allow me to do anything. Could any one of guide me in troubleshooting Windows Server Update Services setup ? Please help soon.

[Zachary]

Troubleshooting the installation of WSUS is generally very straightforward, and there is not too much to go wrong. There are a few common Windows Server Update Services (WSUS) errors you may come across, and once you identify the problems, they're easy to resolve.As you are having trouble installing WSUS, see this:-

Check setup logs

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.

[Steve123]

You need to ensure you have IIS loaded, and both the .NET Framework 1.1 SP1 and BITS 2.0 installed. On this set of software components, the WSUS server setup should run and complete.If the .NET framework has not been installed correctly, WSUS setup may fail. One symptom of this is the failure to run HideConsoleApp.exe. Search WSUSSetupMsi_timestamp.log file for "HideConsoleApp.exe" and look at the return value of the corresponding custom action. If the return value is non-zero, the executable failed to run. Note that HideConsoleApp.exe may fail because of several other reasons. The MSUSCa_timestamp.log file will give the specific reason it failed. Reinstalling .NET framework may solve this problem.

[Shen]

When you configure the root WSUS server on your network, you need to know whether there will be a proxy server between the WSUS server and the Internet. If you do, you will need to check the following issues before starting to install WSUS:

1. Protocols supported by the proxy server. WSUS will communicate with Microsoft Update via HTTP and SSL, so the proxy server must support both protocols.
   
   
2. The authentication method used by the proxy server (basic authentication or Windows authentication).

Before WSUS can begin functioning properly, you will some montages of the Group's policy to install the Windows Update on your server to WSUS. There are about fifteen montages of the policy of the Group with the Windows Update related, and you can access them by the Editor of the objects of the Group's policy to updates from the Windows Components \ of Windows the Templates \ to the Configuration \ of the Administrative Computer access.On completing the installation, you must launch WSUSADMIN. One important thing to check is that the clients can connect with the place. By default, the clients try to connect to the WUS site using port 80. If you have Wus service on a non-failure port is, remember to update your clients to provide the correct port to use.