Forefront Identity Manager Service does not start

I have (or had) a functioning FIM environment until yesterday when the FIM Service stopped.  The service will not start automatically and when I try to start it manually I get the error 

"The ForeFront Identity Manager Service service on Local Computer started and then stopped..."

The following entries appear in the error log when I try to restart the FIM Service

  • "Workload Monitor failed to start. Workload Manager functionality will be turned off. As a result, you may notice decreased performance in the FIM portal or in policy application scenarios. The detailed error information is in the following error report. If you correct the underlying error and restart the service, Workload Manager functionality will be turned on."
  • "mscorlib: System.OverflowException: Arithmetic operation resulted in an overflow."
  • "System.ServiceModel: System.InvalidOperationException: Cannot find the X.509 certificate using the following search criteria: StoreName 'My',..."

There are other recent FIM related errors in the Log that are not directly related to restarting the FIM Service but I suspect are associated with the issue. 

  • "mscorlib: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at http://localhost:5725/ResourceManagementService/MEX that could accept the message. This is often caused by an incorrect address or SOAP action...."
  • "The Forefront Identity Manager Service could not bind to its endpoints.  This failure prevents clients from communicating with the Web services.

    A most likely cause for the failure is another service, possibly another instance of Forefront Identity Manager Service, has already bound to the endpoint.  Another, less likely cause, is that the account under which the service runs does not have permission to bind to endpoints.

    Ensure that no other processes have bound to that endpoint and that the service account has permission to bind endpoints.  Further, check the application configuration file to ensure the Forefront Identity Manager Service is binding to the correct endpoints."

Nothing has changed in the FIM environment except for a reboot of the SQL Server where the FIM dbs Live.  Also, we recently updated the cert that is bound to the FIM portal.  However, that happened a month ago and the portal was working fine up until yesterday.  As far as I know no other change has taken place on the server so I am at a bit of a loss to explain what has happened.  Any suggestions would be appreciated

As an aside, I have seen several posts where people have reported some of the error messages I listed above.  But in all cases, it appears the the issue was associated with SharePoint UPS, which we are not using.

Thanks

  • Edited by ocannada Tuesday, February 25, 2014 9:10 PM
February 26th, 2014 12:09am

So the solution was to revert to the old (expired) cert.  The portal now works, which is great.  I now have a less pressing issue of binding the valid cert to the FIM portal.  
  • Marked as answer by ocannada Tuesday, February 25, 2014 11:51 PM
Free Windows Admin Tool Kit Click here and download it now
February 26th, 2014 2:51am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics