Wednesday, April 20, 2016

User profile service stuck in stopping/starting SharePoint 2010

follow below steps to fix stuck service,

1. run this on powershell command or command prompt,
 stsadm -o enumservices > c:services.txt

you will get all services in file and check user profile service tag in it as  following,


<Service>
    <Type>Microsoft.Office.Server.Administration.UserProfileService, Microsoft.Office.Server.UserProfiles, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c</Type>
    <Name />
    <DisplayName>User Profile Service</DisplayName>
    <Status>Unprovisioning</Status>
  </Service>

2. run using powershell command for user profile service,

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

- you will get "operation completed successfully" message.

- Restart IIS server.

- You can do same thing for USER profile synchronization service to stop it if it stuck in starting/stopping.

- run following for USER PROFILE Synchronization service,
- you can find tag in file,

<Service>
    <Type>Microsoft.Office.Server.Administration.ProfileSynchronizationService, Microsoft.Office.Server.UserProfiles, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c</Type>
    <Name>FIMSynchronizationService</Name>
    <DisplayName>User Profile Synchronization Service</DisplayName>
    <Status>Disabled</Status>
  </Service>

- run using powershell command,

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

- you will get completed successfully message.
- Restart IIS.


1 comment:

  1. Just confirming that good old 'stsadm' still has a place. I tried many powershell commands but the above 'stsadm' and an IISreset was only thing to actually stop both services.

    ReplyDelete