Broken SQL replication between the primary and secondary Cisco Unity servers

[TCC_2]

Core Issue

In the Structured Query Language (SQL) Enterprise Manager, there is a red cross shown on the replication monitor. But, the remote databases can be seen from each Cisco Unity server. Also, the various databases and the corresponding database structure can be seen.

When there is an attempt to configure failover on the secondary Cisco Unity node or to run the Cisco Unity Failover Configuration wizard (FCW), the Configure Cisco Unity failover wizard ? [0x80043721]. Failed to configure SQL replication for Cisco Unity Failover? error message is received. When this error message appears, click OK.

Then, the Failed to find the SQL publication on the primary server. The SQL publication is required for Cisco Unity Failover. Disable all Cisco Unity replication using SQL Enterprise Manager and run this wizard again? error message appears. Click OK at this error message as well.

Resolution

In order to resolve this issue, complete these steps:

1. Verify whether Antivirus software currently runs.
   
   
2. Disable any Antivirus services, and re-run the Cisco Unity Failover Configuration wizard on both nodes.
   
   Refer to Configuring Cisco Unity Failover for more information.
   
   
3. Verify that the MSSQLSERVER and SQLSERVERAGENT services are set to log on as the Cisco Unity directory services account.
   
   
4. Verify that the SQL server registrations are set to the name of the servers, and not to local.
   
   
5. Verify that the SQL server version is 2000 - 8.00.760.
   
   Refer to How to identify your SQL Server version and edition for more information. This document translates to SQL Server 2000 SP3 or SP3a.
   
6. Delete the SQL server registrations and re-add them on the primary node. 
   
   
7. Re-run the Cisco Unity Failover Configuration wizard. Be sure to use the correct Cisco Unity Account (Unity Install) to run the FCW. 
   
   
8. Complete the Cisco Unity Failover Configuration wizard on the primary node and verify that the SQL publication is created. 
   
   
9. Delete and re-register the SQL server registrations and re-run the Cisco Unity Failover Configuration wizard on the secondary node.
   
   
10. Verify that SQL replication is functional.