SQL Server Developer Center > SQL Server Forums > SQL Server Database Engine > SQL Server Active Active Failover Cluster w/ transaction Replication, Registry Resource will not hold SQL Server Parameter Values
Ask a questionAsk a question
 

QuestionSQL Server Active Active Failover Cluster w/ transaction Replication, Registry Resource will not hold SQL Server Parameter Values

  • Wednesday, November 04, 2009 2:17 PMFrank Ivey Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I have been trying to resolve this issue for the past day now.

    Everytime I create a failover sql server 2008 cluster node

    The resource group is always missing the SQL Server and SQL Server Agent Resources.  I go ahead and recreate them based on the Microsoft Suggestion http://support.microsoft.com/default.aspx/kb/883732
    But as soon I create them and restart the server to see if the Parameters are saved, they get don't get saved and I have to recreate them again.  I need these resources in order to start my cluster node. It is only happening on 1 server.

    My server environment is as follows:

    2 Windows Server 2008 Server
    32gb Ram
    500gb disk drives
    SQL Server 2008 Standard
    Windows Server 2008 Failover Cluster
    SQL Server 2008 Failover Cluster - 1 Failover cluster group not working properly because Resource Parameter Values will not stay persistent after reboot.

    I get the following error:

    Event:19019

    [sqsrvres] GetRegKeyAccessMask: Could not get registry access mask for registry key Software\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\Cluster (status 2)).

    Please help!!!!!!




    Network Analyst

All Replies

  • Wednesday, November 04, 2009 2:26 PMSean Gallardy Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Frank,

    Did you by chance change the name of one of the nodes in the cluster group?

    -Sean
  • Wednesday, November 04, 2009 3:10 PMFrank Ivey Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Both nodes in the cluster group have separate distinct names, their names were already given by the time i got my hands on the implementation
    Network Analyst