cisco cad error code dictionary cad error code dictionary 4 december 12, 2013 acda3000 text: unable...

Cisco CAD Error Code DictionaryCAD 10.0 for Cisco Unified Contact Center Express Release 10.0

First Published: December 12, 2013Last Modified: December 12, 2013

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

http://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© 2013 Cisco Systems, Inc. All rights reserved.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

Documentation Feedback

You can provide comments about this document by sending email to the following address:

[email protected]

We appreciate your comments.

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

mailto:[email protected]

http://www.cisco.com/go/trademarks

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 12, 2013 3


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.

ACMI1000 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.

ACMI1000 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).

ACMI2000 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.

Error Description

4 December 12, 2013

Error Messages

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.

ACMI2003 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.

ACMI2004 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.

ACMI3001 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.

Error Description

December 12, 2013 5


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.


ACMI3003 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.

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 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.

Error Description

6 December 12, 2013

Error Messages

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.

ACMI3006 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.


ACMI3007 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.

ACMI3008 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.


Error Description

December 12, 2013 7


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.

ACMI3010 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.


ACMI3011 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.

Error Description

8 December 12, 2013

Error Messages

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.

Error Description

December 12, 2013 9


BIPPA1001 Text: BIPPA service is unable to create a TCP socket listener: <%d:%ls>.

Type: Fatal

Add’l Info: Unable to create TCP socket listener for the BIPPA service to receive requests from CAD-BE clients.




• 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.



Error Description

10 December 12, 2013

Error Messages

BIPPA1002 Text: BIPPA service TCP socket dispatcher failed to run: <%d:%ls>.

Type: Fatal

Add’l Info: TCP socket dispatcher in BIPPA service for receiving requests from CAD-BE clients failed to run.







Error Description

December 12, 2013 11


BIPPA1003 Text: BIPPA service failed to add BIPPA socket listener to socket dispatcher: <%d:%ls>.

Type: Fatal

Add’l Info: TCP socket listener used for receiving requests from CAD-BE clients could not be added to BIPPA socket dispatcher.







BIPPA2000 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.

Error Description


Error Messages

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.

BIPPA2002 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.


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 and CAD-BE to communicate with the BIPPA service.


• For UCCX, check the preferences to see if the TOMCAT HOME value in /opt/cisco/uccx/desktop/config/bippaservice/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/prefs.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.

Error Description


Error Messages

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.

BIPPA2005 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.


BIPPA2006 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.


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.


• Stop unnecessary processes on the machine.


• 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.


• 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 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.


Error Description


Error Messages

BIPPA2010 Text: Failed to accept socket connection: <%ls>.

Type: Error

Add’l Info: BIPPA service could not accept connection because of specified error.


• Check if the CAD-BE client terminated the connection. If so, it is not a problem.






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.


• Check if the CAD-BE client terminated the connection. If so, it is not a problem.






BIPPA2012 Text: Failed to start <%ls> thread: <%ls>.

Type: Error

Add’l Info: Specified thread could not be started.


• Check if the machine is low on memory.




Error Description


Error Messages

BIPPA2013 Text: Internal error. <%ls> wait event is invalid.

Type: Error

Add’l Info: A waitable event is invalid.


• Check if the machine is low on memory.




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.



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.


• 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.



BIPPA2016 Text: Failed to get switch type from LDAP.

Type: Error

Add’l Info: BIPPA service failed to get switch type from LDAP.


• 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.



BIPPA2017 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.

Error Description


Error Messages

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.

BIPPA2019 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.

BIPPA3000 Text: Unable to allocate memory: <%ls>.

Type: Warn

Add’l Info: Unable to allocate memory.

Action: Check system resource availability (CPU and memory).

BIPPA3001 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.


• Ensure that the user that the BIPPA service is running as has permission to read from preferences.



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:




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:




Error Description


Error Messages

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.





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.


• 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.


Error Description



BIPPA3006 Text: Internal error: Unknown format for icon file <%ls>.

Type: Warn

Add’l Info: Specified icon file has unknown file format.


• Ensure the file is an ICO or PNG file.

• Reload or replace icon file if needed.


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.


• Ensure the file is an ICO file.

• Ensure the file has an icon of specified size.



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.



• Ensure the file has an icon at specified index.



Error Description


Error Messages

BIPPA3009 Text: Internal error: Could not read file <%ls>.

Type: Warn

Add’l Info: Unable to read specified file.


• Ensure the file exists.

• Ensure the file is readable by user BIPPA service is running as.


BIPPA3010 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.

BIPPA3011 Text: Internal error: Could not write file <%ls>: <%ls>.

Type: Warn

Add’l Info: Unable to write specified file.


• Ensure the directory exists.

• Ensure the file/directory is writable by user BIPPA service is running as.


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.



• Ensure the file has a small image in index 0 and large image in index 1.



Error Description



BIPPA3013 Text: There are no more licenses available.

Type: Warn

Add’l Info: There are no more licenses available.


• Wait a few minutes and retry.

• CAD-BE agents may have exited their browsers without logging out first. Those sessions will continue to use up licenses for 1 minute after the browser exited.

• Agents logged out of extension mobility without logging out from CAD, CAD-BE 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 CAD-BE and 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.


• Ensure the file exists.


Error Description


Error Messages

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.


• 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.


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.


• Retry CTI action to see if it happens again.



BIPPA3017 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.

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.


• 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.


• 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.


• The client has to shutdown and restart again.

• A cadbe.jar or 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.

Error Description


Error Messages

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.

BIPPA3022 Text: Error sending socket message <%ls> to CAD-BE on <%ls:%d>: <%ls>.

Type: Warn

Add’l Info: BIPPA service was unable to send specified socket message to specified CAD-BE because of specified error.

Action: No action needed if occurred when CAD-BE browser is closed. Otherwise, verify computer where CAD-BE is running is not too slow, CAD server computer is not too slow, and network connection between CAD-BE computer and CAD server computer is not too slow.

BIPPA3023 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.

Error Description



BIPPAC1000 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.

BIPPAC1001 Text: Cannot get localization information for <%s> component.

Type: Fatal

Add’l Info: The specified component cannot get localization information.

Action: Verify that the CadBEStrings.properties file is in cadbe.jar on the BIPPA server. If the file is missing, remove the cadbe directory under ..\Cisco\Desktop\Tomcat\webapps on UCCE and ..\wfavvid\tomcat_appadmin\webapps on UCCX. The Tomcat service will recreate the missing file from the cadbe.war file. You may need to restart the Tomcat service on UCCE and CRS Administration on UCCX to force Tomcat to recreate the directory.

Error Description


Error Messages

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.

BIPPAC2000 Text: CAD-BE cannot retrieve <%s> event information from socket message.

Type: Error

Add’l Info: CAD-BE cannot retrieve specified event information from the socket message.

Action: Look at the status of the connection between CAD-BE and the BIPPA service. If the connection was disrupted, the CAD-BE client has lost data and the agent needs to log in again. If you upgraded the BIPPA service while CAD-BE clients were connected to it, the clients are now running a different version than the BIPPA service. In this case, agents must exit and restart their CAD-BE clients.

Error Description



BIPPAC2001 Text: BIPPA service at host <%s> is down.

Type: Error

Add’l Info: The connection from CAD-BE to the BIPPA service on the specified host failed.

Action: CAD-BE should automatically reconnect to the BIPPA service. If CAD-BE does not reconnect, complete the following steps:

• Verify that the BIPPA service is running and active.

• Verify that the client PC can communicate with the server on which the BIPPA service is running by telnetting to the server hostname or IP address on port 59012.

BIPPAC2002 Text: Insufficient memory to run CAD-BE applet: <%s>.

Type: Error

Type: There is insufficient memory to run the CAD-BE applet.

Add’l Info: Verify that the client PC has enough memory. If the PC has enough memory, verify that JVM has sufficient memory to run the CAD-BE applet. To verify that JVM has sufficient memory, from the Control Panel, start the Java Control Panel. On the Java tab, click Java Applet Runtime Settings. Verify that the Java Runtime Parameters has an -Xmx argument. If this argument is present, increase the value to at least 8 MB.

BIPPAC2003 Text: Client at IP address <%s> and BIPPA service at IP address <%s> have different product version: <%s>.

Type: Error

Add’l Info: CAD-BE applet and BIPPA service have different product version.

Action: Close CAD-BE browser and restart CAD-BE.

Error Description


Error Messages

BIPPAC3000 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.

BIPPAC3001 Text: Cannot get host address for this host.

Type: Warn

Add’l Info: Cannot get the address of this host because of access restriction.

Action: Accept the security certificate when you start CAD-BE.

BIPPAC3002 Text: Received an invalid event from the BIPPA service. Recovery initiated.

Type: Warn

Add’l Info: CAD-BE received an invalid event from the BIPPA service. The socket connection to the BIPPA service will be dropped and reconnected. This error may be caused by BIPPAC2000.

Action: Look at the status of the connection between CAD-BE and the BIPPA service. If the connection was disrupted, the CAD-BE client has lost data and the agent needs to log in again. If you upgraded the BIPPA service while CAD-BE clients were connected to it, the clients are now running a different version than the BIPPA service. In this case, agents must exit and restart their CAD-BE clients. If this error persists, contact technical support.

BIPPAC3003 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.

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.


BIPPAC3005 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. Accept the security certificate when you start CAD-BE. If this error persists, contact technical support.

CACMI2000 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.

CACMI2001 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.

Error Description


Error Messages

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.

CACMI3000 Text: LDAP Error: Failed to get <%ls>: %ls

Type: Warn

Add’l Info: AcmiClient is unable to get specified information from LDAP service.


CACMI3001 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.

CACMI3002 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.

Error Description



CADBE1000 Text: Cannot get configuration information for <%s> component from the BIPPA service.

Type: Fatal

Add’l Info: Communication between CAD-BE and service is slow.


CADBE1001 Text: The specified component cannot get localization information.

Type: Fatal

Add’l Info: None.

Action: Verify that the CadBEStrings.properties file is in cadbe.jar on the BIPPA server. If the file is missing, remove the cadbe directory under ..\Cisco\Desktop\Tomcat\webapps on UCCE and ..\wfavvid\tomcat_appadmin\webapps on UCCX. The Tomcat service will recreate the missing file from the cadbe.war file. You may need to restart the Tomcat service on UCCE and CRS Administration on UCCX to force Tomcat to recreate the directory.

Error Description


Error Messages

CADBE1002 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.

CADBE2000 Text: CAD-BE cannot retrieve <%s> event information from socket message.

Type: Error

Add’l Info: CAD-BE cannot retrieve specified event information from the socket message.

Action: Look at the status of the connection between CAD-BE and the BIPPA service. If the connection was disrupted, the CAD-BE client has lost data and the agent needs to log in again. If you upgraded the BIPPA service while CAD-BE clients were connected to it, the clients are now running a different version than the BIPPA service. In this case, agents must exit and restart their CAD-BE clients.

Error Description



CADBE2001 Text: BIPPA service at host <%s> is down.

Type: Error

Add’l Info: The connection from CAD-BE to the BIPPA service on the specified host failed.

Action: CAD-BE should automatically reconnect to the BIPPA service. If CAD-BE does not reconnect, complete the following steps: - Verify that the BIPPA service is running and active. - Verify that the client PC can communicate with the server on which the BIPPA service is running by telnetting to the server hostname or IP address on port 59012.

CADBE2002 Text: Insufficient memory to run CAD-BE applet: <%s>.

Type: Error

Add’l Info: There is insufficient memory to run the CAD-BE 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 CAD-BE applet. To verify that JVM has sufficient memory, from the Control Panel, start the Java Control Panel. On the Java tab, click Java Applet Runtime Settings. Verify that the Java Runtime Parameters has an -Xmx argument. If this argument is present, increase the value to at least 8 MB.

