jonnyIT
asked on
WSS3.0 no longer working after running "stsadm -o upgrade -inplace"
Hi all,
Whilst trying to sort out some 33002 errors by running "stsadm -o upgrade -inplace" I can no longer navigate to my sharepoint site. Nor can I get to the admin pages.
I noticed that it stopped various IIS and Exchange services after completing the command, but on restarting these, WSS3 will not work!
Companyweb, the built-in SBS sharepoint 2 app seems to still work fine, but I just get error 404 when I try to navigate to http://intranet, the normal URL of the WSS3 site.
Back to the command I ran, I copied and pasted it from somewhere but realised afterwards that it should have "-url http://....." on the end of it. What have I messed up by missing this switch?
I can still navigate to the DB in SQL Server Management Studio Express ok.
A new error I can see in the event log is "The database SharePoint_AdminContent_79 78a1c6-e6e b-40b6-831 4-0d74133a 8611 on RTKSBS01\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures." for all the sharepoint DBS.
Thanks in advance,
Jonny
Whilst trying to sort out some 33002 errors by running "stsadm -o upgrade -inplace" I can no longer navigate to my sharepoint site. Nor can I get to the admin pages.
I noticed that it stopped various IIS and Exchange services after completing the command, but on restarting these, WSS3 will not work!
Companyweb, the built-in SBS sharepoint 2 app seems to still work fine, but I just get error 404 when I try to navigate to http://intranet, the normal URL of the WSS3 site.
Back to the command I ran, I copied and pasted it from somewhere but realised afterwards that it should have "-url http://....." on the end of it. What have I messed up by missing this switch?
I can still navigate to the DB in SQL Server Management Studio Express ok.
A new error I can see in the event log is "The database SharePoint_AdminContent_79
Thanks in advance,
Jonny
ASKER
I was not trying to upgrade the companyweb site, as that is a completely different version of Sharepoint (2 vs 3). I read somewhere that one of the errors I was seeing was a result of not all parts updating when a particular update was applied. I was under the impression that the stsadm command just finished the job and ensured that everything was all at the same level.
Having missed out a bit of the command though, I want to know what I've knocked out. I've got backups of the MDF and LDF files for all the DBs but the last site backup I made throught he WSS3 admin tools was over a month ago.
Cheers for the response.
Jonny
Having missed out a bit of the command though, I want to know what I've knocked out. I've got backups of the MDF and LDF files for all the DBs but the last site backup I made throught he WSS3 admin tools was over a month ago.
Cheers for the response.
Jonny
Try running the PSConfig wizard GUI and let me know what stage it fails on.
:-)
:-)
ASKER
It stops after you are prompted if you want to allow it to stop the IIS services during installation. I've attached a screenshot and a text file containing the full error description.
Below is a snippet from it;
fulldetail.txt
Below is a snippet from it;
************** Exception Text **************
System.InvalidOperationException: Operation is not valid due to the current state of the object.
at Microsoft.SharePoint.Administration.SPContentDatabase.ValidateDatabaseSchemaCompatibility()
at Microsoft.SharePoint.SPSite.PreinitializeServer(SPRequest request)
at Microsoft.SharePoint.SPWeb.InitializeSPRequest()
at Microsoft.SharePoint.SPWeb.EnsureSPRequest()
at Microsoft.SharePoint.SPWeb.get_Request()
at Microsoft.SharePoint.SPWeb.InitWeb()
at Microsoft.SharePoint.SPWeb.get_WebTemplate()
at Microsoft.SharePoint.SPEvaluatorModeProvisioning.TryGetIsSiteProvisioned(String template, String relativePath, Nullable`1 port, SPSite& provisionedSite, SPWeb& provisionedWeb, Uri& provisionedUri)
at Microsoft.SharePoint.PostSetupConfiguration.WelcomeForm.ShowNextFormForServerRoleSingleServer()
at Microsoft.SharePoint.PostSetupConfiguration.WelcomeForm.PsconfigBaseFormNextButtonClickedEventHandler(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
untitled.JPGfulldetail.txt
Run a repair of SharePoint and then reboot the server. Try it again and let me know what happens.
:-)
:-)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sorry, I'm a bit of a noob when it comes to Sharepoint. When you say 'repair', is that using the PSConfigui.exe tool, as if I continue after the error which pops up, and click 'Next', it goes straight the the previous question again and procedes in circles!
Try the last command first:
"psconfig -cmd upgrade -inplace b2b -wait"
If this fails, use Add/Remove Programs and repair SharePoint.
:-)
"psconfig -cmd upgrade -inplace b2b -wait"
If this fails, use Add/Remove Programs and repair SharePoint.
:-)
ASKER
Thank you so much! The "psconfig -cmd upgrade -inplace b2b -wait" worked perfectly and everything's back up and working properly.
Can you explain what that command does please?
I only signed up today for the answer for this question, but I can see it's definitely worth continuing my subscription!
Regards,
Jonny
Can you explain what that command does please?
I only signed up today for the answer for this question, but I can see it's definitely worth continuing my subscription!
Regards,
Jonny
ASKER
Thanks so much for your help.
Jonny
Jonny
The command finishes off the upgrade sequence. I'm not sure what b2b stands for and have just done a search to try and find out. Didn't find anything really.
I'm glad that it worked for you though, and that you're so pleased. SharePoint is a wonderful product and i'm sure you're going to have some real fun with it.
Good luck.
:-)
I'm glad that it worked for you though, and that you're so pleased. SharePoint is a wonderful product and i'm sure you're going to have some real fun with it.
Good luck.
:-)
:-)