Thursday, June 4, 2026
type here...
CM InfrastructureWSUS

Primary site Sync is keep getting failed with error Failed to publish sms client to WSUS error 0x80131509

By Haresh Hirani
0
1414

Issue : 

Primary site Sync is keep getting failed with error: Failed to publish sms client to WSUS, error = 0x80131509

This issue started once Current Branch 1710 Upgraded for infrastructure in this time one for the downstream server is keep starting failed with error 0x80131509

While validate to the Primary site server <Downstream Steam server > WCM.Log: Found that PublishApplication is getting Version Match error.

PublishApplication(A9356B04-DA80-48C3-97DE-C9C528F73A2D) failed with error System.InvalidOperationException: Publishing operation failed because the console and remote server versions~~do not match.~~   at Microsoft.UpdateServices.Internal.BaseApi.Publisher.LoadPackageMetadata(String sdpFile)~~   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetPublisher(String sdpFile)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.PublishApplication(String sPackageId, String sSDPFile, String sCabFile)

 By seeing above error, I have found that its not PublisherApplication (ccmsetup-sup.cab) is not getting match with CAS Servers.

Action taken for solutions.

Step 1:  Login to the Issue reported  primary site server  <Downstream Steam server > Issue reported server.

Step 2:  Validated event viewers, Found error is matching with WCM.LOGS

Step 3: By seeing above error taken backup of the ccmsetup-sup.cab file from the issue reported server from the below path and removed file ccmsetup-sup.cab from below path.

Ex:  I:\Program Files\Microsoft Configuration Manager\bin\i386

      I:\Program Files\Microsoft Configuration Manager\bin\X64

Step 4: Connect CAS Servers à Copy ccmsetup-sup.cab from the Latest BITS and replace on issue reported server.

Below is path bits are available:-

I:\Program Files\Microsoft Configuration Manager\EasySetupPayload:

                            OR

\\Site Server Share\EasySetupPayload:

Step 5: After replace above file issue got fixed.  And component and sync got success.  Status message started with OK:Component status change error to okay

WCM.LOG

Happy learnings!!!

Thanks&regards,
Haresh Hirani
Email: [email protected], [email protected]
Facebook https://www.facebook.com/Hiraniconfigmgr-120189361980772/
Follow us: https://www.linkedin.com/in/hiraniconfigmgr 
Twitter: https://twitter.com/hiraniconfigmgr

Author

  • Hi, I’m Haresh Hirani the mind behind Hiraniconfigmgr.com. I’m a seasoned IT professional with deep expertise in Microsoft technologies, especially in Configuration Manager (ConfigMgr/SCCM). Over the years, I’ve expanded my skill set to cover a broader range of modern device management platforms like Microsoft Intune, Jamf Pro, ManageEngine Endpoint Central, and VMware AirWatch (Workspace ONE UEM), I use this blog to document real-world, tested, working fixes and walkthroughs from my daily technical experiences. The 💡idea is simple: if it helped me, it might help someone like you. My goal is to create a living repository of practical IT solutions for the community. If you find something useful, or if you want to collaborate, feel free to connect with me on LinkedIn or drop a message through the Contact page. Happy to help.

Previous article
Remote Management point in azure failed for port 80 with status code 500
Next article
SCCM replication link is failed between primary server and secondary sites

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Search

Latest posts

I’m the person behind this webpage. Thank you for visiting the website and about me page! My website is all about Microsoft technologies. More about ConfigMgr and all other technologies which are interesting for me. However, larger percentage of my posts are related to SCCM. Normally, like to post the interesting issues which I came across in my day to day tech life. you will find only solutions which comes on my day to day life.

Hot Category

Popular Post

© COPYRIGHT Hiraniconfigmgr.com

Developed By : Deepcoder