[cisco-voip] Help. Publisher and Subscriber issue

[Wes Sisk]

Hi David,

Nice investigative work.  The system is supposed to automatically 
populate the registry based on contents of the SQL database.

DBConnection1 is supposed to be inserted by the DBL process under 
component services when it first starts up and properly accesses the SQL 
database.

As DBConnection1 is failing we can now limit this to one of the following:
a) database not properly updated for sub install.  check service 
paramaters for Database Layer Monitor service for the subscriber, 
advanced parameters, "Database Connection String".  It should look like 
this:
DSN=CiscoCallManager;SERVER=EVOICE-R5-CM1;DATABASE=CCM0301;Trusted_Connection=yes

If that string is missing then you've identified the problem. That 
string should be set at subscriber install time.  I've seen that not be 
set when name resolution was incorrect or IP connectivity intermittent 
during subscriber install.

b) database is properly populated but DBL component under component 
services cannot connect.  this could be failed connection to 
primary(publisher)CM or failure to connect to local subscriber 
database.  This is much more unlikely and would likely be a 
security/permissions issue.


/Wes


David Lima wrote:
> Thanks a lot for your reply Wes, I checked those points that you suggest me, and I found that, there is just one DBCONNECTION0 (for the Publisher Server) configured in the "regedit" and the DBCONNECTION1 that should be configured for the Subscriber Server is missing.
> My question is: Could I add this connection on the regedit in both servers and which cautions should I consider?
> Thanks again
> David
> ________________________________
> De: Wes Sisk [wsisk at cisco.com]
> Enviado el: viernes, 07 de marzo de 2008 02:19 p.m.
> Para: David Lima
> CC: Jonathan Charles; cisco-voip at puck.nether.net
> Asunto: Re: [cisco-voip] Help. Publisher and Subscriber issue
>
> Sounds like ccm.exe on subscriber does not know how to locate the ccm database on the subscriber.  There are several componenents involved in htis:
>
> Cisco database layer monitor service (aupair.exe)
> DBL component in Component Services
> DBConnection1 in the windows registry
> Authentication to the SQL server instance running on the subscriber
>
> All of these are in the path between the ccm.exe process and access to a ccm database that is correctly replicated to a subscriber.  A TAC case with mplace access is likely quickest path to resolution.
>
> /Wes
>
> David Lima wrote:
>
> Thanks for your mail Jonathan, actually I have CCM 4.1(3)sr5d in both servers and SO WIN2000 sr7. I'm gonna load the latest devpack and I let you know the results. Just this another question, When the Publisher goes down, I can't load the Cisco Administrator Web page, it takes a lot of time. Some suggestions?
>
> Thanks again
>
>
>
> -----Mensaje original-----
> De: Jonathan Charles [mailto:jonvoip at gmail.com]
> Enviado el: Thursday, March 06, 2008 11:59 PM
> Para: David Lima
> CC: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
> Asunto: Re: [cisco-voip] Help. Publisher and Subscriber issue
>
> Actually, this sounds like a phone firmware issue, upgrade... load the
> latest devpack...
>
>
> Jonathan
>
> On Thu, Mar 6, 2008 at 3:58 PM, Jonathan Charles <jonvoip at gmail.com><mailto:jonvoip at gmail.com> wrote:
>
>
> Versions?
>
>
>
>  Jonathan
>
>
>
>  On Thu, Mar 6, 2008 at 1:31 PM, David Lima <David.Lima at alphasys.com.bo><mailto:David.Lima at alphasys.com.bo> wrote:
>  >
>  >
>  >
>  >
>  > Hi all, I have a CCM cluster: 1 Publisher and 1 Subscriber, replication
>  > works fine, but when the Publisher goes down, the IP Phones are unable to
>  > register with the Subscriber only if I reset the IP Phone. I have configured
>  > the CCM cluster with both servers, and dhcp and dial-peer commands in the
>  > h323 GW. What could be the reasson?, Does someone could give me a tip to
>  > resolve this problem.
>  >
>  > Thanks a lot
>  >
>  > David.
>  > _______________________________________________
>  >  cisco-voip mailing list
>  >  cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
>  >  https://puck.nether.net/mailman/listinfo/cisco-voip
>  >
>  >
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>