CADBE2003 Text: Client at IP address <%s> and BIPPA service at IP address <%s> have different product version: <%s>.

Type: Error

Add’l Info: CAD-BE applet and BIPPA service have different product version.

Action: Close CAD-BE browser and restart CAD-BE.

Error Description


Error Messages

CADBE3000 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.

Action: Close CAD-BE browser and restart CAD-BE. If that does not fix the problem, contact technical support.

CADBE3001 Text: Cannot get host address for this host.

Type: Warn

Add’l Info: Cannot get the address of this host because of access restriction.

Action: Accept the security certificate when you start CAD-BE.

CADBE3002 Text: Received an invalid event from the BIPPA service. Recovery initiated.

Type: Warn

Add’l Info: CAD-BE received an invalid event from the BIPPA service. The socket connection to the BIPPA service will be dropped and reconnected. This error may be caused by CADBE2000.

Action: Look at the status of the connection between CAD-BE and the BIPPA service. If the connection was disrupted, the CAD-BE client has lost data and the agent needs to log in again. If you upgraded the BIPPA service while CAD-BE clients were connected to it, the clients are now running a different version than the BIPPA service. In this case, agents must exit and restart their CAD-BE clients. If this error persists, contact technical support.

CADBE3003 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.

Error Description



CADBE3004 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.


CADBE3005 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. Accept the security certificate when you start CAD-BE. If this error persists, contact technical support.

CADEEMCONNECTOR2000

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.

Error Description


Error Messages

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.

CADEEMCONNECTOR2002

Text: Caught <%s> which should not happen.

Type: Error

Add’l Info: None.

Action: None.

CADEEMCONNECTOR3000

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.

CADLRM2000 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.

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.

CADLRM2006 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.

CADLRMS1000 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.

CADLRMS1001 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.

Error Description


Error Messages

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.

CADLRMS2002 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.

CADLRMS2004 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.

CADLRMS2005 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.

CADLRMS3000 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.

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.

CDAU12070 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.

CDAU12071 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.

CDAUI1000 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.

Error Description


Error Messages

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.

CDAUI1002 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.

CDAUI2000 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.

CDAUI2011 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.

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.

CDAUI2014 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.

CDAUI2015 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.

CDAUI2016 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.

CDAUI2019 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.

Error Description


Error Messages

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.

CDAUI2021 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.

CDAUI2023 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.

CDAUI2027 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.

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.

CDAUI2029 Text: Incorrect password. Try again.

Type: Error

Add’l Info: Authentication error. Entered password did not match.

Action: Enter the correct password for authentication.

CDAUI2032 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.

CDAUI2033 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.

If valid, try connecting to Unified Presence server with the same settings.

Error Description


Error Messages

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.

CDAUI2036 Text: An instantiation error has occured.

Type: Error

Add’l Info: An Object instantiation error has occurred.

Action: LDAP data error. Contact technical support.

CDAUI2042 Text: A security access error has occurred. Contact technical support.

Type: Error

Add’l Info: Security access error occurred.


CDAUI2043 Text: A no such method error has occurred. Contact technical support.

Type: Error

Add’l Info: Method that is referred is not existing.


CDAUI2044 Text: An illegal argument error has occurred. Contact technical support.

Type: Error

Add’l Info: Argument that is passed is not valid.


CDAUI2045 Text: An object instantiation error has occurred. Contact technical support.

Type: Error

Add’l Info: Object instantiation error.


Error Description



CDAUI2046 Text: An illegal access error has occurred. Contact technical support.

Type: Error

Add’l Info: Illegal access error occurred.


CDAUI2047 Text: An object invokation error has occurred. Contact technical support.

Type: Error

Add’l Info: Object invocation error occurred.


CDAUI2048 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.

CDAUI2049 Text: A no such field error has occurred. Contact technical support.

Type: Error

Add’l Info: No such field error occurred.


CDAUI2050 Text: An LDAP error has occured. Contact technical support.

Type: Error

Add’l Info: An LDAP error occurred.


Error Description


Error Messages

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.

CDAUI2052 Text: Error with the connection to LDAP: %s. Contact technical support.

Type: Error

Add’l Info: An LDAP connection error occurred.


CDAUI2053 Text: No %s was found corresponding to domain objects of type %s.

Type: Error

Add’l Info: Object error occurred.


CDAUI2054 Text: An error occured while casting a class. Contact technical support.

Type: Error

Add’l Info: Class type cast error occurred.


CDAUI2055 Text: A %s class not found error has occured. Contact technical support.

Type: Error

Add’l Info: Class not found error occurred.


CDAUI2056 Text: Error reading data from LDAP. Contact technical support.

Type: Error

Add’l Info: Error occurred while reading data from LDAP.


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.

CDAUI2061 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.

CDAUI2062 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.

CDAUI2065 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.

Error Description


Error Messages

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 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.

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.

CLUP2000 Text: Version mismatch.

Type: Error

Add’l Info: Server and uploading client versions do not match.

Action: None.

CLUP2001 Text: Client mismatch.

Type: Error

Add’l Info: Client file to upload has an invalid name.

Action: None.

CLUP2002 Text: Exception: %s

Type: Error

Add’l Info: Log exception.

Action: None.

CLUP2003 Text: %s

Type: Error

Add’l Info: Log stack trace.

Action: None.

Error Description


Error Messages

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.

CSI1001 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.

CSI2000 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.

CSI2001 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.

CSI2002 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

Error Description



CSI2003 Text: Failed to add/update to LDAP.

Type: Error

Add’l Info: Failed to add value to LDAP


CSI2004 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


CSI2005 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


CSI2006 Text: Failed to read profile for (%ls:%ls) from LDAP.

Type: Error

Add’l Info: Failed to read profile for specified user from LDAP


CSI2007 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


Error Description


Error Messages

CSI2008 Text: Failed to add/update in LDAP.

Type: Error

Add’l Info: Failed to write specified field in LDAP


CSI2009 Text: Failed to delete in LDAP.

Type: Error

Add’l Info: Failed to delete specified field in LDAP


CSI2010 Text: Failed to delete in LDAP.

Type: Error

Add’l Info: Failed to delete specified field in LDAP


CSI2011 Text: Failed to search for contacts in LDAP. Type (%d).

Type: Error

Add’l Info: LDAP Search for Contacts Failed


CSI2012 Text: Invalid CUP Server version for host.

Type: Error

Add’l Info: Invalid version of CUPS


CSI2013 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.

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.

CSI2015 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.

CSI2016 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.

CSI2017 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.

CSI2018 Text: Caught a xercesc::XMLException. Exception message.

Type: Error

Add’l Info: Caught a xercesc::XMLException.


Error Description


Error Messages

CSI2019 Text: Caught a xercesc::DOMException. Exception message.

Type: Error

Add’l Info: Caught a xercesc::DOMException.


CSI2020 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.

CSI2021 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.

CSI3000 Text: The SOAP message does not have tag name.

Type: Warn

Add’l Info: None.

Action: None.

CSI3001 Text: The SOAP message does not have tag name for root tag.

Type: Warn

Add’l Info: None.

Action: None.

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.


DESK2000 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.

DESK2002 Text: Directory Services unable to write macro binary to %ls

Type: Warn

Add’l Info: Communication with directory services was lost.

Action: Reestablish communication.

DESK2003 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.

DESK2004 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.

Error Description


Error Messages

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.

DESK2006 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

DESK2007 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

DESK2009 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.

DESK2010 Text: Unable to read icon profile from LDAP.

Type: Warn

Add’l Info: Unable to read icon profile from LDAP.

Action: None.

DESK2011 Text: Unable to save to Enterprise Database.

Type: Warn

Add’l Info: Unable to save to Enterprise Database.

Action: None.

Error Description



DESK2012 Text: Unable to Logout of RASCAL Server. Error Message = %ls.

Type: Warn

Add’l Info: None.

Action: None.

DESK2013 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

DESK2014 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

DESK2016 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

DESK2017 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

DESK2018 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

Error Description


Error Messages

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

DESK2020 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


DESK2024 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.

DESK2025 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.

DESK2026 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.

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

DESK2048 Text: LRM Inactive Message received.

Type: Warn

Add’l Info: LRM Inactive Message received.

Action: Restart LRM

DESK2049 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

DESK2050 Text: Unable to read Skill Statistics report settings.

Type: Warn



DESK2051 Text: Unable to read Agent Detail report settings.

Type: Warn



DESK2052 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

Error Description


Error Messages

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

DESK2054 Text: Already recording a call at this agent.

Type: Warn

Add’l Info: Duplicate agent ID

Action: Log supervisor out and log back in

DESK2055 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

DESK2056 Text: Attempted to stop recording the callID, but couldn't find the appearance.

Type: Warn



DESK2057 Text: Error getting skill stats. PhoneDev Error.

Type: Warn



DESK2058 Text: Error setting volume level.

Type: Warn

Add’l Info: Error while setting volume.

Action: Restart RASCAL and/or Application.

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.

DESK2060 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.

DESK2061 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

DESK2062 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.

DESK2063 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.

Error Description


Error Messages

DESK2064 Text: Unable to convert macro to binary from %ls: %ls

Type: Warn

Add’l Info: Unable to convert macro to binary

Action: None.

DESK2065 Text: Unable to read Agent Email Log Report settings.

Type: Warn



DESK2066 Text: Unable to read Agent Email Detail Report settings.

Type: Warn



DESK2067 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.

DESK2121 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

DESK2122 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


Error Description



DESK2123 Text: Unable to get RASCAL Global ID for new appearance.

Type: Warn

Add’l Info: Can't get RASCAL global ID


DESK2124 Text: Corrupt ActionList.

Type: Warn

Add’l Info: The ActionList is corrupted

Action: Check the action list in LDAP

DESK2125 Text: Action Index Corrupt

Type: !Warn

Add’l Info: The ActionList is corrupted

Action: Check the action list in LDAP

DESK2126 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

DESK2127 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

DESK2128 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

Error Description


Error Messages

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.

DESK2130 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

DESK2131 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

DESK2132 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

DESK2133 Text: Drop Call Control Action - Empty Call ID.

Type: Warn

Add’l Info: Empty CALLID

Action: Check if the callid is valid

DESK2134 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

DESK2135 Text: Touch Tones Call Control Action - Empty Call ID.

Type: Warn

Add’l Info: Empty callid

Action: check if the call has valid callid

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

DESK2137 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

DESK2138 Text: Redirect Call Control Action - Empty Call ID.

Type: Warn


Action: check if callid is valid

DESK2139 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

DESK2140 Text: Conference Call Control Action - Empty Call ID.

Type: Warn


Action: Check in conference event if callid is not empty

DESK2141 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

Error Description


Error Messages

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

DESK2143 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

DESK2144 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

DESK2145 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

DESK2146 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

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.


DESK2200 Text: CORBA::TRANSIENT is raised minor:<%d>, completion_status:<%d>, retries<%d>.

Type: Warn



DESK2201 Text: AtlUnadvise failed. Error code = 0x<%x>, <%ls>.

Type: Warn



DESK2202 Text: Could not read the Admin Password Set from LDAP. Error code = <%d>, <%ls>

Type: Warn



DESK2203 Text: Could not save Admin Password to LDAP. Error code = <%d>, <%ls>

Type: Warn



Error Description


Error Messages

DESK2204 Text: Could not read the server profile from LDAP. Error code = <%d>, <%ls>

Type: Warn



DESK2206 Text: Could not read product offering from LDAP. Error code = <%d>, <%ls>

Type: Warn



DESK3000 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

DESK3001 Text: Found callID %d, but call was NULL.

Type: Error

Add’l Info: Call node object is invalid.

Action: Restart Cisco Supervisor Desktop.

DESK3002 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.

DESK3003 Text: Chat server error while intercepting in on deviceID %s on callID %d.

Type: Error



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.

DESK3005 Text: Chat Login failed.

Type: Error



DESK3006 Text: Chat AddUser failed.

Type: Error



DESK3007 Text: Chat DropUser failed.

Type: Error



DESK3008 Text: Get Team Snapshot failed.

Type: Error



DESK3009 Text: GenericMessage failed.

Type: Error



DESK3010 Text: Chat SendMsg failed

Type: Error



Error Description


Error Messages

DESK3011 Text: Chat ChangeCallStatus failed.

Type: Error



DESK3012 Text: Chat ChangeOtherPartyCallStatus failed.

Type: Error



DESK3013 Text: Chat ChangeCallID failed.

Type: Error



DESK3014 Text: Chat SetAgentAcdState failed.

Type: Error



DESK3015 Text: Chat BargeIn failed.

Type: Error



DESK3016 Text: Intercept failed.

Type: Error



DESK3017 Text: Chat SetGenericAgentState failed.

Type: Error



Error Description



DESK3018 Text: SendSpecialServerCommand failed.

Type: Error



DESK3019 Text: Unable to retrieve team names.

Type: Error



DESK3020 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.

DESK3021 Text: Error: get supervisor returned.

Type: Error



DESK3022 Text: Error: agentexists returned.

Type: Error



DESK3023 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.

DESK3024 Text: Chat server error.

Type: Error

Add’l Info: Unknown Chat service error.


Error Description


Error Messages

DESK3025 Text: InitCallChatClient failed.

Type: Error

Add’l Info: Chat service error.


DESK3026 Text: Initialize failed with error.

Type: Error


Action: Restart the Chat service. See the error description for more details.

DESK3027 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.

DESK3028 Text: Chat server error while adding user.

Type: Error



DESK3029 Text: Chat server error while logging in.

Type: Error



DESK3030 Text: Unable to connect to Enterprise.

Type: Error

Add’l Info: Enterprise service error.

Action: Restart the Enterprise service.

DESK3031 Text: CBrowserFrame::OnCreate: Major error - exception thrown!!

Type: Error

Add’l Info: CSD CBrowserFrame::OnCreate error.

Action: Restart CSD.

Error Description



DESK3032 Text: CBrowserFrame::LoadToolbar: Major error - exception thrown!!

Type: Error

Add’l Info: CSD CBrowserFrame::LoadToolbar error.


DESK3033 Text: CBrowserFrame::ReLoadBrowserButtons: Major error - exception thrown!!

Type: Error

Add’l Info: CSD CBrowserFrame::ReLoadBrowserButtons error.


DESK3034 Text: CBrowserView::OnInitialUpdate: Major error - exception thrown!!

Type: Error

Add’l Info: CSD CBrowserView::OnInitialUpdate error.


DESK3035 Text: CBrowserView::OnDocumentComplete: Major error - exception thrown!!

Type: Error

Add’l Info: CSD CBrowserView::OnDocumentComplete error.


DESK3036 Text: CBrowserView::Load() Major error - exception thrown!!

Type: Error

Add’l Info: CSD CBrowserView::Load() error.


DESK3037 Text: ChatAPI AddPresenceUser failed.

Type: Error

Add’l Info: Unified Presence server error.

Action: Restart Unified Presence server.

Error Description


Error Messages

DESK3038 Text: ChatAPI DropPresenceUser failed.

Type: Error



DESK3039 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.

DESK3040 Text: Error occurred when setting the playback position. Error: <%ls>.

Type: Error

Add’l Info: Cannot change playback position.


DESK3041 Text: Error occurred attempting resume operation. Error: <%ls>.

Type: Error

Add’l Info: Cannot resume playback.


DESK3042 Text: Error logging out of Recording/Playback server. Error: <%ls>.

Type: Error

Add’l Info: Cannot log out of Recording & Playback service.


DESK3043 Text: Error getting volume level from the Recording/Playback server. Error: <%ls>.

Type: Error

Add’l Info: Cannot get volume level from server.


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.

DESK3045 Text: ChatAPI getPresenceContactList failed.

Type: Error



DESK3046 Text: One or more critical pointers are NULL - returning.

Type: Error

Add’l Info: One or more critical pointers are NULL - returning.

Action: None

DESK3047 Text: Major error - exception thrown

Type: Error

Add’l Info: Major error - exception thrown

Action: None

DESK3048 Text: Error connecting to LDAP.

Type: Error

Add’l Info: Communication problem

Action: Reestablish communication with Directory Services.

DESK3049 Text: Error calling setAgentAcdState

Type: Error



Error Description


Error Messages

DESK3050 Text: CTIOS exception occurred. Description.

Type: Error

Add’l Info: Unknown exception


DESK3051 Text: FailedServer = ReasonCode

Type: Error

Add’l Info: Unknown exception


DESK3052 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.

DESK3101 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.

DESK3102 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.

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.

DESK3105 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.

DESK3107 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.

DESK3109 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

DESK3110 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

DESK3111 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

Error Description


Error Messages

DESK3112 Text: Unknown exception while retrieving a license.

Type: Error

Add’l Info: LRM is not running

Action: check if the server is running

DESK3113 Text: Unknown exception while releasing the license(s)

Type: Error


Action: check if the server is running

DESK3115 Text: Unable to Login Desktop Monitoring

Type: Error

Add’l Info: Desktop monitoring is not running

Action: Check if Desktop monitoring is running

DESK3116 Text: Unable to Start Desktop Monitoring

Type: Error

Add’l Info: Desktop monitoring is not running

Action: Check if Desktop monitoring is running

DESK3117 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.

DESK3118 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.

DESK3119 Text: Read reason codes failed.

Type: Error

Add’l Info: Chat server error.

Action: Restart Chat server.

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.

DESK3121 Text: Read Wrap-up data failed.

Type: Error

Add’l Info: LDAP monitor is not running.

Action: Restart LDAP monitor.

DESK3122 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.

DESK3124 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.

DESK3125 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.

DESK3126 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.

Error Description


Error Messages

DESK3135 Text: Error = <%ls>.

Type: Error

Add’l Info: None.

Action: None.

DESK3204 Text: Failed to open registry key.

Type: Error

Add’l Info: None.

Action: None.

DESK3205 Text: Failed to read value on Entry in the registry key.

Type: Error

Add’l Info: None.

Action: None.

DESK3209 Text: Error saving server profile.

Type: Error

Add’l Info: None.

Action: None.

DESK3210 Text: Error updating the Active TServer entry.

Type: Error

Add’l Info: None.

Action: None.

DESK3211 Text: Error getting server profile.

Type: Error

Add’l Info: None.

Action: None.

DESK3212 Text: Failed to write value to the registry key.

Type: Error

Add’l Info: None.

Action: None.

Error Description



DESK3213 Text: Failed to iterate registry key.

Type: Error

Add’l Info: None.

Action: None.

DESK3214 Text: Error GetKeyValue Switch Type. Error code = <%d>, <%ls>.

Type: Warn

Add’l Info: None.

Action: None.

DESK3215 Text: Error GetKeyValue CTI Type. Error code = <%d>, <%ls>.

Type: Warn

Add’l Info: None.

Action: None.

DESK3216 Text: Error GetServerTypeProfile. Error code = <%d>, <%ls>.

Type: Warn

Add’l Info: None.

Action: None.

DESK3217 Text: Error getting switch and CTI type.

Type: Error

Add’l Info: None.

Action: None.

DESK3221 Text: Error getting GetServerIOR for Sync Server.

Type: Error

Add’l Info: None.

Action: None.

DESK3222 Text: Corba Error. CORBA::is_nil(vDAS).

Type: Error

Add’l Info: None.

Action: None.

Error Description


Error Messages

DESK3223 Text: Error synchronizing directory services.

Type: Error

Add’l Info: None.

Action: None.

DESK3224 Text: Could not update Required Admin Password.

Type: Error

Add’l Info: None.

Action: None.

DESK3225 Text: Could not set the new Admin Pwd.

Type: Error

Add’l Info: None.

Action: None.

DESK3226 Text: Failed to load Enterprise Administrator (Administrator.exe)

Type: Error

Add’l Info: None.

Action: None.

DESK3227 Text: Failed to load Personnel.exe.

Type: Error

Add’l Info: None.

Action: None.

DESK3228 Text: Failed to load Administrator.exe.

Type: Error

Add’l Info: None.

Action: None.

DESK3229 Text: Failed to load IPCCAdm.exe.

Type: Error

Add’l Info: None.

Action: None.

Error Description



DESK3232 Text: Failed to load SWFAdmin.exe.

Type: Error

Add’l Info: None.

Action: None.

DESK3233 Text: Could not add workspace for server name.

Type: Error

Add’l Info: None.

Action: None.

DESK3234 Text: Unexpected error reported.

Type: Error

Add’l Info: None.

Action: None.

DESK3236 Text: SetEvent failed.

Type: Error

Add’l Info: None.

Action: None.

DESK3237 Text: Error getting GetServerIOR for Sync Server.

Type: Error

Add’l Info: None.

Action: None.

DESK3400 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.

DESK3402 Text: Could not read action disk file.

Type: Error

Add’l Info: An attempt to read the disk file has failed.

Action: unknown

Error Description


Error Messages

DESK3403 Text: Action upload to LDAP failed.

Type: Error

Add’l Info: LDAP Error

Action: unknown

DESK3404 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.

DESK3406 Text: Could not create folder.

Type: Error

Add’l Info: None.

Action: None.

DESK3407 Text: The version of action file is not compatible with the application version.

Type: Error

Add’l Info: None.

Action: None.

DESK4001 Text: Unable to log into Voice over IP Monitor server.

Type: Fatal

Add’l Info: None

Action: Check status of VoIP Monitor Server.

DESK4002 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.

DESK4003 Text: Fail to create BrowserFrame

Type: Fatal

Add’l Info: Fail to create BrowserFrame

Action: Restart application.

Error Description



DESK4004 Text: Failed to reload

Type: Fatal

Add’l Info: Fail to reload one of the toolbars


DESK4005 Text: Failed to create bar

Type: !Fatal

Add’l Info: Fail to create one of the toolbars


DESK4007 Text: Unable to verify licence. License error

Type: Fatal


Action: check if LRM is running or wrong LCC or wrong LDAP host

DESK4008 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.

DESK4010 Text: Initialization failed, could not create message window.

Type: Fatal

Add’l Info: Windows system error

Action: Try to restart agent to login

DESK4011 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.

Error Description


Error Messages

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

DESK4013 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

DESK4014 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

DESK4015 Text: Unable to login - Query Confirmation returned logout or unknown agent state.

Type: Fatal

Add’l Info: CTIOS server error

Action: Restart CTIOS server

DESK4016 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

DESK4017 Text:

Type: Fatal

Add’l Info: None.

Action: None.

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

DESK4101 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

DESK4102 Text: Application error.

Type: Fatal

Add’l Info: Voice Over IP not running.

Action: Restart Voice over IP server.

DESK4103 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.

DESK4105 Text: Waiting for timer action event failed with error

Type: Fatal

Add’l Info: Application error

Action: None.

DESK4106 Text: Out of memory.

Type: Fatal


Action: None.

Error Description


Error Messages

DESK4107 Text: AutoRecoverConnection failed ExitInstance. Error code = <%d>, <%ls>.

Type: Fatal


Action: None.

DESK4108 Text: Unable to download JRE from URL: <%ls>.

Type: Fatal

Add’l Info: None

Action: Verify URL is accessible.

EEM1000 Text: Cannot connect to IMAP service, could not resolve host name to an IP address: %s.

Type: Fatal


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.

Error Description



EEM1001 Text: Cannot connect to IMAP service, could not connect to server.

Type: Fatal


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.

Error Description


Error Messages

EEM1002 Text: Cannot connect to IMAP service, Invalid username or password: <%s>.

Type: Fatal


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 "[email protected]", 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 [email protected] ********* . OK User logged in.

Error Description



EEM1003 Text: Cannot connect to IMAP service: %s.

Type: Fatal


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.

EEM1004 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


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.

Error Description


Error Messages

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


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.

Error Description



EEM1006 Text: A connection to the SMTP service could not be made, The user name and password are not valid.

Type: Fatal


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 “[email protected]”, 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.)

Error Description


Error Messages

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:[email protected] 250 2.1.0 [email protected] OK RCPT TO:[email protected] 250 2.1.5 [email protected].... Recpient OK DATA 354 Please start mail input. Test of telnet smtp 250 Mail queued for delivery.

EEM1007 Text: Cannot connect to SMTP service: %s.

Type: Fatal


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.

Error Description



EEM1008 Text: The user specified does not have a mailbox located on the configured server.

Type: Fatal


Action: Verify that the configured account can login and access their mailbox on the configured server.

EEM1009 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.

EEM1010 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.

EEM2000 Text: Could not retrieve specified information from the data buffer.

Type: Error


Action: Look for disruptions in the connection between the Exchange Server and the Email Manager applet.

EEM2001 Text: There is insufficient memory to run the EEM applet.

Type: Error


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.

Error Description

100 December 12, 2013

Error Messages

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


Action: Look in the log to see if the connection attempt eventually succeeds or fails for another reason.

EEM2003 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


Action: None.

EEM2004 Text: Client cannot retrieve specified event information from the socket message.

Type: Error


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.

Error Description

December 12, 2013 101


EEM2005 Text: This is an internal error. The client is not configured with the information that it needs to locate the service.

Type: Error


Action: Ensure that the client is configured with the information that it needs to locate the service.

EEM2006 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


Action: None.

EEM2007 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


Action: None.

EEM2008 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.

Error Description

102 December 12, 2013

Error Messages

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.

EEM2010 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.

EEM3000 Text: Could not make %s IMAP connection.

Type: Warn


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.

Error Description

December 12, 2013 103


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.

EEM3002 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.

EEM3003 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.

Error Description

104 December 12, 2013

Error Messages

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.

EEM3005 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.

EEM3006 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.

Error Description

December 12, 2013 105


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.

EEMAPP1000 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.

EEMAPP1001 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.

Error Description

106 December 12, 2013

Error Messages

EEMAPP2000 Text: EEMApp could not load the specified resource bundle for the specified locale.

Type: Error


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.

EEMAPP2001 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.

EEMAPP2002 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.

EEMAPP3000 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.

Error Description

December 12, 2013 107


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.

EEMAPP3002 Text: The EEMApp could not load the list of assigned emails.

Type: Warn


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.

EEMAPP3003 Text: The EEMApp could not load the assigned email.

Type: Warn


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.

EEMAPP3004 Text: A draft could not be saved for the assigned email.

Type: Warn


Action: Verify that the EEMApp is configured correctly and able to connect to the mail store. See the debug log for more details.

Error Description

108 December 12, 2013

Error Messages

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.


EEMAPP3006 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.


EEMAPP3007 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.

EEMAPP3008 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.

Error Description

December 12, 2013 109


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.

EEMAPP3010 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.

EEMC2000 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.

EEMC3000 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.

Error Description

110 December 12, 2013

Error Messages

EEMS1000 Text: The SocketService could not be started. Reason: (%ls)

Type: Fatal


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.

EEMS1001 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.

EEMS1002 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.

EEMS1003 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.

EEMS2001 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.

Error Description

December 12, 2013 111


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.

EEMS2003 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.

EEMS2004 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.

EEMS2005 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.

Error Description

112 December 12, 2013

Error Messages

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.

EEMS3001 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.

EEMS3002 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.

EEMS3003 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.

EEMS3004 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.

Error Description

December 12, 2013 113


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.

EEMUI1001 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

EEMUI2000 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.

EEMUI2001 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.

Error Description

114 December 12, 2013

Error Messages

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.

EEMUI3000 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.

EEMUI3001 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.

EEMUI3002 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.

EEMUI3003 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.

Error Description

December 12, 2013 115


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.

EEMUI3005 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.

EEMUI3006 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.


EEMUI3007 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.

Error Description

116 December 12, 2013

Error Messages

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.

EEMUI3009 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.

EEMUI3010 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.

EEMUI3011 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.


Error Description

December 12, 2013 117


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.

EEMUI3013 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.

LRM3004 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).

LRM3005 Text: Failed to receive message from the CRS CVD <%d>.

Type: Warn

Add’l Info: Message receive failed


Error Description

118 December 12, 2013

Error Messages

LRM3006 Text: Failed to initialize the connection to CRS CVD.

Type: Warn

Add’l Info: Connection initialization failed


LRM3007 Text: Failed to connect to the CRS CVD.

Type: Warn

Add’l Info: failed to connect


FCCC2002 Text: Unable to create thread.

Type: Fatal

Add’l Info: None.


FCCC2003 Text: Unexpected error. WaitForSingleObject failed.

Type: Fatal

Add’l Info: None.


FCCC2004 Text: Unexpected error. WaitForMultipleObjects failed.

Type: Fatal

Add’l Info: None.


FCCC2005 Text: Network communication error.

Type: Fatal

Add’l Info: None.

Action: Check network connectivity. Verify that the Chat Service is running.

Error Description

December 12, 2013 119


FCCC2009 Text: Unexpected exception.

Type: Fatal

Add’l Info: None.


FCCC2010 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).

FCCC2011 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).

FCCC2014 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).

Error Description

120 December 12, 2013

Error Messages

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.

FCCC2016 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.

FCCC2017 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.

FCCC3000 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.

FCCC3001 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.

Error Description

December 12, 2013 121


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.

FCCS1001 Text: Unable to create thread.

Type: Fatal

Add’l Info: None.


FCCS1002 Text: Unable to start any working threads.

Type: Fatal

Add’l Info: None.


FCCS1003 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.

FCCS1007 Text: Unexpected error. Wait For Multiple Objects failed.

Type: Fatal

Add’l Info: None.


Error Description

122 December 12, 2013

Error Messages

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.

FCCS1009 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).

FCCS1010 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).

FCCS1011 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).

Error Description

December 12, 2013 123


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).

FCCS1013 Text: Unexpected exception in the main network communication thread (fcCorbaServer).

Type: Fatal

Add’l Info: None.


FCCS2000 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).

FCCS2001 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.

FCCS2002 Text: Unable to create a new working thread.

Type: Error

Add’l Info: None.


Error Description

124 December 12, 2013

Error Messages

FCCS2003 Text: Unexpected exception in a working thread.

Type: Error

Add’l Info: None.


FCCS2004 Text: Unexpected exception in the manager thread.

Type: Error

Add’l Info: None.


FCCS2009 Text: Unexpected exception.

Type: Error

Add’l Info: None.


FCCS2010 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).

FCCS2011 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).

Error Description

December 12, 2013 125


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.

FCCS2013 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).

FCCS2014 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).

Error Description

126 December 12, 2013

Error Messages

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.


FCCS2016 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.


FCCS3000 Text: Unable to close thread handle.

Type: Warn

Add’l Info: None.


Error Description

December 12, 2013 127


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.

FCRasServer0220

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.

FCRasServer0226

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.

Error Description

128 December 12, 2013

Error Messages

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.

FCRasServer1012

Text: Unexpected exception during network communication initialization.

Type: Fatal

Add’l Info: Unexpected exception during network communication initialization

Action: None

FCRasServer1013

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

Error Description

December 12, 2013 129


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.

FCRasServer2009

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.

FCRasServer2108

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.

FCRasServer2109

Text: Failure when executing query

Type: Error

Add’l Info: Failure when executing query

Action: None.

FCRasServer2110

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.

Error Description

130 December 12, 2013

Error Messages

FCVRS1001 Text: Unable to create thread.

Type: Fatal

Add’l Info: None.


FCVRS1003 Text: Error handling command line arguments.

Type: Fatal

Add’l Info: None.

Action: Check the command line usage.

FCVRS1007 Text: Unexpected error. WaitForMultipleObjects failed.

Type: Fatal

Add’l Info: None.


FCVRS1008 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.

FCVRS1009 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).

Error Description

December 12, 2013 131


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).

FCVRS1011 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).

FCVRS1012 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).

FCVRS1013 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.

Error Description

132 December 12, 2013

Error Messages

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).

FCVRS2001 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.

FCVRS2002 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.

FCVRS2008 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.

Error Description

December 12, 2013 133


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.

FCVRS2010 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).

FCVRS2011 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).

FCVRS2012 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.

Error Description

134 December 12, 2013

Error Messages

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).

FCVRS2015 Text: Unable to write registry value.

Type: Error

Add’l Info: None.


FCVRS2016 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.

FCVRS2017 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.

FCVRS2018 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.

Error Description

December 12, 2013 135


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.

FCVRS2020 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.

FCVRS3000 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.

FCVRS3001 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.

Error Description

136 December 12, 2013

Error Messages

FMWK2000 Text: CORBA::TRANSIENT is raised minor:<%d>, completion_status:<%d>, retries<%d>.

Type: Warn

Add’l Info: None.

Action: None.

FMWK2001 Text: AtlUnadvise failed. Error code = 0x<%x>, <%s>.

Type: Warn

Add’l Info: None.

Action: None.

FMWK2002 Text: Could not read the Admin Password Set from LDAP. Error code = <%d>, <%s>.

Type: Warn

Add’l Info: None.

Action: None.

FMWK2003 Text: Could not save Admin Password to LDAP. Error code = <%d>, <%s>.

Type: Warn

Add’l Info: None.

Action: None.

FMWK2004 Text: Could not read the server profile from LDAP. Error code = <%d>, <%s>.

Type: Warn

Add’l Info: None.

Action: None.

FMWK2005 Text: Could not save the server type profile to LDAP. Error code = <%d>, <%s>.

Type: Warn

Add’l Info: None.

Action: None.

Error Description

December 12, 2013 137


FMWK2006 Text: Could not read product offering from LDAP. Error code = <%d>, <%s>.

Type: Warn

Add’l Info: None.

Action: None.

FMWK3000 Text: Wait returns <%d> : Handle could be bad.

Type: Error

Add’l Info: The function that was called has failed to respond.

Action: None.

FMWK3001 Text: Failed to get local LCC from the registry.

Type: Error

Add’l Info: None.

Action: None.

FMWK3002 Text: Error in GetKeyValue for LCUSTOM_KEY_ALLOWUPDATE. Error = <%s>.

Type: Error

Add’l Info: None.

Action: None.

FMWK3003 Text: AutoRecoverConnection failed. Error code = <%d>, <%s>.

Type: Error

Add’l Info: None.

Action: None.

FMWK3004 Text: Failed to open registry key.

Type: Error

Add’l Info: None.

Action: None.

Error Description

138 December 12, 2013

Error Messages

FMWK3005 Text: Failed to read value on Entry in the registry key.

Type: Error

Add’l Info: None.

Action: None.

FMWK3006 Text: Failed to write value 1 on Entry in the registry key.

Type: Error

Add’l Info: None.

Action: None.

FMWK3007 Text: Error creating process.

Type: Error

Add’l Info: None.

Action: None.

FMWK3008 Text: Failed to write value 0 on Entry in the registry key.

Type: Error

Add’l Info: None.

Action: None.

