Monday, 7 January 2008

SharePoint Service Pack 1 crash

Hi,

Some people have had SharePoint stop working after the installation of Service Pack One. This is mainly due to the upgrade process not completing. You can force an upgrade by running the following command from a command prompt:

psconfig -cmd upgrade -force

This will force the upgrade process to run again and should fix the problem for you.


# Added 11 Jan 2008

You might want to also try this:

Click Start, click Run, type cmd in the Open box, and then click OK.
At the command prompt, type the following lines, and then press ENTER after each line:

cd /d %commonprogramfiles%\Microsoft Shared\Web Server Extensions\60\Bin

stsadm -o upgrade -forceupgrade

Let me know how it goes.....

Fadi

43 comments:

Garry said...

Hi Fadi, thanks for this post, my install of SP1 failed, ran psconfig -cmd upgrade -force
and the upgrade continued and finished, website now back online. Thanks, Garry

Anonymous said...

Dude, you are my hero. Here I am on a Sunday installing this SP and the whole site goes down!

But that did indeed fix it.

Anonymous said...

Perfect...did its job, my site is back working now.

Thanks a lot.

wintert said...

Thanks mate.
Worked like a magic.
I redirected the solution from my blog to your blog (hope you can read Hebrew) :)
Have a good week

Anonymous said...

i tried psconfig -cmd upgrade -force
filed at the end...
Failed to upgrade SharePoint Products and Technologies.

An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfig
urationTaskException was thrown. Additional exception information: The upgrade
command is invalid or a failure has been encountered.
Failed to upgrade SharePoint Products and Technologies.

Total number of configuration settings run: 3
Total number of successful configuration settings: 2
Total number of unsuccessful configuration settings: 1
Successfully stopped the configuration of SharePoint Products and Technologies.
Configuration of SharePoint Products and Technologies failed. Configuration mus
t be performed before you use SharePoint Products and Technologies. For further
details, see the diagnostic log located at C:\Program Files\Common Files\Micros
oft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_7_22_2008_16_58_32_703_1
534075706.log and the application event log.

Anonymous said...

i tried with psconfig -cmd upgrade -force command but ended with error

Performing configuration task 3 of 4
Upgrading SharePoint Products and Technologies...

Failed to upgrade SharePoint Products and Technologies.

An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfig
urationTaskException was thrown. Additional exception information: The upgrade
command is invalid or a failure has been encountered.
Failed to upgrade SharePoint Products and Technologies.

Total number of configuration settings run: 3
Total number of successful configuration settings: 2
Total number of unsuccessful configuration settings: 1
Successfully stopped the configuration of SharePoint Products and Technologies.
Configuration of SharePoint Products and Technologies failed. Configuration mus
t be performed before you use SharePoint Products and Technologies. For further
details, see the diagnostic log located at C:\Program Files\Common Files\Micros
oft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_7_22_2008_16_58_32_703_1
534075706.log and the application event log.

hicham said...

Hi Fadi,i executed on "cmd.exe" the comand:psconfig -cmd upgrade -force but i got the following error:

"The upgrade command is invalid or a failure has been encountered.
Failed to upgrade SharePoint Products and Technologies because the upgrade type
is not supported or was not specified.
Usage:
PSCONFIG.EXE -cmd Command [Parameters]
PSCONFIG.EXE -help [Command]
PSCONFIG.EXE -?
Commands:
setup
standaloneconfig
configdb
helpcollections
secureresources
services
installfeatures
adminvs
upgrade
evalprovision
applicationcontent
quiet"

Fadi Noja said...

can you send me a copy of the error log.

Fadi Noja said...

try stsadm -o upgrade -inplace -force...

Fadi

Fadi Noja said...

Can you send me your logs and ill see what went wrong....

Anonymous said...

Hi Fadi, Your my hero too. I used the stsadm -o upgrade -inplace -forceupgrade. It took about 5-10 minutes to complete and everything is back. Thanks, Gerry

Anonymous said...

