SQL SERVER – Unable to Install Service Pack in Cluster – There was an Error to Lookup Cluster Resource Types

SQL SERVER - Unable to Install Service Pack in Cluster - There was an Error to Lookup Cluster Resource Types SQL-Cluster Learning never stops for me with SQL Server. Even though I have written articles to solve many issues, I still get pinged from various clients and I find one new thing every day. In this blog post we will learn how to fix the error related to installing the service pack in the cluster.

The other day, while my client was trying to apply service pack for SQL Server and it was failing with an error. When I asked them to share the Detail.txt, I could find below exception which was causing failures.

The following is an exception stack listing the exceptions in outermost to innermost order

Inner exceptions are being indented

ErrorType = 2
Operation = GetObject
ParameterInfo = MSCluster_ResourceType.Name=”Double-Take Source Connection”
ProviderName = MS_CLUSTER_PROVIDER
StatusCode = 4104
Stack:

When I searched on the internet, I found that this was caused to another person in the world due to “Double-Take Source Connection”. We can also see that in our stack.

WORKAROUND/SOLUTION

I gave the option to the customer to contact either Microsoft or Double take software vendor to find the cause of the issue. But they informed that they are not using double-take and it was installed for testing purpose. There was no resource of double-take in their cluster.

Since they were OK to get rid of double-take, we ran below command.

Remove-ClusterResourceType -name “Double-Take Source Connection”

This deleted the “Double-Take Source Connection” cluster resource type, now it was no longer listed using below command

Get-ClusterResourceType

Once we removed above resource type, they were able to install the service pack successfully.

Reference: Pinal Dave (http://blog.SQLAuthority.com)

, , ,
Previous Post
SQL SERVER – Unable to recycle Errorlog – sp_cycle_errorlog – OS error 1392
Next Post
SQL SERVER – FIX: Error: 913, Severity: 16 – Could Not Find Database ID 3. Database May Not be Activated Yet or May be in Transition – SQL Service

Related Posts

Leave a Reply

Menu