FMWK3009 Text: Error saving server profile.

Type: Error

Add’l Info: None.

Action: None.

FMWK3010 Text: Error updating the Active TServer entry.

Type: Error

Add’l Info: None.

Action: None.

FMWK3011 Text: Error getting server profile.

Type: Error

Add’l Info: None.

Action: None.

Error Description

December 12, 2013 139


FMWK3012 Text: Failed to write value to the registry key.

Type: Error

Add’l Info: None.

Action: None.

FMWK3013 Text: Failed to iterate registry key.

Type: Error

Add’l Info: None.

Action: None.

FMWK3014 Text: Error GetKeyValue Switch Type. Error code = <%d>, <%s>.

Type: Error

Add’l Info: None.

Action: None.

FMWK3015 Text: Error GetKeyValue CTI Type. Error code = <%d>, <%s>.

Type: Error

Add’l Info: None.

Action: None.

FMWK3016 Text: Error GetServerTypeProfile. Error code = <%d>, <%s>.

Type: Error

Add’l Info: None.

Action: None.

FMWK3017 Text: Error getting switch and CTI type.

Type: Error

Add’l Info: None.

Action: None.

Error Description

140 December 12, 2013

Error Messages

FMWK3018 Text: Could not establish open stream with definity switch.

Type: Error

Add’l Info: None.

Action: None.

FMWK3019 Text: Timeout waiting for TServer to return.

Type: Error

Add’l Info: None.

Action: None.

FMWK3020 Text: Couldn't establish definity event poll. Error code = <%d>.

Type: Error

Add’l Info: None.

Action: None.

FMWK3021 Text: Error getting GetServerIOR for Sync Server.

Type: Error

Add’l Info: None.

Action: None.

FMWK3022 Text: Corba Error. CORBA::is_nil(vDAS).

Type: Error

Add’l Info: None.

Action: None.

FMWK3023 Text: Error synchronizing directory services.

Type: Error

Add’l Info: None.

Action: None.

FMWK3024 Text: Could not update Required Admin Password.

Type: Error

Add’l Info: None.

Action: None.

Error Description

December 12, 2013 141


FMWK3025 Text: Could not set the new Admin Pwd.

Type: Error

Add’l Info: None.

Action: None.

FMWK3026 Text: Failed to load Enterprise Administrator (TSSPAdm.exe).

Type: Error

Add’l Info: None.

Action: None.

FMWK3027 Text: Failed to load Personnel.exe.

Type: Error

Add’l Info: None.

Action: None.

FMWK3028 Text: Failed to load Administrator.exe.

Type: Error

Add’l Info: None.

Action: None.

FMWK3029 Text: Failed to load IPCCAdm.exe.

Type: Error

Add’l Info: None.

Action: None.

FMWK3032 Text: Failed to load SWFAdmin.exe.

Type: Error

Add’l Info: None.

Action: None.

FMWK3033 Text: Could not add workspace for server name.

Type: Error

Add’l Info: None.

Action: None.

Error Description

142 December 12, 2013

Error Messages

FMWK3034 Text: Unexpected error reported.

Type: Error

Add’l Info: None.

Action: None.

FMWK3035 Text: Error = <%s>.

Type: Error

Add’l Info: None.

Action: None.

FMWK4000 Text: Failed to get local LCC from the registry. Error code = <%d>, <%s>.

Type: Fatal

Add’l Info: None.

Action: None.

FMWK4001 Text: AutoRecoverConnection failed ExitInstance. Error code = <%d>, <%s>.

Type: Fatal

Add’l Info: None.

Action: None.

FMWK4002 Text: Out of memory.

Type: Fatal

Add’l Info: None.

Action: None.

IPCA1000 Text: Unknown Exception.

Type: Fatal

Add’l Info: None.


IPCA1001 Text: Exception. Description = <%ls>

Type: Fatal

Add’l Info: None.

Action: Check Description.

Error Description

December 12, 2013 143


IPCA2001 Text: LDAP connection failed. Description = <%ls>.

Type: Error

Add’l Info: None.

Action: Check LDAP Server is running.

IPCA2002 Text: LdapClient API <%ls> failed. Discription = <%ls>.

Type: Error

Add’l Info: None


IPCA2003 Text: Error Obtaining License. Error: %ls

Type: Error

Add’l Info: None.

Action: Check LRM Server is running.

IPCA2004 Text: Unknown Exception.

Type: Error

Add’l Info: None.


IPCA2005 Text: Exception. Description = <%ls>

Type: Error

Add’l Info: None.

Action: Check Description.

IPCA2006 Text: Error deleting agent profile. Description = <%ls>.

Type: Error

Add’l Info: None.

Action: Check Enterprise Server is running.

IPCA2007 Text: Error loading data.

Type: Error

Add’l Info: None.


Error Description

144 December 12, 2013

Error Messages

IPCA2008 Text: Error writing data to LDAP.

Type: Error

Add’l Info: None.


IPCA2009 Text: Error notifying IPPA Server.

Type: Error

Add’l Info: None.

Action: Check IPPA Server is running.

IPCA2010 Text: Error Reading dynamic re-skilling site1 from LDAP. Error: %ls

Type: Error

Add’l Info: Error reading the dynamic reskilling site.

Action: None.

IPCA2011 Text: Error Reading dynamic re-skilling site2 from LDAP. Error: %ls

Type: Error

Add’l Info: Error reading the dynamic reskilling site.

Action: None.

IPCA2012 Text: Error Writing dynamic re-skilling site to LDAP. Error: %ls

Type: Error

Add’l Info: Error writing the dynamic reskilling site.

Action: None.

IPCA2013 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.

Error Description

December 12, 2013 145


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 Text: Caught exception in OnInitialUpdate in Agentview.

Type: Error

Add’l Info: None.

Action: None.

IPPA2000 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.

IPPA2001 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.

Error Description

146 December 12, 2013

Error Messages

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.

IPPA2003 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.

IPPA2004 Text: Agent phone IP address <%s>: Unexpected error caught: %s

Type: Error

Add’l Info: The IPPA client encountered an unexpected error.


IPPA2005 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.

Error Description

December 12, 2013 147


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.

IPPA2007 Text: Unexpected error caught: %s

Type: Error

Add’l Info: The IPPA client JSP encountered an unexpected error.


IPPA2008 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.

Error Description

148 December 12, 2013

Error Messages

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.

IPPA3001 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.

IPPA3002 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.

Error Description

December 12, 2013 149


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.

IPPA3004 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.

IPPA3005 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.


IPPA3006 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.


Error Description

150 December 12, 2013

Error Messages

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.

IPPA3008 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.

IPAC1000 Text: No arguments passed to application.

Type: Fatal

Add’l Info: No arguments were passed to application.

Action: Call application passing old IP address.

IPAC1001 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.

Error Description

December 12, 2013 151


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.

LA1001 Text: An unexpected error occurred.

Type: Fatal

Add’l Info: Encountered an unexpected error.

Action: None.

LA2000 Text: Error: <%d> <%ls>

Type: Error

Add’l Info: An exception was caught.

Action: None.

LA2001 Text: Error: <%ls>

Type: Error

Add’l Info: An exception was caught

Action: None.

LA2002 Text: Unexpected error reported.

Type: Error

Add’l Info: An unexpected error occurred.

Action: None.

LA2003 Text: Failed: <%ls> Error: <%d> <%ls>

Type: Error


Action: None.

Error Description

152 December 12, 2013

Error Messages

LA2004 Text: Error launch license url = <%ls>.

Type: Error


Action: None.

LA2005 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.

LA3000 Text: Unable to connect to process <%ls>: Error <%ls>.

Type: Warn

Add’l Info: Unable to connect to specified process.

Action: None.

LA3001 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.

LC0001 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.

LC0002 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.

Error Description

December 12, 2013 153


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.

LMS2000 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.

LMS2001 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).

LMS2002 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.

Error Description

154 December 12, 2013

Error Messages

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.

LMS2004 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.

LMS2005 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.

LMS3000 Text: The process could not be started.

Type: Warn

Add’l Info: The process could not be started.

Action: None

LMS3001 Text: The process has unexpectedly stopped running.

Type: Warn

Add’l Info: The process has unexpectedly stopped running.

Action: None

Error Description

December 12, 2013 155


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

LRMS1000 Text: The SocketService could not be started. Reason: (%ls)

Type: Fatal


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.

LRMS2000 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.

LRMS2001 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.

PD1001 Text: GetKeyValue failed. Error = <%d>

Type: Fatal

Add’l Info: None.

Action: None.

Error Description

156 December 12, 2013

Error Messages

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

PD3000 Text: Example Warn!

Type: Error

Add’l Info: Example Warn!

Action: None

PD3001 Text: Error = <%ls>.

Type: Warn

Add’l Info: Generic warn message

Action: See error text for more information.

PD4000 Text: Example Fatal!

Type: Fatal

Add’l Info: Example Fatal!

Action: None.

PI2001 Text: Error = <%ls>.

Type: Warn

Add’l Info: Generic warn Message


PI2002 Text: Unable to read registry value at key.

Type: Warn

Add’l Info: Unable to read registry value


PI2003 Text: Unable to open registry key.

Type: Warn

Add’l Info: Unable to open registry key


Error Description

December 12, 2013 157


PI2004 Text: Failed to open registry key. Error code = <%d>.

Type: Warn

Add’l Info: Failed to open registry key


PI2005 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.


PI2006 Text: SetKeyValue failed.

Type: Warn

Add’l Info: SetKeyValue failed


PI2007 Text: Failed to SetKeyValue for <%ls>.

Type: Warn

Add’l Info: Failed to SetKeyValue for


PI3001 Text: Error = <%ls>.

Type: Error

Add’l Info: Generic Error Message


PI3002 Text: Unexpected error reported.

Type: Error

Add’l Info: Unexpected error reported.

Action: Restart PostInstall

PI3003 Text: AutoRecoverConnection failed. Error code = <%d>, <%ls>.

Type: Error

Add’l Info: AutoRecoverConnection failed.

Action: Check LDAP server and try again.

Error Description

158 December 12, 2013

Error Messages

PI3004 Text: Invalid order index.

Type: Error

Add’l Info: Invalid order index

Action: Check LDAP servers and try again.

PI3005 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.

PI3006 Text: Failed to open registry key. Error code = <%d>.

Type: Error


Action: Check error text

PI3007 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


PI3008 Text: Failed to read value from the registry key. Error code = <%d>.

Type: Error

Add’l Info: Failed to write to the registry


PI3009 Text: DeleteServerProfile failed. Error = <%d>, <%ls>.

Type: Error

Add’l Info: DeleteServerProfile failed.


Error Description

December 12, 2013 159


PI3010 Text: UpdateServerTypeProfile failed. Error = <%d>, <%ls>.

Type: Error

Add’l Info: UpdateServerTypeProfile failed.


PI3011 Text: AddServerTypeProfile failed. Error = <%d>, <%ls>.

Type: Error

Add’l Info: AddServerTypeProfile failed.


PI3012 Text: SetKeyValue failed for <%ls>. Error = <%d>, <%ls>.

Type: Error

Add’l Info: SetKeyValue failed.


PI3013 Text: ServerTypeExist failed. Error = <%d>, <%ls>.

Type: Error

Add’l Info: ServerTypeExist failed.


PI3014 Text: AppExist failed. Error = <%d>, <%ls>.

Type: Error

Add’l Info: AppExist failed.


PI3015 Text: AddApp failed. Error = <%d>, <%ls>.

Type: Error

Add’l Info: AddApp failed.


PI3016 Text: SectExist failed. Error = <%d>, <%ls>.

Type: Error

Add’l Info: SectExist failed.


Error Description

160 December 12, 2013

