SUP No Longer Syncing with MS Update

Question

When I run the "Synchronize Software Updates" I am now seeing this error in the wsyncmgr.log log file.

Sync failed: UssCommunicationError: WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.~~at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS

As far as I know I have not made any changes and this error all of a sudden started appearing. Before I go question the network team, I'd like to know what else I can try to troubleshoot this issue. I've already removed the SUP role, uninstalled WSUS, deleted the SUSDB DB Instance, rebooted, installed WSUS, and installed the SUP role back on. I still get the same error. Any help would be appreciated. Thanks in advance!

Answer 1

I had a colleague look into this with me today and he ran IISCrypto on the Server. He set everything to "Best Practices" (button that does this) and then SUP was able to sync. He believes it was some kind of TLS issue but not exactly sure what. Anyways we're able to sync again and deploy patches again. Thanks for the help.

Answer 2

The error message tells you all that you need to know from a ConfigMgr perspective: "An existing connection was forcibly closed by the remote host." This means something at the network layer, between the SUP and where the WSUS catalog is hosted (catalog.update.microsoft.com I believe) is interfering with the sync traffic. What that something is though is beyond the scope of visibility or control of ConfigMgr. You need to review and troubleshoot that network path. There are many possibilities including firewalls, proxy servers, and other network-layer security.

Answer 3

Hi,

Thank you for coming Microsoft Q&A forum.

1.The connection is being force closed. The error would suggest a communication issue. Is there a proxy involved? Is there a Firewall blocking it?

2.Please help check the wcm.log, wsynmgr.log and wsusctrl.log to see if the reinstallation of SUP completed successfully.

3.Please make sure the WSUSPool IIS Application pool is running well. And the service account is in the local WSUS Administrators group.

Here is a similar thread for your reference:
SOLVING SCCM SOFTWARE UPDATES SYNC FAILURES

Thanks for your time.

Best regards,
Simon

Answer 4

Thanks Jason and SimonRen. We rolled the VM back to a state when it was working and ran the sync again. Same error so at this point I believe its a network issue. I've brought this issue to my network tech and he states he doesn't see anything being blocked. Now it's time for me to prove it's network related. I've installed wireshark and will capture the packets. I'm not an expert with it but I think it might help me figure out what's blocking it. I'll give an update when I find out. Thanks again.

Answer 5

Hi,

Thank you very much for your feedback and sharing. We're glad that the question is solved now. It may help others who have similar issue. If you have any questions in future, we warmly welcome you to post in Microsoft Q&A forum again.

Have a nice day!

Best Regards,
Simon