Error: 3411, Severity: 21, State: 1.

  • Hello

    I have a Windows 2003 R2 cluster with SQL 2005,

    I did a MS update over the weekend for all critical updates. On Node 1, SQL comes up fine on node 2 i get this error and SQL does not come up

     

    2006-07-20 17:39:06.49 Server      Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86)

     Apr 14 2006 01:12:25

     Copyright (c) 1988-2005 Microsoft Corporation

     Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

    2006-07-20 17:39:06.49 Server      (c) 2005 Microsoft Corporation.

    2006-07-20 17:39:06.49 Server      All rights reserved.

    2006-07-20 17:39:06.49 Server      Server process ID is 2352.

    2006-07-20 17:39:06.49 Server      Logging SQL Server messages in file 'S:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.

    2006-07-20 17:39:06.49 Server      This instance of SQL Server last reported using a process ID of 2452 at 7/20/2006 5:36:32 PM (local) 7/20/2006 9:36:32 PM (UTC). This is an informational message only; no user action is required.

    2006-07-20 17:39:06.49 Server      Registry startup parameters:

    2006-07-20 17:39:06.49 Server        -d S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf

    2006-07-20 17:39:06.49 Server        -e S:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG

    2006-07-20 17:39:06.49 Server        -l S:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf

    2006-07-20 17:39:06.49 Server      Error: 3411, Severity: 21, State: 1.

    2006-07-20 17:39:06.49 Server      Configuration block version 0 is not a valid version number. SQL Server is exiting. Restore the master database or reinstall.

    What gets me is it tells me to restore the Master DB, but the master DB is fine because it mounts on node 1.

    Any help would be good.

     

    DE

  • This was removed by the editor as SPAM

  • Maybe I am completely wrong but when I read "Configuration block version wrong" it looks like there is a wrong version of a .NET assembly, namely the Application Configuration block. I just cannot relate this to SQL server.

  • From an MSDN forum, Kevin Farlee says:

    The issue is that the backup app is not properly restoring master.  Most likely it failed to back up the file because it was locked by SQL at the time.

    In an earlier message, same thread, he says:

    The error message, "Configuration block version 0 is not a valid version number" tells us that the configuration page of the master database, which is one of the first pages read when we start up, is invalid.  It appears that for some reason, the master database is not being correctly restored by your DR process.

    So, regardless of whether master is attached, it is apparently corrupt.

    Restore it.

    Thank-you,
    David Russell
    Any Cloud, Any Database, Oracle since 1982

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply