Install of CallManger subscriber failing

[john.heyer]

After a failed upgrade to CCM 4.1, we've reverted the publisher back to 3.3.4, and are doing fresh installs on the subcribers (rebuilt OS, etc).

The installer for the subscribers is failing with the following error message:

Failure occured trying to determine if Cisco Directory install succeeded. Aborting Cisco CallManager install.

We know that Cisco Directory on the publisher is OK, because IPCC express is working fine now.

[kthorngr]

The most common reason the subscriber fails during DC Directory installation is name resolution. Make sure you have the hosts and lmhosts configured on the subscriber.

If this is good then someone will need to look through the log files in c:\dcdsrvr\log to find the problem. You can open a TAC to have them reviewed or if you are not in a hurry you can zip the entire folder and email to me.

Kevin

[electro22]

Also, make sure your CMs are in DNS if you specify a DNS server in the TCP/IP settings.

If your servers aer not in DNS, remove the DNS server entries from the TCP/IP settings (or if DNS is required, put your CMs in DNS).

-Jaret

[john.heyer]

We found the reason for this. We only had CDs for CallManager 3.3.3, and the publisher is 3.3.4

We've obtained a 3.3.4 installer and got it up and running no problem. I did keep the hosts files in place, just in case there's a failure of DNS