SQL Server 2005 Setup Failing to Install on Cluster with Unexpected Failure while Performing the SCC checks


We have observed a number of cases where the installation of the SQL server 2005 instance on the cluster fails with the following unexpected Failure Error Message while performing SCC checks.


ERROR MESSAGE:


====================


There is unexpected failure.


MSGID 50000


In order to troubleshoot the issue we followed the following steps


1)       We checked the Setup Bootstraps Logs which are located in c:\Program files\Microsoft sql server\90\Setup BootStrap\LOGS\Files.


2)       We checked the Core(Local).log and found the following error was reported in the error log


 


<Func Name=’PerformDetections’>


1


Loaded DLL:C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlsval.dll Version:2005.90.3042.0


Failed to enumerate disks.


HRESULT: 0x80070015


The device is not ready.


Error: Action “InvokeSqlSetupDllAction” threw an exception during execution.  Error information reported during run:


  Source File Name: datastore\clusterinfocollector.cpp


Compiler Timestamp: Sat Oct  7 09:43:48 2006


     Function Name: ClusterInfoCollector::collectClusterGroups


Source Line Number: 391


———————————————————-


Failed to determine disk information


        Source File Name: datastore\clusterinfocollector.cpp


      Compiler Timestamp: Sat Oct  7 09:43:48 2006


           Function Name: ClusterInfoCollector::collectClusterGroups


      Source Line Number: 390


      ———————————————————-


      Enum*Disks() returned : 2147942421


WinException : -2147024875


        Error Code: -2147024875


Windows Error Text: The device is not ready.


 


  Source File Name: datastore\clusterinfocollector.cpp


Compiler Timestamp: Sat Oct  7 09:43:48 2006


     Function Name: ClusterInfoCollector::collectClusterGroups


Source Line Number: 390


 


Error: Failed to add file :”C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0020_WPSQL1_.NET Framework 2.0.log” to cab file : “C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0020.cab” Error Code : 2


Error: Failed to add file :”C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0020_WPSQL1_SCC.log” to cab file : “C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0020.cab” Error Code : 32


Running: UploadDrWatsonLogAction at: 2008/8/30 10:16:17


Message pump returning: 2147942421


 


 


3)       From the above error log it was clear that setup.exe was not able to query the information about the Physical Disks.


 


Failed to enumerate disks.


HRESULT: 0x80070015


The device is not ready.


Error: Action “InvokeSqlSetupDllAction” threw an exception during execution.  Error information reported during run:


  Source File Name: datastore\clusterinfocollector.cpp


Compiler Timestamp: Sat Oct  7 09:43:48 2006


     Function Name: ClusterInfoCollector::collectClusterGroups


Source Line Number: 391


———————————————————-


Failed to determine disk information


 


Cause
======

above error is reported when either some of the physical Disk resource is Offline or is not Online from the Active Node where setup was run.


 


Resolution
========

So in order to resolve the issue we need to ensure the Disk Resource is Online from the Node from which we are installing the SQL server instance in the cluster.


Once the Disk resource is brought online, the SQL server 2005 installation runs fine on the cluster


Parikshit Savjani
SE, Microsoft SQL Server

Comments (1)

  1. Esoteric says:

    Here’s a quick checklist before you install an instance of SQL Server on a failover cluster; or any service