-
Upgrading Cisco CallManager Release 4.0(2)
-
Preface
-
Frequently Asked Questions About Cisco CallManager 4.0 Upgrades
-
Upgrading from Cisco CallManager 3.2 (If You Are Not Replacing Hardware)
-
Upgrading from Cisco CallManager 3.3 (If You Are Not Replacing Hardware)
-
Performing Post-Upgrade Tasks
-
Reverting to the Previous Configuration After an Upgrade Attempt
-
Error Messages
-
Replacing Servers During the Upgrade
-
Feedback
Table Of Contents
Resolving Name Resolution Failures
Disabling the Restrict CD-ROM Access to Locally Logged-On User Only Security Policy
Error Messages
The following error messages may display in dialog boxes (not the log file) during the upgrade. You can obtain and review the log file, ccminst <data/time stamp>.log, from C:\Program Files\Common Files\Cisco\Logs.
Table 6-1 Installation Error Messages
You must provide the Computer Name of the publisher server. IP addresses or fully qualified DNS names are not allowed.
You must not enter periods (.) when you enter the publisher database server name.
Reenter the information correctly.
You must provide the publisher server name when installing a subscriber.
This message displays when you install Cisco CallManager on the subscriber server and do not provide the publisher database server name.
Reenter the information correctly.
You have entered an invalid product key. Please re-enter the key.
You entered an invalid product key.
See the Cisco CRS installation documentation to obtain the Cisco CRS product keys. See Installing Cisco CallManager Release 4.0(2) for the Cisco CallManager product key.
You must enter a password.
This message displays when you do not enter a password, but the application requires a password for the installation to occur.
Enter the correct password.
The passwords that you entered do not match.
This error message displays when you enter a password more than one time, but the password that you enter does not match the password on the server.
Enter the same password on all servers in the cluster.
The password that you entered is not valid.
You entered an invalid password.
Enter the correct password.
You must enter a phrase from 1 to 15 characters in length. This phrase may contain English lower-case letters, English upper-case letters, Westernized Arabic Numerals, and the following Non-alphanumeric "special characters" { } . < > : ? / | \ ` ~ ! @ $ ^ & * ( ) _ - +
You entered invalid characters for the private password phrase.
Enter valid characters.
Pending file operations are occurring. Reboot the server and then install Cisco CallManager.
Pending file operations are occurring.
Reboot the server and then install Cisco CallManager.
You are not logged on as `Administrator'. You must log in by using local Administrator user name and password to install Cisco CallManager.
You did not log in to the server with the local Administrator user name and password.
Log in to the server with the local Administrator user name and password.
You do not have administrator privileges. You must have administrator privileges to install Cisco CallManager.
You do not have administrative privileges.
Log in to the server with an account that has administrative privileges.
Windows 2000 Server is not installed. Install Windows 2000 Server before you install Cisco CallManager.
You did not install the appropriate version of the operating system.
Make sure that you installed the operating system version 2000.2.3 (or later) on all dedicated and coresident servers. Upgrade to 2000.2.6 (or later) and install the latest service release (2000-2-6sr1 or later) before installing Cisco CallManager.
Windows 2000 Service Pack 3 or later is not installed. You must have Windows 2000 Service Pack 3 or later installed before you install Cisco CallManager.
You did not install the appropriate version of the operating system.
Make sure that you installed the operating system version 2000.2.3 (or later) on all dedicated and coresident servers. Upgrade to 2000.2.6 (or later) and install the latest service release (2000-2-6sr1 or later) before installing Cisco CallManager.
You must install CallManager by double clicking CCMSetup.exe.
You tried to install Cisco CallManager by double clicking the msi file that is part of the Cisco CallManager package.
Double-click the CCMSetup.exe.
You must apply SQL 2000 Service Pack 3 (or later) before proceeding with this installation.
You did not install Microsoft SQL 2000 Service Pack 3.
Install Microsoft SQL 2000 Service Pack 3 and perform the Cisco CallManager upgrade.
If you have installed intrusion detection or anti-virus protection software, you must stop and disable these applications from the Services Control console before you continue with the Cisco CallManager installation. All other installed third-party applications must be uninstalled before proceeding with the CallManager installation. Failure to follow these directives could result in un-recoverable errors. Would you like to proceed?
This message always displays to alert the administrator of the requirements.
If you have Cisco-verified applications (Cisco AVVID Partner Applications) or platform agents that are installed on the server, you must disable/uninstall them and stop the services.
Because the <BUILDVERSION> of this Cisco CallManager MSI package is not compatible with the Cisco CallManager setup file (ccmsetup.exe), make sure that you are using the ccmsetup.exe that was distributed with this version of Cisco CallManager. The installation will now abort.
This message indicates that the MSI package is not compatible with the Cisco CallManager setup file.
Use the ccmsetup.exe file that was distributed with this version of Cisco CallManager.
You are attempting to upgrade Cisco CallManager <InstalledBUILDVERSION> to version <UpgradeBUILDVERSION>. Direct upgrades from this version of Cisco CallManager are not supported. You must first upgrade to a compatible Cisco CallManager version before upgrading to this version. The installation will now abort.
You tried to upgrade from a version other than Cisco CallManager 3.2 or Cisco CallManager 3.3.
Upgrade to Cisco CallManager 3.2 or Cisco CallManager 3.3 before attempting to upgrade to Cisco CallManager 4.0.
You are attempting to upgrade Cisco CallManager <InstalledBUILDVERSION> to version <UpgradeBUILDVERSION>. Upgrades from this version of Cisco CallManager require using the Same-Server Recovery method. Please refer to the Upgrading Cisco CallManager Release 4.0(2) documentation for more information. The installation will now abort.
You attempted upgrade directly from Cisco CallManager 3.2 to Cisco CallManager 4.0(2) without following the Same Server Recovery procedures.
You must perform a Same Server Recovery by using the operating system disks that ship with this version of Cisco CallManager to install operating system.
For publisher servers, see the "Install the Operating System by Using Same Server Recovery (Required)" section.
For subscriber servers, see the "Install the Operating System by Using Same Server Recovery (Required)" section.
You are attempting to upgrade Cisco CallManager <InstalledBUILDVERSION> to version <UpgradeBUILDVERSION> by using the web download file. You cannot use the web download to upgrade from this version of Cisco CallManager directly. You must obtain the upgrade CD-ROM disks from your Cisco account representative to complete this upgrade. The installation will now abort.
You cannot upgrade Cisco CallManager 3.3(x) to 4.0(2) by using the package for web (PFW) download file.
You must use the upgrade CD-ROM disks from the Cisco CallManager 4.0(2) software kit. Contact your Cisco account representative.
The Same System Recovery flag was detected. Same Server Recovery is required for upgrades from Cisco CallManager 3.2 to Cisco CallManager 4.0. Are you upgrading a Cisco CallManager 3.2 publisher database server to Cisco CallManager 4.0?
You chose the same server recovery option when you installed the operating system.
If you are upgrading from Cisco CallManager 3.2 to Cisco CallManager 4.0(2), refer to the Upgrading Cisco CallManager Release 4.0(2) document.
If you are installing Cisco CallManager on a publisher server for the first time, click No and continue with the installation.
If you are installing Cisco CallManager on a subscriber server for the first time, click No and continue with the installation.
Note
If you click Yes, the installation program configures your server as a publisher server.
The installation has detected that the server exists in a domain. When a server exists in a domain, authentication between servers may fail or the non-default domain security policies may be too restrictive for the Cisco CallManager installation to build critical NT Accounts during an upgrade. Failure to remove the server from the domain and add to a workgroup may cause upgrade errors, upgrade failures, or a total system failure, which includes a loss of data and a complete reinstallation of Cisco CallManager. Would you like to proceed?
The server exists in a domain.
Before you continue the installation, Cisco strongly recommends that you remove all servers in the cluster from the domain.
This release of Cisco CallManager is not supported on this server model. The installation will now abort.
You cannot install this version of Cisco CallManager on this server.
Refer to the Cisco CallManager Compatibility Matrix for a list of servers on which you can install this version of Cisco CallManager. To obtain the most recent version of this document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm.
The installation program does not have enough disk space on the C drive to complete the installation. The installation program requires that you have 3.0 gigabytes of disk space available on your server. Make at least 3.0 gigabytes of disk space available and restart the installation. For information, refer to the Upgrading Cisco CallManager guide.
You attempted an upgrade and do not have enough free disk space.
Make 3.0 gigabytes of disk space available and restart the installation program.
This version of Cisco CallManager is currently installed.
This message displays when you attempt to install the same version of Cisco CallManager that is currently on the server.
Remove the disk from the drive.
A newer version of this package has already been installed.
This message displays when you attempt to install a previous version of Cisco CallManager after a successful installation of a later version.
Remove the disk from the drive.
Cisco CallManager install did not complete successfully. Review the log file for more information.
The Cisco CallManager installation failed.
Obtain and examine the log file.
Unable to locate MSI package associated with this bootstrapper.
You did not copy all the files that came with the Cisco CallManager installation package to the server.
Copy the complete installation package to the server and rerun the Cisco CallManager installation.
Error opening MSI package
Cisco CallManager Setup cannot find the MSI package.
This message displays if you encounter a media problem; insert the disk again.
This package has already been installed.
This message displays when you attempt to install the same version of Cisco CallManager again after a successful installation.
Remove the disk from the drive.
An unexpected error occurred.
An error occurred during the Cisco CallManager Setup.
Obtain and examine the log file.
An unexpected error occurred while creating the log directory.
The installation could not create the log file directory.
Verify that security policies on the server are not restrictive.
The local security policy "Restrict CD-ROM access to locally logged-on user only" is enabled. This setting interferes with the Cisco CallManager installation. Please disable this setting using the Local Security Policy utility, reboot, and rerun the Cisco CallManager installation.
This message indicates that the "Restrict CD-ROM access to locally logged-on user only" local security policy is enabled on your server.
Disable this setting by using the Local Security Policy utility, reboot, and rerun the Cisco CallManager installation.
For more information, see the "cm1.mydomain.com" section.
Failure occurred trying to get DBNAME value from registry. Aborting Cisco CallManager installation.
The installation could not read DBNAME value from registry on the local machine.
Reboot the server and rerun the Cisco CallManager installation.
Failure occurred trying to validate the format of DBNAME value. Aborting Cisco CallManager installation.
The registry contains an invalid format of the DBNAME value. This error only occurs if you have manually modified this value.
Make sure that the DBNAME value is in the format CCM0xxx, where x stands for any digits.
Current OS version does not meet minimum requirements. Aborting Cisco CallManager install.
Cisco CallManager Release 3.3(4) requires Cisco-provided operating system version 2000.2.6 (or later) and the service release 2000-2-6sr1 (or later.)
Refer to Cisco Compatibility Matrix to review which versions are compatible for installation. To access the document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm.
Installing Cisco CallManager using Terminal Services is not allowed. Install will now abort.
Cisco does not support Terminal Services for Cisco CallManager installations, upgrades, or configuration tasks.
Cisco Technical Assistance Center (TAC) uses Terminal Services for remote management and troubleshooting tasks.If you want to use Virtual Network Computing (VNC), obtain the most recent version of the documentation at http://www.cisco.com/univercd/cc/td/doc/product/voice/iptel_os/index.htm.
Failed to launch <name of executable>, aborting install
The installation attempted to launch the executable, and the launch failed.
Obtain and examine the log file. You may have a media problem.
Failure occurred during the Cisco Directory installation. Refer to the log file C:\Program Files\Common Files\Cisco\Directory\IntegratedSetup.trc for details. Aborting Cisco CallManager install.
The DC Directory installation failed.
Obtain and examine the log file.
The Cisco CallManager installation detected an error while copying files. Stop all platform agents and Cisco-verified applications, and restart the installation. For more information, refer to the Upgrading Cisco CallManager document.
The Cisco CallManager installation failed to copy files to your server.
Stop all platform agents and Cisco-verified applications, and restart the installation.
For more information if you are upgrading from Cisco CallManager 3.2, see "Before You Begin" section.
For more information if you are upgrading from Cisco CallManager 3.3, see "Before You Begin" section.
Failure occurred during the Cisco CallManager installation. Please look at the Cisco CallManager installation log file for details. Aborting Cisco CallManager installation.
The Cisco CallManager installation detected an error while copying files. Stop all platform agents and Cisco-verified applications, and restart the installation. For more information, refer to the Upgrading Cisco CallManager document.
Obtain and examine the log file.
The password of [X] does not match the password on the publisher [Y]. For details, review the log file [Z].
The username and/or password of the user installing Cisco CallManager on the subscriber server does not match the username and/or password on the publisher database server.
Make sure that you entered the correct publisher server name and that the username and password on the publisher and subscriber match.
Because no network connectivity exists or you entered the incorrect publisher server name, the installation could not verify the password of [X] against the publisher [Y]. For details, review the log file [Z].
During the subscriber server installation, this error occurs if no network connection exists between the subscriber and publisher database servers or you did not enter the correct name of the publisher database server.
Verify the connection between the publisher database server and subscriber server and make sure that you entered the correct publisher database server name.
Either the password of [X] does not match the password on the publisher [Y], or a network connectivity error occurred. For details, review the log file [Z].
One of the following problems occurred:
•
•
•
Do each of the following tasks:
•
•
•
The private password phrase does not match the private password phrase on the publisher [X]. For details, review the log file [Y].
During the subscribe server installation, one of the following problems occurred:
•
•
•
Do each of the following tasks:
•
•
•
The installation could not verify the private password phrase on the publisher <server name>, because the user does not have permission to access the publisher server over the network. For details, review the log file <log file name>.
The installation could not verify the private password phrase on the publisher <server name>, because the user does not have permission to access the publisher server over the network. For details, review the log file <log file name>.
During the installation of a subscriber server, the installation program could not verify the private password phrase against the publisher server because of the security settings on either the Publisher or the Subscriber.
The probable causes include the following:
•
•
The installation failed to verify the Cisco CallManager version that runs on the publisher database server. Cancel the installation, and review the log file at C:\Program Files\ Common Files\Cisco\Logs\ CCMUIInst.log.
During the subscriber server installation, this error occurs if no network connection exists between the subscriber and publisher database servers or you did not enter the correct name of the publisher database server.
Verify the connection between the publisher database server and subscriber database server and make sure that you entered the correct publisher database server name.
The Cisco CallManager version you are installing on this subscriber does not match the version running on the publisher database server. Cancel the installation and ensure the publisher is upgraded to this Cisco CallManager version before you continue.
You attempted to install a different version of Cisco CallManager on the subscriber database server than you installed on the publisher database server.
Install the same version of Cisco CallManager on the subscriber database server that you installed on the publisher database server.
UMX.dll failed to register. After you complete the installation, review the log file.
UMX.dll failed to register because the process creation failed, the process terminated abnormally, or an error occurred when the system was executing regsvr32.
Verify that you rebooted the server after the installation. Execute a command prompt, enter regsvr32 C:\dcdsrvr\lib\UMX.dll, and press Enter.
To verify that you corrected the problem, try to add a new user in Cisco CallManager Administration on this server.
Indexing directory data did not finish. After you complete the installation, review the log file. The log file C:\dcdsrvr\log\DirInstallValidation.log.
The installation could not determine whether the DC Directory completed the indexing of its data.
Continue with installation. At the end of the installation, reboot the server when prompted to do so. After you reboot the server, bring up the services control and wait for DC Directory Server to have a status of started.
If this is a publisher database server, you can install Cisco CallManager on the subscriber database servers.
If this is a subscriber database server, go to a command window and enter dcdrepcl trigger all. Depending on the number of users that are configured in your system, the service may be in the starting state for a long time before changing to a started state.
The Cisco CallManager installation failed to stop <list of services> service(s). Please reboot the server, manually stop the service(s), and rerun the Cisco CallManager installation program.
The installation program failed to stop the services during installation.
Reboot the server, manually stop the service(s), and rerun the Cisco CallManager installation program.
The installation encountered an unknown error while trying to resolve the Publisher server name [X]. For more information, review the log file CCMInstUI.log.
The name resolution of the publisher server failed.
Verify that you correctly entered the publisher server name. To verify the hosts file, see the "Resolving Name Resolution Failures" section.
The installation could not resolve the Publisher server name [X] to a valid IP address. Verify that you entered the correct publisher server name, and review the log file CCMInstUI.log for more information.
You entered the wrong publisher server name, or the hosts file has the wrong information.
Verify that you correctly entered the publisher server name. To verify the hosts file, see the "Resolving Name Resolution Failures" section.
The installation successfully resolved the Publisher server name [X] to IP address [Y] but could not resolve the IP address back to a host name.
The reverse name resolution of the Cisco CallManager publisher server failed.
Verify that you correctly entered the publisher server name. To verify the hosts file, see the "Resolving Name Resolution Failures" section.
The installation successfully resolved the Publisher server name [X] to IP address [Y] and resolved the IP address back to the host name [Z]. The resolved host name does not match the server name that you entered.
The publisher server name that you entered does not match the server name that the installation program retrieved after completing forward and reverse name resolution.
Verify that you correctly entered the publisher server name. To verify the hosts file, see the "Resolving Name Resolution Failures" section.
Because mapped network drives exist on the server, the installation could not verify the password of [x] against the publisher [y]. Disconnect all the mapped drives, reboot the system, and rerun the installation. For details, review the log file [z].
The installation could not verify that the password on the subscriber server matches the password on the publisher database server.
Disconnect all the mapped drives, reboot the system, and rerun the installation.
Because mapped network drives exist on the server, the installation could not verify the private password phrase against the publisher [y]. Disconnect all the mapped drives, reboot the system, and rerun the installation. For details, review the log file [z].
The installation could not verify that the private password phrase on the subscriber server matches the private password phrase on the publisher database server.
Disconnect all the mapped drives, reboot the system, and rerun the installation.
The Cisco CallManager installation detected an unrecoverable error during database migration. You must revert to the original version of Cisco CallManager. For more information, refer to the Installing the Operating System on the Cisco IP Telephony Applications Server and Upgrading Cisco CallManager documents.
The installation program failed to migrate the Cisco CallManager data.
•
•
•
For more information, see the "Reverting to the Previous Configuration After an Upgrade Attempt" section.
You are upgrading Cisco CallManager <InstalledBUILDVERSION> to version <UpgradeBUILDVERSION> which does NOT support the following features:·
•
•
If you continue to upgrade, these features will no longer be available, and any associated data will be lost. Do you want to continue the upgrade process?
If you upgrade from 3.3(4) and above to 4.0(2), you will forfeit the listed features.
None. This is an informational message.
InsertCDR.exe - Application Error, The instruction at "0x10250fe7" referenced memory at "0x0000000". The memory could not be "read". Click OK to terminate program.
This is a harmless error message.
You should click OK to exit the dialog box and to continue with the installation of Cisco CallManager. Clicking OK does not terminate your installation; in fact, clicking OK will allow you to successfully upgrade your Cisco CallManager system.
The upgrade that you are attempting is not supported. To verify which versions of Cisco CallManager are compatible for upgrade, please refer to the Cisco CallManager Compatibility Matrix on CCO. The installation will now abort.
The version of Cisco CallManager that you are attempting to upgrade from is not supported.
Refer to Cisco Compatibility Matrix to review which versions are compatible for installation. To access the document, go to http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm.
Resolving Name Resolution Failures
Cisco CallManager requires NetBIOS and IP name resolution. An incorrect WINS (NetBIOS) or DNS (IP) configuration could result in a service outage.
To resolve name resolution failures, consult with your network administrator to confirm NetBIOS and IP name resolution within the entire network, which includes local device IP configurations, local device name resolution (LMHOSTS and HOSTS), network-based name resolution systems (WINS and DNS) and DHCP systems.
Note
Note
Note
Procedure
Step 1
Step 2
The following example illustrates a hosts file where cm1 represents the hostname and mydomain.com represents the default DNS suffix or connection-specific DNS suffix from the ipconfig /all command output.
127.0.0.1 localhost
1.3.5.9 cm1 cm1.mydomain.com
1.2.4.8 cm2 cm2.mydomain.comStep 3
The following example illustrates a lmhosts file where cm1 represents the hostname.
1.3.5.9 cm1 #PRE
1.2.4.8 cm2 #PREStep 4
ipconfig /flushdns
nbtstat -R
Note
Step 5
a.
The names of all other servers in the cluster should appear with a life of -1. The names appear multiple times.
The following example represents the output of the nbtstat -c command:
b.
Forward Entries
cm1.mydomain.com.------------------------------------------------------Record Name . . . . . : cm1.mydomain.comRecord Type . . . . . : 1Time To Live . . . . : 30682708Data Length . . . . . : 4Section . . . . . . . : AnswerA (Host) Record . . . :> 1.2.4.8cm1.------------------------------------------------------Record Name . . . . . : cm1Record Type . . . . . : 1Time To Live . . . . : 30682708Data Length . . . . . : 4Section . . . . . . . : AnswerA (Host) Record . . . :> 1.2.4.8Reverse Entries
8.4.2.1.in-addr.arpa.------------------------------------------------------
Record Name . . . . . : 8.4.2.1.in-addr.arpaRecord Type . . . . . : 12Time To Live . . . . : 30682708Data Length . . . . . : 4Section . . . . . . . : AnswerPTR Record . . . . . :> cm1Record Name . . . . . : 8.4.2.1.in-addr.arpaRecord Type . . . . . : 12Time To Live . . . . : 30682708Data Length . . . . . : 4Section . . . . . . . : AnswerPTR Record . . . . . :cm1.mydomain.com
Disabling the Restrict CD-ROM Access to Locally Logged-On User Only Security Policy
If you receive the error message that the local security policy "Restrict CD-ROM access to locally logged-on user only" is enabled, you must disable the setting, reboot the server, and rerun the Cisco CallManager installation. Use the following procedure to disable the security policy.
Procedure
Step 1
Step 2
Step 3
The Local Security Policy dialog box displays.
Step 4
Step 5
Step 6
Step 7
