May 20, 2011 at 9:36 am
Hi, I've tried an UpGrade from 9.3.4294 (2005 SP3 PatchSet 9) to 10.50.1600.1.
The setup failed by execution of 'sqlagent100_msdb_upgrade.sql' with error code 574.
I found the following KB articele http://support.microsoft.com/kb/960781 and this blog http://blogs.msdn.com/b/psssql/archive/2008/09/10/upgrade-for-sql-server-2008-can-fail-if-you-have-renamed-the-sa-account.aspx.
I could start the service and execute the proposed statement to my named instance as followes:
...\Binn\sqlservr.exe" -sSAPQPT -c -f -T 3608
<-- message if sqlcmd is active:
2011-05-20 16:13:46.88 spid51 Starting up database 'QPT'.
2011-05-20 16:13:47.89 spid51 CHECKDB for database 'QPT' finished without e
rrors on 2011-05-15 09:00:06.870 (local time). This is an informational message
only; no user action is required.
sqlcmd -S tpzsqp01\SAPQPT -E -A -Q"alter login <sys-admin> with name = sa"
<-- this gives no feedback to the console...
After this I've used the Repair function of the SQL 2008 setup, but it failed on the same scipt 'sqlagent100_msdb_upgrade.sql'.
I've also tried to change the sa password
sqlcmd -S tpzsqp01\SAPQPT -E -A -Q"ALTER LOGIN sa WITH PASS
WORD = 'xxx' UNLOCK;"
But I'm not able to connect to the server via TCP
C:\Windows\system32>sqlcmd -U sa
Password: HResult 0x274D, Level 16, State 1
TCP Provider: No connection could be made because the target machine actively re
fused it.
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establi
shing a connection to the server. When connecting to SQL Server 2005, this failu
re may be caused by the fact that under the default settings SQL Server does not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
At the moment I don't know what is wrong with the master db and why the setup can not connect with the sa account... we did not change this account in the past?!
May 20, 2011 at 9:45 am
Is that all of the error information that you have?
I'm not too clear what what you have done and why.
Here is a thread where someone got a similar error. I was not sure if you truncated your error message so it may not be of any help:
http://connect.microsoft.com/SQLServer/feedback/details/564134/sql-server-2008-r2-upgrade-failure
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
May 20, 2011 at 9:48 am
Thx, I will take a look... error messages are:
Detail.txt
2011-05-20 10:26:03 Slp: Error result: -2061893608
2011-05-20 10:26:03 Slp: Result facility code: 1306
2011-05-20 10:26:03 Slp: Result error code: 24
SQLServer_ERRORLOG_2011-05-20T09.47.03.txt
cript level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 574, state 0, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x4BDAF9BA@1306@24
Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110520_164101\Detail.txt
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x4BDAF9BA@1306@24
Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110520_164101\Detail.txt
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x4BDAF9BA@1306@24
Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110520_164101\Detail.txt
May 20, 2011 at 9:55 am
I've done the setup and this failed with the same error as described in http://support.microsoft.com/kb/960781. I've followed up this KB article but it did not solve the problem. The problem is still available.
But we never changed the account name for the database user sa, we only changed the password for this account.
May 20, 2011 at 10:06 am
hanging the password would not casue this.
Did you check the error logs?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
May 20, 2011 at 10:14 am
the SQL logs not in detail... but the summarys from above.
I will take a look to the setup error logs line by line on Monday... thanks for all your help
...If the setup runs the SQL Server the following event logs accours:
Application: Error .NET Runtime Optimization Service Event ID 1101
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\Tools\VDT\DataProjects.dll . Error code = 0x8007000b
Application: Error MSSQL$SAPQPT Event ID 3417
Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
Application: Error MSSQL$SAPQPT Event ID 912
Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 574, state 0, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
Syste: Error IscsiPrt Event ID 54
Initiator Service failed to respond in time to a request to encrypt or decrypt data.
....
from Details.txt
2011-05-20 16:57:01 Slp: Error: Action "SqlEngineDBStartConfigAction_repair_configrc_Cpu64" failed during execution.
2011-05-20 16:57:15 Slp: Error result: -2061893608
2011-05-20 16:57:15 Slp: Result facility code: 1306
2011-05-20 16:57:15 Slp: Result error code: 24
from ERROR log
2011-05-20 16:56:25.40 spid7s Error: 3729, Severity: 16, State: 1.
2011-05-20 16:56:25.40 spid7s Cannot DROP FUNCTION 'dbo.fn_sysdac_get_currentusername' because it is being referenced by object 'DF__sysdac_in__creat__7152C524'.
2011-05-20 16:56:25.48 spid7s Error: 2714, Severity: 16, State: 3.
2011-05-20 16:56:25.48 spid7s There is already an object named 'fn_sysdac_get_currentusername' in the database.
2011-05-20 16:56:47.32 spid7s Error: 574, Severity: 16, State: 0.
2011-05-20 16:56:47.32 spid7s CONFIG statement cannot be used inside a user transaction.
2011-05-20 16:56:47.34 spid7s Error: 912, Severity: 21, State: 2.
2011-05-20 16:56:47.34 spid7s Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 574, state 0, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2011-05-20 16:56:47.36 spid7s Error: 3417, Severity: 21, State: 3.
2011-05-20 16:56:47.36 spid7s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
May 20, 2011 at 10:20 am
How about the SQL Server Setup Log?
http://msdn.microsoft.com/en-us/library/ms143702.aspx
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
May 20, 2011 at 10:20 am
Welsh Corgi (5/20/2011)
How about the SQL Server Setup Log?
from Details.txt
2011-05-20 16:57:01 Slp: Error: Action "SqlEngineDBStartConfigAction_repair_configrc_Cpu64" failed during execution.
2011-05-20 16:57:15 Slp: Error result: -2061893608
2011-05-20 16:57:15 Slp: Result facility code: 1306
2011-05-20 16:57:15 Slp: Result error code: 24
from ERROR log
2011-05-20 16:56:25.40 spid7s Error: 3729, Severity: 16, State: 1.
2011-05-20 16:56:25.40 spid7s Cannot DROP FUNCTION 'dbo.fn_sysdac_get_currentusername' because it is being referenced by object 'DF__sysdac_in__creat__7152C524'.
2011-05-20 16:56:25.48 spid7s Error: 2714, Severity: 16, State: 3.
2011-05-20 16:56:25.48 spid7s There is already an object named 'fn_sysdac_get_currentusername' in the database.
2011-05-20 16:56:47.32 spid7s Error: 574, Severity: 16, State: 0.
2011-05-20 16:56:47.32 spid7s CONFIG statement cannot be used inside a user transaction.
2011-05-20 16:56:47.34 spid7s Error: 912, Severity: 21, State: 2.
2011-05-20 16:56:47.34 spid7s Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 574, state 0, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2011-05-20 16:56:47.36 spid7s Error: 3417, Severity: 21, State: 3.
2011-05-20 16:56:47.36 spid7s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
May 20, 2011 at 10:33 am
mulle-78 (5/20/2011)
Welsh Corgi (5/20/2011)
How about the SQL Server Setup Log?from Details.txt
2011-05-20 16:57:01 Slp: Error: Action "SqlEngineDBStartConfigAction_repair_configrc_Cpu64" failed during execution.
2011-05-20 16:57:15 Slp: Error result: -2061893608
2011-05-20 16:57:15 Slp: Result facility code: 1306
2011-05-20 16:57:15 Slp: Result error code: 24
from ERROR log
2011-05-20 16:56:25.40 spid7s Error: 3729, Severity: 16, State: 1.
2011-05-20 16:56:25.40 spid7s Cannot DROP FUNCTION 'dbo.fn_sysdac_get_currentusername' because it is being referenced by object 'DF__sysdac_in__creat__7152C524'.
2011-05-20 16:56:25.48 spid7s Error: 2714, Severity: 16, State: 3.
2011-05-20 16:56:25.48 spid7s There is already an object named 'fn_sysdac_get_currentusername' in the database.
2011-05-20 16:56:47.32 spid7s Error: 574, Severity: 16, State: 0.
2011-05-20 16:56:47.32 spid7s CONFIG statement cannot be used inside a user transaction.
2011-05-20 16:56:47.34 spid7s Error: 912, Severity: 21, State: 2.
2011-05-20 16:56:47.34 spid7s Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 574, state 0, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2011-05-20 16:56:47.36 spid7s Error: 3417, Severity: 21, State: 3.
2011-05-20 16:56:47.36 spid7s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
You added that after I ask for it. :hehe:
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
May 20, 2011 at 10:35 am
mulle-78 (5/20/2011)
Welsh Corgi (5/20/2011)
How about the SQL Server Setup Log?from Details.txt
2011-05-20 16:57:01 Slp: Error: Action "SqlEngineDBStartConfigAction_repair_configrc_Cpu64" failed during execution.
2011-05-20 16:57:15 Slp: Error result: -2061893608
2011-05-20 16:57:15 Slp: Result facility code: 1306
2011-05-20 16:57:15 Slp: Result error code: 24
from ERROR log
2011-05-20 16:56:25.40 spid7s Error: 3729, Severity: 16, State: 1.
2011-05-20 16:56:25.40 spid7s Cannot DROP FUNCTION 'dbo.fn_sysdac_get_currentusername' because it is being referenced by object 'DF__sysdac_in__creat__7152C524'.
2011-05-20 16:56:25.48 spid7s Error: 2714, Severity: 16, State: 3.
2011-05-20 16:56:25.48 spid7s There is already an object named 'fn_sysdac_get_currentusername' in the database.
2011-05-20 16:56:47.32 spid7s Error: 574, Severity: 16, State: 0.
2011-05-20 16:56:47.32 spid7s CONFIG statement cannot be used inside a user transaction.
2011-05-20 16:56:47.34 spid7s Error: 912, Severity: 21, State: 2.
2011-05-20 16:56:47.34 spid7s Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 574, state 0, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2011-05-20 16:56:47.36 spid7s Error: 3417, Severity: 21, State: 3.
2011-05-20 16:56:47.36 spid7s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
You added that after I ask for it. :hehe:
It is not looking good.
"2011-05-20 16:56:47.36 spid7s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online."
I hope that this a Test Machine.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
May 23, 2011 at 1:22 am
yes it is the first upgrade try on a test machine...
I found a further blog: http://datazulu.com/blog/post/Sql2008-R2-Upgrade-Fail.aspx
But default file and default log are correct assigned to existing folders 🙁
I checked the file locations over a admin connection: ADMIN:host\instance
http://msdn.microsoft.com/en-us/library/ms178068.aspx
http://claysql.blogspot.com/2009/02/receiving-error-18461-when-attempting.html
May 23, 2011 at 2:12 am
I executed this one:
use master
EXEC sp_change_users_login 'Report';
This script found a user, but what menas: "Check if there are Orphan users in system databases and fix them"
What exactly does the 'sqlagent100_msdb_upgrade.sql' <- is the code printed somewhere?
error is:
2011-05-23 10:15:21.69 spid5s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2011-05-23 10:15:21.69 spid5s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2011-05-23 10:15:21.69 spid5s Error: 574, Severity: 16, State: 0.
2011-05-23 10:15:21.69 spid5s CONFIG statement cannot be used inside a user transaction.
2011-05-23 10:15:21.69 spid5s Error: 912, Severity: 21, State: 2.
2011-05-23 10:15:21.69 spid5s Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 574, state 0, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2011-05-23 10:15:21.69 spid5s Error: 3417, Severity: 21, State: 3.
2011-05-23 10:15:21.69 spid5s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
May 23, 2011 at 4:48 am
In the following blog the it is described I have to search for "Orphan" users. I found one entry in the master DB.
The MS article to sp_change_users_login describes
"Report" Lists the users and corresponding security identifiers (SID) in the current database that are not linked to any login. user, login, and password must be NULL or not specified.
http://msdn.microsoft.com/de-de/library/ms174378.aspx
What means the following result? And How I can fix it?
USE master EXEC sp_change_users_login 'Report';
UserName / UserSID
qpt / 0xXXXXXX90B7E35446ADAE02CBAFXXXXXX
....
done:
USE master
EXEC sp_change_users_login 'Auto_Fix', 'qpt', NULL, 'PASSWORD';
EXEC sp_change_users_login 'Report'
May 23, 2011 at 7:11 am
The stored proc sp_change_users is the old proc used to achieve resolving orphaned users. As outlined in BOL and available via this link http://msdn.microsoft.com/en-us/library/ms174378.aspx this will be removed and you should use the alter user command instead.
MCT
MCITP Database Admin 2008
MCITP Database Admin 2008
MCITP Database Dev 2008
www.jnrit.com.au/Blog.aspx
May 23, 2011 at 7:29 am
We could at the moment not solve the problem. What is with a fresh installation. Can we uninstall the old MSSQL components, do a freh install of a named instance and attach the production database?
What I have to do if I attach a MSSQL 2005 database to a MSSQL 2008 instance? Do I have to do some post activities on the customer DB?
Viewing 15 posts - 1 through 15 (of 18 total)
You must be logged in to reply to this topic. Login to reply