Sync failed: Sync already running: wsyncact

Dinesh Vinay 81 Reputation points
2020-10-03T05:27:05.527+00:00

Hi Folks,

Hope everyone is doing good.

We can able to see that errors are frequently updating in wsyncmgr.log while primary site server trying to sync to one of the downstream SUP server. The error message was strange. Its saying that “Sync failed: Sync already running: wsyncact”.

29966-screenshot6.jpg

Below troubleshooting method to check for the fix . But no luck.

Restart the WSUS service and reboot the site system
Uninstall and re-install the SUP role for SZ site system
Remove the WSUS administration site and WSUS app pool and try to reconfigure the by running WSUSutil post install cmdline

Also, confirmed that there are no errors in WSUSctrl.log and WSUS is working correctly in Eventvwr for that downstream SCCM server.

However after performing the full schedule sync. We can able to see that SUP synchronization status is completed and exited with return code 0. But its not updating the WSUS catalog version in SCCM console.

29958-screenshot8.jpg

Also verified that there are no errors in WCM.log in primary site server.

Did anyone has any idea about the sync issue. Due to this client are not receiving WSUS location path in LocationServices.log. and we are not able o deploy patching an SCEP to SZ servers.

Much appreciate for your help. Thanks.

Regards,
Dinesh Vinay

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).
922 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. AllenLiu-MSFT 38,006 Reputation points Microsoft Vendor
    2020-10-05T05:58:16.467+00:00

    @Dinesh Vinay
    Thank you for posting in Microsoft Q&A forum.

    The error message was strange. Its saying that “Sync failed: Sync already running: wsyncact”.

    The information indicates that the sync is running. What is the sync schedule setting of this downstream SUP?
    If it's too frequent, it may cause this issue.


    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. Dinesh Vinay 81 Reputation points
    2020-10-07T09:45:11.78+00:00

    Allen, Much thanks for your reply.

    Sync schedule is not too frequent. Our CAS server sync with Microsoft update in every 6 hours. All the downstream servers are able to update the WSUS catalog version expect the problematic one

    Finally we completely wipe the SUP role and WSUS on that downstream server and reinstall the WSUS role and SUP role again. But still no luck. Also verified there is no error in SMS_WSUS_Control_Manager component

    We are getting the same error. We can able to justify that there is no problem in downstream server. Believe the problem is occurring on primary site server. We unable to find root cause why we are getting this below error when primary site server trying to sync with downstream server on every 60 min sync schedule.

    Its saying that “Sync failed: Sync already running: wsyncact

    Other than that, There is no sync failure in Software update point synchronization status in Monitoring node. Only things are WSUS catalog version and Catalog last updated is not updated in console. But we can able to see the WSUS catalog version is updating on SCCM DB by running the below query.

    30682-screenshot9.jpg

    Still we are working on this. But we can predict that problem in primary site server. But we don't know where to check exact root cause for this problem. Apart from reconfiguring WSUS in downstream SUP server. Would you suggest anything to check on primary site server

    0 comments No comments