User profile synchronization service shows starting for long time
User profile synchronization service shows starting for long time
http://4.bp.blogspot.com/-sjXc2YPbBvY/Uyfo-NEKD6I/AAAAAAAABc4/_ptUU9mZw34/s1600/1.bmp
There could be many reasons for the service is in struck and shows starting only. .Why does it get stuck? Well, 15 provisioning runs will be attempted before it gives up. When we hit Start in Services in Server a series of tasks are run, which are to running the second stage of the Forefront Identity Manager setup. Those include things like setting up certificates, windows services, installing database schemas so on. If something is incorrect, it will try all tasks again, and more often than not, fail the service to start. That’s why it appears to be “stuck” when in fact its attempting each of the runs. Of course this can take a while, hence the appearance of being “stuck”. After around 20 to 45 minutes the status will return to Stopped, and you can attempt to start it again.
In some cases, the status will remain as “Starting” even after reboots. In this case something very bad has happened and you are best off throwing away the UPA service application and starting over.
You can however, manually start things back to the state before the starting of the UPS service instance. This can be necessary in some cases, but again, I strongly recommend you start clean by deleting and recreating the UPA. Before Re-creating the Service application ensure that all the below steps tried.
· Ensure to restart the user profile service and synchronization service
· Ensure to restart the FIM services
· Ensure to do IISReset after the services starts
· Ensure to reboot the server
· Ensure to have the available space on DB server and SP server.
If all done but still issues not resolved, then try to Delete the Existing UPA service Application and create the new one and check the status.
Note: I resolved the issue by above Method. If you find a different solution, please report it as a comment to this post. This will be useful to SharePoint Community. Be sure to double-verify it: undo your solution and verify that the problem comes back, then redo it and verify that the problem goes away.