SCCM Software Update Point Sync Failed

Question

Hi,

We have SCCM or MECM Version 2010 and SUP installed and working correctly on main primary server, in addition we have SUP installed for a remote location which works fine. Now I am asked to install a new SUP on a 3rd remote location and the sync fails. This 3rd remote server has all the pre-req items installed similar like the second working remote SUP server. Those items are WSUS, and WSUS is using SQL. Both main server and 3rd remote server can talk on port 8530.

Any help is greatly appreciated.

On the SCCM console Software Update Synchronization Status I see error 0XFFFFFFFF

I see on the 3rd remote server WSUS sync failed error:

SoapException: Fault occurred
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetUpdateData(Cookie cookie, UpdateIdentity[] updateIds)
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetUpdateData(UpdateIdentity[] updateIds, List1 allMetadata, List1 allFileUrls, List1& updatesWithSecureFileData, Boolean isForConfig) at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.GetUpdateDataInChunksAndImport(List1 neededUpdates, List1 allMetadata, List1 allFileUrls, Boolean isConfigData)
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.GetAndSaveUpdateMetadata(List`1 updates)
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRe

Answer 1

@anaconda1442
Based on the feedback on the other posts, you are not the only one with the synchronization issue and Microsoft has fixed it now.

Occasionally, there would be issues on the MS side which cause the sync failure. Sometimes it is related to update production such as Office, and sometime it is related to update classification such as definition this time.

WSUS synchronization fails with SoapException (We may try the solution in the official document)

Hope my answer could help you and look forward to your feedback.

---

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.

Answer 2

@ SunnyNiu-MSFT

Thanks for your response, I saw that article when google searching however I was hesitant on trying it out.

The reason is because the instructions say "follow these steps on the topmost WSUS server that connects directly to Microsoft Update" which would be our main primary SCCM production server that has WSUS installed.

Another reason I did not want to try any fix on the main SCCM server is because it's working fine and I don't want to break anything.

I do have a SCCM Development environment in VMware that I can try this fix on and if it breaks WSUS I can revert back.

So I will add a new SUP/WSUS in development environment and see what happens.
I'll keep you posted.

Answer 3

Why are you installing a SUP at a remote location? Is this part of a secondary site within the hierarchy?

Answer 4

@SunnyNiu-MSFT

I finally got to work on the solution you mentioned from that Microsoft link

I ran the first portion of the PS command (shown below) on the topmost WSUS server that connects directly to Microsoft Update

It shows that I already have https://sws.update.microsoft.com set and it does not need to be changed.

Any other ideas?

PS C:\Windows\system32> $server = Get-WsusServer
PS C:\Windows\system32> $config = $server.GetConfiguration()
PS C:\Windows\system32> $config.MUUrl
https://sws.update.microsoft.com
PS C:\Windows\system32> $config.RedirectorChangeNumber
4002