8-29
Cisco Customer Response Solutions Servicing and Troubleshooting Guide, Release 5.0(1)
Chapter 8 Troubleshooting Tips
CRS Engine Problems

Error occurs with Reactive Debugging Tool

Symptom An error occurs when using the Reactive Debugging tool.
Error Message Not defined.
Possible Cause Using the CRS Editor Reactive Debugging tool on a translation routed call can cause an
error.
Recommended Action From the ICM Configuration Manager, choose Tools > List Tools > Network VRU
Script List and temporarily increase the value in the Timeout field for the script.
CRS Engine Problems
This section contains the following troubleshooting tips on CRS Engine problems
• Agent cannot go Ready after logging in, page 8-30
• Voice Browser step throws an exception, page 8-30
• CRS Engine does not start and an RMI port in use error appears, page 8-30
• Attempting to start the Cisco CRS Node Manager service causes an error 1067, page 8-31
• Attempting to start the Cisco CRS Node Manager service causes an error 1069, page 8-31
• Application subsystem is in partial service, page 8-31
• CRS Engine is running but calls are not answered, page 8-32
• Changing the time on CRS machines results in agents getting logged off, page 8-32
• An error message plays when calling a CTI route point, page 8-33
• Changes to applications do not register, page 8-33
• Call drops during transfer over gateway, page 8-34
• H.323 client DTMF digits not detected, page 8-34
• Redirected call is disconnected, page 8-34
• The CRS server runs out of disk space, page 8-35
• CRS Server runs at 100% capacity or is very slow, page 8-35
• Database Subsystem goes into partial service, page 8-36
• JTAPI subsystem is in partial service, page 8-37
• Unable to connect to JTAPI provider, page 8-37
• The Simple Recognition step takes the unsuccessful branch, page 8-38
• Calling party and CRS do not have common codec, page 8-38
• Prompts with incorrect codec being played out, page 8-38
• Prompt Exception in CRS Engine log file, page 8-39
• CRS Engine does not start, page 8-39
• Application subsystem in partial service and application running for an unexpectedly long time,
page 8-39
• CRS Server and Active Directory integration results in some services being unregistered, page 8-40