SharePoint 2013: Critical 6398: The Execute method of job definition Microsoft.Office.Server.UserProfiles.UserProfileImportJob...

Problem

The following event is occuring every minute in the application event log on one of your farm's application servers:

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          [date/time]
Event ID:      6398
Task Category: Timer
Level:         Critical
Keywords:      
User:          [FarmServiceAccount]
Computer:      [ApplicationServer]
Description:
The Execute method of job definition Microsoft.Office.Server.UserProfiles.
UserProfileImportJob (ID deabe75d-3701-43c1-9968-920febb91024) threw an 
exception. More information is included below.

There was no endpoint listening at 
http://[ApplicationServer]:5725/ResourceManagementService/MEX that could 
accept the message. This is often caused by an incorrect address or SOAP 
action. See InnerException, if present, for more details.
Event Xml:
...

 
Checking the Services control panel on the farm application server, I found that the FIM service had stopped.

Solution

• Start or restart the FIM and/or FIM Synchronization services (whichever is stopped).

References

• Error while creating UPSA Synchronization connection in SharePoint 2013
• There was no endpoint listening at... ResourceManagementService/MEX that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details

Notes

• I checked failed jobs in Central Administration Job History listing during the period that this event was occurring (the error event filled the server's Application log), but was unable to find any failed job that occurred at the same times.  The only user profile jobs having one minute scheduling were
  • User Profile Service - System Job to Manage User Profile Synchronization
  • User Profile Service - User Profile to SharePoint Language And Region Synchronization. 
  However, both these jobs showed Succeed for each occurence in the Job History.  If anyone can provide some helpful insight on this puzzling discovery, I would be grateful.  Was it one of these jobs that was generating the error?  Or does this particular task not generate a failed job entry if it fails?