[cisco-voip] DC Directory issues between pub and sub

[Erick Bergquist]

Appears to be. We did the CCMPwdChanger tool and
checked several registry and INI file settings over
weekend. We worked long hours with TAC and meeting
place on this and no luck in getting DC Directory
working w/subscriber yet so next step is to rebuild
the subscriber server and see if that corrects the
issue. Plan is to do that next weekend.

--- Kevin Thorngren <kevint at cisco.com> wrote:
> Hi Erick,
> 
> Depending on the CCM version you have the password
> is encrypted and 
> stored in the register and/or an INI file in one of
> the folders under 
> c:\dcdsrvr.  It is not embedded into IIS.  What you
> described below is 
> a symptom of an incorrect password.
> 
> Thanks,
> Kevin
> On Apr 23, 2005, at 5:45 PM, Erick Bergquist wrote:
> 
> > Kevin,
> >
> > Thanks.
> >
> > Would we get a HTTP 500 Error (Internal Server
> error)
> > for lower web page frame when we selected User ->
> > Global Directory from CCMAdmin if the password was
> > different on sub?  Is the password embedded
> somewhere
> > in WWW/IIS also? We were getting this at one point
> > also.
> >
> > --- Kevin Thorngren <kevint at cisco.com> wrote:
> >> Hi Erick,
> >>
> >> The Directory Manager password on the Pub and Sub
> do
> >> need to be the
> >> same.  This is why replication is not working and
> >> probably why the
> >> reconfig_cluster command is not working.  Based
> on
> >> your description
> >> below you know what the password is on the Pub
> and
> >> the Sub.  I would
> >> recommend using the CCMPwdChanger tool to set the
> >> Pub's password to be
> >> the same as the Sub.  Then use the
> reconfig_cluster
> >> command to
> >> re-establish the replication agreements.  Once
> this
> >> is done, if needed,
> >> you can use the CCMPwdChanger tool to set the
> >> password back to the one
> >> that was on the Publisher.
> >>
> >> Here is more information to run the
> CCMPwdChanger:
> >>
> >
>
http://www.cisco.com/en/US/products/sw/voicesw/ps556/
> >>
> >>
> products_configuration_example09186a00800942be.shtml
> >>
> >> HTH,
> >> Kevin
> >> On Apr 23, 2005, at 2:24 PM, Erick Bergquist
> wrote:
> >>
> >>> Hi,
> >>>
> >>> Were having issue where the DC Directory between
> >>> publisher and subscriber is not
> >> syncing/replicating
> >>> correctly. If you look at users on publisher and
> >>> compare to subscriber they have different
> >> information.
> >>> We have waited days and data does not replicate.
> >>>
> >>> TAC had advised run DC Directory scripts and we
> >> did
> >>> that, but the reconfig_cluster step errors out
> and
> >> the
> >>> trace/log files say it can not talk with the
> >>> subscriber server. saids to do it manually.
> >>>
> >>> The pub/sub are on same network/LAN and switch
> and
> >> in
> >>> same subnet. SQL is working between the servers
> >> fine.
> >>>
> >>> How do we sync the database manually? Do we copy
> >> the
> >>> database from pub to sub then do the reconfig
> >> commands
> >>> in script instructions? I can't find clear cisco
> >> docs
> >>> on what to do if the script steps fail.
> >>>
> >>> When we launch DC Directory Manager the login
> for
> >> the
> >>> publisher and subscriber work, but need to use a
> >>> different password on pub and subscriber.
> >>>
> >>> Has anyone ran into this before? Is it a
> password
> >>> issue and we need to run a password utility to
> get
> >>> things corrected and synced back up?
> >>>
> >>>
> __________________________________________________
> >>> Do You Yahoo!?
> >>> Tired of spam?  Yahoo! Mail has the best spam
> >> protection around
> >>> http://mail.yahoo.com
> >>> _______________________________________________
> >>> cisco-voip mailing list
> >>> cisco-voip at puck.nether.net
> >>>
> >>
> https://puck.nether.net/mailman/listinfo/cisco-voip
> >>>
> >>
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam
> protection around
> > http://mail.yahoo.com
> >
> 

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com