Sharepoint and SBS monitoring Databases Fail to Start after Upgrade to 10d

[Curt_Maas]

We installed a new copy of Backup Exec 10.0 for SBS on a SBS 2003 server about two weeks ago.

We upgraded the 10.0 to 10d and the upgrade failed and rolled back to 10.0. After the roll back we had to uninstall 10.0 because it would not run. We then installed 10d and noticed that both the MSSQL$SHAREPOINT and MSSQL$SBSMonitoring databases would not start. The Event log shows there were Database on these databases errors starting at the time of the rollback.

Is this a known issue and if so is there a way to repair the MSSQL services so that they start properly? Sharepoint is not that difficult to reinstall but the SBS Monitoring database is a bit more involved.

Any help or insight would be appreciated.

[Ajit_Kulkarni]

Hello,


How did you first uninstalled Backup Exec ?

Was it successful ?

Also, was the reinstallation of Backup Exec also successful ?


Kindly update.


Regards


NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.

[Curt_Maas]

Ajit

It appears that the roll back caused the database issues with Sharepoint and the SBSMonitoring. We attempted to upgrade the BE 10 to BE10d. We received an error message at about 95% complete and the rollback commenced. When we tried to run BE it would not talk to the tape drives any longer so we rebooted.

After the reboot we could still not talk to the tape drives so we performed the uninstall from the add remove programs option in control panel. We then installed 10d clean and it works. We did not notice that Sharepoint was not running until we began looking at the website and the event logs. The time stamp in the logs for the Sharepoint and SBS Monitoring database errors showed up after the first reboot where we had attempted to get the tape drivers back on line.

[Curt_Maas]

Ajit

Also one thing I forgot to mention, the actual databases are still on the disk and appear intact. It is the MSSQL$Sharepoint and the MSSQL$SBSMonitoring services that will not start either automatically or manually. These had been running up until the rollback.

[Asma_Tamboli]

Hi,



Could you please update us on the issue?


NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.