Please Help I have spent 2 full days trying to install SQL Server 2000 Failover Clustering on a MS Windows 2003 Enterprise Edition Server, but the installation will not start the SQL cluster resources and complete. Firstly, my MS Clustering service is installed and working. It is a 2-node cluster. Both nodes have MS Windows 2003 Enterprise Edition SP1 installed. The only cluster resource I have defined is a physical Disk, which is connected via SAN to a Fibre Channel Shared Disk Array. Both nodes can see the shared disk and the cluster groups failover successfully between each node. There are no problems reported in my event viewer or cluster log. Moving on to the SQL Server 2000 Installation, I am using SQL Server 2000 Enterprise Edition, May 2003 (SP2)*. I have followed the microsoft guide (Chapter 12 - Failover Clustering) and made sure the preinstall requirements are met (Netbios disabled on private network, services stopped/started, MSDTC cluster resource added). *note: I recieve an error which tells me that SQL Server 2000 SP2 is not compatible with this version of Windows, and I must apply SP3 after installation. I then run the Database Server installation and choose the neccessary options for a single-instance clustered database (virtual server, name, IP, typical install....). I am using a domain user with local administrative permissions. The installation gets as far as checking the cluster nodes, then (says it) installs SQL Server Fulltext and then finally errors when creating virtual cluster resources. The installer then rolls back. The following error in the event log is the only event I get of "Error" type: _____________________________________________________ Event Type:Error Event Source:ClusSvc Event Category:Failover Mgr Event ID:1069 Date:08/09/2005 Time:17:48:43 User:N/A ComputerR-CC-DBCLUST1 Description: Cluster resource 'SQL Server Fulltext' in Resource Group 'Group 0' failed. For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp. ______________________________________________________ Example of cluster log (node1): ______________________________________________________ 000005f8.000007f0::2005/09/08-09:13:20.142 INFO [FM] FmpPropagateGroupState: Group 7264aab2-e8fc-4952-83d0-ab22e9887fa0 state = 0, persistent state = 0 00000860.00000cd8::2005/09/08-09:13:20.173 INFO [RM] RmpSetResourceStatus, Posting state 4 notification for resource <SQL Server Fulltext (STORM_MTP)> 000005f8.0000086c::2005/09/08-09:13:20.173 INFO [FM] NotifyCallBackRoutine: enqueuing event 000005f8.0000086c::2005/09/08-09:13:20.173 INFO [FM] Calling RmNotifyChanges in monitor 0860. 000005f8.000007ec::2005/09/08-09:13:20.173 INFO [CP] CppResourceNotify for resource SQL Server Fulltext (STORM_MTP) 000005f8.000007ec::2005/09/08-09:13:20.173 INFO [FM] FmpRmDoHandleCriticalResourceStateChange: call InterlockedDecrement on gdwQuoBlockingResources, Resource 10d6663d-d2e4-4845-b6c9-28c4d9be12a4 000005f8.000007f0::2005/09/08-09:13:20.173 WARN [FM] FmpHandleResourceTransition: Resource Name = 10d6663d-d2e4-4845-b6c9-28c4d9be12a4 [SQL Server Fulltext (STORM_MTP)] old state=129 new state=4 000005f8.000007f0::2005/09/08-09:13:20.173 WARN [FM] FmpHandleResourceTransition: Resource failed, post a work item 00000860.00000cd8::2005/09/08-09:13:20.173 ERR Microsoft Search Service Instance <SQL Server Fulltext (STORM_MTP)>: An error occurred during the online operation for instance <SQL Server Fulltext (STORM_MTP)>: 80070002 - The system cannot find the file specified. ____________________________________________________ Example of cluster log (node2): ____________________________________________________ ____________________________________________________ To resolve this, I have tried: 0. Following the steps for this event in the help and support center. 1. Installing a local (non clustered) database and upgrading it to a clustered database. - the same problem exisits 2. Installing a local (non clustered) database and then installing a new clustered database as a seperate named instance - the same problem exisits 3. Installing a local (non clustered) database, installing SP3 and upgrading it to a clustered database. - the same problem exisits 4. Installing a local (non clustered) database, installing SP3 and then installing a new clustered database as a seperate named instance - the same problem exisits 5. Installing a local (non clustered) database, installing SP4 and upgrading it to a clustered database. - the same problem exisits 6. Installing a local (non clustered) database, installing SP4 and then installing a new clustered database as a seperate named instance - the same problem exisits 7. Installing SQL Server Fulltext service from SP3 prior to install. - the same problem exisits 8. Selecting only node 1 of the cluster to install to (not selecting node 2). 9. Evicting node 2 and then installing solely to node 1. 10. Rebuilding the Cluster Service 11. Reinstalling MSDTC in it's own cluster group I have not (yet) tried: 1. Uninstalling Windows Server 2003 Ent Ed SP1, then repeat previous steps 2. Rebuilding Windows. To conclude, all of my hardware is HCL certified: HP MSA 1000 packaged cluster (2 x ProLiant DL380 G4). I am now getting worried that SQL Server might not be compatible with my shared disk driver. Could this be possible? Any solutions would be greatly appreciated. Thank you in advance.