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 Contributors
.. I Love WSUS
.. WSUS Wiki Diary
.. Wiki Statistics
.. To Do Page
Miscellaneous Stuff
.. Other Resources
.. Do You Know?
Terms of Use
Trademarks
Privacy Statement
Troubleshooting WSUS Installation |
Troubleshooting the installation of WSUS is generally very straightforward, and there is not too much to go wrong. The following steps should get you up and going.
First you should ensure you have all the necessary pre-requsites, and have them installed. See WSUS Installation Prerequsites for more information on these. 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.
On the completing the installation, you should be able to launch the WSUSADMIN site. One important thing to check is that clients can connect to the site. By default, clients attempt to connect to to the WUS site using port 80. If you have the Wus Service running on a non-default port, remember to configure your clients to use the correct port.
If you are migrating from SUS to WUS, you have the option of migrating the updates from your old SUS server by using the wsutil.exe comment. See Working with WSUSUTIL for details on this comand and see Troubleshooting WSUS Upgrade for issues with upgrading. NB: you must perform a synchronisation of the WUS server before migrating updates using wsutil.
Comments:
From Deepak - 5/16/08 2:34 AM
From Deepak - 5/15/08 11:01 AM
Bro,
there seems to be some issue with your SQL application. Refer below link for details.
http://wsus.editme.com/TroubleshootingWSUSInstallation
Hope this will resolve your problem
Deepak.
From donald71 - 5/15/08 7:51 AM
Hallo i had a same Problem with upgrading Wsus 30 to Sp1 after deinstallation from the old one.
Here is my Install log File!
Thanks for help
2008-05-15 10:04:30 Success MWUSSetup Validating pre-requisites...
2008-05-15 10:04:43 Success MWUSSetup Creating database backup...
2008-05-15 10:08:32 Success MWUSSetup Removing Wsus...
2008-05-15 10:09:45 Success MWUSSetup Installing ASP.Net
2008-05-15 10:10:18 Success MWUSSetup ASP.Net is installed successfully
2008-05-15 10:10:18 Success MWUSSetup Installing wYukon using MSI on Win2k3
2008-05-15 10:10:18 Success MWUSSetup wYukon is already installed on this machine
2008-05-15 10:10:18 Success MWUSSetup Installing WSUS...
2008-05-15 10:10:23 Success CustomActions.Dll Successfully set propery of WSUS admin groups' full names
2008-05-15 10:10:24 Success CustomActions.Dll .Net framework path: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
2008-05-15 10:10:25 Success CustomActions.Dll Creating user group: WSUS-Berichterstatter with Description: WSUS-Administratoren, die nur Berichte auf dem Windows Server Update Services-Server ausführen können.
2008-05-15 10:10:25 Success CustomActions.Dll Creating WSUS-Berichterstatter user group
2008-05-15 10:10:25 Success CustomActions.Dll WSUS-Berichterstatter user group already exists
2008-05-15 10:10:25 Success CustomActions.Dll Successfully created WSUS-Berichterstatter user group
2008-05-15 10:10:25 Success CustomActions.Dll Creating user group: WSUS-Administratoren with Description: WSUS-Administratoren können den Windows Server Update Services-Server verwalten.
2008-05-15 10:10:25 Success CustomActions.Dll Creating WSUS-Administratoren user group
2008-05-15 10:10:25 Success CustomActions.Dll WSUS-Administratoren user group already exists
2008-05-15 10:10:25 Success CustomActions.Dll Successfully created WSUS-Administratoren user group
2008-05-15 10:10:25 Success CustomActions.Dll Successfully created WSUS user groups
2008-05-15 10:37:19 Error MWUSSetup InstallWsus: MWUS Installation Failed (Error 0x80070643: Schwerwiegender Fehler bei der Installation.)
2008-05-15 10:37:19 Error MWUSSetup CUpgradeDriver::PerformSetup: WSUS installation failed (Error 0x80070643: Schwerwiegender Fehler bei der Installation.)
2008-05-15 10:37:19 Error MWUSSetup CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Schwerwiegender Fehler bei der Installation.)
From Marty - 12/18/06 2:33 PM
From khennett - 11/10/06 4:11 PM
I am installing WSUS 2 SP1 on a Windows 2000 Server with SP4, IIS 5 (with the lockdown tool), SQL Server 2000 SP5, .NET 1.1 SP1 and BITS 2.0. So in other words I have all the pre-requisites. Yet when I install I get to the point in the installation where it tries to detect my web sites in IIS which are up and working. It returns an error of being unable to locate any IIS web sites and to make sure it is running.
Has anyone run into this problem or know what I am doing wrong. Nothing on Microsoft's site about this error. Thanks.
From gujomania - 4/19/06 11:14 AM
I don't even get that far. I keep getting these errors:
2006-03-16 10:04:51 Success MWUSSetup WSUS Server Setup Started.
2006-03-16 10:04:51 Success MWUSSetup Parsing command line arguments
2006-03-16 10:04:51 Success MWUSSetup WSUS Setup: Performing Install
2006-03-16 10:04:52 Success MWUSSetup Validating pre-requisites
2006-03-16 10:04:52 Error MWUSSetup CoCreateInstance failed to create IBackgroundCopyManager interface (Error 0x80070005: Access is denied.)
2006-03-16 10:04:52 Error MWUSSetup IsBitsInstalled failed (Error 0x80070005: Access is denied.)
2006-03-16 10:04:52 Error MWUSSetup Failed to determine if BITS 2.0 is installed (Error 0x80070005: Access is denied.)
2006-03-16 10:04:52 Error MWUSSetup ValidatePreRequisites failed (Error 0x80070005: Access is denied.)
2006-03-16 10:04:52 Error MWUSSetup Validation of PreRequsites failed (Error 0x80070005: Access is denied.)
2006-03-16 10:04:52 Error MWUSSetup PerformInstall failed (Error 0x80070005: Access is denied.)
2006-03-16 10:04:52 Error MWUSSetup CProgressManager::EnableCancel: GetDlgItem returning error (Error 0x80070578: Invalid window handle.)
2006-03-16 10:04:52 Success MWUSSetup Rolling back Installation
2006-03-16 10:04:52 Success MWUSSetup WSUS Server installation failed. You can look at C:\Program Files\Update Services\LogFiles\WSUSSetup_060316_1004.log file to determine the cause of the failure
2006-03-16 10:04:52 Success MWUSSetup Insert string: %1 For more information, see the Setup log "%2".
2006-03-16 10:04:52 Success MWUSSetup szErrorType: Microsoft Windows Server Update Services could not be installed.
2006-03-16 10:04:52 Success MWUSSetup ErrorLog: C:\Program Files\Update Services\LogFiles\WSUSSetup_060316_1004.log
2006-03-16 10:04:52 Success MWUSSetup StringObtained: Microsoft Windows Server Update Services could not be installed. For more information, see the Setup log "C:\Program Files\Update Services\LogFiles\WSUSSetup_060316_1004.log".
2006-03-16 10:05:00 Error MWUSSetup WSUS Setup: Performing Install Failed. (Error 0x80070005: Access is denied.)
2006-03-16 10:05:00 Error MWUSSetup WSUS Setup Failed. (Error 0x80070005: Access is denied.)
Any Ideas??
From tomek29kce - 1/2/06 8:14 AM
have you resove this problem?
I have got this same :-(
From molnes - 8/2/05 5:50 PM
Well something can apparently go wrong despite that one have all the necessary pre-requsites.
This is where it fails on my server:
Quote from log:
Creating WSUS Administrators user group 2005-08-01 11:58:15 Success CustomActions.Dll WSUS Administrators user group already exists 2005-08-01 11:58:15 Success CustomActions.Dll Successfully created WSUS Administrators user group 2005-08-01 11:59:26 Error CustomActions.Dll SQL command is returning error (Error 0x80004005: Unspecified error)...........
Last Modified 3/22/05 10:31 AM
Hi,
sry for incorrect link. but look for below mentioned descript. this should resolve the issue. try and let me know the result
First Possible Cause: An incompatible default DCOM impersonation level.
To verify that your default level is appropriate and fix the problem, follow these steps
On a Windows 2000 machine:
1) launch "dcomcnfg.exe"
2) choose "Default Properties"
3) in the "Default Impersonation Level" combo box (at the bottom), choose "Impersonate" or "Identify".
On a Windows XP SP2 machine:
1) launch "dcomcnfg.exe"
2) navigate to "Component Services\Computers\My Computer"
3) right click on "DCOM Config" and choose "Properties"
4) choose the "Default Properties" tab
5) select "Impersonate" or "Identify".
If you have a specfic need to choose "Delegate" you choose that option as well, but I would not recommend it as the default choice if it is not required.
Second Possible Cause: Corrupt default access permisisons on the machine
It is possible for the default DCOM access permissions on the machine to be corrupted. This can sometimes happen if the DCOMCnfg tool is used to view or edit the default access permission ACLs.You can check for this situation and resolve this issue by doing the following:
1. launch regedit.exe
2. Locate the following key: HKEY_LOCAL_MACHINE\Software\Microsoft\Ole
3. Look for the value "DefaultAccessPermission" (NOT DefaultLaunchPermission)
If this value exists, it is possible that the value has been corrupted or is incorrect. If you don't have the need for specific default permissions, you can restore the original permissions on the machine by deleting this value (do not delete the entire reg key, just that one value.)