UpGrade failed 9.3.4294 (2005 SP3 PatchSet 9) to 10.50.1600.1.

Question

Hi, I've tried an UpGrade from 9.3.4294 (2005 SP3 PatchSet 9) to 10.50.1600.1. (SAP media ID 51039339)
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:
...Binnsqlservr.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 tpzsqp01SAPQPT -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 tpzsqp01SAPQPT -E -A -Q"ALTER LOGIN sa WITH PASS
WORD = 'xxx' UNLOCK;"
But I'm not able to connect to the server via TCP
C:Windowssystem32>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?! 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.
Error messages by setup 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 FilesMicrosoft SQL Server100Setup BootstrapLog20110520_164101Detail.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 FilesMicrosoft SQL Server100Setup BootstrapLog20110520_164101Detail.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 FilesMicrosoft SQL Server100Setup BootstrapLog20110520_164101Detail.txt
Edited by: René Schulz on May 24, 2011 9:23 AM

Answer 1

for further ideas with trace flag -T3601; the upgrade script seems to have a problem with RECONFIGURE ??? :
/* DMF Post-upgrade steps */
-- >>> CTP5 -> CTP6 Upgrade
-- Restoring previously saved data and converting TargetSets to ObjectSets
IF (OBJECT_ID('dbo.dmf_upgrade', 'U') IS NOT NULL)
BEGIN
BEGIN TRANSACTION
-- Restore policies
SET IDENTITY_INSERT dbo.syspolicy_policies_internal ON
INSERT dbo.syspolicy_policies_internal (policy_id,name,condition_id,root_condition_id,date_created,execution_mode,policy_category_id,schedule_uid,description,help_text,help_link,is_enabled,job_id,created_by,modified_by,date_modified)
SELECT policy_id,name,condition_id,root_condition_id,date_created,execution_mode,policy_category_id,schedule_uid,description,help_text,help_link,is_enabled,job_id,created_by,modified_by,date_modified
FROM msdb.dbo.tmp_syspolicy_policies_internal
SET IDENTITY_INSERT dbo.syspolicy_policies_internal OFF
-- Restore Health state
SET IDENTITY_INSERT dbo.syspolicy_system_health_state_internal ON
INSERT dbo.syspolicy_system_health_state_internal (health_state_id,policy_id,last_run_date,target_query_expression_with_id,target_query_expression,result)
SELECT * FROM msdb.dbo.tmp_syspolicy_system_health_state_internal
SET IDENTITY_INSERT dbo.syspolicy_system_health_state_internal OFF
-- Restore Execution history
SET IDENTITY_INSERT dbo.syspolicy_policy_execution_history_internal ON
INSERT dbo.syspolicy_policy_execution_history_internal (history_id,policy_id,start_date,end_date,result,is_full_run,exception_message,exception)
SELECT * FROM msdb.dbo.tmp_syspolicy_policy_execution_history_internal
SET IDENTITY_INSERT dbo.syspolicy_policy_execution_history_internal OFF
SET IDENTITY_INSERT dbo.syspolicy_policy_execution_history_details_internal ON
INSERT dbo.syspolicy_policy_execution_history_details_internal (detail_id,history_id,target_query_expression,target_query...
2011-05-23 14:03:53.29 spid7s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2011-05-23 14:03:53.29 spid7s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2011-05-23 14:03:53.30 spid7s Error: 574, Severity: 16, State: 0.
2011-05-23 14:03:53.30 spid7s CONFIG statement cannot be used inside a user transaction.
2011-05-23 14:03:53.30 spid7s Error: 912, Severity: 21, State: 2.