Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Problems installing CCM 3.3.2 as a subscriber on a MCS7835-2400

I have installed a Cisco Call Manager 3.3.2 (as a publisher) on a MCS7835-1266.

The Installation was completed the CCM-Services and the W2K and CCM-Servicability don´t start. Database layer monitor hung on starting.

I couln´t start the services manually.

After upgrading to CCM 3.3.sr1 (installing all winos- /ccm- updates and patches it works.

Now I want to install a Cisco Call Manager 3.3.2 as a subscriber on a MCS7835-2400.

The winos installation seams to be successful. The CCM installation ends with an error and the rollback of the installation starts.

Someone tolds me, that the installation is not successful, because the version of the publishers DC-directory is not correct.

The current version is .

Can anyone help me to solve this Problem?

Cisco Employee

Re: Problems installing CCM 3.3.2 as a subscriber on a MCS7835-2

You are running into thsi issue:

CSCec00220 - Install of new Subscriber with 3.3(2) CDs into 3.3(3) cluster fails

Install of NEW Subscriber server with version 3.3(2) CD's into a

version 3.3(3) CallManager cluster fails.

In the past, with previous versions of CallManager as far back as

3.0, a customer could always install a new Subscriber using an

earlier version of CD's and then upgrade that subscriber to the

version currently installed on the Publisher.

This does not work with with an existing 3.3(3) cluster when

attempting to initially install a new subscriber using 3.3(2) CD's.

They should obtain 3.3(3) CD's in order for the installation to be

successful due to DC Directory checking the version installed on the


The issue can be identified with IntegratedSetup.trc showing:

Read remote registry to get IntegratedInstall version on Publisher

Publisher's IntegratedInstall version:""

Subscriber's install version is diffeent from Publisher's.

Install is aborted/cancelled...

At the time of this bug being raised 3.3(3) CD's have not yet FCS'ed

Work-around (will get you past this point but cause other issues):

Change the value of "IntegratedInstallVersion" on Publisher registry

"HKEY_LOCAL_MACHINE\Cisco Systems, Inc.\Directory Configuration" to

"". Please note down the existing value before changing it to

This will enable CallManager 3.3(2) to be installed on Subscriber as

far as directory install is concerned.

Now, once Subscriber install is complete, reset the

"IntegratedInstallVersion" on Publisher to original value and upgrade

the Subscriber to 3.3(3).


Get 3.3(3) install CD's

CreatePlease to create content