DCDirectory Will No Start - System Down

[TheLaw]

If anyone's listening...

We've upgraded (attempted) the Publisher from 3.1 to 3.2 and now DCDirectory fails. Event viewer reports:

Error: kCtiProviderOpenFailure CTI Application Failed To Open
Reason Code: 2362179683

The service fails to start. A little history, a couple of months ago we re-installed the CRA - however, apparantly an undocumented yet critical step was ommitted (DCD Reconfig).

Now the DC won't start (the subscriber will), however, it appears as though the directories have not been synching properly (Publshier directory at 400meg, subscriber at 10meg - the 400meg due to the DCD Reconfig not begin done).

Cisco's documentation on DCDirectory repair says "Do Not Do this on 3.2 installations" Anyone have any DCD repair docs for 3.2?

We are waiting for TAC to respond. In the meantime, can anyone here help.

TIA

 

[TheLaw]

Padon me. The upgrade was from 3.2.2c Service Pack E to 3.2.2c Service Pack G.

Thanks

 

[icebrrrg]

I'm having the same issue after upgrading to CCM 3.3 SPG. Anyone have any updates?

 

[BuckWeet]

Well you got the upgrade for CCM so you obviously have SmartNET support, so I'd give TAC a call if your system is down..


BuckWeet

 

[osteohead]

With a system down and DcDirrectory not working, I would wonder if the administrator password was mistyped when the upgrade was run. I had a similar problem with 3.2(2) You could also have JTAPI issue that may cause this. As an additional note: CallManager 3.2(2) Sp H has errors in it and will take out CRA... The Windows hotfix associated with the update will kill your ability to access AppAdmin. Service Pack I is out now and H has been pulled from Cisco's site but, if you have it and were waiting to install, you may want to consider using Service Pack I instead.

 

[icebrrrg]

i mis-posted ... i'm running spI. sorry about that.

 

[icebrrrg]

to clarify -- i'm running OS build 2000.2.3, sp I, and CCM 3.2(2c) spG.

my issue is everything's running fine on the subscriber, but my CTI Manager service is barfing app errors (kCtiProviderOpenFailure) and the DC directory will not start. i can log in as local user administrator with the password i set ... and i can't reset the dcdirectory admin password without running dcdirectory.

i've tried setting it manually in the registry (using the password utility), but no dice. any advice?

 

[icebrrrg]

latest: i've removed the callmanager (not the OS) spG. DCDirectory is working again. I may go back to spG, or at least spF, but i think i'll leave it alone for the day.

 

[TheLaw]

Are all of your CRS engines running (i.e. non in partial state)?

 

[icebrrrg]

Everything seems to be running ... we've also re-applied CCM spG this morning and so far, so good. How'd yours coming, TheLaw?

 

[TheLaw]

Ours was fixed shortly after the post. Though I'm struggling to locate the documentation on what we did. I apologise to the forum for not providing the fix right away, however, I completely forgot I submitted a post!

I'll keep digging for the documentation. If I remember correctly, I believe we blew away the directory database on the subsriber and re-synched. I also know we had Jtapi issues (since we neglected to update Java).

 

[jafe]

TheLaw,
I'm encountering this problem with one of my customers. We have a P1 TAC case open and the engineer is doing a great job but so we don't reinvent the wheel here did you ever remember what you did that fixed the problem?
thanks,
JAFE