Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
The publisher server is not visible on the Cisco CallManager Serviceability Control Center page, and the "Connection to server could not be established" error message appears
This issue occurs due to Structured Query Language (SQL) database replication issues between the Cisco CallManager servers in the cluster. The replication of the SQL database is a core function of the Cisco CallManager clusters. The server with the master copy of the Cisco CallManager database is called the publisher, while the servers that replicate the database are called subscribers. The subscriber server consistently polls the publisher server for any new changes to the publisher database. If any new changes are made, the subscriber performs a pull subscription in order to receive the most recent changes to the database.
In order to resolve this issue and correct the database replication, complete these steps:
If issues occur with Cisco CallManager failover or if SQL replication errors appear in the application event log, check for the DBLHelper.exe file first. This file is located in the c:\program files\cisco\bin directory. Make sure the latest DBLHelper file is in this location. If the file is not currently on the system, open a case with Cisco Technical Support with the TAC Service Request Tool and detail a broken SQL subscription.