Share via

There was an error to lookup cluster groups

Abouzar Asgari 20 Reputation points
2024-03-06T06:42:44.0633333+00:00

Hi

During installation another node to fail over cluster ,after select SQL Sever Instance Name in step Cluster Node Configuration and click Next button,installation crashed and not responding ,then  raise error

There was an error to lookup cluster groups. Error: There was a failure to call cluster code from a provider. Exception message: Critical error . Status code: 4106. Description: Critical error

 

i saw installation log file , i found this error:

 

(01) 2024-02-28 11:19:46 Slp: Running Action: RunScenarioGlobalRules

(01) 2024-02-28 11:19:46 Slp: Running in UI mode, unattended rules execution skipped.

(01) 2024-02-28 11:19:46 Slp: Completed Action: RunScenarioGlobalRules, returned True

(01) 2024-02-28 11:19:46 Slp: ----------------------------------------------------------------------

(01) 2024-02-28 11:19:46 Slp: Running Action: DiscoverClusterData

(01) 2024-02-28 11:19:47 Slp: There was an issue determining the cluster debugging information. Setup will continue.

(01) 2024-02-28 11:19:47 Slp: The following is an exception stack listing the exceptions in outermost to innermost order

(01) 2024-02-28 11:19:47 Slp: Inner exceptions are being indented

(01) 2024-02-28 11:19:47 Slp:

(01) 2024-02-28 11:19:47 Slp: Exception type: System.InvalidOperationException

(01) 2024-02-28 11:19:47 Slp: Message:

(01) 2024-02-28 11:19:47 Slp: There was an error generating the XML document.

(01) 2024-02-28 11:19:47 Slp: HResult : 0x80131509

(01) 2024-02-28 11:19:47 Slp: Stack:

(01) 2024-02-28 11:19:47 Slp: at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)

(01) 2024-02-28 11:19:47 Slp: at System.Xml.Serialization.XmlSerializer.Serialize(Stream stream, Object o, XmlSerializerNamespaces namespaces)

(01) 2024-02-28 11:19:47 Slp: at Microsoft.SqlServer.Configuration.ClusterConfiguration.DiscoverClusterDataAction.ExecuteAction(String actionId)

(01) 2024-02-28 11:19:47 Slp: Inner exception type: Microsoft.SqlServer.Configuration.Cluster.ClusterGroupsLookupException

(01) 2024-02-28 11:19:47 Slp: Message:

(01) 2024-02-28 11:19:47 Slp: There was an error to lookup cluster groups. Error: There was a failure to call cluster code from a provider. Exception message: Critical error . Status code: 4106. Description: Critical error

(01) 2024-02-28 11:19:47 Slp: .

(01) 2024-02-28 11:19:47 Slp: HResult : 0x86d8000e

(01) 2024-02-28 11:19:47 Slp: FacilityCode : 1752 (6d8)

(01) 2024-02-28 11:19:47 Slp: ErrorCode : 14 (000e)

(01) 2024-02-28 11:19:47 Slp: Data:

(01) 2024-02-28 11:19:47 Slp: errorMessage = There was a failure to call cluster code from a provider. Exception message: Critical error . Status code: 4106. Description: Critical error

.

(01) 2024-02-28 11:19:47 Slp: WatsonData = Microsoft.SqlServer.Configuration.Cluster.ClusterGroupsLookupException@14

(01) 2024-02-28 11:19:47 Slp: Stack:

(01) 2024-02-28 11:19:47 Slp: at Microsoft.SqlServer.Configuration.Cluster.WindowsCluster.get_Groups()

(01) 2024-02-28 11:19:47 Slp: at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriter1.Write113_WindowsCluster(String n, String ns, WindowsCluster o, Boolean isNullable, Boolean needType)

(01) 2024-02-28 11:19:47 Slp: at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriter1.Write237_WindowsCluster(Object o)

(01) 2024-02-28 11:19:47 Slp: Inner exception type: Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException

(01) 2024-02-28 11:19:47 Slp: Message:

(01) 2024-02-28 11:19:47 Slp: There was a failure to call cluster code from a provider. Exception message: Critical error . Status code: 4106. Description: Critical error

(01) 2024-02-28 11:19:47 Slp: .

(01) 2024-02-28 11:19:47 Slp: HResult : 0x86d70002

(01) 2024-02-28 11:19:47 Slp: FacilityCode : 1751 (6d7)

(01) 2024-02-28 11:19:47 Slp: ErrorCode : 2 (0002)

(01) 2024-02-28 11:19:47 Slp: Data:

(01) 2024-02-28 11:19:47 Slp: ExceptionMessage = Critical error

(01) 2024-02-28 11:19:47 Slp: StatusCode = 4106

(01) 2024-02-28 11:19:47 Slp: Description = Critical error

(01) 2024-02-28 11:19:47 Slp: WatsonData = Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException@2

(01) 2024-02-28 11:19:47 Slp: Stack:

(01) 2024-02-28 11:19:47 Slp: at Microsoft.SqlServer.Configuration.Cluster.WMICollectionWrapper.WmiEnumeratorWrapper.MoveNext()

(01) 2024-02-28 11:19:47 Slp: at Microsoft.SqlServer.Configuration.Cluster.ClusterProvider.<get_Groups>d__11.MoveNext()

(01) 2024-02-28 11:19:47 Slp: at Microsoft.SqlServer.Configuration.Cluster.WindowsCluster.get_Groups()

(01) 2024-02-28 11:19:47 Slp: Inner exception type: System.Management.ManagementException

(01) 2024-02-28 11:19:47 Slp: Message:

(01) 2024-02-28 11:19:47 Slp: Critical error

(01) 2024-02-28 11:19:47 Slp: HResult : 0x80131501

(01) 2024-02-28 11:19:47 Slp: Data:

(01) 2024-02-28 11:19:47 Slp: WmiErrorCode = CriticalError

(01) 2024-02-28 11:19:47 Slp: WatsonData = CriticalError@4106

(01) 2024-02-28 11:19:47 Slp: Description = Critical error

(01) 2024-02-28 11:19:47 Slp: ErrorType = 2

(01) 2024-02-28 11:19:47 Slp: Operation = ExecQuery

(01) 2024-02-28 11:19:47 Slp: ParameterInfo = select * from MSCluster_ClusterToResourceGroup where __CLASS = "MSCluster_ClusterToResourceGroup"

(01) 2024-02-28 11:19:47 Slp: ProviderName = WinMgmt

(01) 2024-02-28 11:19:47 Slp: StatusCode = 4106

(01) 2024-02-28 11:19:47 Slp: Stack:

(01) 2024-02-28 11:19:47 Slp: at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)

(01) 2024-02-28 11:19:47 Slp: at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()

(01) 2024-02-28 11:19:47 Slp: at Microsoft.SqlServer.Configuration.Cluster.WMICollectionWrapper.WmiEnumeratorWrapper.MoveNext()

(01) 2024-02-28 11:19:47 Slp: Completed Action: DiscoverClusterData, returned True

(01) 2024-02-28 11:19:47 Slp: Completed Action: ExecuteGlobalRulesWorkflow, returned True

 

in the Cluster log file i found this error:

mscs::TopologyPersister::TryGetNetworkPrivateProperties: (2)' because of 'OpenSubKey(Parameters) failed.'

 

first of all  I thought my Cluster lack of enough permission but after talked with network administrator ,I found cluster and i have very high permission .

there is another problem with this issues

when i run this command in powershell ,i got error

get-wmiobject mscluster_resourcegroup  -namespace "ROOT\MSCluster

error

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,697 questions
0 comments
Accepted answer
  1. LiHongMSFT-4306 26,791 Reputation points
    2024-03-07T06:14:29.5066667+00:00

    Hi @Abouzar Asgari

    Error: There was a failure to call cluster code from a provider. Exception message: Critical error . Status code: 4106. Description: Critical error

    This error typically occurs during cluster operations and can have various causes. Here are some steps you can take to troubleshoot and resolve the issue:

    Check Permissions:

    • Ensure that the account used to install SQL Server has the correct permissions within the cluster.
    • Specifically, grant the “Create Computer Objects” permission to the Cluster Name Object (CNO) in Active Directory.
    • Locate the “Computer” container, add the CNO, and select the “Computers” option in the “Object Types” window.

    Review Event Logs:

    • Look at the event logs for more detailed information about this error.
    • Insufficient permissions or other issues may be logged there.

    Resource Conflicts:

    • The error message suggests that property values for the resource are in conflict with those of its dependent resource(s).
    • Verify that resource properties (such as IP addresses, service accounts, and disks) are correctly configured and consistent across related resources.

    Cluster Group Ownership:

    • The operation may fail if the specified cluster node is not the owner of the resource or if it’s not a possible owner.
    • Check the cluster group ownership settings and ensure they align with your intended configuration.

    Downtime Considerations:

    • When installing a new instance, consider whether it’s best to do so on the secondary passive node (Node B) or on a node hosting all cluster resources.
    • Installing on Node B may minimize downtime for existing production instances.
    • However, be cautious and plan accordingly to avoid service interruptions.

    Remember that diagnosing cluster issues can be complex, especially in production environments. If possible, consult with your system administrator or a database specialist to address this critical error effectively.

    Best regards,

    Cosmog Hong

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.
    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.