Fixed – SCCM WSUS Sync Failed with UssInternalError SoapException Error 0x80131500 | ConfigMgr

Today Morning, the ConfigMgr community started reporting WSUS Sync failed with UssInternalError SoapException Error 0x80131500. Microsoft MVP Panu Saukko reports that the SUP server failed to sync after 04/08 01.00 am (his local time).

I tried to run WSUS Sync in my lab environment, and I couldn’t reproduce the sync issue. The issue is not there for all the SCCM/WSUS environments. I think the impact is there when you have enabled some of the Dev Tools product categories from the products list. More details in the below section of the post.

The following screenshot is taken from Panu’s tweet and gives you an idea about the WSUS sync error from Wsyncmgr.log.

Hot Issue SCCM WSUS Sync Failed with UssInternalError SoapException Error 0x80131500 | ConfigMgr
Hot Issue SCCM WSUS Sync Failed with UssInternalError SoapException Error 0x80131500 | ConfigMgr

Workaround

The workaround solution provided by Sr. Support Escalation Engineer Vinay Pamnani. You have to follow the steps mentioned below to workaround this issue.

  • Navigate to \Administration\Overview\Site Configuration\Sites
  • Select the Standalone Primary server -> Configure Site Components -> Software Update Point
Hot Issue SCCM WSUS Sync Failed with UssInternalError SoapException Error 0x80131500 | ConfigMgr
Hot Issue SCCM WSUS Sync Failed with UssInternalError SoapException Error 0x80131500 | ConfigMgr
  • Click on Products Tab
  • You need to uncheck Visual Studio 2017 and 2019 from the Developer category of products.
  • Click OK to save the setting.
Hot Issue SCCM WSUS Sync Failed with UssInternalError SoapException Error 0x80131500 | ConfigMgr
Hot Issue SCCM WSUS Sync Failed with UssInternalError SoapException Error 0x80131500 | ConfigMgr
  • Navigate to \Software Library\Overview\Software Updates\All Software Updates.
  • Initiate a manual WSUS sync to check whether the WSUS sync is goin to work or not.
Hot Issue SCCM WSUS Sync Failed with UssInternalError SoapException Error 0x80131500 | ConfigMgr
Hot Issue SCCM WSUS Sync Failed with UssInternalError SoapException Error 0x80131500 | ConfigMgr
  • Monitor the WSUSSyncMgr.log to confirm the sync status.
Fixed - SCCM WSUS Sync Failed with UssInternalError SoapException Error 0x80131500 | ConfigMgr 1

Fix Error 0x80131500

Microsoft is yet to come up with a fix for SCCM WSUS Sync failed with UssInternalError SoapException Error 0x80131500. I will keep you posted if I see more updates on this topic.

Update 09 April 2021 – The issue is fixed as per David James tweet.

We believe this should be resolved now for everyone, without any manual workaround. If you experienced an issue before and didn’t do the workaround, just trigger sync and verify it is working. Customers that didn’t notice the issue should silently recover on the next sync.

David James Tweet

Root Cause

David James shares another news that Beginning next week (patch Tuesday), you can patch VS through WSUS and ConfigMgr (only security updates via SCCM). The backend changes related to these Visual Studio updates caused major issues with WSUS Sync.

Fixed - SCCM WSUS Sync Failed with UssInternalError SoapException Error 0x80131500 | ConfigMgr 2

You can deploy Visual studio updates with SCCM now. Feature Pack and regular updates of Visual studio are available in SCCM using the manual import method.

Fixed - SCCM WSUS Sync Failed with UssInternalError SoapException Error 0x80131500 | ConfigMgr 3

FAQ?

Let’s have a quick look at the WSUS Sync issue reported today morning.

Microsoft Released Fix for WSUS Sync Issue?

NO, they are still working on the fix.

Root Cause of WSUS Sync Issue?

There is no public information released about this issue.

Did Microsoft provided Workaround this issue?

Yes, that is to uncheck Visual Studio 2016 and 2019 products.

Is this WSUS Sync issue impacting all environments?

No, it impacts only the environments where Dev tool updates are selected.

Resources

Sharing is caring!

7 thoughts on “Fixed – SCCM WSUS Sync Failed with UssInternalError SoapException Error 0x80131500 | ConfigMgr”

  1. I have seen issue on Windows 2019 but this is not a fix

    Asus pool getting stopped automatically.

    WSUS sync works but SUP failed

    Reply
  2. HI Anoop,

    After seeing you post, I have initiated the WSUS sync in my environment. I have received the below error. Looks like this error is not like which you mentioned in the post. But All Developer tools are checked in my environment under “Software Update point – Products”.
    Please suggest is the below error also related this post.

    Sync failures summary: SMS_WSUS_SYNC_MANAGER 4/9/2021 3:59:52 PM 41180 (0xA0DC)
    Failed to sync update b60bca3b-829a-400f-b57c-463b6ae1217f. Error: Failed to save update 950514e6-5457-4758-8e0d-ab9052be5f17. CCISource error: -1. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate SMS_WSUS_SYNC_MANAGER 4/9/2021 3:59:52 PM 41180 (0xA0DC)
    Sync failed: Failed to sync some of the updates. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates SMS_WSUS_SYNC_MANAGER 4/9/2021 3:59:53 PM 6568 (0x19A8)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE=”SMS Server” COMP=”SMS_WSUS_SYNC_MANAGER” SYS= SITE= PID=3596 TID=6568 GMTDATE=Fri Apr 09 13:59:53.373 2021 ISTR0=”Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates” ISTR1=”Failed to sync some of the updates” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 4/9/2021 3:59:53 PM 6568 (0x19A8)
    Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 4/9/2021 3:59:53 PM 6568 (0x19A8)

    Reply

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.