WSUS unable to synchronise updates after updates applied to server

Question

Hi all,
I've landed myself in some hot water by breaking our WSUS server, unfortunately I'm at a loss as to where to go from here and was hoping someone who has some more knowledge of WSUS workings might be able to point me in the right direction.
I have WSUS 3.0 (3.2.7600.226) running on Server 2008 R2. The server also hosts our SCCM environment. As we are rolling out FEP 2010 I updated the server with SP1 and the the other critical / security updates that were available after doing so (bunch of
.NET 3.5 fixes). Since this update however, the WSUS server is unable to synchronise updates. I receive the following message:
WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 65.54.51.180:443
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()
   at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)
   at Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper)
   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS()
   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)
Unfortunately I'm unable to find much on this message out on the web (regarding the no connection could be made part). We had synchronisations errors in the past that ended up being a proxy error, unfortunately I do not control this proxy so I cannot check
if it's getting stuck there - I have logged a request with the team that does however. Just to clarify - WSUS is not configured to use a proxy, it is set to sync directly from MS Updates, however a direct exception is made on the proxy for this server.
I have tried uninstalling the .NET updates from the Server, but haven't gone so far as to remove the SP1 installation yet. I did notice there was a WSUS update available (KB2720211), which I applied, however the installation failed and this broke the console
altogether, so I fixed that issue and reinstalled WSUS on the box, still no love however.
Can anyone out there offer up some suggestions? Many Thanks.

Answer 1

The solution actually might be as simple as logging into the server, make sure the admin consoles for IIS and WSUS are not running, and open an admin command prompt.  Then navigate to the "setup" folder in your install directory (most likely "C:\Program
Files\Update Services\setup") and run this command:
cscript installselfupdateonport80.vbs
Then simply reboot your server.  When it's back "up", log back in and try syncing again.  You should be golden :).
Not really.
The absence of the /selfupdate on port 80 (when using a port 8530-based WSUS server) has been functionally irrelevant for several years, and was only ever relevant to certain WUAgent updates performed on Windows 2000 or Windows XP systems.
But, with the changes made to the WUA in March, 2012, that resource has been absolutely irrelevant since then.
Furthermore, this issue has absolutely nothing to do with a missing /selfupdate feature.
We may well have been given the root cause in the original post, but I focused on the O.P. claiming the change occurred after installing updates, but it's more likely it's actually directly related to the presence of Configuration Manager on the same
server.
From the original post:
I have WSUS 3.0 (3.2.7600.226) running on Server 2008 R2. The server also hosts our SCCM environment.
And the answer  here lies in understanding the implications of installing a Configuration Manager Management Point (MP) on the same machine as WSUS. It can be done but WSUS must be installed on port 8530 for it to work, and after installation of
both, certain SSL modifications must be made to the Default Web Site; otherwise, you'll encounter these type of SSL conflicts within the Default Web Site as a result of the installation of the SCCM MP.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.