Bill Baer

Senior Product Marketing Manager (SharePoint), Microsoft Certified Master for SharePoint, Microsoft Corporation

KB934525 Troubleshooting "Cannot start service SPAdmin on computer '.'."

KB934525 Troubleshooting "Cannot start service SPAdmin on computer '.'."

  • Comments 11
  • Likes

I've come across a handful of posts regarding KB934525 for Windows SharePoint Services and failure to start the Windows SharePoint Services Administration service.  I've attached some basic troubleshooting steps that may provide resolution to issues where psconfig fails with Cannot start service SPAdmin on computer '.'.  For those who have installed the KB and have experienced issues where the service has failed to start, Option 4 is the recommended solution. 

UPDATE Oct. 15, 2007 18:50 If you are unable to successfully initialize and complete the SharePoint Products and Technologies Configuration Wizard (psconfig) after following the steps in Option 4 below, consider Options 1 through 3; otherwise, uninstall WSS from the server, reinstall WSS, extract the contents of the KB using the steps provided in Option 3 below and install from the extracted STS.msp and following the remaining steps in Option 4 to start SPAdmin and complete configuration.

UPDATE Oct. 16, 2007 13:15 I received information indicating you may also experience the attached error in your server farm to which Option # 4 resolves:

The schema version (3.0.149.0) of the database WSS_Content_<databasename> on <databaseserver>\<instance> is not consistent with the expected database schema version (3.0.151.0) on <database>.  Connections to this database from this server have been blocked to avoid data loss.  Upgrade the web front end or the content database to ensure that these versions match.

UPDATE Oct. 23, 2007 14:52

See below on steps to resolve The database WSS_Content on HOME\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures.

Option # 1 

  • Start the Windows SharePoint Services Administration service using the Services applet (Start, Run, Services.msc) and run SharePoint Products and Technologies Configuration Wizard.

Option # 2 

  • Start the SPAdmin service under the context of a local administrator on the server where the SPAdmin service failed to start when running the SharePoint Products and Technologies Configuration Wizard (psconfig.exe) and run SharePoint Products and Technologies Configuration Wizard.
net start spadmin

Option # 3 

Extract wssv3-kb934525-fullfile-x86-glb.exe and run the installation by executing C:\temp\STS.msp (see below).

<drive>:\wssv3-kb934525-fullfile-x86-glb.exe /extract:c:\temp.

Option # 4 

  • On the machine where psconfig failed to start the SPAdmin service run:
%commonprogramfiles%\Microsoft Shared\Web Server Extensions\12\BIN\psconfig -cmd upgrade -inplace b2b -wait -force

Modify the service timeout values in the Registry:

HKLM\SYSTEM\CurrentControlSet\Control add/modify DWORD value ServicesPipeTimeout to 60000 (60 seconds)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control add/modify STRING value WaitToKillServiceTimeout to 120000 (120 seconds)

Restart the server machine.

UPDATE Oct. 23, 2007 14:52

A solution is available to administrators of SharePoint Products and Technologies deployments experiencing the following application event after introducing WSS October public update KB934525.

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Topology
Event ID: 6800
Date: 10/17/2007
Time: 8:09:40 PM
User: NA
Computer: HOME
Description: The database WSS_Content on HOME\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures.

1.  Run the following STSADM operations to stop and start the SPWebService:

stsadm -o provisionservice -action stop -servicetype spwebservice -servicename ""

stsadm -o provisionservice -action start -servicetype spwebservice -servicename ""

2.  Instantiate the upgrade by executing psconfig.exe or psconfigui.exe.

The cause of this issue is the SPWebService instance failed to finish provisioning. The status of that service is marked as provisioning. However, it has done enough provisioning work so that the user sites are working and/or during upgrade, the upgrade code skipped any web service instances that are not online, upgrading the administration sites; however, skipping the user sites.

Comments
  • Excellent advice, and timely too - I've been battling this MS screw-up all day. None of the other workarounds I had found worked, your Option #4 did the trick - thank you :)

  • Thanks for this info William, however, I have followed your instructions in Option #4 and now I have a permissions problem!  Any ideas?

  • Can you elaborate on the scope of the permissions problem you are experiencing?

  • Thanks Bill, you're a champ! Option # 4 sorted out my issues on day 2 of a new semester, the teachers were too busy to notice their site was down for a day and a half 8-)

  • William,  I was being prompted for a username and password and regardless of what I entered I would be presented with a 'You are not authorized to view this page' message.

    I simply rebooted the server again and everything seems to be working fine now.

    Is there any detailed discussion as to what KB934525 actually did to break things??

    Thanks again for your very valuable help, it has saved quite a bit of embarrassment and not to mention work for me!

    Brian Cowley

  • Man I wish I'd known this last week.  Great info- thanks!

  • Seriously, you should install the updates before you have to set those clocks back an hour. Heck, if

  • I've gotten some questions asked on the hotfix and public update I wanted to address here. Product Support

  • Thanks for the advice - this is what got me back up and running without having to restore from backup:

    1. Download this file that matches your OS. http://www.microsoft.com/downloads/details.aspx?familyid=A49472F9-93E

    If you try to run the file it will tell you the patch is already installed but run the file with "/extract" extract the file to a temp folder and run  "dw20w.msp" (can take a long time to run - 5mins for us, 1hr for others)

    2.  Stop the WSV3C service using a command prompt (net stop w3svc).  

    3.  Change directory to <system drive>\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN and run the following command: psconfig -cmd upgrade -inplace b2b -wait

  • We ran into a condition when running the configuration wizard in which for 2 1/2 hours all that was appearing in the upgrade log was the following:

    SyncUpgradeTimerJob: sleeping for 10 seconds

    We noticed that in our from dev and stage farms this message was only logged for a minute or two before the upgrade process proceeded.  We also noticed that the upgrade had stopped the sptimerv3 service but we had an automated MOM rule that had restarted it.  We simply stopped sptimerv3 for a few minutes then re-started it.  Within 5 minutes the upgrade had proceeded passed the sleeping phase and was upgrading databases.  It completed successfully.  

  • Body: I was recently called into do some reviews of several server farm deployments. As part of our services

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment