Guest

Cisco Unified Communications Manager (CallManager)

Cisco CallManager CDBLException Dump: [ActiveX object not initialized via insert or select] Administration Database Replication Error

Cisco - Cisco CallManager CDBLException Dump: [ActiveX object not initialized via insert or select] Administration Database Replication Error

Document ID: 97218

Updated: Jul 04, 2007

   Print

Introduction

This document describes this database replication error message and the necessary steps to troubleshoot it:

Cisco CallManager CDBLException Dump: [ActiveX object 
not initialized via insert or select] Administration

Prerequisites

Requirements

Cisco recommends that you have knowledge of Cisco Unified Communications Manager.

Components Used

The information in this document is based on Cisco Unified Communications Manager.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Problem

When a user logs into the Cisco CallManager web page, the Cisco CallManager CDBLException Dump: [ActiveX object not initialized via insert or select] Administration database replication error message appears as this example shows:

ccm-activex-error-1.gif

Solution

The error message described in this document can appear when there are two Network Interface Cards (NICs) enabled and with IP addresses assigned. Ensure you only have one NIC enabled on the server at a time.

Dual NICs are not supported. The recommendation is to have two NICs and use one as fault tolerance, but only one is operational at a time. Failure to disable the second NIC can result in two IP addresses that are assigned to the Cisco CallManager server. When two IP addresses are assigned to the Cisco CallManager server, it can cause a loss of service.

This error message can also be a result of a virus on the server. Run the latest approved virus engine against your CallManager servers.

Another possible reason could be related to cache memory. The workaround for this is to reboot the cluster. Please try this after hours.

If these workarounds do not solve the problem, try any one of these workarounds:

  1. You might need to check to see if you have the latest Cisco Security/OS service packs. Refer to Cisco IP Telephony Operating System, SQL Server, Security Updates for more information on these service packs. In order to get the latest Cisco CallManager software packs, refer to the CallManager and Voice Apps Crypto Software downloads (registered customers only) page

  2. Stop and restart IIS and test the browser on the affected server.

  3. Update the hosts and lmhosts files.

    1. On each CallManager server there exists an up to date "hosts" file located in c:\winnt\system32\drivers\etc.

    2. On each CallManager server there exists an up to date "lmhosts" file located in c:\winnt\system32\drivers\etc.

      Make sure the information on these files is up to date, if there is any information missing add it and enter the nbtstat -R command in command prompt.

Related Information

Updated: Jul 04, 2007
Document ID: 97218