SOLVED Unable to Connect to local WSUS Server

[MagnumVP]

The SMS_ISVUPDATES_SYNCAGENT.log is showing "Unable to Connect to local WSUS Server" every minute ans has been for days (the log only goes back 3 days and it's full with these messages).
I recently performed an in-place upgrade from 2012 R2 to what is now 1910 with Hotfix. So far everything seems to be working as expected but notices this last night and I'm not sure where to look.
I can connect to the local SQL DB where WSUS DB is located and connect to the SCCM DB as well.
This is the only Software Update point and syncs with MS directly.

 

[Youssef Saad]

The SMS_ISVUPDATES_SYNCAGENT.log is related for the third-party software updates.

Check the the following log files instead of the above:

• WCM.log
• WSUSCtrl.log
• wsyncmgr.log

 

[MagnumVP]

I was able to get the WSUS service back up and running on an upgrade OS 2016 Server. Hope this helps someone in the future.

1. Removed the Software Updates Roles from SCCM - Monitor SUSSetup.log
2. Rebooted
3. Removed WSUS as described in the link.
4. Rebooted
5. Updated OS to Server 2016
6. Installed WSUS as described in the link using SQL default Instance
7. Do NOT run the Post install command....yet.
8. Open Services and change W3SVC and WAS to automatic (default is DISABLED) and start
9. Run the post install SQL script to create the directories and DB
10. Open IIS verify Application Pool WsusPool and WSUS Administration Site is created.
11. Install Software Updates Roles within SCCM (MECM now) - Monitor SUSSetup.log
12. Perform Software Sync - Monitor with WCM.log and wsyncmgr.log

If in the WCB.log file you notice "Failed to set Subscriptions on the WSUS Server" then this helps https://www.prajwaldesai.com/failed-to-set-subscriptions-on-wsus-server-error-0x80131500/