User Profile Synchronization stuck on ‘Starting’
I have been exploring the User Profile Service Application configuration for a few hours and finally figured out why the User Profile Synchronization service hangs and remains in the “Starting” status as such –
- User Profile Service Application configured with the correct databases and application pools
- User Profile Service Application started fine.
- User Profile Service Synchronization Service stuck on “starting”
The reason why this happened to me specifically is because I started the “Managed Metadata Service” after Step1 was completed. User Profile Service application relies heavily on the Managed Metadata Service so even if it is started the User Profile Service Synchronization will get stuck. In addition, the Forefront services in the Services Panel will remain “Disabled” or won’t start as expected –
Solution:
To correct this issue:
1) I de-provisioned my User Profile Service application as such (NOTE: I am doing this in a pilot environment so make sure to back up your data because this will remove the existing “Sync DB, Social DB, and Profile DB” –
2) Configured and started the Managed Metadata Service
3) Reconfigured the User Profile Service by re-creating the databases, application pool.
4) Start the User Profile Service
5) Start the User Profile Synchronization Service.
6) Restart IIS – command prompt IISReset.
The results:
“Manage Services on Server” page in CA
Services Panel:
User Profile Configuration page:
And I now I have profiles –
IMPORTANT OBSERVATION:
If you are using Virtual Machines and your domain controller is running on a separate virtual instance then make sure the SharePoint 2010 virtual instance has not loss connectivity with the domain controller machine. The forefront identity services (especially the Forefront Identity Manager Services) relies on this. The way I check connectivity between SharePoint 2010 server and the DC is intact is by doing a “people picker” directory search. If results are returned then I know SharePoint is communicating with the DC.
This got me scratching my head for a bit but it’s finally working now!
This solution worked for me and your mileage may vary.
Thanks a Ton Alikan. It’s a great and lifesaving article. I’ve struggled for couple of days with this issue and now resolved as you suggested.
In another instance that I was installing, without Sharepoint 2010 Service Pack 1 and June Cumulative Updates, I was able to get around this by doing the DisableLoopbackCheck registry and restarting the server.