with an SPUpdatedConcurrencyException. Here’s the detailed update conflict error message:

Application Server job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (56e7982c-ffa5-47a2-8f8a-75491ea0f1d3).

Reason: An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by DOMAIN\SPSERVER$, in the OWSTIMER (1320) process, on machine SPSERVER.  View the tracing log for more information about the conflict.

Technical Support Details:
Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by DOMAIN\SPSERVER$, in the OWSTIMER (1320) process, on machine SPSERVER.  View the tracing log for more information about the conflict.
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

This error occurs every minute in the event log.

image

Another sympton is that you might not be able to access the content sources in the central administration. This URL looks like:

/_admin/search/listcontentsources.aspx?appid=">http://spserver:<PORT_OF_CENTRAL_ADMINISTRATION>/_admin/search/listcontentsources.aspx?appid=<GUID>

To resolve this error you must clear all server’s Program caches:

1. Delete all contents unter

%ALLUSERSPROFILE%\Microsoft\SharePoint\Config\<GUID>

2. Create a cache.ini file and set it’s content with “1”:

image

There might be an issue with service accounts, so be sure to have a proper understanding of using deployment administrative and service accounts and the post-installation steps for search.

About these ads