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

Upgrade from CCM 3.3(3) to 3.3(4) failed

Hi cant upgrade my ccm from 3.3(3) to 3.3(4)or any other version.

Here s the error in the log :

=== Logging stopped: 8/29/2006 21:46:09 ===

MSI (c) (50:60): Product: Cisco CallManager -- Configuration failed.

08/29/2006 21:46:09.589 CCMSetup.cpp fnRunCommand CreateProcess returned: 1603

08/29/2006 21:46:09.589 CCMSetup.cpp fnRunCommand Function ended

08/29/2006 21:46:09.589 CCMSetup.cpp fnInstallPackage msiexec.exe: Return Code: 1603: Fatal error during installation.

08/29/2006 21:46:16.902 CCMSetup.cpp fnInstallPackage Cisco CallManager Upgrade did not complete successfully. Review the log file for more information.

08/29/2006 21:46:16.902 CCMSetup.cpp fnInstallPackage User responded "OK" to message box.

08/29/2006 21:46:16.902 CCMSetup.cpp fnInstallPackage Function ended

08/29/2006 21:46:16.902 CCMSetup.cpp WinMain Function ended.

Any idea ?

Regards

Nicolas

1 REPLY
Green

Re: Upgrade from CCM 3.3(3) to 3.3(4) failed

The installation is not proceeding in the PUB or in the SUB?

Make sure you have run Upgrade Assistant and

LMHOSTS|HOSTS files are configured correctly.

Windows path environment path is not correct. So the isntaller is unable to save the dc

database.

It could be incorrect DNS entree that maybe preventing it from properly installing it.

It could be that you running into

CSCee81635 bug below are the details.

If the problem is after installing CallManager, DCDirectory service fails to start giving a logon failure error message.

Conditions:

If windows administrator password has any of the following 4 characters, this

problem will surface.

\ " % ^

Workaround:

Change the windows administrator password to remove the one or more special

characters mentioned above from the windows administrator password and reinstall CallManager.

HTH

124
Views
0
Helpful
1
Replies
CreatePlease to create content