Below is a list of requirements and common points of failure for the user profile synchronization service.
If you have an issue with the sync service failing to start, stuck starting or stopping, verify the items below in the Your environment.
=> Verify that the Sync account is a member of the local administrators group.
=> Verify the account is a member of the farm administrators group.
=> Verify that a profile service application has been created prior to starting the sync service.
=> Verify that the application pool for the UPA is leveraging the farm account.
Look for SQL alias issues using CLICONFG – should be fixed with the CU1 update.
Verify proper permissions in SQL for Sync account – As this is leveraging the farm account, it should have DBCreator and SecurityAdmin.
Look at the registry keys for the FIM components: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\FIMService] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\FIMSynchronizationService]
Monitor ULSViewer during the sync service configuration with a filter of Category contains Profile applied.
Check Application and System logs for errors during configuration
Consider rebuilding the FIM registry keys – See FIMService file in the resources section of this document.
Consider rebuilding the User Profile Application to obtain a new sync database.
In this process you need to back up the profile and social databases, then specify those names where appropriate in the new UPA creation
While entering a new name to create a new sync db. This will recreate the UPA while preserving the social and profile data
Consider using Process Monitor to look for Access Denied issues
Verify if the domain was upgraded from Windows 2000.
If so add the sync account to the “Pre-Windows 2000 Compatible Access” and “Windows Authorization Access” groups. If in doubt add the account being used by the sync service to those groups in AD as appropriate.
If service is stuck in starting or stopping, consider setting the FIM services back to their default values of Disabled and Local System, and rebooting the server.
