Tuesday, September 16, 2014

Software Update Point not working in Config Mgr

Howdy,

In this article, I will add some information related to the error in WCM Logs on the Config Mgr 2012 R2 when you have configured SCCM as Software Update Point.

What symptoms will you find?

- The Software Update Point never works
- The "Run Synchronization" does nothing
- You see no updates getting populated.

Issue:

The key to find any issues within Config Mgr is to look at the logs and that is what i did in this case.
Go to the Logs ( Usually under the logs folder of the SCCM Install directory) and look for WCM logs
You will find this.

Supported WSUS version found    SMS_WSUS_CONFIGURATION_MANAGER    9/15/2014 11:50:44 PM    3632 (0x0E30)
Attempting connection to WSUS server: abc.contoso.com, port: 80, useSSL: False    SMS_WSUS_CONFIGURATION_MANAGER    9/15/2014 11:50:44 PM    3632 (0x0E30)
System.Net.WebException: The request failed with HTTP status 404: Not Found.~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)    SMS_WSUS_CONFIGURATION_MANAGER    9/15/2014 11:50:45 PM    3632 (0x0E30)
Remote configuration failed on WSUS Server.    SMS_WSUS_CONFIGURATION_MANAGER    9/15/2014 11:50:45 PM    3632 (0x0E30)
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=abc.contoso.com SITE=BLR PID=1892 TID=3632 GMTDATE=Tue Sep 16 06:50:45.479 2014 ISTR0="abc.contoso.com" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0    SMS_WSUS_CONFIGURATION_MANAGER    9/15/2014 11:50:45 PM    3632 (0x0E30)
Setting new configuration state to 3 (WSUS_CONFIG_FAILED)    SMS_WSUS_CONFIGURATION_MANAGER    9/15/2014 11:50:45 PM    3632 (0x0E30)
Waiting for changes for 60 minutes    SMS_WSUS_CONFIGURATION_MANAGER    9/15/2014 11:50:45 PM    3632 (0x0E30)
Trigger event array index 0 ended.    SMS_WSUS_CONFIGURATION_MANAGER    9/15/2014 11:50:48 PM    3632 (0x0E30)

  
 








So, it is very clear from the above logs that we are unable to connect to WSUS Server fro ConfigMgr. Rather, it gives 404 error which is Object not found from the web server.



Attempting connection to WSUS server: abc.contoso.com, port: 80, useSSL: False    SMS_WSUS_CONFIGURATION_MANAGER    9/15/2014 11:50:44 PM    3632 (0x0E30)
System.Net.WebException: The request failed with HTTP status 404: Not Found







Let's Look at the WSUS Configuration and its binding


So,  I have got a default binding on my WSUS Site. Now, lets look at the SUP configuration on ConfigMgr.

  
So, this is a problem now. we are trying to connect on Port 80 but, the WSUS is configured to accept connections on 8530. What is next?

There are two solutions:

1. Reconfigure the SUP on the ConfigMgr to connection 8530 and 8531 or
2. Reconfigure the WSUS to use 80 and 443

I would go with solution one as changing WSUS to use port 80 and 443 needs reconfiguration on WSUS as well as IIS.

So, in the SUP on ConfigMgr change the ports to 8530 and 8531

If there are no other errors, you should be able to connect without errors and in the WCM logs, you would see this

user(NT AUTHORITY\SYSTEM) runing application(SMS_WSUS_CONFIGURATION_MANAGER) from machine (abc.contoso.com) is submitting SDK changes from site(BLR)    SMS_WSUS_CONFIGURATION_MANAGER    9/16/2014 12:42:43 AM    3632 (0x0E30)
Attempting connection to WSUS server: abc.contoso.com, port: 8530, useSSL: False    SMS_WSUS_CONFIGURATION_MANAGER    9/16/2014 12:42:48 AM    3632 (0x0E30)
Successfully connected to server: abc.contoso.com, port: 8530, useSSL: False    SMS_WSUS_CONFIGURATION_MANAGER    9/16/2014 12:42:48 AM    3632 (0x0E30)

I hope this helps.

 



 

No comments:

Post a Comment