SUP Sync Error - 0x80131509

Andy-Nag_1 1 Reputation point
2021-01-13T00:41:46.51+00:00

As the title suggests i am getting the above error within SCCM console when i sync the updates.

No issues with WSUS sync as all the sync has been successful.

SCCM version 2002

WSYSNCMGR.log error - Sync failed: The operation has timed out. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse

Event Log error - 6703 - Same error as above.

not sure where and what to look for with regarding to network issue as that is what all forum as recommending.

SCCM server has been whitelisted so there is no block in place.

We have maintenance in place regarding Re-indexing which ran a week ago.

i have done clean up wizard as well in WSUS.

restarted IIS service

Any recommendation on what to check?

Microsoft Configuration Manager Updates
Microsoft Configuration Manager Updates
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Updates: Broadly released fixes addressing specific issue(s) or related bug(s). Updates may also include new or modified features (i.e. changing default behavior).
967 questions
0 comments No comments
{count} votes

5 answers

Sort by: Most helpful
  1. SunnyNiu-MSFT 1,696 Reputation points
    2021-01-13T09:53:27.307+00:00

    @Andy-Nag_1
    According to your question description, it is suggested that you may uncheck some items under Classification of the SUP Component Properties. Re-run the synchronization to see if the synchronization is successful. Then re-enable the same items as before and run the synchronization again to observe whether the synchronization is successful.


    If the response is helpful, please click "Accept Answer"and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. Andy-Nag_1 1 Reputation point
    2021-01-14T21:29:15.653+00:00

    tried youre recommendation and it did not work
    what else can i try

    0 comments No comments

  3. SunnyNiu-MSFT 1,696 Reputation points
    2021-01-15T06:04:51.387+00:00

    @Andy-Nag_1
    WSUS gets uncooperative after a certain amount of time without regular maintenance. The built-in WSUS maintenance task does very little to help clean-up the database in the context of ConfigMgr. The WSUS Cleanup Wizard is used in the WSUS console. This wizard will help, but many scripts created by others will work better. You may run the clean-up script(s) to expire superseded and other misc unecessary updates.
    Here is a reference script link: http://damgoodadmin.com/2018/04/17/software-update-maintenance-script-updated-all-the-wsusness/ (Third-party link, just for your reference.)
    After the maintenance is complete, you also need to re-index the WSUS database.


    If the response is helpful, please click "Accept Answer"and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  4. Andy-Nag_1 1 Reputation point
    2021-01-19T03:22:52.2+00:00

    Issue has been resolved.

    followed steps from below website

    https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/wsus-maintenance-guide


  5. SunnyNiu-MSFT 1,696 Reputation points
    2021-01-19T08:55:18.36+00:00

    @Andy-Nag_1
    We are glad that your issue has been resolved, and thank you very much for your updated solution. If you have any questions in the future, we warmly welcome you to post in this forum again.


    If the response is helpful, please click "Accept Answer"and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments