{"id":74,"date":"2015-02-03T15:21:29","date_gmt":"2015-02-03T15:21:29","guid":{"rendered":"http:\/\/www.ccrossan.com\/?p=74"},"modified":"2015-03-02T11:37:50","modified_gmt":"2015-03-02T16:37:50","slug":"forefront-identity-manager-2010-r2-synchronization-service-becomes-disabled","status":"publish","type":"post","link":"https:\/\/crossan007.dev\/blog\/identity-management\/forefront-identity-manager-2010-r2-synchronization-service-becomes-disabled\/","title":{"rendered":"ForeFront Identity Manager (2010 R2) Synchronization Service Becomes Disabled"},"content":{"rendered":"\n
Tweet<\/a><\/div>\n

I had just installed FIM 2010 R2 in a lab environment – All roles on one server, and noticed that the “Forefront Identity Manager Synchronization Service” \u00a0Kept stopping, and being set to “Disabled.”<\/p>\n

I had installed all of the latest patches for both FIM (4.1.3613.0<\/a>) and SharePoint (14.0.7140.5000<\/a>). I saw nothing in the Windows Event log to indicate there was a problem. \u00a0The “Synchronization Service Manager on FIM” application would launch fine while the service was running. \u00a0All configured management agents would synchronize no problem. \u00a0It’s just that – Every so often, the\u00a0 “Forefront Identity Manager Synchronization Service” would just up and STOP!<\/p>\n

After some research, I found this TechNet Blog Post<\/a>\u00a0which suggests that SharePoint is the culprit!<\/p>\n

Since SharePoint is installed on this server only for the purpose of providing the FIM Portal, I had no need to set up (or otherwise use) the User Profile Service. \u00a0 Consequently, SharePoint isn’t expecting the Synchronization Service to be in a running state! So, as part of the “Health Analysis Job (Hourly, Microsoft SharePoint Foundation Timer, All Servers)” SharePoint notices the service is running, and disables it!<\/p>\n

I verified this by returning the service to the normal Automatic – Running state, and manually kicking off that Timer Job.<\/p>\n

Sure enough, the job was stopped! ULS Viewer shows me this also:<\/p>\n

\"\"<\/a><\/p>\n

See that? – “The SharePoint Health Analyzer found and fixed the following problem: One or more services have started or stopped unexpectedly..” \u00a0No details about\u00a0which<\/em> service was “started unexpectedly,” but I presume that the\u00a0“Forefront Identity Manager Synchronization Service” was the culprit.<\/p>\n

To prevent this from happening again, I\u00a0nagivated to “Review Job Definitions” under “Monitoring” in Central Administration, located the \u00a0“Health Analysis Job (Hourly, Microsoft SharePoint Foundation Timer, All Servers)” and disabled it.<\/p>\n

All seems well at this point in time…<\/p>\n

My set of links for FIM installation tips, tricks, procedures, etc:<\/p>\n