How to resolve User Profile Synchronization Service is Stuck at Starting

Let’s assume you are at the stage where the User profile Sync service is stuck on starting mode. First you need to stop the User Profile Sync service using the below power shell command.

1. Open SharePoint 2010 Power shell and run the below command
2. Get-SPServiceInstance (Returns the services instance for a specific server or the entire farm)
3. Copy the ID for the User Profile Synchronization service.
4. Stop-SPServiceInstance –id

Where <id> is the GUID of the User Profile Synchronization service

5. Come back to the Central Administration Page – Manage Services on Server and you will notice that the User Profile Synchronization service should be stopped now.
6. Stop SharePoint timer and SharePoint admin service from services.msc
7. Clear the SharePoint Config cache by following the article http://blogs.msdn.com/b/josrod/archive/2007/12/12/clear-the-sharepoint-configuration-cache-for-timer-job-and-psconfig-errors.aspx
8. Run the below command

stsadm -o execadmsvcjobs

9. Start the SharePoint timer and SharePoint Admin service from services.msc
10. IIsreset
11. On the SharePoint Server Click on Start — Run — MMC — file — add/ remove snap in — select certificate. You will Find My user account | Service Account | Computer Account.
12. Except service account added the other two accounts
13. Clicked Ok.
14. Delete all the certificated related to ForefrontIdentityManager from all the folders you see in the console.

(Note: DO NOT DELETE ANY OTHER CERTIFICATES EXCEPT THE ForefrontIdentityManager)

15. Open regedit — Hkey Local Machine — System — Current Control Set — Service — FimService and verify the database name to point to the correct sync database name that is used with the User Profile Service Application.

NOTE: You need to check the same registry key under Control Set002 and Current Control Set001. If the sync database name is incorrect, then manually correct it use the database name which is being used by the User Profile Service Application.

16. Do an IISreset.
17. Go to Central Administration – Manage Services on Server and try starting the User Profile Synchronization service and it should start.

If still the issue persist try:

 Additional Steps 2:

Reprovisioning UPA service using below command:

stsadm -o provisionservice -action start -servicetype “Microsoft.Office.Server.Administration.ProfileSynchronizationService, Microsoft.Office.Server.UserProfiles, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” -servicename “FIMSynchronizationService”

stsadm -o provisionservice -action stop -servicetype “Microsoft.Office.Server.Administration.ProfileSynchronizationService, Microsoft.Office.Server.UserProfiles, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” -servicename “FIMSynchronizationService”

 

 Additional Steps 3:

ULS Error:

OWSTIMER.EXE (0x1F10) 0x07CC SharePoint Portal Server User Profiles g11n High UserProfileApplicationProxy.InitializePropertyCache: System.Security.Cryptography.CryptographicException: Object already exists.       at Microsoft.Office.Server.UserProfiles.MossClientBase`1.ExecuteOnChannel(String operationName, CodeBlock codeBlock)     at Microsoft.Office.Server.UserProfiles.ProfilePropertyServiceClient.ExecuteOnChannel(String operationName, CodeBlock codeBlock)     at Microsoft.Office.Server.UserProfiles.ProfilePropertyServiceClient.GetProfileProperties()     at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.RefreshProperties(Guid applicationID)     at Microsoft.Office.Server.Utilities.SPAsyncCache`2.GetValueNow(K key)     at Microsoft.Office.Server.Utilities.SPAsyncCache`2.GetValue(K key, Boolean asynchronous)     at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.InitializePropertyCache() bf17b890-20c2-4e56-9e35-86c9e7adf902

Resolution:

-> Goto :-

“C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys”

-> Give full permission to SharePoint groups “WSS_WPG” & WSS_ADMIN_WPG” on folder MachineKeys.

-> Start UPA sync