WSUS (S2016) Initial Sync Crashes

Question

I'm setting up a brand-new server as a WSUS replica (Windows Server 2016). On the initial WSUS Server Configuration Wizard run when you first launch WSUS, when I try to do the initial sync with Start Connecting, after a few seconds it crashes with the message "An unexpected error occurred, and this wizard must be closed. You may restart the WSUS Server Configuration Wizard from the Options page in the WSUS console."

Running the wizard again gives the same error.

In the Application log, it gives the following message:

-----------

The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,

Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC.

System.FormatException -- The specified text did not contain a token for the specified linkIndex.

Source
Microsoft.UpdateServices.UI.SnapIn

Stack Trace:
at Microsoft.UpdateServices.UI.SnapIn.Controls.CustomControls.FormatLinkText(String text, Int32 linkIndex, LinkArea& linkArea, Object[] formatters)
at Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE.BaseOOBEContentPane.ShowError(ExtendedTableLayoutPanel notificationArea, String errorText, String linkText, LinkLabelLinkClickedEventHandler linkClickedEventHandler)
at Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE.ConnectToUSSContentPane.OnSyncCompleted(Object sender, GetSyncStatusCompletedEventArgs e)

-------------

I tried removing the wsus file as suggested, but it didn't help. I've tried removing the WSUS services and wiping the remaining files, and starting over, but the same thing is still occurring.

I also found this in the SoftwareDistribution.log file, not sure if it's related or not:

----------------

2022-10-07 16:58:10.628 UTC Error WsusService.47 CatalogSyncAgentCore.ExecuteSyncProtocol One or more updates failed to import to local database. - Microsoft.UpdateServices.ServerSync.CatalogSyncException: Exception of type 'Microsoft.UpdateServices.ServerSync.CatalogSyncException' was thrown.
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS()
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.CatalogSyncThreadProcess()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

----------------

Any help would be greatly appreciated.

Answer 1

Hi, @Nathaniel Miller

Thanks very much for your feedback. Anyway, we're glad that the problem is solved now. Here's a short summary for the problem, we believe this will help other users to search for useful information more quickly.

Problem/Symptom:
When setting up a brand-new server as a WSUS replica, on the initial WSUS Server Configuration Wizard run when first launch WSUS, when click "Start Connecting", it crashes with the message "An unexpected error occurred, and this wizard must be closed. You may restart the WSUS Server Configuration Wizard from the Options page in the WSUS console."

Solution/Workaround:
Point the new WSUS to look another "parallel" server as its upstream source, it's able to connect, then click back without finish the wizard, then change the upstream source to the previous one, and then it was able to connect and complete the Wizard without any problem.

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Answer 2

Hi, @Nathaniel Miller

Thank you for posting in Microsoft Q&A forum.

You may try to change the private memory limit to "0" which means no limit to see if it helps, remember to back under Application pools, right-click on the WsusPool again and choose 'Recycle...'.
https://www.404techsupport.com/2016/03/21/iis-wsus-private-memory/
(Please Note: Since the website is not hosted by Microsoft, just for your reference.)

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
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 3

I fixed the problem, but have no idea why it worked.

The server in question is a replica, one of several that are used to bridge separate networks. I pointed WSUS to look to another "parallel" server as its upstream source; that was able to connect without any crashes. Then, clicking Back without completing the Wizard, I changed it back to the proper upstream server, and it was able to connect and complete the Wizard without any problem.