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

Cisco CallManager upgrade from 3.3(2c) to 3.3(3) fails with error messages in the DC Directory installation

Core Issue

When the Cisco CallManager is upgraded from version 3.3(2c) to 3.3(3), it fails with the Failure occured trying to determine if Cisco Directory install succeeded. Aborting Cisco CallManager install error message. The upgrade fails with the errors

Resolution

This issue involves Cisco bug ID CSCeb52723 - CM upgrade should continue even if dir inst fails (CM not using DCD).

To resolve the issue, perform these steps:

  1. Check the value of this registry key on the publisher:

    HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\Directory Configuration\ DCDMGRPW 

    If it has the value 0c0a000a2c101c1a100354615c, it is fine.

  2. If it does not have the above value, open a DOS command prompt and type PasswordUtils ciscocisco123 to generate an encrypted password for ciscocisco123. The encrypted password is0c0a000a2c101c1a100354615c.
  3. Paste the encrypted password into this registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\Directory Configuration\ DCDMGRPW

After completing the procedure, re-boot the server and re-start the upgrade, as it may encounter Cisco bug IDCSCeb71414 - Failed Install (Pending File Operations) then 1603 msiexec error.

Version history
Revision #:
1 of 1
Last update:
‎06-22-2009 05:02 PM
Updated by:
 
Labels (1)