Fadi, You are my hero too. I used the stsadm -o upgrade -inplace -forceupgrade and it took 5-10 minutes to complete and everything came up. Thanks, Gerry

Anonymous said...

YOU.SAVED.ME!!
God, this was really a life saver :-)!

I installed a WSS hotfix and then my Central Admin wasn't accessible anymore. Using the stsadm -o upgrade -forceupgrade command did the trick!
I owe you big time :-)

Anonymous said...

Hi Fadi

Both psconfig -cmd upgrade -force and stsadm -o upgrade -inplace -forceupgrade failed.

psconfig failed at cnofig 3 an stsadm could not start the service SPTimer on computer

Suresh.C said...

Thanks a lot....
You Saved My Time...

Anonymous said...

Hi Fadi and friends...
wish you could help me...
i already like you said
stsadm -o upgrade -inplace -forceupgrade....
its work but with some error....

Upgrade completed with errors. Review the upgrade.log file located in C:\Progra
m Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs\Upgrade.log.
The number of errors and warnings is listed at the end of the upgrade log file....

so could you help me...anybody...please.... :D
wait for your explanation...

Thanks, Reza, Indonesia

Anonymous said...

Thank you ! Life saver!!

i had the same problem , and after i run "psconfig -cmd upgrade -force" in cmd. the central admin came back, so happy!!!@@

Fran├žois said...

Hey, I know this post is old.
But am experiencing a similar problem, although the Central Admin is available, and so is one Web App but none of the other.
Running PSCONFIG -cmd upgrade -
or the STSADM equivalent for a site collection did not fix it.

Logs looks like it's a right problem on the SQL DBs :-( but they have domain admin login.
suggestion ?

Anonymous said...

Hi Fadi
Like all the others... a big thanks for the post.
Just to help search engines..
We have SharePoint 2007 MOSS running on Windows 2008 server and SQL 2008 also on W2K8.
I ran the two command lines and it fixed it!
Thanks again
Larry (Cambridge UK)

Anonymous said...

Hi Fadi,

After installing windows updates I am unable to open up my sites on MOSS 2007.I am getting the following error..

Server error: http://go.microsoft.com/fwlink?LinkID=96177

I can open up Central Admin site.

Thank you for your time.

Fadi Noja said...

Can you send me the error code or the event logs so I can try to help

Anonymous said...

Fadi,

event logs are:

event id:6102
LoadBalancer.RegisterLauncher failed: Unable to connect to the remote server

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

event id: 18456

Login failed for user 'SBTUSBFG1003WS\Administrator'. [CLIENT: 192.168.10.1]

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

0000: 18 48 00 00 0e 00 00 00 .H......
0008: 1d 00 00 00 53 00 42 00 ....S.B.
0010: 54 00 55 00 53 00 42 00 T.U.S.B.
0018: 46 00 47 00 31 00 30 00 F.G.1.0.
0020: 30 00 33 00 57 00 53 00 0.3.W.S.
0028: 5c 00 4f 00 46 00 46 00 \.O.F.F.
0030: 49 00 43 00 45 00 53 00 I.C.E.S.
0038: 45 00 52 00 56 00 45 00 E.R.V.E.
0040: 52 00 53 00 00 00 07 00 R.S.....
0048: 00 00 6d 00 61 00 73 00 ..m.a.s.
0050: 74 00 65 00 72 00 00 00 t.e.r...

Anonymous said...

Fadi,

Just now I have created new site and it is opening up but the old sites are not opening up.

i tried stsadm -o upgrade -inplace
and i got:

upgrade completed with errors.Review the upgrade.log

Fadi Noja said...

have you got the GroupBoard site template installed? if you do, uninstall it, run the wizard then re-install it.

Anonymous said...

Fadi,

I have deleted the site which has TCM Template(GroupBoard)...still configuration is failed.

can you please tell me your email id,so I can send PSDiagnostics log file.

Anonymous said...

Hi Fadi,

I'm having the same issues as those above with it failing at step three. Our site was up and running and then the server was restarted and hotfixes were installed. Any help would be very appreciated.

Anonymous said...

