[dlabette]

I installed WSUS 3.0 on a Windows Server 2003 Standard Edition Service Pack 2 server. The server is also a domain controller.

At the final part of the WSUS 3.0 install I received an error message. The title of the dialog box was "WSUS Server Configuration Wizard". The content was "An error occurred 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 to use Internet Explorer to access http://servername or http://servername/wsusadmin, I get the message "Service Unavailable".

When I click Start > Programs > Administrative Tools > Microsoft Windows Server Update Services 3.0, the Windows Server Update Services snap-in opens up, but I cannot "Connect to Server". When I try to connect to server, I type http://servername and click connect and then receive an error message. The title of the dialog box is "Connect to Server". The content is "Cannot connect to 'HTTP://SERVERNAME'. The machine could not be contacted."

When I check services.msc, the "Update Services" service has the status of started.

[Samok]

dlabette, on Mon 14th May 2007, 07:58 pm, said:

I installed WSUS 3.0 on a Windows Server 2003 Standard Edition Service Pack 2 server. The server is also a domain controller.

At the final part of the WSUS 3.0 install I received an error message. The title of the dialog box was "WSUS Server Configuration Wizard". The content was "An error occurred 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 to use Internet Explorer to access http://servername or http://servername/wsusadmin, I get the message "Service Unavailable".

When I click Start > Programs > Administrative Tools > Microsoft Windows Server Update Services 3.0, the Windows Server Update Services snap-in opens up, but I cannot "Connect to Server". When I try to connect to server, I type http://servername and click connect and then receive an error message. The title of the dialog box is "Connect to Server". The content is "Cannot connect to 'HTTP://SERVERNAME'. The machine could not be contacted."

When I check services.msc, the "Update Services" service has the status of started.

WSUS 3 used MMC console and not HTTP ( like WSUS 2)
IN the connect server type your computer name

if is not working check your security DB, IIS, Folder

Sam

[dlabette]

Samok, on Wed 16th May 2007, 11:59 am, said:

WSUS 3 used MMC console and not HTTP ( like WSUS 2)
IN the connect server type your computer name

if is not working check your security DB, IIS, Folder

I still cannot connect. What do you mean by "check your security DB, IIS, Folder"?

Also, I have noticed Windows Server Update Services events in the application section of event viewer. The errors have event IDs of: 12002, 12012, 12022, 12032, 12042, 12052, and 13042. The warning has an event ID of 13051.

Event ID 12002 description: The reporting Web Service is not working.
Event ID 12012 description: The API Remoting Web Service is not working.
Event ID 12022 description: The Client Web Service is not working.
Event ID 12032 description: The Server Synchronization Web Service is not working.
Event ID 12042 description: The SimpleAuth Web Service is not working.
Event ID 12052 description: The DSS Authentication Web Service is not working.
Event ID 13042 description: Self-update is not working.
Event ID 13051 description: No client computers have ever contacted the server.

[sscooktx]

I have the same problem exactly -- did anyone ever provide a good answer for this?

dlabette, on Thu 31st May 2007, 09:05 am, said:

Samok, on Wed 16th May 2007, 11:59 am, said:

WSUS 3 used MMC console and not HTTP ( like WSUS 2)
IN the connect server type your computer name

if is not working check your security DB, IIS, Folder

I still cannot connect. What do you mean by "check your security DB, IIS, Folder"?

Also, I have noticed Windows Server Update Services events in the application section of event viewer. The errors have event IDs of: 12002, 12012, 12022, 12032, 12042, 12052, and 13042. The warning has an event ID of 13051.

Event ID 12002 description: The reporting Web Service is not working.
Event ID 12012 description: The API Remoting Web Service is not working.
Event ID 12022 description: The Client Web Service is not working.
Event ID 12032 description: The Server Synchronization Web Service is not working.
Event ID 12042 description: The SimpleAuth Web Service is not working.
Event ID 12052 description: The DSS Authentication Web Service is not working.
Event ID 13042 description: Self-update is not working.
Event ID 13051 description: No client computers have ever contacted the server.

[Bumpy]

sscooktx, on Sat 16th Jun 2007, 04:42 am, said:

I have the same problem exactly -- did anyone ever provide a good answer for this?

I Have a open case with Microsoft on this issue, You can try changing the service startup account to 'Local System' This has worked for me on all bar one server. MS are still investigating

[dstrebel]

On what service did you use local system?

[Bumpy]

dstrebel, on Mon 18th Jun 2007, 10:54 am, said:

On what service did you use local system?

'Update Services'

[brads]

Bumpy, on Mon 18th Jun 2007, 12:53 pm, said:

dstrebel, on Mon 18th Jun 2007, 10:54 am, said:

On what service did you use local system?

'Update Services'

Hi,

I am too receiveing the message when installing WSUS 3.0. I have completed all the suggested issues from the forum but without any luck. I am receiving the following in my Event Manager:

The DSS Authentication Web Service is not working. Event ID 12052
The SimpleAuth Web Service is not working. ID 12042
The Client Web Service is not working. ID 12022
The Server Synchronization Web Service is not working. ID 12032
The API Remoting Web Service is not working. 12012
The Reporting Web Service is not working. 12002

Can you assist?

Thanks

Brad

[sblair588]

Add me to the list of people who also got the same errors & event log messages.

I managed to get it working by uninstalling WSUS 3.0 & .Net 3.0 & reinstalling WSUS 3.0.

In my case, it seemd like .Net 3.0 was the problem.

[timbo05]

I found that when I unchecked the requirement for SSL for the ApiRemoting30, ClientWebService, ReportingWebService, ServerSyncWebService, SimpleAuthWebService and SelfUpdate virtual directories within IIS, the errors in my event log went away.

[jimgo]

timbo05, on Tue 26th Jun 2007, 03:30 pm, said:

I found that when I unchecked the requirement for SSL for the ApiRemoting30, ClientWebService, ReportingWebService, ServerSyncWebService, SimpleAuthWebService and SelfUpdate virtual directories within IIS, the errors in my event log went away.

Can you elaborate on this procedure. how did you specifically do this?

[hastingse]

I am also having the same issue.

I'm currently running Windows Server 2003 SP2 with all of the latest security updates.

I've double checked IIS and NTFS permissions and all seems to be correct.
I've uninstalled and reinstalled several times.
Uninstalled and deleted WSUS and IIS directories.
Changed the login for the service from Network Service to Local System account and a domain user.

Also checked the require SSL settings and they are not checked on any of the VD.

The DSS Authentication Web Service is not working.
The SimpleAuth Web Service is not working.
The Client Web Service is not working.
The Server Synchronization Web Service is not working.
The Reporting Web Service is not working.
Self-update is not working.

These events pop up in the Application event log as soon as the Updates Services service starts.
I've found and followed a couple of KB articles, they all point to a permissions issue.
But at least in my case the permissions are correct.

This post has been edited by hastingse: 27 Jun 2007, 07:11

[djmrmagic]

I had a similar issue and yes changing the "Update Service" logon to Local System worked, also so did adding "machinename\Network Service" to the local administrators group

[jpanlilio]

My issue is not as bad,
I get a on my Event Viewer on my SBS 2003 (not R2):

Event Source: Windows Server Update Services
Event Category: Clients
Event ID: 13051
Date: 6/27/2007

Description:
No client computers have ever contacted the server.

My environment is sbs2003 and all Vista Business; I can't add any of the clients to WSUS; it can't see any of the clients on the network

[dlabette]

sblair588, on Wed 20th Jun 2007, 12:03 am, said:

I managed to get it working by uninstalling WSUS 3.0 & .Net 3.0 & reinstalling WSUS 3.0.

I tried that, but it did not resolve my problem.

djmrmagic, on Wed 27th Jun 2007, 12:14 pm, said:

I had a similar issue and yes changing the "Update Service" logon to Local System worked, also so did adding "machinename\Network Service" to the local administrators group

I tried changing the 'update service' logon to local system, but it did not resolve my problem.
I cannot add 'machinename\network service' to the local administrators group because the computer is a domain controller. The Local Users and Groups snap-in cannot be used on a domain controller.

[mikeofcontex]

dlabette, on Wed 27th Jun 2007, 03:06 pm, said:

sblair588, on Wed 20th Jun 2007, 12:03 am, said:

I managed to get it working by uninstalling WSUS 3.0 & .Net 3.0 & reinstalling WSUS 3.0.

I tried that, but it did not resolve my problem.

djmrmagic, on Wed 27th Jun 2007, 12:14 pm, said:

I had a similar issue and yes changing the "Update Service" logon to Local System worked, also so did adding "machinename\Network Service" to the local administrators group

I tried changing the 'update service' logon to local system, but it did not resolve my problem.
I cannot add 'machinename\network service' to the local administrators group because the computer is a domain controller. The Local Users and Groups snap-in cannot be used on a domain controller.

I had file access auditing turned on and found several files is windows\temp with failures. I changed network service permissions to modify and everything took off.

[baldcat]

Hey guys, try re-installing .NET2

What normally happens if a Security update comes down for .NET2 and it doesn't work 99% of the time due to service already in use..
This breaks stuff, so a manually repair of .NET2 should get you up and going in no time

[denta]

My solution (it works for me):

Our WSUS-Website for 3.0 worked on Port 80, now on Port 80 and 8530:

I've added Port 8530 to the port 80 under IIS -> WSUS Administration Website -> Properties -> on the Web Site tab click the Advanced button -> add Port 8530 (now you use Port 80 and(!) 8530 for WSUS-Administration)
Restart IIS

use wsusutil.exe under /Tools with: wsusutil checkhealth

Now, i get no error (12052,12042, 12022, etc.)

I think, it's the same problem, if your site works on Port 8530. Try to add Port 80 to your WSUS-Website.

[Bumpy]

Ok i have found the answer for my situation:

Our servers do NOT have internet access by default, we run a ISA proxy server, with WebMarshall security/block lists.
Running the following command on the WSUS server enabled the service to start 'proxycfg -p 0.0.0.0' This is an invalid address, but still the 'Update Service' starts, remove the proxy settings using the 'proxycfg -d' command, stops the service starting

I have requested a please explain from my MS engineer in China

[kikuyu]

Hallo,
I had the sames errors on my 2K3+SP2 server
------------------------
13042 Self-update is not working
12002 The Reporting Web Service is not working
12012 The API Remoting Web Service is not working.
12032 The Server Synchronization Web Service is not working
12022 The Client Web Service is not working.
12042 The SimpleAuth Web Service is not working
12052 The DSS Authentication Web Service is not working.
------------------
I gave the rights to IUSR_MACHINE on the \WSUS\WSUScontent.
and restarted the default web site.
The errors were gone.
A+