Brandon Buffin Tue, 03/13/2007 - 13:47
User Badges:
  • Purple, 4500 points or more

You can find the 3.3(3) upgrade at the folllowing link, however this is only for an upgrade from 3.3(2).


http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr-33


If you need to get there from a previous version, you might check the archive page here:


http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr-archive


Hope this helps. If so, please rate the post.


Brandon

dframos Wed, 03/14/2007 - 06:09
User Badges:

I need the media for new 3.3(3). The servers are licensed but they do not have the media. I am building new call managers offline the BARS backup that I have is from the existing 3.3(3). I have the new servers ready with same OS same OS/SR. Need to install 3.3(3) on new to restore from BARS an continue to 4.1 and 4.2(3) which I do have the media. I do not see Cisco archiving 3.3(3) anymore. What can I do?

Brandon Buffin Wed, 03/14/2007 - 12:52
User Badges:
  • Purple, 4500 points or more

Since you have the 4.1 and 4.2(3) media, one option would be to go ahead and upgrade the current servers, backup using BARS, install 4.2(3) on the new servers and restore from backup. This may even be a better option as you will end up with a fresh install of 4.2(3) as opposed to an upgrade.


Brandon

dframos Thu, 03/15/2007 - 11:33
User Badges:

Thanks. I found Release Notes, failure is due to bug id:CSCee81635 it is failing on 3.3.5 and 4.1 as well. I will use the

Cisco Password utility to correct the problem.

Upgrade of Callmanager from 3.3(3) to 3.3(4) fails when using ~, %, or @ in

Directory Manager password. Error is "Failure occured during the Cisco

Directory

installation. Please look at the Cisco CallManager installation log files for

details.

Aborting Cisco CallManager install."


The integratedsetup.trc file contains the following

Error : Execution of "C:\dcdsrvr\perl\scripts\avvid_upgrade.pl". Refer

C:\dcdsrvr\log\avvid_upgrade.error.

[18:22:50] Completed

Populate ciscoatUserProfileString

- Done; skipped

Setting the environment variable PERLLIB..

IntegratedInstall aborted due to failure in configuration of Directory.

Install is aborted/cancelled...



Workaround

Change the Directory Manager password so that it does not include special

characters.


Actions

This Discussion