This error could occur due to a variety of reasons, but primarily related to the Structured Query Language (SQL) Database (DB) connectivity between the publisher and the subscriber.
To resolve this issue, perform these steps:
- Verify that you have an lmhosts file on both the publisher and subscriber. The steps for this are outlined in Cisco CallManager: Subscriber Upgrade Fails / Unable to Find Updated Database.
- Verify that the SQL database is synchronized between the publisher and the subscriber by verifying the SQL subscription details. To verify this connectivity, refer to Reestablishing a Broken Cisco CallManager Cluster SQL Subscription with CallManager 3.0, 3.1 and 3.2.
- Ensure that the publisher and subscribers are running the same version with the service packs. If you find any inconsistency, take the necessary steps to bring them to the same version and service pack levels.
- Ensure that the SQLsvc passwords are the same on both the publisher and subscriber. To set a common password and private password phrase, try the adminutility. For more information on the adminutility, refer to these documents: