Guest

Cisco Unified Communications Manager (CallManager)

Field Notice: When Upgrading to CM3.03B SQL, the Server Screen Is Confusing


November 15, 2000



Products Affected

Cisco Call Manager version 3.0(3b)

Problem Description

With CM version 3.02b or 3.01 loaded, and you upgrade CM using the 3.03B executable file from CCO. When asked "where the SQL server is located", you specify the local machine host name. After the upgrade is complete, you try to add a new subscriber. The subscriber will never get replicated and will not become part of the cluster.

Background

When customers use the 3.03B upgrade procedure, they are given a screen to specify their SQL Server Location. The two options are "Primary Database Location" or "Create Primary Database". Many users think selecting "Create Primary Database" will overwrite their existing database. However, this is not the case, and in fact, selecting "Primary Database Location" is incorrect for most users. The upgrade should never ask this question. The upgrade should know if the system is a publisher or subscriber and upgrade appropriately.

Problem Symptoms

No other CM's will be allowed into the cluster.

Workaround/Solution

Recovery procedure for choosing the incorrect option during the 3.0(3b) install is listed below:

  1. On the Publisher, reinstall CCM 3.0(3b) and this time choose the option that states "I want this machine to host the primary database".

  2. After the system has rebooted following the install, click on Start - Programs - Microsoft SQL Server 7.0 - Enterprise Manager.

  3. Expand the tree until you reach the folder named Databases.

  4. Click on the plus sign next to Databases and then click on the plus sign next to the highest numbered CCM database (such as CCM0300, CCM0301).

  5. Click on the plus sign next to the folder named Publications and then highlight the subscription that is listed under the folder. (The subscription will contain the same name as the database in Step 4).

  6. The right window will contain a list of current subscriptions. Right click on the subscription named xxx: where xxx is the name of the Publisher and is the database from Step 4.

  7. Choose Delete Subscription and then click Yes. A window will pop up asking if you want to remove the subscription information from the Subscriber. Choose No and close Enterprise Manager.

Fixing the DC Directory

Note:?These steps should be followed after all of the servers in the cluster have been upgraded to 3.0(3b). Also, these steps MUST be run locally in order to work properly.

  1. On the Publisher, click Start, Run and then type cmd and press Enter.

  2. Type c:\dcdsrvr\bin and press Enter.

  3. Type avvid_save and press Enter.

  4. Type net stop dcdirectory and press Enter.

  5. After the message "The DC Directory Server service was stopped successfully." appears, type cleandsa and press Enter. When instructed to by the prompt, press a key to continue.

  6. When finished, type net start dcdirectory and press Enter.

  7. After the message "The DC Directory Server service was started successfully." appears type avvid_cfg "(local)" where is the name of the database used in Step 4 of the previous procedure. (ex. avvid_cfg "(local)" CCM0300).

  8. When that is finished type avvid_restore and press Enter.

  9. Close the command prompt window.

Do the following steps on EACH of the subscriber machines.

  1. Click Start - Run - type cmd and press Enter.

  2. At the prompt type c:\dcdsrvr\bin and press Enter.

  3. Type net stop dcdirectory and press Enter.

  4. After the message "The DC Directory Server service was stopped successfully." appears, type cleandsa and press Enter. When instructed to by the prompt, press a key to continue.

  5. When finished, type net start dcdirectory and press Enter.

  6. After the message "The DC Directory Server service was started successfully." appears type avvid_scfg.cmd where is the name of the publisher server and is the name of the subscriber server that the procedure is being done on. (ex. avvid_scfg.cmd Cisco-Pub Cisco-Sub). Press enter.

  7. Repeat Steps 1 through 7 on EACH subscriber's machine.

Resolution to the Problem

In Call Manager Release 3.0(4), we changed the dialog box so that it is less confusing to customers so they will be successful in choosing the correct option for new installs or upgrades.

Option Examples:

I am upgrading / installing the CallManager Publisher.

Or

I am upgrading / installing the CallManager Subscriber. Please enter the hostname of your CallManager Publisher:

In Call Manager Release 3.0(5), the users will not be asked to choose either option.

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

View bug details for CSCds58697 (registered customers only)

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods: