SCCM and WSUS (Full Version)

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager



Message

jdavis375 -> SCCM and WSUS (9/24/2007 11:25:13 AM)

I'm trying to get SCCM and WSUS configured, but keep getting error messages related to SCCM not being able to configure WSUS. here is what I have done so far. (all of this is on a single server)
  1. Installed Windows Server 2003 / SP2 and all updates
  2. Installed SQL 2005 and SQL 2005 SP2
  3. Added IIS (including ASP and BITS)
  4. Updated BITS to 2.5 (KB 923845)
  5. Installed WSUS 3.0. Used SQL for the DB. Used a custom web site (ports 8530/8531). Sync with Microsoft Update. Did not choose to give it a folder to download updates to (this will be managed by SCCM)
  6. Installed SCCM RTM Eval in Mixed Mode.
  7. Added Software Update Point. Active SUP on site server...ports 8530/8531...no ssl...synchronize from Microsoft Update
  8. there is no proxy server involved in this environment

Immediately after installing with those settings, SCCM attempts to connect with WSUS to finish it's configuration and to synchronize the updates catalog. The first time it does so, the following error appears in the SMS_WSUS_SYNC_MANAGER log:
>>>>>>>>>
SMS WSUS Synchronization failed.
Message: The request failed with HTTP status 401: Unauthorized.
Source: Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer.
The operating system reported error 2147500037: Unspecified error
>>>>>>>>>

After this, every time SCCM tries to synchronize the catalog (Computer Management / Software Updates / Update Repository / "Run Synchronization"), the following error appears:
>>>>>>>>
SMS WSUS Synchronization failed.
Message: WSUS server not configured.
Source: CWSyncMgr::DoSync.
The operating system reported error 2147500037: Unspecified error
>>>>>>>>

I have removed and reinstalled both WSUS and the SUP multiple times, but still can't get it working. I even went so far as to create another virtual server and reinstall everything from scratch, but all I succeeded in doing was replicating the problem.

Anyone got a clue as to what might be going on and how to fix it?

Thanks in advance.

Jarvis



sbedri92 -> RE: SCCM and WSUS (9/26/2007 6:42:15 PM)

I ran into the same error in my environment; however my env. is in NATIVE mode, and have my WSUS is on a separate server.  I followed the flowchart on this link http://technet.microsoft.com/en-us/library/bb632481.aspx and still kept getting the error. (for mixed mode go to this link if you haven't already: http://technet.microsoft.com/en-us/library/bb632862.aspx )
to resolve the issue I did the following:
1-  Added SUP as a site role to the central site server I was synchronizing updates to (not as active SUP) that's in addition to adding a SUP site role to my WSUS server which I've done previously.
2-  Start WSUS admin console from the central site server and connect to the WSUS server over SSL, and used the FQDN of the WSUS server.
3-  Ran a manual sync from the SCCM console.  I monitored the wsyncmgr.log and the updates were getting synchronized successfully.
 
So for your situation, I would ensure that you can connect to the WSUS server from the Wsus admin console specifying the port you've listed (8530 for http).  hope that helps!



jdavis375 -> RE: SCCM and WSUS (9/27/2007 11:36:57 AM)

Thanks for the reply. All of my configuration (SCCM, WSUS, all components) is on the same server...so my Active SUP is the only SUP. I had already gone into the WSUS console and run a synchronization there to confirm that WSUS could connect to Microsoft...it was successful...WSUS can connect fine. But I get the errors when I try to run a synchronization from within SCCM. The issue appears to be that SCCM can't successfully connect to and/or configure the WSUS component.

I was able to pull a more complete version of the 401 error that I listed in my original post...not sure if the extra is helpful at all. This comes from the wcm.log file:
>>>>>>>>>>>
System.Net.WebException: The request failed with HTTP status 401: Unauthorized.~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)
>>>>>>>>>>>>

If I read that error correctly (following the three "at"s in the message)...
the 401 is spit out by Microsoft.UpdateServices.Administration.AdminProxy.createupdateserver
which comes from Microsoft.UpdateServices.Administration.AdminProxy.getupdateserver
which come from Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer

So...is it tied to it not being able to connect to the WSUS server? and if so...WHY will it not connect!!! This should be a fairly simple setup that I have spent way too much time getting it to not work.

Thanks again.
Jarvis



lcpc78 -> RE: SCCM and WSUS (10/4/2007 12:35:53 PM)

Does the remote WSUS server also have to have a SCCM role on it in order for it to communicate with the SUP on the SCCM Primary Site?  The current setup I have is one server with every role currently on it. Now I also have a remote WSUS server that I am pointed to and everything is setup correctly.  SSL is enabled and the ports match between the WSUS and SCCM server. 

Now I am getting this error in my WSUSctrl.log file:
Microsoft.UpdateServices.Administration.WsusInvalidServerException: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)

Failures reported during periodic health check by the WSUS Server <--this error is pointing to my SCCM Primary Site and not my WSUS server.  Shouldn't this be pointing to my remote WSUS server?

Any thoughts?

Thanks

Luis

Update:  Disregard.  I moved the SUP role from my Primary Site to the server hosting the WSUS and it's working like a champ now. 



Kan -> RE: SCCM and WSUS (10/8/2007 10:19:20 AM)

If you installed WSUS on the SCCM server, it was probably installed to a different port other than 80 because SMS components were using port 80, and you probably configured the Software Update Point to use port 80 rather than the port to which WSUS is installed.  What you need to do is:
  1. Run IIS Manager, expand the Web Sites node, and see what port "WSUS Administration" is using.
  2. Use the port number from above in the Software Update Point configuration

Kan.



jdavis375 -> RE: SCCM and WSUS (10/23/2007 2:51:14 PM)

Well...I got this resolved. Short answer is that it is related to proxy issues (even though the proxy is not required and all proxy checkboxes are unchecked). I've posted a full detailed description of the problem, symptoms, log entries, and my analysis (with a workaround) on my blog that you can check out if you want more info.

Hope this helps others out there.

Jarvis
http://verbalprocess.wordpress.com/2007/10/23/sccm-and-wsus-issues/



jjgleason -> RE: SCCM and WSUS (10/25/2007 11:18:09 PM)

Great write up Jarvis.  I like the idea of a host file entry.  You may need to change your blog title to the "written processor".  

I doubt this is relevent since you wouldn't use DHCP on your server segment but can you fire up the DHCP console and double check that the WPAD setting is not set for that segment?  I've kicked around using WPAD, but instead use a GPO to point my desktops and servers to the Proxy Auto Config script (pac file).

http://en.wikipedia.org/wiki/Web_Proxy_Autodiscovery_Protocol



jdavis375 -> RE: SCCM and WSUS (10/26/2007 12:30:17 PM)

Actually...for reasons outside of my control...DHCP is enabled on that server segment. That is where it was getting the proxy info from.

Thanks for the encouragement on the blog entry...it will motivate me to take the time to do more write-ups. I'm like a puppy...encourage me and I'll do tricks. :-)

Jarvis



jonf -> RE: SCCM and WSUS (11/1/2007 3:03:51 PM)

I had this exact same problem with the same error codes and behavior.  I read through your article and the links you provided and they were very helpful.  I ended up getting it working and I believe it was a combination of things.

I added the SCCM computer account to the WSUS server.

Then I also checked the 'Use a proxy server when synchronizing' option on the ConfigMger SUP Properties and specified my WSUS server name (FQDN not needed) and the default port of 80 which is what my WSUS server was configured as.  I did not add credentials to connect to the proxy server.

I attempted to synchronize again and everything works. 

I was thrown off because I do not have a proxy server for my WSUS, but apparently ConfigMgr needed the WSUS server specified for it to synchronize properly.



nbellur -> RE: SCCM and WSUS (6/26/2008 9:13:48 PM)

Today I had the same issue(SMS WSUS Synchronization failed.
Message: WSUS server not configured.
Source: CWSyncMgr::DoSync.
The operating system reported error 2147500037: Unspecified error ) I was able to overcome this. The name in the proxy was not matching (FQDN) what was in DNS ( I pinged the proxy name from the command prompt). Later, I added an entry in the host file which had the host name (present in proxy) and IP address ( from the ping result). That worked. Now, SCCM server is able to sync.



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.390625