SQL SERVER – Unable to Apply Security Patch – The setup has encountered an unexpected error in datastore

SQL
2 Comments

One of my clients reported that he is trying to apply security patch for SQL Server clustered instance and it was failing. Since this is SQL 2005 instance, there is no official support available from Microsoft at this point. So, they contacted me. I asked to share setup logs and found a very interesting note.

SQL9_Hotfix_KB2494120_sqlrun_sql.msp.log

MSI (s) (4C!64) [23:29:00:069]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (4C!64) [23:29:00:069]: Product: Microsoft SQL Server 2005 (64-bit) — Error 29527. The setup has encountered an unexpected error in datastore. The action is SetInstanceProperty. The error is : Source File Name: datastore\clusterinfocollector.cpp
Function Name: ClusterInfoCollector::collectClusterGroups
Source Line Number: 391
———————————————————-
Failed to determine disk information
Source File Name: datastore\clusterinfocollector.cpp
Compiler Timestamp: Tue Sep 21 15:48:22 2010
Function Name: ClusterInfoCollector::collectClusterGroups
Source Line Number: 390
———————————————————-
Enum*Disks() returned : 2147943568

Interesting message is:  “Failed to determine disk information”

I am not an expert at looking at these logs, but we can clearly see that the setup was failing at getting the disk information. After looking at above error, I asked the DBA to check windows failover cluster manager. He found that there was one disk resource in the available storage that was in the failed state. We can conclude that because of this, the setup was failing.

SQL SERVER - Unable to Apply Security Patch - The setup has encountered an unexpected error in datastore patch-01

WORKAORUND / SOLUTION

At this point, we had two choices:

  • Bring the disk resource online
  • If it can’t come online due to hardware change, then remove it.

They were not able to bring disk online so finally they deleted it. Once they have done that, the setup succeeded for database engine and it was happiness everywhere.

Have you ever encountered an issue with the SQL setup was failing because of another resource?

Reference: Pinal Dave (https://blog.sqlauthority.com)

, , ,
Previous Post
SQL SERVER – Fix – Error 15240, Severity: 16, State: 2 – Cannot write into file
Next Post
SQL SERVER – AlwaysOn AG (Availability Group) and TDE Error – Please Create a Master Key

Related Posts

2 Comments. Leave new

  • Another nice addition to knowledge base. That’s why it is said that a SQL DBA must have knowledge about windows cluster as well. Thanks Pinal for sharing this.

    Reply

Leave a Reply

Menu