Error Messages

PI3017 Text: AddSect failed. Error = <%d>, <%ls>.

Type: Error

Add’l Info: AddSect failed.


PI3018 Text: SetKey login failed. Error = <%d>, <%ls>.

Type: Error

Add’l Info: SetKey login failed.


PI3019 Text: SetKey pwd failed. Error = <%d>, <%ls>.

Type: Error

Add’l Info: SetKey pwd failed.


PI3020 Text: SetKey CM Version failed. Error = <%d>, <%ls>.

Type: Error

Add’l Info: SetKey CM Version failed.


PI3021 Text: Failed on GetServerProfileList. Error code = <%d>, <%ls>.

Type: Error

Add’l Info: GetServerProfileList failed.


PI3022 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.


Error Description

December 12, 2013 161


PI3023 Text: Invalid order index.

Type: Error

Add’l Info: Invalid order index.


PI3024 Text: Failed to delete registry key. Error code = <%d>.

Type: Error

Add’l Info: Failed to delete registry key


PI3028 Text: Failed to open registry key.

Type: Error



PI3029 Text: Failed to read value from the registry key.

Type: Error



PI3037 Text: GetKeyValue failed. Error = <%d>, <%ls>.

Type: Error

Add’l Info: GetKeyValue failed

Action: None.

PI3042 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.


PI3045 Text: Operation failed.

Type: Error

Add’l Info: Operation failed.

Action: None.

Error Description

162 December 12, 2013

Error Messages

PI3046 Text: Operation failed. IP = <%ls>, API Name = <%ls>, Error Code = <%d>.

Type: Error


Action: None.

PI3048 Text: Failed to write to the registry. Entry <%ls>, key <%ls>. Error code = <%d>.

Type: Error


Action: None.

PI3049 Text: Failed to remove entry <%ls>, key <%ls>. Error code = <%d>.

Type: Error


Action: None.

PI3050 Text: %ls not defined.

Type: Error


Action: None.

PI3051 Text: Base is not defined. Error = <%ls>.

Type: Error


Action: None.

PI3053 Text: failed. Error = <%d>, <%ls>.

Type: Error


Action: None.

Error Description

December 12, 2013 163


PI3054 Text: Failed to read value from the registry. Entry <%ls>, key <%ls>. Error code = <%d>.

Type: Error



PI3055 Text: LOBYTE/HIBYTE failed.

Type: Error


Action: None.

PI3056 Text: Screen list is empty.

Type: Error


Action: None.

PI3057 Text: Unexpected Switch/CTI type.

Type: Error


Action: None.

PI3058 Text: RestoreDefaultLCCdata failed.

Type: Error


Action: None.

PI3060 Text: Error in SHGetMalloc.

Type: Error


Action: None.

PI3061 Text: Error in ParseDisplayName.

Type: Error


Action: None.

Error Description

164 December 12, 2013

Error Messages

PI3062 Text: Error in SHGetPathFromIDList.

Type: Error


Action: None.

PI3063 Text: Failed to write IOR to the registry.

Type: Error


Action: None.

PI3064 Text: StartSync failed.

Type: Error


Action: None.

PI3067 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.

QMUT1000 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.

QMUT2002 Text: Error loading required DLLs. An error occurred loading required DLLs.

Type: Error

Add’l Info: None.

Action: Restart the application.

Error Description

December 12, 2013 165


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.

QMUT3000 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.

QMUT3004 Text: The account with the specified username has expired.

Type: Warn

Add’l Info: None.

Action: Verify account.

RECORD1001 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

RECORD1002 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

RECORD1004 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.

Action:

Error Description

166 December 12, 2013

Error Messages

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:

RECORD1007 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.


RECORD1008 Text: Unable to start Refresh Thread. Exiting.

Type: Fatal



RECORD1009 Text: Caught a CORBA exception changing CORBA server to ready. Exiting.

Type: Fatal


Action: Check network settings.

Error Description

December 12, 2013 167


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.

RECORD1013 Text: An exception occurred calling ORB_init(). Exiting.

Type: Fatal

Add’l Info: check network settings.

Action:

RECORD1014 Text: An exception occurred calling BOA_init(). Exiting.

Type: Fatal


Action:

RECORD1015 Text: Unable to create a Logout event. Exiting.

Type: Fatal


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:

Error Description

168 December 12, 2013

Error Messages

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 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).

RECORD2007 Text: The free disk space limit has been reached.

Type: Error


Action: Check system resource availability (disk).

RECORD2008 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.

RECORD2009 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.

Error Description

December 12, 2013 169


RECORD2010 Text: Creating the listening socket failed.

Type: Error

Add’l Info: None.

Action: None.

RECORD2011 Text: Unable to retrieve local IP address for host name

Type: Error

Add’l Info: None.

Action: None.

RECORD2012 Text: The VPN thread failed to bind to the local address.

Type: Error

Add’l Info: None.

Action: None.

RECORD2013 Text: VPN thread failed to listen to the local address.

Type: Error

Add’l Info: None.

Action: None.

RECORD2014 Text: stream (%hs): socket creation failed with code: (%hs)

Type: Error

Add’l Info: None.

Action: None.

RECORD2015 Text: stream (%hs): Socket BIND failed with code: (%hs)

Type: Error

Add’l Info: None.

Action: None.

Error Description

170 December 12, 2013

Error Messages

RECORD2016 Text: stream (%hs): Socket SELECT failed with code: (%hs)

Type: Error

Add’l Info: None.

Action: None.

RECORD2017 Text: stream (%hs): recvfrom failed with code: (%hs)

Type: Error

Add’l Info: None.

Action: None.

RECORD2018 Text: stream (%hs): Writing an RTP packet failed. Aborting recording of this stream.

Type: Error

Add’l Info: None.

Action: None.

RECORD2019 Text: stream (%hs): (%lu) packets were dropped due to the disk being slow.

Type: Error

Add’l Info: None.

Action: None.

RECORD2020 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.

RECORD2021 Text: VPN thread failed to listen to the local address.

Type: Error

Add’l Info: None.

Action: None.

Error Description

December 12, 2013 171


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.

RECORD2023 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.

RECORD3000 Text: temp file = <%hs> could not be renamed.

Type: Warn

Add’l Info: None.

Action: None.

SAW1000 Text: Unable to start Resiprocate thread. Caught an exception, exception message= <%ls>

Type: Fatal

Add’l Info: The main resiprocate Thread could not be started.

Action: None.

SAW1001 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.

SAW1002 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.

Error Description

172 December 12, 2013

Error Messages

SAW1003 Text: Adding Resiprocate message types failed. Error Code = <%ls>

Type: Fatal


Action: None.

SAW1004 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.

SAW1005 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.

SAW1006 Text: Could not login user into any of the presence Servers retrieved from GetPresenceSvrConfig().Error Code = <%ls>

Type: Fatal


Action: None.

SAW1007 Text: Starting of Notification threads failed.Error Code = <%ls>

Type: Fatal


Action: None.

Error Description

December 12, 2013 173


SAW1008 Text: GetAgentBuddyList() failed. Error Code = <%ls>

Type: Fatal


Action: None.

SAW1009 Text: GetAgentBuddiesInfo() failed.Error Code = <%ls>

Type: Fatal


Action: None.

SAW1010 Text: Unable to start Notification thread. Caught an exception, exception message = <%ls>

Type: Fatal

Add’l Info: Unable to start Notification thread.

Action: None.

SAW1011 Text: addResiprocateServerSettings failed. Error Code = <%ls>

Type: Fatal


Action: None.

SAW2000 Text: An unexpected exception occurred.

Type: Error


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.

Error Description

174 December 12, 2013

Error Messages

SAW2001 Text: Publishing of CAD Users presence state failed.

Type: Error

Add’l Info: Publishing of CAD Users presence state failed.

Action: None.

SAW2002 Text: Sending out individual Subscription messages failed. Error Code = <%ls>

Type: Error


Action: None.

SAW2003 Text: Sending out individual Subscription messages failed. Error Code = <%ls>

Type: Error


Action: None.

SAW2004 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.

SAW2005 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.

SAW2006 Text: Inserting a chat event into the external list failed. Error Code = <%ls>

Type: Error


Action: None.

Error Description

December 12, 2013 175


SAW3000 Text: The notify message does not have tag name = <%ls> .

Type: Warn

Add’l Info: None.

Action: None.

SAW3001 Text: The threads = <%ls> could not be started. Exception = <%ls>

Type: Warn

Add’l Info: The thread could not be started.

Action: None.

SAW3002 Text: Getting contacts configured on CUPS failed with error code = <%ls>

Type: Error

Add’l Info: None.

Action: None.

SL1005 Text: The Control handler could not be installed

Type: Error

Add’l Info: None.

Action: None.

SL1006 Text: Failed to install

Type: Error

Add’l Info: None.

Action: None.

SL1007 Text: Could not remove Error message

Type: Error

Add’l Info: None.

Action: None.

SL1008 Text: Invalid Arguments,

Type: Error

Add’l Info: None.

Action: Exit.

Error Description

176 December 12, 2013

Error Messages


Type: Error

Add’l Info: None.

Action: None.


Text: Error

Type: None.

Add’l Info: None.

SL2001 Text: Invalid Request.

Type: Error

Add’l Info: None.

Action: None.

SMC3000 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.

SMC3001 Text: Error getting server profile: type (%ls) msg (%ls)

Type: Error

Add’l Info: Failed to retrieve specified server profile from LDAP.


SMC3002 Text: Error getting attribute: type (%ls) attribute (%ls)

Type: Error

Add’l Info: Failed to retrieve specified attribute for specified server profile from LDAP.


Error Description

December 12, 2013 177


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.


SMC3004 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.

SMC3005 Text: Error retrieving IP from IOR: type (%ls) ior (%ls)

Type: Error

Add’l Info: Failed to retrieve ip address from ior.


SMC3006 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.

SMC3007 Text: Error retrieving list of servers: type (%ls) msg (%ls)

Type: Error

Add’l Info: Failed to retrieve ip address from ior.


SMTP2000 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.

Error Description

178 December 12, 2013

Error Messages

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.

SPLKAXL2000 Text: An unexpected exception occurred.

Type: Error

Add’l Info: None.

Action: Complete the following steps.

• 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 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.

SPLKAXL2002 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).

Error Description

December 12, 2013 179


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.

SPLKAXL2004 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).

SPLKAXL2005 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.


• 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).

Error Description

180 December 12, 2013

Error Messages

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.





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.





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.





Error Description

December 12, 2013 181


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.





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.


• Verify that the login and password specified for the CallManager AXL Interface are correct.



Error Description

182 December 12, 2013

Error Messages

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.





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.




• Check for network connectivity issues.

Error Description

December 12, 2013 183


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.




• 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.



• 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.


• Verify that LDAP Server is running.


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.




Error Description

184 December 12, 2013

Error Messages

SPLKAXL2017 Text: SplkAXL has not been initialized.

Type: Error

Add’l Info: SplkAXL being used before being initialized.




SPLKAXL2018 Text: Failed to query CallManager(%ls) Port(%d) Error(%d:%ls).

Type: Error

Add’l Info: An error occurred querying the specified CallManager.


• See text in error for more details.



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.




SPLKAXL2020 Text: Unknown CallManager version: %ls.

Type: Error

Add’l Info: The CallManager version found is not supported.




Error Description

December 12, 2013 185


SPLKAXL2021 Text: Caught a splk_std::SplkXmlException. Exception message: %ls.

Type: Error

Add’l Info: Caught a splk_std::SplkXmlException.


• Read the error message for a description.




SPLKAXL2022 Text: Caught a xercesc::XMLException. Exception message: %hs.

Type: Error

