Document ID: 109715
Updated: Feb 26, 2009
Contents
Introduction
After an upgrade to Cisco Unified Web Interaction Manager 4.2.(5), ISAPI error is received. This document describes how to troubleshoot this issue.
Prerequisites
Requirements
Cisco recommends that you have knowledge of how to install Cisco
Unified Web and E-Mail Interaction Manager. Refer to
Installing
Cisco Unified Web and E-Mail Interaction Manager
for more
information.
Components Used
The information in this document is based on the Cisco Unified Web and E-Mail Interaction Manager version 4.2(5).
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
After you upgrade to Cisco Unified Web Interaction Manager 4.2.5, Weblogic causes an ISAPI error. Weblogic does not come up, even if started as stand-alone, and it appears that the license mapping is corrupted.
Solution
Complete these steps in order to fix the license mapping:
Caution: You need to run the populate.bat file
only if you see
I18N_EGPL_LICENSE-ACTION_LICENSE_MAPPING_CORRUPT
exceptions in the License manager log while it is coming up.
-
Place the file populate.bat in the <CIM_install>\bin\platform\windows folder on the file server.
-
Change the JAVA home and PL home path in this file.
-
Make sure that the Cisco Interaction Manager (CIM) application is stopped.
-
Run populate.bat with partition ids as the input parameters. For example, run this command at the commad prompt c:\CIM\eservice\bin\platform\windows\populate.bat 0 1
Related Information
Open a Support Case (Requires a Cisco Service Contract.)
Related Cisco Support Community Discussions
The Cisco Support Community is a forum for you to ask and answer questions, share suggestions, and collaborate with your peers.
Refer to Cisco Technical Tips Conventions for information on conventions used in this document.