SharePoint 2013: The Execute method of job definition Microsoft.Office.Server.UserProfiles.UserProfileImportJob... threw an exception.

Problem

You see the following error occur in a farm application server 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:      [FarmAppServer]
Description:
The Execute method of job definition 
Microsoft.Office.Server.UserProfiles.UserProfileImportJob 
(ID a170d607-3f04-4bdd-8d50-4a28c530399d) threw an exception. 
More information is included below.

There was no endpoint listening at 
http://[FarmAppServer]: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:
...

This error occurs at one minute intervals and started happening after you rebooted the server (although you didn't catch it right then).  The regularity indicates that this error likely arises from a failed SharePoint scheduled farm job, and this is further corroborated by noting this portion of the error message: Microsoft.Office.Server.UserProfiles.UserProfileImportJob.

Solution

1. Open the Services control panel.
2. Look for these two services:
• Forefront Identity Manager Service
• Forefront Identity Manager Synchronization Service
3. Verify that both are started. If they are not, start them right here.

Notes

• From experience I have observed that some services do not restart on boot and that they must be started manually.  The Forefront Identity Manager Service is one such.  Others include AppFabric, SharePoint Search Host Controller, SharePoint Timer Service and other.
• The error message here is another example where the hints presented in the error do not adequately point to the underlying cause and can even lead to pursuing unproductive troubleshooting pathways.  The salient clue that I spotted and acted upon was this portion: Microsoft.Office.Server.UserProfiles.UserProfileImportJob.