February 9, 2007 at 4:20 pm
Hi,
We are running a test upgrade form sql 2000 standard edition to sql 2005 developer edition. Followed through all the steps and specified the account(SA priveleges and currently used by the 2000 version) and is the local admin on the box for the services and the setup seemed to move fine, except for when it got to the point of installing database services - This is the error message that I got:
MSSQLServer could not be started. Verify you have sufficient priveleges to start system services. The was no choice but to hit cancel and then the set up progressed with a final message of 'SEtup failed'.
Here is a portion of the error log:
Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
Database Mirroring Transport is disabled in the endpoint configuration.
Starting up database 'master'.
Converting database 'master' from version 589 to the current version 611.
Database 'master' running the upgrade step from version 589 to version 590.
Error: 946, Severity: 14, State: 1.
Cannot open database 'master' version 589. Upgrade the database to the latest version.
System Task Aggregate global counters produced an error that was not handled. Major: 9, Minor: 46, Severity:14, State:1
Error: 928, Severity: 20, State: 1.
During upgrade, database raised exception 15151, severity 16, state 1, address 01C4C50B. Use the exception number to determine the cause.
Error: 15151, Severity: 16, State: 1.
Cannot find the endpoint 'TSQL Local Machine', because it does not exist or you do not have permission.
Any help would be greatly appreciated
Thanks KR
February 9, 2007 at 4:33 pm
My personal openion it is not go to run inplace upgrade...some times if you get the errors like this...there will not be any option to go back..
Better to side by side upgrade..even if you have single server you can install another instance and run backup/restore or detach/attach for user dbs...
For system dbs you can script the logins and jobs to move to 2005 instance...
How to transfer logins and passwords between instances of SQL Server
http://support.microsoft.com/kb/246133
MohammedU
Microsoft SQL Server MVP
February 9, 2007 at 5:27 pm
Unfortunatley, there is not an option to do side-by-side upgrade on this server --- not enogh resources.
Also, I would like to know what caused this error since the account has all the previleges it needs
Thanks
KR
February 9, 2007 at 5:38 pm
No clue what cuased it...
But what service pack you were on?
Did you run the Upgrade adviser before upgrade?
MohammedU
Microsoft SQL Server MVP
February 9, 2007 at 6:22 pm
The upgrade advisor did show any problems with the upgrade other than some ols syntax issues in the stored procedures to correct after the upgrade.
I was on service pack 4
February 9, 2007 at 11:37 pm
Karthik,
Did u run the upgrade advisor before doing the upgrade. what was the output of the advisor. Did u resolve all those errors/warnings mentioned in the report generated.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
February 10, 2007 at 8:57 am
I did run the upgrade advisor, there were no warnings that needed taken care of before the upgrade. There were warnings about some stored procedures that had syntax that would not work with sql 2005, but that was supposed to be done after. There were also a few stored procedure that look at the master table and the advisor suggested to redo those too anytime. So I did not have any issues to do before the upgrade.
Thanks
KR
February 11, 2007 at 3:20 am
Based on the error it looks like some authentication issue...
Upgrade advisor will check for procedures,logins and dts etc...
MohammedU
Microsoft SQL Server MVP
February 11, 2007 at 9:14 am
Yes, it does seem that way by looking at the error - only the account is in the local admin group for the box and in the system administrator fixed role on the sql server - there should be no authentication problems - which is why it is making no sense to me.
KR
February 12, 2007 at 4:12 pm
Hi,
It was not a rights issue after all - the master database somehow did not get upgraded to sql 2005 version like it should have(I am still trying to find the cause of corruption), so I rebuilt the master, which meant of course I lost all my login info, and database pointers etc, but once I did that, I was able to get my services up and running and completed the upgrade successfully.
Thanks
KR
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply