At the first instance the error is clear that some problem with SQL resource that was allocated to the Cluster resource.

Just a background on SQL Server Failover Clustering, that the server cluster consists of a failover cluster instance that runs under Cluster Services (MSCS). The instance of SQL Server might be hosted by Microsoft MSCS-based nodes that provide the Microsoft Server Cluster, say if  problems exist on the nodes that host the server cluster, those problems may manifest themselves as issues with your failover cluster instance.

So to investigate further on the errors and issues you migh follow the steps defined below::

  1. Hardware: Review Microsoft Windows system event logs.
  2. Operating system: Review Windows system and application event logs.
  3. Network: Review Windows system and application event logs. Verify the current configuration as per KBA Recommended Private "Heartbeat" Configuration on a Cluster Server.
  4. Security: Review Windows application and security event logs.
  5. MSCS: Review Windows system, application event, and cluster logs.
  6. SQL Server: Troubleshoot as normal after the hardware, operating system, network, security, and MSCS foundations are verified to be problem-free.

Further to this Microsoft documentation refers clearly that if there is any usage of  extended stored procedures with a failover clustering configuration, all extended stored procedures must be installed on a SQL Server-dependent cluster disk. Doing so ensures that when a node fails over, the extended stored procedures can still be used. If the extended stored procedures use COM components, the administrator must register the COM components on each node of the cluster. The information for loading and executing COM components must be in the registry of the active node in order for the components to be created. Otherwise, the information remains in the registry of the computer on which the COM components were first registered.

Coming back to the problem by default you need to setup a SQL Server 2008 failover cluster on a subnet, this subnet only contains IPV6 addresses that are link-local type. Also it is a pre-requisite to SQL Server 2008 Failover Cluster on a Windows Server 2008 environment is SLIPSTREAM (I will cover this on seperate blog post)!. There have been a lot of changes regarding clustering between Windows Server 2003 and Windows Server 2008. It took quite a lot of effort for us to build a cluster in Windows Server 2003 - from making sure that the server hardware for all nodes are cluster-compatible to creating resource groups. Microsoft has redefined clustering with Windows Server 2008, making it simpler and easier to implement.

TO resolve the issues the quick search of MS KBA articles helped to retrieve FIX: SQL Server 2008 clustered resources cannot come online if you have enabled the FILESTREAM feature for Transact-SQL access link to supress the issue.