Skip to main content

Application Server Administration job failed

Problem
CPU 99%.
User Profile Synchronization is stuck on Running.
SharePoint Timer Service is eating up the whole CPU and the event viewer says:

Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance

 Reason: An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by xxxxxxxx, in the OWSTIMER process, on machine xxxxxxx.  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 xxxxxxxx, in the OWSTIMER process, on machine xxxxxxx. 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 issue occurs if the contents of the file system cache on the front end servers are newer than the contents of the configuration database.

Fix the problem
Manually clear the file system cache on the local servers (fe's) on which the timer service is running (KB)

  • Stop the SharePoint Timer Service in Administrative Tool/Services.
  • Go to the cache folder. For Windows Server 2008: Drive:\ProgramData\Microsoft\SharePoint\Config
  • Find the folder that contains the file Cache.ini
  • Delete all the XML configuration files in the folder so that you can verify that the folder is replaced by new XML files when the cache is rebuilt. 
  • Open the Cache.ini file, delete all content in the file and type 1, save and exit. 
  • Start the SharePoint Timer service 

The file system cache should now have been recreated. Make sure that you perform this procedure on all servers in the server farm.
Make sure that the Cache.ini file in the folder now contains the previous value. For example, make sure that the value of the Cache.ini file is not 1.

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

Error when running Register-SPAppPrincipal

Problem You get the error, "Cannot find an SPWeb object with Id or Url" , when trying to get the RootWeb of the SPSite object when you register a new app with the Register-SPAppPrincipal PowerShell cmdl. Register-SPAppPrincipal -NameIdentifier $appPrincipalIdentifier -Site $site.RootWeb -DisplayName 'ProviderHostedApp' The cause could be The user who is running the script is NOT a farm administrator. Fix the problem Add the user to the farm administrator group
Post a Comment
Read more

Enable PowerShell commandlets for SharePoint 2013 in PowerShell ISE

Open the PowerShell ISE and create a profile by running the following code: if (!(test-path $profile.AllUsersAllHosts)) { new-item -type file -path $profile.AllUsersAllHosts-force } Open the newly created profile with the following command: psEdit $profile.AllUsersAllHosts The profile will be open in the PowerShell ISE. Add the following code to the profile: (If the profile for some reason doesn't open then you can get it here: C:\Windows\System32\WindowsPowerShell\v1.0\profile.ps1) if ((Get-PSSnapIn -Name Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue) -eq $null ) { Add-PSSnapIn -Name Microsoft.SharePoint.PowerShell } Save the profile. Next time you open the PowerShell ISE you will have all the Microsoft.SharePoint.PowerShell commandlets.
1 comment
Read more

Can't read from source file or disk

When you are using Windows Explorer View in SharePoint you can't MOVE a file from one site to another if it's not directly below the root site, but you can copy the file. See the different scenarios below. Working Scenario Moving files between libraries within the same site. For example: "http://sharepointsite/sites/site1/site2/library1" (source) "http://sharepointsite/sites/site1/site2/library2" (destination) Moving files between libraries across different sites as long as they are directly below the root site. For example: "http://sharepointsite/site1/library1 (source) "http://sharepointsite/site2/library2 (destination) Non-working Scenario Moving files between libraries in sub-sites that are more than 1 level below the root site. For example: "http://sharepointsite/sites/site1/site1/library1" (source) "http://sharepointsite/sites/site1/site2/library2" (destination)
3 comments
Read more