Cisco CAD Error Code Dictionary
CAD 10.6 for Cisco Unified Contact Center Express Release 10.6
First Published: December 17, 2014
Last Updated: December 17, 2014
Cisco Systems, Inc.
www.cisco.com
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED
WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED
WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of
UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL
FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE
PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of
Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use
of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples,
command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual
IP addresses or phone numbers in illustrative content is unintentional and coincidental.
Cisco CAD Error Code Dictionary 
© 2014 Cisco Systems, Inc. All rights reserved.
2
Cisco CAD Error Code Dictionary
Error Messages
Error messages are classified by the level of severity of the error. These levels are:
■
Fatal. The program cannot continue.
■
Error. The program has suffered a loss of functionality, but it continues to run.
■
Warn. There is a malfunction that is a nuisance but that does not interfere
with the program’s operation.
■
Informational. Not an error, this is related information that might be useful for
troubleshooting.
NOTE: Informational error messages are not listed in this document.
Error
Description
ACDA2000
Text:
Client and BIPPA service have different product
version.
Type:
Error
Add’l Info:
CTIOS API wait for single object fails.
Action:
Close client browser and restart client.
December 17, 2014
3
Cisco CAD Error Code Dictionary
Error
Description
ACDA3000
Text:
Unable to load BIPPA or Surrogate service IP
addresses, port, or rank: %s. Using defaults.
Type:
Error
Add’l Info:
Unable to load BIPPA service IP address or
Surrogate service IP address, port, or rank from
ACD Adapter service configuration file because
of specified error. Default values are used
instead.
Add’l Info:
Verify ACD Adapter service configuration file
exists and is readable by ACD Adapter service.
Verify BIPPA service IP address, Surrogate
service IP address, port, and rank settings exist
and are valid in the configuration file.
Text:
Enterprise Data value is greater than maximum
size of %d characters, truncating to fit.
Type:
Warn
Add’l Info:
None.
Action:
The Enterprise Data that was entered is larger
than the maximum size for that field. See the
field that is being set and make sure that any
time it is set (manually, workflows, etc.) the data
is less than the maximum.
Text:
Unable to create thread. Error(%ls)
Type:
Fatal
Add’l Info:
None.
Action:
The program was not able to create the
specified thread.Check system resource
availability (CPU and memory).
Text:
Error occured when validating message:
<%d:%hs> for element <%hs:%d>.
Type:
Error
Add’l Info:
AcmiClient is unable to validate specified ACMI
message because of problems with specified
element in the message.
Action:
Verify user entered information is correct. If the
element is for data obtained from LDAP or LRM,
verify the services are running and active. Verify
post install has completed.
ACMI1000
ACMI1000
ACMI2000
4
December 17, 2014
Error Messages
Error
Description
ACMI2002
Text:
Error occured when validating <%hs> message:
<%d:%hs> for element <%hs:%d>.
Type:
Error
Add’l Info:
AcmiClient is unable to validate specified ACMI
message because of problems with specified
element in the message.
Action:
Verify user entered information is correct. If the
element is for data obtained from LDAP or LRM,
verify the services are running and active. Verify
post install has completed.
Text:
Error occured when encoding message: Msg.
Type:
Error
Add’l Info:
None.
Action:
Error occured when encoding message being
sent form the CTI server. See error text for
further details. Were any errors reported during
CAD installation? Contact technical support if
the error persists.
Text:
Error occured when receiving message from CTI
server.
Type:
Error
Add’l Info:
None.
Action:
Error occured when receiving message being
sent from the CTI server. See error text for
further details. The client will attempt to recover
the connection.Check network connectivity if
error persists.
Text:
LDAP Error: Could not find <%ls> for host <%ls>
for service type <%ls>.
Type:
Warn
Add’l Info:
AcmiClient is unable to get specified information
for specified host of specified service type from
LDAP service.
Action:
Check if LDAP service is running. Check whether
specified information exists in LDAP.
ACMI2003
ACMI2004
ACMI3001
December 17, 2014
5
Cisco CAD Error Code Dictionary
Error
Description
ACMI3002
Text:
LDAP Error: No host defined in LDAP.
Type:
Warn
Add’l Info:
There are no host defined for ACMI services in
LDAP service.
Action:
Check if LDAP service is running. Check whether
specified information exists in LDAP.
Text:
Failed to get a valid OPEN_CONF response to the
OPEN_REQ sent to CTI service: <exception>.
Type:
Warn
Add’l Info:
None.
Action:
If the exception is SplkIllegalStateException, the
OPEN_REQ failed. Check whether the
information sent in OPEN_REQ, such as
peripheral ID or agent ID, is valid. Check if the
CTI service, the peripheral or central controller,
or the agent phone is offline or out of service.
Check if the Connect Only if Peripheral is Online
flag is true and the Peripheral Online Vvalue in
OPEN_CONF is false.
ACMI3003
If the exception is SplkSocketTimeoutException,
CTI service did not respond to OPEN_REQ sent in
a timely fashion. Run Network Checks and CPU
Checks specified in Cisco CAD Troubleshooting
Guide. Verify CTI service is running and active.
If the exception is
SplkNotYetConnectedException,
SplkClosedChannelException, or
SplkSocketException, the connection to CTI
service is down. Run Network Checks specified
in Cisco CAD Troubleshooting Guide. Verify CTI
service is running and active.
ACMI3004
6
Text:
Peripheral is offline at <host>.
Type:
Warn
Add’l Info:
Current CTI Service that ACMI client is
connecting to is offline.
Action:
Verify CTI Service setting are correct in
postinstall.exe. Verify CTI Service is running and
active.
December 17, 2014
Error Messages
Error
Description
ACMI3005
Text:
Message queue has reached max size <%d>.
Discarding received message <%ls>.
Type:
Warn
Add’l Info:
Unable to add received CTI message to message
queue because the queue has reached its
maximum size. Messages are being received
faster than they are being processed.
Action:
Run CPU Checks specified in Cisco CAD
Troubleshooting Guide. Check if application is
hung.
Text:
Timeout after <%d> milliseconds waiting for
<%ls> receiver thread to start.
Type:
Warn
Add’l Info:
Timeout after specified delay waiting for
specified ACMI receiver thread to start.
Action:
Run CPU Checks specified in Cisco CAD
Troubleshooting Guide. Check if application is
hung.
Text:
Internal error: Attempting to get string value
from non-string <element> element at index
<index> in <messageType> message.
Type:
Warn
Add’l Info:
An internal error where the application is
attempting to get a string value from a non-string
element at specified index of specified message.
Action:
Contact technical support.
Text:
Timeout after <%d> milliseconds waiting for
<%ls> receiver thread to stop.
Type:
Warn
Add’l Info:
Timeout after specified delay waiting for
specified ACMI receiver thread to stop.
Action:
Run CPU Checks specified in Cisco CAD
Troubleshooting Guide. Check if application is
hung.
ACMI3006
ACMI3007
ACMI3008
December 17, 2014
7
Cisco CAD Error Code Dictionary
Error
Description
ACMI3009
Text:
Timeout after <%d> milliseconds waiting for
<%ls> receiver thread to start.
Type:
Warn
Add’l Info:
Timeout after specified delay waiting for
specified ACMI receiver thread to start. Check if
application is hung.
Action:
Run CPU Checks and Memory Checks specified
in the Cisco CAD Troubleshooting Guide.
Text:
Internal error: Attempting to get string value
from non-string <%ls> element at index <%d> in
<%ls> message.
Type:
Warn
Add’l Info:
An internal error where the application is
attempting to get a string value from a non-string
element at specified index of specified message.
Action:
Contact technical support.
Text:
Timeout after <%d> milliseconds waiting for
<%ls> receiver thread to stop.
Type:
Warn
Add’l Info:
Timeout after specified delay waiting for
specified ACMI receiver thread to stop.
Action:
Run CPU Checks and Memory Checks specified
in the Cisco CAD Troubleshooting Guide. Check if
application is hung.
ACMI3010
ACMI3011
8
December 17, 2014
Error Messages
Error
Description
BIPPA1000
Text:
BIPPA service is unable to create a CORBA
service: CORBA error <%ls>.
Type:
Fatal
Add’l Info:
Unable to create CORBA service for the BIPPA
service to receive requests from IP Phone Agent
clients.
Action:
Do the following:
• Restart the BIPPA service.
• Check if another instance of BIPPA service is
already running. If so, stop it or don’t start a
second instance.
• Check if another service is using the same
socket port (3013 for UCCX, 59010 for
UCCE) as BIPPA CORBA service. If so, stop
that service. If that service needs to be
running, contact technical support.
• Check whether a firewall or security software
is preventing BIPPA service from using the
port.
• If the error persists, contact technical
support.
BIPPA2000
December 17, 2014
Text:
Internal error: An unexpected error occurred
while <%ls>.
Type:
Error
Add’l Info:
An error occurred while performing specified
action.
Action:
Restart the LDAP, LRM, and BIPPA services, wait
until they are all active, and then try the action
again. If the problem persists, contact technical
support.
9
Cisco CAD Error Code Dictionary
Error
Description
BIPPA2001
Text:
LRM service error: Failed to initialize LRM
manager.
Type:
Error
Add’l Info:
An error occurred while setting up
communication with the LRM service.
Action:
Restart the BIPPA and LRM services, wait until
they are both active, and then try the action
again. If the problem persists, contact technical
support.
Text:
LRM service error: Failed to register for BIPPA
events: <%ls>.
Type:
Error
Add’l Info:
An error occurred while registering with the LRM
service for BIPPA events.
Action:
Restart the BIPPA and LRM services, wait until
they are both active, and then try the action
again. If the problem persists, contact technical
support.
BIPPA2002
10
December 17, 2014
Error Messages
Error
Description
BIPPA2003
Text:
Could not open BIPPA service information file
<%ls>.
Type:
Error
Add’l Info:
Could not open the BIPPA service information
file used by the IPPA JSP client to communicate
with the BIPPA service.
Action:
Do the following:
• For UCCX, check the preferences to see if the
TOMCAT HOME value in
/opt/cisco/uccx/desktop/config/bippaservic
e/config/prefs.cfg preferences is the
location of the Tomcat directory. For UCCE,
check the registry to see if the
TOMCAT_HOME value in
HKEY_LOCAL_MACHINE\SOFTWARE\
Calabrio\CAD\IPPA\Config is the location of
the Tomcat directory. By default, it is set to
the folder C:\Program Files\Cisco\Desktop\
Tomcat\ for UCCE and $TOMCAT_HOME for
UCCX. Ensure the directory exists.
• For UCCX, check the preferences to see if the
Install Directory preferences value in
/opt/cisco/uccx/desktop/config/sitesetup/p
refs.cfg is the location of CAD software. For
UCCE, check the registry to see if the Install
Directory value in HKEY_LOCAL_MACHINE\
SOFTWARE\Calabrio\CAD\Site Setup is the
location of CAD software. By default, it is C:\
Program Files\Cisco\Desktop\ for UCCE and
/opt/cisco/uccx/desktop for UCCX. Ensure
the directory exists.
• BIPPA service does not have sufficient
permissions to create a file in the Tomcat
folder. Login as the user that the BIPPA
service is running as and attempt to create a
file in that directory to verify.
• The file is read only. Make it writable.
• The disk is full. Remove unnecessary files.
• If this does not correct the problem, contact
technical support.
December 17, 2014
11
Cisco CAD Error Code Dictionary
Error
Description
BIPPA2004
Text:
Unable to set process priority to high: <%ls>.
Type:
Error
Add’l Info:
The BIPPA service was unable to change its
process priority to high because of the specified
Windows error.
Action:
Check the Windows error. Ensure that the user
that the BIPPA service is running as has
permission to change its process priority to High.
Text:
LRM service error: Failed to register for LRM
events: <%ls>.
Type:
Error
Add’l Info:
An error occurred while registering with the LRM
service for LRM events.
Action:
Restart the BIPPA and LRM services, wait until
they are both active, and then try the action
again. If the problem persists, contact technical
support.
Text:
LRM service error: Failed to register BIPPA
service: <%ls>.
Type:
Error
Add’l Info:
An error occurred while registering BIPPA service
with the LRM service.
Action:
Restart the BIPPA and LRM services, wait until
they are both active, and then try the action
again. If the problem persists, contact technical
support.
BIPPA2005
BIPPA2006
12
December 17, 2014
Error Messages
Error
Description
BIPPA2007
Text:
Internal error: Could not create <%ls> object
because is out of memory.
Type:
Error
Add’l Info:
The machine running the BIPPA service ran out
of available memory.
Action:
Do the following:
• Stop unnecessary processes on the
machine.
• Restart the BIPPA service.
• Run a memory check.
• Add more memory to the machine.
BIPPA2008
Text:
Internal error: Toolbar type <%ls> has no default
configuration.
Type:
Error
Add’l Info:
There is no default configuration for specified
toolbar type.
Action:
Do the following:
• Check whether installation completed
successfully and default data has been
loaded into LDAP.
• Check whether backup data has been
restored successfully.
• Restart the BIPPA service if install and
restore were done successfully.
• Contact technical support if the above steps
do not work.
BIPPA2009
December 17, 2014
Text:
LRM service error in getting license: <%ls>.
Type:
Error
Add’l Info:
BIPPA service could not obtain license from LRM
service because of specified error.
Action:
Restart the BIPPA and LRM services, wait until
they are both active, and then try the action
again. If the problem persists, contact technical
support.
13
Cisco CAD Error Code Dictionary
Error
Description
BIPPA2010
Text:
Failed to accept socket connection: <%ls>.
Type:
Error
Add’l Info:
BIPPA service could not accept connection
because of specified error.
Action:
Do the following:
• Restart the BIPPA service.
• Check if another instance of BIPPA service is
already running. If so, stop it or don’t start a
second instance.
• Check if another service is using the same
socket port (3014 for UCCX, 59012 for
UCCE) as BIPPA service. If so, stop that
service. If that service needs to be running,
contact technical support.
• Check whether a firewall or security software
is preventing BIPPA service from using the
port.
• If the error persists, contact technical
support.
14
December 17, 2014
Error Messages
Error
Description
BIPPA2011
Text:
Failed to initialize socket connection: <%ls>.
Type:
Error
Add’l Info:
BIPPA service could not initialize socket
connection from client because of specified
error.
Action:
Do the following:
• Restart the BIPPA service.
• Check if another instance of BIPPA service is
already running. If so, stop it or don’t start a
second instance.
• Check if another service is using the same
socket port (3014 for UCCX, 59012 for
UCCE) as BIPPA service. If so, stop that
service. If that service needs to be running,
contact technical support.
• Check whether a firewall or security software
is preventing BIPPA service from using the
port.
• If the error persists, contact technical
support.
BIPPA2012
Text:
Failed to start <%ls> thread: <%ls>.
Type:
Error
Add’l Info:
Specified thread could not be started.
Action:
Do the following:
• Check if the machine is low on memory.
• Stop unnecessary processes on the
machine.
• Restart the BIPPA service.
• If the error persists, contact technical
support.
December 17, 2014
15
Cisco CAD Error Code Dictionary
Error
Description
BIPPA2013
Text:
Internal error. <%ls> wait event is invalid.
Type:
Error
Add’l Info:
A waitable event is invalid.
Action:
Do the following:
• Check if the machine is low on memory.
• Stop unnecessary processes on the
machine.
• Restart the BIPPA service.
• If the error persists, contact technical
support.
BIPPA2014
Text:
CTI service is not available.
Type:
Error
Add’l Info:
CTI service is not available.
Action:
Nothing needs to be done if CTI service fails over
successfully or was shutdown intentionally.
Otherwise, do the following:
• Restart CTI service if it is not running.
• If CTI service is running, run Network Checks
specified in the CAD Troubleshooting Guide
to determine why BIPPA service computer
could not reach CTI service computer.
• Restart the BIPPA service.
• If the error persists, contact technical
support.
16
December 17, 2014
Error Messages
Error
Description
BIPPA2015
Text:
The CORBA connection information for the BIPPA
service obtained from LRM service is invalid.
Type:
Error
Add’l Info:
The CORBA connection information for the BIPPA
service obtained from LRM service is invalid.
Action:
Do the following:
• Ensure BIPPA service is running and active.
• Run Network Checks specified in the CAD
Troubleshooting Guide to ensure BIPPA
service is reachable from client computer.
• Restart the BIPPA service.
• If the error persists, contact technical
support.
BIPPA2016
Text:
Failed to get switch type from LDAP.
Type:
Error
Add’l Info:
BIPPA service failed to get switch type from
LDAP.
Action:
Do the following:
• Ensure LDAP service is running and active.
• Run Network Checks specified in the CAD
Troubleshooting Guide to ensure LDAP
service is reachable from BIPPA service
computer.
• Restart the BIPPA service.
• If the error persists, contact technical
support.
BIPPA2017
December 17, 2014
Text:
Client socket descriptor <%d> is negative.
Type:
Error
Add’l Info:
Client socket descriptor is invalid.
Action:
Restart the BIPPA service. If the error persists,
contact technical support.
17
Cisco CAD Error Code Dictionary
Error
Description
BIPPA2018
Text:
Failed to stop <%ls> thread: <%ls>.
Type:
Error
Add’l Info:
Specified thread could not be stopped.
Text:
Verify if the machine is low on memory. Stop
unnecessary processes on the machine. Restart
the BIPPA service. If the error persists, contact
technical support.
Text:
<ThreadName> is deadlock.
Type:
Error
Add’l Info:
Specified thread is deadlocked.
Action:
Check if the machine is low on memory. Stop
unnecessary processes on the machine. Check
if the Recording and Statistics, VoIP Monitor, or
Recording & Playback services are down, hung,
or unreachable. Check if the Recording and
Statistics, VoIP Monitor, Mobile Agent Monitor,
or Recording & Playback clients are deadlocked.
Restart the application. If the error persists,
contact technical support.
Text:
Unable to allocate memory: <%ls>.
Type:
Warn
Add’l Info:
Unable to allocate memory.
Action:
Check system resource availability (CPU and
memory).
Text:
Unable to initialize preferences watcher: <%d>.
Type:
Warn
Add’l Info:
Unable to initialize preferences watcher. BIPPA
service is unable to detect changes to
preferences.
Action:
Do the following:
BIPPA2019
BIPPA3000
BIPPA3001
• Ensure that the user that the BIPPA service is
running as has permission to read from
preferences.
• Restart the BIPPA service.
• If this does not correct the problem, contact
technical support.
18
December 17, 2014
Error Messages
Error
Description
BIPPA3002
Text:
Unable to check preferences for local IP address
BIPPA should use to create its CORBA service:
<%d>.
Type:
Warn
Add’l Info:
Unable to check preferences for local IP address
BIPPA should use to create its CORBA service. It
will try again every 10 seconds.
Action:
If it continues to encounter this problem, do the
following:
• Ensure that the user that the BIPPA service is
running as has permission to read from
preferences.
• Restart the BIPPA service.
• If this does not correct the problem, contact
technical support.
BIPPA3003
Text:
Unable to get local IP address BIPPA should use
to create its CORBA service from preferences:
<%d>.
Type:
Warn
Add’l Info:
Unable to get local IP address BIPPA should use
to create its CORBA service from preferences.
Action:
If it continues to encounter this problem, do the
following:
• Ensure that the user that the BIPPA service is
running as has permission to read from
preferences.
• Restart the BIPPA service.
• If this does not correct the problem, contact
technical support.
December 17, 2014
19
Cisco CAD Error Code Dictionary
Error
Description
BIPPA3004
Text:
Unable to enable NT Event logging for
application name <%ls>.
Type:
Warn
Add’l Info:
Unable to enable NT Event logging for specified
application name.
Action:
Do the following:
• Ensure that the user that the BIPPA service is
running as has permission to read from
preferences.
• Restart the BIPPA service.
• If this does not correct the problem, contact
technical support.
BIPPA3005
Text:
Could not get <%ls> data from LDAP: <%ls>.
Type:
Warn
Add’l Info:
The BIPPA service cannot communicate with the
LDAP service or the data was not found in LDAP
service.
Action:
Do the following:
• Nothing needs to be done if the data type is
marked as optional. Default values will be
used.
• Verify that the LDAP service is running. If not,
start it (via LDAP Monitor service).
• (UCCE only) Verify that LDAP service has
been populated using CAD Configuration
Setup.
• Restart LDAP service (via LDAP Monitor
service).
• Restart BIPPA service.
• Verify the data exists in LDAP. If the data
does not exist, it might need to be added
using the Sync service (for agent and team
information), Cisco Desktop Administrator
(for workgroup and other settings), from
previous backups/upgrades, or reinstall CAD.
• If this does not correct the problem, contact
technical support.
20
December 17, 2014
Error Messages
Error
Description
BIPPA3006
Text:
Internal error: Unknown format for icon file
<%ls>.
Type:
Warn
Add’l Info:
Specified icon file has unknown file format.
Action:
Do the following:
• Ensure the file is an ICO or PNG file.
• Reload or replace icon file if needed.
• If this does not correct the problem, contact
technical support.
BIPPA3007
Text:
Internal error: Unable to load <%ls> icon file with
<%ls> format and <%d> size.
Type:
Warn
Add’l Info:
Unable to load icon file with specified format and
size.
Action:
Do the following:
• Ensure the file is an ICO file.
• Ensure the file has an icon of specified size.
• Reload or replace icon file if needed.
• If this does not correct the problem, contact
technical support.
BIPPA3008
Text:
Internal error: Could not convert ICO icon <%ls>
index <%d> to PNG icon <%ls>.
Type:
Warn
Add’l Info:
Unable to convert ICO icon with at specified
index into PNG icon.
Action:
Do the following:
• Ensure the file is an ICO file.
• Ensure the file has an icon at specified index.
• Reload or replace icon file if needed.
• If this does not correct the problem, contact
technical support.
December 17, 2014
21
Cisco CAD Error Code Dictionary
Error
Description
BIPPA3009
Text:
Internal error: Could not read file <%ls>.
Type:
Warn
Add’l Info:
Unable to read specified file.
Action:
Do the following:
• Ensure the file exists.
• Ensure the file is readable by user BIPPA
service is running as.
• Restart BIPPA service.
BIPPA3010
BIPPA3011
Text:
Internal error: PNG icon file <%ls> is empty.
Type:
Warn
Add’l Info:
Specified PNG icon file is empty.
Action:
Reload or replace PNG icon with non empty icon
file.
Text:
Internal error: Could not write file <%ls>: <%ls>.
Type:
Warn
Add’l Info:
Unable to write specified file.
Action:
Do the following:
• Ensure the directory exists.
• Ensure the file/directory is writable by user
BIPPA service is running as.
• Restart BIPPA service.
BIPPA3012
Text:
Internal error: Could not convert ICO icon <%ls>
to large PNG icon <%ls>. Using normal icon
instead.
Type:
Warn
Add’l Info:
Unable to convert ICO icon to large PNG icon.
Action:
Do the following:
• Ensure the file is an ICO file.
• Ensure the file has a small image in index 0
and large image in index 1.
• Reload or replace icon file if needed.
• If this does not correct the problem, contact
technical support.
22
December 17, 2014
Error Messages
Error
Description
BIPPA3013
Text:
There are no more licenses available.
Type:
Warn
Add’l Info:
There are no more licenses available.
Action:
Do the following:
• Wait a few minutes and retry.
• Agents logged out of extension mobility
without logging out from CAD or IPPA. These
agents are still logged in but in Not Ready
state. For CAD, it will continue to use up the
license until CAD exits. For IPPA, it will
continue to use up the license until BIPPA
service is restarted or the agents login again
and logout properly.
BIPPA3014
Text:
Internal error: Icon file <%ls> not found for
button type <%ls>.
Type:
Warn
Add’l Info:
Could not find specified icon file for button type.
If the large icon file is missing but the normal
icon file exists, the normal icon file is used for
large icon also.
Action:
Do the following:
• Ensure the file exists.
• If this does not correct the problem, contact
technical support.
December 17, 2014
23
Cisco CAD Error Code Dictionary
Error
Description
BIPPA3015
Text:
Unable to send CTI action <%ls> for agent %ls
<%ls>: <%ls>.
Type:
Warn
Add’l Info:
Unable to send specified CTI action to CTI
service for specified agent/extension because of
specified error.
Action:
Do the following:
• Ensure the CTI service is running, active, and
reachable from BIPPA service computer.
• Check that the CTI service is a supported
version for this version of BIPPA service.
• If this does not correct the problem, contact
technical support.
BIPPA3016
Text:
Internal error: CTI request ID <%d> and
response ID <%d> do not match for agent %ls
<%ls>.
Type:
Warn
Add’l Info:
The IDs of response to CTI request do not match
for specified agent ID/extension.
Action:
Do the following:
• Retry CTI action to see if it happens again.
• Restart BIPPA service.
• If this does not correct the problem, contact
technical support.
BIPPA3017
24
Text:
CTI action <%ls> failed for agent %ls <%ls>:
<%d> <%ls>.
Type:
Warn
Add’l Info:
Specified CTI action failed for specified agent
ID/extension because of specified error.
Action:
Check the error code and description for cause
of problem.
December 17, 2014
Error Messages
Error
Description
BIPPA3018
Text:
Maximum conference parties reached for agent
extension <%ls>: <%d><%ls>.
Type:
Warn
Add’l Info:
The maximum conference parties has been
reached for specified agent extension.
Action:
Do the following:
• Increase the maximum number of
conference parties allowed for the extension.
• Do not attempt to conference more than
maximum conference parties allowed.
BIPPA3019
Text:
BIPPA client unable to communicate with BIPPA
service: CORBA error <%ls>.
Type:
Warn
Add’l Info:
BIPPA client unable to communicate with BIPPA
service because of specified error.
Action:
Do the following:
• Ensure BIPPA service is running and active.
• Run Network Checks specified in the CAD
Troubleshooting Guide to ensure BIPPA
service is reachable from client computer.
• Restart BIPPA service, wait until it is running
and active before restarting BIPPA client.
BIPPA3020
Text:
BIPPA client at IP address <%ls> port <%d> is
unable to connect because the client is at
version <%ls> while service is at version <%ls>.
Type:
Warn
Add’l Info:
BIPPA client unable to communicate with BIPPA
service because they are of different version.
Action:
Do the following:
• The client has to shutdown and restart again.
• A BIPPAClient.jar of different version cached
by the browser is being used instead of the
one from BIPPA server. Run Clear Browser
Cache specified in the CAD Troubleshooting
Guide to remove the cached jars.
December 17, 2014
25
Cisco CAD Error Code Dictionary
Error
Description
BIPPA3021
Text:
Timeout while waiting for changed LDAP data to
be replicated to currently connected LDAP
service for synchronize key <%ls>.
Type:
Warn
Add’l Info:
BIPPA service could not get all the changed
LDAP data from a replicated LDAP service before
timeout (20 seconds) occurred.
Action:
Verify LDAP replication is working. Restart BIPPA
service.
Text:
<Rascal/VoIP/Recording/EEM> has reached
max size <size>. Discarding received request
<request>.
Type:
Warn.
Add’l Info:
Unable to add received module request to
queue because the queue has reached in
maximum size. Requests are being received
faster than they are being processed.
Action:
Run CPU checks. Check if Rascal/VoIP/
Recording/EEM is hung. Check if BIPPA is hung.
Text:
Cannot get configuration information for <%s>
component from the BIPPA service.
Type:
Fatal
Add’l Info:
The BIPPA service did not respond within 5
seconds. This could be due to network latency or
a slow BIPPA service.
Action:
Check the connection speed to rule out network
latency. If the connection is slow, try a faster
connection. If a faster connection does not
improve latency, look for other possible causes
for the latency. Check the CPU usage of the
BIPPA service. If the CPU usage is high, check
the debugging threshold for the BIPPA service.
The debugging threshold may be set too high.
BIPPA3023
BIPPAC1000
26
December 17, 2014
Error Messages
Error
Description
BIPPAC1002
Text:
Cannot connect to BIPPA service.
Type:
Fatal
Add’l Info:
Cannot connect to the BIPPA service within 8
seconds.
Action:
Verify that the BIPPA service is running and
active for the URL used. Verify that port 59012,
which is used by the BIPPA service, is not
blocked. Verify the status of the port by
telnetting to the server using port 59012 from a
DOS command window on the client PC. Check
the connection speed to rule out network
latency. If the connection is slow, try a faster
connection. If a faster connection does not
improve latency, look for other possible causes
for the latency. Check the CPU usage of the
BIPPA service. If the CPU usage is high, check
the debugging threshold for the BIPPA service.
The debugging threshold may be set too high.
Text:
Received an invalid event <%s> from the BIPPA
service.
Type:
Warn
Add’l Info:
A configuration error resulting in invalid data
sent from the BIPPA service or client is of
different version than service.
Text:
Cannot login agent. Cause <%d:%s>.
Type:
Warn
Add’l Info:
The BIPPA service cannot log in the agent
because of the specified error.
Action:
Depends on the error code and description cited
in the text.
BIPPAC3000
BIPPAC3003
December 17, 2014
27
Cisco CAD Error Code Dictionary
Error
Description
BIPPAC3004
Text:
<%s> component did not get response from
BIPPA service for <%s> request.
Type:
Warn
Add’l Info:
The specified component did not get a response
from the BIPPA service for the specified request
within 5 seconds.
Action:
Check the connection speed to rule out network
latency. If the connection is slow, try a faster
connection. If a faster connection does not
improve latency, look for other possible causes
for the latency. Check the CPU usage of the
BIPPA service. If the CPU usage is high, check
the debugging threshold for the BIPPA service.
The debugging threshold may be set too high.
Text:
Applet context passed to <%s> component is
null.
Type:
Warn
Add’l Info:
The specified component received a null applet
context that prevents the component from
performing browser operations.
Action:
Check the security settings for your web browser
as described in the installation guide. Log out
and restart the browser. If this error persists,
contact technical support.
Text:
LRM Error: Failed to initialize LRM Client.
Type:
Error
Add’l Info:
AcmiClient is unable to initialize LRM manager
for connecting to LRM service.
Action:
Verify LRM service is running and active.
Perform network checks.
Text:
LRM Error: Failed to register for CRS CTI events.
Type:
Error
Add’l Info:
AcmiClient is unable to register with LRM service
for CRS CTI events.
Action:
Verify LRM service is running and active.
Perform network checks.
BIPPAC3005
CACMI2000
CACMI2001
28
December 17, 2014
Error Messages
Error
Description
CACMI2001
Text:
Error occured while encrypting password, will
attempt plain text login.
Type:
Error
Add’l Info:
AcmiClient failed to encrypt the password.
Action:
Verify your password is under the length limit
and retry login.
Text:
LDAP Error: Failed to get <%ls>: %ls
Type:
Warn
Add’l Info:
AcmiClient is unable to get specified information
from LDAP service.
Action:
Check if LDAP service is running. Check whether
specified information exists in LDAP.
Text:
LDAP Error: Could not find for host for service
type.
Type:
Warn
Add’l Info:
CadAcmiClient is unable to get specified
information for specified host of specified
service type from LDAP service.
Action:
Verify if LDAP service is running. Check whether
specified information exists in LDAP.
Text:
LDAP Error: No host defined in LDAP.
Type:
Warn
Add’l Info:
There are no host defined for ACMI services in
LDAP service.
Action:
Verify if LDAP service is running. Check whether
specified information exists in LDAP.
Text:
Connector cannot retrieve <%s> event
information from socket message.
Type:
Error
Add’l Info:
Connector cannot retrieve specified event
information from the socket message.
Action:
Look at the status of the connection between
CAD and the EEM applet.
CACMI3000
CACMI3001
CACMI3002
CADEEMCONNECTOR2000
December 17, 2014
29
Cisco CAD Error Code Dictionary
Error
Description
CADEEMCONNECTOR2001
Text:
Insufficient memory to run EEM applet: <%s>.
Type:
Error
Add’l Info:
There is insufficient memory to run the EEM
applet.
Action:
Verify that the client PC has enough memory. If
the PC has enough memory, verify that JVM has
sufficient memory to run the EEM applet.
Text:
Caught <%s> which should not happen.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
An exception was thrown in the event handler:
%s
Type:
Warn
Add’l Info:
An error occurred in the event handler.
Action:
See the error text for details.
Text:
LRMClient could not get the list of LRM Server
profiles from LDAP, connection may fail. Reason:
Type:
Error
Add’l Info:
The CADLRM Client could not get a list of LRM
server profiles from LDAP.
Action:
Verify that LRM Server is running. Verify that
LDAP is up and replication is working correctly.
Verify that the client can connect to LDAP. Verify
that the ServerProfile entries are located in
LDAP.
CADEEMCONNECTOR2002
CADEEMCONNECTOR3000
CADLRM2000
30
December 17, 2014
Error Messages
Error
Description
CADLRM2003
Text:
LRMClient could not get the list of LRM Servers
to connect to.
Type:
Error
Add’l Info:
The CADLRM Client could not find an LRM
Server to connect to.
Action:
Verify that LRM Server is running. Verify that
LDAP is up and replication is working correctly.
Verify that the client can connect to LDAP. Verify
that the ServerProfile entries are located in
LDAP. Verify that LDAP Hosts are configured
correctly.
Text:
LRMClient could not get the list of profiles from
LDAP, connection may fail. Reason:
Type:
Error
Add’l Info:
The CADLRM Service could not get a list of
server profiles from LDAP.
Action:
Verify that LDAP is up and replication is working
correctly. Verify that the server can connect to
LDAP. Verify that the ServerProfile entries are
located in LDAP.
Text:
The SocketService could not be started. Reason:
Type:
Fatal
Add’l Info:
The SocketService could not be started.
Action:
See debug log for details, validate that the
service IP Address and Port are configured
correctly, and that the service is not already
running. Restart the service.
Text:
The master selection strategy could not be
created. Reason:
Type:
Fatal
Add’l Info:
Could not create master selection strategy.
Action:
Verify host addresses in site setup.
CADLRM2006
CADLRMS1000
CADLRMS1001
December 17, 2014
31
Cisco CAD Error Code Dictionary
Error
Description
CADLRMS2001
Text:
LRM could write the Bundle to TUP.ini. Reason:
Type:
Error
Add’l Info:
The CADLRM Service could not write the offering
to TUP.ini.
Action:
Verify that TUP.ini is in the correct location and
that LRMServer has write permissions.
Text:
LRM failed to get recording license limits from
CRS, the limit will be set to 0.
Type:
Error
Add’l Info:
The CADLRM Service could not get the
Recording license limits from CRS.
Action:
Check that Recording licenses are configured
and that LRM has access to CRS.
Text:
LRM could not write the Bundle to LDAP.
Reason:
Type:
Error
Add’l Info:
The CADLRM Service could not write the offering
to LDAP.
Action:
Check that Default Data in LDAP is populated
and LRMServer is connected to LDAP.
Text:
Initiating failover due to problems with
Type:
Error
Add’l Info:
A service failed too many times and a manual
failover was initiated.
Action:
Verify status of failed service.
Text:
LRM could not write server profile to LDAP,
clients may not be able to connect.
Type:
Warn
Add’l Info:
CADLRM Service could not write the server
profile information to LDAP. Clients may not be
able to connect.
Action:
Verify that LDAP is running and that LRM can
write to it.
CADLRMS2002
CADLRMS2004
CADLRMS2005
CADLRMS3000
32
December 17, 2014
Error Messages
Error
Description
CDAU12069
Text:
Maximum Outbound Attachments Size is more
than the allowed Maximum Outbound
Attachment size (50 MB).
Type:
Error
Add’l Info:
The Maximum Outbound Attachments Size is
greater than the allowed maximum of 50 MB.
Action:
Enter a value less than or equal to 50 MB.
Text:
Select a VoIP Monitor Service. --Select-- is not a
valid choice.
Type:
Error
Add’l Info:
The Remove button was clicked without
selecting a VoIP Monitor Service to remove.
Action:
Select a VoIP Monitor Service and then click
Remove.
Text:
Select a Recording & Playback Service. --Select-is not a valid choice.
Type:
Error
Add’l Info:
The Remove button was clicked without
selecting a Recording & Playback Service to
remove.
Action:
Select a Recording & Playback service and then
click Remove.
Text:
Error while trying to load data. Ensure that the
system path includes the location of the
WebAdminLib.dll.
Type:
Fatal
Add’l Info:
Error indicating that the location of the
WebAdminLib.dll is not added to the System
path.
Action:
Add the location of the WebAdminLib.dll 
(C:\Program Files\Cisco\Desktop\bin) to the
Path environment variable.
CDAU12070
CDAU12071
CDAUI1000
December 17, 2014
33
Cisco CAD Error Code Dictionary
Error
Description
CDAUI1001
Text:
Error while trying to load data. Ensure that the
system path includes the location of the
LDAPClientDLL.dll.
Type:
Fatal
Add’l Info:
Error indicating that the location of the
LDAPClientDLL.dll is not added to the System
path.
Action:
Add the location of the LDAPClientDLL.dll 
(C:\Program Files\Cisco\Desktop\bin) to the
Path environment variable.
Text:
Critical installation files are missing. Contact
technical support.
Type:
Fatal
Add’l Info:
Some important files needed to access Cisco
Desktop Presence Administrator are missing.
Action:
Contact technical support about the missing
files.
Text:
An error has occurred. Contact technical
support.
Type:
Error
Add’l Info:
Generic error message when no known error is
encountered.
Action:
Get the log files and contact technical support.
Text:
Error while trying to load data. Ensure that the
system path includes the location of the
WebAdminLib.dll.
Type:
Error
Add’l Info:
Error indicating that the location of the
WebAdminLib.dll is not added to the System
path.
Action:
Add the location of the WebAdminLib.dll 
(C:\Program Files\Cisco\Desktop\bin) to the
Path environment variable.
CDAUI1002
CDAUI2000
CDAUI2011
34
December 17, 2014
Error Messages
Error
Description
CDAUI2012
Text:
Error while trying to load data. Ensure that the
system path includes the location of the
LDAPClientDLL.dll.
Type:
Error
Add’l Info:
Error indicating that the location of the
LDAPClientDLL.dll is not added to the System
path.
Action:
Add the location of the LDAPClientDLL.dll 
(C:\Program Files\Cisco\Desktop\bin) to the
Path environment variable.
Text:
The contact list name you entered is already in
use. Enter a unique contact list name.
Type:
Error
Add’l Info:
A Contact List with that name already exists.
Contact List Name must be unique.
Action:
A Contact List with that name already exists.
Enter another unique name for the Contact List.
Text:
LDAP default data error: the password is not in
LDAP.
Type:
Error
Add’l Info:
Default Password is missing in LDAP.
Action:
Password that is required for authentication is
missing from LDAP. Contact technical support.
Text:
The username or password you entered is
incorrect. Try again.
Type:
Error
Add’l Info:
Authentication error. Username or password is
incorrect.
Action:
Enter the correct username and password for
authentication to Cisco Desktop Administrator.
Text:
Old password is incorrect. Try again.
Type:
Error
Add’l Info:
User entered Old password didn't match with the
current password.
Action:
Enter the correct current password in the Old
Password field.
CDAUI2014
CDAUI2015
CDAUI2016
CDAUI2019
December 17, 2014
35
Cisco CAD Error Code Dictionary
Error
Description
CDAUI2020
Text:
Spaces are not allowed in passwords. Try again.
Type:
Error
Add’l Info:
User entered a space in the new password or
confirm password field. Space is not an allowed
character.
Action:
Space is not an allowed character. Enter another
new password that does not have a space in it.
Text:
Entries in New Password and Confirm Password
fields do not match. Try again.
Type:
Error
Add’l Info:
User entered New Password and Confirm
Password strings did not match.
Action:
Enter the same string in New Password and
Confirm Password fields.
Text:
A Host/IP address cannot be entered in more
than one Host/IP Address field. %s entered in
more than one Host/IP Address field. Try again.
Type:
Error
Add’l Info:
An Host/IP address is duplicated in the Host/IP
address sections.
Action:
Delete the duplicated entry of the Host/IP
address.
Text:
Search Criteria error. For Included, select either
True or False.
Type:
Error
Add’l Info:
User selected the search criteria as 
Included = True and Included = False which is
not a valid combination.
Action:
Use either Included = True or 
Included = False search criteria. Both are not
allowed at the same time.
CDAUI2021
CDAUI2023
CDAUI2027
36
December 17, 2014
Error Messages
Error
Description
CDAUI2028
Text:
The external contact URI you entered is already
in use. Enter a unique URI.
Type:
Error
Add’l Info:
An External Contact with the specified URI
already exists. URI is a unique field for the Cisco
Unified Presence Server External Contact.
Action:
An External Contact with the specified URI
already exists. Enter another unique URI for the
External Contact.
Text:
Incorrect password. Try again.
Type:
Error
Add’l Info:
Authentication error. Entered password did not
match.
Action:
Enter the correct password for authentication.
Text:
An error has occurred. Contact your system
administrator.
Type:
Error
Add’l Info:
Generic error message when no known error is
encountered.
Action:
Contact system administrator or technical
support.
Text:
Error communicating with the Unified Presence
Server.
Type:
Error
Add’l Info:
Error communicating with the Unified Presence
Server.
Action:
Check the IP/Host Name specified in Cisco
Unified Presence settings.
CDAUI2029
CDAUI2032
CDAUI2033
If valid, try connecting to Unified Presence server
with the same settings.
December 17, 2014
37
Cisco CAD Error Code Dictionary
Error
Description
CDAUI2034
Text:
Invalid Cisco Unified Presence Cluster user
credentials. Configured user must be able to run
SOAP queries.
Type:
Error
Add’l Info:
Configured user doesn't have permissions to run
SOAP queries.
Action:
Enter the credentials of the user who has
permissions to run SOAP queries.
Text:
An instantiation error has occured.
Type:
Error
Add’l Info:
An Object instantiation error has occurred.
Action:
LDAP data error. Contact technical support.
Text:
A security access error has occurred. Contact
technical support.
Type:
Error
Add’l Info:
Security access error occurred.
Action:
Contact technical support.
Text:
A no such method error has occurred. Contact
technical support.
Type:
Error
Add’l Info:
Method that is referred is not existing.
Action:
Contact technical support.
Text:
An illegal argument error has occurred. Contact
technical support.
Type:
Error
Add’l Info:
Argument that is passed is not valid.
Action:
Contact technical support.
Text:
An object instantiation error has occurred.
Contact technical support.
Type:
Error
Add’l Info:
Object instantiation error.
Action:
Contact technical support.
CDAUI2036
CDAUI2042
CDAUI2043
CDAUI2044
CDAUI2045
38
December 17, 2014
Error Messages
Error
Description
CDAUI2046
Text:
An illegal access error has occurred. Contact
technical support.
Type:
Error
Add’l Info:
Illegal access error occurred.
Action:
Contact technical support.
Text:
An object invokation error has occurred. Contact
technical support.
Type:
Error
Add’l Info:
Object invocation error occurred.
Action:
Contact technical support.
Text:
Class definition is not found. Ensure that the
system path includes the location of the
required DLLs. Contact technical support.
Type:
Error
Add’l Info:
Error indicating that he referred class is not
found. Required DLLs location is not added to
the System path.
Action:
Add the location of the required dlls 
(C:\Program Files\Cisco\Desktop\bin) to the
Path environment variable.
Text:
A no such field error has occurred. Contact
technical support.
Type:
Error
Add’l Info:
No such field error occurred.
Action:
Contact technical support.
Text:
An LDAP error has occured. Contact technical
support.
Type:
Error
Add’l Info:
An LDAP error occurred.
Action:
Contact technical support.
CDAUI2047
CDAUI2048
CDAUI2049
CDAUI2050
December 17, 2014
39
Cisco CAD Error Code Dictionary
Error
Description
CDAUI2051
Text:
Error connecting to LDAP: %s. Contact technical
support.
Type:
Error
Add’l Info:
An LDAP connection error occurred.
Action:
Check the LDAP connection credentials and test
the LDAP connection. Contact technical support.
Text:
Error with the connection to LDAP: %s. Contact
technical support.
Type:
Error
Add’l Info:
An LDAP connection error occurred.
Action:
Check the LDAP connection credentials and test
the LDAP connection. Contact technical support.
Text:
No %s was found corresponding to domain
objects of type %s.
Type:
Error
Add’l Info:
Object error occurred.
Action:
Contact technical support.
Text:
An error occured while casting a class. Contact
technical support.
Type:
Error
Add’l Info:
Class type cast error occurred.
Action:
Contact technical support.
Text:
A %s class not found error has occured. Contact
technical support.
Type:
Error
Add’l Info:
Class not found error occurred.
Action:
Contact technical support.
Text:
Error reading data from LDAP. Contact technical
support.
Type:
Error
Add’l Info:
Error occurred while reading data from LDAP.
Action:
Check the LDAP connection credentials and test
the LDAP connection. Contact technical support.
CDAUI2052
CDAUI2053
CDAUI2054
CDAUI2055
CDAUI2056
40
December 17, 2014
Error Messages
Error
Description
CDAUI2057
Text:
LDAP service is down. Contact technical support.
Type:
Error
Add’l Info:
LDAP service is down.
Action:
Restart LDAP or contact technical support.
Text:
Enter at least one character other than space
character in the Contact List Name field.
Type:
Error
Add’l Info:
Only spaces are entered in the Contact List
Name field.
Action:
Enter at least one character other than space
character in the Contact List Name field.
Text:
Enter at least one character other than space
character in the URI field.
Type:
Error
Add’l Info:
Only spaces are entered in the URI field.
Action:
Enter at least one character other than space
character in the URI field.
Text:
Enter at least one character other than space
character in the Contact List Description field.
Type:
Error
Add’l Info:
Only spaces are entered in the Contact List
Description field.
Action:
Enter at least one character other than space
character in the Contact List Description field.
CDAUI2061
CDAUI2062
CDAUI2065
December 17, 2014
41
Cisco CAD Error Code Dictionary
Error
Description
CDAUI2067
Text:
Search did not complete successfully, and only
partial results are displayed. Contact technical
support.
Type:
Error
Add’l Info:
SME search did not complete successfully and
only partial results are displayed.
Action:
Either a Cisco Unified Presence Server search or
an LDAP search failed.
Verify that the user specified on Cisco Unified
Presence Server settings page has permissions
to do SOAP query.
Verify that the LDAP settings are correct and
check the LDAP connection.
CDAUI2068
42
Text:
Unable to save your changes to the work flow
group. The maximum number of contact lists
that can be added to a work flow group is 25.
Type:
Error
Add’l Info:
Added more than the allowed number of contact
lists (25) to a work flow group.
Action:
Add only up to 25 contact lists to a work flow
group.
December 17, 2014
Error Messages
Error
Description
CDAUI2082
Text:
At least one error has occurred during the
manual synchronization of directory services.
Contact technical support.
Type:
Error
Add’l Info:
Manual Synchronization always fails. Because
there are a large number of agents, the Sync
service times out while reading all agents from
LDAP.
Action:
Increase LDAP Request Timeout on the server
using the set uccx cad prefs SiteSetup “LDAP
Request Timeout” <Timeout> CLI command.
See the CLI Command Syntax and SiteSetup
sections in the Cisco CAD Troubleshooting Guide
for more information. The value for Timeout
must be in seconds. Because this value needs to
be derived based on the number of agents and
network speed, you can increase the value in
steps of 5 seconds to arrive at a value that does
not cause timeout.
Text:
Version mismatch.
Type:
Error
Add’l Info:
Server and uploading client versions do not
match.
Action:
None.
Text:
Client mismatch.
Type:
Error
Add’l Info:
Client file to upload has an invalid name.
Action:
None.
Text:
Exception: %s
Type:
Error
Add’l Info:
Log exception.
Action:
None.
Text:
%s
Type:
Error
Add’l Info:
Log stack trace.
Action:
None.
CLUP2000
CLUP2001
CLUP2002
CLUP2003
December 17, 2014
43
Cisco CAD Error Code Dictionary
Error
Description
CSI1000
Text:
Unable to start Resiprocate thread. Caught an
exception, exception message.
Type:
Fatal
Add’l Info:
The main resiprocate Thread could not be
started.
Action:
None.
Text:
Unable to retrieve presence Server information.
Error Code.
Type:
Fatal
Add’l Info:
The presence Server information cannot be
retrieved by GetPresenceSvrConfig().
Action:
None.
Text:
An unexpected exception occurred.
Type:
Error
Add’l Info:
An unexpected exception occurred.
Action:
See the log for other errors. Make sure that all
appropriate Cisco services are up and running.
Check the log files of other Cisco related
services for errors. Check the System Event
Viewer for system errors. Check system resource
availability (memory, CPU). Check for network
communication errors.
Text:
Failed to connect to LDAP.
Type:
Error
Add’l Info:
Failed to connect to LDAP.
Action:
Verify that LDAP server is up and running.
Text:
Failed to retrieve from LDAP.
Type:
Error
Add’l Info:
Failed to retrieve specified value from LDAP
Action:
Verify that LDAP server is up and running. Verify
that the system is completely configured
CSI1001
CSI2000
CSI2001
CSI2002
44
December 17, 2014
Error Messages
Error
Description
CSI2003
Text:
Failed to add/update to LDAP.
Type:
Error
Add’l Info:
Failed to add value to LDAP
Action:
Verify that LDAP server is up and running. Verify
that the system is completely configured
Text:
Failed to read contact groups for workflow group
from LDAP.
Type:
Error
Add’l Info:
Failed to contact groups for specified workflow
group value from LDAP
Action:
Verify that LDAP server is up and running. Verify
that the system is completely configured
Text:
Failed to read contacts for contact group from
LDAP.
Type:
Error
Add’l Info:
Failed to read contacts for specified contact
group from LDAP
Action:
Verify that LDAP server is up and running. Verify
that the system is completely configured
Text:
Failed to read profile for (%ls:%ls) from LDAP.
Type:
Error
Add’l Info:
Failed to read profile for specified user from
LDAP
Action:
Verify that LDAP server is up and running. Verify
that the system is completely configured
Text:
Failed to read workflow group settings for
(%ls:%ls) from LDAP.
Type:
Error
Add’l Info:
Failed to read workflow settings for specified
user from LDAP
Action:
Verify that LDAP server is up and running. Verify
that the system is completely configured
CSI2004
CSI2005
CSI2006
CSI2007
December 17, 2014
45
Cisco CAD Error Code Dictionary
Error
Description
CSI2008
Text:
Failed to add/update in LDAP.
Type:
Error
Add’l Info:
Failed to write specified field in LDAP
Action:
Verify that LDAP server is up and running. Verify
that the system is completely configured
Text:
Failed to delete in LDAP.
Type:
Error
Add’l Info:
Failed to delete specified field in LDAP
Action:
Verify that LDAP server is up and running. Verify
that the system is completely configured
Text:
Failed to delete in LDAP.
Type:
Error
Add’l Info:
Failed to delete specified field in LDAP
Action:
Verify that LDAP server is up and running. Verify
that the system is completely configured
Text:
Failed to search for contacts in LDAP. Type (%d).
Type:
Error
Add’l Info:
LDAP Search for Contacts Failed
Action:
Verify that LDAP server is up and running. Verify
that the system is completely configured
Text:
Invalid CUP Server version for host.
Type:
Error
Add’l Info:
Invalid version of CUPS
Action:
Verify that LDAP server is up and running. Verify
that the system is completely configured
Text:
Error preparing CURL.
Type:
Error
Add’l Info:
There was a problem preparing the CURL
connection.
Action:
Read the error message for a description. Check
the log for other errors. Check for network
communication errors.
CSI2009
CSI2010
CSI2011
CSI2012
CSI2013
46
December 17, 2014
Error Messages
Error
Description
CSI2014
Text:
Error performing CURL action.
Type:
Error
Add’l Info:
There was a problem performing the CURL
action.
Action:
Read the error message for a description. Check
the log for other errors. Check for network
communication errors.
Text:
Error in Request to CUP Server Port Error.
Type:
Error
Add’l Info:
An error occured querying the specified CUP
Server.
Action:
See text in error for more details. Check system
resource availability (CPU and memory). Check
for network connectivity issues.
Text:
XML passed to parser is empty.
Type:
Error
Add’l Info:
XML passed to parser is empty
Action:
Check CUP server status Check system resource
availability (CPU and memory). Check for
network connectivity issues.
Text:
Caught a splk_std::SplkXmlException. Exception
message.
Type:
Error
Add’l Info:
Caught a splk_std::SplkXmlException.
Action:
Read the error message for a description. Check
the log for other errors. Check system resource
availability (memory, CPU). Check for network
communication errors.
Text:
Caught a xercesc::XMLException. Exception
message.
Type:
Error
Add’l Info:
Caught a xercesc::XMLException.
Action:
Read the error message for a description. Check
the log for other errors. Check system resource
availability (memory, CPU). Check for network
communication errors.
CSI2015
CSI2016
CSI2017
CSI2018
December 17, 2014
47
Cisco CAD Error Code Dictionary
Error
Description
CSI2019
Text:
Caught a xercesc::DOMException. Exception
message.
Type:
Error
Add’l Info:
Caught a xercesc::DOMException.
Action:
Read the error message for a description. Check
the log for other errors. Check system resource
availability (memory, CPU). Check for network
communication errors.
Text:
Request failed. Request Error.
Type:
Error
Add’l Info:
Requested data not found
Action:
Check CUP server status Check system resource
availability (CPU and memory). Check for
network connectivity issues.
Text:
Invalid configuration. Exceeded maximum limit
of (%d) for (%s).
Type:
Error
Add’l Info:
Exceeded the maximum number of specified
config allowed.
Action:
Change configuration to match limits.
Text:
The SOAP message does not have tag name.
Type:
Warn
Add’l Info:
None.
Action:
None.
Text:
The SOAP message does not have tag name for
root tag.
Type:
Warn
Add’l Info:
None.
Action:
None.
CSI2020
CSI2021
CSI3000
CSI3001
48
December 17, 2014
Error Messages
Error
Description
CSI3002
Text:
Failed to retrieve from LDAP.
Type:
Warn
Add’l Info:
Failed to retrieve specified value from LDAP.
Field might be optional.
Action:
Verify that LDAP server is up and running. Verify
that the system is completely configured
Text:
Unable to load macro from LDAP.
Type:
Warn
Add’l Info:
A work flow action contained the name of a
keystroke macro but the macro does not exist.
Action:
If the macro has been delete on purpose, delete
the name of the macro from the action list(s).
Communication with Directory services has been
lost. Reestablish communication with directory
services.
Text:
Directory Services unable to write macro binary
to %ls
Type:
Warn
Add’l Info:
Communication with directory services was lost.
Action:
Reestablish communication.
Text:
Unable to macro, Directory Services returned an
error.
Type:
Warn
Add’l Info:
Communication with directory services was lost.
Action:
Reestablish communication and try again.
Text:
Error, not found. Directory Services data is
corrupt.
Type:
Warn
Add’l Info:
The data from Directory services is not correct.
Action:
Restore directory services from backup files.
DESK2000
DESK2002
DESK2003
DESK2004
December 17, 2014
49
Cisco CAD Error Code Dictionary
Error
Description
DESK2005
Text:
Error, action name missing for. Data from
Directory Services is incorrect.
Type:
Warn
Add’l Info:
Data in Directory Services database is not
correct and possibly is corrupted.
Action:
Use restore utility to restore data.
Text:
Request to change agent state failed.
Type:
Warn
Add’l Info:
CTIOS error or ICM error
Action:
Restart CTIOS to give a second try. Look into
CTIOS error for more details
Text:
Request to log the agent in failed.
Type:
Warn
Add’l Info:
CTIOS error or ICM error
Action:
Restart CTIOS to give a second try. Look into
CTIOS error for more details
Text:
Unable to retrieve the Data Fields from Directory
Services.
Type:
Warn
Add’l Info:
Data received from Directory Services is
incorrect or corrupt.
Action:
Use utility to restore Directory Services data
from backup.
Text:
Unable to read icon profile from LDAP.
Type:
Warn
Add’l Info:
Unable to read icon profile from LDAP.
Action:
None.
Text:
Unable to save to Enterprise Database.
Type:
Warn
Add’l Info:
Unable to save to Enterprise Database.
Action:
None.
DESK2006
DESK2007
DESK2009
DESK2010
DESK2011
50
December 17, 2014
Error Messages
Error
Description
DESK2012
Text:
Unable to Logout of RASCAL Server. Error
Message = %ls.
Type:
Warn
Add’l Info:
None.
Action:
None.
Text:
Unable to Logout of Desktop Monitoring. Error =
%d
Type:
Warn
Add’l Info:
Can't logout of Desktop monitoring.
Action:
See Desktop monitoring error message for more
details
Text:
Unable to Stop of Desktop Monitoring. Error =
%d
Type:
Warn
Add’l Info:
Unable to read icon profile from LDAP.
Action:
Can't stop desktop monitoring
Text:
Last try to get RASCAL Global ID to update
wrapup data. Error = %ls
Type:
Warn
Add’l Info:
Error getting RASCAL Global ID
Action:
See RASCAl error message for more details
Text:
Unable to update wrapup data to RASCAL: no
global ID.
Type:
Warn
Add’l Info:
Unable to update data to RASCAL
Action:
See if there is a call with callID
Text:
Unable to update wrapup data to RASCAL:
GID=%u Error=%ls.
Type:
Warn
Add’l Info:
Unable to update data to RASCAL
Action:
See if there is a call with callID
DESK2013
DESK2014
DESK2016
DESK2017
DESK2018
December 17, 2014
51
Cisco CAD Error Code Dictionary
Error
Description
DESK2019
Text:
Unable to get RASCAL Global ID for agent state
change.
Type:
Warn
Add’l Info:
Error from RASCAL server, Can't get RASCAL
global ID.
Action:
See RASCAL error message for more details
Text:
Last try was still unable to get RASCAL Global ID
for agent state change.
Type:
Warn
Add’l Info:
Fail to get RASCAL global ID
Action:
See RASCAL error message for more details
Text:
Unable to get enterprise data for callID <%lu>.
Type:
Warn
Add’l Info:
Enterprise server is down. Error from Enterprise
server.
Action:
Check the status of the Enterprise Service. Verify
CPU usage on server machine.
Text:
Unable to get a layout name for callID <%lu>.
Type:
Warn
Add’l Info:
Unable to retrieve the call layout name for
Enterprise Data.
Action:
Check the status of the Enterprise Service. Verify
CPU usage on server machine. Verify that the
layout name is valid and configured correctly.
Text:
Unable to update field <%ld> with data <%ls>
for callID <%lu>.
Type:
Warn
Add’l Info:
Unable to update the enterprise data field action
to the Enterprise Service.
Action:
Check the status of the Enterprise Service. Verify
CPU usage on server machine.
DESK2020
DESK2024
DESK2025
DESK2026
52
December 17, 2014
Error Messages
Error
Description
DESK2047
Text:
Blind Transfer Call Control Action - Complete
Transfer Failed.
Type:
Warn
Add’l Info:
Blind Transfer Call Control Action - Complete
Transfer Failed.
Action:
Check CTI server if it runs correctly
Text:
LRM Inactive Message received.
Type:
Warn
Add’l Info:
LRM Inactive Message received.
Action:
Restart LRM
Text:
Unable to read Agent ACD State Log report
settings.
Type:
Warn
Add’l Info:
LDAP monitor is not running
Action:
Restart LDAP monitor server
Text:
Unable to read Skill Statistics report settings.
Type:
Warn
Add’l Info:
LDAP monitor is not running
Action:
Restart LDAP monitor server
Text:
Unable to read Agent Detail report settings.
Type:
Warn
Add’l Info:
LDAP monitor is not running
Action:
Restart LDAP monitor server
Text:
Unable to start recording callID %d with error
%ls.
Type:
Warn
Add’l Info:
Recording server is not running correctly
Action:
Restart Recording server
DESK2048
DESK2049
DESK2050
DESK2051
DESK2052
December 17, 2014
53
Cisco CAD Error Code Dictionary
Error
Description
DESK2053
Text:
Attempted to start recording the callID, but
couldn't find the appearance.
Type:
Warn
Add’l Info:
No call appearance to do recording
Action:
Check to see if agent has valid call ID
Text:
Already recording a call at this agent.
Type:
Warn
Add’l Info:
Duplicate agent ID
Action:
Log supervisor out and log back in
Text:
Unable to stop recording callID %d with error
%ls.
Type:
Warn
Add’l Info:
Recording server is not running correctly
Action:
Restart Recording server
Text:
Attempted to stop recording the callID, but
couldn't find the appearance.
Type:
Warn
Add’l Info:
No call appearance to do recording
Action:
Check to see if agent has valid call ID
Text:
Error getting skill stats. PhoneDev Error.
Type:
Warn
Add’l Info:
No call appearance to do recording
Action:
Check to see if agent has valid call ID
Text:
Error setting volume level.
Type:
Warn
Add’l Info:
Error while setting volume.
Action:
Restart RASCAL and/or Application.
DESK2054
DESK2055
DESK2056
DESK2057
DESK2058
54
December 17, 2014
Error Messages
Error
Description
DESK2059
Text:
Blind Conference Call Control Action - Empty Call
ID.
Type:
Warn
Add’l Info:
When the action was attempted, there was no
associated call.
Action:
Make sure there is a call appearance and it is
selected before this action is executed.
Text:
Blind Conference Call Control Action - Calls is
invalid state.
Type:
Warn
Add’l Info:
When the action was attempted, the call not
either on hold or connected.
Action:
The associated call must be in a connected or
hold state.
Text:
Blind Conference Call Control Action - Setup
Conference Failed.
Type:
Warn
Add’l Info:
When attempting to set up the conference, a
failure status was returned.
Action:
Retry the action later
Text:
Blind Conference Call Control Action Destination Call ID is Empty Call ID.
Type:
Warn
Add’l Info:
Error while setting volume.
Action:
Restart RASCAL and/or Application.
Text:
Blind Conference Call Control Action - Complete
Conference Failed.
Type:
Warn
Add’l Info:
While waiting for the conference to connect, a
failure response was received.
Action:
Retry the action later.
DESK2060
DESK2061
DESK2062
DESK2063
December 17, 2014
55
Cisco CAD Error Code Dictionary
Error
Description
DESK2064
Text:
Unable to convert macro to binary from %ls: %ls
Type:
Warn
Add’l Info:
Unable to convert macro to binary
Action:
None.
Text:
Unable to read Agent Email Log Report settings.
Type:
Warn
Add’l Info:
LDAP monitor is not running
Action:
Restart LDAP monitor server
Text:
Unable to read Agent Email Detail Report
settings.
Type:
Warn
Add’l Info:
LDAP monitor is not running
Action:
Restart LDAP monitor server
Text:
Unable to obtain license type from LRM.
Type:
Warn
Add’l Info:
Can not obtain license from LRM
Action:
Check license usage and LRM server.
Text:
Unable to write agent state change to RASCAL:
GID=%u Error=%ls
Type:
Warn
Add’l Info:
Can't write agent state change to RASCAL.
Action:
See RASCAL error for more details
Text:
Unable to get RASCAL Global ID for logout agent
state change.
Type:
Warn
Add’l Info:
Can't get RASCAL global ID for logout
Action:
See RASCAL error message for more details
DESK2065
DESK2066
DESK2067
DESK2121
DESK2122
56
December 17, 2014
Error Messages
Error
Description
DESK2123
Text:
Unable to get RASCAL Global ID for new
appearance.
Type:
Warn
Add’l Info:
Can't get RASCAL global ID
Action:
See RASCAL error message for more details
Text:
Corrupt ActionList.
Type:
Warn
Add’l Info:
The ActionList is corrupted
Action:
Check the action list in LDAP
Text:
Action Index Corrupt
Type:
!Warn
Add’l Info:
The ActionList is corrupted
Action:
Check the action list in LDAP
Text:
Unable to write call data to RASCAL: GID= %u
Error=%ls
Type:
Warn
Add’l Info:
Can't write data to RASCAL
Action:
See RASCAL error message for more detail
Text:
Unable to get call layout for callID, callID was not
found.
Type:
Warn
Add’l Info:
Can't get call layout for callID due to callid is not
found
Action:
Check if the call returns valid CALLID
Text:
Unable to get call history for callID, callID was
not found.
Type:
Warn
Add’l Info:
Can't get call history due to callid is not found
Action:
check if the call returns valid CALLID
DESK2124
DESK2125
DESK2126
DESK2127
DESK2128
December 17, 2014
57
Cisco CAD Error Code Dictionary
Error
Description
DESK2129
Text:
Unable to update field number with data for
callID, field number is invalid
Type:
Warn
Add’l Info:
Field number is invalid
Action:
None.
Text:
Unable to update field number with data for
callID, callID was not found
Type:
Warn
Add’l Info:
Callid is not found
Action:
Check if the call has valid callid
Text:
Answer Call Control Action - Empty Call ID.
Type:
Warn
Add’l Info:
CallID is empty
Action:
Check if the call has a valid callID
Text:
Answer Call Control Action - Answer Failed.
Type:
Warn
Add’l Info:
Invalid callid
Action:
check if CAD answers the call with valid, correct
callID
Text:
Drop Call Control Action - Empty Call ID.
Type:
Warn
Add’l Info:
Empty CALLID
Action:
Check if the callid is valid
Text:
Drop Call Control Action - Drop Failed.
Type:
Warn
Add’l Info:
Invalid callid or releasing device id is in correct
Action:
check if the callid or releasing device id is valid
Text:
Touch Tones Call Control Action - Empty Call ID.
Type:
Warn
Add’l Info:
Empty callid
Action:
check if the call has valid callid
DESK2130
DESK2131
DESK2132
DESK2133
DESK2134
DESK2135
58
December 17, 2014
Error Messages
Error
Description
DESK2136
Text:
Touch Tones Call Control Action - Send DTMF
Failed.
Type:
Warn
Add’l Info:
Invalid callid
Action:
check if callid is valid
Text:
Make Call Control Action - Place Call Failed.
Type:
Warn
Add’l Info:
Invalid CALLID or Calling device ID
Action:
Check if callid or calling device ID is valid
Text:
Redirect Call Control Action - Empty Call ID.
Type:
Warn
Add’l Info:
Empty callid
Action:
check if callid is valid
Text:
Redirect Call Control Action - Call State not
Offering.
Type:
Warn
Add’l Info:
Call state is not in OFFERING state
Action:
check in delivered event the call state is
OFFERING state
Text:
Conference Call Control Action - Empty Call ID.
Type:
Warn
Add’l Info:
Empty callid
Action:
Check in conference event if callid is not empty
Text:
Super Transfer Call Control Action - Empty Call
ID.
Type:
Warn
Add’l Info:
Super Transfer Call Control Action - Empty Call
ID.
Action:
Check in conference event if the callid is not
empty
DESK2137
DESK2138
DESK2139
DESK2140
DESK2141
December 17, 2014
59
Cisco CAD Error Code Dictionary
Error
Description
DESK2142
Text:
Supervisor Transfer Call Control Action - Calls in
invalid state.
Type:
Warn
Add’l Info:
Call is in invalid state
Action:
check if call is in hold pending transfer for old
callID
Text:
Blind Transfer Call Control Action - Empty Call ID.
Type:
Warn
Add’l Info:
Blind Transfer Call Control Action - Empty Call ID.
Action:
Check if call id is not empty in transfer event
Text:
Blind Transfer Call Control Action - Calls is invalid
state.
Type:
Warn
Add’l Info:
Blind Transfer Call Control Action - Calls is invalid
state.
Action:
Check if the call is held pending transfer for old
callid
Text:
Blind Transfer Call Control Action - Setup
Transfer Failed.
Type:
Warn
Add’l Info:
Blind Transfer Call Control Action - Setup
Transfer Failed.
Action:
Check in transfer event if callid or callstate is in
valid state
Text:
Blind Transfer Call Control Action - Destination
Call ID is Empty Call ID.
Type:
Warn
Add’l Info:
Blind Transfer Call Control Action - Destination
Call ID is Empty Call ID.
Action:
Check if the callid of the transferred deviceID is
empty
DESK2143
DESK2144
DESK2145
DESK2146
60
December 17, 2014
Error Messages
Error
Description
DESK2162
Text:
Blind Conference Call Control Action Destination Call ID is Empty Call ID.
Type:
Warn
Add’l Info:
The wait for an active call ID to be the target for
the blind conference timed out.
Action:
Retry the action later
Text:
CORBA::TRANSIENT is raised minor:<%d>,
completion_status:<%d>, retries<%d>.
Type:
Warn
Add’l Info:
The wait for an active call ID to be the target for
the blind conference timed out.
Action:
Retry the action later
Text:
AtlUnadvise failed. Error code = 0x<%x>, <%ls>.
Type:
Warn
Add’l Info:
The wait for an active call ID to be the target for
the blind conference timed out.
Action:
Retry the action later
Text:
Could not read the Admin Password Set from
LDAP. Error code = <%d>, <%ls>
Type:
Warn
Add’l Info:
The wait for an active call ID to be the target for
the blind conference timed out.
Action:
Retry the action later
Text:
Could not save Admin Password to LDAP. Error
code = <%d>, <%ls>
Type:
Warn
Add’l Info:
The wait for an active call ID to be the target for
the blind conference timed out.
Action:
Retry the action later
DESK2200
DESK2201
DESK2202
DESK2203
December 17, 2014
61
Cisco CAD Error Code Dictionary
Error
Description
DESK2204
Text:
Could not read the server profile from LDAP.
Error code = <%d>, <%ls>
Type:
Warn
Add’l Info:
The wait for an active call ID to be the target for
the blind conference timed out.
Action:
Retry the action later
Text:
Could not read product offering from LDAP. Error
code = <%d>, <%ls>
Type:
Warn
Add’l Info:
The wait for an active call ID to be the target for
the blind conference timed out.
Action:
Retry the action later
Text:
General exception occurred.
Type:
Error
Add’l Info:
General Exception
Action:
Get the Dr Watson log, dump files and agent logs
sent to developer
Text:
Found callID %d, but call was NULL.
Type:
Error
Add’l Info:
Call node object is invalid.
Action:
Restart Cisco Supervisor Desktop.
Text:
Chat server error while barging in on deviceID %s
on callID %d.
Type:
Error
Add’l Info:
Internal error in the Chat service.
Action:
Restart the Chat service.
Text:
Chat server error while intercepting in on
deviceID %s on callID %d.
Type:
Error
Add’l Info:
Internal error in the Chat service.
Action:
Restart the Chat service.
DESK2206
DESK3000
DESK3001
DESK3002
DESK3003
62
December 17, 2014
Error Messages
Error
Description
DESK3004
Text:
Unable to monitor extension %s.
Type:
Error
Add’l Info:
The VoIP Monitor service is not running; a SPAN
port is not set up for the device; the phone is not
connected to the CallManager.
Action:
Restart the VoIP Monitor service.
Text:
Chat Login failed.
Type:
Error
Add’l Info:
Internal error in the Chat service.
Action:
Restart the Chat service.
Text:
Chat AddUser failed.
Type:
Error
Add’l Info:
Internal error in the Chat service.
Action:
Restart the Chat service.
Text:
Chat DropUser failed.
Type:
Error
Add’l Info:
Internal error in the Chat service.
Action:
Restart the Chat service.
Text:
Get Team Snapshot failed.
Type:
Error
Add’l Info:
Internal error in the Chat service.
Action:
Restart the Chat service.
Text:
GenericMessage failed.
Type:
Error
Add’l Info:
Internal error in the Chat service.
Action:
Restart the Chat service.
Text:
Chat SendMsg failed
Type:
Error
Add’l Info:
Internal error in the Chat service.
Action:
Restart the Chat service.
DESK3005
DESK3006
DESK3007
DESK3008
DESK3009
DESK3010
December 17, 2014
63
Cisco CAD Error Code Dictionary
Error
Description
DESK3011
Text:
Chat ChangeCallStatus failed.
Type:
Error
Add’l Info:
Internal error in the Chat service.
Action:
Restart the Chat service.
Text:
Chat ChangeOtherPartyCallStatus failed.
Type:
Error
Add’l Info:
Internal error in the Chat service.
Action:
Restart the Chat service.
Text:
Chat ChangeCallID failed.
Type:
Error
Add’l Info:
Internal error in the Chat service.
Action:
Restart the Chat service.
Text:
Chat SetAgentAcdState failed.
Type:
Error
Add’l Info:
Internal error in the Chat service.
Action:
Restart the Chat service.
Text:
Chat BargeIn failed.
Type:
Error
Add’l Info:
Internal error in the Chat service.
Action:
Restart the Chat service.
Text:
Intercept failed.
Type:
Error
Add’l Info:
Internal error in the Chat service.
Action:
Restart the Chat service.
Text:
Chat SetGenericAgentState failed.
Type:
Error
Add’l Info:
Internal error in the Chat service.
Action:
Restart the Chat service.
DESK3012
DESK3013
DESK3014
DESK3015
DESK3016
DESK3017
64
December 17, 2014
Error Messages
Error
Description
DESK3018
Text:
SendSpecialServerCommand failed.
Type:
Error
Add’l Info:
Internal error in the Chat service.
Action:
Restart the Chat service.
Text:
Unable to retrieve team names.
Type:
Error
Add’l Info:
Internal error in the Chat service.
Action:
Restart the Chat service.
Text:
Error received while attempting to read from
Directory Services.
Type:
Error
Add’l Info:
The LDAP Monitor service is not running.
Action:
Restart the LDAP Monitor service.
Text:
Error: get supervisor returned.
Type:
Error
Add’l Info:
The LDAP Monitor service is not running.
Action:
Restart the LDAP Monitor service.
Text:
Error: agentexists returned.
Type:
Error
Add’l Info:
The LDAP Monitor service is not running.
Action:
Restart the LDAP Monitor service.
Text:
Could not read Offering out of LDAP.
Type:
Error
Add’l Info:
Offering flag is not in LDAP.
Action:
Cisco Supervisor Desktop will run in Standard
offering.
Text:
Chat server error.
Type:
Error
Add’l Info:
Unknown Chat service error.
Action:
Restart the Chat service.
DESK3019
DESK3020
DESK3021
DESK3022
DESK3023
DESK3024
December 17, 2014
65
Cisco CAD Error Code Dictionary
Error
Description
DESK3025
Text:
InitCallChatClient failed.
Type:
Error
Add’l Info:
Chat service error.
Action:
Restart the Chat service.
Text:
Initialize failed with error.
Type:
Error
Add’l Info:
Chat service error.
Action:
Restart the Chat service. See the error
description for more details.
Text:
Unable to Login to RASCAL Server.
Type:
Error
Add’l Info:
The Recording and Statistics service is not
running.
Action:
Restart the Recording and Statistics service.
Text:
Chat server error while adding user.
Type:
Error
Add’l Info:
Chat service error.
Action:
Restart the Chat service.
Text:
Chat server error while logging in.
Type:
Error
Add’l Info:
Chat service error.
Action:
Restart the Chat service.
Text:
Unable to connect to Enterprise.
Type:
Error
Add’l Info:
Enterprise service error.
Action:
Restart the Enterprise service.
Text:
CBrowserFrame::OnCreate: Major error exception thrown!!
Type:
Error
Add’l Info:
CSD CBrowserFrame::OnCreate error.
Action:
Restart CSD.
DESK3026
DESK3027
DESK3028
DESK3029
DESK3030
DESK3031
66
December 17, 2014
Error Messages
Error
Description
DESK3032
Text:
CBrowserFrame::LoadToolbar: Major error exception thrown!!
Type:
Error
Add’l Info:
CSD CBrowserFrame::LoadToolbar error.
Action:
Restart CSD.
Text:
CBrowserFrame::ReLoadBrowserButtons: Major
error - exception thrown!!
Type:
Error
Add’l Info:
CSD CBrowserFrame::ReLoadBrowserButtons
error.
Action:
Restart CSD.
Text:
CBrowserView::OnInitialUpdate: Major error exception thrown!!
Type:
Error
Add’l Info:
CSD CBrowserView::OnInitialUpdate error.
Action:
Restart CSD.
Text:
CBrowserView::OnDocumentComplete: Major
error - exception thrown!!
Type:
Error
Add’l Info:
CSD CBrowserView::OnDocumentComplete
error.
Action:
Restart CSD.
Text:
CBrowserView::Load() Major error - exception
thrown!!
Type:
Error
Add’l Info:
CSD CBrowserView::Load() error.
Action:
Restart CSD.
Text:
ChatAPI AddPresenceUser failed.
Type:
Error
Add’l Info:
Unified Presence server error.
Action:
Restart Unified Presence server.
DESK3033
DESK3034
DESK3035
DESK3036
DESK3037
December 17, 2014
67
Cisco CAD Error Code Dictionary
Error
Description
DESK3038
Text:
ChatAPI DropPresenceUser failed.
Type:
Error
Add’l Info:
Unified Presence server error.
Action:
Restart Unified Presence server.
Text:
Error logging into Recording/Playback server.
Error: <%ls>.
Type:
Error
Add’l Info:
Cannot login to Recording & Playback service.
Action:
Restart Recording & Playback service.
Text:
Error occurred when setting the playback
position. Error: <%ls>.
Type:
Error
Add’l Info:
Cannot change playback position.
Action:
Restart Recording & Playback service.
Text:
Error occurred attempting resume operation.
Error: <%ls>.
Type:
Error
Add’l Info:
Cannot resume playback.
Action:
Restart Recording & Playback service.
Text:
Error logging out of Recording/Playback server.
Error: <%ls>.
Type:
Error
Add’l Info:
Cannot log out of Recording & Playback service.
Action:
Restart Recording & Playback service.
Text:
Error getting volume level from the
Recording/Playback server. Error: <%ls>.
Type:
Error
Add’l Info:
Cannot get volume level from server.
Action:
Restart Recording & Playback service.
DESK3039
DESK3040
DESK3041
DESK3042
DESK3043
68
December 17, 2014
Error Messages
Error
Description
DESK3044
Text:
Failed to authenticate cti user. Error: <%ls>.
Type:
Error
Add’l Info:
Failed to authenticate supervisor login against
CTI server.
Action:
See error code for details on error.
Text:
ChatAPI getPresenceContactList failed.
Type:
Error
Add’l Info:
Unified Presence server error.
Action:
Restart Unified Presence server.
Text:
One or more critical pointers are NULL returning.
Type:
Error
Add’l Info:
One or more critical pointers are NULL returning.
Action:
None
Text:
Major error - exception thrown
Type:
Error
Add’l Info:
Major error - exception thrown
Action:
None
Text:
Error connecting to LDAP.
Type:
Error
Add’l Info:
Communication problem
Action:
Reestablish communication with Directory
Services.
Text:
Error calling setAgentAcdState
Type:
Error
Add’l Info:
Internal error in the Chat service.
Action:
Restart the Chat service.
DESK3045
DESK3046
DESK3047
DESK3048
DESK3049
December 17, 2014
69
Cisco CAD Error Code Dictionary
Error
Description
DESK3050
Text:
CTIOS exception occurred. Description.
Type:
Error
Add’l Info:
Unknown exception
Action:
Get the Dr Watson log, dump files and agent logs
sent to developer
Text:
FailedServer = ReasonCode
Type:
Error
Add’l Info:
Unknown exception
Action:
Get the Dr Watson log, dump files and agent logs
sent to developer
Text:
AgentMonitor is not yet initialized! Execution will
continue, however if Agent Device Monitor
configuration for extension %ls is anything other
than Desktop, recording/monitoring may not
work.
Type:
Error
Add’l Info:
Agent Device Monitor type is not yet obtained
from the server, and the program waited as long
as possible to receive the configuration.
Action:
Restart Agent Desktop to ensure
recording/monitoring support with SPAN. If the
issue persists after you restart, investigate VoIP
Monitor Service on the server.
Text:
Error Obtaining License.
Type:
Error
Add’l Info:
Server down or all licenses in use.
Action:
Restart server or wait for a license to become
available.
Text:
Directory services could not retrieve icon data in
<%ls> from <%ls>.
Type:
Error
Add’l Info:
Not enough rights to the directory. Misformatted
data. Internal error.
Action:
Assure the target file contains an icon. Try
another file with an icon.
DESK3051
DESK3052
DESK3101
DESK3102
70
December 17, 2014
Error Messages
Error
Description
DESK3104
Text:
Unable to retrieve data from Directory Services.
Type:
Error
Add’l Info:
Communication problems with directory
services. Possible data corruption.
Action:
Reestablish communication with directory
services. Restore directory services database
from backup.
Text:
Directory services was unable to write icon
binary into %ls
Type:
Error
Add’l Info:
Not enough rights to the directory.
Action:
Procure rights to the directory through your
administrator.
Text:
Unable to retrieve data from Enterprise
Database.
Type:
Error
Add’l Info:
Possible communication problem with
Enterprise server, or requested data does not
exist.
Action:
Restart Enterprise server or ignore.
Text:
Could not obtain license from LRM.
Type:
Error
Add’l Info:
LRM is not running.
Action:
check if the server is running or check if CAD is
licensed during installation
Text:
Error: get agent returned.
Type:
Error
Add’l Info:
LDAP monitoring is not running
Action:
check the server is running or restart the server
Text:
Error: get team returned.
Type:
Error
Add’l Info:
LDAP monitoring is not running
Action:
check the server is running or restart the server
DESK3105
DESK3107
DESK3109
DESK3110
DESK3111
December 17, 2014
71
Cisco CAD Error Code Dictionary
Error
Description
DESK3112
Text:
Unknown exception while retrieving a license.
Type:
Error
Add’l Info:
LRM is not running
Action:
check if the server is running
Text:
Unknown exception while releasing the
license(s)
Type:
Error
Add’l Info:
LRM is not running
Action:
check if the server is running
Text:
Unable to Login Desktop Monitoring
Type:
Error
Add’l Info:
Desktop monitoring is not running
Action:
Check if Desktop monitoring is running
Text:
Unable to Start Desktop Monitoring
Type:
Error
Add’l Info:
Desktop monitoring is not running
Action:
Check if Desktop monitoring is running
Text:
Failed to write data to the Enterprise Server.
Type:
Error
Add’l Info:
Enterprise server is not running
Action:
Check if the ES is running or restart server.
Text:
Save reason codes failed.
Type:
Error
Add’l Info:
Attempt to write reason codes to LDAP failed.
Action:
See LDAP client error message for details.
Text:
Read reason codes failed.
Type:
Error
Add’l Info:
Chat server error.
Action:
Restart Chat server.
DESK3113
DESK3115
DESK3116
DESK3117
DESK3118
DESK3119
72
December 17, 2014
Error Messages
Error
Description
DESK3120
Text:
Save Wrap-up data failed.
Type:
Error
Add’l Info:
Attempt to write reason codes to LDAP failed.
Action:
See LDAP client error message for details.
Text:
Read Wrap-up data failed.
Type:
Error
Add’l Info:
LDAP monitor is not running.
Action:
Restart LDAP monitor.
Text:
Error, could not execute action.
Type:
Error
Add’l Info:
The workflow action could not complete.
Action:
The administrator should review the action
setup in the Cisco Desktop Administrator.
Text:
Unable to start EEM client controller.
Type:
Error
Add’l Info:
Attempt to start EEM Client Controller failed.
Action:
See EEMClientController error message for
details.
Text:
E-Mail Client is disconnected.
Type:
Error
Add’l Info:
E-Mail Client is disconnected from CAD and
attempt to recover.
Action:
E-Mail agent log out. See EEMClientController
error message for details.
Text:
Agent E-mail disabled, Java Runtime version not
found.
Type:
Error
Add’l Info:
Required Java Runtime Environment not found
on system.
Action:
Install Java Runtime Environment version
supported by this release.
DESK3121
DESK3122
DESK3124
DESK3125
DESK3126
December 17, 2014
73
Cisco CAD Error Code Dictionary
Error
Description
DESK3135
Text:
Error = <%ls>.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Failed to open registry key.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Failed to read value on Entry in the registry key.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error saving server profile.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error updating the Active TServer entry.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error getting server profile.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Failed to write value to the registry key.
Type:
Error
Add’l Info:
None.
Action:
None.
DESK3204
DESK3205
DESK3209
DESK3210
DESK3211
DESK3212
74
December 17, 2014
Error Messages
Error
Description
DESK3213
Text:
Failed to iterate registry key.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error GetKeyValue Switch Type. Error code =
<%d>, <%ls>.
Type:
Warn
Add’l Info:
None.
Action:
None.
Text:
Error GetKeyValue CTI Type. Error code = <%d>,
<%ls>.
Type:
Warn
Add’l Info:
None.
Action:
None.
Text:
Error GetServerTypeProfile. Error code = <%d>,
<%ls>.
Type:
Warn
Add’l Info:
None.
Action:
None.
Text:
Error getting switch and CTI type.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error getting GetServerIOR for Sync Server.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Corba Error. CORBA::is_nil(vDAS).
Type:
Error
Add’l Info:
None.
Action:
None.
DESK3214
DESK3215
DESK3216
DESK3217
DESK3221
DESK3222
December 17, 2014
75
Cisco CAD Error Code Dictionary
Error
Description
DESK3223
Text:
Error synchronizing directory services.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Could not update Required Admin Password.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Could not set the new Admin Pwd.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Failed to load Enterprise Administrator
(Administrator.exe)
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Failed to load Personnel.exe.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Failed to load Administrator.exe.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Failed to load IPCCAdm.exe.
Type:
Error
Add’l Info:
None.
Action:
None.
DESK3224
DESK3225
DESK3226
DESK3227
DESK3228
DESK3229
76
December 17, 2014
Error Messages
Error
Description
DESK3232
Text:
Failed to load SWFAdmin.exe.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Could not add workspace for server name.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Unexpected error reported.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
SetEvent failed.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error getting GetServerIOR for Sync Server.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Could not upload. File is missing or corrupted.
Type:
Error
Add’l Info:
The file is not the same as the one that was
written.
Action:
Restore the file to the original, or delete the file.
Text:
Could not read action disk file.
Type:
Error
Add’l Info:
An attempt to read the disk file has failed.
Action:
unknown
DESK3233
DESK3234
DESK3236
DESK3237
DESK3400
DESK3402
December 17, 2014
77
Cisco CAD Error Code Dictionary
Error
Description
DESK3403
Text:
Action upload to LDAP failed.
Type:
Error
Add’l Info:
LDAP Error
Action:
unknown
Text:
Invalid data received from file
Type:
Error
Add’l Info:
Though the file could be read, the data received
was not what was expected.
Action:
The file cannot be used.
Text:
Could not create folder.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
The version of action file is not compatible with
the application version.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Unable to log into Voice over IP Monitor server.
Type:
Fatal
Add’l Info:
None
Action:
Check status of VoIP Monitor Server.
Text:
Error getting formatted GUID from COM Library.
Error <0x%x>
Type:
Fatal
Add’l Info:
Communication failure with a server.
Action:
Restart the desktop application.
Text:
Fail to create BrowserFrame
Type:
Fatal
Add’l Info:
Fail to create BrowserFrame
Action:
Restart application.
DESK3404
DESK3406
DESK3407
DESK4001
DESK4002
DESK4003
78
December 17, 2014
Error Messages
Error
Description
DESK4004
Text:
Failed to reload
Type:
Fatal
Add’l Info:
Fail to reload one of the toolbars
Action:
Restart application.
Text:
Failed to create bar
Type:
!Fatal
Add’l Info:
Fail to create one of the toolbars
Action:
Restart application.
Text:
Unable to verify licence. License error
Type:
Fatal
Add’l Info:
LRM is not running
Action:
check if LRM is running or wrong LCC or wrong
LDAP host
Text:
Program exiting...
Type:
Fatal
Add’l Info:
All attempts to communicate with Directory
Services have failed.
Action:
Restart after communication with Directory
Services is restored.
Text:
Initialization failed, could not create message
window.
Type:
Fatal
Add’l Info:
Windows system error
Action:
Try to restart agent to login
Text:
At least one component of the Cisco ICM server
is offline.
Type:
Fatal
Add’l Info:
One of ICM components is down.
Action:
Restart that component.
DESK4005
DESK4007
DESK4008
DESK4010
DESK4011
December 17, 2014
79
Cisco CAD Error Code Dictionary
Error
Description
DESK4012
Text:
Unable to set the agent mode.
Type:
Fatal
Add’l Info:
Send agent Mode request fails
Action:
Restart CTIOS server; get CTIOS logs and agent
logs sent to developers
Text:
Connect to CTIOS server failed.
Type:
Fatal
Add’l Info:
No OPEN_CONF receives or receive
CONTROL_FAILURE_CONF
Action:
Get CTIOS logs from server and sent to
developers
Text:
Client has tried to make connection using
incompatible versions of the Cisco CTIOS server
and Cisco CTI OS CIL.
Type:
Fatal
Add’l Info:
Wrong version number of CTIOS
Action:
Use the correct CTIOS libraries version number
Text:
Unable to login - Query Confirmation returned
logout or unknown agent state.
Type:
Fatal
Add’l Info:
CTIOS server error
Action:
Restart CTIOS server
Text:
Wait for connection to Cisco CTIOS server failed
Type:
Fatal
Add’l Info:
No OPEN_CONF receives
Action:
Restart CTIOS server or ICM components
DESK4013
DESK4014
DESK4015
DESK4016
DESK4017
80
Text:
Type:
Fatal
Add’l Info:
None.
Action:
None.
December 17, 2014
Error Messages
Error
Description
DESK4100
Text:
Directory Services auto-recovery message. %ls is
%ls
Type:
Fatal
Add’l Info:
Directory services has sent a status message to
the application.
Action:
None
Text:
IPPA auto-recovery message. %ls is %ls
Type:
Fatal
Add’l Info:
IPPA server has sent a status message to the
application.
Action:
None
Text:
Application error.
Type:
Fatal
Add’l Info:
Voice Over IP not running.
Action:
Restart Voice over IP server.
Text:
Unexpected error.
Type:
Fatal
Add’l Info:
An unexpected internal error has occurred.
Action:
If application has aborted or error occurs more
than once, open a bug report.
Text:
Waiting for timer action event failed with error
Type:
Fatal
Add’l Info:
Application error
Action:
None.
Text:
Out of memory.
Type:
Fatal
Add’l Info:
Application error
Action:
None.
DESK4101
DESK4102
DESK4103
DESK4105
DESK4106
December 17, 2014
81
Cisco CAD Error Code Dictionary
Error
Description
DESK4107
Text:
AutoRecoverConnection failed ExitInstance.
Error code = <%d>, <%ls>.
Type:
Fatal
Add’l Info:
Application error
Action:
None.
Text:
Unable to download JRE from URL: <%ls>.
Type:
Fatal
Add’l Info:
None
Action:
Verify URL is accessible.
Text:
Cannot connect to IMAP service, could not
resolve host name to an IP address: %s.
Type:
Fatal
Add’l Info:
CTIOS API wait for single object fails.
Action:
Verify to make sure that the host name is
correct. Try running the ping command to verify
that the host name can be resolved from the
server machine. This may be a DNS issue or a
Microsoft TCP/IP Host Name Resolution Order
issue. Try using an IP address instead of a host
name.
DESK4108
EEM1000
82
December 17, 2014
Error Messages
Error
Description
EEM1001
Text:
Cannot connect to IMAP service, could not
connect to server.
Type:
Fatal
Add’l Info:
CTIOS API wait for single object fails.
Action:
This may be because there is no IMAP server
running at the specified host and port or
because there is no network connectivity to the
machine, or the connection was refused or
timed out for some other reason. Verify to make
sure that the host name is correct. Try running
the ping command to verify that there is
connectivity to the machine. You may also use
telnet to try to connect to IMAP store. Try running
the following command from the command line
of your CAD server using your IMAP address and
port, for example, telnet mail.myimapserver.com
143 If successful this should return something
like: telnet mail.myimapserver.com 143 Trying
192.168.1.1... Connected to mail.myserver.com
(192.168.1.1). Escape character is '^]'. * OK
IMAP4 ready.
December 17, 2014
83
Cisco CAD Error Code Dictionary
Error
Description
EEM1002
Text:
Cannot connect to IMAP service, Invalid
username or password: <%s>.
Type:
Fatal
Add’l Info:
CTIOS API wait for single object fails.
Action:
Verify to make sure the user name and
password specified are valid. On an Exchange
IMAP usernames are more than a simple login
name if NT authentication is enabled. For
example, if your email address is
"J.User@server.com", your Windows NT login
name is "juser", your NT domain name is "dom",
and your Exchange mailbox name is "Joe User",
then you would need to use a username of
"dom\juser\J.User" when logging into the IMAP
server. You can verify your username and
password using an email client like Microsoft
Outlook or you can validate it by connecting to
the server by using telnet.
Try running the following command from the
command line of your CAD server using your
IMAP address and port: telnet
mail.myserver.com 143. If successful, this
should return something like: telnet
mail.myimapserver.com 143 Trying
192.168.1.1... Connected to
mail.myimapserver.com (192.168.1.1). Escape
character is '^]'. * OK IMAP4 ready.
Next, try logging in using the login command.
Type '. login' followed by your username and
password separated by spaces. If successful,
this should return something like: . login
accountname@myserver.com ********* . OK
User logged in.
84
December 17, 2014
Error Messages
Error
Description
EEM1003
Text:
Cannot connect to IMAP service: %s.
Type:
Fatal
Add’l Info:
CTIOS API wait for single object fails.
Action:
This is a catch all error for any error condition
not described by EEM1000-EEM1002. The
message will be in the form of java exceptions
which should provide an indication as to why the
connection failed. Try following the Telnet
procedure described in EEM103 to determine
the root cause of the problem. It is likely a
network connectivity issue, a down server issue,
or an authentication issue.
Text:
A connection to the SMTP service could not be
made. The host name specified could not be
resolved to an IP address.
Type:
Fatal
Add’l Info:
CTIOS API wait for single object fails.
Action:
Verify to make sure that the host name is
correct. Try running the ping command to verify
that the host name can be resolved from the
server machine. This may be a DNS issue or a
Microsoft TCP/IP Host Name Resolution Order
issue. Try using an IP address instead of a host
name.
EEM1004
December 17, 2014
85
Cisco CAD Error Code Dictionary
Error
Description
EEM1005
Text:
A connection to the SMTP service could not be
made, An attempt was made to connect to the
server but was unsuccessful.
Type:
Fatal
Add’l Info:
CTIOS API wait for single object fails.
Action:
This may occur because there is no SMTP server
running at the specified host and port or
because there is no network connectivity to the
machine, or the connection was refused or
timed out for some other reason. Ensure that
the host name is correct. Try running the ping
command to verify that there is connectivity to
the machine. You can also use telnet to try to
connect to SMTP server. Try running the
following command from the command line of
your CAD server using your IMAP address and
port: telnet mail.mysmtpserver.com 25. If
successful, this should return something similar
to the following: telnet
mail.mysmtpserver.com 25 220
mail.mysmtpserver.com Microsoft ESMTP
MAIL Service, Version: 6.0.3790.3959
ready at Mon, 10 Dec 2007 16:53:25
-0600.
86
December 17, 2014
Error Messages
Error
Description
EEM1006
Text:
A connection to the SMTP service could not be
made, The user name and password are not
valid.
Type:
Fatal
Add’l Info:
CTIOS API wait for single object fails.
Action:
Verify that the user name and password
specified are valid. On an Exchange Server
SMTP usernames are typically just a login ID.
They are not as complicated as the IMAP user ID.
For example, if your email address is
“J.User@server.com”, your Windows NT login
name is “juser”, your NT domain name is “dom”,
and your Exchange mailbox name is “Joe User”,
then your username is “juser” when logging into
the SMTP server. You can verify your username
and password using an email client like
Microsoft Outlook or you can validate it by
connecting to the server by using telnet. See the
Microsoft Technet topic “How to Use Telnet to
Test SMTP Communication” for details.
A summary of the procedure follows:
Try running the following command from the
command line of your CAD server: telnet
mail.mysmtpserver.com 25. If successful, this
should return something similar to the following:
220 mail.mysmtpserver.com Microsoft
ESMTP MAIL Service, Version:
6.0.3790.3959 ready at Mon, 10 Dec 2007
16:53:25 -0600.
Next, specify your mail server domain by typing
the following into your telnet session using your
mailserver domain: EHLO mysmtpserver.com. If
successful, this should return several lines
beginning with 250. The last line should be the
following: 250 OK.
(contd.)
December 17, 2014
87
Cisco CAD Error Code Dictionary
Error
Description
EEM1006
Action:
Next, try to log into the SMTP server. Enter AUTH
LOGIN into your telnet session. The server will
respond with an encrypted prompt for your user
name. You must enter your user name encrypted
in base 64. There are many tools online to do
this. Try doing a web search for the keywords
base64 converter. The server responds with an
encrypted base 64 prompt for your password.
Enter your password encrypted in base 64.
For example if your username is <myname> and
your password is <mypassword>, the base64
conversions will be bXluYW1l and
bXlwYXNzd29yZA==, respectively. A login
sequence using these will look something
similar to the following: AUTH LOGIN 334
VXNlcm5hbWU6 bXluYW1l 334 UGFzc3dvcmQ6
bXlwYXNzd29yZA==.
If successful, you will see the following: 235
2.7.0 Authentication successful.
You can also test sending an email with this
account by entering the following: MAIL
FROM:myname@mysmtpserver.com 250 2.1.0
myname@mysmtpserver.com....Sender OK
RCPT TO:recipient@mysmtpserver.com 250
2.1.5 recipient@mysmtpserver.com....
Recpient OK DATA 354 Please start mail
input. Test of telnet smtp 250 Mail
queued for delivery.
EEM1007
88
Text:
Cannot connect to SMTP service: %s.
Type:
Fatal
Add’l Info:
CTIOS API wait for single object fails.
Action:
This is a catch all error for any error condition
not described by EEM1004-EEM1006. The
message will be in the form of java exceptions
which should provide an indication as to why the
connection failed. Try following the telnet
procedure described in EEM1006 to determine
the root cause of the problem. It is likely a
network connectivity issue, a down server issue,
or an authentication issue.
December 17, 2014
Error Messages
Error
Description
EEM1008
Text:
The user specified does not have a mailbox
located on the configured server.
Type:
Fatal
Add’l Info:
CTIOS API wait for single object fails.
Action:
Verify that the configured account can login and
access their mailbox on the configured server.
Text:
Agent <%s> could not be notified of assignment
<%s> after <%d> attempts. Assignment will be
canceled, and agent requeued.
Type:
Fatal
Add’l Info:
An agent could not be notified of their e-mail
assignment.
Action:
Check that the configured account can login and
access the mailbox on the configured server.
Text:
For agent <%s>: Could not cleanup from failed
assignment in folder <%s> after <%d> attempts.
Duplicate E-Mails may be present.
Type:
Fatal
Add’l Info:
Attempting to recover from a requeue failure
also failed.
Action:
Check that the configured account can login and
access their mailbox on the configured server.
Text:
Could not retrieve specified information from the
data buffer.
Type:
Error
Add’l Info:
CTIOS API wait for single object fails.
Action:
Look for disruptions in the connection between
the Exchange Server and the Email Manager
applet.
Text:
There is insufficient memory to run the EEM
applet.
Type:
Error
Add’l Info:
CTIOS API wait for single object fails.
Action:
Verify that the client PC has enough memory. If
the PC has enough memory, verify that JVM has
sufficient memory to run Agent E-Mail.
EEM1009
EEM1010
EEM2000
EEM2001
December 17, 2014
89
Cisco CAD Error Code Dictionary
Error
Description
EEM2002
Text:
You are connecting to a server with a test or self
signed certificate. The application will attempt to
download the certificate to the certificate store If
this works the program will make another
attempt to connect with the server.
Type:
Error
Add’l Info:
CTIOS API wait for single object fails.
Action:
Look in the log to see if the connection attempt
eventually succeeds or fails for another reason.
Text:
There is a message in the mail store outbox that
is not a Mime encoded message. The EEM
service will not be able to send this message.
Manually remove this message from the mail
store using a third party client. The CAD software
should not be able to create such a message on
it's own, so verify that no other users are
accessing mail store folders.
Type:
Error
Add’l Info:
CTIOS API wait for single object fails.
Action:
None.
Text:
Client cannot retrieve specified event
information from the socket message.
Type:
Error
Add’l Info:
CTIOS API wait for single object fails.
Action:
Look at the status of the connection between
client and the service. If the connection was
disrupted, the client has lost data and the client
needs to be restarted. If you upgraded the
service while clients were connected to it, the
clients are now running a different version than
the service. In this case, clients must exit and be
restarted.
EEM2003
EEM2004
90
December 17, 2014
Error Messages
Error
Description
EEM2005
Text:
This is an internal error. The client is not
configured with the information that it needs to
locate the service.
Type:
Error
Add’l Info:
CTIOS API wait for single object fails.
Action:
Ensure that the client is configured with the
information that it needs to locate the service.
Text:
Failed to send message using SMTP. Message:
<%s> using e-mail from address: <%s>. Moving
message to the Not Sendable folder. Check your
SMTP and CAD configuration.
Type:
Error
Add’l Info:
CTIOS API wait for single object fails.
Action:
None.
Text:
Failed to send message using SMTP. Message:
<%s>. Probably an invalid recipient address.
Moving message to the Not Sendable folder.
Check your SMTP and CAD configuration.
Type:
Error
Add’l Info:
CTIOS API wait for single object fails.
Action:
None.
Text:
Failed to send message using SMTP. Message:
<%s>. This was the final failure number %d.
Moving message to the Pending Error folder.
Check your SMTP and CAD configuration.
Type:
Error
Add’l Info:
A message in the outbox could not be sent
because of an SMTP failure code of 421 4.4.1,
which can be obtained during a timeout.
Action:
Message moved to the “Pending Error” folder.
EEM2006
EEM2007
EEM2008
December 17, 2014
91
Cisco CAD Error Code Dictionary
Error
Description
EEM2009
Text:
Failed to send message using SMTP. Message:
<%s>. This message is currently on hour <%d>
of its <%d> hour Time-to-Live grace period. After
the TTL expires and the message still cannot be
sent, the message will be moved to the Not
Sendable folder. Check your SMTP and CAD
configuration.
Type:
Error
Add’l Info:
A message in the Pending Error folder could not
be sent because of an SMTP failure code of 421
4.4.1, which can be obtained during a timeout.
Action:
None.
Text:
Failed to send message using SMTP. Message:
<%s>. This message's Time-to-Live grace period
of <%d> hours has expired. Moving message to
the Not Sendable folder. Check your SMTP and
CAD configuration.
Type:
Error
Add’l Info:
A message in the Pending Error folder could not
be sent because of an SMTP failure code of 421
4.4.1, which can be obtained during a timeout.
Action:
Message moved to the “Not Sendable” folder.
Text:
Could not make %s IMAP connection.
Type:
Warn
Add’l Info:
CTIOS API wait for single object fails.
Action:
If you feel this attempt should have succeeded
see the error message that occured prior to this,
you may not have the security set correctly on
you IMAP server.
EEM2010
EEM3000
92
December 17, 2014
Error Messages
Error
Description
EEM3001
Text:
Could not make %s SMTP connection.
Type:
Warn
Add’l Info:
Specifies that the IMAP connection attempt
failed when trying the specified security type,
and attempt will be made with the other security
type.
Action:
If you feel this attempt should have succeeded
see the error message that occured prior to this,
you may not have the security set correctly on
you IMAP server.
Text:
Could not transfer message agentId=<%s>,
messageId=<%s>, error=<%s>.
Type:
Warn
Add’l Info:
Indicates that an e-mail could not be transferred
because of an error.
Action:
See the log to see the type of error.
Text:
Caught TRYCREATE messaging exception,
attempting to recover.
Type:
Warn
Add’l Info:
The EmailUtils caught a TRYCREATE exception
and will attempt to recover.
Action:
Under normal circumstances the application will
recover on its own. However, if it does not, See
the logs for reasons why it is not recovering, and
troubleshoot the connection.
EEM3002
EEM3003
December 17, 2014
93
Cisco CAD Error Code Dictionary
Error
Description
EEM3004
Text:
Unable to map inbound e-mail to a CSQ. Moving
to the Not Routable folder. Check your settings
in desktop administrator if you want to route
e-mails sent to this e-mail address. Message:
<%s>, recipients: <%s>.
Type:
Warn
Add’l Info:
The Agent E-mail Service was not able to map
any of the recipient e-mail addresses to a CSQ.
The e-mail will then be moved to the Not
Routable folder.
Action:
Make sure you have mapped all of the e-mail
addresses that clients will send e-mails to, to a
CSQ. After doing that you can use a 3rd party
IMAP client to move messages back into the
Inbox from the Not Routable folder. The Agent
E-mail Service will then pick those messages up
automatically and reprocess them.
Text:
Unable to create outbound autoresponse
message. Exception: <%s>.
Type:
Warn
Add’l Info:
The Agent E-Mail Service was not able to create
an autoresponse message.
Action:
Check the Agent E-Mail Service’s IMAP
Connection, and verify the configuration.
Text:
Unable to route message. Exception: <%s>.
Type:
Warn
Add’l Info:
The Agent E-Mail Service lost connection while
routing messages.
Action:
Check the Agent E-Mails Service’s IMAP
Connection and configuration.
EEM3005
EEM3006
94
December 17, 2014
Error Messages
Error
Description
EEM3007
Text:
Failed to send message using SMTP. Message:
<%s>. This was failure number %d. Re-attempts
will be made until a total of %d failures of this
nature occur.
Type:
Warn
Add’l Info:
A message in the outbox could not be sent
because of an SMTP failure code of 421 4.4.1,
which can be obtained during a timeout.
Action:
Retry sending the message.
Text:
A connection to CAD using CADEEMConnector
could not be established.
Type:
Fatal
Add’l Info:
The EEMApplet could not connect to CAD. Check
to be sure that CAD is running and is listening on
the expected port. See debug log for details.
Action:
Check to be sure that CAD is running and is
listening on the expected port. See debug log for
details.
Text:
A connection to the mail store could not be
established.
Type:
Fatal
Add’l Info:
The EEMApplet could not connect to the Mail
Store. Check to be sure that the mail store is
running and is listening on the expected port.
Check that the connection information and
credentials configured for the mail store are
correct. See debug log for details.
Action:
Check to be sure that the mail store is running
and is listening on the expected port. Check that
the connection information and credentials
configured for the mail store are correct. See
debug log for details.
EEMAPP1000
EEMAPP1001
December 17, 2014
95
Cisco CAD Error Code Dictionary
Error
Description
EEMAPP2000
Text:
EEMApp could not load the specified resource
bundle for the specified locale.
Type:
Error
Add’l Info:
CTIOS API wait for single object fails.
Action:
Verify that the specified local is supported and
has a valid resource bundle available on the
classpath. See the debug log for details of the
failure.
Text:
The resource <%s> could not be found.
Type:
Error
Add’l Info:
EEMApp could not load the specified resource
string.
Action:
Verify that the specified local is supported and
has a valid resource bundle available on the
classpath. Make sure that the resource key is
available for the system's locale. See the debug
log for details of the failure.
Text:
Unable to transfer message <%s>, caught <%s>.
Type:
Error
Add’l Info:
EemApp could not transfer the specified email.
Action:
Check that the client is connected to the
mailstore and other cad services. Restart if the
problem persists.
Text:
The EemApplet connector port value <%s> is
invalid.
Type:
Warn
Add’l Info:
The specified port value is invalid.
Action:
Verify that the port value being passed to the
EEMApplet is a valid value between 0 and
65535.
EEMAPP2001
EEMAPP2002
EEMAPP3000
96
December 17, 2014
Error Messages
Error
Description
EEMAPP3001
Text:
The EemApplet could not delete the email:
<%s>.
Type:
Warn
Add’l Info:
The specified email could not be deleted.
Action:
Verify that the email still exists in the expected
location and that the EEMApp is connected to
the mail store and has permissions to delete
messages. See the debug log for more details.
Text:
The EEMApp could not load the list of assigned
emails.
Type:
Warn
Add’l Info:
CTIOS API wait for single object fails.
Action:
Verify that the EEMApp is configured correctly
and able to connect to the mail store. Verify that
the agent has assigned emails; this message
may appear if there are no messages assigned
to the agent. See the debug log for more details.
Text:
The EEMApp could not load the assigned email.
Type:
Warn
Add’l Info:
CTIOS API wait for single object fails.
Action:
Verify that the EEMApp is configured correctly
and able to connect to the mail store. Verify that
the assigned email exists in the agent's folder.
See the debug log for more details.
Text:
A draft could not be saved for the assigned
email.
Type:
Warn
Add’l Info:
CTIOS API wait for single object fails.
Action:
Verify that the EEMApp is configured correctly
and able to connect to the mail store. See the
debug log for more details.
EEMAPP3002
EEMAPP3003
EEMAPP3004
December 17, 2014
97
Cisco CAD Error Code Dictionary
Error
Description
EEMAPP3005
Text:
The EemApplet could not send a response for
the assigned e-mail: <%s>.
Type:
Warn
Add’l Info:
A response could not be sent for the assigned
e-mail.
Action:
Verify that the EEMApp is configured correctly
and able to connect to the mail store. See the
debug log for more details.
Text:
The EemApplet was unable to send deleted
email to address: <%s>
Type:
Warn
Add’l Info:
A copy of a deleted email could not be sent to
the specified address.
Action:
Verify that the EEMApp is configured correctly
and able to connect to the mail store. See the
debug log for more details.
Text:
Lost connection to the mail store or transport,
attempting to recover.
Type:
Warn
Add’l Info:
The EEMApp has lost its connection to the IMAP
and/or SMTP service and is attempting to
recover.
Action:
Under normal circumstances the applet will
recover on its own. However, if it does not, see
the logs for reasons why it is not recovering, and
troubleshoot the connection.
Text:
Caught TRYCREATE messaging exception,
attempting to recover.
Type:
Warn
Add’l Info:
The EemApp caught a TRYCREATE exception and
will attempt to recover.
Action:
Under normal circumstances the applet will
recover on its own. However, if it does not, see
the logs for reasons why it is not recovering, and
troubleshoot the connection.
EEMAPP3006
EEMAPP3007
EEMAPP3008
98
December 17, 2014
Error Messages
Error
Description
EEMAPP3009
Text:
Unable to get template contents for template:
<%s> at url <%s>.
Type:
Warn
Add’l Info:
The EemApp could not load the contents of the
specified template.
Action:
Check the configuration to be sure that the
template URL is accessible by client desktops.
Text:
Unable to save draft for message <%s>.
Type:
Warn
Add’l Info:
The EemApp could not save a draft message, an
in-memory copy will be made.
Action:
Verify that the IMAP server is running and that
the client can access it, and that the quota for
the account has not been reached. Then try
saving the draft again.
Text:
Failed to log in.
Type:
Error
Add’l Info:
The client was unable to log in.
Action:
This means that there was an error
communicating with the server. Check that the
client was connected at the time and that they
received a confirmation response from the
server after logging in.
Text:
The agent could not be found.
Type:
Warn
Add’l Info:
Information for the agent that logged in could
not be found.
Action:
See log for errors; this probably means that the
agent logged out before login could complete.
EEMAPP3010
EEMC2000
EEMC3000
December 17, 2014
99
Cisco CAD Error Code Dictionary
Error
Description
EEMS1000
Text:
The SocketService could not be started. Reason:
(%ls)
Type:
Fatal
Add’l Info:
The SocketService could not be started.
Action:
See debug log for details, validate that the
service IP Address and Port are configured
correctly, and that the service is not already
running. Restart the service.
Text:
The Java process could not be initialized.
Reason: (%ls)
Type:
Fatal
Add’l Info:
The Java process could not be initialized.
Action:
Verify that a valid JRE is installed and that the
JavaHome registry key for EEMServer is set
correctly.
Text:
The Java Email Manager service could not be
started. Reason: (%ls)
Type:
Fatal
Add’l Info:
The Java Email Manager service could not be
started.
Action:
Verify that the JVM was initialized and that all of
the necessary jar files and configuration values
are present.
Text:
The Java Email Manager service could not be
restarted during autorecovery. Reason: (%ls)
Type:
Fatal
Add’l Info:
The Java Email Manager service could not be
restarted during autorecovery.
Action:
Restart the EEM Service.
Text:
The Java Email Manager service could not
determine the ID of the host. Reason: (%ls)
Type:
Error
Add’l Info:
The Java Email Manager service could not
determine the ID of the host.
Action:
Verify that the IOR hostname matches an LDAP
Host N value in the Site setup registry.
EEMS1001
EEMS1002
EEMS1003
EEMS2001
100
December 17, 2014
Error Messages
Error
Description
EEMS2002
Text:
The Java Email Manager service could be
initialized. Reason: (%ls)
Type:
Error
Add’l Info:
The Java Email Manager service could be
initialized
Action:
Verify that the Java process is running and that
the connection is stable.
Text:
Could not connect to the RASCAL service.
Reason: (%hs).
Type:
Error
Add’l Info:
The service was unable to connect to the
RASCAL Service. This will cause email logging to
fail for newly arrived messages.
Action:
Verify that the RASCAL Service is active, and
troubleshoot the connection using the RASCAL
error message.
Text:
Lost communication with the java service,
attempting to recover.
Type:
Error
Add’l Info:
The service has not received a heartbeat
message from the java service in 30 seconds,
the java service will be restarted.
Action:
Service should recover automatically. If it
doesn't, the entire EEM Service may need to be
restarted.
Text:
Error communicating with the java service,
attempting to recover.
Type:
Error
Add’l Info:
The service received an error communicating
with the java service, the java service will be
restarted.
Action:
Service should recover automatically. If it
doesn't, the entire EEM Service may need to be
restarted.
EEMS2003
EEMS2004
EEMS2005
December 17, 2014
101
Cisco CAD Error Code Dictionary
Error
Description
EEMS3000
Text:
The agent could not be found.
Type:
Warn
Add’l Info:
Information for the agent that logged in could
not be found.
Action:
See log for errors; this probably means that the
agent logged out before login could complete.
Text:
The message could not be assigned to the
agent.
Type:
Warn
Add’l Info:
A message could not be assigned to an agent.
Add’l Info:
Probably means that the agent disconnected
without logging out after requesting a message.
Verify that the agent sees the message when
logging back in.
Text:
No Email CSQs were loaded, check
configuration.
Type:
Warn
Add’l Info:
No Email CSQs could be loaded.
Action:
Verify that the server has an active LDAP
connection and that valid Email Skills exist in
LDAP.
Text:
Could not load specified JVM, attempting to load
a default JVM.
Type:
Warn
Add’l Info:
The JVM specified by the JavaHome registry key
could not be found.
Action:
Verify that the value is correct or that the correct
version of the JVM was loaded anyway.
Text:
The Java Email Manager service could not be
stopped normally. Reason: (%ls).
Type:
Warn
Add’l Info:
The Java Email Manager service could not be
stopped normally.
Action:
The EEMService may need to be restarted if is
not functioning correctly.
EEMS3001
EEMS3002
EEMS3003
EEMS3004
102
December 17, 2014
Error Messages
Error
Description
EEMUI1000
Text:
A connection to CAD using CADEEMConnector
could not be established.
Type:
Fatal
Add’l Info:
The Applet could not connect to CAD. Check to
be sure that cad is running and is listening on
the expected port. See debug log for details.
Action:
None.
Text:
A connection to the mail store could not be
established.
Type:
Fatal
Add’l Info:
The Applet could not connect to the Mail Store.
Check to be sure that the mail store is running
and is listening on the expected port. Check that
the connection information and credentials
configured for the mail store are correct. See
debug log for details.
Action:
None
Text:
EEMUI cannot load the %s bundle using the
resource <%s> and locale <%s>.
Type:
EEMUI could not load the specified resource
bundle for the specified locale.
Add’l Info:
Error
Action:
Check that the specified local is supported and
has a valid resource bundle available on the
classpath. See the debug log for details of the
failure.
Text:
The resource <%s> could not be found.
Type:
Error
Add’l Info:
EEMUI could not load the specified resource
string.
Action:
Check that the specified local is supported and
has a valid resource bundle available on the
classpath. Make sure that the resource key is
available for the system’s locale. Check the
debut log for details of the failure.
EEMUI1001
EEMUI2000
EEMUI2001
December 17, 2014
103
Cisco CAD Error Code Dictionary
Error
Description
EEMUI2002
Text:
Unable to transfer message <%s>, caught <%s>
Type:
Error
Add’l Info:
EEMUI could not transfer the specified email.
Action:
Check that the client is connected to the
mailstore and other cad services. Restart if the
problem persists.
Text:
The Applet connector port value <%s> is invalid.
Type:
Warn
Add’l Info:
The specified port value is invalid.
Action:
Check that the port value being passed to the
Applet is a valid value between 0 and 65535.
Text:
The Applet could not delete the email: <%s>
Type:
Warn
Add’l Info:
The specified email could not be deleted.
Action:
Check that the email still exists in the expected
location and that the EEMUI is connected to the
mail store and has permissions to delete
messages. See the debug log for more details.
Text:
The Applet could not load the list of assigned
emails.
Type:
Warn
Add’l Info:
The EEMUI could not load the list of assigned
emails.
Action:
Check that the EEMUI is configured correctly and
able to connect to the mail store. Check that the
agent has assigned emails; this message may
appear if there are no messages assigned to the
agent. See the debug log for more details.
Text:
The Applet could not load the assigned email:
<%s>
Type:
Warn
Add’l Info:
The EEMUI could not load the assigned email.
Action:
Check that the EEMUI is configured correctly and
able to connect to the mail store. Check that the
assigned email exists in the agent’s folder. See
the debug log for more details.
EEMUI3000
EEMUI3001
EEMUI3002
EEMUI3003
104
December 17, 2014
Error Messages
Error
Description
EEMUI3004
Text:
The Applet could not save a draft for the
assigned email: <%s>
Type:
Warn
Add’l Info:
A draft could not be saved for the assigned
email.
Action:
Check that the EEMUI is configured correctly and
able to connect to the mail store. See the debug
log for more details.
Text:
The Applet could not send a response for the
assigned email: <%s>
Type:
Warn
Type:
A response could not be sent for the assigned
email.
Add’l Info:
Check that the EEMUI is configured correctly and
able to connect to the mail store. See the debug
log for more details.
Text:
The Applet was unable to send deleted email to
address: <%s>
Type:
Warn
Add’l Info:
A copy of a deleted email could not be sent to
the specified address.
Action:
Check that the EEMUI is configured correctly and
able to connect to the mail store. See the debug
log for more details.
Text:
Lost connection to the mail store or transport,
attempting to recover.
Type:
Warn
Add’l Info:
The EEMUI has lost its connection to the IMAP
and/or SMTP service and is attempting to
recover.
Action:
Under normal circumstances the applet will
recover on its own. However, if it does not, check
the logs for reasons why it is not recovering, and
troubleshoot the connection.
EEMUI3005
EEMUI3006
EEMUI3007
December 17, 2014
105
Cisco CAD Error Code Dictionary
Error
Description
EEMUI3008
Text:
Caught TRYCREATE messaging exception,
attempting to recover.
Type:
Warn
Add’l Info:
The EEMUI caught a TRYCREATE exception and
will attempt to recover.
Action:
Under normal circumstances the applet will
recover on its own. However, if it does not, check
the logs for reasons why it is not recovering, and
troubleshoot the connection.
Text:
Unable to get template contents for template:
<%s> at url <%s>.
Type:
Warn
Add’l Info:
The EEMUI could not load the contents of the
specified template.
Action:
Check the configuration to be sure that the
template URL is accessible by client desktops.
Text:
Unable to save draft for message <%s>
Type:
Warn
Add’l Info:
The EEMUI could not save a draft message, an
in-memory copy will be made.
Action:
Check that the IMAP server is running and that
the client can access it, and that the quota for
the account has not been reached. Then try
saving the draft again.
Text:
The Applet could not forward a response for the
assigned email: <%s>
Type:
Warn
Add’l Info:
A response could not be forwarded for the
assigned email.
Action:
Check that the EEMUI is configured correctly and
able to connect to the mail store. See the debug
log for more details.
EEMUI3009
EEMUI3010
EEMUI3011
106
December 17, 2014
Error Messages
Error
Description
EEMIUI3012
Text:
Email received from IMAP different than
advertised by EEMServer! EEMServer message:
<%s>
Type:
Warn
Add’l Info:
The EemUi could not download a message from
IMAP which matched the message info received
from EEMServer.
Action:
Check that the IMAP server is running and that
the client can access it.
Text:
The Java long value %d may not have a precise
representation as a double-precision floating
point number in JavaScript:
Type:
Warn
Add’l Info:
A Java Long value is outside the range of
integers that is guaranteed to have an exact
representation in JavaScript.
Action:
None.
Text:
Timeout waiting for a response from the CRS
CVD.
Type:
Warn
Add’l Info:
Timeout
Action:
The service will try to recover the connection to
the CVD automatically. if this error continues to
occur, then check the CRS CVD logs (CRS Cluster
View Daemon).
Text:
Failed to receive message from the CRS CVD
<%d>.
Type:
Warn
Add’l Info:
Message receive failed
Action:
The service will try to recover the connection to
the CVD automatically. if this error continues to
occur, then check the CRS CVD logs (CRS Cluster
View Daemon).
EEMUI3013
LRM3004
LRM3005
December 17, 2014
107
Cisco CAD Error Code Dictionary
Error
Description
LRM3006
Text:
Failed to initialize the connection to CRS CVD.
Type:
Warn
Add’l Info:
Connection initialization failed
Action:
The service will try to recover the connection to
the CVD automatically. if this error continues to
occur, then check the CRS CVD logs (CRS Cluster
View Daemon).
Text:
Failed to connect to the CRS CVD.
Type:
Warn
Add’l Info:
failed to connect
Action:
The service will try to recover the connection to
the CVD automatically. if this error continues to
occur, then check the CRS CVD logs (CRS Cluster
View Daemon).
Text:
Unable to create thread.
Type:
Fatal
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory).
Text:
Unexpected error. WaitForSingleObject failed.
Type:
Fatal
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory).
Text:
Unexpected error. WaitForMultipleObjects failed.
Type:
Fatal
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory).
Text:
Network communication error.
Type:
Fatal
Add’l Info:
None.
Action:
Check network connectivity. Verify that the Chat
Service is running.
LRM3007
FCCC2002
FCCC2003
FCCC2004
FCCC2005
108
December 17, 2014
Error Messages
Error
Description
FCCC2009
Text:
Unexpected exception.
Type:
Fatal
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory).
Text:
Unable to open registry key.
Type:
Fatal
Add’l Info:
None.
Action:
The specified registry key should exist, but the
program will continue to function without it.The
installation may have failed or become
corrupted. If the registry entry does exist, check
system resource availability (CPU and memory).
Text:
Unable to read registry value.
Type:
Fatal
Add’l Info:
None.
Action:
The specified registry value should exist, but the
program will continue to function without it.The
installation may have failed or become
corrupted. If the registry entry does exist, check
system resource availability (CPU and memory).
Text:
Unable to determine the local IP address. The
program will continue to function, but VPN
desktops will not be supported. Error code: %d.
Type:
Fatal
Add’l Info:
None.
Action:
Restart the program if this is a VPN desktop
(CAD/CSD). If the condition continues to occur,
check the network configuration and make sure
the system has a valid IP address. If the network
settings are valid, then check system resource
availability (CPU and memory).
FCCC2010
FCCC2011
FCCC2014
December 17, 2014
109
Cisco CAD Error Code Dictionary
Error
Description
FCCC2015
Text:
The connection to the Desktop Chat Service has
been lost. The program will attempt to reconnect
automatically.
Type:
Fatal
Add’l Info:
None.
Action:
Check network connectivity. Verify that the Chat
Service is running.
Text:
The transcript directory does not exist and was
unable to be created.
Type:
Error
Add’l Info:
The transcript directory doesn’t exist and was
unable to be created.
Action:
Check file permissions.
Text:
The transcript file \“%ls\” does not exist and
was unable to be created.
Type:
Error
Add’l Info:
The transcript file does not exist and was unable
to be created.
Action:
Check file permissions.
Text:
Unable to close thread handle.
Type:
Warn
Add’l Info:
None.
Action:
The program should continue to function
normally. Check system resource availability
(CPU and memory). Monitor handle usage by this
service.
Text:
Failed to start monitoring \“%ls\”, got error:
[%d|%ls].
Type:
Error
Add’l Info:
A failure occurred while starting to monitor a
presence group.
Action:
Presence chatting may not work, check
presence server status.
FCCC2016
FCCC2017
FCCC3000
FCCC3001
110
December 17, 2014
Error Messages
Error
Description
FCCC3002
Text:
Failed to stop monitoring \“%ls\”, got error:
[%d|%ls].
Type:
Error
Add’l Info:
A failure occurred while stopping to monitor a
presence group.
Text:
Presence chatting may not work, check
presence server status.
Text:
Unable to create thread.
Type:
Fatal
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory).
Text:
Unable to start any working threads.
Type:
Fatal
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory).
Text:
Error handling command line arguments.
Type:
Fatal
Add’l Info:
None.
Action:
If you are attempting to run this program from
the command line, then check the command
line usage.Normally this program should only be
run as a service, but TAC or DE may advise you
to run at as a console application.
Text:
Unexpected error. Wait For Multiple Objects
failed.
Type:
Fatal
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory).
FCCS1001
FCCS1002
FCCS1003
FCCS1007
December 17, 2014
111
Cisco CAD Error Code Dictionary
Error
Description
FCCS1008
Text:
Unexpected network communication error
(omniORB fatalException). File: %hs, line: %d,
msg: %hs.
Type:
Fatal
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory). Check network settings.
Text:
Unable to open registry key.
Type:
Fatal
Add’l Info:
None.
Action:
The specified registry key is required for the
service to function properly. The installation may
have failed or become corrupted. If the registry
entry does exist, check system resource
availability (CPU and memory).
Text:
Unable to read registry value.
Type:
Fatal
Add’l Info:
None.
Action:
The specified registry value is required for the
service to function properly. The installation may
have failed or become corrupted. If the registry
entry does exist, check system resource
availability (CPU and memory).
Text:
Unable to initialize log files.
Type:
Fatal
Add’l Info:
None.
Action:
The service was unable to set up it's logging
files. Check the INSTALLATION
DIRECTORYregistry value under
HKEY_LOCAL_MACHINE\SOFTWARE\Calabrio\
CAD\Site Setup and verify that it's valid.Check
the settings for the service in the service control
panel and verify that it's running under the Local
System account. Check system resource
availability (CPU and memory).
FCCS1009
FCCS1010
FCCS1011
112
December 17, 2014
Error Messages
Error
Description
FCCS1012
Text:
Unexpected exception during network
communication initialization (omniORB).
Type:
Fatal
Add’l Info:
None.
Action:
Verify that the HKEY_LOCAL_MACHINE\
SOFTWARE\Calabrio\CAD\Site Setup\IOR
HOSTNAME registry value specify's a valid local
hostname or IP address. Check system resource
availability (CPU and memory).
Text:
Unexpected exception in the main network
communication thread (fcCorbaServer).
Type:
Fatal
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory).
Text:
Registry error (DetectRegistryChg::Open). Unable
to open path key <%ls> key <%ls>: <%d>.
Type:
Error
Add’l Info:
None.
Action:
The service will automatically retry the
operation. The specified registry key is required
for the service to function properly. If the
condition continues to occur, the installation
may have failed or become corrupted. If the
registry entry does exist, check system resource
availability (CPU and memory).
Text:
Unable to connect to the LDAP service.
Type:
Error
Add’l Info:
None.
Action:
Verify that the LDAP Monitor Service is running.
Check the LDAP Monitor Service logs for errors.
Text:
Unable to create a new working thread.
Type:
Error
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory).
FCCS1013
FCCS2000
FCCS2001
FCCS2002
December 17, 2014
113
Cisco CAD Error Code Dictionary
Error
Description
FCCS2003
Text:
Unexpected exception in a working thread.
Type:
Error
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory).
Text:
Unexpected exception in the manager thread.
Type:
Error
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory).
Text:
Unexpected exception.
Type:
Error
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory).
Text:
Unable to open registry key.
Type:
Error
Add’l Info:
None.
Action:
The specified registry key should exist, but the
service will continue to function without it.The
installation may have failed or become
corrupted. If the registry entry does exist, check
system resource availability (CPU and memory).
Text:
Unable to read registry value.
Type:
Error
Add’l Info:
None.
Action:
The specified registry value should exist, but the
service will continue to function without it.The
installation may have failed or become
corrupted. If the registry entry does exist, check
system resource availability (CPU and memory).
FCCS2004
FCCS2009
FCCS2010
FCCS2011
114
December 17, 2014
Error Messages
Error
Description
FCCS2012
Text:
Unable to set the process priority for this service
to high. The service will run at normal priority.
Type:
Error
Add’l Info:
None.
Action:
The service will continue to run, and should run
normally. However, in some cases under heavy
server load it's possible that by running at
normal priority the service will not get the
needed CPU time to keep up with it's tasks. The
symptom for this would be sluggish behavior in
CAD and CSD.
Text:
Unable to initialize the network communication
library. The service will continue to function, but
VPN desktops will not be supported. Error code:
%d.
Type:
Error
Add’l Info:
None.
Action:
Restart the service if you have any VPN desktops
(CAD/CSD). If the condition continues to occur,
check system resource availability (CPU and
memory).
Text:
Unable to determine the local IP address. The
service will continue to function, but VPN
desktops will not be supported. Error code: %d.
Type:
Error
Add’l Info:
None.
Action:
Restart the service if you have any VPN desktops
(CAD/CSD). If the condition continues to occur,
check the network configuration and make sure
the system has a valid IP address. If the network
settings are valid, then check system resource
availability (CPU and memory).
FCCS2013
FCCS2014
December 17, 2014
115
Cisco CAD Error Code Dictionary
Error
Description
FCCS2015
Text:
Unexpected network communication error in the
VPN-support thread. The service will continue to
function, but VPN desktops will not be
supported. Error code: %d.
Type:
Error
Add’l Info:
None.
Action:
Restart the service if you have any VPN desktops
(CAD/CSD). If the condition continues to occur,
check the network configuration and make sure
the system has a valid IP address. If the network
settings are valid, then check system resource
availability (CPU and memory).
Text:
Unexpected network communication error in the
VPN-support thread. The service will continue to
function, but VPN desktops will not be
supported.
Type:
Error
Add’l Info:
Unexpected exception in the VPN-support
thread. The service will continue to function, but
VPN desktops will not be supported.
Action:
Restart the service if you have any VPN desktops
(CAD/CSD). If the condition continues to occur,
check the network configuration and make sure
the system has a valid IP address. If the network
settings are valid, then check system resource
availability (CPU and memory).
Text:
Unable to close thread handle.
Type:
Warn
Add’l Info:
None.
Action:
Restart the service if you have any VPN desktops
(CAD/CSD). If the condition continues to occur,
check the network configuration and make sure
the system has a valid IP address. If the network
settings are valid, then check system resource
availability (CPU and memory).
FCCS2016
FCCS3000
116
December 17, 2014
Error Messages
Error
Description
FCCS3008
Text:
Network communication error sending message
to application. The application will be logged out.
Type:
Warn
Add’l Info:
None.
Action:
The service should continue to function
normally. Check system resource availability
(CPU and memory). Monitor handle usage by this
service.
Text:
The Admin Workstation Database connection
has not been configured. ASA statistics will be
unavailable.
Type:
Error
Add’l Info:
None.
Action:
Verify RASCAL database setup.
Text:
Rascal Database is currently at %d kilobytes,
max size allowed is %d kilobytes
Type:
Warn
Add’l Info:
Rascal Database is currently at <xxx> kilobytes,
max size allowed is <xxx> kilobytes
Action:
Check the Rascal Server Log files for additional
error messages. Ensure that the daily purge
functionality is working correctly. Ensure that all
SQL Server agent jobs are running correctly.
Perform a complete backup to cause the log file
to be checkpointed, then run the SQL server
agent jobs manually.
FCRasServer0220
FCRasServer0226
December 17, 2014
117
Cisco CAD Error Code Dictionary
Error
Description
FCRasServer0227
Text:
Daily purge may not be working. Table has at
least one record that is %d days old; this
message is triggered when a record is %d days
old.
Type:
Warn
Add’l Info:
Daily purge may not be working. Table <name>
has at least one record that is <xxx> days old;
this message is triggered when a record is <xxx>
days old.
Action:
Check the Rascal Server Log files for additional
error messages. Ensure that the daily purge
functionality is working correctly. Ensure that all
Sql Server agent jobs are running correctly. Stop
and restart sql server instance to free up any
locks or transactions that are holding records
open. Perform a complete backup to cause the
log file to be checkpointed, then run the Sql
server agent jobs manually.
Text:
Unexpected exception during network
communication initialization.
Type:
Fatal
Add’l Info:
Unexpected exception during network
communication initialization
Action:
None
Text:
Unexpected exception in the main network
communication thread.
Type:
Fatal
Add’l Info:
Unexpected exception in the main network
communication thread <message>
Action:
None
FCRasServer1012
FCRasServer1013
118
December 17, 2014
Error Messages
Error
Description
FCRasServer2002
Text:
The ADS query queue is full. Some agent data
will be lost.
Type:
Error
Add’l Info:
The ADS query queue is full. Some agent data
will be lost.
Action:
Check that the CAD Sql Server engine is running.
Check that the CAD database is not full. Check
the Common log file for other error messages.
Check the System Event Viewer for system
errors.
Text:
Unexpected exception.
Type:
Error
Add’l Info:
Unexpected exception
Action:
Check the Common log file for other error
messages. Check the System Event Viewer for
system errors.
Text:
All available connections to the database are in
use. (using a Disconnected Connection).
Type:
Error
Add’l Info:
All available connections to the database are in
use. (using a Disconnected Connection)
Action:
Check the Rascal log file for other error
messages. Check the System Event Viewer for
system errors. Restart the Rascal server to free
up connections.
Text:
Failure when executing query
Type:
Error
Add’l Info:
Failure when executing query
Action:
None.
Text:
Database Update Error
Type:
Error
Add’l Info:
Database Update Error: (Remainder of message
gives more detail.)
Action:
Check the Rascal log file and debug files for
other error messages. Check the System Event
Viewer for system errors.
FCRasServer2009
FCRasServer2108
FCRasServer2109
FCRasServer2110
December 17, 2014
119
Cisco CAD Error Code Dictionary
Error
Description
FCVRS1001
Text:
Unable to create thread.
Type:
Fatal
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory).
Text:
Error handling command line arguments.
Type:
Fatal
Add’l Info:
None.
Action:
Check the command line usage.
Text:
Unexpected error. WaitForMultipleObjects failed.
Type:
Fatal
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory).
Text:
Unexpected network communication error
(omniORB fatalException). File: %S, line: %d,
msg: %S.
Type:
Fatal
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory). Check network settings.
Text:
Unable to open registry key.
Type:
Fatal
Add’l Info:
None.
Action:
The specified registry key is required for the
service to function properly. The installation may
have failed or become corrupted. If the registry
entry does exist, check system resource
availability (CPU and memory).
FCVRS1003
FCVRS1007
FCVRS1008
FCVRS1009
120
December 17, 2014
Error Messages
Error
Description
FCVRS1010
Text:
Unable to read registry value.
Type:
Fatal
Add’l Info:
None.
Action:
The specified registry value is required for the
service to function properly. The installation may
have failed or become corrupted. If the registry
entry does exist, check system resource
availability (CPU and memory).
Text:
Unable to initialize log files.
Type:
Fatal
Add’l Info:
None.
Action:
The service was unable to set up it's logging
files. Check the INSTALLATION DIRECTORY
registry value under HKEY_LOCAL_MACHINE\
SOFTWARE\Calabrio\CAD\Site Setup and verify
that it's valid.Check the settings for the service
in the service control panel and verify that it's
running under the Local System account. Check
system resource availability (CPU and memory).
Text:
Unexpected exception during network
communication initialization.
Type:
Fatal
Add’l Info:
None.
Action:
Verify that the HKEY_LOCAL_MACHINE\
SOFTWARE\Calabrio\CAD\Site Setup\IOR
HOSTNAME registry value specify's a valid local
hostname or IP address. Check system resource
availability (CPU and memory).
Text:
Unexpected exception in the main network
communication thread.
Type:
Fatal
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory). If the problem continues to occur,
gather debug logs for the service and open a
TAC case.
FCVRS1011
FCVRS1012
FCVRS1013
December 17, 2014
121
Cisco CAD Error Code Dictionary
Error
Description
FCVRS2000
Text:
Registry error. DetectRegistryChg::Open failed
for path <%s> key <%s>: <%d>.
Type:
Error
Add’l Info:
None.
Action:
The service will automatically retry the
operation. The specified registry key is required
for the service to function properly. If the
condition continues to occur, the installation
may have failed or become corrupted. If the
registry entry does exist, check system resource
availability (CPU and memory).
Text:
Unable to connect to the LDAP service.
Type:
Error
Add’l Info:
None.
Action:
Verify that the LDAP Monitor Service is running.
Check the LDAP Monitor Service logs for errors.
Text:
The ADS query queue is full. Some agent data
will be lost.
Type:
Error
Add’l Info:
None.
Action:
ADS database queries are backing up and being
discarded as needed to control the size of the
queue. Verify that the ADS is running. Check
system resource availability (CPU) on the servers
that run this service and the ADS.
Text:
Network communication error.
Type:
Error
Add’l Info:
None.
Action:
Check network connectivity between the
Recording and Statistics S.The remote
application may have terminated abnormally,
check it's logs for errors.Check any firewall
settings to make sure that the proper ports are
open. See the port utilization guide for more
information on this.
FCVRS2001
FCVRS2002
FCVRS2008
122
December 17, 2014
Error Messages
Error
Description
FCVRS2009
Text:
Unexpected exception.
Type:
Error
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory). If system resources are fine and the
condition continues to occur, recreate the
problem with debug logging turned on to further
isolate.
Text:
Unable to open registry key.
Type:
Error
Add’l Info:
None.
Action:
The specified registry key should exist, but the
service will continue to function without it.The
installation may have failed or become
corrupted. If the registry entry does exist, check
system resource availability (CPU and memory).
Text:
Unable to read registry value.
Type:
Error
Add’l Info:
None.
Action:
The specified registry value should exist, but the
service will continue to function without it.The
installation may have failed or become
corrupted. If the registry entry does exist, check
system resource availability (CPU and memory).
Text:
Unable to set the process priority for this service
to high. The service will run at normal priority.
Type:
Error
Add’l Info:
None.
Action:
The service will continue to run, and should run
normally. However, in some cases under heavy
server load it's possible that by running at
normal priority the service will not get the
needed CPU time to keep up with it's tasks. The
symptom for this would be sluggish behavior in
CAD and CSD. If this occurs, open a TAC case.
FCVRS2010
FCVRS2011
FCVRS2012
December 17, 2014
123
Cisco CAD Error Code Dictionary
Error
Description
FCVRS2013
Text:
Unable to initialize the network communication
library. The service will continue to function, but
VPN desktops will not be supported. Error code:
%d.
Type:
Error
Add’l Info:
None.
Action:
Restart the service if you have any VPN desktops
(CAD/CSD). If the condition continues to occur,
check system resource availability (CPU and
memory).
Text:
Unable to write registry value.
Type:
Error
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory).
Text:
The name of the ADS SQL named instance was
not found in LDAP. Will retry.
Type:
Error
Add’l Info:
None.
Action:
The service will retry the operation. If the
problem continues to occur, open a TAC case.
Text:
An error occurred trying to populate the cache
from the ADS database. Will retry.
Type:
Error
Add’l Info:
None.
Action:
The service will retry the operation. If the
problem continues to occur, check for other
more specific errors related to the database
access. Verify that the ADS database is running.
Text:
An error occurred while attempting to register
this service in LDAP.
Type:
Error
Add’l Info:
None.
Action:
The service will retry the operation. If the
problem continues to occur, check the LDAP
service logs for more information.
FCVRS2015
FCVRS2016
FCVRS2017
FCVRS2018
124
December 17, 2014
Error Messages
Error
Description
FCVRS2019
Text:
SQL Query failed with SQL error %s for query %s.
Type:
Error
Add’l Info:
None.
Action:
The service will continue to run and recover it's
connection to the database as needed.Verify
that the SQL statement is valid. Verify that the
ADS is running.
Text:
The Admin Workstation Database connection
has not been configured. ASA statistics will be
unavailable.
Type:
Error
Add’l Info:
None.
Action:
Configure the connection to the Admin
Workstation Database in the Cisco Agent
Desktop Configuration Setup program, then
restart the Recording and Statistics Service.
Text:
Unable to close thread handle.
Type:
Warn
Add’l Info:
None.
Action:
The service should continue to function
normally. Check system resource availability
(CPU and memory). Monitor handle usage by this
service.
Text:
Unable to retrieve the list of skill groups from
LDAP. Will retry.
Type:
Warn
Add’l Info:
None.
Action:
The service will retry the operation. If the
problem continues to occur, check the contents
of LDAP for skill group information. If skill group
data is missing, check the Sync Service logs for
any problems.
FCVRS2020
FCVRS3000
FCVRS3001
December 17, 2014
125
Cisco CAD Error Code Dictionary
Error
Description
FMWK2000
Text:
CORBA::TRANSIENT is raised minor:<%d>,
completion_status:<%d>, retries<%d>.
Type:
Warn
Add’l Info:
None.
Action:
None.
Text:
AtlUnadvise failed. Error code = 0x<%x>, <%s>.
Type:
Warn
Add’l Info:
None.
Action:
None.
Text:
Could not read the Admin Password Set from
LDAP. Error code = <%d>, <%s>.
Type:
Warn
Add’l Info:
None.
Action:
None.
Text:
Could not save Admin Password to LDAP. Error
code = <%d>, <%s>.
Type:
Warn
Add’l Info:
None.
Action:
None.
Text:
Could not read the server profile from LDAP.
Error code = <%d>, <%s>.
Type:
Warn
Add’l Info:
None.
Action:
None.
Text:
Could not save the server type profile to LDAP.
Error code = <%d>, <%s>.
Type:
Warn
Add’l Info:
None.
Action:
None.
FMWK2001
FMWK2002
FMWK2003
FMWK2004
FMWK2005
126
December 17, 2014
Error Messages
Error
Description
FMWK2006
Text:
Could not read product offering from LDAP. Error
code = <%d>, <%s>.
Type:
Warn
Add’l Info:
None.
Action:
None.
Text:
Wait returns <%d> : Handle could be bad.
Type:
Error
Add’l Info:
The function that was called has failed to
respond.
Action:
None.
Text:
Failed to get local LCC from the registry.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error in GetKeyValue for
LCUSTOM_KEY_ALLOWUPDATE. Error = <%s>.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
AutoRecoverConnection failed. Error code =
<%d>, <%s>.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Failed to open registry key.
Type:
Error
Add’l Info:
None.
Action:
None.
FMWK3000
FMWK3001
FMWK3002
FMWK3003
FMWK3004
December 17, 2014
127
Cisco CAD Error Code Dictionary
Error
Description
FMWK3005
Text:
Failed to read value on Entry in the registry key.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Failed to write value 1 on Entry in the registry
key.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error creating process.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Failed to write value 0 on Entry in the registry
key.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error saving server profile.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error updating the Active TServer entry.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error getting server profile.
Type:
Error
Add’l Info:
None.
Action:
None.
FMWK3006
FMWK3007
FMWK3008
FMWK3009
FMWK3010
FMWK3011
128
December 17, 2014
Error Messages
Error
Description
FMWK3012
Text:
Failed to write value to the registry key.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Failed to iterate registry key.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error GetKeyValue Switch Type. Error code =
<%d>, <%s>.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error GetKeyValue CTI Type. Error code = <%d>,
<%s>.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error GetServerTypeProfile. Error code = <%d>,
<%s>.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error getting switch and CTI type.
Type:
Error
Add’l Info:
None.
Action:
None.
FMWK3013
FMWK3014
FMWK3015
FMWK3016
FMWK3017
December 17, 2014
129
Cisco CAD Error Code Dictionary
Error
Description
FMWK3018
Text:
Could not establish open stream with definity
switch.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Timeout waiting for TServer to return.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Couldn't establish definity event poll. Error code
= <%d>.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error getting GetServerIOR for Sync Server.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Corba Error. CORBA::is_nil(vDAS).
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error synchronizing directory services.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Could not update Required Admin Password.
Type:
Error
Add’l Info:
None.
Action:
None.
FMWK3019
FMWK3020
FMWK3021
FMWK3022
FMWK3023
FMWK3024
130
December 17, 2014
Error Messages
Error
Description
FMWK3025
Text:
Could not set the new Admin Pwd.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Failed to load Enterprise Administrator
(TSSPAdm.exe).
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Failed to load Personnel.exe.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Failed to load Administrator.exe.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Failed to load IPCCAdm.exe.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Failed to load SWFAdmin.exe.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Could not add workspace for server name.
Type:
Error
Add’l Info:
None.
Action:
None.
FMWK3026
FMWK3027
FMWK3028
FMWK3029
FMWK3032
FMWK3033
December 17, 2014
131
Cisco CAD Error Code Dictionary
Error
Description
FMWK3034
Text:
Unexpected error reported.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error = <%s>.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Failed to get local LCC from the registry. Error
code = <%d>, <%s>.
Type:
Fatal
Add’l Info:
None.
Action:
None.
Text:
AutoRecoverConnection failed ExitInstance.
Error code = <%d>, <%s>.
Type:
Fatal
Add’l Info:
None.
Action:
None.
Text:
Out of memory.
Type:
Fatal
Add’l Info:
None.
Action:
None.
Text:
Unknown Exception.
Type:
Fatal
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory).
Text:
Exception. Description = <%ls>
Type:
Fatal
Add’l Info:
None.
Action:
Check Description.
FMWK3035
FMWK4000
FMWK4001
FMWK4002
IPCA1000
IPCA1001
132
December 17, 2014
Error Messages
Error
Description
IPCA2001
Text:
LDAP connection failed. Description = <%ls>.
Type:
Error
Add’l Info:
None.
Action:
Check LDAP Server is running.
Text:
LdapClient API <%ls> failed. Discription =
<%ls>.
Type:
Error
Add’l Info:
None
Action:
Check LDAP Server is running.
Text:
Error Obtaining License. Error: %ls
Type:
Error
Add’l Info:
None.
Action:
Check LRM Server is running.
Text:
Unknown Exception.
Type:
Error
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory).
Text:
Exception. Description = <%ls>
Type:
Error
Add’l Info:
None.
Action:
Check Description.
Text:
Error deleting agent profile. Description =
<%ls>.
Type:
Error
Add’l Info:
None.
Action:
Check Enterprise Server is running.
Text:
Error loading data.
Type:
Error
Add’l Info:
None.
Action:
Check LDAP Server is running.
IPCA2002
IPCA2003
IPCA2004
IPCA2005
IPCA2006
IPCA2007
December 17, 2014
133
Cisco CAD Error Code Dictionary
Error
Description
IPCA2008
Text:
Error writing data to LDAP.
Type:
Error
Add’l Info:
None.
Action:
Check LDAP Server is running.
Text:
Error notifying IPPA Server.
Type:
Error
Add’l Info:
None.
Action:
Check IPPA Server is running.
Text:
Error Reading dynamic re-skilling site1 from
LDAP. Error: %ls
Type:
Error
Add’l Info:
Error reading the dynamic reskilling site.
Action:
None.
Text:
Error Reading dynamic re-skilling site2 from
LDAP. Error: %ls
Type:
Error
Add’l Info:
Error reading the dynamic reskilling site.
Action:
None.
Text:
Error Writing dynamic re-skilling site to LDAP.
Error: %ls
Type:
Error
Add’l Info:
Error writing the dynamic reskilling site.
Action:
None.
Text:
Caught exception in Reading dynamic re-skilling
site from LDAP. Error: %ls
Type:
Error
Add’l Info:
Exception in reading dynamic reskilling site.
Action:
None.
IPCA2009
IPCA2010
IPCA2011
IPCA2012
IPCA2013
134
December 17, 2014
Error Messages
Error
Description
IPCA2014
Text:
Caught exception in Writing dynamic re-skilling
site from LDAP. Error: %ls
Type:
Error
Add’l Info:
Exception in writing dynamic reskilling site.
None.
IPCA2015
IPPA2000
IPPA2001
December 17, 2014
Text:
Caught exception in OnInitialUpdate in
Agentview.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Cannot get locale for IPPA client..
Type:
Error
Add’l Info:
IPPA client cannot get the locale to use.
Action:
Make sure BIPPA service has started at least
once on the same computer as IPPA client so
that IPPAClient.properties will be updated by
BIPPA service. See IPPAClient.properties to
ensure the ippa.language and ippa.country have
been set to supported language/country. If not,
restart BIPPA service to see if BIPPA service
updates them to valid values. IPPA client does
not have permission to read from
IPPAClient.properties.
Text:
Cannot get resource bundle for <%s> locale: %s
Type:
Error
Add’l Info:
IPPA client cannot get resource bundle for
specified locale.
Action:
Check actions for IPPA2000. An internal error
where the resource bundle for specified local is
missing. Contact technical support.
135
Cisco CAD Error Code Dictionary
Error
Description
IPPA2002
Text:
Cannot get environment properties because of
security restrictions: %s
Type:
Error
Add’l Info:
IPPA client cannot get environment properties
because of security restrictions.
Action:
Tomcat is not configured correctly to allow IPPA
client servlet to access environment settings.
Check security policy of Tomcat.
Text:
Cannot read IPPA client configuration file <%s>:
%s
Type:
Error
Add’l Info:
IPPA client cannot read the IPPA client
configuration file.
Action:
Verify if IPPAClient.properties exists in Tomcat
config directory. If the exception is a security
exception, verify Tomcat is configured to allow
IPPA client servlet to access
IPPAClient.properties file in the Tomcat config
directory.
Text:
Agent phone IP address <%s>: Unexpected error
caught: %s
Type:
Error
Add’l Info:
The IPPA client encountered an unexpected
error.
Action:
Contact technical support.
Text:
Agent phone IP address <%s>: Invalid BIPPA
service CORBA IOR <%s>.
Type:
Error
Add’l Info:
The IPPA client found an invalid BIPPA service
CORBA IOR in the configuration file.
Action:
Restart the BIPPA service and verify the CORBA
IOR in IPPAClient.properties changes. If the
CORBA IOR does not change, BIPPA service does
not have permissions to write to the file. Make
sure the BIPPA service is run as a user with
sufficient permissions to change the properties
in the file.
IPPA2003
IPPA2004
IPPA2005
136
December 17, 2014
Error Messages
Error
Description
IPPA2006
Text:
Agent phone IP address <%s>: IPPA client
cannot connect to BIPPA service: %s.
Type:
Error
Add’l Info:
The IPPA client cannot connect to BIPPA service.
Action:
Verify to see if BIPPA service is running and
active. If not, follow troubleshooting section on
getting BIPPA service running and active. If
BIPPA service is running and active, Verify if
there are firewalls issue.
Text:
Unexpected error caught: %s
Type:
Error
Add’l Info:
The IPPA client JSP encountered an unexpected
error.
Action:
Contact technical support.
Text:
Cannot read BIPPA service configuration file
<%s>: %s
Type:
Error
Add’l Info:
IPPA client cannot read the BIPPA service
configuration file.
Action:
(Linux only) Verify if UCCX_HOME environment
variable is visible to IPPA servlet. Verify if
IPPASvr.cfg exists in
$UCCX_HOME/desktop/config (Linux) or
~/Desktop/config (Windows) directory. If the
exception is a security exception, verify Tomcat
is configured to allow IPPA client servlet to
access IPPASvr.cfg file in
$UCCX_HOME/desktop/config (Linux) or
~/Desktop/config (Windows) directory.
IPPA2007
IPPA2008
December 17, 2014
137
Cisco CAD Error Code Dictionary
Error
Description
IPPA3000
Text:
No localized string or resource found for the
given key <%s>: %s.
Type:
Warn
Add’l Info:
The IPPA client cannot get the localized string or
resource for the given key.
Action:
There may be a mismatch between the IPPA
client version and the service version. Check the
version of IPPASvr.exe and ipphone.war to make
sure they match. Make sure the locale used by
IPPA client is a supported language or country. If
you verified the previous actions and the error
persists, this is an internal error where given key
is not found in the localized resource file.
Contact technical support.
Text:
Agent phone IP address <%s>: Invalid message
ID <%s> passed from BIPPA service: %s.
Type:
Warn
Add’l Info:
The IPPA client received an invalid message ID
from the BIPPA service.
Action:
There may be a mismatch between the IPPA
client version and the service version. Check the
version of IPPASvr.exe and ipphone.war to make
sure they match. If you verified the previous
action and the error persists, this is an internal
error. Contact technical support.
Text:
Agent phone IP address <%s>: Invalid message
ID <%d> passed from BIPPA service.
Type:
Warn
Add’l Info:
The IPPA client received an invalid message ID
from the BIPPA service.
Action:
There may be a mismatch between the IPPA
client version and the service version. Check the
version of IPPASvr.exe and ipphone.war to make
sure they match. If you verified the previous
action and the error persists, this is an internal
error. Contact technical support.
IPPA3001
IPPA3002
138
December 17, 2014
Error Messages
Error
Description
IPPA3003
Text:
Agent phone IP address <%s>: Invalid argument
<%s> for parameter %s passed to the IPPA client
JSP %s: %s
Type:
Warn
Add’l Info:
The IPPA client received an invalid argument to
JSP script.
Action:
Make sure the URL used by the agent is correct.
Text:
Cannot convert a Java string to a CORBA string:
%s
Type:
Warn
Add’l Info:
The IPPA client cannot convert a Java string to a
CORBA string to send to the BIPPA service.
Action:
This is an internal error. Contact technical
support.
Text:
Cannot convert a CORBA string to a Java string:
%s
Type:
Warn
Add’l Info:
The IPPA client received a CORBA string from
BIPPA service that could not be converted to a
Java string.
Action:
This is an internal error. Contact technical
support.
Text:
Cannot convert a CORBA byte array to a UTF-8
string: %s
Type:
Warn
Add’l Info:
The IPPA client received a CORBA byte array
from the BIPPA service that could not be
converted to a UTF-8 string.
Action:
This is an internal error. Contact technical
support.
IPPA3004
IPPA3005
IPPA3006
December 17, 2014
139
Cisco CAD Error Code Dictionary
Error
Description
IPPA3007
Text:
Agent phone IP address <%s>: IPPA client
encountered an unexpected error while making
<%s> call to the BIPPA service: %s
Type:
Warn
Add’l Info:
The IPPA client encountered an unexpected
error while making the specified call to the
BIPPA service.
Action:
The IPPA client will automatically drop and
reconnect to the BIPPA service before trying the
same call again. If it succeeds, no action is
required. If it keeps failing, contact technical
support.
Text:
Agent phone IP address <%s>: IPPA client
encountered an error <%d:%s> while making
<%s> call to BIPPA service.
Type:
Warn
Add’l Info:
The IPPA client encountered an error while
making the specified call to the BIPPA service.
Action:
See the error code and its description and take
appropriate action for that method.
Text:
No arguments passed to application.
Type:
Fatal
Add’l Info:
No arguments were passed to application.
Action:
Call application passing old IP address.
Text:
Empty argument was passed to application.
Type:
Fatal
Add’l Info:
Empty argument was passed to application.
Action:
Call application passing old IP address.
IPPA3008
IPAC1000
IPAC1001
140
December 17, 2014
Error Messages
Error
Description
IPAC2000
Text:
Unable to delete server type <%ls> server profile
for IP address <%ls>: <%d:%ls>.
Type:
Error
Add’l Info:
An error occurred while deleting specified servet
type’s server profile for specified IP address
from LDAP.
Action:
Check that LDAP service is running. Check that
LDAP Host 1 and/or LDAP Host 2 is pointing to
the right running LDAP service(s). The LDAP error
code and description in the log message can
provide specific information about why it failed.
Text:
An unexpected error occurred.
Type:
Fatal
Add’l Info:
Encountered an unexpected error.
Action:
None.
Text:
Error: <%d> <%ls>
Type:
Error
Add’l Info:
An exception was caught.
Action:
None.
Text:
Error: <%ls>
Type:
Error
Add’l Info:
An exception was caught
Action:
None.
Text:
Unexpected error reported.
Type:
Error
Add’l Info:
An unexpected error occurred.
Action:
None.
Text:
Failed: <%ls> Error: <%d> <%ls>
Type:
Error
Add’l Info:
An unexpected error occurred.
Action:
None.
LA1001
LA2000
LA2001
LA2002
LA2003
December 17, 2014
141
Cisco CAD Error Code Dictionary
Error
Description
LA2004
Text:
Error launch license url = <%ls>.
Type:
Error
Add’l Info:
An unexpected error occurred.
Action:
None.
Text:
Error notifying LRM of license update. Manually
restart LRM service.
Type:
Error
Add’l Info:
Could not refresh LRM license information.
Action:
Manually restart LRM server.
Text:
Unable to connect to process <%ls>: Error
<%ls>.
Type:
Warn
Add’l Info:
Unable to connect to specified process.
Action:
None.
Text:
Waitable object destroyed while waiting.
Stopping thread.
Type:
Warn
Add’l Info:
Waitable object has been destroyed while
waiting on it, the thread will shut down now.
Action:
None.
Text:
An exception occurred in <%ls(%ls, %ls)> while
%ls -- %ls
Type:
Warn
Add’l Info:
Error occurred while performing an LDAP
operation.
Action:
None.
Text:
The LDAP host name index is invalid.
Type:
Warn
Add’l Info:
Invalid LDAP Host Name index.
Action:
Review the debug log file. The debug log file will
contain specific information about this error.
LA2005
LA3000
LA3001
LC0001
LC0002
142
December 17, 2014
Error Messages
Error
Description
LC0003
Text:
Currently in recovery to service.
Type:
Warn
Add’l Info:
Currently in recovery to [service] service.
Action:
LdapClient is trying to connect to the service.
Check the log file after a small duration. If
LdapClient still can't connect to the service,
restart the service.
Text:
The LDAP replication check has failed. Data is
not successfully replicating.
Type:
Error
Add’l Info:
The LDAP replication check has failed.
Action:
Verify both LDAP servers are running and able to
communicate with each other.
Text:
Failed to finish configuring LDAP with replication
strategy: <%ls>. Reason: <%ls>
Type:
Error
Add’l Info:
The setup of the specified LDAP replication
strategy failed.
Action:
Ensure both LDAP Monitor servers are running
and can communicate with each other. There
also could be a locked file or bad socket that
may be fixed by restarting the server(s).
Text:
The two servers are on different versions. No
LDAP replication will be setup until the versions
match. Details <%ls>
Type:
Error
Add’l Info:
The two servers in the cluster are on different
versions. LDAP replication requires both systems
to be at the same version.
Action:
Finish upgrading/applying any patches currently
in process. After the software is on the exact
same version on both systems, this should go
away.
LMS2000
LMS2001
LMS2002
December 17, 2014
143
Cisco CAD Error Code Dictionary
Error
Description
LMS2003
Text:
LDAP Backup could not be completed due to
problems accessing the backup file and archive.
Reason <%ls>.
Type:
Error
Add’l Info:
The LDAP backup could not be completed due to
some problem with the file or the file system.
Action:
Ensure file access permissions for the file and
the directory of the archive.
Text:
LDAP Backup could not be completed because
the backup script could not complete
successfully.
Type:
Error
Add’l Info:
The LDAP backup script could not be run
successfully.
Action:
Ensure the script is in the bin directory and has
permission to run.
Text:
LDAP Backup file is not valid. Reason <%ls>.
Type:
Error
Add’l Info:
The LDAP backup file is not valid. It is either
missing a required item or it contains an
unwanted item. See reason for which it is.
Action:
The LDAP database is possibly corrupted.
Recovery may be necessary.
Text:
The process could not be started.
Type:
Warn
Add’l Info:
The process could not be started.
Action:
None
Text:
The process has unexpectedly stopped running.
Type:
Warn
Add’l Info:
The process has unexpectedly stopped running.
Action:
None
LMS2004
LMS2005
LMS3000
LMS3001
144
December 17, 2014
Error Messages
Error
Description
LMS3002
Text:
The setup step failed before starting the
process. Reason <%ls>.
Type:
Warn
Add’l Info:
Before starting the process, the setup step
failed.
Action:
None
Text:
The SocketService could not be started. Reason:
(%ls)
Type:
Fatal
Add’l Info:
The SocketService could not be started.
Action:
Check debug log for details, validate that the
service IP Address and Port are configured
correctly, and that the service is not already
running. Restart the service.
Text:
The LRM service could not determine the local
host addresses. Reason: (%ls)
Type:
Error
Add’l Info:
The LRM Service could not get a list of local
hostnames.
Action:
Check that the server’s network connection is
functioning correctly and that it has a valid Ip
Address and Hostname.
Text:
The LRM client failed to connect to any service.
Type:
Error
Add’l Info:
The LRM Client could not connect to any
services.
Action:
Check that the client is configured properly and
that the LRM server is running.
Text:
GetKeyValue failed. Error = <%d>
Type:
Fatal
Add’l Info:
None.
Action:
None.
LRMS1000
LRMS2000
LRMS2001
PD1001
December 17, 2014
145
Cisco CAD Error Code Dictionary
Error
Description
PD2001
Text:
*** Receive OPEN_CONF. But Peripheral is
OFFLINE ***
Type:
Error
Add’l Info:
Received OPEN_CONF, peripheral is offline
Action:
Verify that peripheral is online
Text:
Example Warn!
Type:
Error
Add’l Info:
Example Warn!
Action:
None
Text:
Error = <%ls>.
Type:
Warn
Add’l Info:
Generic warn message
Action:
See error text for more information.
Text:
Example Fatal!
Type:
Fatal
Add’l Info:
Example Fatal!
Action:
None.
Text:
Error = <%ls>.
Type:
Warn
Add’l Info:
Generic warn Message
Action:
See error text for more information.
Text:
Unable to read registry value at key.
Type:
Warn
Add’l Info:
Unable to read registry value
Action:
See error text for more information.
Text:
Unable to open registry key.
Type:
Warn
Add’l Info:
Unable to open registry key
Action:
See error text for more information.
PD3000
PD3001
PD4000
PI2001
PI2002
PI2003
146
December 17, 2014
Error Messages
Error
Description
PI2004
Text:
Failed to open registry key. Error code = <%d>.
Type:
Warn
Add’l Info:
Failed to open registry key
Action:
See error text for more information.
Text:
Failed to read from the registry. Entry <%ls>, key
<%ls>. Error code = <%d>.
Type:
Warn
Add’l Info:
Failed to read from the registry.
Action:
See error text for more information.
Text:
SetKeyValue failed.
Type:
Warn
Add’l Info:
SetKeyValue failed
Action:
See error text for more information.
Text:
Failed to SetKeyValue for <%ls>.
Type:
Warn
Add’l Info:
Failed to SetKeyValue for
Action:
See error text for more information.
Text:
Error = <%ls>.
Type:
Error
Add’l Info:
Generic Error Message
Action:
See error text for more information.
Text:
Unexpected error reported.
Type:
Error
Add’l Info:
Unexpected error reported.
Action:
Restart PostInstall
Text:
AutoRecoverConnection failed. Error code =
<%d>, <%ls>.
Type:
Error
Add’l Info:
AutoRecoverConnection failed.
Action:
Check LDAP server and try again.
PI2005
PI2006
PI2007
PI3001
PI3002
PI3003
December 17, 2014
147
Cisco CAD Error Code Dictionary
Error
Description
PI3004
Text:
Invalid order index.
Type:
Error
Add’l Info:
Invalid order index
Action:
Check LDAP servers and try again.
Text:
Numbers of Host doesn't match numbers of port
in registry.
Type:
Error
Add’l Info:
Numbers of Host doesn't match numbers of port
in registry.
Action:
None.
Text:
Failed to open registry key. Error code = <%d>.
Type:
Error
Add’l Info:
Failed to open registry key
Action:
Check error text
Text:
Failed to write value to the registry. Entry <%ls>,
key <%ls>. Error code = <%d>.
Type:
Error
Add’l Info:
Failed to write to the registry
Action:
Check error text
Text:
Failed to read value from the registry key. Error
code = <%d>.
Type:
Error
Add’l Info:
Failed to write to the registry
Action:
Check error text
Text:
DeleteServerProfile failed. Error = <%d>, <%ls>.
Type:
Error
Add’l Info:
DeleteServerProfile failed.
Action:
Check LDAP server and try again.
PI3005
PI3006
PI3007
PI3008
PI3009
148
December 17, 2014
Error Messages
Error
Description
PI3010
Text:
UpdateServerTypeProfile failed. Error = <%d>,
<%ls>.
Type:
Error
Add’l Info:
UpdateServerTypeProfile failed.
Action:
Check LDAP server and try again.
Text:
AddServerTypeProfile failed. Error = <%d>,
<%ls>.
Type:
Error
Add’l Info:
AddServerTypeProfile failed.
Action:
Check LDAP server and try again.
Text:
SetKeyValue failed for <%ls>. Error = <%d>,
<%ls>.
Type:
Error
Add’l Info:
SetKeyValue failed.
Action:
Check LDAP server and try again.
Text:
ServerTypeExist failed. Error = <%d>, <%ls>.
Type:
Error
Add’l Info:
ServerTypeExist failed.
Action:
Check LDAP server and try again.
Text:
AppExist failed. Error = <%d>, <%ls>.
Type:
Error
Add’l Info:
AppExist failed.
Action:
Check LDAP server and try again.
Text:
AddApp failed. Error = <%d>, <%ls>.
Type:
Error
Add’l Info:
AddApp failed.
Action:
Check LDAP server and try again.
Text:
SectExist failed. Error = <%d>, <%ls>.
Type:
Error
Add’l Info:
SectExist failed.
Action:
Check LDAP server and try again.
PI3011
PI3012
PI3013
PI3014
PI3015
PI3016
December 17, 2014
149
Cisco CAD Error Code Dictionary
Error
Description
PI3017
Text:
AddSect failed. Error = <%d>, <%ls>.
Type:
Error
Add’l Info:
AddSect failed.
Action:
Check LDAP server and try again.
Text:
SetKey login failed. Error = <%d>, <%ls>.
Type:
Error
Add’l Info:
SetKey login failed.
Action:
Check LDAP server and try again.
Text:
SetKey pwd failed. Error = <%d>, <%ls>.
Type:
Error
Add’l Info:
SetKey pwd failed.
Action:
Check LDAP server and try again.
Text:
SetKey CM Version failed. Error = <%d>, <%ls>.
Type:
Error
Add’l Info:
SetKey CM Version failed.
Action:
Check LDAP server and try again.
Text:
Failed on GetServerProfileList. Error code =
<%d>, <%ls>.
Type:
Error
Add’l Info:
GetServerProfileList failed.
Action:
Check LDAP server and try again.
Text:
Unknown server type. Expecting
LCUSTOM_SVR_TYPE_SWITCH_CTI_SERVER,
LCUSTOM_SVR_TYPE_IVR_CTI_SERVER or
LCUSTOM_SVR_TYPE_SWITCH_CTIOS_SERVER.
Type:
Error
Add’l Info:
Unknown server type.
Action:
Check LDAP server and try again.
PI3018
PI3019
PI3020
PI3021
PI3022
150
December 17, 2014
Error Messages
Error
Description
PI3023
Text:
Invalid order index.
Type:
Error
Add’l Info:
Invalid order index.
Action:
Check LDAP server and try again.
Text:
Failed to delete registry key. Error code = <%d>.
Type:
Error
Add’l Info:
Failed to delete registry key
Action:
Check error text
Text:
Failed to open registry key.
Type:
Error
Add’l Info:
Failed to open registry key
Action:
Check error text
Text:
Failed to read value from the registry key.
Type:
Error
Add’l Info:
Failed to open registry key
Action:
Check error text
Text:
GetKeyValue failed. Error = <%d>, <%ls>.
Type:
Error
Add’l Info:
GetKeyValue failed
Action:
None.
Text:
Failed to read from the registry. Entry <%ls>, key
<%ls>. Error code = <%d>.
Type:
Error
Add’l Info:
Failed to read from the registry.
Action:
See error text for more information.
Text:
Operation failed.
Type:
Error
Add’l Info:
Operation failed.
Action:
None.
PI3024
PI3028
PI3029
PI3037
PI3042
PI3045
December 17, 2014
151
Cisco CAD Error Code Dictionary
Error
Description
PI3046
Text:
Operation failed. IP = <%ls>, API Name = <%ls>,
Error Code = <%d>.
Type:
Error
Add’l Info:
Operation failed.
Action:
None.
Text:
Failed to write to the registry. Entry <%ls>, key
<%ls>. Error code = <%d>.
Type:
Error
Add’l Info:
Operation failed.
Action:
None.
Text:
Failed to remove entry <%ls>, key <%ls>. Error
code = <%d>.
Type:
Error
Add’l Info:
Operation failed.
Action:
None.
Text:
%ls not defined.
Type:
Error
Add’l Info:
Operation failed.
Action:
None.
Text:
Base is not defined. Error = <%ls>.
Type:
Error
Add’l Info:
Operation failed.
Action:
None.
Text:
failed. Error = <%d>, <%ls>.
Type:
Error
Add’l Info:
Operation failed.
Action:
None.
PI3048
PI3049
PI3050
PI3051
PI3053
152
December 17, 2014
Error Messages
Error
Description
PI3054
Text:
Failed to read value from the registry. Entry
<%ls>, key <%ls>. Error code = <%d>.
Type:
Error
Add’l Info:
Failed to open registry key
Action:
Check error text
Text:
LOBYTE/HIBYTE failed.
Type:
Error
Add’l Info:
Operation failed.
Action:
None.
Text:
Screen list is empty.
Type:
Error
Add’l Info:
Operation failed.
Action:
None.
Text:
Unexpected Switch/CTI type.
Type:
Error
Add’l Info:
Operation failed.
Action:
None.
Text:
RestoreDefaultLCCdata failed.
Type:
Error
Add’l Info:
Operation failed.
Action:
None.
Text:
Error in SHGetMalloc.
Type:
Error
Add’l Info:
Operation failed.
Action:
None.
Text:
Error in ParseDisplayName.
Type:
Error
Add’l Info:
Operation failed.
Action:
None.
PI3055
PI3056
PI3057
PI3058
PI3060
PI3061
December 17, 2014
153
Cisco CAD Error Code Dictionary
Error
Description
PI3062
Text:
Error in SHGetPathFromIDList.
Type:
Error
Add’l Info:
Operation failed.
Action:
None.
Text:
Failed to write IOR to the registry.
Type:
Error
Add’l Info:
Operation failed.
Action:
None.
Text:
StartSync failed.
Type:
Error
Add’l Info:
Operation failed.
Action:
None.
Text:
Admin only, no screens to show.
Type:
Error
Add’l Info:
Administrator is the only application installed on
this machine.
Action:
Install agent, supervisor or in case of Enterprise
run it on the server.
Text:
Error parsing LDAP configuration. An error
occurred parsing numbers from the DbCleaner
settings.
Type:
Fatal
Add’l Info:
None.
Action:
Logs should show which settings are actually
wrong.
Text:
Error loading required DLLs. An error occurred
loading required DLLs.
Type:
Error
Add’l Info:
None.
Action:
Restart the application.
PI3063
PI3064
PI3067
QMUT1000
QMUT2002
154
December 17, 2014
Error Messages
Error
Description
QMUT2007
Text:
The application could not find a required DLL.
Type:
Error
Add’l Info:
None.
Action:
Verify the DLL exists and is in the SQM bin
directory.
Text:
The application could not read the output of the
spawned process.
Type:
Warn
Add’l Info:
None.
Action:
Verify the command line is valid.
Text:
The account with the specified username has
expired.
Type:
Warn
Add’l Info:
None.
Action:
Verify account.
Text:
Error opening registry: HKEY_LOCAL_MACHINE\
\. Exiting.
Type:
Fatal
Add’l Info:
The installation may have failed or registry
become corrupted.
Action:
Reinstall CAD
Text:
Error reading registry entry:
HKEY_LOCAL_MACHINE\\. Exiting.
Type:
Fatal
Add’l Info:
The installation may have failed or registry
become corrupted.
Action:
Reinstall CAD
Text:
Unable to start Corba Thread. Exception = <%ls>
Exiting.
Type:
Fatal
Add’l Info:
Check system resource availability (CPU and
memory). Make sure the Record service
properties are correct.
QMUT3000
QMUT3004
RECORD1001
RECORD1002
RECORD1004
Action:
December 17, 2014
155
Cisco CAD Error Code Dictionary
Error
Description
RECORD1005
Text:
Unable to start LDAP Update Thread. Exiting.
Text:
Fatal
Type:
Check system resource availability (CPU and
memory). Make sure the Record service
properties are correct.
Add’l Info:
RECORD1006
Text:
Unable to start VPN Thread. Exiting.
Type:
Fatal
Add’l Info:
The initialization of the Windows NT service was
unsuccessful.
Action:
Check system resource availability (CPU and
memory).
Action:
RECORD1007
RECORD1008
RECORD1009
156
Text:
Unable to register with LRM server at this time,
will attempt to recover.
Type:
Fatal
Add’l Info:
The initialization of the Linux service was
unsuccessful.
Action:
Check system resource availability (CPU and
memory).
Text:
Unable to start Refresh Thread. Exiting.
Type:
Fatal
Add’l Info:
The initialization of the Windows NT service was
unsuccessful.
Action:
Check system resource availability (CPU and
memory).
Text:
Caught a CORBA exception changing CORBA
server to ready. Exiting.
Type:
Fatal
Add’l Info:
The initialization of the Windows NT service was
unsuccessful.
Action:
Check network settings.
December 17, 2014
Error Messages
Error
Description
RECORD1010
Text:
No audio path. Exiting.
Type:
Fatal
Add’l Info:
The audio directory not found and could not be
created
Action:
Check the security settings.
Text:
An exception occurred calling ORB_init(). Exiting.
Type:
Fatal
Add’l Info:
check network settings.
RECORD1013
Action:
RECORD1014
Text:
An exception occurred calling BOA_init(). Exiting.
Type:
Fatal
Add’l Info:
check network settings.
Action:
RECORD1015
Text:
Unable to create a Logout event. Exiting.
Type:
Fatal
Add’l Info:
check network settings.
Action:
RECORD1016
Text:
An exception occurred calling initializing the
CORBA playback interface. Exiting.
Type:
Fatal
Add’l Info:
Check network settings.
Action:
RECORD1017
Text:
An exception occurred calling initializing the
CORBA recording interface. Exiting.
Type:
Fatal
Add’l Info:
Check network settings.
Action:
December 17, 2014
157
Cisco CAD Error Code Dictionary
Error
Description
RECORD1018
Text:
MAX_RECORDING_DISK_USAGE is not set!
Recording disabled.
Type:
Fatal
Add’l Info:
Verify server is properly installed.
Action:
RECORD1019
Text:
Unable to create I/O signal handler.
Type:
Fatal
Add’l Info:
None.
Action:
RECORD2006
RECORD2007
RECORD2008
RECORD2009
158
Text:
The disk subsystem is overloaded. Recording
quality negatively impacted.
Type:
Error
Add’l Info:
An error occurred while synchronizing agents.
Action:
Check system resource availability (CPU,
memory and disk).
Text:
The free disk space limit has been reached.
Type:
Error
Add’l Info:
An error occurred while synchronizing agents.
Action:
Check system resource availability (disk).
Text:
The limit for maximum disk space that can be
used for recordings is reached.
Type:
Error
Add’l Info:
The maximum disk space that can be used by
recordings has be reached.
Action:
Check system resources.
Text:
Initializing the Winsock library failed.
Type:
Error
Add’l Info:
The maximum disk space that can be used by
recordings has be reached.
Action:
Check system resources.
December 17, 2014
Error Messages
Error
Description
RECORD2010
Text:
Creating the listening socket failed.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Unable to retrieve local IP address for host name
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
The VPN thread failed to bind to the local
address.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
VPN thread failed to listen to the local address.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
stream (%hs): socket creation failed with code:
(%hs)
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
stream (%hs): Socket BIND failed with code:
(%hs)
Type:
Error
Add’l Info:
None.
Action:
None.
RECORD2011
RECORD2012
RECORD2013
RECORD2014
RECORD2015
December 17, 2014
159
Cisco CAD Error Code Dictionary
Error
Description
RECORD2016
Text:
stream (%hs): Socket SELECT failed with code:
(%hs)
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
stream (%hs): recvfrom failed with code: (%hs)
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
stream (%hs): Writing an RTP packet failed.
Aborting recording of this stream.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
stream (%hs): (%lu) packets were dropped due
to the disk being slow.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Free disk space (%ld MB) is under the (%ld MB)
limit. All recordings will be stopped.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
VPN thread failed to listen to the local address.
Type:
Error
Add’l Info:
None.
Action:
None.
RECORD2017
RECORD2018
RECORD2019
RECORD2020
RECORD2021
160
December 17, 2014
Error Messages
Error
Description
RECORD2022
Text:
A side of the recording stopped playing due to a
read error.
Type:
Error
Add’l Info:
Playback stopped, most likely because the
cache was empty.
Action:
Verify that disk I/O is not overloaded.
Text:
Unable to start playback. Buffering is taking too
long.
Type:
Error
Add’l Info:
Playback stopped, most likely because the
cache was empty.
Action:
Verify that disk I/O is not overloaded.
Text:
temp file = <%hs> could not be renamed.
Type:
Warn
Add’l Info:
None.
Action:
None.
Text:
Unable to start Resiprocate thread. Caught an
exception, exception message= <%ls>
Type:
Fatal
Add’l Info:
The main reciprocate Thread could not be
started.
Action:
None.
Text:
Unable to retrieve presence Server information.
Error Code = <%ls>
Type:
Fatal
Add’l Info:
The presence Server information cannot be
retrieved by GetPresenceSvrConfig().
Action:
None.
Text:
Adding Resiprocate handlers failed. Error Code =
<%ls>
Type:
Fatal
Add’l Info:
Resiprocate Transport, Profile and Message
Handlers could not be set.
Action:
None.
RECORD2023
RECORD3000
SAW1000
SAW1001
SAW1002
December 17, 2014
161
Cisco CAD Error Code Dictionary
Error
Description
SAW1003
Text:
Adding Resiprocate message types failed. Error
Code = <%ls>
Type:
Fatal
Add’l Info:
Resiprocate Transport, Profile and Message
Handlers could not be set.
Action:
None.
Text:
Unable to start ChatMessage Process Thread.
Caught an exception, exception message =
<%ls>
Type:
Fatal
Add’l Info:
Unable to start Chat Message Process thread.
Action:
None.
Text:
Unable to start Presence Events Thread Caught
an exception, exception message = <%ls>
Type:
Fatal
Add’l Info:
Unable to start Presence Events Thread.
Action:
None.
Text:
Could not login user into any of the presence
Servers retrieved from
GetPresenceSvrConfig().Error Code = <%ls>
Type:
Fatal
Add’l Info:
Resiprocate Transport, Profile and Message
Handlers could not be set.
Action:
None.
Text:
Starting of Notification threads failed.Error Code
= <%ls>
Type:
Fatal
Add’l Info:
Resiprocate Transport, Profile and Message
Handlers could not be set.
Action:
None.
SAW1004
SAW1005
SAW1006
SAW1007
162
December 17, 2014
Error Messages
Error
Description
SAW1008
Text:
GetAgentBuddyList() failed. Error Code = <%ls>
Type:
Fatal
Add’l Info:
Resiprocate Transport, Profile and Message
Handlers could not be set.
Action:
None.
Text:
GetAgentBuddiesInfo() failed.Error Code = <%ls>
Type:
Fatal
Add’l Info:
Resiprocate Transport, Profile and Message
Handlers could not be set.
Action:
None.
Text:
Unable to start Notification thread. Caught an
exception, exception message = <%ls>
Type:
Fatal
Add’l Info:
Unable to start Notification thread.
Action:
None.
Text:
addResiprocateServerSettings failed. Error Code
= <%ls>
Type:
Fatal
Add’l Info:
Resiprocate Transport, Profile and Message
Handlers could not be set.
Action:
None.
Text:
An unexpected exception occurred.
Type:
Error
Add’l Info:
An unexpected exception occurred.
Action:
Check the log for other errors. Make sure that all
appropriate Cisco services are up and running.
Check the log files of other Cisco related
services for errors. Check the System Event
Viewer for system errors. Check system resource
availability (memory, CPU). Check for network
communication errors.
SAW1009
SAW1010
SAW1011
SAW2000
December 17, 2014
163
Cisco CAD Error Code Dictionary
Error
Description
SAW2001
Text:
Publishing of CAD Users presence state failed.
Type:
Error
Add’l Info:
Publishing of CAD Users presence state failed.
Action:
None.
Text:
Sending out individual Subscription messages
failed. Error Code = <%ls>
Type:
Error
Add’l Info:
Publishing of CAD Users presence state failed.
Action:
None.
Text:
Sending out individual Subscription messages
failed. Error Code = <%ls>
Type:
Error
Add’l Info:
Publishing of CAD Users presence state failed.
Action:
None.
Text:
Inserting a presence event into the external list
failed. Error Code = <%ls>
Text:
Error
Type:
Publishing of CAD Users presence state failed.
Add’l Info:
None.
Text:
Inserting a presence event into the internal list
failed. Error Code = <%ls>
Text:
Error
Type:
Publishing of CAD Users presence state failed.
Add’l Info:
None.
Text:
Inserting a chat event into the external list failed.
Error Code = <%ls>
Type:
Error
Add’l Info:
Publishing of CAD Users presence state failed.
Action:
None.
SAW2002
SAW2003
SAW2004
SAW2005
SAW2006
164
December 17, 2014
Error Messages
Error
Description
SAW3000
Text:
The notify message does not have tag name =
<%ls> .
Type:
Warn
Add’l Info:
None.
Action:
None.
Text:
The threads = <%ls> could not be started.
Exception = <%ls>
Type:
Warn
Add’l Info:
The thread could not be started.
Action:
None.
Text:
Getting contacts configured on CUPS failed with
error code = <%ls>
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
The Control handler could not be installed
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Failed to install
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Could not remove Error message
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Invalid Arguments,
Type:
Error
Add’l Info:
None.
Action:
Exit.
SAW3001
SAW3002
SL1005
SL1006
SL1007
SL1008
December 17, 2014
165
Cisco CAD Error Code Dictionary
Error
Description
SL1009
Text:
The Control handler could not be installed
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
The Control handler could not be installed
Text:
Error
Type:
None.
Add’l Info:
None.
Text:
Invalid Request.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error getting server type profile: type (%ls) msg
(%ls)
Type:
Error
Add’l Info:
Failed to retrieve specified server type profile
from LDAP.
Action:
Check if the server type in question is up and
running. Check if LDAP is running.
Text:
Error getting server profile: type (%ls) msg (%ls)
Type:
Error
Add’l Info:
Failed to retrieve specified server profile from
LDAP.
Action:
Check if the server type in question is up and
running. Check if LDAP is running.
Text:
Error getting attribute: type (%ls) attribute (%ls)
Type:
Error
Add’l Info:
Failed to retrieve specified attribute for specified
server profile from LDAP.
Action:
Check if the server type in question is up and
running. Check if LDAP is running.
SL1010
SL2001
SMC3000
SMC3001
SMC3002
166
December 17, 2014
Error Messages
Error
Description
SMC3003
Text:
Error getting server IPs: type (%ls) msg (%ls)
Type:
Error
Add’l Info:
Failed to retrieve IP addresses fir specified
server profile from LDAP.
Action:
Check if the server type in question is up and
running. Check if LDAP is running.
Text:
Error converting IOR wstring to string: type (%ls)
ior (%ls)
Type:
Error
Add’l Info:
Failed to convert IOR from wstring to string.
Action:
Check if the server type in question is up and
running fine.
Text:
Error retrieving IP from IOR: type (%ls) ior (%ls)
Type:
Error
Add’l Info:
Failed to retrieve ip address from ior.
Action:
Check if the server type in question is up and
running fine.
Text:
Error getting LDAP registry settings: msg (%ls)
Type:
Error
Add’l Info:
Failed to get LDAP registry settings
Action:
Check if LDAP is up and running fine.
Text:
Error retrieving list of servers: type (%ls) msg
(%ls)
Type:
Error
Add’l Info:
Failed to retrieve ip address from ior.
Action:
Check if the server type in question is up and
running fine.
Text:
SendMail Exception: msg (%ls)
Type:
Fatal
Add’l Info:
Exception occured when invoking Sendmail
methods.
Add’l Info:
Check if the Exchange Server is up and running;
Check system resources.
SMC3004
SMC3005
SMC3006
SMC3007
SMTP2000
December 17, 2014
167
Cisco CAD Error Code Dictionary
Error
Description
SNMPEA1000
Text:
Unable to start the client recovery thread.
Type:
Warn
Add’l Info:
The connection recovery thread could not be
started.
Action:
Restart the application if the connection is lost.
Text:
An unexpected exception occurred.
Type:
Error
Add’l Info:
None.
Action:
Complete the following steps.
SPLKAXL2000
• Check the log for other errors.
• Make sure that all appropriate Cisco services
are up and running.
• Check the log files of other Cisco related
services for errors.
• Check the System Event Viewer for system
errors.
• Check system resource availability (memory,
CPU).
• Check for network communication errors.
SPLKAXL2001
SPLKAXL2002
168
Text:
An error was returned by the CallManager SOAP
interface. SOAP-ENV:Fault (%ls) axl:error (%ls).
Type:
Error
Add’l Info:
An error was returned by CallManager.
Action:
See text in error message for more details.
Check the log for other errors.
Text:
An error occurred initializing the HTTP Interface.
HTTP Error: %ls.
Type:
Error
Add’l Info:
An error occurred initializing the HTTP Interface.
Action:
See text in error message for more details.
Check the log for other errors. Check system
resource availability (CPU and memory).
December 17, 2014
Error Messages
Error
Description
SPLKAXL2003
Text:
The port specified, %d, was invalid.
Type:
Error
Add’l Info:
The port used is invalid.
Action:
Check the log for other errors. Contact technical
support.
Text:
Failed to set the HTTP option, %ls, for host: %ls.
Error: %ls.
Type:
Error
Add’l Info:
An error occurred when trying to set the
specified HTTP option.
Action:
See text in error message for more details.
Check system resource availability (CPU and
memory).
Text:
Failed to connect to CallManager Host: %ls.
HTTP Error: %ls.
Type:
Error
Add’l Info:
An error occurred while trying to connect to the
specified CallManager AXL interface.
Action:
Complete the following steps.
SPLKAXL2004
SPLKAXL2005
• See text in error message for more details.
• Verify that the CallManager IP address or
host is correct.
• Check system resource availability (CPU and
memory).
December 17, 2014
169
Cisco CAD Error Code Dictionary
Error
Description
SPLKAXL2006
Text:
Failed to create an HTTP request to CallManager
Host: %ls. HTTP Error: %ls.
Type:
Error
Add’l Info:
An error occurred when trying to create an HTTP
request to the specified CallManager AXL
interface.
Action:
Complete the following steps.
• See text in error message for more details.
• Verify that the CallManager IP address or
host is correct.
• Check system resource availability (CPU and
memory).
SPLKAXL2007
Text:
Failed to set login credentials for CallManager
Host: %ls. HTTP Error: %ls.
Type:
Error
Add’l Info:
An error occurred when passing login credentials
to the specified CallManager AXL interface.
Action:
Complete the following steps.
• See text in error message for more details.
• Verify that the CallManager IP address or
host is correct.
• Check system resource availability (CPU and
memory).
SPLKAXL2008
Text:
Failed to send the HTTP request to CallManager
Host: %ls. HTTP Error: %ls.
Type:
Error
Add’l Info:
An error occurred when sending an HTTP
request to the specified CallManager AXL
interface.
Action:
Complete the following steps.
• See text in error message for more details.
• Verify that the CallManager IP address or
host is correct.
• Check system resource availability (CPU and
memory).
170
December 17, 2014
Error Messages
Error
Description
SPLKAXL2009
Text:
Failed to receive a response to an HTTP request
to CallManager Host: %ls. HTTP Error: %ls.
Type:
Error
Add’l Info:
An error occurred when receiving response to an
HTTP request to the specified CallManager AXL
interface.
Action:
Complete the following steps.
• See text in error message for more details.
• Verify that the CallManager IP address or
host is correct.
• Check system resource availability (CPU and
memory).
SPLKAXL2010
Text:
Failed to authenticate user.
Type:
Error
Add’l Info:
HTTP response code 401 received for the
second time from the web server. Authentication
failed.
Action:
Complete the following steps.
• Verify that the login and password specified
for the CallManager AXL Interface are
correct.
• Verify that the CallManager IP address or
host is correct.
• Check system resource availability (CPU and
memory).
December 17, 2014
171
Cisco CAD Error Code Dictionary
Error
Description
SPLKAXL2011
Text:
Bad response code received (%d) from an HTTP
request to CallManager Host(%ls). HTTP Error:
%ls.
Type:
Error
Add’l Info:
Bad HTTP response code received from the web
server.
Action:
Complete the following steps.
• See text in error message for more details.
• Verify that the CallManager IP address or
host is correct.
• Check system resource availability (CPU and
memory).
SPLKAXL2012
Text:
Failed to read amount of data available in the
response from an HTTP request to CallManager
Host(%ls). HTTP Error: %ls.
Type:
Error
Add’l Info:
An error occurred when reading amount of data
response from an HTTP request to the specified
CallManager AXL interface.
Action:
Complete the following steps.
• See text in error message for more details.
• Check system resource availability (CPU and
memory).
• Check for network connectivity issues.
172
December 17, 2014
Error Messages
Error
Description
SPLKAXL2013
Text:
Failed to read data in the response from an
HTTP request to CallManager Host(%ls). HTTP
Error: %ls.
Type:
Error
Add’l Info:
An error occurred when reading data response
from an HTTP request to the specified
CallManager AXL interface.
Action:
Complete the following steps.
• See text in error message for more details.
• Check system resource availability (CPU and
memory).
• Check network connectivity.
SPLKAXL2014
Text:
At least one required argument is missing.
Host(%ls) Port(%d) Query(%ls).
Type:
Error
Add’l Info:
A required argument is missing.
Action:
Complete the following steps.
• Check the log for other errors.
• Contact technical support.
SPLKAXL2015
Text:
Failed to connect to LDAP.
Type:
Error
Add’l Info:
SplkAXL was not able to connect to LDAP. It will
attempt to connect periodically until it succeeds.
Action:
Complete the following steps.
• Verify that LDAP Server is running.
• Check for network connectivity issues.
SPLKAXL2016
Text:
Failed to get %ls from LDAP. Error(%d:%ls).
Type:
Error
Add’l Info:
SplkAXL was not able to get the specified
information from LDAP.
Action:
Complete the following steps.
• Verify that LDAP Server is running.
• Check for network connectivity issues.
December 17, 2014
173
Cisco CAD Error Code Dictionary
Error
Description
SPLKAXL2017
Text:
SplkAXL has not been initialized.
Type:
Error
Add’l Info:
SplkAXL being used before being initialized.
Action:
Complete the following steps.
• Check the log for other errors.
• Contact technical support.
SPLKAXL2018
Text:
Failed to query CallManager(%ls) Port(%d)
Error(%d:%ls).
Type:
Error
Add’l Info:
An error occurred querying the specified
CallManager.
Action:
Complete the following steps.
• See text in error for more details.
• Check system resource availability (CPU and
memory).
• Check for network connectivity issues.
SPLKAXL2019
Text:
Failed to set (%ls) from LDAP. Error(%d:%ls).
Type:
Error
Add’l Info:
SplkAXL was unable to set the specified info in
LDAP.
Action:
Complete the following steps.
• Verify that LDAP Server is running.
• Check for network connectivity issues.
SPLKAXL2020
Text:
Unknown CallManager version: %ls.
Type:
Error
Add’l Info:
The CallManager version found is not supported.
Action:
Complete the following steps.
• Check the log for other errors.
• Contact technical support.
174
December 17, 2014
Error Messages
Error
Description
SPLKAXL2021
Text:
Caught a splk_std::SplkXmlException. Exception
message: %ls.
Type:
Error
Add’l Info:
Caught a splk_std::SplkXmlException.
Action:
Complete the following steps.
• Read the error message for a description.
• Check the log for other errors.
• Check system resource availability (memory,
CPU).
• Check for network communication errors.
SPLKAXL2022
Text:
Caught a xercesc::XMLException. Exception
message: %hs.
Type:
Error
Add’l Info:
Caught a xercesc::XMLException.
Action:
Complete the following steps.
• Read the error message for a description.
• Check the log for other errors.
• Check system resource availability (memory,
CPU).
• Check for network communication errors.
SPLKAXL2023
Text:
Caught a xercesc::DOMException. Exception
message: %hs.
Type:
Error
Add’l Info:
Caught a xercesc::DOMException.
Action:
Complete the following steps.
• Read the error message for a description.
• Check the log for other errors.
• Check system resource availability (memory,
CPU).
• Check for network communication errors.
December 17, 2014
175
Cisco CAD Error Code Dictionary
Error
Description
SPLKAXL2024
Text:
Failed to get the AXL authentication information
from CRS for switch type: %ls. Error %d (%hs).
Type:
Error
Add’l Info:
There was a problem getting the AXL username
and password from CRS.
Action:
Complete the following steps.
• Read the error message for a description.
• Check the log for other errors.
• Check for network communication errors.
SPLKAXL2025
Text:
Failed to get the JTapi user ID from CRS. Error
%d (%hs).
Type:
Error
Add’l Info:
There was a problem getting the JTapi user ID
from CRS.
Action:
Complete the following steps.
• Read the error message for a description.
• Check the log for other errors.
• Check for network communication errors.
SPLKAXL2026
Text:
There was a problem preparing CURL: %ls. Error:
%hs.
Type:
Error
Add’l Info:
There was a problem preparing the CURL
connection.
Action:
Complete the following steps.
• Read the error message for a description.
• Check the log for other errors.
• Check for network communication errors.
176
December 17, 2014
Error Messages
Error
Description
SPLKAXL2027
Text:
There was a problem performing the CURL
action. Error: %hs.
Type:
Error
Add’l Info:
There was a problem performing the CURL
action.
Action:
Complete the following steps.
• Read the error message for a description.
• Check the log for other errors.
• Check for network communication errors.
SPLKAXL2028
Text:
Failed to get the version from CallManager: %ls.
Type:
Error
Add’l Info:
There was a problem performing the CURL
action.
Action:
Complete the following steps.
• Read the error message for a description.
• Check the log for other errors.
• Verify that the CallManager hostname is
correct.
• Verify that the AXL username and password
used is correct.
• Verify that the AXL user has AXL API access.
SPLKAXL3000
Text:
Timeout occurred making HTTP call:%ls.
CallManager: %ls.
Type:
Warn
Add’l Info:
The specified HTTP call timed out. The program
will retry request when this error occurs.
Action:
Complete the following steps.
• See text in error for more details.
• Check system resource availability (CPU and
memory).
• Check for network connectivity issues.
December 17, 2014
177
Cisco CAD Error Code Dictionary
Error
Description
SPLKAXL3001
Text:
The version used (%ls) does not match
supported versions. Using version %ls.
Type:
Warn
Add’l Info:
The version used does not match supported
versions.
Action:
Complete the following steps.
• See text in error for more details.
• Check system resource availability (CPU and
memory).
• Check for network connectivity issues.
SPLKAXL3002
Text:
The query returned HTTP 401. Check the AXL
username (%ls) and password.
Type:
Warn
Add’l Info:
The query return a 401 status code that may
indicate a user authentication error.
Action:
Complete the following steps.
• See text in error for more details.
• Check the AXL username and password.
SPLKAXL3003
Text:
The query returned HTTP 403. Verify that this
user (%ls) has AXL API access.
Type:
Warn
Add’l Info:
The query return a 403 status code that may
indicate that the user does not have AXL API
access.
Action:
Complete the following steps.
• See text in error for more details.
• Check the AXL username and password.
178
December 17, 2014
Error Messages
Error
Description
SPLKAXL3004
Text:
The query return an unexpected status code:
%d.
Type:
Warn
Add’l Info:
The query return an unexpected status code.
Action:
Complete the following steps.
• See text in error for more details.
• Check the AXL username and password.
SPLKTSSP1000
SPLKTSSP1001
SPLKTSSP2038
STD1000
STD1001
December 17, 2014
Text:
SL1000 Could not create thread.
Type:
Fatal
Add’l Info:
Could not create thread.
Action:
Check system resource availability (memory,
CPU).
Text:
SS1001 Unexpected error.
Type:
Fatal
Add’l Info:
An unexpected exception occurred.
Action:
Check the log for other errors. Check the System
Event Viewer for system errors. Check system
resource availability (memory, CPU).
Text:
Network communication error.
Type:
Error
Add’l Info:
Network communication error.
Action:
Check network connectivity. Verify that the
Enterprise Service is running.
Text:
An exception occured.
Type:
Fatal
Add’l Info:
An exception occured.
Action:
None.
Text:
Failed to connect to LDAP.
Type:
Fatal
Add’l Info:
An exception occured.
Action:
None.
179
Cisco CAD Error Code Dictionary
Error
Description
STD2000
Text:
Client <%ls> failed to send heart beat to service
at <%ls>.
Type:
Error
Add’l Info:
The specified client failed to send a heart beat to
the service on the specified host. This error
could be due to one of several conditions: the
service is down, the server on which the service
is running is down, or a network problem exists
between the client and the server.
Action:
Complete the following steps.
• Check the status of the server. If it is down,
restart it.
• Check the status of the service. If it is down,
restart it.
• Verify the network connection between the
client and the server on which the service is
running. To verify the connection, run ping or
telnet from the client to the server.
STD2001
Text:
Client <%ls> failed to connect to any service.
Type:
Error
Add’l Info:
The specified client failed to connect to a
service. The client application will automatically
attempt to reconnect to the service. If the
connection attempt succeeds, no action is
needed.
Action:
If the connection attempt fails, check the status
of the service.
• If the service is not running and active,
restart it.
• If the service is running and active, verify the
network connection between the client and
the server on which the service is running.
• To verify the network connection, run ping or
telnet from the client to the server.
180
December 17, 2014
Error Messages
Error
Description
STD2002
Text:
The service controller threw an exception: %ls.
Type:
Error
Add’l Info:
The service controller threw an exception.
Action:
Check the exception message for an explanation
of the exception and appropriate actions for
resolving the issue.
Text:
Failed to install console control signal translator.
Reason:[%d:%ls].
Type:
Error
Add’l Info:
The application failed to install the console
control signal translator.
Action:
Check the error message for an explanation of
the error and appropriate actions for resolving
the issue.
Text:
Failed to remove console control signal
translator. Reason:[%d:%ls].
Type:
Error
Add’l Info:
The application failed to remove the console
control signal translator.
Action:
Check the error message for an explanation of
the error and appropriate actions for resolving
the issue.
Text:
%ls %ls: <%ls>.
Type:
Warn
Add’l Info:
Encountered specified Windows error when
performing specified registry operation.
Action:
No action is needed if the registry entry is
optional.
STD2003
STD2004
STD3000
Complete the following steps.
• Check if registry entry exists.
• Check if application user has permissions to
read/write/delete specified registry entry.
• Check Windows error description for details.
December 17, 2014
181
Cisco CAD Error Code Dictionary
Error
Description
STD3001
Text:
Registry key <%ls> is not of REG_SZ or
REG_DWORD type.
Type:
Warn
Add’l Info:
Specified registry key is not of REG_SZ or
REG_DWORD type.
Action:
If registry key is not of REG_SZ or REG_DWORD
type, change it to REG_SZ or REG_DWORD.
Text:
Registry key <%ls> is not of REG_DWORD type.
Type:
Warn
Add’l Info:
Specified registry key is not of REG_DWORD
type.
Action:
If registry key is not of REG_DWORD type,
change it to REG_DWORD.
Text:
Internal error: Caught unknown exception in
<%ls>.
Type:
Warn
Add’l Info:
Caught unknown exception in specified function.
Action:
Contact technical support.
Text:
Preference change notification queue has
reached its maximum size <%d>.
Type:
Warn
Add’l Info:
Preference change notification queue has
reached its maximum size. The listener(s) for
preference changes is slow or no longer
responding to notification; or the amount of
preference changes is coming faster than
listeners can handle them.
Action:
Complete the following steps.
STD3002
STD3003
STD3004
• Check for CPU and memory usage to ensure
machine is not running out of resources.
• Check if some other process is taking up all
the CPU, potentially starving this process.
• Check log for other issues that may affect
this.
• Restart process to see if the error reoccurs.
182
December 17, 2014
Error Messages
Error
Description
STD3005
Text:
Preference change blocker queue has reached
its maximum size <%d>.
Type:
Warn
Add’l Info:
Preference change blocker queue has reached
its maximum size. The blocker user is slow or no
longer attempting to get events from the queue;
or the amount of preference changes is coming
faster than blocker user can handle them.
Action:
Complete the following steps.
• Check for CPU and memory usage to ensure
machine is not running out of resources.
• Check if some other process is taking up all
the CPU, potentially starving this process.
• Check log for other issues that may affect
this.
• Restart process to see if the error reoccurs.
STD3006
STD3007
Text:
Unable to initialize Xerces XML system : %ls.
Type:
Warn
Add’l Info:
Application could not initialize Xerces XML
system.
Action:
Check if xerces-c_2_7.dll (on Windows) is
accessible by the application. Check Xerces
error description for further information.
Text:
Unable to shutdown Xerces XML system : %ls.
Type:
Warn
Add’l Info:
Application could not shutdown Xerces XML
system properly.
Xerces XML system is only shut down when
SplkStd library is unloaded from the application.
If this message occurs during application
shutdown, it should not impact functionality. If it
occurs during normal application running, it
indicates SplkStd library may have been
unloaded prematurely.
Action:
December 17, 2014
Check Xerces error description for further
information.
183
Cisco CAD Error Code Dictionary
Error
Description
STD3008
Text:
The thread [%ls:%ls] terminated unexpectedly.
Reason: %ls.
Type:
Warn
Add’l Info:
An exception was caught, causing an executing
thread to terminate unexpectedly.
Action:
Contact technical support.
Text:
Thread <0x%llx:%ls> in thread pool <%ls>
running task <%ls> is considered hung and
removed. The running task %ls aborted.
Type:
Warn
Add’l Info:
The specified thread in the specified thread pool
took too long processing specified task and is
considered hung. Therefore the thread was
removed from the thread pool.
Action:
Complete the following steps.
STD3009
• Check for CPU and memory usage to ensure
machine is not running out of resources.
• Check if some other process is taking up all
the CPU, potentially starving this process.
• Check log for other issues that may affect
this.
• Restart process to see if the error reoccurs.
184
December 17, 2014
Error Messages
Error
Description
STD3010
Text:
Thread factory <%ls> could not create thread for
thread pool <%ls>. Potentially discarding task
<%ls>.
Type:
Warn
Add’l Info:
The specified thread factory could not create a
new thread for specified thread pool potentially
causing specified task to be discarded.
Action:
Complete the following steps.
• Check for CPU and memory usage to ensure
machine is not running out of resources.
• Check if some other process is taking up all
the CPU, potentially starving this process.
• Check log for other issues that may affect
this.
• Restart process to see if the error reoccurs.
STD3011
STD3013
December 17, 2014
Text:
Failed to start the log file compression thread.
Log files may not be compressed automatically.
Exception <%ls>
Type:
Warn
Add’l Info:
Failed to start the log file compression thread.
Log files may not be compressed automatically.
Action:
Check for CPU and memory usage to ensure
machine is not running out of resources. Check
if some other process is taking up all the CPU,
potentially starving this process. Check log for
other issues may affect this. Restart process to
see if it reoccurs.
Text:
Failed to stop <%ls> thread: <%ls>.
Type:
Warn
Add’l Info:
None
Action:
Check if the machine is low on memory. Stop
unnecessary processes on the machine. Restart
the application. If the error persists, contact
technical support.
185
Cisco CAD Error Code Dictionary
Error
Description
STORAGE1000
Text:
Could not create thread (%ls).
Type:
Fatal
Add’l Info:
Could not create thread.
Action:
Verify system resource availability (memory,
CPU).
Text:
Unexpected error. WaitForSingleObject failed.
Type:
Fatal
Add’l Info:
Unexpected error. WaitForSingleObject failed.
Action:
Verify system resource availability (memory,
CPU).
Text:
Failed to create CompletionIOPort
Type:
Fatal
Add’l Info:
Failed to create IO Completion Port
Action:
Verify system resource availability (memory,
CPU).
Text:
Unexpected exception during network
communication initialization (omniORB).
Type:
Fatal
Add’l Info:
Unexpected error. Failed to initialize CORBA.
Action:
Verify system resource availability (memory,
CPU).
Text:
Unrecoverable Error occured. Exiting.
Type:
Fatal
Add’l Info:
Unrecoverable error
Action:
Verify system resource availability (memory,
CPU).
Text:
Unexpected error creating LDAP connection.
Type:
Fatal
Add’l Info:
Unexpected error. Could not create connection
to LDAP.
Action:
Verify system resource availability (memory,
CPU). Verify if LDAP is running.
STORAGE1001
STORAGE1002
STORAGE1004
STORAGE1005
STORAGE1006
186
December 17, 2014
Error Messages
Error
Description
STORAGE2002
Text:
Lost connection to the CTI Server. Recover
connection.
Type:
Error
Add’l Info:
Lost connection to the CTI Server. Recover
connection.
Action:
Check the log for other errors. Make sure that all
appropriate Cisco services are up and running.
Check the log files of other Cisco related
services for errors. Check the System Event
Viewer for system errors. Check system resource
availability (memory, CPU). Check for network
communication errors.
Text:
SS2016 Failed to perform LDAP operation for
Device LDAP.
Type:
Error
Add’l Info:
Failed to perform specified LDAP operation.
Action:
Verify if LDAP is running. See error specified in
message.
Text:
Unable to open specified archive file.
Type:
Error
Add’l Info:
Unable to open specified archive file
Action:
Verify system resource availability (memory,
CPU). Check permissions on file if it already
exists. Check if specified path is valid
Text:
Failed to send Config Request Event to the CTI
server.
Type:
Error
Add’l Info:
Failed to send Config Request to CTI Server
Action:
Check system resource availability (memory,
CPU). Check if CTI Server is running Check
network connectivity Check log file for any other
ACMI related error messages prior to this
message
STORAGE2016
STORAGE2017
STORAGE2018
December 17, 2014
187
Cisco CAD Error Code Dictionary
Error
Description
STORAGE2019
Text:
Failed to send Config Key Request to the CTI
server.
Type:
Error
Add’l Info:
Failed to send Config Key Request to CTI Server
Action:
Check system resource availability (memory,
CPU). Check if CTI Server is running Check
network connectivity Check log file for any other
ACMI related error messages prior to this
message
Text:
An unexpected exception occurred.
Type:
Error
Add’l Info:
An unexpected exception occurred.
Action:
Check the log for other errors. Check the System
Event Viewer for system errors. Check system
resource availability (memory, CPU).
Text:
An unexpected exception occurred.
Type:
Error
Add’l Info:
An unexpected exception occurred.
Action:
Check the log for other errors. Check the System
Event Viewer for system errors. Check system
resource availability (memory, CPU).
Text:
Error getting the List of Supervisor Workflows
from LDAP for Supervisor. (Error %d:%ls).
Type:
Error
Add’l Info:
Error in retrieving specified value from LDAP.
Action:
Check if LDAP is running Check network
connectivity
Text:
The CTI Server returned a Failure Confirmation
Error Status for InvokeID.
Type:
Error
Add’l Info:
Received Failure Confirmation from CTI Server
Action:
Check log file for any other ACMI related error
messages prior to this message The status in
this message should provide more info on the
error.
STORAGE2020
STORAGE2021
STORAGE2022
STORAGE2028
188
December 17, 2014
Error Messages
Error
Description
STORAGE2030
Text:
Error calling PostQueuedCompletionStatus for
SkillStatsThread.
Type:
Error
Add’l Info:
IO Completion port error.
Action:
Check the log for other errors. Check the System
Event Viewer for system errors. Check system
resource availability (memory, CPU).
Text:
Failed to query skill group invokeid.
Type:
Error
Add’l Info:
Failed to query skill group from CTI Server
Action:
Check log file for any other ACMI related error
messages prior to this message The status in
this message should provide more info on the
error.
Text:
Failed to perform LDAP operation LDAP Error.
Type:
Error
Add’l Info:
Failed to perform LDAP operation.
Action:
Check if LDAP is running Check the log for other
errors. Check the System Event Viewer for
system errors. Check system resource
availability (memory, CPU).
Text:
Error in retrieving data type list from LDAP.
Type:
Error
Add’l Info:
Failed to perform LDAP operation.
Action:
Check if LDAP is running Check the log for other
errors. Check the System Event Viewer for
system errors. Check system resource
availability (memory, CPU).
Text:
Failed to query agent state from CTI server for
agent extension.
Type:
Error
Add’l Info:
Failed to query agent state from CTI Server
Action:
Check log file for any other ACMI related error
messages prior to this message The status in
this message should provide more info on the
error.
STORAGE2034
STORAGE2035
STORAGE2050
STORAGE2052
December 17, 2014
189
Cisco CAD Error Code Dictionary
Error
Description
STORAGE2053
Text:
Failed to get a snapshot from CTI server for
extension.
Type:
Error
Add’l Info:
Failed to get snapshot from CTI Server for
specified extension
Action:
Check log file for any other ACMI related error
messages prior to this message The status in
this message should provide more info on the
error.
Text:
Failed to get a snapshot from CTI server for Call
Extension.
Type:
Error
Add’l Info:
Failed to get snapshot from CTI Server for
specified call & extension
Action:
Check log file for any other ACMI related error
messages prior to this message The status in
this message should provide more info on the
error.
Text:
Failed to query skill statistics from CTI server for
Skill.
Type:
Error
Add’l Info:
Failed to query skill stats from CTI Server
Action:
Check log file for any other ACMI related error
messages prior to this message The status in
this message should provide more info on the
error.
Text:
Failed to set ECC Variable.
Type:
Error
Add’l Info:
Failed to set ECC variable
Action:
Check log file for any other ACMI related error
messages prior to this message The status in
this message should provide more info on the
error.
STORAGE2054
STORAGE2055
STORAGE2056
190
December 17, 2014
Error Messages
Error
Description
STORAGE2057
Text:
Failed to set call data variable.
Type:
Error
Add’l Info:
Failed to set Call variable
Action:
Check log file for any other ACMI related error
messages prior to this message The status in
this message should provide more info on the
error.
Text:
Could not detach thread.
Type:
Warn
Add’l Info:
Could not detach thread.
Action:
Check system resource availability (memory,
CPU).
Text:
Received partial status, treating as success.
Type:
Warn
Add’l Info:
Received partial configuration from CTI Server
Action:
Check status of CTI Server; Check error logs on
CTI Server.
Text:
Unable to find a host for the CORBA server.
Type:
Warn
Add’l Info:
Failed to get IOR HOSTNAME from registry.
Server will use system default
Action:
Verify that installation is complete.
Text:
Failed request to CTI Server, Error (%ls).
Type:
Warn
Add’l Info:
Failed specified request to CTI Server
Action:
Check system resource availability (memory,
CPU). Check if CTI Server is running Check
network connectivity Check log file for any other
ACMI related error messages prior to this
message.
STORAGE3000
STORAGE3001
STORAGE3002
STORAGE3003
December 17, 2014
191
Cisco CAD Error Code Dictionary
Error
Description
SWFA1000
Text:
Unknown Exception.
Type:
Fatal
Add’l Info:
None.
Action:
Check system resource availability (CPU and
memory).
Text:
Exception. Description= <%s>
Type:
Fatal
Add’l Info:
None.
Action:
Check description.
Text:
Unknown Exception in EmailAction OnOk…
Type:
Fatal
Add’l Info:
The exception may be due to a field that is
empty or the use of special characters.
Action:
Delete and recreate the Supervisor Workflow.
Text:
Unknown Exception in EmailAction OnInit…
Type:
Fatal
Add’l Info:
When the fields are repopulated at startup, the
data in LDAP may have been corrupted.
Action:
Delete the Mail Server, To, and BCC fields and
enter them again.
Text:
Unknown Exception in EmailAction
OnBnClickedEmailTest…
Type:
Fatal
Add’l Info:
A field might be empty or contain special
characters.
Action:
Enter data in the Mail Server, To, and BCC fields
again, avoiding special characters and spaces.
Text:
Unknown Exception in EmailAction TrimSpaces…
Type:
Fatal
Add’l Info:
Some fields might contain hidden spaces
Action:
Enter data in the Mail Server, To, and BCC fields
again, avoiding spaces.
SWFA1001
SWFA1002
SWFA1003
SWFA1004
SWFA1005
192
December 17, 2014
Error Messages
Error
Description
SWFA1006
Text:
Unknown Exception in EmailAction TrimSpaces
Type:
Fatal
Add’l Info:
Some fields might contain hidden spaces.
Action:
Enter data in the Mail Server, To, and BCC fields
again, avoiding spaces.
Text:
Unknown Exception in EmailAction
ValidateFields…
Type:
Fatal
Add’l Info:
Some fields might contain hidden spaces or
spaces between strings.
Action:
Delete the spaces between the strings in the
Mail Server, To, and BCC fields.
Text:
Unknown Exception in EmailAction
SendSWFMail…
Type:
Fatal
Add’l Info:
Some fields might contain hidden spaces or
spaces between strings, or the strings might be
corrupt.
Action:
Enter data in the Mail Server, To, and BCC fields
again.
Text:
Unknown Exception in EmailAction
IsValidEmailAddr…
Type:
Fatal
Add’l Info:
The Email Alert Action Setup dialog box
encountered an exception while verifying the
email address.
Action:
Enter valid email addresses in the To and BCC
fields.
Text:
LDAP Initialization failed.
Type:
Error
Add’l Info:
None.
Action:
Check that the LDAP service is running. Check
the Site Setup registry values.
SWFA1007
SWFA1008
SWFA1009
SWFA2000
December 17, 2014
193
Cisco CAD Error Code Dictionary
Error
Description
SWFA2001
Text:
Ldap connection failed. Description= <%s>
Type:
Error
Add’l Info:
None.
Action:
Check that the LDAP service is running. Check
the Site Setup registry values.
Text:
LdapClient API <%s> failed. Description= <%s>.
Type:
Error
Add’l Info:
None.
Action:
Check that the LDAP service is running. Check
the Site Setup registry values.
Text:
SPLK XML Parser failed to parse SWF <%s>.
Type:
Error
Add’l Info:
The parser failed to read the data from LDAP.
LDAP data may be corrupt.
Action:
Delete and recreate the Supervisor Workflow.
Text:
Unknown Exception...
Type:
Error
Add’l Info:
Internal exception.
Action:
Check system resource availability (CPU and
memory).
Text:
Exception. Description= <%s>.
Type:
Error
Add’l Info:
Internal exception.
Action:
Check description.
Text:
Enterprise Server Client API <%s> failed.
Description= <%s>.
Type:
Error
Add’l Info:
Internal exception.
Action:
Check that the Enterprise service is running.
SWFA2002
SWFA2003
SWFA2004
SWFA2005
SWFA2006
194
December 17, 2014
Error Messages
Error
Description
SWFA2007
Text:
Enterprise Server is not active.
Type:
Error
Add’l Info:
The Enterprise service is down.
Action:
Check that the Enterprise service is running.
Text:
SWF <%s> might be corrupted.
Type:
Error
Add’l Info:
Internal error.
Action:
Delete and recreate the Supervisor Workflow.
Text:
SPLK XML Parser failed encode SWF <%s> to
XML.
Type:
Error
Add’l Info:
Internal error.
Action:
Delete and recreate the Supervisor Workflow.
Text:
Error in spAutoRecoverConnection = <%hs>
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
spConnect failed with error = <%hs>
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Another instance of SWFAdmin is already
running.
Type:
Warn
Add’l Info:
Another instance of Supervisor Workflow
Administration is running.
Action:
Shut down one instance of Supervisor Workflow
Administration.
SWFA2008
SWFA2009
SWFA2010
SWFA2011
SWFA3000
December 17, 2014
195
Cisco CAD Error Code Dictionary
Error
Description
SYNC1000
Text:
%ls could not be installed as a Windows NT
service. The Windows NT service error code is
%d.
Type:
Fatal
Add’l Info:
Could not install a Windows NT service.
Action:
Check the error code provided in the message.
Make sure the Sync service is not already
running in the system.
Text:
The %ls Windows NT service could not be
uninstalled. The Windows NT service error code
is %d.
Type:
Fatal
Add’l Info:
Could not uninstalled a Windows NT service.
Action:
Check the error code provided in the message.
Make sure the Sync service is installed on the
system.
Text:
The argument passed to the program is invalid
and the program will exit.
Type:
Fatal
Add’l Info:
The argument passed to the program is invalid
and the program will exit.
Action:
Check the argument passed to the Sync service
in the command line.
Text:
The Windows NT service is not able to register
itself with the Windows NT service manager.
Type:
Fatal
Add’l Info:
The Windows NT service is not able to register
itself with the Windows NT service manager.
Action:
Check system resource availability (CPU and
memory). Make sure the Sync service properties
are correct. Check the System Event Viewer for
errors.
SYNC1001
SYNC1002
SYNC1003
196
December 17, 2014
Error Messages
Error
Description
SYNC1004
Text:
The initialization of the Windows NT service was
unsuccessful.
Type:
Fatal
Add’l Info:
The initialization of the Windows NT service was
unsuccessful.
Action:
Check the System Event Viewer for error
messages related to the Sync service. Check for
other error messages.
Text:
An unexpected exception occurred.
Type:
Error
Add’l Info:
An unexpected exception occurred.
Action:
Check the log for other errors related to ODBC,
LDAP, or network issues. Make sure that all
appropriate Cisco services are up and running.
Check the log files of other Cisco related
services for errors. Check the System Event
Viewer for system errors. Check system resource
availability (memory, CPU). Check for network
communication errors.
Text:
An error occurred while synchronizing agents.
Type:
Error
Add’l Info:
An error occurred while synchronizing agents.
Action:
Search the log for errors related to LDAP. Make
sure that the LDAP Monitor service is up and
running.
Text:
An error occurred while synchronizing teams.
Type:
Error
Add’l Info:
An error occurred while synchronizing teams.
Action:
Search the log for errors related to LDAP. Make
sure that the LDAP Monitor service is up and
running.
SYNC2000
SYNC2001
SYNC2002
December 17, 2014
197
Cisco CAD Error Code Dictionary
Error
Description
SYNC2003
Text:
An error occurred while synchronizing queues.
Type:
Error
Add’l Info:
An error occurred while synchronizing queues.
Action:
Search the log for errors related to LDAP. Make
sure that the LDAP Monitor service is up and
running.
Text:
An invalid request was received by the Windows
NT service from the Windows NT service
manager.
Type:
Error
Add’l Info:
An invalid request was received by the Windows
NT service from the Windows NT service
manager.
Action:
Check the System Event Viewer for errors.
Text:
Could not get CSQ description, for CSQ id<%ls>,
err<%d>, desc<%ls>.
Type:
Error
Add’l Info:
Could not get CSQ description.
Action:
Read the included error description.
Text:
Failed to allocate memory for DirAccessSynSvr_i.
Type:
Error
Add’l Info:
Failed to allocate memory for DirAccessSynSvr_i.
Action:
Check system resource availability (memory).
Search for other error messages.
Text:
Could not get resource list from the database.
Type:
Error
Add’l Info:
Could not get resource list from the database.
Action:
Search the log for database related errors.
Text:
Could not get resource description from the
database.
Type:
Error
Add’l Info:
Could not get resource description from the
database.
Action:
Search the log for database related errors.
SYNC2004
SYNC2005
SYNC2006
SYNC2007
SYNC2008
198
December 17, 2014
Error Messages
Error
Description
SYNC2009
Text:
Could not get CSQ list from the database.
Type:
Error
Add’l Info:
Could not get CSQ list from the database.
Action:
Search the log for database related errors.
Text:
Could not get CSQ description from the
database.
Type:
Error
Add’l Info:
Could not get CSQ description from the
database.
Action:
Search the log for database related errors.
Text:
Could not get MAC list from the database.
Type:
Error
Add’l Info:
Could not get MAC list from the database.
Action:
Search the log for database related errors.
Text:
Failed to allocate memory for SDeviceInfo.
Type:
Error
Add’l Info:
Failed to allocate memory for SDeviceInfo.
Action:
Check system resource availability (memory).
Search for other error messages.
Text:
Failed to get periodic synchronization object.
Type:
Error
Add’l Info:
Failed to get periodic synchronization object.
Action:
Search for other error messages.
Text:
Caught sync_server_exception: %ls.
Type:
Error
Add’l Info:
Caught sync_server_exception.
Action:
Read exception description.
Text:
Caught std::exception: %hs.
Type:
Error
Add’l Info:
Caught exception.
Action:
Read exception description.
SYNC2010
SYNC2011
SYNC2012
SYNC2013
SYNC2015
SYNC2016
December 17, 2014
199
Cisco CAD Error Code Dictionary
Error
Description
SYNC2017
Text:
Failed to initialize LCC:<%ls>, fcn<%ls>,
problem<%ls>, errcode<%d>.
Type:
Error
Add’l Info:
Failed to initialize the LCC object.
Action:
Read error description. Make sure the LDAP
Monitor service is up and running.
Text:
Failed to synchronize LCC:<%ls>, fcn<%ls>,
problem<%ls>, errcode<%d>.
Type:
Error
Add’l Info:
Failed to synchronize the LCC object.
Action:
Read error description.
Text:
Could not initialize ORB runtime (INITIALIZE).
Type:
Error
Add’l Info:
Could not initialize ORB runtime (INITIALIZE).
Action:
Check the log for network errors. Make sure that
all appropriate Cisco services are up and
running. Check system resource availability
(memory, CPU).
Text:
A CORBA error with minor error of %d and
completed flag of %d was caught. exception
name: %hs.
Type:
Error
Add’l Info:
A CORBA exception was caught.
Action:
Read error description. Check for network
communication errors. Make sure that all
appropriate Cisco services are up and running.
Text:
Caught omniORB::fatalException, desc:<%hs>.
Type:
Error
Add’l Info:
Caught omniORB::fatalException.
Action:
Read error description. Check for network
communication errors. Make sure that all
appropriate Cisco services are up and running.
SYNC2018
SYNC2019
SYNC2020
SYNC2021
200
December 17, 2014
Error Messages
Error
Description
SYNC2022
Text:
CORBA server instance is null.
Type:
Error
Add’l Info:
CORBA server instance is null.
Action:
Search for other error messages. Check for
network communication errors. Make sure that
all appropriate Cisco services are up and
running.
Text:
A CORBA error with minor error of %d(%hs) and
completed flag of %d was caught.
Type:
Error
Add’l Info:
A CORBA error was caught.
Action:
Check for network communication errors. Make
sure that all appropriate Cisco services are up
and running.
Text:
Could not connect to database, first try.
Type:
Error
Add’l Info:
Could not connect to database, first try.
Action:
Search for database related error messages.
Check the Logger Database configuration
section of CAD Configuration Setup for proper
values.
Text:
Could not connect to database, second try.
Type:
Error
Add’l Info:
Could not connect to database, second try.
Action:
Search for database related error messages.
Text:
Failed to create synchronization thread.
Type:
Error
Add’l Info:
Failed to create synchronization thread.
Action:
Search for other error messages. Check system
resource availability (memory, CPU).
SYNC2023
SYNC2024
SYNC2025
SYNC2026
December 17, 2014
201
Cisco CAD Error Code Dictionary
Error
Description
SYNC2027
Text:
An unexpected exception occurred when
synchronizing LDAP.
Type:
Error
Add’l Info:
An unexpected exception occurred when
synchronizing LDAP.
Action:
Make sure LDAP Monitor service is up and
running. Search the log for more errors. Make
sure that all appropriate Cisco services are up
and running.
Text:
An unexpected exception occurred when getting
resource list from the SQL MGR.
Type:
Error
Add’l Info:
An unexpected exception occurred when getting
resource list from the SQL MGR.
Action:
Search the log for ODBC related errors.
Text:
An unexpected exception occurred when
initializing the Sync service.
Type:
Error
Add’l Info:
An unexpected exception occurred when
initializing the Sync service.
Action:
Check the System Event Viewer for errors.
Text:
The Windows NT service was not removed
successfully.
Type:
Error
Add’l Info:
The Windows NT service was not removed
successfully.
Action:
Check the System Event Viewer for errors.
Text:
An error occurred during synchronization of
reason codes.
Type:
Error
Add’l Info:
An error occurred during synchronization of
reason codes.
Action:
Search the log for errors related to LDAP. Make
sure that the LDAP Monitor service is up and
running.
SYNC2028
SYNC2029
SYNC2030
SYNC2031
202
December 17, 2014
Error Messages
Error
Description
SYNC2032
Text:
Failed to allocate memory for SSQL object.
Type:
Error
Add’l Info:
Failed to allocate memory for SSQL object.
Action:
Check system resource availability (memory).
Search for other error messages.
Text:
Agent (%ls) not found in LDAP map.
Type:
Error
Add’l Info:
Agent not found in LDAP map.
Action:
Search for other error messages.
Text:
Could not delete agent from LDAP: %ls..
Type:
Warn
Add’l Info:
Could not delete agent from LDAP.
Action:
Read the included error description. Make sure
that the LDAP Monitor service is up and running.
Text:
Could not add agent to LDAP: %ls.
Type:
Warn
Add’l Info:
Could not add agent to LDAP.
Action:
Read the included error description. Make sure
that the LDAP Monitor service is up and running.
Text:
Could not add supervisor to LDAP: %ls.
Type:
Warn
Add’l Info:
Could not add supervisor to LDAP.
Action:
Read the included error description. Make sure
that the LDAP Monitor service is up and running.
Text:
Could not update agent in LDAP: %ls.
Type:
Warn
Add’l Info:
Could not update agent in LDAP.
Action:
Read the included error description. Make sure
that the LDAP Monitor service is up and running.
SYNC2033
SYNC3000
SYNC3001
SYNC3002
SYNC3003
December 17, 2014
203
Cisco CAD Error Code Dictionary
Error
Description
SYNC3004
Text:
Could not delete supervisor from LDAP: %ls.
Type:
Warn
Add’l Info:
Could not delete supervisor from LDAP.
Action:
Read the included error description. Make sure
that the LDAP Monitor service is up and running.
Text:
Could not update team in LDAP: %ls.
Type:
Warn
Add’l Info:
Could not update team in LDAP.
Action:
Read the included error description. Make sure
that the LDAP Monitor service is up and running.
Text:
Could not add team to LDAP: %ls.
Type:
Warn
Add’l Info:
Could not add team to LDAP.
Action:
Read the included error description. Make sure
that the LDAP Monitor service is up and running.
Text:
Could not delete team from LDAP: %ls.
Type:
Warn
Add’l Info:
Could not delete team from LDAP.
Action:
Read the included error description. Make sure
that the LDAP Monitor service is up and running.
Text:
Could not delete skill from LDAP: %ls.
Type:
Warn
Add’l Info:
Could not delete skill from LDAP.
Action:
Read the included error description. Make sure
that the LDAP Monitor service is up and running.
Text:
Could not add skill to LDAP: %ls.
Type:
Warn
Add’l Info:
Could not add skill to LDAP.
Action:
Read the included error description. Make sure
that the LDAP Monitor service is up and running.
SYNC3005
SYNC3006
SYNC3007
SYNC3008
SYNC3009
204
December 17, 2014
Error Messages
Error
Description
SYNC3010
Text:
Could not update skill in LDAP: %ls.
Type:
Warn
Add’l Info:
Could not update skill in LDAP.
Action:
Read the included error description. Make sure
that the LDAP Monitor service is up and running.
Text:
Could not get resource list from SQL MGR, err
<%d>, desc<%ls>.
Type:
Warn
Add’l Info:
Could not get resource list from SQL MGR.
Action:
Read the included error description. Check the
communication with the ICM SQL Logger
Database.
Text:
Could not allocate resource list.
Type:
Warn
Add’l Info:
Could not allocate resource list.
Action:
Check system resource availability (memory).
Check for other error messages.
Text:
Could not get resource description from the
database, resource id <%ls>, err <%d>,
desc<%ls>.
Type:
Warn
Add’l Info:
Could not get resource description from the
database.
Action:
Read the included error description. Check the
communication with the ICM SQL Logger
Database.
Text:
Could not get CSQ list from the database.
Type:
Warn
Add’l Info:
Could not get CSQ list from the database.
Action:
Read the included error description. Check the
communication with the ICM SQL Logger
Database.
SYNC3011
SYNC3012
SYNC3013
SYNC3014
December 17, 2014
205
Cisco CAD Error Code Dictionary
Error
Description
SYNC3015
Text:
Failed to reset periodic synchronizer.
Type:
Warn
Add’l Info:
Failed to reset periodic synchronizer.
Action:
Search for other errors. Check system resource
availability (memory, CPU).
Text:
Failed to reset synchronizer.
Type:
Warn
Add’l Info:
Failed to reset synchronizer.
Action:
Search the log for LDAP related errors.
Text:
Failed to reset the object synchronizer.
Type:
Warn
Add’l Info:
Failed to reset the object synchronizer.
Action:
Search the log for LDAP related errors.
Text:
The peripheral not expected, returned peripheral
<%ls> already exists.
Type:
Warn
Add’l Info:
The peripheral not expected.
Action:
Search for other error messages.
Text:
ResetLog failed error<%ls>.
Type:
Warn
Add’l Info:
ResetLog failed.
Action:
Read the included error description.
Text:
An unexpected exception occurred.
Type:
Warn
Add’l Info:
None.
Action:
Check the log for errors related to ODBC, LDAP,
or network issues. Make sure that all
appropriate Cisco services are up and running.
Check the log files of other Cisco-related
services for errors. Check the System Event
Viewer for system errors. Check system resource
availability (memory, CPU). Check the
communication with the ICM SQL Logger
Database
SYNC3016
SYNC3017
SYNC3018
SYNC3019
SYNC3020
206
December 17, 2014
Error Messages
Error
Description
SYNC3021
Text:
The program could not get the driver list from
ODBC.
Type:
Warn
Add’l Info:
None.
Action:
Check the System Event Viewer for system
errors. Check system resource availability
(memory, CPU). Check the communication with
the ICM SQL Logger Database
Text:
The program could not get the system data
sources from ODBC.
Type:
Warn
Add’l Info:
The program could not get the system data
sources from ODBC.
Action:
Check the System Event Viewer for system
errors. Check system resource availability
(memory, CPU). Check the communication with
the ICM SQL Logger Database.
Text:
The ODBC operation failed.
Type:
Warn
Add’l Info:
The ODBC operation failed.
Action:
Check for other ODBC error messages. Check
the System Event Viewer for system errors.
Check system resource availability (memory,
CPU). Check the communication with the ICM
SQL Logger Database.
Text:
The program could not get the record values
when fetching database columns.
Type:
Warn
Add’l Info:
The program could not get the record values
when fetching database columns.
Action:
Check for other ODBC error messages. Check
the System Event Viewer for system errors.
SYNC3022
SYNC3023
SYNC3024
December 17, 2014
207
Cisco CAD Error Code Dictionary
Error
Description
SYNC3025
Text:
The program could not get the next record from
the database.
Type:
Warn
Add’l Info:
The program could not get the next record from
the database.
Action:
Check for other ODBC error messages. Check
the System Event Viewer for system errors.
Check system resource availability (memory,
CPU).
Text:
The program could not get the table name from
the database.
Type:
Warn
Add’l Info:
The program could not get the table name from
the database.
Action:
Check for other ODBC error messages. Check
the System Event Viewer for system errors.
Check system resource availability (memory,
CPU).
Text:
The program could not get the next table from
the database.
Type:
Warn
Add’l Info:
The program could not get the next table from
the database.
Action:
Check for other ODBC error messages. Check
the System Event Viewer for system errors.
Check system resource availability (memory,
CPU).
Text:
The program could not get the list of tables from
the database.
Type:
Warn
Add’l Info:
The program could not get the list of tables from
the database.
Action:
Check for other ODBC error messages. Check
the System Event Viewer for system errors.
Check system resource availability (memory,
CPU).
SYNC3026
SYNC3027
SYNC3028
208
December 17, 2014
Error Messages
Error
Description
SYNC3029
Text:
The program could not get the column
description from the database.
Type:
Warn
Add’l Info:
The program could not get the column
description from the database.
Action:
Check for other ODBC error messages. Check
the System Event Viewer for system errors.
Check system resource availability (memory,
CPU).
Text:
The program could not get the number of
columns returned from the query.
Type:
Warn
Add’l Info:
The program could not get the number of
columns returned from the query.
Action:
Check for other ODBC error messages. Check
the System Event Viewer for system errors.
Text:
The program could not execute the SQL
statement.
Type:
Warn
Add’l Info:
The program could not execute the SQL
statement.
Action:
Check for other ODBC error messages.
Text:
The program could not prepare the SQL
statement.
Type:
Warn
Add’l Info:
The program could not prepare the SQL
statement.
Action:
Check for other ODBC error messages.
Text:
Unable to connect to the database, status: %d.
Type:
Warn
Add’l Info:
Unable to connect to the database.
Action:
Check for other ODBC error messages. Check
the communication with the ICM SQL Logger
Database.
SYNC3030
SYNC3031
SYNC3032
SYNC3033
December 17, 2014
209
Cisco CAD Error Code Dictionary
Error
Description
SYNC3034
Text:
The query failed on second try.
Type:
Warn
Add’l Info:
The query failed on second try.
Action:
Check the log for SQL error messages.
Text:
There is insufficient memory to handle the ODBC
statement.
Type:
Warn
Add’l Info:
There is insufficient memory to handle the ODBC
statement.
Action:
Check for other ODBC error messages. Check
the System Event Viewer for system errors.
Check system resource availability (memory,
CPU).
Text:
There is insufficient memory to establish an
ODBC connection with the Enterprise host.
Type:
Warn
Add’l Info:
There is insufficient memory to establish an
ODBC connection with the Enterprise host.
Action:
Check for other ODBC error messages. Check
the System Event Viewer for system errors.
Check system resource availability (memory,
CPU). Check the communication with the ICM
SQL Logger Database.
Text:
The program cannot communicate with the
Enterprise host via ODBC.
Type:
Warn
Add’l Info:
The program cannot communicate with the
Enterprise host via ODBC.
Action:
Check for other ODBC error messages. Check
the System Event Viewer for system errors.
Check system resource availability (memory,
CPU). Check the communication with the ICM
SQL Logger Database.
SYNC3035
SYNC3036
SYNC3037
210
December 17, 2014
Error Messages
Error
Description
SYNC3038
Text:
There is insufficient memory to handle the ODBC
statement.
Type:
Warn
Add’l Info:
There is insufficient memory to handle the ODBC
statement.
Action:
Check for other ODBC error messages. Check
the System Event Viewer for system errors.
Check system resource availability (memory,
CPU). Check the communication with the ICM
SQL Logger Database.
Text:
Failed to get switch type from LDAP, defaulting
to %ls. Error: <%d>, <%ls>.
Type:
Warn
Add’l Info:
Failed to get the switch type from LDAP.
Action:
Read the included error description. Make sure
that the LDAP Monitor service is up and running.
Text:
Failed to get the default LCC from LDAP. Error:
<%d>, <%ls>.
Type:
Warn
Add’l Info:
Failed to get the default LCC from LDAP.
Action:
Read the included error description. Make sure
that the LDAP Monitor service is up and running.
Text:
Failed to get the list of CallManagers from LDAP.
Error: <%d>, <%ls>.
Type:
Warn
Add’l Info:
Failed to get the list of Unified CMs from LDAP.
Action:
Read the included error description. Make sure
that the LDAP Monitor service is up and running.
Text:
Failed to add CallManager(%ls) to LDAP. Error:
<%d>, <%ls>.
Type:
Warn
Add’l Info:
Failed to add Unified CM to LDAP.
Action:
Read the included error description. Make sure
that the LDAP Monitor service is up and running.
SYNC3039
SYNC3040
SYNC3041
SYNC3042
December 17, 2014
211
Cisco CAD Error Code Dictionary
Error
Description
SYNC3043
Text:
Failed to update CallManager(%ls) in LDAP.
Error: <%d>, <%ls>.
Type:
Warn
Add’l Info:
Failed to update Unified CM in LDAP.
Action:
Read the included error description. Make sure
that the LDAP Monitor service is up and running.
Text:
Failed to remove CallManager(%ls) from LDAP.
Error: <%d>, <%ls>.
Type:
Warn
Add’l Info:
Failed to remove Unified CM from LDAP.
Action:
Read the included error description. Make sure
that the LDAP Monitor service is up and running.
Text:
Failed to synchronize CallManagers.
Type:
Warn
Add’l Info:
Failed to synchronize Unified CMs.
Action:
Read the log for other error messages. Make
sure that the LDAP Monitor service is up and
running.
Text:
Failed to get CallManager list from CRS.
Type:
Warn
Add’l Info:
Failed to get Unified CM list from Unified CCX.
Action:
Read the log for other error messages. Make
sure that the Unified CCX services are up and
running.
Text:
Could not create a necessary object [Mutex for
CFCDMCritSection object].
Type:
Error
Add’l Info:
Mutex for CFCDMCritSection object.
Action:
Check the system resources (memory &
handles) and restart the service.
SYNC3044
SYNC3045
SYNC3046
VOIP2000
212
December 17, 2014
Error Messages
Error
Description
VOIP2001
Text:
Could not create a necessary object [Shutdown
event].
Type:
Error
Add’l Info:
Shutdown event.
Action:
Check the system resources (memory &
handles) and restart the service.
Text:
Could not create a necessary object [LDAP
Up/Down event].
Type:
Error
Add’l Info:
LDAP Up/Down event.
Action:
Check the system resources (memory &
handles) and restart the service.
Text:
Could not find the Desktop Monitor adapter
name in the Registry.
Type:
Error
Add’l Info:
Desktop Monitor adapter name in the Registry
not available.
Action:
Check that installation has been completed and
all required values are in the registry.
Text:
Could not find the IOR Hostname entry in the
Registry.
Type:
Error
Add’l Info:
IOR Hostname entry in the Registry not
available.
Action:
Check that installation has been completed and
all required values are in the registry.
Text:
Could not create a necessary object
[initialization event].
Type:
Error
Add’l Info:
Check the system resources (memory &
handles) and restart the service.
Action:
Initialization event not created.
VOIP2002
VOIP2003
VOIP2005
VOIP2007
December 17, 2014
213
Cisco CAD Error Code Dictionary
Error
Description
VOIP2008
Text:
Could not create a necessary process [Desktop
Monitoring initialization thread].
Type:
Error
Add’l Info:
Desktop Monitoring initialization thread not
created.
Action:
Check the system resources (memory &
handles) and restart the service.
Text:
Could not create a necessary object
[CDesktopMonitor object].
Type:
Error
Add’l Info:
CDesktopMonitor object not created.
Action:
Check the system resources (memory &
handles) and restart the service.
Text:
Could not create a necessary object
[CFCDMMonitorServerList object].
Type:
Error
Add’l Info:
CFCDMMonitorServerList object not created.
Action:
Check the system resources (memory &
handles) and restart the service.
Text:
Could not create a necessary process [Corba
listening thread].
Type:
Error
Add’l Info:
Corba listening thread not available.
Action:
Check the system resources (memory &
handles) and restart the service.
Text:
Could not create a necessary object
[CFCDMCritSection object].
Type:
Error
Add’l Info:
CFCDMCritSection object not available.
Action:
Check the system resources (memory &
handles) and restart the service.
VOIP2009
VOIP2010
VOIP2011
VOIP2012
214
December 17, 2014
Error Messages
Error
Description
VOIP2013
Text:
Could not create a necessary object
[CFCDMSniffer object].
Type:
Error
Add’l Info:
CFCDMSniffer object not available.
Action:
Check the system resources (memory &
handles) and restart the service.
Text:
Could not create a necessary process [Periodic
Cleanup thread].
Type:
Error
Add’l Info:
Periodic Cleanup thread creation failed.
Action:
Check the system resources (memory &
handles) and restart the service.
Text:
Could not create a necessary process [LDAP
Connection Monitoring thread].
Type:
Error
Add’l Info:
LDAP Connection Monitoring thread creation
failed.
Action:
Check the system resources (memory &
handles) and restart the service.
Text:
Could not create a necessary object [Logout
event].
Type:
Error
Add’l Info:
Logout event creation failed.
Action:
Check the system resources (memory &
handles) and restart the service.
Text:
Could not create a necessary process [Login
thread].
Type:
Error
Add’l Info:
Login thread creation failed.
Action:
Check the system resources (memory &
handles) and restart the service.
VOIP2014
VOIP2015
VOIP2016
VOIP2017
December 17, 2014
215
Cisco CAD Error Code Dictionary
Error
Description
VOIP2019
Text:
Process ended prematurely [Login thread].
Type:
Error
Add’l Info:
Login thread ended.
Action:
Check the log and debug files for related errors
and restart.
Text:
Desktop monitoring enabled for extension [%hs].
Type:
Error
Add’l Info:
Desktop monitoring enabled for extension.
Action:
Subsystem will recover automatically, no action
needed unless further errors occur.
Text:
Process ended prematurely [LDAP thread].
Type:
Error
Add’l Info:
LDAP thread ended.
Action:
Check the log and debug files for related errors
and restart.
Text:
Could not create a necessary object [Sniffing
event].
Type:
Error
Add’l Info:
Sniffing event object creation error.
Action:
Check the system resources (memory &
handles) and restart the service.
Text:
Could not create a necessary object [Sniffer
session shutdown event].
Type:
Error
Add’l Info:
Sniffer session shutdown event object creation
error.
Action:
Check the system resources (memory &
handles) and restart the service.
Text:
Could not create a necessary process
[SnifferSession thread].
Type:
Error
Add’l Info:
SnifferSession thread creation error.
Action:
Check the system resources (memory &
handles) and restart the service.
VOIP2021
VOIP2023
VOIP2033
VOIP2034
VOIP2035
216
December 17, 2014
Error Messages
Error
Description
VOIP2036
Text:
Process ended prematurely [Sniffer Session
thread].
Type:
Error
Add’l Info:
Sniffer Session thread termination.
Action:
Check the system resources (memory &
handles) and restart the service.
Text:
Unable to open the NIC adapter for sniffing.
Please reconfigure the installation.
Type:
Error
Add’l Info:
Error opening NIC adapter.
Action:
Check the configuration and restart the VoIP
Monitor service.
Text:
Unable to get network information for the
adapter.
Type:
Error
Add’l Info:
Network information not available.
Action:
Check the configuration and restart the VoIP
Monitor service.
Text:
Unable to set the sniffing filter.
Type:
Error
Add’l Info:
Error while setting the sniffing filter.
Action:
Check the configuration and restart the VoIP
Monitor service.
Text:
No packets captured for [%lu] seconds.
Type:
Error
Add’l Info:
Error receiving packets.
Action:
Check the configuration and restart the VoIP
Monitor service.
Text:
System error. Failed to create socket for sending
out voice streams. Error: [%hs].
Type:
Error
Add’l Info:
Socket creation failed.
Action:
Restart the VoIP Monitor service.
VOIP2037
VOIP2038
VOIP2039
VOIP2041
VOIP2046
December 17, 2014
217
Cisco CAD Error Code Dictionary
Error
Description
VOIP2048
Text:
Could not get the MAC address for extension
[%hs] from the CallManager database.
Type:
Error
Add’l Info:
MAC Address not found.
Action:
Complete the following steps.
1. Check the Unified CM database for changes.
2. Verify the FCVoIP ODBC DSN is correct.
3. Verify that the Unified CM database is
running.
4. Verify that a record for the extension exists in
the Unified CM database.
5. Reinstall the monitor service if it requires a
new username or password.
VOIP2049
VOIP2050
218
Text:
Service connection IP address used by clients
not found in Registry. Service initialization will
not continue until CAD Configuration Setup has
been run to configure the software. (IOR
Hostname).
Type:
Error
Add’l Info:
MAC Address not found.
Action:
Check that installation has been completed and
all required values are in the registry.
Text:
The VoIP Service is missing information required
for start up.
Type:
Error
Add’l Info:
NIC monitoring adapter name not found in
Registry. Service initialization will not continue
until CAD Configuration Setup has been run to
configure the software.
Action:
NIC monitoring adapter name not found.
December 17, 2014
Error Messages
Error
Description
VOIP2051
Text:
System error. Unable to start a necessary
process: [Periodic Cleanup thread].
Type:
Error
Add’l Info:
Process creation failed.
Action:
Check the system resources (memory &
handles) and restart the service.
Text:
System error. Unable to start a necessary
process: [LRM thread].
Type:
Error
Add’l Info:
LRM thread creation failed.
Action:
Check the system resources (memory &
handles) and restart the service.
Text:
System error. Unable to start a necessary
process: [VPN thread].
Type:
Error
Add’l Info:
VPN thread creation failed.
Action:
Check the system resources (memory &
handles) and restart the service.
Text:
System error. Unable to start a necessary
process: [Corba thread].
Type:
Error
Add’l Info:
Corba thread creation failed.
Action:
Check the system resources (memory &
handles) and restart the service.
Text:
Unable to open the NIC adapter [%ls] for sniffing.
Type:
Error
Add’l Info:
NIC adapter opening failed.
Action:
Check the configuration and restart the VoIP
Monitor service.
VOIP2052
VOIP2053
VOIP2054
VOIP2055
December 17, 2014
219
Cisco CAD Error Code Dictionary
Error
Description
VOIP2056
Text:
System error. The NIC adapter used for sniffing
is not configured correctly.
Type:
Error
Add’l Info:
NIC adapter not configured correctly .
Action:
Check the configuration and restart the VoIP
Monitor service.
Text:
System error. The filter used for capturing voice
streams could not be set.
Type:
Error
Add’l Info:
Error while setting the filter.
Action:
Check the configuration and restart the VoIP
Monitor service.
Text:
System error. Unable to start a necessary
process: [LDAP Monitor thread].
Type:
Error
Add’l Info:
LDAP Monitor thread creation failed.
Action:
Check the system resources (memory &
handles) and restart the service.
Text:
System error. Client interface could not be
created. Retrying operation. (Corba).
Type:
Error
Add’l Info:
Failed to create Client interface.
Action:
If problems continue, restart the service.
Text:
We are unable to connect or reconnect to the
current CM. Trying subscribers.
Type:
Error
Add’l Info:
Failed to connect or reconnect to the current
Unified CM.
Action:
Check the status of the Unified CM processes.
There must be at least one Unified CM with an
active AXL database service in the cluster.
VOIP2057
VOIP2061
VOIP2062
VOIP2063
220
December 17, 2014
Error Messages
Error
Description
VOIP2064
Text:
All ODBC's have been unsuccessful.
Type:
Error
Add’l Info:
ODBCs failed.
Action:
Verify that the Unified CM database is running.
Text:
Could not determine the local IP address. Error:
[%hs]. (OmniOrbUseHostName invalid).
Type:
Error
Add’l Info:
OmniOrbUseHostName invalid.
Action:
Contact TAC for assistance.
Text:
Could not initialize the connection to the
CallManager database. AXL error: [%d: %ls].
Type:
Error
Add’l Info:
Unified CM database connection initialization
failed.
Action:
Verify that the Unified CM database is running
and that VoIP is configured correctly.
Text:
Unable to monitor agent. Cannot connect to the
VoIP Monitor Service [%hs] configured to
monitor extension [%hs].
Type:
Error
Add’l Info:
Unable to monitor agent
Action:
Check that the VoIP Monitor service is running
and active.
Text:
Unable to monitor agent. Host [%hs] is under
recovery.
Type:
Error
Add’l Info:
Unable to monitor agent.
Action:
Retry when the VoIP Monitor service recovery
completes.
Text:
Unable to monitor agent with VoIP Monitor
server [%hs]. Corba exception [%hs] returned.
Type:
Error
Add’l Info:
Unable to monitor agent.
Action:
Restart.
VOIP2065
VOIP2066
VOIP2067
VOIP2068
VOIP2069
December 17, 2014
221
Cisco CAD Error Code Dictionary
Error
Description
VOIP2070
Text:
Unable to monitor agent with VoIP Monitor
server [%hs]. Unknown Corba exception
returned.
Type:
Error
Add’l Info:
Unable to monitor agent.
Action:
Restart.
Text:
Unable to refresh the monitoring session with
the agent on extension [%hs]. Host [%hs] is
under recovery.
Type:
Error
Add’l Info:
Unable to refresh the monitoring session with
the agent.
Action:
Restart.
Text:
Unable to refresh the monitoring session with
the agent on extension [%hs] with the VoIP
Monitor service [%hs]. Corba exception [%hs]
returned.
Type:
Error
Add’l Info:
Unable to refresh the monitoring session with
the agent.
Action:
Restart.
Text:
Unable to refresh the monitoring session with
the agent on extension [%hs] with the VoIP
Monitor service [%hs]. Unknown Corba exception
returned.
Type:
Error
Add’l Info:
Unable to refresh the monitoring session with
the agent.
Action:
Restart.
Text:
Unable to stop the monitoring session. The VoIP
Monitor service [%hs] was not found.
Type:
Error
Add’l Info:
Unable to stop the monitoring session.
Action:
Restart.
VOIP2071
VOIP2072
VOIP2073
VOIP2074
222
December 17, 2014
Error Messages
Error
Description
VOIP2075
Text:
Unable to stop the monitoring session for
supervisor [%hs] on VoIP service [%hs]. Corba
exception [%hs] returned.
Type:
Error
Add’l Info:
Unable to stop the monitoring session for
supervisor.
Action:
Restart.
Text:
Unable to stop the monitoring session for
supervisor [%hs] on VoIP service [%hs].
Unknown Corba exception returned.
Type:
Error
Add’l Info:
Unable to stop the monitoring session for
supervisor.
Action:
Restart.
Text:
Caught a Corba exception while testing the
connection to the VoIP service [%hs].
Type:
Error
Add’l Info:
Caught a Corba exception while testing the
connection to the VoIP Monitor service.
Action:
Restart.
Text:
Unable to record agent. Cannot connect to the
VoIP Monitor Service [%hs] configured to
monitor extension [%hs].
Type:
Error
Add’l Info:
Unable to record Agent.
Action:
Restart.
Text:
Unable to record the agent with extension [%hs].
Host [%hs] is under recovery.
Type:
Error
Add’l Info:
Unable to record Agent.
Action:
Restart.
VOIP2076
VOIP2077
VOIP2079
VOIP2080
December 17, 2014
223
Cisco CAD Error Code Dictionary
Error
Description
VOIP2081
Text:
Unable to record the agent with extension [%hs]
using the VoIP Monitor service [%hs]. Corba
exception [%hs] returned.
Type:
Error
Add’l Info:
Corba exception Unable to record the agent.
Action:
Restart.
Text:
Unable to record the agent with extension [%hs]
using the VoIP Monitor service [%hs]. Unknown
Corba exception returned.
Type:
Error
Add’l Info:
Unknown Corba exception.Unable to record the
agent.
Action:
Restart.
Text:
Unable to record agent. Cannot connect to the
VoIP Monitor Service [%hs] configured to
monitor address [%hs].
Type:
Error
Add’l Info:
Unable to record agent.
Action:
Check that the VoIP Monitor service is running
and restart.
Text:
Unable to record the agent with rtpAddress
[%hs]. Host [%hs] is under recovery.
Type:
Error
Add’l Info:
Unable to record agent.
Action:
Check that the VoIP Monitor service is running.
Text:
Unable to record the agent with rtpAddress
[%hs] using the VoIP Monitor service [%hs].
Corba exception [%hs] returned.
Type:
Error
Add’l Info:
Unable to record the agent with rtpAddress.
Action:
Check that the VoIP Monitor service is running
and restart.
VOIP2082
VOIP2083
VOIP2084
VOIP2085
224
December 17, 2014
Error Messages
Error
Description
VOIP2086
Text:
Unable to record the agent with rtpAddress
[%hs] using the VoIP Monitor service [%hs].
Unknown Corba exception returned.
Type:
Error
Add’l Info:
Unable to record the agent with rtpAddress.
Action:
Check that the VoIP Monitor service is running
and restart.
Text:
Unable to stop the recording session. The VoIP
Monitor service [%hs] was not found.
Type:
Error
Add’l Info:
Unable to record the agent with rtpAddress.
Action:
Check that the VoIP Monitor service is running
and restart.
Text:
Unable to stop the recording session. The VoIP
Monitor service [%hs] is under recovery.
Type:
Error
Add’l Info:
Unable to stop the recording session.
Action:
Check that the VoIP Monitor service is running
and restart.
Text:
Unable to stop the recording session on VoIP
service [%hs]. Corba exception [%hs] returned.
Type:
Error
Add’l Info:
Corba exception. Unable to stop the recording
session.
Action:
Check that the VoIP Monitor service is running
and restart.
Text:
Unable to stop the recording session on VoIP
service [%hs]. Unknown Corba exception
returned.
Type:
Error
Add’l Info:
Unknown Corba exception. Unable to stop the
recording session.
Action:
Check that the VoIP Monitor service is running
and restart.
VOIP2087
VOIP2088
VOIP2089
VOIP2090
December 17, 2014
225
Cisco CAD Error Code Dictionary
Error
Description
VOIP2091
Text:
Unable to get connection information for the
VoIP service [%hs].
Type:
Error
Add’l Info:
Unable to get connection information for the
VoIP Monitor service.
Action:
Check that the VoIP Monitor service is running
and restart.
Text:
Invalid connection information for the VoIP
service [%hs].
Type:
Error
Add’l Info:
Unable to get connection information for the
VoIP Monitor service.
Action:
Check that the VoIP Monitor service is running
and restart.
Text:
Unable to initialize the Corba connection for VoIP
service [%hs].
Type:
Error
Add’l Info:
Unable to initialize the Corba connection for VoIP
Monitor service.
Action:
Check that the VoIP Monitor service is running
and restart.
Text:
Unable to get the VPN IP address from a VoIP
service.
Type:
Error
Add’l Info:
Unable to get the VPN IP address.
Action:
Check that the VoIP Monitor service is running
and restart.
Text:
Unable to get the MAC address for extension
[%hs] from the VoIP service [%hs]. Corba
exception [%hs] returned.
Type:
Error
Add’l Info:
Error getting the MAC address.
Action:
Check that the VoIP Monitor service is running
and configured correctly and restart.
VOIP2092
VOIP2093
VOIP2095
VOIP2096
226
December 17, 2014
Error Messages
Error
Description
VOIP2097
Text:
Unable to get the MAC address for extension
[%hs] from the VoIP service [%hs]. Unknown
Corba exception returned.
Type:
Error
Add’l Info:
Unknown Corba exception while looking for MAC
address.
Action:
Check that the VoIP Monitor service is running
and restart.
Text:
Unable to get the MAC address for extension
[%hs] from the VoIP service [%hs]. VoIP service
error returned.
Type:
Error
Add’l Info:
Unable to get the MAC address.
Action:
Check the VoIP Monitor service logs.
Text:
Unable to get the MAC address for extension
[%hs] from any VoIP service.
Type:
Error
Add’l Info:
Error while looking for MAC address.
Action:
Check the VoIP Monitor service logs.
Text:
Invalid connection information for the VoIP
service [%hs].
Type:
Error
Add’l Info:
Invalid connection information for the VoIP
Monitor service.
Action:
Check that the VoIP Monitor service is running
and restart.
Text:
Unable to initialize the Corba connection for VoIP
service [%ls].
Type:
Error
Add’l Info:
Unable to initialize the Corba connection.
Action:
Check that the VoIP Monitor service is running
and restart.
VOIP2098
VOIP2099
VOIP2100
VOIP2101
December 17, 2014
227
Cisco CAD Error Code Dictionary
Error
Description
VOIP2102
Text:
Unable to initialize Corba connection for desktop
monitoring of extension [%hs].
Type:
Error
Add’l Info:
Unable to initialize Corba connection for desktop
monitoring.
Action:
Check that the Client is running and restart.
Text:
Unable to initialize Corba connection for
recording extension [%hs].
Type:
Error
Add’l Info:
Unable to initialize Corba connection for
recording extension.
Action:
Check that the Client is running and restart.
Text:
Failed to start <%ls> thread.
Type:
Error
Add’l Info:
Failed to start thread.
Action:
Check the system resources (memory &
handles) and restart.
Text:
Failed to initialize Chat client: %d:%ls
Type:
Error
Add’l Info:
Unable to initialize Chat client because of
specified error. Cisco initiated monitoring may
fail.
Action:
Verify Chat service is running, active and
reachable from this computer. Restart Chat
service.
Text:
Failed to login Chat client: %d:%ls
Type:
Error
Add’l Info:
Unable to initialize Chat client because of
specified error. Cisco initiated monitoring may
fail.
Action:
Verify Chat service is running, active and
reachable from this computer. Restart Chat
service.
VOIP2103
VOIP2104
VOIP2106
VOIP2107
228
December 17, 2014
Error Messages
Error
Description
VOIP2108
Text:
Failed to start <%ls> thread: <%ls>.
Type:
Error
Add’l Info:
Specified thread could not be started.
Action:
Check if the machine is low on memory. Stop
unnecessary processes on the machine. Restart
the VoIP service. If the error persists, contact
technical support.
Text:
Failed to stop <%ls> thread: <%ls>.
Type:
Error
Add’l Info:
Specified thread could not be stopped.
Action:
Check if the machine is low on memory. Stop
unnecessary processes on the machine. Restart
the VoIP service. If the error persists, contact
technical support.
Text:
System error. Failed to create socket for VPN
service. Error: [%hs].
Type:
Warn
Add’l Info:
Failed to create socket for VPN service.
Action:
Read the included error description.
Text:
Unable to stop the monitoring session. The VoIP
Monitor service [%hs] is under recovery.
Type:
Warn
Add’l Info:
Unable to stop the monitoring session.
Action:
Read the included error description.
Text:
Could not create the LDAP recovery thread.
Type:
Warn
Add’l Info:
Could not create the LDAP recovery thread.
Action:
Read the included error description.
Text:
Unsupported Codec. PayloadType = <%ls>.
Type:
Warn
Add’l Info:
Unsupported Codec format.
Action:
Use one of the supported codec formats. G.711,
G.729, aLaw, or uLaw.
VOIP2109
VOIP3001
VOIP3002
VOIP3003
VOIP3004
December 17, 2014
229
Cisco CAD Error Code Dictionary
Error
Description
WAL1106
Text:
Out of memory.
Type:
Fatal
Add’l Info:
Application error
Action:
None.
Text:
Unable to read LDAP hosts from Registry.
Reason <%ls>.
Type:
Error
Add’l Info:
WebAdmin could not read the LDAP Hosts from
the registry.
Action:
Check that the LDAP host(s) are in the Site
Setup key.
Text:
Failed to write to LDAP. Action <%ls>. Error
<%ls>.
Type:
Error
Add’l Info:
WebAdmin could not write to LDAP.
Action:
Ensure LDAP is running properly, accepting
connections, and data integrity is good.
Text:
Unable to read IOR host name from Registry.
Reason <%ls>.
Type:
Error
Add’l Info:
WebAdmin could read the IOR hostname from
the Registry/Preference file.
Action:
Check that the IOR hostname is in the Site Setup
key.
Text:
GetHostname returned Local host loopback.
Type:
Error
Add’l Info:
SplkSocket returned Loopback address
Action:
Check network connections
Text:
SetKey login failed. Error = <%d>, <%ls>.
Type:
Error
Add’l Info:
SetKey login failed.
Action:
Check LDAP server and try again.
WAL2001
WAL2002
WAL2003
WAL2004
WAL2005
230
December 17, 2014
Error Messages
Error
Description
WAL2006
Text:
SetKey pwd failed. Error = <%d>, <%ls>.
Type:
Error
Add’l Info:
SetKey pwd failed.
Action:
Check LDAP server and try again.
Text:
Error Reading NIC Adapters
Type:
Error
Add’l Info:
Error Reading NIC Adapters
Action:
Check Splk Socket information.
Text:
At least one error occurred during the
synchronization process.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Could not connect to Directory Services
Synchronize Server.
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Could not convert from CORBAwstring to wstring.
Type:
Error
Add’l Info:
Could not convert from CORBAwstring to wstring
Action:
Retry manual sync.
Text:
Corba Error. CORBA::is_nil(vDAS).
Type:
Error
Add’l Info:
None.
Action:
None.
Text:
Error synchronizing directory services.
Type:
Error
Add’l Info:
Error synchronizing directory services.
Action:
Retry manual sync.
WAL2007
WAL2008
WAL2009
WAL2010
WAL2222
WAL2223
December 17, 2014
231
Cisco CAD Error Code Dictionary
Error
Description
WAL2224
Text:
Error notifying IPPA of Login method change.
Type:
Error
Add’l Info:
Error notifying IPPA of Login method change.
Action:
Restart IPPA.
Text:
Error getting GetServerIOR for Sync Server.
Type:
Error
Add’l Info:
Error getting GetServerIOR for Sync Server.
Action:
Retry manual sync.
WAL2237
232
December 17, 2014