SharePoint 2010 SharePoint Administration Service not starting
-
Tuesday, June 12, 2012 9:29 PM
I am trying to configure a SharePoint 2010 server but is giving configuration failed message, as it could not get SharePoint Administration Services(SPAdminV4) to start. It is failing to start inspite of every effort.
Any solutions? If it fails to start will uninstalling and reinstalling SharePoint help?
All Replies
-
Tuesday, June 12, 2012 9:53 PMModeratorCheck the System Event Log when it fails to start. My best off hand guess is that you have a bad password for the user account running that service.
http://sharepoint.nauplius.net
-
Tuesday, June 12, 2012 10:00 PM
Description:
The SharePoint 2010 Administration service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Error: 1053Any suggestions how to start it?
- Edited by geeam Tuesday, June 12, 2012 10:40 PM
-
Wednesday, June 13, 2012 6:35 AM
Has the password for that account changed ? If yes, then update the new credentials in the Service Logon details.
Talib Ali Khan
SharePoint Specialist
MCTS
Blog : http://www.onlineasp.net
Twitter : https://twitter.com/TalibAliKhan
LinkedIn: http://sa.linkedin.com/in/talibalikhan -
Wednesday, June 13, 2012 7:21 AM
The password has not changed. The server has SharePoint 2010 and project server 2010 installed. Will uninstalling and reinstalling them help? Also if SharePoint is to be unistalled and reinstalled, is it necessary to uninstall and restall project server?
-
Monday, June 18, 2012 4:08 PM
Hi There,
we are having the same issue with our SharePoint 2010 Server. We have SP1 with CU Feb 2012 installed.
For us the KB2677070 Update was the problem. After we removed it our SPAdminV4 Service was running again.
Does some have the same Error?
Greetings, Thomas
-
Monday, June 18, 2012 5:04 PM
Hi,
I can confirm that KB 2677070 (http://support.microsoft.com/kb/2677070) will break your Sharepoint 2010 farm *if* your Sharepoint servers do not have internet connectivity and are not able to retrieve the updated certificate trust lists.
We have seen this happen over the weekend on a number of Sharepoint farms where both the Claims To Windows Token service and the Sharepoint Administration service were unable to start unless we either removed this update or allowed the machines to connect out to the internet.
Regards,
Paul Lynch
http://www.iisadmin.co.uk
- Proposed As Answer by Thomas Staender Tuesday, June 19, 2012 6:45 AM
- Marked As Answer by Rock Wang– MSFT Thursday, June 21, 2012 7:36 AM
-
Thursday, June 21, 2012 7:49 PMThis hit on one of our servers in the Sharepoint farm, and ultimately was due to a proxy not being set on that server (netsh winhttp set proxy), so if you are using proxies, check that. Would've been a tough one to figure out if not for this post. Thanks!
-
Wednesday, July 04, 2012 2:35 PM
Hi,
This post solved my issue after more than 20 hours trying to figure out what it was.
My application servers for Sharepoint do not have access to the internet.
MANY thanks for this post!
André Esteves
-
Friday, October 12, 2012 11:24 AM
Hi,
i had the same issue with our Server. I removed KB2677070 from server and the problem was resolved.
This post solved my problem and saved my time.
Thanks a lot, Arash
-
Friday, October 19, 2012 12:29 AM
Hi There,
We have the same issue here. CA server not internet connected and started getting this error after installing kb2677070. I have followed your adice and removed the update (via Control panel, Progams and features, Uninstall and update). I then restarted the timer service and restarted the machine.
Problem is I stil lget the same error when trying to start the Sharepoint 2010 Administration service:
Windows could not start the Sharepoint 2010 Administration service on SERVERNAME. Error 1053: The service did not respond to the start or control in a timley fashion.
I have also run the Psconfigui.exe again and dont get any errors.
Is there something i've missed or is it possible there are other issues here?
Cheers,
Clarky000
-
Tuesday, October 23, 2012 10:54 PM
OK, so the solution was to update the local group policy. Details:
http://support.microsoft.com/kb/2677070
- Proposed As Answer by clarky000 Tuesday, October 23, 2012 10:54 PM

