Skip to main content

SharePoint 2010: Unable to start UPA sync service ,stuck at “Starting”

Unable to start User Profile sync service from Central administration site -system settings-Services on server. The service freezes at "starting" and never start. Below are the information from event viewer and verbose enabled ULS logs.

I found the below solution at Here


Resolution
- Stop User profile service and User profile sync service on ALL SharePoint servers in the farm

- Clear timer config cache by following the "resolution" documented athttp://support.microsoft.com/kb/939308

- Deleted the Pending timer job related to the UPA sync service provisioning using Central administration-Monitoring-check job status

- Confirmed that the security token service has only windows and anonymous enabled ( from IIS manager-SharePoint web services-Security token service-Authentication (under IIS))

- On the SharePoint server access the registry editor and confirm that the information related to FIM ( database servername , sync DB name etc ) are properly populated, if found wrong , back  up the registry key and edit the values to reflect the right information.

HKLM\system\currentcontrolset001\services\FIMservice

HKLM\system\currentcontrolset002\services\FIMservice

HKLM\system\currentcontrolset\services\FIMservice

- Delete all FIM related certificates from certificate store ( for account and system) . Make sure that no FIM related certificate is listed in any folders when looked at certificate manager.

- From Central administration-Application management-Manage service application, Make sure the User profile service application and its proxy are started, If found stopped, its always recommended to recreate them taking necessary backups (mysites)

- Start User profile service on the machine where you would like to start the User profile sync service (use central administration console)

- Once the service is started, try starting the User profile sync service from the central administration site


Comments

Popular posts from this blog

How to get SPUser or SPGroup from Person or Group field

You have person or group field in SharePoint list and you want to programmatically get the user or person. The below code to gets SPUser from User or Group field in the list when multiple choice and Groups are not allowed in the field: //get SPUser SPFieldUser userField = (SPFieldUser)item.Fields.GetField("Users"); SPFieldUserValue userFieldValue = (SPFieldUserValue)userField.GetFieldValue(item["Users"].ToString()); SPUser user = userFieldValue.User; This part of code would help you to get SPUser when multiple choice is allowed and groups are not allowed: //Multiple choices are allowed SPFieldUser userField = (SPFieldUser)item.Fields.GetField("Users"); SPFieldUserValueCollection userFieldValueCollection = (SPFieldUserValueCollection)userField.GetFieldValue(item["Users"].ToString()); foreach (SPFieldUserValue userFieldValue in userFieldValueCollection) {     Console.WriteLine("     " + userFieldValue.User.LoginName); } And when group...

SharePoint publishing page scheduling

In SharePoint 2010 publishing enabled team site collection is not showing schedule button in publish ribbon. Solution: Here is how to enable it  though the UI: Locate the SharePoint Server Web site on which you want to enable content approval and item scheduling. Click  Site Actions , click  Site Settings , and then click  Modify Pages Library Settings . Under  General Settings , click  Versioning Settings . Click  Yes  next to  Content Approval , and then click  OK . Click  Manage item scheduling .   Click to enable the  Enable scheduling of items in this list  check box, and then click  OK .

Changing Content Type Hub URL

Change the Hub URL through powershell by using: Set-SPMetadataServiceApplication -Identity " " -HubURI " " For Ex: Set-SPMetadataServiceApplication -Identity "Managed Metadata Service" -HubURI "http://contenttype.Domain.Com" When you try to do this you get this rather scary message: This is SharePoint telling you that this is a major thing so be careful! Essentially all your content types that you have published out will be removed if they can, and you have to republish all of your content types out again which can cause some issue.