“Persisted Navigation Term Set Synchronization” Job Failures

Applies to SharePoint 2016; not tested on other versions of SharePoint.  

Symptoms

 

https://caUrl/_admin/TimerJobHistory.aspx?View=5 shows continuous failures of the “Persisted Navigation Term Set Synchronization” job, which begins shortly after 06:00.













 



























Error Messages

 

There was no endpoint listening at http://<servername02>:32843/d93d2dec585f4ebfbf47591fc1d8dd3d/MetadataWebService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.. (Correlation=9e6b2ba1-d1f4-1019-9297-1728042606ca)

 

There was no endpoint listening at http://<servername01>:32843/d93d2dec585f4ebfbf47591fc1d8dd3d/MetadataWebService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.. (Correlation=9e6b2ba1-71af-1019-9297-1d5b64a5c2e0)

The “endpoint listening” URL is going back and forth between http://<servername01>:* and <servername02>* in the error messages.

 

Cause

 

Failure of the Timer Service Recycle job on the <servername01> and <servername02> servers at 06:00. Why the job fails to recycle is undetermined.


Resolution

 

Restart the SharePoint Timer Service (SPTimerV4) on <servername01> and <servername02>. To verify, either wait for the next scheduled run (runs every hour) or wait for a few minutes and manually trigger it by hitting “Run Now” on the “Edit Timer Job” page. If the latter option is chosen, you may have to run it a couple of times to get an accurate result.


Popular posts from this blog

October 2025 SharePoint CU Failed to Install After Applying September 2025 SharePoint CU

September 2025 SharePoint 2016 CU - Configuration Wizard failed

Broken Site Collection