Home Dashboard Directory Help
Search

Error: 537, Severity: 16, State: 3. - error during updating master DB from 2012 to 2012 SP1 by Webio


Status: 

Closed
 as Fixed Help for as Fixed


5
0
Sign in
to vote
Type: Bug
ID: 774535
Opened: 12/17/2012 2:50:48 AM
Access Restriction: Public
1
Workaround(s)
view
1
User(s) can reproduce this bug

Description

Hello,

I had situation latelly where update process where failing on updating master DB with msdb110_upgrade.sql script file.

Error:

2012-12-15 01:53:35.09 spid7s     Error: 537, Severity: 16, State: 3.
2012-12-15 01:53:35.09 spid7s     Invalid length parameter passed to the LEFT or SUBSTRING function.
2012-12-15 01:53:35.10 spid7s     Error: 912, Severity: 21, State: 2.
2012-12-15 01:53:35.10 spid7s     Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 537, state 3, 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.
2012-12-15 01:53:35.11 spid7s     Error: 3417, Severity: 21, State: 3.
Details
Sign in to post a comment.
Posted by Microsoft on 1/21/2013 at 5:30 PM
This issue will be addressed in future releases of SQL Server. Please report this issue to Microsoft Customer Support if you need this fix available in SQL 2012
Posted by Sethu Srinivasan on 12/18/2012 at 3:59 PM
Thanks for reporting this issue. We shall investigate this issue and keep you posted

Thanks
Sethu Srinivasan [MSFT]
SQL Server
http://blogs.msdn.com/sqlagent
Sign in to post a workaround.
Posted by Brandon.Tucker on 9/4/2013 at 10:35 AM
See http://social.msdn.microsoft.com/Forums/sqlserver/en-US/163963c0-5118-40e4-8f08-1abfdc898f28/script-level-upgrade-for-database-master-failed-because-upgrade-step-msdb110upgradesql for more information. This occurs when non-master database files have a logical name of "master".