If you receive the following error during a SPS 2003 -> MOSS 2007 upgrade: “Failed to
start the database service MSSQL$OfficeServers. Repair this product using Add/Remove Programs”
The chances are that you have selected an invalid option during configuration. When you first configure the product on a machine that is running a previous version, you will be asked if you would like to perform a gradual upgrade, an in-place upgrade, no upgrade. If you quickly choose one of the options and click next and you are already running SQL Server 2000, you will more than likely run into this problem. In order to fix this problem, perform a reinstall (yes I know, it’s a pain in the behind). Then next time around, before clicking next, click the second tab located across the top of the wizard. You will now see 3 more options, where you can choose to either do a ‘complete’ install, or the default which is ‘stand alone server’. The default option, just so happens to install all of the components AND the database server (MSDE). This is where I believe the problem is. What it seems to be doing is trying to install MSDE, then it updates the internal service instance registry key to point to a services instance that does not exist (MSSQL$OfficeServers). I located the key, and tried to change it manually back to the correct instance, but I had no luck (perhaps you might, if you dare try). So:
There’s plenty more of these gotcha’s which I will blog for you over the course of the next few weeks. I am currently doing a lot of work around migration, so if you have any questions just drop me a comment or an email.
MOSS 2007 Upgrade Error
3 07 2006Reinstall
Select ‘Complete Installation (The first option in the list)
Click next to continue the install
Now after your restart, when you re-run the configuration wizard, you will not get this error. It should continue to play nicely
Hi,
I had the same problem when trying to upgrade from MOSS2007 beta2 to beta2TR.
How did you solved that ?
Does somebody else see the same problem as me ?
Damien
Hi,
I had the same problem when trying to upgrade from MOSS2007 beta2 to beta2TR.
How did you solved that ?
Does somebody else see the same problem as me ?
Damien
Hi, thanks for the tip – I had a similar error but the service name was different.
Unfortunately, under the second tab (Server Type), there are only two options:
Web Front End
Stand-alone
The Stand-alone option is the one that caused the problem.
Reinstalling with Web Front End looks like it might work…
Marc
I had same problem
I uninstall the MOSS and install again with standard installation settings
and it worked for me!
Hi,I got the same problem.I reinstalled the MOSS and the problem was resolved.Thanks a lot.
Many thanks: spent 1.5 days trying to wrestle MOSS onto a test box and the ‘Complete Install’ tip was a major help. Cheers.
I have similar problem when I uninstall Search Server Express 2008. Trying to reinstall MOSS2007, but problem still persist.
I’m running on a migration project to migrate from Lotus Note to Sharepoint. Do you have experiences about this? If you have, could we discuss about it? My email: nhutnh@fsoft.com.vn
Thanks a ton ….Complete install solved the problem