Summary:
IME and SQL 2000 are initially installed on a Microsoft Cluster and working perfectly. After changing the virtual IP address of the SQL Cluster, IME can no longer connect to the database if and only if the SQL Cluster Group and the IME Cluster Group are on different cluster nodes.

Symptom:
In the Event Viewer's Application Log, there will be numerous "Unable to connect to database" errors from IME.

When starting up the IME Cluster Group on the node not running the SQL Cluster Group, the IME database dependent cluster resources* will remain in an "Online Pending" state indefinitely. The remaining IME cluster resources will successfully startup and be brought "Online". Moving the IME Cluster Group to the same node as the SQL Cluster Group will fix this condition, as will moving the SQL Cluster Group to the IME Cluster Group.

* - IMEAccountManager, IMEController, IMEMailListManager, IMEPackageManager, IMEDeliveryManager, IMECustomObjectManager, IMETaskManager require a connection to the SQL Database.

Detailed Information:
SQL 2000 Database should be IP independent, but there is a single configuration in a SQL 2000 Cluster that is not. Unfortunately, this is not exposed in the UI, only in the Windows Registry.

This information is detailed in Microsoft Knowledge Base Article 319578.

Resolution:
1. Take the SQL Cluster Group offline.
2. Start Menu, Run.. , regedt32.
3. Follow the instructions in the Microsoft Knowledge Base Article, or update the following registry value to the correct IP address:

HKLM\Software\Microsoft\Microsoft SQL Server\Instance Name\Cluster\ClusterIpAddr

You MUST use regedt32.exe (not regedit.exe) to edit this value, as this is a REG_MULTI_SZ data type (Unicode), not REG_SZ.

Original Author: JCHOI
Original Submitter: ACUNY
Keywords: sql cluster ip address ime IME ID#29997