When I try to run the command, I just get the same as stsadm -help, it does not work!
Why?

Thanks

Fadi Noja said...

try

stsadm.exe -o upgrade -inplace

Fadi

Administrator said...

I do not have the 60 folder as listed in this file path: cd /d %commonprogramfiles%\Microsoft Shared\Web Server Extensions\60\Bin

I have a 50 folder and the 12 hive. Any ideas? I upgraded to Service Pack 2 and receive the following error. An error has occurred on the server.http://go.microsoft.com/fwlink?LinkID=96177

Fadi Noja said...

sorry, was a typo, should be the 12 hive.

AlbertWT said...

Hi Fadi,

the upgrade also failed on my Windows 2008 SP1 + MOSS 2007 SP1 + SQL 2008 SP1

what i did is that i upgraded SQL Serve 2008 SP1 -> OK
and then WSS 3.0 SP2 --> OK (wssv3sp2-kb953338-x64-fullfile-en-us.exe)
but MOSS 2007 SP2 --> FAILED (officeserver2007sp2-kb953334-x64-fullfile-en-us.exe)

here is the following command that i tried but failed.

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>psconfig
'psconfig' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Administrator>stsadm
'stsadm' is not recognized as an internal or external command,
operable program or batch file.

any idea of how to get it back again please ?

Fadi Noja said...

are there any errors in the upgrade.log file? Did it fail during the wizard or the install?

DeeKe said...

Hi Fadi,

I am stuck-up with problems after sp1 installation. psconfig failed with below message.

Performing configuration task 1 of 4
Initializing SharePoint Products and Technologies upgrade...

Successfully initialized SharePoint Products and Technologies upgrade.

Performing configuration task 2 of 4
Initiating the upgrade sequence...

Successfully initiated the upgrade sequence.

Performing configuration task 3 of 4
Upgrading SharePoint Products and Technologies...

Failed to upgrade SharePoint Products and Technologies.

An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfig
urationTaskException was thrown. Additional exception information: The upgrade
command is invalid or a failure has been encountered.
Failed to upgrade SharePoint Products and Technologies.

Total number of configuration settings run: 3
Total number of successful configuration settings: 2
Total number of unsuccessful configuration settings: 1
Successfully stopped the configuration of SharePoint Products and Technologies.
Configuration of SharePoint Products and Technologies failed. Configuration mus
t be performed before you use SharePoint Products and Technologies. For further
details, see the diagnostic log located at C:\Program Files\Common Files\Micros
oft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_6_14_2009_10_57_34_797_1
087511976.log and the application event log.

An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information: The upgrade command is invalid or a failure has been encountered.
Failed to upgrade SharePoint Products and Technologies.
Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException: Exception of type 'Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException' was thrown.
at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

Any immediate help is highly appreciated.

Thanks,

Rick said...

Hi fadi,

I found an error in my upgrade log after using stsadm.exe -o upgrade -inplace with the following error:

[SPManager] [ERROR] [8/10/2009 4:46:16 PM]: The service did not start due to a logon failure
[SPManager] [ERROR] [8/10/2009 4:46:16 PM]: Cannot start service SPSearch on computer '.'.
[SPManager] [ERROR] [8/10/2009 4:46:16 PM]: at System.ServiceProcess.ServiceController.Start(String[] args)
at System.ServiceProcess.ServiceController.Start()
at Microsoft.SharePoint.Win32.SPAdvApi32.StartService(String strServiceName)
at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Start()
at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision(Boolean start)
at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision()
at Microsoft.SharePoint.Search.Administration.SPSearchServiceInstance.Provision()
at Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.EnableAndProvisionSearchNTService()
at Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.PostUpgrade()
at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse)
[SPManager] [INFO] [8/10/2009 4:46:16 PM]: Resetting the status of PersistedUpgradableObject: SPServer Name=dev-server Parent=SPFarm Name=SharePoint_Config to Online.
[SPManager] [ERROR] [8/10/2009 4:46:16 PM]: ReflexiveUpgrade [SPServer Name=dev-server Parent=SPFarm Name=SharePoint_Config] failed.
[SPManager] [ERROR] [8/10/2009 4:46:16 PM]: The service did not start due to a logon failure
[SPManager] [ERROR] [8/10/2009 4:46:16 PM]: Cannot start service SPSearch on computer '.'.
[SPManager] [ERROR] [8/10/2009 4:46:16 PM]: at System.ServiceProcess.ServiceController.Start(String[] args)
at System.ServiceProcess.ServiceController.Start()
at Microsoft.SharePoint.Win32.SPAdvApi32.StartService(String strServiceName)
at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Start()
at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision(Boolean start)
at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision()
at Microsoft.SharePoint.Search.Administration.SPSearchServiceInstance.Provision()
at Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.EnableAndProvisionSearchNTService()
at Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.PostUpgrade()
at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse)
[SPManager] [INFO] [8/10/2009 4:46:16 PM]: Resetting the status of PersistedUpgradableObject: SPFarm Name=SharePoint_Config to Online.
[SPManager] [INFO] [8/10/2009 4:46:16 PM]: Inplace Upgrade session finishes. root object = SPFarm Name=SharePoint_Config, recursive = True. 3 errors and 0 warnings encountered.
[SPManager] [ERROR] [8/10/2009 4:46:16 PM]: Upgrade failed.
[SPManager] [ERROR] [8/10/2009 4:46:16 PM]: Upgrade completed with errors. Review the upgrade.log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs\Upgrade.log. The number of errors and warnings is listed at the end of the upgrade log file.
[SPManager] [ERROR] [8/10/2009 4:46:16 PM]: at Microsoft.SharePoint.Upgrade.SPManager.RunUpgradeSession(IUpgradable root, Boolean bRecursive)
at Microsoft.SharePoint.StsAdmin.SPUpgrade.RunUpgrade(StringDictionary keyValues)

Please help, thank you in advance.

Fadi Noja said...

Hi Rick,

Have you got any templates installed? I had the same issue when I installed the Microsoft Group Template and it cause SP2 to fail install.

Rick said...

Hi Fadi,

I haven't got any template installed. I just installed the WSS3 SP1 and then it gave me this error. But I could open the Central Administration page but not the SharePoint page. It gave me the error message say that "Server error: http://go.microsoft.com/fwlink?LinkID=96177"...

Thank you, Rick

Fadi Noja said...

Ok, it's probably quicker to email me. But I need to know a few things:

1, Are you using just WSS or MOSS?
2, 1 server farm or multiple
3, are there any third party software installed?

rick said...

Hi Fadi, below answers your questions:
1. I use both MOSS and WSS.
2. I have only 1 server running.
3. I don't have any third party software installed.

PS: I have found that while installing it could start the SPSearchInstance and it asked me to start the service manually. I don't know if this will cause the problem or not but this is the only one problem I could catch on screen.

I would like to say you are my hero as the others :) so that I can rest today. Thank you for helping me.

Fadi Noja said...

email me - fadi@dhf.com.au

Have you tried the force install? Also did you install both MOSS SP1 and WSS SP1 and in the correct order?

rick said...

If the force install meant the given SharePoint commands in your post then I have tried both of them already but they didn't work with me. And when install, I installed the WSS SP1 first but it was not successful installed and my SharePoint page gave me an error message "An error has occurred on the server.http://go.microsoft.com/fwlink?LinkID=96177".

By the way, thank you very much for your email I will attach the upgrade.log for you.

Anonymous said...

Guys,
I found out that the GroupBoard application/addon/webpart was teh cause of this error for us.

It may be too much to ask for two microsoft products to work cohesively.

Anonymous said...

thanx a lot fadi

stsadm -o upgrade -inplace -forceupgrade

did the trick for me

Thomas said...

Hi and thanks for the excellent info! Installed MS hotfix package (Sts.msp): October 28, 2008 and it crashed the Sharepoint.

I used the "stsadm -o upgrade -forceupgrade" and it worked perfect after that.

Your article helped me a lot.

Thanks
/Thomas