Cisco Cisco Administrative Workstation Release Notes

37

where <host> is the name of the Admin Workstation on which Dynamic Agent Re-skilling was installed.

After running ICM Setup in edit mode to modify an AW Distributor component with Dynamic Agent 
Re-skilling enabled, Tomcat services are unable to start, causing web-based Dynamic Agent Re-skilling 
not to work. In the icmsetup.log file, the following error appears: 

 

"Could not rename C:\icm\tomcat\conf\server.xml.custom to C:\icm\tomcat\conf\server.xml". 

This problem occurs after editing an already installed AW Distributor component with Dynamic Agent 
Re-skilling enabled. This problem occurs for IPCC Enterprise/Hosted Editions, though not for System 
IPCC. 

If you plan to use ICM Setup to modify an AW distributor with Dynamic Agent Re-skilling enabled, 
first save a copy of C:\icm\tomcat\conf\server.xml to another location, and copy it back when setup 
is complete. Then start Apache Tomcat from the Windows Services control panel. 

If you do not discover this problem until the problem has already occurred, and if there are no 
engineering specials (ESs) or service releases (SRs) applied to the system, you can correct the 
problem by running Setup from the ICM Software CD, and re-editing the AW component—in 
particular, checking the Agent Re-skilling Web Tool feature again. (If you do have an SR or ES 
installed, you must uninstall it before running Setup. After running Setup, reinstall the SR or ES.)

Alternatively, if you do not discover this problem until the problem has already occurred, you can 
copy server.xml from another valid installation of a 7.0(0) AW distributor with Dynamic Agent 
Re-skilling enabled to C:\icm\tomcat\conf\server.xml, if you have such an installation available. 

It was not initially documented in the Staging Guide for Cisco ICM/IPCC Enterprise & Hosted Editions 
that System IPCC servers must not be partitioned.

If you have partitioned your System IPCC server, the System IPCC installer may report the following 
error on installation:

"Internal error creating databases. It is possible that you do not have sufficient hard drive space available 
for the databases."

The details for a workaround in this situation are provided by accessing CSCsb74424 through Bug 
Toolkit ( 

 ).

In System IPCC Enterprise, when creating or modifying a machine, if you keep getting the error 

 

 

"Unable to find the registry on machine XYZ. Make sure the hostname or IP address of the machine is 
correct, the right IPCC components are installed, and the IPCC Machine Initializer has been run."

 

 

and you have double checked everything and re-run the IPCC Machine Initializer on the machine in 
question, make sure that 

 

"File and Printer Sharing for Microsoft Networks" is turned ON under 

 

Start > Settings > Network Connections... Local Area Connections > General tab > Properties

 

on that machine.