Monday, April 21, 2014

SharePoint 2013: The Execute method of job definition Microsoft.Office.Server.UserProfiles.LMTRepopulationJob (ID...) threw an exception.

Problem

You see the following events occur in the SharePoint 2013 server's application log:

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          [date/time]
Event ID:      6398
Task Category: Timer
Level:         Critical
Keywords:      
User:          [FarmServiceAccount]
Computer:      [A WFE server]
Description:
The Execute method of job definition 
Microsoft.Office.Server.UserProfiles.LMTRepopulationJob 
(ID ae7328f0-62dc-4bff-9eb1-df9e88f9b088) threw an exception. 
More information is included below.
System.TimeoutException

and
 
Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Portal Server
Date:          [date/time]
Event ID:      5555
Task Category: User Profiles
Level:         Critical
Keywords:      
User:          [FarmServiceAccount]
Computer:      [WFE servername]
Description:
Failure trying to synch web application 76d8e4ce-9f2a-4e3d-a43e-4a945eb4755a, 
ContentDB 5c305513-be21-4a26-b797-c8c5eb8d4495  Exception message was 
Microsoft.Office.Server.UserProfiles.UserProfileApplicationNotAvailableException: 
UserProfileApplicationNotAvailableException_Logging :: 
UserProfileApplicationProxy.ApplicationProperties ProfilePropertyCache does not 
have 011651c9-c8ce-4520-9eab-d4bcad5534fe 
   at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_ApplicationProperties()
   at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_PerfmonInstanceHandle()
   at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer..ctor(ELogType logType, 
      SPContentDatabase cdb, SPJobState jobState, SyncType syncType, 
      WSSSyncUsageEntry usage, String[] excludedAccountsRegexStrings)
   at Microsoft.Office.Server.UserProfiles.WSSProfileSyncJob.Execute()


Solution
  • Launch the Services.msc and ensure that the SharePoint Timer Service is started and that its Startup Type is Automatic.
 References

No comments: