none
SQL 2008 R2 cluster install SP1 error: 5184 severity: 16, state: 2 RRS feed

  • Question

  • Hi,

    I have a SQL 2008 R2 cluster with 3 nodes and 2 SQL instances. I install on the third node on one instance (which is not active) SP1 for sql 2008 R2. After installing I try to bring this instance active on this node. The instance comes online for a few second and fails then. In the sql server errorlog I can see the following errors:

    ERRORLOG:

    2012-07-12 15:49:36.20 Logon       Error: 18401, Severity: 14, State: 1.
    2012-07-12 15:49:36.20 Logon       Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. [CLIENT: 192.168.141.27]
    2012-07-12 15:49:37.39 spid7s      Signing sps ...
    2012-07-12 15:49:37.39 spid7s      Dropping existing Agent certificate ...
    2012-07-12 15:49:37.40 spid7s      DBCC TRACEON 4606, server process ID (SPID) 7. This is an informational message only; no user action is required.
    2012-07-12 15:49:37.40 spid7s      DBCC execution completed. If DBCC printed error messages, contact your system administrator.
    2012-07-12 15:49:37.65 spid7s      DBCC TRACEOFF 4606, server process ID (SPID) 7. This is an informational message only; no user action is required.
    2012-07-12 15:49:37.65 spid7s      DBCC execution completed. If DBCC printed error messages, contact your system administrator.
    2012-07-12 15:49:37.73 spid7s      Error: 5184, Severity: 16, State: 2.
    2012-07-12 15:49:37.73 spid7s      Cannot use file 'E:\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\temp_MS_AgentSigningCertificate_database.mdf' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the Sql Server does not have a dependency on it.
    2012-07-12 15:49:38.12 spid7s      Error: 1802, Severity: 16, State: 1.
    2012-07-12 15:49:38.12 spid7s      CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
    2012-07-12 15:49:38.14 spid7s      Error: 912, Severity: 21, State: 2.
    2012-07-12 15:49:38.14 spid7s      Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 598, state 1, severity 25. 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-07-12 15:49:38.15 spid7s      Error: 3417, Severity: 21, State: 3.
    2012-07-12 15:49:38.15 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.
    2012-07-12 15:49:38.15 spid7s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
    2012-07-12 15:49:38.26 Logon       Error: 18401, Severity: 14, State: 1.
    2012-07-12 15:49:38.26 Logon       Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. [CLIENT: 192.168.141.27]
    2012-07-12 15:49:38.32 Server      The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/SQLSTD.Reinhard.local ] for the SQL Server service.
    2012-07-12 15:49:38.32 Server      The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/SQLSTD.Reinhard.local:1433 ] for the SQL Server service.

    How can I solve this problem?

    Thank you for any reply,

    Reinhard

    Thursday, July 12, 2012 2:18 PM

Answers

  • Hi Reinhard Greuner,

    In cluster environment, you can keep the database files on the drives on which SQL Server resource has dependencies. These must be shared drivers. Please verify that the sql server cluster resource has the drive E as a dependency? If it does not, you will need to offline SQL Server, add it, and online. You need to go to cluster admin. Right Click and Go to Properties of SQL Server resource. to dependencies tab and add the disk.

    For more information, please refer to How to create databases or change disk file locations on a shared cluster drive on which SQL Server was not originally installed.

    According to the error message, seems related to MS_AgentSigningCertificate for clustered server. The error maybe caused by the path cannot be found. One of the situations could be that the path is invalid. For the solution please refer to the Resolution part from this blog

    Please follow the step-by- step in above blog, if any problem please let me know.

     


    Regards, Amber zhang

    Friday, July 13, 2012 6:39 AM
    Moderator
  • Hi Amber,

    thank you for your reply.

    The problem was the dependencies. The sql server resource didn't have the disk E: as a dependency.

    regards Reinhard

    Friday, July 13, 2012 9:49 AM

All replies

  • Hi Reinhard Greuner,

    In cluster environment, you can keep the database files on the drives on which SQL Server resource has dependencies. These must be shared drivers. Please verify that the sql server cluster resource has the drive E as a dependency? If it does not, you will need to offline SQL Server, add it, and online. You need to go to cluster admin. Right Click and Go to Properties of SQL Server resource. to dependencies tab and add the disk.

    For more information, please refer to How to create databases or change disk file locations on a shared cluster drive on which SQL Server was not originally installed.

    According to the error message, seems related to MS_AgentSigningCertificate for clustered server. The error maybe caused by the path cannot be found. One of the situations could be that the path is invalid. For the solution please refer to the Resolution part from this blog

    Please follow the step-by- step in above blog, if any problem please let me know.

     


    Regards, Amber zhang

    Friday, July 13, 2012 6:39 AM
    Moderator
  • Hi Amber,

    thank you for your reply.

    The problem was the dependencies. The sql server resource didn't have the disk E: as a dependency.

    regards Reinhard

    Friday, July 13, 2012 9:49 AM