Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3136
  • Last Modified:

WSUS 3.0 Errors

Hi all.

I have a domain member server server running Server Enterprise 2008 SP1 (IIS7), a SQL 2008 instance and SCCM 2007 SP1.  I have been trying to install WSUS 3.0 SP1 onto this server and run into errors.

I install WSUS with the following configuration:
-Full Install
-Store updates locally (D:\WSUS)
-Use the existing SQL 2008 Instance to host the DB
-Create a new Website for WSUS using port 8530

This install completes successfully but give the following error when trying to start the configuration wizard: "An error occured when communicating with the server, and this wizard must be closed. You may restart the WSUS Server Configuration Wizard from the Options Page in the WSUS 3.0 console."

When I try and connect to the server through the WSUS Console I get the following: "Cannot connect to 'servername'. The server may be using another port or different Secure Sockets Layer setting."

When I checked the event log, I have the following:

Log Name:      Application
Source:        Windows Server Update Services
Date:          08/02/2009 18:35:22
Event ID:      12002
Task Category: 9
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      
Description:
The Reporting Web Service is not working.

Log Name:      Application
Source:        Windows Server Update Services
Date:          08/02/2009 18:35:22
Event ID:      12012
Task Category: 9
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      
Description:
The API Remoting Web Service is not working.

Log Name:      Application
Source:        Windows Server Update Services
Date:          08/02/2009 18:35:22
Event ID:      12032
Task Category: 9
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      
Description:
The Server Synchronization Web Service is not working.

Log Name:      Application
Source:        Windows Server Update Services
Date:          08/02/2009 18:35:22
Event ID:      12022
Task Category: 9
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      
Description:
The Client Web Service is not working.

Log Name:      Application
Source:        Windows Server Update Services
Date:          08/02/2009 18:35:22
Event ID:      12042
Task Category: 9
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      
Description:
The SimpleAuth Web Service is not working.

Log Name:      Application
Source:        Windows Server Update Services
Date:          08/02/2009 18:35:22
Event ID:      12052
Task Category: 9
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      
Description:
The DSS Authentication Web Service is not working.

Log Name:      Application
Source:        Windows Server Update Services
Date:          08/02/2009 18:35:43
Event ID:      7032
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      
Description:
The WSUS administration console was unable to connect to the WSUS Server via the remote API.

Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

System.Net.WebException -- The request failed with HTTP status 405: Method Not Allowed.

Source
Microsoft.UpdateServices.Administration

Stack Trace:
   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()
   at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer()
   at Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE.OOBEWizard.get_AdminApiTools()
   at Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE.OOBEWizard.get_ServerState()
   at Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE.OOBEWizard.SetNavigationItemEnabledStates()
   at Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE.OOBEWizard.InitializeNavigationItems()
   at Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE.OOBEWizard.OOBEWizardInitialize()

I've tried all sorts, checking permissions, using default website, changing service logon account.  No change.

Hope someone can help.
0
James_Charlton
Asked:
James_Charlton
  • 6
  • 4
1 Solution
 
Donald StewartNetwork AdministratorCommented:
0
 
Donald StewartNetwork AdministratorCommented:
And if that isnt your case


Make sure the value for PortNumber under this key
 HKLM\SOFTWARE\Microsoft\Update Services\Server\Setup is set to the correct
 port (the one your WSUS site is on)
0
 
James_CharltonAuthor Commented:
Hi dstewartjr

Thanks for the prompt reply.

I checked for the existance of the selfupdate folder under the default website and it already exists.  I did run through the permissions though and corrected them.  The errors still exists after a restart.

I also checked the registry key and it is indeed set to the correct port (8530)

Regards

James
0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
Donald StewartNetwork AdministratorCommented:
0
 
Donald StewartNetwork AdministratorCommented:
0
 
James_CharltonAuthor Commented:
I've been through the entire WSUS thread with no joy.

Tried the second link, still no joy.
0
 
Donald StewartNetwork AdministratorCommented:
This may be your issue then

http://support.microsoft.com/kb/938699
0
 
James_CharltonAuthor Commented:
Thats interesting, I shall try that tomorrow.
0
 
James_CharltonAuthor Commented:
Fixed it, I had upgraded the server from 2003 to 2008.  I found this link which has fixed it.

http://kbalertz.com/948139/services-working-upgrade-Windows-Server-computer-Windows-Server.aspx
0
 
rochestermnCommented:
I've been running wsus 3 for some time.  We've had 3 XP pc's running the remote console and that's been working fine..   But I tried to add a 4th console running XP sp3, and I'm getting an error that you can't connect to the server, it may be using a different port message.   I've re-checked settings and didn't find anthing obvious.   I note that when I attempted to install windowsxp-kb907265-x86-enu (microsoft mgmt console 3, it says it can't because our sp is newer)....so this must be built into sp3.  
We're running std port 80 (not cert).    the other consoles were installed when they were at sp2, and later upgraded to sp3.   And they continue to work fine.  
Any good ideas?
thanks
0
 
Donald StewartNetwork AdministratorCommented:
I suggest you open a new question as this question is closed and it is not fair for the other experts that might have insight on your question.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now