Cisco CM (Subscriber Server) Can not reach Publisher

[megaco]

Guys I have the following configuration.

2 servers (x.x.x.191 & x.x.x.190)

The .191 server is the subscriber and active cm
The .190 server is the publisher and the standby cm

The cluster replication works if you make a change on the backup CM the entry appears in the active cm (subcriber)

If you try to add a call forward on a phone via the softkey you get an error in the LCD saying database unreachable. If you try to change details in the active CM you get a message:

Cannot update data because the publisher is not
available. Please try again later. (58)

What is the most possible explaination?

I have checked the LMHost files and name resolution works on both servers.

Any help would be appreciated. I thought of changing the priority around but then that is defeating the object of redundant servers.

 

[congogrey]

sounds like an issue with the replication between the servers. What version of CCM do you have? Depending on the version you might have a file called DBLHelper.exe run that file on your publisher and see what the status is on the various tabs of the application. IF they are not all green you can either re-publish or re-initialize the databases and correct most anything.

"For every complex problem, there is a solution that is simple, neat and wrong" -- H.L. Mencken

 

[megaco]

I looked for DBLHelper.exe but could not find it (somewhere under drivers/etc/ from memory) - I read a doc that said if you don't have this file then you should raise a tac case.

Is this required for version 3.3?

Thanks for your assistance

 

[congogrey]

Some later versions of CCM the file comes with it. It should be under C:\Program Files\Cisco\bin

I would open a TAC case or I can send you a copy of the file. (it_richATyahoo.com)

"For every complex problem, there is a solution that is simple, neat and wrong" -- H.L. Mencken

 

[megaco]

I have just connected to both servers and the replication problem has resolved itself. This problem was there for about a week and now its just disappeared.

Is there any SQL replication logs I can view to find out what happened? Where would they be located? Thanks in advance.