Add’l Info: Caught a xercesc::XMLException.






SPLKAXL2023 Text: Caught a xercesc::DOMException. Exception message: %hs.

Type: Error

Add’l Info: Caught a xercesc::DOMException.






Error Description

186 December 12, 2013

Error Messages

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.





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.





SPLKAXL2026 Text: There was a problem preparing CURL: %ls. Error: %hs.

Type: Error

Add’l Info: There was a problem preparing the CURL connection.





Error Description

December 12, 2013 187


SPLKAXL2027 Text: There was a problem performing the CURL action. Error: %hs.

Type: Error






SPLKAXL2028 Text: Failed to get the version from CallManager: %ls.

Type: Error





• 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.





Error Description

188 December 12, 2013

Error Messages

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.





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.



• 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.




Error Description

December 12, 2013 189


SPLKAXL3004 Text: The query return an unexpected status code: %d.

Type: Warn

Add’l Info: The query return an unexpected status code.




SPLKTSSP1000 Text: SL1000 Could not create thread.

Type: Fatal

Add’l Info: Could not create thread.

Action: Check system resource availability (memory, CPU).

SPLKTSSP1001 Text: SS1001 Unexpected error.

Type: Fatal


Action: Check the log for other errors. Check the System Event Viewer for system errors. Check system resource availability (memory, CPU).

SPLKTSSP2038 Text: Network communication error.

Type: Error

Add’l Info: Network communication error.

Action: Check network connectivity. Verify that the Enterprise Service is running.

STD1000 Text: An exception occured.

Type: Fatal

Add’l Info: An exception occured.

Action: None.

STD1001 Text: Failed to connect to LDAP.

Type: Fatal

Add’l Info: An exception occured.

Action: None.

Error Description

190 December 12, 2013

Error Messages

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.


• 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.

Error Description

December 12, 2013 191


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.

STD2003 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.

STD2004 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.

STD3000 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.

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.

Error Description

192 December 12, 2013

Error Messages

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.

STD3002 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.

STD3003 Text: Internal error: Caught unknown exception in <%ls>.

Type: Warn

Add’l Info: Caught unknown exception in specified function.


STD3004 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.


• 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.

Error Description

December 12, 2013 193


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.






STD3006 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.

STD3007 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: Check Xerces error description for further information.

Error Description

194 December 12, 2013

Error Messages

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.


STD3009 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.






Error Description

December 12, 2013 195


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.






STD3011 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.

STD3013 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.

Error Description

196 December 12, 2013

Error Messages

STORAGE1000 Text: Could not create thread (%ls).

Type: Fatal

Add’l Info: Could not create thread.

Action: Verify system resource availability (memory, CPU).

STORAGE1001 Text: Unexpected error. WaitForSingleObject failed.

Type: Fatal

Add’l Info: Unexpected error. WaitForSingleObject failed.


STORAGE1002 Text: Failed to create CompletionIOPort

Type: Fatal

Add’l Info: Failed to create IO Completion Port


STORAGE1004 Text: Unexpected exception during network communication initialization (omniORB).

Type: Fatal

Add’l Info: Unexpected error. Failed to initialize CORBA.


STORAGE1005 Text: Unrecoverable Error occured. Exiting.

Type: Fatal

Add’l Info: Unrecoverable error


STORAGE1006 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.

Error Description

December 12, 2013 197


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.

STORAGE2016 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.

STORAGE2017 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

STORAGE2018 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

Error Description

198 December 12, 2013

Error Messages

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

STORAGE2020 Text: An unexpected exception occurred.

Type: Error



STORAGE2021 Text: An unexpected exception occurred.

Type: Error



STORAGE2022 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

STORAGE2028 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.

Error Description

December 12, 2013 199


STORAGE2030 Text: Error calling PostQueuedCompletionStatus for SkillStatsThread.

Type: Error

Add’l Info: IO Completion port error.


STORAGE2034 Text: Failed to query skill group invokeid.

Type: Error

Add’l Info: Failed to query skill group from CTI Server


STORAGE2035 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).

STORAGE2050 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).

STORAGE2052 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


Error Description

200 December 12, 2013

Error Messages

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


STORAGE2054 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


STORAGE2055 Text: Failed to query skill statistics from CTI server for Skill.

Type: Error

Add’l Info: Failed to query skill stats from CTI Server


STORAGE2056 Text: Failed to set ECC Variable.

Type: Error

Add’l Info: Failed to set ECC variable


Error Description

December 12, 2013 201


STORAGE2057 Text: Failed to set call data variable.

Type: Error

Add’l Info: Failed to set Call variable


STORAGE3000 Text: Could not detach thread.

Type: Warn

Add’l Info: Could not detach thread.

Action: Check system resource availability (memory, CPU).

STORAGE3001 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.

STORAGE3002 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.

STORAGE3003 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.

Error Description

202 December 12, 2013

Error Messages

SWFA1000 Text: Unknown Exception.

Type: Fatal

Add’l Info: None.


SWFA1001 Text: Exception. Description= <%s>

Type: Fatal

Add’l Info: None.

Action: Check description.

SWFA1002 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.

SWFA1003 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.

SWFA1004 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.

SWFA1005 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.

Error Description

December 12, 2013 203


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.

SWFA1007 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.

SWFA1008 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.

SWFA1009 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.

SWFA2000 Text: LDAP Initialization failed.

Type: Error

Add’l Info: None.

Action: Check that the LDAP service is running. Check the Site Setup registry values.

Error Description

204 December 12, 2013

Error Messages

SWFA2001 Text: Ldap connection failed. Description= <%s>

Type: Error

Add’l Info: None.


SWFA2002 Text: LdapClient API <%s> failed. Description= <%s>.

Type: Error

Add’l Info: None.


SWFA2003 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.


SWFA2004 Text: Unknown Exception...

Type: Error

Add’l Info: Internal exception.


SWFA2005 Text: Exception. Description= <%s>.

Type: Error


Action: Check description.

SWFA2006 Text: Enterprise Server Client API <%s> failed. Description= <%s>.

Type: Error


Action: Check that the Enterprise service is running.

Error Description

December 12, 2013 205


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.

SWFA2008 Text: SWF <%s> might be corrupted.

Type: Error

Add’l Info: Internal error.


SWFA2009 Text: SPLK XML Parser failed encode SWF <%s> to XML.

Type: Error

Add’l Info: Internal error.


SWFA2010 Text: Error in spAutoRecoverConnection = <%hs>

Type: Error

Add’l Info: None.

Action: None.

SWFA2011 Text: spConnect failed with error = <%hs>

Type: Error

Add’l Info: None.

Action: None.

SWFA3000 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.

Error Description

206 December 12, 2013

Error Messages

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.

SYNC1001 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.

SYNC1002 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.

SYNC1003 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.

Error Description

December 12, 2013 207


SYNC1004 Text: The initialization of the Windows NT service was unsuccessful.

Type: Fatal


Action: Check the System Event Viewer for error messages related to the Sync service. Check for other error messages.

SYNC2000 Text: An unexpected exception occurred.

Type: Error


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.

SYNC2001 Text: An error occurred while synchronizing agents.

Type: Error


Action: Search the log for errors related to LDAP. Make sure that the LDAP Monitor service is up and running.

SYNC2002 Text: An error occurred while synchronizing teams.

Type: Error

Add’l Info: An error occurred while synchronizing teams.


Error Description

208 December 12, 2013

Error Messages

SYNC2003 Text: An error occurred while synchronizing queues.

Type: Error

Add’l Info: An error occurred while synchronizing queues.


SYNC2004 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.

SYNC2005 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.

SYNC2006 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.

SYNC2007 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.

SYNC2008 Text: Could not get resource description from the database.

Type: Error

Add’l Info: Could not get resource description from the database.


Error Description

December 12, 2013 209


SYNC2009 Text: Could not get CSQ list from the database.

Type: Error

Add’l Info: Could not get CSQ list from the database.


SYNC2010 Text: Could not get CSQ description from the database.

Type: Error

Add’l Info: Could not get CSQ description from the database.


SYNC2011 Text: Could not get MAC list from the database.

Type: Error

Add’l Info: Could not get MAC list from the database.


SYNC2012 Text: Failed to allocate memory for SDeviceInfo.

Type: Error

Add’l Info: Failed to allocate memory for SDeviceInfo.


SYNC2013 Text: Failed to get periodic synchronization object.

Type: Error

Add’l Info: Failed to get periodic synchronization object.

Action: Search for other error messages.

SYNC2015 Text: Caught sync_server_exception: %ls.

Type: Error

Add’l Info: Caught sync_server_exception.

Action: Read exception description.

SYNC2016 Text: Caught std::exception: %hs.

Type: Error

Add’l Info: Caught exception.

Action: Read exception description.

Error Description

210 December 12, 2013

Error Messages

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.

SYNC2018 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.

SYNC2019 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).

SYNC2020 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.

SYNC2021 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.

Error Description

December 12, 2013 211


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.

SYNC2023 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.

SYNC2024 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.

SYNC2025 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.

SYNC2026 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).

Error Description

212 December 12, 2013

Error Messages

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.

SYNC2028 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.

SYNC2029 Text: An unexpected exception occurred when initializing the Sync service.

Type: Error

Add’l Info: An unexpected exception occurred when initializing the Sync service.


SYNC2030 Text: The Windows NT service was not removed successfully.

Type: Error

Add’l Info: The Windows NT service was not removed successfully.


SYNC2031 Text: An error occurred during synchronization of reason codes.

Type: Error

Add’l Info: An error occurred during synchronization of reason codes.


Error Description

December 12, 2013 213


SYNC2032 Text: Failed to allocate memory for SSQL object.

Type: Error

Add’l Info: Failed to allocate memory for SSQL object.


SYNC2033 Text: Agent (%ls) not found in LDAP map.

Type: Error

Add’l Info: Agent not found in LDAP map.


SYNC3000 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.

SYNC3001 Text: Could not add agent to LDAP: %ls.

Type: Warn

Add’l Info: Could not add agent to LDAP.


SYNC3002 Text: Could not add supervisor to LDAP: %ls.

Type: Warn

Add’l Info: Could not add supervisor to LDAP.


SYNC3003 Text: Could not update agent in LDAP: %ls.

Type: Warn

Add’l Info: Could not update agent in LDAP.


Error Description

214 December 12, 2013

Error Messages

SYNC3004 Text: Could not delete supervisor from LDAP: %ls.

Type: Warn

Add’l Info: Could not delete supervisor from LDAP.


SYNC3005 Text: Could not update team in LDAP: %ls.

Type: Warn

Add’l Info: Could not update team in LDAP.


SYNC3006 Text: Could not add team to LDAP: %ls.

Type: Warn

Add’l Info: Could not add team to LDAP.


SYNC3007 Text: Could not delete team from LDAP: %ls.

Type: Warn

Add’l Info: Could not delete team from LDAP.


SYNC3008 Text: Could not delete skill from LDAP: %ls.

Type: Warn

Add’l Info: Could not delete skill from LDAP.


SYNC3009 Text: Could not add skill to LDAP: %ls.

Type: Warn

Add’l Info: Could not add skill to LDAP.


Error Description

December 12, 2013 215


SYNC3010 Text: Could not update skill in LDAP: %ls.

Type: Warn

Add’l Info: Could not update skill in LDAP.


SYNC3011 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.

SYNC3012 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.

SYNC3013 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.


SYNC3014 Text: Could not get CSQ list from the database.

Type: Warn

Add’l Info: Could not get CSQ list from the database.


Error Description

216 December 12, 2013

Error Messages

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).

SYNC3016 Text: Failed to reset synchronizer.

Type: Warn

Add’l Info: Failed to reset synchronizer.

Action: Search the log for LDAP related errors.

SYNC3017 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.

SYNC3018 Text: The peripheral not expected, returned peripheral <%ls> already exists.

Type: Warn

Add’l Info: The peripheral not expected.


SYNC3019 Text: ResetLog failed error<%ls>.

Type: Warn

Add’l Info: ResetLog failed.


SYNC3020 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

Error Description

December 12, 2013 217


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

SYNC3022 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.

SYNC3023 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.

SYNC3024 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.

Error Description

218 December 12, 2013

Error Messages

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).

SYNC3026 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.


SYNC3027 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.


SYNC3028 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.


Error Description

December 12, 2013 219


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.


SYNC3030 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.

SYNC3031 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.

SYNC3032 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.

SYNC3033 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.

Error Description

220 December 12, 2013

Error Messages

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.

SYNC3035 Text: There is insufficient memory to handle the ODBC statement.

Type: Warn

Add’l Info: There is insufficient memory to handle the ODBC statement.


SYNC3036 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.


SYNC3037 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.


Error Description

December 12, 2013 221


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.


SYNC3039 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.


SYNC3040 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.


SYNC3041 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.


SYNC3042 Text: Failed to add CallManager(%ls) to LDAP. Error: <%d>, <%ls>.

Type: Warn

Add’l Info: Failed to add Unified CM to LDAP.


Error Description

222 December 12, 2013

Error Messages

SYNC3043 Text: Failed to update CallManager(%ls) in LDAP. Error: <%d>, <%ls>.

Type: Warn

Add’l Info: Failed to update Unified CM in LDAP.


SYNC3044 Text: Failed to remove CallManager(%ls) from LDAP. Error: <%d>, <%ls>.

Type: Warn

Add’l Info: Failed to remove Unified CM from LDAP.


SYNC3045 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.

SYNC3046 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.

VOIP2000 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.

Error Description

December 12, 2013 223


VOIP2001 Text: Could not create a necessary object [Shutdown event].

Type: Error

Add’l Info: Shutdown event.


VOIP2002 Text: Could not create a necessary object [LDAP Up/Down event].

Type: Error

Add’l Info: LDAP Up/Down event.


VOIP2003 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.

VOIP2005 Text: Could not find the IOR Hostname entry in the Registry.

Type: Error

Add’l Info: IOR Hostname entry in the Registry not available.


VOIP2007 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.

Error Description

224 December 12, 2013

Error Messages

VOIP2008 Text: Could not create a necessary process [Desktop Monitoring initialization thread].

Type: Error

Add’l Info: Desktop Monitoring initialization thread not created.


VOIP2009 Text: Could not create a necessary object [CDesktopMonitor object].

Type: Error

Add’l Info: CDesktopMonitor object not created.


VOIP2010 Text: Could not create a necessary object [CFCDMMonitorServerList object].

Type: Error

Add’l Info: CFCDMMonitorServerList object not created.


VOIP2011 Text: Could not create a necessary process [Corba listening thread].

Type: Error

Add’l Info: Corba listening thread not available.


VOIP2012 Text: Could not create a necessary object [CFCDMCritSection object].

Type: Error

Add’l Info: CFCDMCritSection object not available.


Error Description

December 12, 2013 225


VOIP2013 Text: Could not create a necessary object [CFCDMSniffer object].

Type: Error

Add’l Info: CFCDMSniffer object not available.


VOIP2014 Text: Could not create a necessary process [Periodic Cleanup thread].

Type: Error

Add’l Info: Periodic Cleanup thread creation failed.


VOIP2015 Text: Could not create a necessary process [LDAP Connection Monitoring thread].

Type: Error

Add’l Info: LDAP Connection Monitoring thread creation failed.


VOIP2016 Text: Could not create a necessary object [Logout event].

Type: Error

Add’l Info: Logout event creation failed.


VOIP2017 Text: Could not create a necessary process [Login thread].

Type: Error

Add’l Info: Login thread creation failed.


Error Description

226 December 12, 2013

Error Messages

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.

VOIP2021 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.

VOIP2023 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.

VOIP2033 Text: Could not create a necessary object [Sniffing event].

Type: Error

Add’l Info: Sniffing event object creation error.


VOIP2034 Text: Could not create a necessary object [Sniffer session shutdown event].

Type: Error

Add’l Info: Sniffer session shutdown event object creation error.


VOIP2035 Text: Could not create a necessary process [SnifferSession thread].

Type: Error

Add’l Info: SnifferSession thread creation error.


Error Description

December 12, 2013 227


VOIP2036 Text: Process ended prematurely [Sniffer Session thread].

Type: Error

Add’l Info: Sniffer Session thread termination.


VOIP2037 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.

VOIP2038 Text: Unable to get network information for the adapter.

Type: Error

Add’l Info: Network information not available.


VOIP2039 Text: Unable to set the sniffing filter.

Type: Error

Add’l Info: Error while setting the sniffing filter.


VOIP2041 Text: No packets captured for [%lu] seconds.

Type: Error

Add’l Info: Error receiving packets.


VOIP2046 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.

Error Description

228 December 12, 2013

Error Messages

VOIP2048 Text: Could not get the MAC address for extension [%hs] from the CallManager database.

Type: Error

Add’l Info: MAC Address not found.


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 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.


VOIP2050 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.

Error Description

December 12, 2013 229


VOIP2051 Text: System error. Unable to start a necessary process: [Periodic Cleanup thread].

Type: Error

Add’l Info: Process creation failed.


VOIP2052 Text: System error. Unable to start a necessary process: [LRM thread].

Type: Error

Add’l Info: LRM thread creation failed.


VOIP2053 Text: System error. Unable to start a necessary process: [VPN thread].

Type: Error

Add’l Info: VPN thread creation failed.


VOIP2054 Text: System error. Unable to start a necessary process: [Corba thread].

Type: Error

Add’l Info: Corba thread creation failed.


VOIP2055 Text: Unable to open the NIC adapter [%ls] for sniffing.

Type: Error

Add’l Info: NIC adapter opening failed.


Error Description

230 December 12, 2013

Error Messages

VOIP2056 Text: System error. The NIC adapter used for sniffing is not configured correctly.

Type: Error

Add’l Info: NIC adapter not configured correctly .


VOIP2057 Text: System error. The filter used for capturing voice streams could not be set.

Type: Error

Add’l Info: Error while setting the filter.


VOIP2061 Text: System error. Unable to start a necessary process: [LDAP Monitor thread].

Type: Error

Add’l Info: LDAP Monitor thread creation failed.


VOIP2062 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.

VOIP2063 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.

Error Description

December 12, 2013 231


VOIP2064 Text: All ODBC's have been unsuccessful.

Type: Error

Add’l Info: ODBCs failed.

Action: Verify that the Unified CM database is running.

VOIP2065 Text: Could not determine the local IP address. Error: [%hs]. (OmniOrbUseHostName invalid).

Type: Error

Add’l Info: OmniOrbUseHostName invalid.

Action: Contact TAC for assistance.

VOIP2066 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.

VOIP2067 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.

VOIP2068 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.

VOIP2069 Text: Unable to monitor agent with VoIP Monitor server [%hs]. Corba exception [%hs] returned.

Type: Error


Action: Restart.

Error Description

232 December 12, 2013

Error Messages

VOIP2070 Text: Unable to monitor agent with VoIP Monitor server [%hs]. Unknown Corba exception returned.

Type: Error


Action: Restart.

VOIP2071 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.

VOIP2072 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


Action: Restart.

VOIP2073 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


Action: Restart.

VOIP2074 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.

Error Description

December 12, 2013 233


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.

VOIP2076 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.

VOIP2077 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.

VOIP2079 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.

VOIP2080 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.

Error Description

234 December 12, 2013

Error Messages

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.

VOIP2082 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.

VOIP2083 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.

VOIP2084 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.

VOIP2085 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.


Error Description

December 12, 2013 235


VOIP2086 Text: Unable to record the agent with rtpAddress [%hs] using the VoIP Monitor service [%hs]. Unknown Corba exception returned.

Type: Error



VOIP2087 Text: Unable to stop the recording session. The VoIP Monitor service [%hs] was not found.

Type: Error



VOIP2088 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.


VOIP2089 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.


VOIP2090 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.


Error Description

236 December 12, 2013

Error Messages

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.


VOIP2092 Text: Invalid connection information for the VoIP service [%hs].

Type: Error

Add’l Info: Unable to get connection information for the VoIP Monitor service.


VOIP2093 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.


VOIP2095 Text: Unable to get the VPN IP address from a VoIP service.

Type: Error

Add’l Info: Unable to get the VPN IP address.


VOIP2096 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.

Error Description

December 12, 2013 237


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.


VOIP2098 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.

VOIP2099 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.

VOIP2100 Text: Invalid connection information for the VoIP service [%hs].

Type: Error

Add’l Info: Invalid connection information for the VoIP Monitor service.


VOIP2101 Text: Unable to initialize the Corba connection for VoIP service [%ls].

Type: Error

Add’l Info: Unable to initialize the Corba connection.


Error Description

238 December 12, 2013

Error Messages

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.

VOIP2103 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.

VOIP2104 Text: Failed to start <%ls> thread.

Type: Error

Add’l Info: Failed to start thread.

Action: Check the system resources (memory & handles) and restart.

VOIP2106 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.

VOIP2107 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.

Error Description

December 12, 2013 239


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.

VOIP2109 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.

VOIP3001 Text: System error. Failed to create socket for VPN service. Error: [%hs].

Type: Warn

Add’l Info: Failed to create socket for VPN service.


VOIP3002 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.


VOIP3003 Text: Could not create the LDAP recovery thread.

Type: Warn

Add’l Info: Could not create the LDAP recovery thread.


VOIP3004 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.

Error Description

240 December 12, 2013

Error Messages

WAL1106 Text: Out of memory.

Type: Fatal


Action: None.

WAL2001 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.

WAL2002 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.

WAL2003 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.

WAL2004 Text: GetHostname returned Local host loopback.

Type: Error

Add’l Info: SplkSocket returned Loopback address

Action: Check network connections

WAL2005 Text: SetKey login failed. Error = <%d>, <%ls>.

Type: Error

Add’l Info: SetKey login failed.


Error Description

December 12, 2013 241


WAL2006 Text: SetKey pwd failed. Error = <%d>, <%ls>.

Type: Error

Add’l Info: SetKey pwd failed.


WAL2007 Text: Error Reading NIC Adapters

Type: Error

Add’l Info: Error Reading NIC Adapters

Action: Check Splk Socket information.

WAL2008 Text: At least one error occurred during the synchronization process.

Type: Error

Add’l Info: None.

Action: None.

WAL2009 Text: Could not connect to Directory Services Synchronize Server.

Type: Error

Add’l Info: None.

Action: None.

WAL2010 Text: Could not convert from CORBAwstring to wstring.

Type: Error

Add’l Info: Could not convert from CORBAwstring to wstring

Action: Retry manual sync.

WAL2222 Text: Corba Error. CORBA::is_nil(vDAS).

Type: Error

Add’l Info: None.

Action: None.

WAL2223 Text: Error synchronizing directory services.

Type: Error

Add’l Info: Error synchronizing directory services.


Error Description

242 December 12, 2013

Error Messages

WAL2224 Text: Error notifying IPPA of Login method change.

Type: Error

Add’l Info: Error notifying IPPA of Login method change.

Action: Restart IPPA.

WAL2237 Text: Error getting GetServerIOR for Sync Server.

Type: Error

Add’l Info: Error getting GetServerIOR for Sync Server.


Error Description

December 12, 2013 243


244 December 12, 2013

cisco cad error code dictionary cad error code dictionary 4 december 12, 2013 acda3000 text: unable...

Documents