Error Message
AEResponderAlarmCatalog- 4 -PlatformAdminAccountLocked : A user attempted too many incorrect authentications and the corresponding account was locked by the platform. User ID [String] Unlock Time [String] Failed Login Count [String]

Explanation A user repeatedly attempted to login using invalid credentials and the platform locked the user account when the user exhausted the number of allowed login attempts as specified by the FailedLoginCount shown in this alarm. The account remains locked until the number of seconds specified in the UnlockTime elapses.

Recommended Action Investigate why the user may have been attempting to login using invalid credentials to determine if the account lockout was the result of forgotten credentials or some other reason.

Error Message
AuditLogCatalog- 6 -AdministrativeEvent : Audit Event is generated by this application . UserID [String] ClientAddress [String] Severity [String] EventType [String] ResourceAccessed [String] EventStatus [String] AuditDetails [String] ComponentID [String] CompulsoryEvent [String] AuditCategory [String]

Explanation Failed to write into the primary file path.

Recommended Action Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.

Error Message
AuditLogCatalog- 6 -SecurityEvent : Audit Event is generated by this application . UserID [String] ClientAddress [String] Severity [String] EventType [String] ResourceAccessed [String] EventStatus [String] AuditDetails [String] ComponentID [String] CompulsoryEvent [String] AuditCategory [String]

Explanation Failed to write into the primary file path.

Recommended Action Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.

Error Message
AuditLogCatalog- 6 -CriticalEvent : Audit Event is generated by this application . UserID [String] ClientAddress [String] Severity [String] EventType [String] ResourceAccessed [String] EventStatus [String] AuditDetails [String] ComponentID [String] CompulsoryEvent [String] AuditCategory [String]

Explanation Failed to write into the primary file path.

Recommended Action Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.

Error Message
BIPPALibrary- 1 -BIPPA1000 : Unable to create CORBA service for the BIPPA service to receive requests from IP Phone Agent clients.. Service Name [String] error Id [String] Message [String]

Explanation The SocketService could not be started.

Recommended Action Restart the BIPPA service. If the error persists, contact technical support.

Error Message
BIPPALibrary- 1 -BIPPA1001 : Unable to create TCP socket listener for the BIPPA service to receive requests from CAD-BE clients.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart the BIPPA service. Check if another instance of BIPPA service is already running. If so, stop it or don't start a second instance. Check if another service is using the same socket port (3014) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
BIPPALibrary- 1 -BIPPA1002 : TCP socket dispatcher in BIPPA service for receiving requests from CAD-BE clients failed to run.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart the BIPPA service. Check if another instance of BIPPA service is already running. If so, stop it or don't start a second instance. Check if another service is using the same socket port (3014) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
BIPPALibrary- 1 -BIPPA1003 : TCP socket listener used for receiving requests from CAD-BE clients could not be added to BIPPA socket dispatcher.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart the BIPPA service. Check if another instance of BIPPA service is already running. If so, stop it or don't start a second instance. Check if another service is using the same socket port (3014) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
BIPPALibrary- 3 -BIPPA2000 : An error occurred while performing specified action.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
BIPPALibrary- 3 -BIPPA2001 : An error occurred while setting up communication with the LRM service.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
BIPPALibrary- 3 -BIPPA2002 : An error occurred while registering with the LRM service for BIPPA events.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
BIPPALibrary- 3 -BIPPA2003 : Could not open the BIPPA service information file used by the IPPA JSP client and CAD-BE to communicate with the BIPPA service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the registry to see if the /HKLM/SOFTWARE/Spanlink/CAD/IPPA/Config/TOMCAT HOME registry value is the location of the Tomcat directory. By default, it is set to the folder C:\Program Files\Cisco\Desktop\Tomcat\ for UCCE and C:\Program Files\wfavvid\tomcat_appadmin\ for UCCX. Ensure the directory exists. Check the registry to see if the /HKLM/SOFTWARE/Spanlink/CAD/Site Setup/Install Directory registry value is the location of CAD software. By default, it is C:\Program Files\Cisco\Desktop\. 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 Message
BIPPALibrary- 3 -BIPPA2004 : The BIPPA service was unable to change its process priority to high because of the specified Windows error.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
BIPPALibrary- 3 -BIPPA2005 : An error occurred while registering with the LRM service for LRM events.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
BIPPALibrary- 3 -BIPPA2006 : An error occurred while registering BIPPA service with the LRM service.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
BIPPALibrary- 3 -BIPPA2007 : The machine running the BIPPA service ran out of available memory.. Service Name [String] error Id [String] Message [String]

Explanation .

Recommended Action Stop unnecessary processes on the machine. Restart the BIPPA service. Run a memory check. See "Memory Check" on page 206. Add more memory to the machine.

Error Message
BIPPALibrary- 3 -BIPPA2008 : There is no default configuration for specified toolbar type.. Service Name [String] error Id [String] Message [String]

Explanation The SocketService could not be started.

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

Error Message
BIPPALibrary- 3 -BIPPA2009 : BIPPA service could not obtain license from LRM service because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
BIPPALibrary- 3 -BIPPA2010 : BIPPA service could not accept connection because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the CAD-BE client terminated the connection. If so, it is not a problem. Restart the BIPPA service. Check if another instance of BIPPA service is already running. If so, stop it or don't start a second instance. Check if another service is using the same socket port (3014) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
BIPPALibrary- 3 -BIPPA2011 : BIPPA service could not initialize socket connection from client because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the CAD-BE client terminated the connection. If so, it is not a problem. Restart the BIPPA service. Check if another instance of BIPPA service is already running. If so, stop it or don't start a second instance. Check if another service is using the same socket port (3014) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
BIPPALibrary- 3 -BIPPA2012 : Specified thread could not be started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the machine is low on memory. Stop unnecessary processes on the machine. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
BIPPALibrary- 3 -BIPPA2013 : A waitable event is invalid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the machine is low on memory. Stop unnecessary processes on the machine. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
BIPPALibrary- 3 -BIPPA2014 : CTI service is not available.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Nothing needs to be done if CTI service fails over successfully or was shutdown intentionally. Restart CTI service if it is not running. If CTI service is running, run Network Checks specified in Troubleshooting manual to determine why BIPPA service computer could not reach CTI service computer. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
BIPPALibrary- 3 -BIPPA2015 : The CORBA connection information for the BIPPA service obtained from LRM service is invalid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure BIPPA service is running and active. Run Network Checks specified in Troubleshooting manual to ensure BIPPA service is reachable from client computer. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
BIPPALibrary- 3 -BIPPA2016 : BIPPA service failed to get switch type from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure LDAP service is running and active. Run Network Checks specified in Troubleshooting manual to ensure LDAP service is reachable from BIPPA service computer. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
BIPPALibrary- 3 -BIPPA2017 : Client socket descriptor is invalid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart the BIPPA service. If the error persists, contact technical support.

Error Message
BIPPALibrary- 3 -BIPPA2018 : Specified thread could not be stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the machine is low on memory. Stop unnecessary processes on the machine. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
BIPPALibrary- 4 -BIPPA3000 : Unable to allocate memory.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
BIPPALibrary- 4 -BIPPA3001 : Unable to initialize preferences watcher. BIPPA service is unable to detect changes to preferences.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure that the user that the BIPPA service is running as has permission to read from registry. Restart the BIPPA service. If this does not correct the problem, contact technical support.

Error Message
BIPPALibrary- 4 -BIPPA3002 : Unable to check preferences for local IP address BIPPA should use to create its CORBA service. It will try again every 10 seconds.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure that the user that the BIPPA service is running as has permission to read from registry. Restart the BIPPA service. If this does not correct the problem, contact technical support.

Error Message
BIPPALibrary- 4 -BIPPA3003 : Unable to get local IP address BIPPA should use to create its CORBA service from registry.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure that the user that the BIPPA service is running as has permission to read from registry. Restart the BIPPA service. If this does not correct the problem, contact technical support.

Error Message
BIPPALibrary- 4 -BIPPA3004 : Unable to enable NT Event logging for specified application name.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure that the user that the BIPPA service is running as has permission to read from registry. Restart the BIPPA service. If this does not correct the problem, contact technical support.

Error Message
BIPPALibrary- 4 -BIPPA3005 : The BIPPA service cannot communicate with the Directory Services server or the data was not found in Directory Services.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Nothing needs to be done if the data type is marked as optional. Default values will be used. Verify that the Directory Services server is running. If not, start it. (UCCE only) Verify that Directory Services has been populated using CAD Configuration Setup. Restart Directory Services. Restart BIPPA service. Verify the data exists in LDAP. If the data does not exist, it might need to be added using the Sync service (for agent and team information), Cisco Desktop Administrator (for workgroup and other settings), from previous backups/upgrades, or reinstall CAD. If this does not correct the problem, contact technical support.

Error Message
BIPPALibrary- 4 -BIPPA3006 : Specified icon file has unknown file format.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Action: Do the following: Ensure the file is an ICO or PNG file. Reload or replace icon file if needed. If this does not correct the problem, contact technical support.

Error Message
BIPPALibrary- 4 -BIPPA3007 : Unable to load icon file with specified format and size.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure the file is an ICO file. Ensure the file has an icon of specified size. Reload or replace icon file if needed. If this does not correct the problem, contact technical support.

Error Message
BIPPALibrary- 4 -BIPPA3008 : Unable to convert ICO icon with at specified index into PNG icon.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the file is an ICO file. Ensure the file has an icon at specified index. Reload or replace icon file if needed. If this does not correct the problem, contact technical support.

Error Message
BIPPALibrary- 4 -BIPPA3009 : Unable to read specified file.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the file exists. Ensure the file is readable by user BIPPA service is running as. Restart BIPPA service.

Error Message
BIPPALibrary- 4 -BIPPA3010 : Specified PNG icon file is empty.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Reload or replace PNG icon with non empty icon file.

Error Message
BIPPALibrary- 4 -BIPPA3011 : Unable to write specified file.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the directory exists. Ensure the file/directory is writable by user BIPPA service is running as. Restart BIPPA service.

Error Message
BIPPALibrary- 4 -BIPPA3012 : Unable to convert ICO icon to large PNG icon.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the file is an ICO file. Ensure the file has a small image in index 0 and large image in index 1. Reload or replace icon file if needed. If this does not correct the problem, contact technical support.

Error Message
BIPPALibrary- 4 -BIPPA3013 : There are no more licenses available.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: 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 minutes 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.

Error Message
BIPPALibrary- 4 -BIPPA3014 : 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.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the file exists. If this does not correct the problem, contact technical support.

Error Message
BIPPALibrary- 4 -BIPPA3015 : Unable to send specified CTI action to CTI service for specified agent/extension because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the CTI service is running, active, and reachable from BIPPA service computer. Check that the CTI service is a supported version for this version of BIPPA service. If this does not correct the problem, contact technical support.

Error Message
BIPPALibrary- 4 -BIPPA3016 : The IDs of response to CTI request do not match for specified agent ID/extension.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Retry CTI action to see if it happens again. Restart BIPPA service. If this does not correct the problem, contact technical support.

Error Message
BIPPALibrary- 4 -BIPPA3017 : Specified CTI action failed for specified agent ID/extension because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Check the error code and description for cause of problem.

Error Message
BIPPALibrary- 4 -BIPPA3018 : The maximum conference parties has been reached for specified agent extension.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Increase the maximum number of conference parties allowed for the extension. Do not attempt to conference more than maximum conference parties allowed.

Error Message
BIPPALibrary- 4 -BIPPA3019 : BIPPA client unable to communicate with BIPPA service because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure BIPPA service is running and active. Run Network Checks specified in Troubleshooting manual to ensure BIPPA service is reachable from client computer. Restart BIPPA service, wait until it is running and active before restarting BIPPA client.

Error Message
BIPPALibrary- 4 -BIPPA3020 : BIPPA client unable to communicate with BIPPA service because they are of different version.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action The client has to shutdown and restart again.

Error Message
BIPPALibrary- 4 -BIPPA3021 : BIPPA service could not get all the changed LDAP data from a replicated LDAP service before timeout (20 seconds) occurred.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify LDAP replication is working. Restart BIPPA service.

Error Message
BIPPALibrary- 4 -BIPPA3022 : BIPPA service is not using IOR hostname from registry because it is empty... Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify LDAP replication is working. Restart BIPPA service.

Error Message
BIPPALibrary- 6 -BIPPA0000 : BIPPA service is starting.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0001 : LRM service on specified host and port became inactive.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0002 : LRM service on specified host and port became active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0003 : BIPPA service on specified host and IOR became inactive.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0004 : BIPPA service on specified host and IOR became active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0005 : BIPPA service on this computer became active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0006 : BIPPA service on this computer became inactive.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0007 : BIPPA service is reloading LDAP information after reconnecting to LDAP service after LDAP service came up.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0008 : BIPPA service has lost connection to LDAP service. It will automatically attempt to recover connection to LDAP service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0009 : Specifies language used at this site obtained from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0010 : Specifies language used at this site obtained from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0011 : Specifies switch type used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0012 : Specifies default CCM version used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0013 : Specifies default CCM port used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0014 : Specifies CCM IP address and version used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0015 : Specifies CCM authentication URL used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0016 : Specifies BIPPA service information file used by IPPA JSP client and CAD-BE.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0017 : BIPPA service is waiting for post install to populate LDAP before BIPPA service can complete its startup.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0018 : BIPPA service is aborting initialization because shutdown was called.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0019 : Indicates post install has populated LDAP so BIPPA service can continue its startup.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0020 : BIPPA service is waiting for IOR hostname to be populated in registry before BIPPA service can complete its startup.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0021 : Specifies IOR hostname obtained from registry that will be used to create BIPPA CORBA service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0022 : BIPPA service is not using IOR hostname from registry because it is empty.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0023 : Specifies CORBA IOR for BIPPA CORBA service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0024 : BIPPA service is shutting down.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0025 : BIPPA service received specified console control event.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0026 : BIPPA service could not set console event handler.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0027 : BIPPA service created specified object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0028 : BIPPA service destroyed specified object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0029 : Specified object was not initialized.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0030 : BIPPA service initialized specified object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0031 : BIPPA service shutdown specified object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0033 : Specified interface/service became available.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0034 : Specified interface/service became unavailable.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0035 : Specified thread has started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0036 : Specified thread has stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0037 : There is no Enterprise data for this call.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0038 : BIPPA service is stopped. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0039 : BIPPA socket service has shut down.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0040 : Specified CTI action timed out for specified agent ID/extension while waiting for response from CTI service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action This may happen ocasionly under heavy load. Agent can retry action again. If this happens often, run Basic Checks, CPU Checks and Memory Checks specified in Troubleshooting manual.

Error Message
BIPPALibrary- 6 -BIPPA0041 : Specified agent has already logged in.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check whether agent is logged in via a different interface. If so, logout from the other interface or do a force login from current interface. A BIPPA service or CTI service component may have stopped or restarted while an agent is logged in such that BIPPA service thinks the agent is not logged in when agent is still logged into the CTI service. In this case, do a force login.

Error Message
BIPPALibrary- 6 -BIPPA0042 : Specified agent could not change to desired state from current state.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check whether desired state is one that can be changed to from current state. If not, no action is needed. If it fails again, log the agent out and then back in, and then try again. Verify that the CTI service is running and active. If the error continues to occur, restart the CTI and IPPA services and try again. If the error persists, open a TAC case.

Error Message
BIPPALibrary- 6 -BIPPA0043 : Agent is unable to change state because the extension is incorrect or used by another agent.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check whether the extension entered is correct. Check whether another agent is using the extension.

Error Message
BIPPALibrary- 6 -BIPPA0044 : Agent is unable to change state because the extension is not configured correctly on Call Manager.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check whether the extension exists in Call Manager. Check whether the extension is configured correctly in Call Manager.

Error Message
BIPPALibrary- 6 -BIPPA0045 : Client connected to BIPPA service at specified host using specified IOR.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0046 : Specifies product offering used by BIPPA service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
BIPPALibrary- 6 -BIPPA0047 : CadBERequestHandlerFactory is now using specified connection session info.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CadAcmiClient- 3 -CACMI2000 : CadAcmiClient is unable to initialize LRM manager for connecting to LRM service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Fill me once new LRMClient is available.

Error Message
CadAcmiClient- 3 -CACMI2001 : CadAcmiClient is unable to register with LRM service for CRS CTI events.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify LRM service is running and active. Perform network checks.

Error Message
CadAcmiClient- 4 -CACMI3000 : CadAcmiClient is unable to get specified information from LDAP service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if LDAP service is running. Check whether specified information exists in LDAP.

Error Message
CadAcmiClient- 4 -CACMI3001 : CadAcmiClient is unable to get specified information for specified host of specified service type from LDAP service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if LDAP service is running. Check whether specified information exists in LDAP.

Error Message
CadAcmiClient- 4 -CACMI3002 : There are no host defined for ACMI services in LDAP service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if LDAP service is running. Check whether specified information exists in LDAP.

Error Message
CadAcmiClient- 6 -CACMI0000 : CadAcmiClient is unable to get specified information from LDAP service and will use default values.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if LDAP service is running. Check whether specified information exists in LDAP.

Error Message
CADLRMServer- 1 -CADLRMS1000 : The SocketService could not be started.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
CADLRMServer- 1 -CADLRMS1001 : Could not create master selection strategy.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify host addresses in site setup.

Error Message
CADLRMServer- 3 -CADLRMS2001 : The CADLRM Service could not write the offering to TUP.ini.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that TUP.ini is in the correct location and that LRMServer has write permissions.

Error Message
CADLRMServer- 3 -CADLRMS2002 : The CADLRM Service could not get the Recording license limits from CRS.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that Recording licenses are configured and that LRM has access to CRS.

Error Message
CADLRMServer- 3 -CADLRMS2004 : The CADLRM Service could not write the offering to LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that Default Data in LDAP is populated and LRMServer is connected to LDAP.

Error Message
CADLRMServer- 3 -CADLRMS2005 : A service failed too many times and a manual failover was initiated.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check status of failed service.

Error Message
CADLRMServer- 4 -CADLRMS3000 : CADLRM Service could not write the server profile information to LDAP. Clients may not be able to connect.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that LDAP is running and that LRM can write to it.

Error Message
CADLRMServer- 6 -CADLRMS0000 : The socket service has been started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CADLRMServer- 6 -CADLRMS0001 : The socket service has been stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CADLRMServer- 6 -CADLRMS0002 : The CADLRM Service has become active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CADLRMServer- 6 -CADLRMS0003 : The CADLRM Service has become inactive.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CADLRM- 3 -CADLRM2000 : The CADLRM Client could not get a list of LRM server profiles from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that LRM Server is running. Check that LDAP is up and replication is working correcly. Check that the client can connect to LDAP. Check that the ServerProfile entries are located in LDAP.

Error Message
CADLRM- 3 -CADLRM2003 : The CADLRM Client could not find an LRM Server to connect to.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that LRM Server is running. Check that LDAP is up and replication is working correcly. Check that the client can connect to LDAP. Check that the ServerProfile entries are located in LDAP. Check that LDAP Hosts are configured correctly.

Error Message
CADLRM- 3 -CADLRM2006 : The CADLRM Service could not get a list of server profiles from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that LRM Server is running. Check that LDAP is up and replication is working correcly. Check that the client can connect to LDAP. Check that the ServerProfile entries are located in LDAP.

Error Message
CadSplkStd- 6 -CADSTD0000 : .. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CallManager- 2 -CallManagerFailure : Indicates an internal failure in Unified CM. Additional Text [String] Host Name of Hosting Node [String] Host Node IP Address [String] Reason code [Enum]

Explanation This alarm indicates that an internal failure occurred in the Cisco CallManager service. The service should restart in an attempt to clear the failure.

Recommended Action Monitor for other alarms and restart Cisco CallManager service, if necessary. Collect the core file if available, SDL and CCM/SDI trace files (you can gather these from Trace and Log Central in RTMT using the Collect Files feature) and contact the Cisco Technical Assistance Center (TAC).

Reason code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Unknown - Unified CM has failed for an unknown reason
2 HeartBeatStopped - An internal heart beat has stopped after the preceding heart beat interval
3 RouterThreadDied - An internal thread has failed
4 TimerThreadDied - An internal thread has failed
5 CriticalThreadDied - An internal thread has failed
Error Message
CallManager- 5 -SDLLinkISV : SDL link to remote application restored. Remote Application IP Address [String] Unique Link ID [String] Local Node ID [UInt] Local Application ID [Enum] Remote Node ID [UInt] Remote Application ID [Enum]

Explanation This alarm indicates that the local Unified CM has gained communication with the remote Unified CM. Note that the remote Unified CM should also indicate SDLLinkISV with a different LinkID.

Recommended Action Informational only; no action is required

Local Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
100 CallManager
Remote Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
100 CallManager
Error Message
CallManager- 1 -SDLLinkOOS : SDL link to remote application is out of service. Remote Application IP Address [String] Unique Link ID [String] Local Node ID [UInt] Local Application ID [Enum] Remote Node ID [UInt] Remote Application ID [Enum]

Explanation This alarm indicates that the local Unified CM has lost communication with the remote Unified CM. This alarm usually indicates that a node has gone out of service (whether intentionally for maintenance or to install a new load for example; or unintentionally due to a service failure or connectivity failure).

Recommended Action In the Cisco Unified Reporting tool, run a CM Cluster Overview report and check to see if all servers can communicate with the Publisher. Also check for any alarms that might have indicated a CallManager failure and take appropriate action for the indicated failure. If the node was taken out of service intentionally, bring the node back into service.

Local Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
100 CallManager
Remote Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
100 CallManager
Error Message
CallManager- 1 -CMVersionMismatch : One or more Unified CM nodes in a cluster are running different Unified CM versions. Remote Application Link Protocol Version [String] Local Application Link Protocol Version [String] Remote Node ID [UInt] Remote Application ID [Enum] Remote Application Version [String]

Explanation This alarm indicates that the local Unified CM is unable to establish communication with the remote Unified CM due to a software version mismatch. This is generally a normal occurrence when you are upgrading a Unified CM node.

Recommended Action The alarm details include the versions of the local and remote Unified CM nodes. Compare the versions and upgrade a node if necessary.

Remote Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
100 CallManager
200 CTIManager
300 CMI
Error Message
CallManager- 2 -BChannelOOS : The B-channel is out of service. Unique Channel ID [String] Device Name [String] Reason [Enum] Channel ID [UInt]

Explanation The B-channel indicated by this alarm has gone out of service. Some of the more common reasons for a B-channel to go out of service include: Taking the channel out of service intentionally to perform maintenance on either the near-end or far-end; Losing T1/E1/BRI cable connectivity; When the MGCP gateway returns an error code 501 or 510 for a MGCP command sent from Unified CM; When the MGCP gateway doesn't respond to an MGCP command sent by Unified CM three times; When a speed and duplex mismatch exists on the Ethernet port between Unified CM and the MGCP gateway.

Recommended Action Check the Cisco CallManager advanced service parameter, Change B-channel Maintenance Status to determine if the B-channel has been taken out of service intentionally; Check the Q.931 trace for PRI SERVICE message to determine whether a PSTN provider has taken the B-channel out of service; Check the connection of the T1/E1/BRI cable; Reset the MGCP gateway; Check the speed and duplex settings on the Ethernet port.

Reason-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 None Defined
Error Message
CallManager- 5 -BChannelISV : B-channel is in service. Channel ID [UInt] Unique Channel ID [String] Device Name [String]

Explanation The B-channel indicated by this alarm has gone in service

Recommended Action Informational purposes only; no action is required

Error Message
CallManager- 2 -DChannelOOS : The D-channel is out of service. Channel ID [UInt] Unique Channel ID [String] Device Name [String] Device IP Address [String] Reason [Enum]

Explanation The D-channel indicated by this alarm has gone out of service. Common reasons for a D-channel to go out of service include losing T1/E1/BRI cable connectivity; losing the gateway data link (Layer 2) due to an internal or external problem; or a gateway reset.

Recommended Action Check the connection of the T1/E1/BRI cable; reset the gateway to restore Layer 2 connectivity; investigate whether the gateway reset was intentional. If the reset was not intentional, take steps to restrict access to the Gateway Configuration window in Cisco Unified CM Administration and the gateway terminal.

Reason-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 None Defined
Error Message
CallManager- 5 -DChannelISV : D-channel is in service. Channel ID [UInt] Unique Channel ID [String] Device Name [String] Device IP Address [String]

Explanation The indicated D-channel has gone in service

Recommended Action Notification purposes only; no action is required

Error Message
CallManager- 4 -DeviceTransientConnection : A device attempted to register but did not complete registration. Device IP Address [String] Device Name [String] Device MAC Address [String] Protocol [String] Device type [Enum] Reason Code [Enum] Connecting Port [UInt] Registering SIP User [String] IPv6Address [String] IPAddressAttributes [Enum] IPv6AddressAttributes [Enum]

Explanation A connection was established and immediately dropped before completing registration. Incomplete registration may indicate that a device is rehoming in the middle of registration. The alarm could also indicate a device misconfiguration, database error, or an illegal/unknown device trying to attempt a connection. Network connectivity problems can affect device registration, or the restoration of a primary Unified CM may interrupt registration.

Recommended Action In the Cisco Unified Reporting tool, check the Active Services section of the Unified CM Cluster Overview report to confirm that any failover/fallback scenarios have completed. Confirm that auto-registration is enabled if the phone attempting to connect is set to auto-register, or locate the phone that is attempting to auto-register if auto-registration has been intentionally disabled. Check the device indicated in this alarm and confirm that the device registration details in Cisco Unified CM Administration are accurate. Also, refer to the reason code definitions in the alarm for recommended actions. No action is required if this event was issued as a result of a normal device rehome.

Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
10 CISCO_VGC_PHONE
11 CISCO_VGC_VIRTUAL_PHONE
30 ANALOG_ACCESS
40 DIGITAL_ACCESS
42 DIGITAL_ACCESS+
43 DIGITAL_ACCESS_WS-X6608
47 ANALOG_ACCESS_WS-X6624
48 VGC_GATEWAY
50 CONFERENCE_BRIDGE
51 CONFERENCE_BRIDGE_HARDWARE
52 CONFERENCE_BRIDGE_HARDWARE_HDV2
53 CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM
62 H323_GATEWAY
70 MUSIC_ON_HOLD
71 DEVICE_PILOT
73 CTI_ROUTE_POINT
80 VOICE_MAIL_PORT
83 SOFTWARE_MEDIA_TERMINATION_POINT_HDV2
84 CISCO_MEDIA_SERVER
85 CISCO_VIDEO_CONFERENCE_BRIDGE
90 ROUTE_LIST
100 LOAD_SIMULATOR
110 MEDIA_TERMINATION_POINT
111 MEDIA_TERMINATION_POINT_HARDWARE
112 MEDIA_TERMINATION_POINT_HDV2
113 MEDIA_TERMINATION_POINT_WS-SVC-CMM
120 MGCP_STATION
121 MGCP_TRUNK
122 GATEKEEPER
124 7914_14_BUTTON_LINE_EXPANSION_MODULE
125 TRUNK
126 TONE_ANNOUNCEMENT_PLAYER
131 SIP_TRUNK
132 SIP_GATEWAY
133 WSM_TRUNK
134 REMOTE_DESTINATION_PROFILE
227 7915_12_BUTTON_LINE_EXPANSION_MODULE
228 7915_24_BUTTON_LINE_EXPANSION_MODULE
229 7916_12_BUTTON_LINE_EXPANSION_MODULE
230 7916_24_BUTTON_LINE_EXPANSION_MODULE
232 CKEM_36_BUTTON_LINE_EXPANSION_MODULE
254 UNKNOWN_MGCP_GATEWAY
255 UNKNOWN
30027 ANALOG_PHONE
30028 ISDN_BRI_PHONE
30032 SCCP_GATEWAY_VIRTUAL_PHONE
Reason Code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Unknown - (SCCP only) The device failed to register for an unknown reason. If this persists, collect SDL/SDI traces with "Enable SCCP Keep Alive Trace" enabled and contact TAC.
2 NoEntryInDatabase - (MGCP only) The device is not configured in the Unified CM Administration database and auto-registration is either not supported for the device type or is not enabled. To correct this problem, configure this device in Unified CM Administration.
3 DatabaseConfigurationError - The device is not configured in the Unified CM Administration database and auto-registration is either not supported for the device type or is not enabled. To correct this problem, configure this device in Unified CM Administration.
4 DeviceNameUnresolveable - For SIP third-party devices this means that Unified CM could not determine the name of the device from the Authorization header in the REGISTER message. The device did not provide an Authorization header after Unified CM challenged with a 401 Unauthorized message. Verify that the device is configured with digest credentials and is able to respond to 401 challenges with an Authorization header. If this is a Cisco IP phone, the configuration may be out-of-sync. First, go to the Cisco Unified Reporting web page, generate a Unified CM Database Status report, and verify "all servers have a good replication status". If DB replications looks good, reset the phone. If that still doesn't fix the problem, restart the TFTP and the Cisco CallManager services. For all other devices, this reason code means that DNS lookup failed. Verify the DNS server configured via the OS Administration CLI is correct and that the DNS name used by the device is configured in the DNS server.
6 ConnectivityError - The network connection between the device and Unified CM dropped before the device was fully registered. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify that there is network connectivity between the device and Unified CM, and verify the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT).
7 InitializationError - An internal error occurred within Unified CM while processing the device registration. Cisco recommends that you restart the Cisco CallManager service. If this issue occurs repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER Refresh) Trace" and "Enable SCCP Keep Alive Trace" under Cisco CallManager services turned on and contact the Cisco Technical Assistance Center (TAC).
10 AuthenticationError - The device failed either TLS or SIP digest security authentication. If the device is a SIP phone and is enabled for digest authentication (on the System > Security Profile > Phone Security Profile, check if "Enable Digest Authentication" checkbox is checked), verify that the information in the Digest Credentials field on the End User Configuration page is configured. Also, check the Phone Configuration page to determine whether the phone is associated with the specified end user in the Digest User drop box. If the device is a third-party SIP device, verify that the digest credentials configured on the phone match the Digest Credentials configured in the End User Configuration page.
11 InvalidX509NameInCertificate - Configured "X.509 Subject Name" doesn't match the information in the certificate from the device. Check the Security profile of the indicated device and verify that the Device Security Mode is set to either Authenticated or Encrypted. Verify that the X.509 Subject Name field has the appropriate content; it should match the Subject Name in the certificate from the peer.
12 InvalidTLSCipher - Unsupported cipher algorithm used by the device; Unified CM only supports AES_128_SHA cipher algorithm. Recommended action is for the device to regenerate its certificate with the AES_128_SHA cipher algorithm.
14 MalformedRegisterMsg - (SIP only) A SIP REGISTER message could not be processed because of an illegal format. Possible causes include a missing Call-ID header, a missing AoR in the To header, or an expires value that is too small. Check the REGISTER message for any of these issues and if you find one, correct the issue.
15 ProtocolMismatch - The protocol of the device (SIP or SCCP) does not match the configured protocol in Unified CM. Recommended actions: 1) Verify that the device is configured with the appropriate protocol; 2) Verify that the firmware load ID on the Device Defaults page in Cisco Unified CM Administration is correct and actually exists on the TFTP server; 3) If there is a firmware load ID configured on the Device Configuration page, verify that it is correct and that it exists on the TFTP server (on Cisco Unified OS Administration page, access Software Upgrades > TFTP File Management, then look for the file name as specified by load ID); 4) Restart the TFTP and Cisco CallManager services. Use the Cisco Unified OS Administration TFTP File Management page to verify that the configured firmware loads exist.
16 DeviceNotActive - The device has not been activated
17 AuthenticatedDeviceAlreadyExists - A device with the same name is already registered. If this occurs repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER Refresh) Trace" and "Enable SCCP Keep Alive Trace" under Cisco CallManager services turned on and contact the Cisco Technical Assistance Center (TAC). There may be an attempt by unauthorized devices to register.
18 ObsoleteProtocolVersion - (SCCP only) A SCCP device registered with an obsolete protocol version. Power-cycle the phone. Verify that the TFTP service is activated. Verify that the TFTP server is reachable from the device. If there is a firmware load ID configured on the Phone Configuration page, verify that the firmware load ID exists on the TFTP server (on Cisco Unified OS Administration page, access Software Upgrades > TFTP File Management, then look for the file name as specified by load ID).
23 DatabaseTimeout - Unified CM requested device configuration data from the database but did not receive a response within 10 minutes.
25 RegistrationSequenceError - (SCCP only) A device requested configuration information from Unified CM at an unexpected time and Unified CM had not yet obtained the requested information. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be an internal firmware error. Collect existing SDI and SDL traces and contact the Cisco Technical Assistance Center (TAC).
26 InvalidCapabilities - (SCCP only) Unified CM detected an error in the media capabilities reported in the StationCapabilitiesRes message by the device during registration. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be a protocol error. Collect existing SDI and SDL traces and contact the Cisco Technical Assistance Center (TAC).
27 CapabilityResponseTimeout - (SCCP only) Unified CM timed out while waiting for the device to respond to a request to report its media capabilities. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify that network connectivity exists between the device and Unified CM, and verify that the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT).
28 SecurityMismatch - Unified CM detected a mismatch in the security settings of the device and/or Unified CM. This alarm can occur due to any of the following situations: The device established a secure connection yet reported that it does not have the ability to do authenticated signaling; the device did not establish a secure connection but the security mode configured for the device indicates that it should have done so; or the device established a secure connection but the security mode configured for the device indicates that it should not have done so. To correct the error, ensure that the security settings of the device and Unified CM are correct for your deployment. Resetting the device may help because it forces the device to download its latest settings. If the device is a Cisco phone, verify that the TFTP service is running and reachable by the phone and view the Unified CM Database Status report in Cisco Unified Reporting to verify that database replication is Good. You can also issue the following command on the CLI to view database replication: utils dbreplication runtimestate.
29 AutoRegisterDBError - Auto-registration of a device failed because auto-registration is not allowed for the device type or because an error occurred while adding the auto-registering device to the database (stored procedure). Note that if Unified CM is in mixed mode (System > Enterprise Parameters > Cluster Security Mode = 1), auto-registration is not allowed and the device must be configured manually. If you are not planning to auto-register phones, either manually configure the phone (Device > Phone > Add New), power the device down, or remove it from the network. If you are attempting to auto-register this phone, verify that the cluster is not in mixed mode (System > Enterprise Parameters > Cluster Security Mode = 1) and verify that auto-registration is enabled on the node to which this device is registering (System > Cisco Unified CM > ensure that the Auto-registration Disabled... checkbox is not checked).
30 DBAccessError - Device registration failed because of an error that occurred while building the station registration profile. This usually indicates a synchronization problem with the database. View the Unified CM Database Status report in Cisco Unified Reporting to verify that database replication is Good. You can also issue the following command on the CLI to view database replication: utils dbreplication runtimestate. When database replication is Good on all nodes, restart the Cisco CallManager service on the node to which the device is attempting to register. If the problem persists, collect SDI and SDL traces for the Cisco Database layer Monitor service and contact the Cisco Technical Assistance Center (TAC).
31 AutoRegisterDBConfigTimeout - (SCCP only) Unified CM timed out during auto-registration of a device. The registration profile of the device did not get inserted into the database in time. The device will automatically attempt to register again. Check for high CPU utilization on this Unified CM node because congestion could be a cause of this alarm. If this alarm continues to occur, restart the Cisco CallManager service. If the problem persists, contact the Cisco Technical Assistance Center (TAC).
32 DeviceTypeMismatch - The device type reported by the device does not match the device type configured on Unified CM. Verify that the Product Type on the Phone Configuration page in Unified CM Administration matches the model number of the phone. If it does not match, delete the phone and add a new one with the correct Product Type. If the device is a Cisco phone, verify that the TFTP service is running and reachable by the phone, and view the Unified CM Database Status report in Cisco Unified Reporting to verify that database replication is Good. You can also issue the following command on the CLI to view database repliction: utils dbreplication runtimestate.
33 AddressingModeMismatch - (SCCP only) Unified CM detected an error related to the addressing mode configured for the device. One of the following errors was detected: 1) The device is configured to use only IPv4 addressing, but did not specify an IPv4 address; or 2) The device is configured to use only IPv6 addressing, but did not specify an IPv6 address. Reset the device to resolve the problem. If the problem persists, restart the Cisco CallManager service.
34 SourceVerificationForSoftwareMediaDevicesFailure - This applies to Annunciator (ANN) and Music on Hold (MOH) servers only. When the enterprise parameter Cluster Security Mode is set to 1 (mixed mode) and the Unified CM service parameter Enable Source Verification for Software Media Devices is set to True, the source IP address of an ANN or MOH server will be verified to be one of the Unified CM nodes in the cluster. When this alarm occurs with value 34 as the reason, it means that the IP address of the ANN or MOH server is not a recognized node in the cluster. Because ANN or MOH servers currently can only be installed on a Unified CM node, an unknown server that registers an untrusted device as an ANN or MOH server could indicate a security breach. The IP address of the device trying to register is included as part of the alarm; use the IP address to determine whether an unapproved server is attempting to register or if a network address translation (NAT) error occurred because a firewall device is in the network path between two Unified CM nodes.
IPAddressAttributes-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 Unknown - The device has not indicated what this IPv4 address is used for
1 Administrative only - The device has indicated that this IPv4 address is used for administrative communication (web interface) only
2 Signal only - The device has indicated that this IPv4 address is used for control signaling only
3 Administrative and signal - The device has indicated that this IPv4 address is used for administrative communication (web interface) and control signaling
IPv6AddressAttributes-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 Unknown - The device has not indicated what this IPv6 address is used for
1 Administrative only - The device has indicated that this IPv6 address is used for administrative communication (web interface) only
2 Signal only - The device has indicated that this IPv6 address is used for control signaling only
3 Administrative and signal - The device has indicated that this IPv6 address is used for administrative communication (web interface) and control signaling
Error Message
CallManager- 3 -EndPointTransientConnection : An endpoint attempted to register but did not complete registration. Device IP address [String] Device name [String] Device MAC address [String] Protocol [String] Device type [Enum] Reason Code [Enum] Connecting Port [UInt] Registering SIP User [String] IPv6Address [String] IPAddressAttributes [Enum] IPv6AddressAttributes [Enum] LastSignalReceived [String] StationState [String]

Explanation A connection was established and immediately dropped before completing registration. Incomplete registration may indicate that a device is rehoming in the middle of registration. The alarm could also indicate a device misconfiguration, database error, or an illegal/unknown device trying to attempt a connection. Network connectivity problems can affect device registration, or the restoration of a primary Unified CM may interrupt registration.

Recommended Action Investigate any network connectivity problems in the system. It's possible that you have reached the maximum number of devices; the Cisco CallManager service parameter, Maximum Number of Registered Devices, controls the number of devices allowed in the system. After taking licensing, system hardware and other related concerns into consideration, you could increase the value of the service parameter. Also, refer to the reason code definitions in the alarm for additional recommended actions. No action is required if this event was issued as a result of a normal device rehome.

Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 CISCO_30SP+
2 CISCO_12SP+
3 CISCO_12SP
4 CISCO_12S
5 CISCO_30VIP
6 CISCO_7910
7 CISCO_7960
8 CISCO_7940
9 CISCO_7935
12 CISCO_ATA_186
20 SCCP_PHONE
61 H323_PHONE
72 CTI_PORT
115 CISCO_7941
119 CISCO_7971
255 UNKNOWN
302 CISCO_7989
307 CISCO_7911
308 CISCO_7941G_GE
309 CISCO_7961G_GE
335 MOTOROLA_CN622
336 BASIC_3RD_PARTY_SIP_DEVICE
348 CISCO_7931
358 CISCO_UNIFIED_COMMUNICATOR
365 CISCO_7921
369 CISCO_7906
374 ADVANCED_3RD_PARTY_SIP_DEVICE
375 CISCO_TELEPRESENCE
404 CISCO_7962
412 CISCO_3951
431 CISCO_7937
434 CISCO_7942
435 CISCO_7945
436 CISCO_7965
437 CISCO_7975
446 CISCO_3911
468 CISCO_UNIFIED_MOBILE_COMMUNICATOR
478 CISCO_TELEPRESENCE_1000
479 CISCO_TELEPRESENCE_3000
480 CISCO_TELEPRESENCE_3200
481 CISCO_TELEPRESENCE_500
484 CISCO_7925
493 CISCO_9971
495 CISCO_6921
496 CISCO_6941
497 CISCO_6961
20000 CISCO_7905
30002 CISCO_7920
30006 CISCO_7970
30007 CISCO_7912
30008 CISCO_7902
30016 CISCO_IP_COMMUNICATOR
30018 CISCO_7961
30019 CISCO_7936
30035 IP_STE
Reason Code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Unknown - (SCCP only) The device failed to register for an unknown reason. If this persists, collect SDL/SDI traces with "Enable SCCP Keep Alive Trace" enabled and contact the Cisco Technical Assistance Center (TAC).
2 NoEntryInDatabase - (MGCP only) The device is not configured in the Unified CM database and auto-registration is either not supported for the device type or is not enabled. To correct this problem, configure this device in Cisco Unified CM Administration.
3 DatabaseConfigurationError - The device is not configured in the Unified CM database and auto-registration is either not supported for the device type or is not enabled. To correct this problem, configure this device in Cisco Unified CM Administration.
4 DeviceNameUnresolveable - For SIP third-party devices this means that Unified CM could not determine the name of the device from the Authorization header in the REGISTER message. The device did not provide an Authorization header after Unified CM challenged with a 401 Unauthorized message. Verify that the device is configured with digest credentials and is able to respond to 401 challenges with an Authorization header. If this is a Cisco IP phone, the configuration may be out-of-sync. First go to the Cisco Unified Reporting web page, generate a Unified CM Database Status report, and verify that "all servers have a good replication status." If DB replication looks good, reset the phone. If resetting the phone doesn't fix the issue, restart TFTP and Cisco CallManager services. For all other devices, this reason code means that DNS lookup failed. Verify that the DNS server configured via the OS Administration CLI is correct and that the DNS name used by the device is configured in the DNS server.
6 ConnectivityError - The network connection between the device and Unified CM dropped before the device was fully registered. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify network connectivity between the device and Unified CM, and verify that the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT).
7 InitializationError - An internal error occurred within Unified CM while processing the device registration. Cisco recommends that you restart the Cisco CallManager service. If this issue occurs repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER Refresh) Trace" and "Enable SCCP Keep Alive Trace" under Cisco CallManager services turned on and contact the Cisco Technical Assistance Center (TAC).
10 AuthenticationError - The device failed either TLS or SIP digest security authentication. If the device is a SIP phone and is enabled for digest authentication (System > Security Profile > Phone Security Profile, check whether the Enable Digest Authentication checkbox is checked), verify that the Digest Credentials field in the End User Configuration page is configured. Also, check the Phone Configuration page to determine whether the phone is associated with the specified end user in the Digest User drop-down list box. If the device is a third-party SIP device, verify that the digest credentials configured on the phone match the Digest Credentials configured in the End User Configuration page in Unified CM Administration.
11 InvalidX509NameInCertificate - The configured X.509 Subject Name doesn't match the information in the certificate from the device. Check the Security profile of the indicated device and verify that the Device Security Mode is set to either Authenticated or Encrypted. Verify that the X.509 Subject Name field has the appropriate information. It should match the Subject Name in the certificate from the peer.
12 InvalidTLSCipher - An unsupported cipher algorithm was used by the device; Unified CM only supports AES_128_SHA cipher algorithm. Recommended action is for the device to regenerate its certificate with the AES_128_SHA cipher algorithm.
14 MalformedRegisterMsg - (SIP only) A SIP REGISTER message could not be processed because of an illegal format. Possible causes include a missing Call-ID header, a missing AoR in the To header, or an expires value that is too small. Check the REGISTER message for any of these issues and if you find one, correct the issue.
15 ProtocolMismatch - The protocol of the device (SIP or SCCP) does not match the configured protocol in Unified CM. Recommended actions: 1) Verify that the device is configured with the desired protocol; 2) Verify that the firmware load ID on the Device Defaults page in Unified CM Administration is correct and actually exists on the TFTP server; 3) If there is a firmware load ID configured on the device page, verify that it is correct and exists on the TFTP server (on the Cisco Unified OS Administration page, access Software Upgrades > TFTP File Management, then look for the file name as specified by load ID); 4) Restart the TFTP and Cisco CallManager services. Use the Cisco Unified OS Administration TFTP File Management page to verify that the configured firmware loads exist.
16 DeviceNotActive - The device has not been activated
17 AuthenticatedDeviceAlreadyExists - A device with the same name is already registered. If this occurs repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER Refresh) Trace" and "Enable SCCP Keep Alive Trace" under Cisco CallManager services turned on and contact the Cisco Technical Assistance Center (TAC). There may be an attempt by unauthorized devices to register.
18 ObsoleteProtocolVersion - (SCCP only) A SCCP device registered with an obsolete protocol version. Power-cycle the phone. Verify that the TFTP service is activated. Verify that the TFTP server is reachable from the device. If there is a firmware load ID configured on the Phone Configuration page, verify that the firmware load ID exists on the TFTP server (on the Cisco Unified OS Administration page, access Software Upgrades > TFTP File Management, then look for the file name as specified by load ID).
19 DigestAuthChallenge - (SIP only) A SIP device configured for digest authentication attempted to register with invalid credentials. Unified CM has responded with a challenge (401) to request new credentials.
20 DigestAuthChallengeForID - (SIP only) A SIP device attempted to register without a device name or MAC address. Unified CM responded with a challenge (401) which requests the device to resend the REGISTER message and include an Authorization header containing a user ID. Unified CM will use this user ID to attempt to find the device in the configuration database.
21 DigestChallengeTimeout - (SIP only) A SIP device requiring digest authentication sent a REGISTER message and Unified CM responded with a challenge (401) to request the authorization credentials. The device did not resend the REGISTER within the 30-second timeout interval.
22 ExpiresTimeTooSmall - (SIP only) A SIP device attempted to register with an Expires value smaller than the configured SIP Station Keepalive Interval value in the Call Manager Service Parameters. Unified CM responded with 423 Interval Too Brief and the device should re-register with the correct Expires value.
23 DatabaseTimeout - Unified CM requested device configuration data from the database but did not receive a response in time (within 15 seconds for SIP devices, or within 10 minutes for SCCP devices).
24 UniqueDeviceForUserNotFound - (SIP only) A 3rd-party device attempted to register but there is more than 1 device associated with the same Digest User. Third-party devices must be configured with a unique Digest User.
25 RegistrationSequenceError - (SCCP only) A device requested configuration information from Unified CM at an unexpected time and Unified CM had not yet obtained the requested information. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be an internal firmware error. Collect existing SDI and SDL traces and contact the Cisco Technical Assistance Center (TAC).
26 InvalidCapabilities - (SCCP only) Unified CM detected an error in the media capabilities reported in the StationCapabilitiesRes message by the device during registration. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be a protocol error. Collect existing SDI and SDL traces and contact the Cisco Technical Assistance Center (TAC).
27 CapabilityResponseTimeout - (SCCP only) Unified CM timed out while waiting for the device to respond to a request to report its media capabilities. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify that network connectivity exists between the device and Unified CM, and verify that the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT).
28 SecurityMismatch - Unified CM detected a mismatch in the security settings of the device and/or Unified CM. This alarm can occur due to any of the following situations: The device established a secure connection yet reported that it does not have the ability to do authenticated signaling; the device did not establish a secure connection but the security mode configured for the device indicates that it should have done so; or the device established a secure connection but the security mode configured for the device indicates that it should not have done so. To correct the error, ensure that the security settings of the device and Unified CM are correct for your deployment. Resetting the device may help because it forces the device to download its latest settings. If the device is a Cisco phone, verify that the TFTP service is running and reachable by the phone and view the Unified CM Database Status report in Cisco Unified Reporting to verify that database replication is Good. You can also issue the following command on the CLI to view database replication: utils dbreplication runtimestate. If the device is a third-party SIP phone, verify that the configuration on the phone is set to UDP or TCP only; Unified CM does not support TLS on third-party phones. Because each third-party phone model has unique configuration interfaces, please refer to the configuration guide for your phone to learn where the third-party phone defines the UDP/TCP setting.
29 AutoRegisterDBError - Auto-registration of a device failed because auto-registration is not allowed for the device type or because an error occurred while adding the auto-registering device to the database (stored procedure). Note that if Unified CM is in mixed mode (System > Enterprise Parameters > Cluster Security Mode = 1), auto-registration is not allowed and the device must be configured manually. If you are not planning to auto-register phones, either manually configure the phone (Device > Phone > Add New), power the device down, or remove it from the network. If you are attempting to auto-register this phone, verify that the cluster is not in mixed mode (System > Enterprise Parameters > Cluster Security Mode = 1) and verify that auto-registration is enabled on the node to which this device is registering (System > Cisco Unified CM > ensure that the Auto-registration Disabled... checkbox is not checked).
30 DBAccessError - Device registration failed because of an error that occurred while building the station registration profile. This usually indicates a synchronization problem with the database. View the Unified CM Database Status report in Cisco Unified Reporting to verify that database replication is Good. You can also issue the following command on the CLI to view database replication: utils dbreplication runtimestate. When database replication is Good on all nodes, restart the Cisco CallManager service on the node to which the device is attempting to register. If the problem persists, collect SDI and SDL traces for the Cisco Database layer Monitor service and contact the Cisco Technical Assistance Center (TAC).
31 AutoRegisterDBConfigTimeout - (SCCP only) Unified CM timed out during auto-registration of a device. The registration profile of the device did not get inserted into the database in time. The device will automatically attempt to register again. Check for high CPU utilization on this Unified CM node because congestion could be a cause of this alarm. If this alarm continues to occur, restart the Cisco CallManager service. If the problem persists, contact the Cisco Technical Assistance Center (TAC).
32 DeviceTypeMismatch - The device type reported by the device does not match the device type configured on Unified CM. Verify that the Product Type on the Phone Configuration page in Unified CM Administration matches the model number of the phone. If it does not match, delete the phone and add a new one with the correct Product Type. If the device is a Cisco phone, verify that the TFTP service is running and reachable by the phone, and view the Unified CM Database Status report in Cisco Unified Reporting to verify that database replication is Good. You can also issue the following command on the CLI to view database repliction: utils dbreplication runtimestate.
33 AddressingModeMismatch - (SCCP only) Unified CM detected an error related to the addressing mode configured for the device. One of the following errors was detected: 1) The device is configured to use only IPv4 addressing, but did not specify an IPv4 address; or 2) The device is configured to use only IPv6 addressing, but did not specify an IPv6 address. Reset the device to resolve the problem. If the problem persists, restart the Cisco CallManager service.
IPAddressAttributes-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 Unknown - The device has not indicated what this IPv4 address is used for
1 Administrative only - The device has indicated that this IPv4 address is used for administrative communication (web interface) only
2 Signal only - The device has indicated that this IPv4 address is used for control signaling only
3 Administrative and signal - The device has indicated that this IPv4 address is used for administrative communication (web interface) and control signaling
IPv6AddressAttributes-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 Unknown - The device has not indicated what this IPv6 address is used for
1 Administrative only - The device has indicated that this IPv6 address is used for administrative communication (web interface) only
2 Signal only - The device has indicated that this IPv6 address is used for control signaling only
3 Administrative and signal - The device has indicated that this IPv6 address is used for administrative communication (web interface) and control signaling
Error Message
CallManager- 6 -DeviceRegistered : Device registered. Device name [String] Device MAC address [String] Device IP address [String] Protocol [String] Device description [String] User ID [String] Load ID [String] Associated directory numbers [String] Performance monitor object [Enum] Device type [Enum] Configured Gatekeeper Name [String] Technology Prefix Name [String] Zone Information [String] Alternate Gatekeeper List [String] Active Gatekeeper [String] Call Signal Address [String] RAS Address [String] IPV6Address [String] IPAddressAttributes [Enum] IPV6AddressAttributes [Enum] ActiveLoadId [String] InactiveLoadId [String]

Explanation A device successfully registered with Cisco Unified Communications Manager

Recommended Action Informational purposes only; no action is required

Performance monitor object-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Cisco CallManager
2 Cisco Phones
3 Cisco Lines
4 Cisco H323
5 Cisco MGCP Gateway
6 Cisco MOH Device
7 Cisco Analog Access
8 Cisco MGCP FXS Device
9 Cisco MGCP FXO Device
10 Cisco MGCP T1CAS Device
11 Cisco MGCP PRI Device
12 Cisco MGCP BRI Device
13 Cisco MTP Device
14 Cisco Transcode Device
15 Cisco SW Conference Bridge Device
16 Cisco HW Conference Bridge Device
17 Cisco Locations
18 Cisco Gatekeeper
19 Cisco CallManager System Performance
20 Cisco Video Conference Bridge Device
21 Cisco Hunt Lists
22 Cisco SIP
23 Cisco Annunciator Device
24 Cisco QSIG Features
25 Cisco SIP Stack
26 Cisco Presence Features
27 Cisco WSMConnector
28 Cisco Dual-Mode Mobility
29 Cisco SIP Station
30 Cisco Mobility Manager
31 Cisco Signaling
32 Cisco Call Restriction
33 External Call Control
34 Cisco SAF Client
35 IME Client
36 IME Client Instance
Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
10 CISCO_VGC_PHONE
11 CISCO_VGC_VIRTUAL_PHONE
30 ANALOG_ACCESS
40 DIGITAL_ACCESS
42 DIGITAL_ACCESS+
43 DIGITAL_ACCESS_WS-X6608
47 ANALOG_ACCESS_WS-X6624
48 VGC_GATEWAY
50 CONFERENCE_BRIDGE
51 CONFERENCE_BRIDGE_HARDWARE
52 CONFERENCE_BRIDGE_HARDWARE_HDV2
53 CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM
62 H323_GATEWAY
70 MUSIC_ON_HOLD
71 DEVICE_PILOT
73 CTI_ROUTE_POINT
80 VOICE_MAIL_PORT
83 SOFTWARE_MEDIA_TERMINATION_POINT_HDV2
84 CISCO_MEDIA_SERVER
85 CISCO_VIDEO_CONFERENCE_BRIDGE
90 ROUTE_LIST
100 LOAD_SIMULATOR
110 MEDIA_TERMINATION_POINT
111 MEDIA_TERMINATION_POINT_HARDWARE
112 MEDIA_TERMINATION_POINT_HDV2
113 MEDIA_TERMINATION_POINT_WS-SVC-CMM
120 MGCP_STATION
121 MGCP_TRUNK
122 GATEKEEPER
124 7914_14_BUTTON_LINE_EXPANSION_MODULE
125 TRUNK
126 TONE_ANNOUNCEMENT_PLAYER
131 SIP_TRUNK
132 SIP_GATEWAY
133 WSM_TRUNK
134 REMOTE_DESTINATION_PROFILE
227 7915_12_BUTTON_LINE_EXPANSION_MODULE
228 7915_24_BUTTON_LINE_EXPANSION_MODULE
229 7916_12_BUTTON_LINE_EXPANSION_MODULE
230 7916_24_BUTTON_LINE_EXPANSION_MODULE
232 CKEM_36_BUTTON_LINE_EXPANSION_MODULE
254 UNKNOWN_MGCP_GATEWAY
255 UNKNOWN
30027 ANALOG_PHONE
30028 ISDN_BRI_PHONE
30032 SCCP_GATEWAY_VIRTUAL_PHONE
IPAddressAttributes-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 Unknown - The device has not indicated what this IPv4 address is used for
1 Administrative only - The device has indicated that this IPv4 address is used for administrative communication (web interface) only
2 Signal only - The device has indicated that this IPv4 address is used for control signaling only
3 Administrative and signal - The device has indicated that this IPv4 address is used for administrative communication (web interface) and control signaling
IPV6AddressAttributes-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 Unknown - The device has not indicated what this IPv6 address is used for
1 Administrative only - The device has indicated that this IPv6 address is used for administrative communication (web interface) only
2 Signal only - The device has indicated that this IPv6 address is used for control signaling only
3 Administrative and signal - The device has indicated that this IPv6 address is used for administrative communication (web interface) and control signaling
Error Message
CallManager- 6 -EndPointRegistered : Endpoint registered. Device name [String] Device MAC address [String] Device IP address [String] Protocol [String] Device description [String] User ID [String] Load ID [String] Associated directory numbers [String] Performance monitor object [Enum] Device type [Enum] IPV6Address [String] IPAddressAttributes [Enum] IPV6AddressAttributes [Enum] ActiveLoadId [String] InactiveLoadId [String]

Explanation An endpoint successfully registered with Cisco Unified Communications Manager

Recommended Action Notification purposes only; no action is required

Performance monitor object-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
2 Cisco Phone
Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 CISCO_30SP+
2 CISCO_12SP+
3 CISCO_12SP
4 CISCO_12S
5 CISCO_30VIP
6 CISCO_7910
7 CISCO_7960
8 CISCO_7940
9 CISCO_7935
12 CISCO_ATA_186
20 SCCP_PHONE
61 H323_PHONE
72 CTI_PORT
115 CISCO_7941
119 CISCO_7971
255 UNKNOWN
302 CISCO_7989
307 CISCO_7911
308 CISCO_7941G_GE
309 CISCO_7961G_GE
335 MOTOROLA_CN622
336 BASIC_3RD_PARTY_SIP_DEVICE
348 CISCO_7931
358 CISCO_UNIFIED_COMMUNICATOR
365 CISCO_7921
369 CISCO_7906
374 ADVANCED_3RD_PARTY_SIP_DEVICE
375 CISCO_TELEPRESENCE
404 CISCO_7962
412 CISCO_3951
431 CISCO_7937
434 CISCO_7942
435 CISCO_7945
436 CISCO_7965
437 CISCO_7975
446 CISCO_3911
468 CISCO_UNIFIED_MOBILE_COMMUNICATOR
478 CISCO_TELEPRESENCE_1000
479 CISCO_TELEPRESENCE_3000
480 CISCO_TELEPRESENCE_3200
481 CISCO_TELEPRESENCE_500
484 CISCO_7925
493 CISCO_9971
495 CISCO_6921
496 CISCO_6941
497 CISCO_6961
20000 CISCO_7905
30002 CISCO_7920
30006 CISCO_7970
30007 CISCO_7912
30008 CISCO_7902
30016 CISCO_IP_COMMUNICATOR
30018 CISCO_7961
30019 CISCO_7936
30035 IP_STE
IPAddressAttributes-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 Unknown - The device has not indicated what this IPv4 address is used for
1 Administrative only - The device has indicated that this IPv4 address is used for administrative communication (web interface) only
2 Signal only - The device has indicated that this IPv4 address is used for control signaling only
3 Administrative and signal - The device has indicated that this IPv4 address is used for administrative communication (web interface) and control signaling
IPV6AddressAttributes-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 Unknown - The device has not indicated what this IPv6 address is used for
1 Administrative only - The device has indicated that this IPv6 address is used for administrative communication (web interface) only
2 Signal only - The device has indicated that this IPv6 address is used for control signaling only
3 Administrative and signal - The device has indicated that this IPv6 address is used for administrative communication (web interface) and control signaling
Error Message
CallManager- 4 -DevicePartiallyRegistered : A device has partially registered. Device name [String] Device MAC address [String] Device IP address [String] Protocol [String] Device description [String] User ID [String] Load ID [String] Associated directory numbers [String] Performance monitor object [Enum] Device type [Enum] ActiveLoadId [String] InactiveLoadId [String] IPV6Address [String]

Explanation A device is partially registered with Cisco Unified Communications Manager. Some, but not all, of the lines configured on the device have successfully registered.

Recommended Action In the Cisco Unified Reporting tool, run the Unified CM Multi-Line Devices report and check the number of lines that are supposed to be configured on the device identified in this alarm. If the device has registered an inconsistent number of lines compared the Multi-Line report for this device, restart the device so that it can reregister all lines. If this alarm persists, verify that the appropriate number of lines has been configured on the device, and that the appropriate directory numbers have been configured. If the device is a third-party SIP phone, verify that the directory numbers configured on the phone match the directory numbers configured on the device in Unified CM Administration.

Performance monitor object-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Cisco CallManager
2 Cisco Phones
3 Cisco Lines
4 Cisco H323
5 Cisco MGCP Gateway
6 Cisco MOH Device
7 Cisco Analog Access
8 Cisco MGCP FXS Device
9 Cisco MGCP FXO Device
10 Cisco MGCP T1CAS Device
11 Cisco MGCP PRI Device
12 Cisco MGCP BRI Device
13 Cisco MTP Device
14 Cisco Transcode Device
15 Cisco SW Conference Bridge Device
16 Cisco HW Conference Bridge Device
17 Cisco Locations
18 Cisco Gatekeeper
19 Cisco CallManager System Performance
20 Cisco Video Conference Bridge Device
21 Cisco Hunt Lists
22 Cisco SIP
23 Cisco Annunciator Device
24 Cisco QSIG Features
25 Cisco SIP Stack
26 Cisco Presence Features
27 Cisco WSMConnector
28 Cisco Dual-Mode Mobility
29 Cisco SIP Station
30 Cisco Mobility Manager
31 Cisco Signaling
32 Cisco Call Restriction
33 External Call Control
34 Cisco SAF Client
35 IME Client
36 IME Client Instance
Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 CISCO_30SP+
2 CISCO_12SP+
3 CISCO_12SP
4 CISCO_12S
5 CISCO_30VIP
6 CISCO_7910
7 CISCO_7960
8 CISCO_7940
9 CISCO_7935
10 CISCO_VGC_PHONE
11 CISCO_VGC_VIRTUAL_PHONE
12 CISCO_ATA_186
20 SCCP_PHONE
30 ANALOG_ACCESS
40 DIGITAL_ACCESS
42 DIGITAL_ACCESS+
43 DIGITAL_ACCESS_WS-X6608
47 ANALOG_ACCESS_WS-X6624
48 VGC_GATEWAY
50 CONFERENCE_BRIDGE
51 CONFERENCE_BRIDGE_HARDWARE
52 CONFERENCE_BRIDGE_HARDWARE_HDV2
53 CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM
61 H323_PHONE
62 H323_GATEWAY
70 MUSIC_ON_HOLD
71 DEVICE_PILOT
72 CTI_PORT
73 CTI_ROUTE_POINT
80 VOICE_MAIL_PORT
83 SOFTWARE_MEDIA_TERMINATION_POINT_HDV2
84 CISCO_MEDIA_SERVER
85 CISCO_VIDEO_CONFERENCE_BRIDGE
90 ROUTE_LIST
100 LOAD_SIMULATOR
110 MEDIA_TERMINATION_POINT
111 MEDIA_TERMINATION_POINT_HARDWARE
112 MEDIA_TERMINATION_POINT_HDV2
113 MEDIA_TERMINATION_POINT_WS-SVC-CMM
115 CISCO_7941
119 CISCO_7971
120 MGCP_STATION
121 MGCP_TRUNK
122 GATEKEEPER
124 7914_14_BUTTON_LINE_EXPANSION_MODULE
125 TRUNK
126 TONE_ANNOUNCEMENT_PLAYER
131 SIP_TRUNK
132 SIP_GATEWAY
133 WSM_TRUNK
134 REMOTE_DESTINATION_PROFILE
227 7915_12_BUTTON_LINE_EXPANSION_MODULE
228 7915_24_BUTTON_LINE_EXPANSION_MODULE
229 7916_12_BUTTON_LINE_EXPANSION_MODULE
230 7916_24_BUTTON_LINE_EXPANSION_MODULE
232 CKEM_36_BUTTON_LINE_EXPANSION_MODULE
254 UNKNOWN_MGCP_GATEWAY
255 UNKNOWN
302 CISCO_7989
307 CISCO_7911
308 CISCO_7941G_GE
309 CISCO_7961G_GE
335 MOTOROLA_CN622
336 BASIC_3RD_PARTY_SIP_DEVICE
348 CISCO_7931
358 CISCO_UNIFIED_COMMUNICATOR
365 CISCO_7921
369 CISCO_7906
374 ADVANCED_3RD_PARTY_SIP_DEVICE
375 CISCO_TELEPRESENCE
404 CISCO_7962
412 CISCO_3951
431 CISCO_7937
434 CISCO_7942
435 CISCO_7945
436 CISCO_7965
437 CISCO_7975
446 CISCO_3911
468 CISCO_UNIFIED_MOBILE_COMMUNICATOR
478 CISCO_TELEPRESENCE_1000
479 CISCO_TELEPRESENCE_3000
480 CISCO_TELEPRESENCE_3200
481 CISCO_TELEPRESENCE_500
484 CISCO_7925
493 CISCO_9971
495 CISCO_6921
496 CISCO_6941
497 CISCO_6961
20000 CISCO_7905
30002 CISCO_7920
30006 CISCO_7970
30007 CISCO_7912
30008 CISCO_7902
30016 CISCO_IP_COMMUNICATOR
30018 CISCO_7961
30019 CISCO_7936
30027 ANALOG_PHONE
30028 ISDN_BRI_PHONE
30032 SCCP_GATEWAY_VIRTUAL_PHONE
30035 IP_STE
Error Message
CallManager- 4 -DeviceUnregistered : Device unregistered. Device name [String] Device MAC address [String] Device IP address [String] Protocol [String] Device type [Enum] Device description [String] Reason Code [Enum] IPV6Address [String] IPAddressAttributes [Enum] IPV6AddressAttributes [Enum]

Explanation A device that has previously registered with Unified CM has unregistered. In cases of normal unregistration with reason code 'CallManagerReset', 'CallManagerRestart', or 'DeviceInitiatedReset', the severity of this alarm is lowered to INFORMATIONAL. A device can unregister for many reasons, both intentional such as manually resetting the device after a configuration change, and unintentional such as loss of network connectivity. Other causes for this alarm could include a phone being registered to a secondary node and then the primary node coming online, which causes the phone to rehome to the primary Unified CM node. Or, lack of a KeepAlive being returned from the Unified CM node to which this device was registered. Unregistration also occurs if Unified CM receives a duplicate registration request for this same device.

Recommended Action Actions to take vary depending on the reason specified in this alarm for the device unregistration. If the reason is ConfigurationMismatch, go to the Device Configuration page in Cisco Unified CM Administration, make a change to the Description field for this device, click Save, then reset the device. In the case of a network connectivity problem or loss of KeepAlives, use network diagnostic tools and the Cisco Unified CM Reporting tool to fix any reported network or Unified CM system errors. In the case of a device rehoming to the primary Unified CM node, watch for a successful registration of the device on the primary node. In the case of a duplicate registration request, it may be a non-malicious occurrence due to timing of a device registering and unregistering; if duplicate registration requests continue or if the same device has different IP addresses, confirm the IP address on the physical device itself by checking the settings on the device (settings button). If unregistration of this device was expected, no action is required. Also, refer to the reason code descriptions for recommended actions.

Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
10 CISCO_VGC_PHONE
11 CISCO_VGC_VIRTUAL_PHONE
30 ANALOG_ACCESS
40 DIGITAL_ACCESS
42 DIGITAL_ACCESS+
43 DIGITAL_ACCESS_WS-X6608
47 ANALOG_ACCESS_WS-X6624
48 VGC_GATEWAY
50 CONFERENCE_BRIDGE
51 CONFERENCE_BRIDGE_HARDWARE
52 CONFERENCE_BRIDGE_HARDWARE_HDV2
53 CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM
62 H323_GATEWAY
70 MUSIC_ON_HOLD
71 DEVICE_PILOT
73 CTI_ROUTE_POINT
80 VOICE_MAIL_PORT
83 SOFTWARE_MEDIA_TERMINATION_POINT_HDV2
84 CISCO_MEDIA_SERVER
85 CISCO_VIDEO_CONFERENCE_BRIDGE
90 ROUTE_LIST
100 LOAD_SIMULATOR
110 MEDIA_TERMINATION_POINT
111 MEDIA_TERMINATION_POINT_HARDWARE
112 MEDIA_TERMINATION_POINT_HDV2
113 MEDIA_TERMINATION_POINT_WS-SVC-CMM
120 MGCP_STATION
121 MGCP_TRUNK
122 GATEKEEPER
124 7914_14_BUTTON_LINE_EXPANSION_MODULE
125 TRUNK
126 TONE_ANNOUNCEMENT_PLAYER
131 SIP_TRUNK
132 SIP_GATEWAY
133 WSM_TRUNK
134 REMOTE_DESTINATION_PROFILE
227 7915_12_BUTTON_LINE_EXPANSION_MODULE
228 7915_24_BUTTON_LINE_EXPANSION_MODULE
229 7916_12_BUTTON_LINE_EXPANSION_MODULE
230 7916_24_BUTTON_LINE_EXPANSION_MODULE
232 CKEM_36_BUTTON_LINE_EXPANSION_MODULE
254 UNKNOWN_MGCP_GATEWAY
255 UNKNOWN
30027 ANALOG_PHONE
30028 ISDN_BRI_PHONE
30032 SCCP_GATEWAY_VIRTUAL_PHONE
Reason Code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Unknown - The device has unregistered for an unknown reason. If the device does not re-register within 5 minutes, verify that it is powered up and verify that there is network connectivity between the device and Unified CM.
6 ConnectivityError - Network communication between the device and Unified CM has been interrupted. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify that there is network connectivity between the device and Unified CM, and verify that the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT).
8 DeviceInitiatedReset - The device has initiated a reset, possibly due to a power cycle or internal error. No action required; the device will re-register automatically.
9 CallManagerReset - A device reset was initiated from Cisco Unified CM Administration, either due to an explicit command from an administrator, or due to internal errors encountered. No action necessary; the device will re-register automatically.
10 DeviceUnregistered - The device has explicitly unregistered. Possible causes include a change in the IP address or port of the device. No action is necessary; the device will re-register automatically.
11 MalformedRegisterMsg - (SIP only) A SIP REGISTER message could not be processed because of an illegal format. Possible causes include a missing Call-ID header, a missing AoR in the To header, or an expires value that is too small. Check the REGISTER message for any of these issues and if you find one, correct the issue.
12 SCCPDeviceThrottling - (SCCP only) The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. Events can be phone calls, KeepAlive messages, or excessive SCCP or non-SCCP messages. The maximum number of allowed events is controlled by the Cisco CallManager service parameter, Max Events Allowed. When an individual device exceeds the number configured in that service parameter, Unified CM closes the TCP connection to the device; automatic reregistration generally follows. This action is an attempt to stop malicious attacks on Unified CM or to ward off excessive CPU usage.
13 KeepAliveTimeout - A KeepAlive message was not received. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify that there is network connectivity between the device and Unified CM, and verify the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT).
14 ConfigurationMismatch (SIP only) The configuration on the device does not match the configuration in Unified CM. This can be caused by database replication errors or other internal Unified CM communication errors. Go to the Cisco Unified Reporting web page, generate a Unified CM Database Status report and verify "all servers have a good replication status". You can also go to the Real-Time Reporting Tool (RTMT) and check the Replication Status in the Database Summary page. If status shows 2, then replication is working. If this device continues to unregister with this reason code, go to the Device Configuration page in Unified CM Administration for the device indicated in this alarm and click Save. This generates a change notify message to the Cisco CallManager and TFTP services and rebuilds a new configuration file for the device. If the problem still persists, restart the TFTP service and the Cisco CallManager service.
15 CallManagerRestart - A device restart was initiated from Unified CM Administration, either due to an explicit command from an administrator or due to a configuration change such as adding, deleting or changing a directory number associated with the device. No action is necessary; the device will re-register automatically.
16 DuplicateRegistration - Unified CM detected that the device attempted to register to two nodes at the same time. Unified CM initiated a restart to the phone to force it to re-home to a single node. No action is necessary; the device will re-register automatically.
17 CallManagerApplyConfig - An ApplyConfig action was performed in Unified CM Administration resulting in an unregistration. No action is necessary; the device will re-register automatically.
18 DeviceNoResponse - The device did not respond to a reset or restart notification, so it is being forcefully reset. If the device does not re-register within 5 minutes, confirm that it is powered up and confirm that there is network connectivity between the device and Unified CM.
19 EMLoginLogout - The device has been unregistered due to an Extension Mobility login or logout
20 EMCCLoginLogout - The device has been unregistered due to an Extension Mobility Cross Cluster login or logout
25 RegistrationSequenceError - (SCCP only) A device requested configuration information from Unified CM at an unexpected time and Unified CM no longer had the requested information in memory. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be an internal firmware error. Collect existing SDI and SDL traces and contact the Cisco Technical Assistance Center (TAC).
26 InvalidCapabilities - (SCCP only) Unified CM detected an error in the updated media capabilities reported in one of the StationUpdateCapabilities messages sent by the device. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be a protocol error. Collect existing SDI and SDL traces and contact the Cisco Technical Assistance Center (TAC).
28 FallbackInitiated - The device has initiated a fallback and will automatically re-register to a higher-priority Unified CM. No action is necessary.
IPAddressAttributes-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 Unknown - The device has not indicated what this IPv4 address is used for
1 Administrative only - The device has indicated that this IPv4 address is used for administrative communication (web interface) only
2 Signal only - The device has indicated that this IPv4 address is used for control signaling only
3 Administrative and signal - The device has indicated that this IPv4 address is used for administrative communication (web interface) and control signaling
IPV6AddressAttributes-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 Unknown - The device has not indicated what this IPv6 address is used for
1 Administrative only - The device has indicated that this IPv6 address is used for administrative communication (web interface) only
2 Signal only - The device has indicated that this IPv6 address is used for control signaling only
3 Administrative and signal - The device has indicated that this IPv6 address is used for administrative communication (web interface) and control signaling
Error Message
CallManager- 3 -EndPointUnregistered : An endpoint has unregistered. Device name [String] Device MAC address [String] Device IP address [String] Protocol [String] Device type [Enum] Device description [String] Reason Code [Enum] IPV6Address [String] IPAddressAttributes [Enum] IPV6AddressAttributes [Enum] LastSignalReceived [String] CallState [String]

Explanation An endpoint that has previously registered with Cisco Unified Communications Manager has unregistered. In cases of normal unregistration with reason code 'CallManagerReset', 'CallManagerRestart', 'DeviceInitiatedReset', 'EMLoginLogout', or 'EMCCLoginLogout', the severity of this alarm is lowered to INFORMATIONAL. An endpoint can unregister for many reasons, both intentional such as manually resetting the device after a configuration change, or unintentional such as loss of network connectivity. Other causes for this alarm could include a phone being registered to a secondary node and then the primary node coming online, causing the phone to rehome to the primary Unified CM node. Or, lack of a KeepAlive message being returned from the Unified CM node to which this endpoint was registered. Unregistration also occurs if Unified CM receives a duplicate registration request for this same device.

Recommended Action Actions to take vary depending on the reason specified for the endpoint unregistration. If the reason is ConfigurationMismatch, go to the Device Configuration page in Cisco Unified CM Administration, make a change to the Description field for this device, click Save, then reset the device. In the case of a network connectivity problem or loss of KeepAlives, use network diagnostic tools and the Cisco Unified CM Reporting tool to fix any reported network or Unified CM system errors. In the case of an endpoint rehoming to the primary Unified CM node, watch for a successful registration of the device on the primary node. In the case of a duplicate registration request, it may be a non-malicious occurrence due to timing of an endpoint registering and unregistering; if duplicate registration requests continue or if the same endpoint has different IP addresses, confirm the IP address on the physical device itself by checking the settings on the device (settings button). If unregistration of this device was expected, no action is required. Also, refer to the reason code descriptions in this alarm for additional recommended actions.

Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 CISCO_30SP+
2 CISCO_12SP+
3 CISCO_12SP
4 CISCO_12S
5 CISCO_30VIP
6 CISCO_7910
7 CISCO_7960
8 CISCO_7940
9 CISCO_7935
12 CISCO_ATA_186
20 SCCP_PHONE
61 H323_PHONE
72 CTI_PORT
115 CISCO_7941
119 CISCO_7971
255 UNKNOWN
302 CISCO_7989
307 CISCO_7911
308 CISCO_7941G_GE
309 CISCO_7961G_GE
335 MOTOROLA_CN622
336 BASIC_3RD_PARTY_SIP_DEVICE
348 CISCO_7931
358 CISCO_UNIFIED_COMMUNICATOR
365 CISCO_7921
369 CISCO_7906
374 ADVANCED_3RD_PARTY_SIP_DEVICE
375 CISCO_TELEPRESENCE
404 CISCO_7962
412 CISCO_3951
431 CISCO_7937
434 CISCO_7942
435 CISCO_7945
436 CISCO_7965
437 CISCO_7975
446 CISCO_3911
468 CISCO_UNIFIED_MOBILE_COMMUNICATOR
478 CISCO_TELEPRESENCE_1000
479 CISCO_TELEPRESENCE_3000
480 CISCO_TELEPRESENCE_3200
481 CISCO_TELEPRESENCE_500
484 CISCO_7925
493 CISCO_9971
495 CISCO_6921
496 CISCO_6941
497 CISCO_6961
20000 CISCO_7905
30002 CISCO_7920
30006 CISCO_7970
30007 CISCO_7912
30008 CISCO_7902
30016 CISCO_IP_COMMUNICATOR
30018 CISCO_7961
30019 CISCO_7936
30035 IP_STE
Reason Code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Unknown - The device has unregistered for an unknown reason. If the device does not re-register within 5 minutes, verify that it is powered up and verify that network connectivity exists between the device and Unified CM.
6 ConnectivityError - Network communication between the device and Unified CM has been interrupted. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify that network connectivity exists between the device and Unified CM, and verify that the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT).
8 DeviceInitiatedReset - The device has initiated a reset, possibly due to a power cycle or internal error. No action is required; the device will re-register automatically.
9 CallManagerReset - A device was reset from Cisco Unified CM Administration, either due to an explicit command from an administrator, or due to internal errors encountered. No action is necessary; the device will re-register automatically.
10 DeviceUnregistered - The device has explicitly unregistered. Possible causes include a change in the IP address or port of the device. No action is necessary; the device will re-register automatically.
11 MalformedRegisterMsg - (SIP only) A SIP REGISTER message could not be processed because of an illegal format. Possible causes include a missing Call-ID header, a missing AoR in the To header, or an expires value that is too small. Check the REGISTER message for any of these issues and if you find one, correct the issue.
12 SCCPDeviceThrottling - (SCCP only) The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. Events can be phone calls, KeepAlive messages, or excessive SCCP or non-SCCP messages. The maximum number of allowed events is controlled by the Cisco CallManager service parameter, Max Events Allowed. When an individual device exceeds the number configured in that service parameter, Unified CM closes the TCP connection to the device; automatic reregistration generally follows. This action is an attempt to stop malicious attacks on Unified CM or to ward off excessive CPU usage. No action is necessary; the device will re-register automatically.
13 KeepAliveTimeout - A KeepAlive message was not received. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify that network connectivity exists between the device and Unified CM, and verify that the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT). No action is necessary; the device will re-register automatically.
14 ConfigurationMismatch (SIP only) The configuration on the device does not match the configuration in Unified CM. This can be caused by database replication errors or other internal Unified CM communication errors. First go to the Cisco Unified Reporting web page, generate a Unified CM Database Status report, and verify "all servers have a good replication status". You can also go to the Real-Time Reporting Tool (RTMT) and check the Replication Status in the Database Summary page. If status shows 2, then replication is working. If this device continues to unregister with this reason code, go to the Device Configuration page in Unified CM Administration for the device identified in this alarm and click Save. This generates a change notification message to the Cisco CallManager and TFTP services and rebuilds a new configuration file. If the problem still persists, restart the TFTP service and Cisco CallManager service.
15 CallManagerRestart - A device restart was initiated from Unified CM, either due to an explicit command from an administrator, or due to a configuration change such as adding, deleting or changing a directory number associated with the device. No action is necessary; the device will re-register automatically.
16 DuplicateRegistration - Unified CM detected that the device attempted to register to two nodes at the same time. Unified CM initiated a restart to the phone to force it to re-home to a single node. No action is necessary; the device will re-register automatically.
17 CallManagerApplyConfig - An ApplyConfig action was performed in Unified CM Administration resulting in an unregistration. No action is necessary; the device will re-register automatically.
18 DeviceNoResponse - The device did not respond to a reset or restart notification, so it is being forcefully reset. If the device does not re-register within 5 minutes, confirm that the device is powered-up and confirm that network connectivity exists between the device and Unified CM.
19 EMLoginLogout - The device has been unregistered due to an Extension Mobility login or logout
20 EMCCLoginLogout - The device has been unregistered due to an Extension Mobility Cross Cluster login or logout
21 PowerSavePlus - The device powered off as a result of the Power Save Plus feature that is enabled for this device. When the device powers off, it remains unregistered from Unified CM until the Phone On Time defined in the Product Specific Configuration for this device.
22 CallManagerForcedRestart - (SIP Only) The device did not respond to an Apply Config request and as a result, Unified CM sent a restart request to the device. The device may be offline due to a power outage or network problem. Confirm that the device is powered-up and that network connectivity exists between the device and Unified CM.
23 SourceIPAddrChanged - (SIP Only) The device has been unregistered because the IP address in the Contact header of the REGISTER message has changed. The device will be automatically re-registered. No action is necessary.
24 SourcePortChanged - (SIP Only) The device has been unregistered because the port number in the Contact header of the REGISTER message has changed. The device will be automatically re-registered. No action is necessary.
25 RegistrationSequenceError - (SCCP only) A device requested configuration information from Unified CM at an unexpected time and Unified CM no longer had the requested information in memory. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be an internal firmware error. Collect existing SDI and SDL traces and contact the Cisco Technical Assistance Center (TAC).
26 InvalidCapabilities - (SCCP only) Unified CM detected an error in the updated media capabilities reported in one of the StationUpdateCapabilities messages sent by the device. The device will automatically attempt to register again. If this alarm occurs again, manually reset the device. If this alarm continues to occur after the manual reset, there may be a protocol error. Collect existing SDI and SDL traces and contact the Cisco Technical Assistance Center (TAC).
28 FallbackInitiated - The device has initiated a fallback and will automatically re-register to a higher-priority Unified CM. No action is necessary.
29 DeviceSwitch - A second instance of an endpoint with the same device name has registered and assumed control. No action is necessary.
IPAddressAttributes-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 Unknown - The device has not indicated what this IPv4 address is used for
1 Administrative only - The device has indicated that this IPv4 address is used for administrative communication (web interface) only
2 Signal only - The device has indicated that this IPv4 address is used for control signaling only
3 Administrative and signal - The device has indicated that this IPv4 address is used for administrative communication (web interface) and control signaling
IPV6AddressAttributes-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 Unknown - The device has not indicated what this IPv6 address is used for
1 Administrative only - The device has indicated that this IPv6 address is used for administrative communication (web interface) only
2 Signal only - The device has indicated that this IPv6 address is used for control signaling only
3 Administrative and signal - The device has indicated that this IPv6 address is used for administrative communication (web interface) and control signaling
Error Message
CallManager- 4 -SIPLineRegistrationError : SIP line registration error. Device IP address [String] Device Port [UInt] Device name [String] Device MAC address [String] Device type [Enum] Reason Code [Enum] Connecting Port [UInt] Configured DNs [String] Registering SIP User [String] IPV6Address [String]

Explanation A SIP line attempted to register with Cisco Unified Communications Manager (Unified CM) and failed due to the error indicated in the Reason Code parameter. The alarm could indicate a device misconfiguration, database error, or an illegal/unknown device trying to attempt a connection. This alarm typically occurs with a third-party device.

Recommended Action Verify that the directory number(s) on the device itself match the directory number(s) that are configured for that device in Cisco Unified CM Administration. Also, confirm that database replication is working. To do so, check the Unified CM Database Status report in Cisco Unified Reporting to verify that database replication is working. You can also go to Real-Time Reporting Tool (RTMT) and check the Replication Status in the Database Summary page. If status shows 2, then replication is working. Refer to the reason code definitions for additional recommended actions.

Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 CISCO_30SP+
2 CISCO_12SP+
3 CISCO_12SP
4 CISCO_12S
5 CISCO_30VIP
6 CISCO_7910
7 CISCO_7960
8 CISCO_7940
9 CISCO_7935
12 CISCO_ATA_186
20 SCCP_PHONE
61 H323_PHONE
72 CTI_PORT
115 CISCO_7941
119 CISCO_7971
255 UNKNOWN
302 CISCO_7989
307 CISCO_7911
308 CISCO_7941G_GE
309 CISCO_7961G_GE
335 MOTOROLA_CN622
336 BASIC_3RD_PARTY_SIP_DEVICE
348 CISCO_7931
358 CISCO_UNIFIED_COMMUNICATOR
365 CISCO_7921
369 CISCO_7906
374 ADVANCED_3RD_PARTY_SIP_DEVICE
375 CISCO_TELEPRESENCE
404 CISCO_7962
412 CISCO_3951
431 CISCO_7937
434 CISCO_7942
435 CISCO_7945
436 CISCO_7965
437 CISCO_7975
446 CISCO_3911
468 CISCO_UNIFIED_MOBILE_COMMUNICATOR
478 CISCO_TELEPRESENCE_1000
479 CISCO_TELEPRESENCE_3000
480 CISCO_TELEPRESENCE_3200
481 CISCO_TELEPRESENCE_500
484 CISCO_7925
493 CISCO_9971
495 CISCO_6921
496 CISCO_6941
497 CISCO_6961
20000 CISCO_7905
30002 CISCO_7920
30006 CISCO_7970
30007 CISCO_7912
30008 CISCO_7902
30016 CISCO_IP_COMMUNICATOR
30018 CISCO_7961
30019 CISCO_7936
30035 IP_STE
Reason Code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
2 MisconfiguredDirectoryNumber - There is a configuration mismatch between the directory numbers configured on the phone and the directory numbers configured in the Unified CM database. If this is a third-party phone, confirm that the phone configuration is correct and matches the Unified CM configuration. If this is a Cisco IP phone, go to the Cisco Unified Reporting web page and confirm that database replication has a "good status" in the Unified CM Database Status report. You can also go to Real-Time Reporting Tool (RTMT) and check the Replication Status in the Database Summary page. If status shows 2, then replication is working. If the database replication status is good, reset the device. If the problem still persists, restart the TFTP service and the Cisco CallManager service from the Control Center - Feature Services web page.
3 MalformedRegisterMessage - Unified CM cannot process a REGISTER message because of a problem with the format of the message. If the device is a third-party phone, confirm that the endpoint is sending a properly formatted REGISTER message.
4 AuthenticationError - The digest User ID or password sent from the phone does not match the User ID or password configured in Cisco Unified CM Administration. Digest User ID is the end user who is associated with the phone, as shown on the Phone Configuration page (in the Digest User drop-down list box). Password is configured on the End User Configuration page in the Digest Credentials field. If this is a third-party phone, ensure that the phone's digest credentials match the digest credentials configured on the End User Configuration page in Unified CM Administration. If this is a Cisco IP phone, go to the Cisco Unified Reporting web page to confirm that database replication has a "good status" in the Unified CM Database Status report. You can also go to Real-Time Reporting Tool (RTMT) and check the Replication Status in the Database Summary page. If status shows 2, then replication is working. If the database replication status is good, reset the device. If the problem still persists, restart the TFTP service and the Cisco CallManager service from the Control Center - Feature Services web page.
6 MaxLinesExceeded - The phone is attempting to register more lines than are allowed. The maximum lines per device is 1024. Reduce the number of lines configured on this device.
7 TransportProtocolMismatch - Incorrect transport protocol (UDP, TCP or TCL) on which the REGISTER message was received. If the device is a third-party phone, ensure that the phone is using a transport protocol that matches the Phone Security Profile assigned to the phone on the phone's Device Configuration page in Unified CM Administration. If the device is a Cisco phone, go to the Cisco Unified Reporting web page to confirm that database replication has a "good status" in the Unified CM Database Status report. You can also go to Real-Time Reporting Tool (RTMT) and check the Replication Status in the Database Summary page. If status shows 2, then replication is working. If the database replication status is good, reset the device. If the problem still persists, restart the TFTP service and the Cisco CallManager service from the Control Center - Feature Services web page.
8 BulkRegistrationError - An unexpected bulk registration message was received. If this occurs repeatedly, collect SDL/SDI detailed traces with "Enable SIP Keep Alive (REGISTER Refresh) Trace" under Cisco CallManager service turned on and contact the Cisco Technical Assistance Center (TAC).
Error Message
CallManager- 5 -H323Started : Unified CM is ready to handle calls for the indicated H.323 device. Device Name [String] IP Address [String] Device type [Enum] Device description [String] Remote Unified CM Server IP Address/Host Name list as configured in the Trunk Configuration window [String] The Server 1 IP Address/Host Name as configured in the Trunk Configuration window; this parameter provides a partial list of remote Unified CM servers. Refer to the RemoteUnifiedCMServerList for the complete list of Unified CM servers. This parameter will be removed in Unified CM release 10.0(1) [String] Remote Unified CM Server 2 [String] Remote Unified CM Server 3 [String]

Explanation Cisco Unified Communications Manager (Unified CM) is ready to communicate with the indicated H.323 device. Note that this alarm describes the readiness of Unified CM to communicate with the indicated device but does not provide information about the state of the H.323 device (whether it is ready to communicate as well).

Recommended Action Notification purposes only; no action is required

Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
61 H323_PHONE
62 H323_GATEWAY
122 GATEKEEPER
125 TRUNK
Error Message
CallManager- 4 -H323Stopped : Unified CM is not ready to handle calls for the indicated H.323 device. Device Name [String] IP Address [String] Device type [Enum] Device description [String] Remote CallManager Server [String] Remote CallManager Server 2 [String] Remote CallManager Server 3 [String]

Explanation Unified CM is not ready to handle calls for the indicated H.323 device. This could be due to Unified CM being unable to resolve the gateway name to IP address. For trunks, this alarm should only occur when a system administrator has made a configuration change such as resetting the H.323 trunk. For H.323 clients, this alarm occurrence is normal on lower-priority Unified CM nodes when a high-priority Unified CM node starts.

Recommended Action If the service was stopped intentionally, no action is required. Check the domain name system (DNS) configuration for any errors in the gateway name or IP address and correct.

Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
61 H323_PHONE
62 H323_GATEWAY
122 GATEKEEPER
125 TRUNK
Error Message
CallManager- 5 -SIPStarted : Unified CM is ready to handle calls for the indicated SIP device. Device Name [String] IP Address [String] Device type [Enum] Device description [String] Incoming Port Number [UInt] Outgoing Port Number [UInt] Incoming Transport Type [Enum] Outgoing Transport Type [Enum] IPV6Address [String]

Explanation Unified CM is ready to handle calls for the indicated SIP device. This alarm does not indicate the current state of the SIP device, only that Unified CM is prepared to handle calls to/from the SIP device.

Recommended Action Informational purposes only; no action is required

Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
131 SIP_TRUNK
Incoming Transport Type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 TCP
2 UDP
3 TLS
4 TCP/UDP
Outgoing Transport Type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 TCP
2 UDP
3 TLS
Error Message
CallManager- 4 -SIPStopped : Unified CM is not ready to handle calls for the indicated SIP device. Device Name [String] IP Address [String] Device type [Enum] Device description [String] Incoming Port Number [UInt] Outgoing Port Number [UInt] Incoming Transport Type [Enum] Outgoing Transport Type [Enum] IPV6Address [String]

Explanation Unified CM is not ready to handle calls for the indicated SIP device. Possible reasons could be internal database error, the SIP device is not activated on this node, the SIP device failed to register, or the SIP device was deleted from Cisco Unified CM Administration.

Recommended Action This alarm doesn't necessarily mean an error. It could occur as a result of normal administrative changes. If the alarm is unexpected, check whether the StationPortInitError alarm also fired. Check the Device Pool assigned to the SIP device identified in this alarm to ensure that the Cisco Unified Communications Manager Group of the Device Pool includes the Unified CM node that issued the alarm.

Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
131 SIP_TRUNK
Incoming Transport Type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 TCP
2 UDP
3 TLS
4 TCP/UDP
Outgoing Transport Type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 TCP
2 UDP
3 TLS
Error Message
CallManager- 5 -SIPNormalizationScriptOpened : Unified CM has opened the script for this device. Device Name [String] Script Name [String] In Use Memory [UInt]

Explanation The normalization script for the indicated SIP device has been successfully loaded, initialized, and is active on Unified CM

Recommended Action Notification purposes only; no action is required

Error Message
CallManager- 5 -SIPNormalizationScriptClosed : Unified CM has closed (disabled) the script for this device . Device Name [String] Script Name [String] Reason Code [Enum] Reason Text [String] Additional Information [String]

Explanation Unified CM closed the script either because the indicated device (SIP trunk) was reset manually or automatically, the trunk was deleted, or because of a script error or resource error, or because of an internal error. When the script is closed, Unified CM is not invoking normalization script message handlers for the indicated SIP device.

Recommended Action This alarm serves as notification of the script closure if the alarm occurred due to a SIP trunk maintenance window or some other expected reason for the script to close. If this alarm is unexpected, check for an occurrence of the SIPNormalizationScriptError alarm and refer to the specific action based on the reason code identified in that alarm.

Reason Code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 DeviceResetManually - The associated device was manually reset via Cisco Unified CM Administration
2 DeviceResetAutomatically - The associated device was reset automatically; the reset was triggered by an execution error in the script
3 DeviceDeleted - The associated device was manually deleted in Cisco Unified CM Administration
4 ScriptDisassociated - A configuration change occurred in Cisco Unified CM Administration and the script is no longer associated with the device
5 ScriptInfoChanged - A change in the script logic occurred or a change to one or more fields on the SIP Normalization Script Configuration window in Cisco Unified CM Administration occurred
6 ScriptError - An error occurred in the script; check for a SIPNormalizationScriptError alarm and perform the recommended actions described to correct the script error
Error Message
CallManager- 3 -SIPNormalizationScriptError : A script error occurred. Device Name [String] Script Name [String] Script Function [String] Script Type [String] Error Code [Enum] Error Code Text [String] Error Message [String] Configured Action [String] Resulting Action [String] In Use Memory [UInt] Memory Threshold [UInt] In Use Lua Instructions [UInt] Lua Instruction Threshold [UInt]

Explanation Unified CM encountered an error during loading, initializing, or during execution of the SIP normalization script for the indicated SIP device. If the error was due to a resource issue, the SIPNormalizationResourceWarning alarm will also be issued. The Configured Action shown in this alarm may differ from the Resulting Action shown in this alarm because certain errors, such as those occurring during loading or initialization, cannot be configured. If the script closes three times within a 10-minute window due to errors, Unified CM will follow the configured action three times; on the fourth occurrence of the error, Unified CM disables the script and issues the SIPNormalizationAutoResetDisabled alarm.

Recommended Action Examine SDI trace files for details regarding the error such as function calls and the call ID which may help provide details that assist with troubleshooting the error. Examine the script for syntax or logic errors; for scripts provided by Cisco, contact the Cisco Technical Assistance Center (TAC). If the error was due to a resource issue, the SIPNormalizationResourceWarning alarm will also be issued. Check that alarm for additional information and recommended actions.

Error Code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 LoadError - The script failed to load either due to a syntax error in the script or a resource error; check the Recommended Actions for instructions
2 InitializationError - The script encountered a failure while initializing either due to a syntax error in the script or a resource error; check the Recommended Actions for instructions
3 ExecutionError - The script encountered a failure during execution; check the Recommended Actions for instructions
4 InternalError - The system encountered an unexpected condition during execution; check the Recommended Actions for instructions
Error Message
CallManager- 3 -SIPNormalizationResourceWarning : The script has exceeded an internal resource threshold and may be in danger of closing. Device Name [String] Script Name [String] Script Function [String] Script Type [String] Reason Code [Enum] Reason Text [String] In Use Memory [UInt] Memory Threshold [UInt] In Use Lua Instructions [UInt] Lua Instruction Threshold [UInt]

Explanation The normalization script for the indicated SIP device has exceeded an internal threshold for resource consumption. This alarm can occur for memory consumption or when the script is close to exceeding the configured allowance of Lua instructions. When the amount of memory (as defined in the Memory Threshold field) or the number of Lua instructions utilized by this script (as defined by the Lua Instruction Threshold) exceeds an internal threshold, this alarm is triggered. For example, if the Memory Threshold is set to 100 kb and the internal threshold is 80%, this alarm will occur when this script has consumed 80 kb of memory. The internal threshold is not configurable and may fluctuate from Unified CM release to release. Another example: if the Lua Instruction Threshold is set to 2000 and the internal threshold is 50%, this alarm occurs when the script has executed 1000 Lua instructions. This alarm serves as a warning that resources (either memory or Lua instructions) have passed an internal mark where investigation into the consumption of those resources may be advisable to ensure the health of the script. Investigate and correct the resource issue before the script closes. When the values that have been configured in the fields, Memory Threshold field and/or Lua Instruction Threshold on the SIP Normalization Script Configuration window are met, the script closes and the SIPNormalizationScriptClosed alarm also occurs. For additional information when troubleshooting, check the SIP Normalization counter, MemoryUsagePercentage to learn the current resource usage.

Recommended Action Examine the thresholds (Memory Threshold and Lua Instruction Threshold) configured in the SIP Normalization Script Configuration window and evaluate if those thresholds can be increased (take into consideration the CPU resources and memory when deciding to increase these values) or examine the script to determine if the message handlers can be written more efficiently to reduce the number of instructions in the script. Examine the script for logic errors. If the script is otherwise functioning normally but contains extensive logic, consider increasing the value in the Lua Instruction Threshold field. Be aware that more computing resources will be consumed as a result. You can also examine SDI trace files for additional details about this resource condition. For scripts provided by Cisco, contact the Cisco Technical Assistance Center (TAC).

Reason Code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 InternalLuaInstructionsThreshold - The script exceeded the internal threshold for the number of Lua instructions
2 InternalMemoryThreshold - The script exceeded the internal threshold for script memory usage
Error Message
CallManager- 5 -SIPNormalizationAutoResetDisabled : An error has occurred repeatedly and Unified CM disabled the script. Device Name [String] Script Name [String] Script Type [String] Reason Code [Enum] Reason Text [String] Additional Information [String]

Explanation The script failed due to execution errors three times within a 10 minute period. As a result, the normalization script for the indicated SIP device has been disabled. Unified CM is no longer attempting to automatically reset either the script or the device for the purposes of recovering the script.

Recommended Action Notification purposes; examine the information and perform the recommended actions in the SIPNormalizationScriptError alarm, which should have been issued prior to this alarm

Reason Code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 ScriptResetDisabled - The system has automatically reset the script three times within a 10 minute period due to script execution errors; on the fourth occurrence of this error, Unified CM disabled the script
2 TrunkResetDisabled - The system has automatically reset the trunk three times within a 10 minute period due to script execution errors; on the fourth occurrence of this error, Unified CM disabled the script
Error Message
CallManager- 5 -SIPTrunkISV : All remote peers are available to handle calls for this SIP trunk . SIP Trunk Name [String] Available remote peers for this SIP trunk [String]

Explanation All remote peers are available to handle calls for this SIP trunk. This alarm specifies the available remote peers for this SIP trunk; each peer is identified by resolved IP address and port number, and hostname or SRV if configured on SIP trunk.

Recommended Action Notification purpose only; no action is required

Error Message
CallManager- 3 -SIPTrunkOOS : All remote peers are out of service and unable to handle calls for this SIP trunk. SIP Trunk Name [String] Unavailable remote peers with Reason Code [String]

Explanation All remote peers for this SIP trunk are out of service and unable to handle calls. This alarm provides the reason code received by the SIP trunk in response to an Options request sent to the remote peer. The list of unavailable remote peers is provided in this alarm and each peer is separated by semi-colon. For each peer, the alarm provides the hostname or SRV (if configured on SIP trunk), resolved IP address, port number, and reason code in the following format: ReasonCodeType=ReasonCode. ReasonCodeType could be based on a SIP response from the remote peer as defined in SIP RFCs (Remote) or based on a reason code provided by Unified CM (Local). Examples of possible reason codes include Remote=503 ("503 Service Unavailable" a standard SIP RFC error code), Remote=408 ("408 Request Timeout" a standard SIP RFC error code), Local=1 (request timeout), Local=2 (local SIP stack is not able to create a socket connection with the remote peer), Local=3 (DNS query failed). For Local=3, IP address in Alarm will be represented as "0" and when dns srv is configured on SIP trunk then port will be represented as "0".

Recommended Action For Remote=503, possible reasons include 1) route/sip trunk for originating side doesn't exist on remote peer; 2) route/sip trunk for originating side does exist on the remote peer but the port is either used for a SIP phone or a different sip trunk; 3) the remote peer has limited resources and may not be able to handle new calls. For the first cause (item 1), if the remote peer is Unified CM, add a new SIP trunk in Unified CM Administration for the remote peer (Device > Trunk) and make certain that the Destination Address and Destination Port fields are configured to point to the originating host (the originating host is the same node on which this alarm was generated). Also ensure the new SIP trunk has the incoming port in associated SIP Trunk Security Profile configured to be same as originating side SIP Trunk destination port. For the second cause (item 2), if the remote peer is Unified CM, then in Unified CM Administration for the remote peer (Device > Trunk) make certain that incoming port in associated SIP Trunk Security Profile is configured to be same as originating side SIP Trunk destination port. For the third cause (item 3), if the remote peer is administered by a different system administrator, consider communicating the resource issue with the other administrator. For remote=408, possible reason includes remote is running low in resources and unable to process the request. If the remote peer is administered by a different system administrator, consider communicating the resource issue with the other administrator. For Local=1, possible reason could be that no responses has been received for Options request after all retries when transport is configured as UDP in SIP trunk Security Profile assigned to the SIP trunk on originating side. To fix this issue, if the remote peer is Unified CM, then go to remote peer Serviceability web page and then Tools -> Control Center (Feature Services) and make sure Cisco Call Manager service is activated and started. Also, go to remote peer admin web page and then to Device -> Trunk and do a find and make sure that there is a SIP trunk exist with incoming port in associated SIP Trunk security profile configured to be same as what is configured on originating side SIP Trunk destination port. Also, check the network connectivity using the CLI command "utils network ping remote_peer" at originating side. For Local=2, possible reason could be that Unified CM is not be able to create socket connection with remote peer. To fix this issue, if remote peer is Unified CM, then go to remote peer Serviceability web page and then Tools -> Control Center (Feature Services) and make sure Cisco Call Manager service is activated and started. Also, go to remote peer admin web page and then to Device -> Trunk and do a find and make sure that there is a SIP trunk exist with incoming port in associated SIP Trunk security profile configured to be same as what is configured on originating side SIP Trunk destination port. Also, check the network connectivity using "utils network ping remote_peer" at originating side. For Local=3, possible reason could be DNS server is not reachable or DNS is not properly configured to resolve hostname or SRV which is configured on local SIP trunk. To fix this issue, go to OS Administration web page and go to Show -> Network and look into DNS Details and make sure it is correct. If not then configure correct DNS server information using CLI "set network dns primary" command. Also, check the network connectivity with DNS server using "utils network ping "remote_peer" and make sure DNS server is properly configured.

Error Message
CallManager- 4 -SIPTrunkPartiallyISV : Some of the remote peers are not available to handle calls for this SIP Trunk. SIP Trunk Name [String] Unavailable remote peers with Reason Code [String] Available remote peers for this SIP trunk [String]

Explanation Some of the remote peers are not available to handle calls for this SIP trunk. This alarm provides a list of available remote peers and a list of unavailable remote peers and each peer is separated by semi-colon. Each available peer is identified by resolved IP address and port number, and hostname or SRV (if configured on SIP trunk). In the case of unavailable peers, the alarm provides the hostname or SRV (if configured on SIP trunk), resolved IP address, port number, and reason code in the following format: ReasonCodeType=ReasonCode. ReasonCodeType could be based on a SIP response from the remote peer as defined in SIP RFCs (Remote) or based on a reason code provided by Unified CM (Local). Examples of possible reason codes include Remote=503 ("503 Service Unavailable" a standard SIP RFC error code), Remote=408 ("408 Request Timeout" a standard SIP RFC error code), Local=1 (request timeout), Local=2 (local SIP stack is not able to create a socket connection with the remote peer), Local=3 (DNS query failed). For Local=3, IP address in Alarm will be represented as "0" and when dns srv is configured on SIP trunk then port will be represented as "0".

Recommended Action Available peer list is for notification purpose only; no action is required. For each unavailable peer, complete the following steps depending on the reason code provided in this alarm. For Remote=503, possible reasons include 1) route/sip trunk for originating side doesn't exist on remote peer; 2) route/sip trunk for originating side does exist on the remote peer but the port is either used for a SIP phone or a different sip trunk; 3) the remote peer has limited resources and may not be able to handle new calls. For the first cause (item 1), if the remote peer is Unified CM, add a new SIP trunk in Unified CM Administration for the remote peer (Device > Trunk) and make certain that the Destination Address and Destination Port fields are configured to point to the originating host (the originating host is the same node on which this alarm was generated). Also ensure the new SIP trunk has the incoming port in associated SIP Trunk Security Profile configured to be same as originating side SIP Trunk destination port. For the second cause (item 2), if the remote peer is Unified CM, then in Unified CM Administration for the remote peer (Device > Trunk) make certain that incoming port in associated SIP Trunk Security Profile is configured to be same as originating side SIP Trunk destination port. For the third cause (item 3), if the remote peer is administered by a different system administrator, consider communicating the resource issue with the other administrator. For remote=408, possible reason includes remote is running low in resources and unable to process the request. If the remote peer is administered by a different system administrator, consider communicating the resource issue with the other administrator. For Local=1, possible reason could be that no responses has been received for Options request after all retries when transport is configured as UDP in SIP trunk Security Profile assigned to the SIP trunk on originating side. To fix this issue, if the remote peer is Unified CM, then go to remote peer Serviceability web page and then Tools -> Control Center (Feature Services) and make sure Cisco Call Manager service is activated and started. Also, go to remote peer admin web page and then to Device -> Trunk and do a find and make sure that there is a SIP trunk exist with incoming port in associated SIP Trunk security profile configured to be same as what is configured on originating side SIP Trunk destination port. Also, check the network connectivity using the CLI command "utils network ping remote_peer" at originating side. For Local=2, possible reason could be that Unified CM is not be able to create socket connection with remote peer. To fix this issue, if remote peer is Unified CM, then go to remote peer Serviceability web page and then Tools -> Control Center (Feature Services) and make sure Cisco Call Manager service is activated and started. Also, go to remote peer admin web page and then to Device -> Trunk and do a find and make sure that there is a SIP trunk exist with incoming port in associated SIP Trunk security profile configured to be same as what is configured on originating side SIP Trunk destination port. Also, check the network connectivity using "utils network ping remote_peer" at originating side. For Local=3, possible reason could be DNS server is not reachable or DNS is not properly configured to resolve hostname or SRV which is configured on local SIP trunk. To fix this issue, go to OS Administration web page and go to Show -> Network and look into DNS Details and make sure it is correct. If not then configure correct DNS server information using CLI "set network dns primary" command. Also, check the network connectivity with DNS server using "utils network ping "remote_peer" and make sure DNS server is properly configured.

Error Message
CallManager- 3 -ConnectionFailure : Unified CM failed to open a TLS connection for the indicated device. Device Name [String] IP Address [String] Device type [Enum] Device description [String] Reason code [Enum] IPV6Address [String]

Explanation Unified CM failed to open a TLS connection for the indicated device because an incorrect Device Security Mode was configured or an incorrect X.509 Subject Name was configured, or due to an unsupported cipher algorithm

Recommended Action Check the Security Profile of the indicated device. Make certain that Device Security Mode is set to either Authenticated or Encrypted. Make sure that the X.509 Subject Name field has the appropriate content; it should match the Subject Name in the certificate from the peer. Also, Unified CM only supports the AES_128_SHA cipher algorithm; let the peer regenerate its certificate with the correct algorithm.

Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 CISCO_30SP+
2 CISCO_12SP+
3 CISCO_12SP
4 CISCO_12S
5 CISCO_30VIP
6 CISCO_7910
7 CISCO_7960
8 CISCO_7940
9 CISCO_7935
12 CISCO_ATA_186
20 SCCP_PHONE
61 H323_PHONE
72 CTI_PORT
115 CISCO_7941
119 CISCO_7971
131 SIP_TRUNK
255 UNKNOWN
302 CISCO_7989
307 CISCO_7911
308 CISCO_7941G_GE
309 CISCO_7961G_GE
335 MOTOROLA_CN622
336 BASIC_3RD_PARTY_SIP_DEVICE
348 CISCO_7931
358 CISCO_UNIFIED_COMMUNICATOR
365 CISCO_7921
369 CISCO_7906
374 ADVANCED_3RD_PARTY_SIP_DEVICE
375 CISCO_TELEPRESENCE
404 CISCO_7962
412 CISCO_3951
431 CISCO_7937
434 CISCO_7942
435 CISCO_7945
436 CISCO_7965
437 CISCO_7975
446 CISCO_3911
468 CISCO_UNIFIED_MOBILE_COMMUNICATOR
478 CISCO_TELEPRESENCE_1000
479 CISCO_TELEPRESENCE_3000
480 CISCO_TELEPRESENCE_3200
481 CISCO_TELEPRESENCE_500
484 CISCO_7925
493 CISCO_9971
495 CISCO_6921
496 CISCO_6941
497 CISCO_6961
20000 CISCO_7905
30002 CISCO_7920
30006 CISCO_7970
30007 CISCO_7912
30008 CISCO_7902
30016 CISCO_IP_COMMUNICATOR
30018 CISCO_7961
30019 CISCO_7936
30035 IP_STE
Reason code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 AuthenticationError - Device Security Mode is not set to either Authenticated or Encrypted
2 InvalidX509NameInCertificate - Configured X.509 Subject Name doesn't match the name in the certificate from the peer
3 InvalidTLSCipher - Unsupported cipher algorithm used by the peer; Unified CM only supports AES_128_SHA
Error Message
CallManager- 4 -MediaResourceListExhausted : The requested device type is not found in the media resource list or default list or the configured devices are not registered. Media Resource Type [Enum] Media Resource List Name [String]

Explanation The requested device is not configured in the Media Resource Group List or Default List, or it's possible that one or more of the devices that are configured in the Media Resource Group List or Default List are not registered to Cisco Unified Communications Manager

Recommended Action First, go to Cisco Unified CM Administration to check the configuration of the devices that are part of the Media Resource Groups in the Media Resource Group List that was specified in the alarm (Media Resource Group List Configuration window and Media Resource Group Configuration window in Unified CM Administration). Check whether the requested type of device is configured in any of the Media Resource Groups in that particular Media Resource Group List; for RSVP Agent, check whether any media termination point or transcoder is configured in any of the Media Resource Groups in that particular Media Resource Group List. Next, go to the Media Resources menu in Cisco Unified CM Administration to see all the devices of the requested type and then check all the Media Resource Groups (irrespective of whether they belong to the Media Resource Group List for which the alarm is generated) to determine whether the devices belong to at least one Media Resource Group. If there exists some media resources of the requested type which do not belong to any Media Resource Groups, then these devices will belong to the Default List. If the requested type of device is not configured in any of the Media Resource Groups of the Media Resource Group List for which the alarm is generated or in the Default List, add the requested type of device to a Media Resource Group in the specified Media Resource Group List or add it to the Default List. To add a media resource to the Default List, remove the Media Device from all the Media Resource Groups. In general, when a new media device is initially added to Unified CM it will automatically be added to the Default List. This Default List can be used by any device or trunk. But when the media device is added to any particular Media Resource Group it will not be available to the Default List. It can only be used by devices and trunks that are configured with the Media Resource Group List that have that particular Media Resource Group. Note that a particular Media Resource Group can be added to multiple Media Resource Group Lists. If the requested device is properly configured in Cisco Unified CM Administration, check whether the device is registered to Unified CM. To do that go to the Media Resources menu of the requested type of device (such as Annunciator or Conference Bridge or Media Termination Point or Music On Hold Server or Transcoder) and click the Find button. All the devices of that type will display along with their status, device pool, and so on. Check the status field to see whether the device is registered with Unified CM. Note that the display on the status field is not a confirmation that the device is registered to Unified CM. It may happen in a Unified CM cluster that the Publisher can only write to the Unified CM database and suppose the Publisher goes down. Because the Subscriber may not be able to write to the database the devices may still display as registered in Unified CM Administration after they are actually unregistered. However, if the Publisher is down that should generate another alarm with higher priority than this alarm. If the device is not registered, click on the name of that particular device and check the type of the device. Device types including Cisco Conference Bridge Software, Cisco Media Termination Point Software, or that specify a server name that is the same name as a Unified CM node of the cluster indicate that the requested device is a software device and is part of the Cisco IP Voice Media Streaming application. Check to be sure that the IP Voice Media Streaming App service is enabled on that Unified CM node (Cisco Unified Serviceability > Tools > Service Activation) and if it is not enabled, activate the Cisco IP Voice Media Streaming App service. Devices should try to register. You can also check the status of the service to be sure it is showing as Started (Tools > Control Center > Feature Services). If the device type is a type other than Cisco Conference Bridge Software, Cisco Media Termination Point Software, or a server name that is the same name as a Unified CM node, that indicates that the device is an external media resource to Unified CM. Check the configuration (such as Conference Bridge type, MAC address, and conference bridge name in the case of a conference bridge; Media Termination Point name in the case of a Media Termination Point; Transcoder type, MAC address, and Transcoder name in the case of a Transcoder) of the device in Cisco Unified CM Administration and compare it with the configuration of the actual device. To check the configuration of the actual device you may need to refer to the user manual of the media device. The user manual should provide all the details such as connecting to the media device to check the configuration, commands needed to view and update the configuration, and so on. If configuration in Unified CM and on the actual devices are different, make the necessary changes so that the configurations match. If the configuration matches and the device is still not registered, restart the external media device or the service associated with the external media device. If the external media device continues to fail to register with Unified CM, check the network connectivity between Unified CM and the media device.

Media Resource Type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Media termination point
2 Transcoder
3 Conference bridge
9 RSVP agent
Error Message
CallManager- 4 -RouteListExhausted : An available route could not be found in the indicated route list. Route List Name [String]

Explanation An available route could not be found in the indicated route list. This alarm is generated when all members' status is unavailable or busy or when the member is down (out of service), not registered, or busy.

Recommended Action Consider adding additional routes in the indicated route list. For shared line when some phones are not ringing, check the busy trigger and maximum call settings of shared line phones; check whether there are some outstanding calls on that DN. When one shared line phone answers an incoming call, the other shared line phone cannot see that remote-in-use call; check the privacy setting of the phone that answers the call. Try to make a call directly to the member, bypassing the route list, to verify that there is not a device or connectivity issue. If you cannot identify the cause through these steps, gather the CCM (SDI) trace and contact the Cisco Technical Assistance Center; TAC may be able to locate a cause code which may provide additional explanation for this alarm.

Error Message
CallManager- 3 -DeviceTypeMismatch : Device type mismatch between the information contained in the device's TFTP configuration file and what is configured in Unified CM Administration for that device. Database device type [Enum] Device type [Enum] Name of device [String]

Explanation The device type indicated in the device's configuration file does not match the database configuration. This could indicate that a change was made in the database configuration that failed to get updated at the device itself.

Recommended Action Check the Unified CM Database Status report in Cisco Unified Reporting to verify that database replication is working. You can also go to Real-Time Reporting Tool (RTMT) and check the Replication Status in the Database Summary page. If status shows 2, then replication is working. Restart the phone to download a new configuration file from TFTP.

Database device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 CISCO_30SP+
2 CISCO_12SP+
3 CISCO_12SP
4 CISCO_12S
5 CISCO_30VIP
6 CISCO_7910
7 CISCO_7960
8 CISCO_7940
9 CISCO_7935
12 CISCO_ATA_186
20 SCCP_PHONE
61 H323_PHONE
72 CTI_PORT
115 CISCO_7941
119 CISCO_7971
255 UNKNOWN
302 CISCO_7989
307 CISCO_7911
308 CISCO_7941G_GE
309 CISCO_7961G_GE
335 MOTOROLA_CN622
336 BASIC_3RD_PARTY_SIP_DEVICE
348 CISCO_7931
358 CISCO_UNIFIED_COMMUNICATOR
365 CISCO_7921
369 CISCO_7906
374 ADVANCED_3RD_PARTY_SIP_DEVICE
375 CISCO_TELEPRESENCE
404 CISCO_7962
412 CISCO_3951
431 CISCO_7937
434 CISCO_7942
435 CISCO_7945
436 CISCO_7965
437 CISCO_7975
446 CISCO_3911
468 CISCO_UNIFIED_MOBILE_COMMUNICATOR
478 CISCO_TELEPRESENCE_1000
479 CISCO_TELEPRESENCE_3000
480 CISCO_TELEPRESENCE_3200
481 CISCO_TELEPRESENCE_500
484 CISCO_7925
493 CISCO_9971
495 CISCO_6921
496 CISCO_6941
497 CISCO_6961
20000 CISCO_7905
30002 CISCO_7920
30006 CISCO_7970
30007 CISCO_7912
30008 CISCO_7902
30016 CISCO_IP_COMMUNICATOR
30018 CISCO_7961
30019 CISCO_7936
30035 IP_STE
Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 CISCO_30SP+
2 CISCO_12SP+
3 CISCO_12SP
4 CISCO_12S
5 CISCO_30VIP
6 CISCO_7910
7 CISCO_7960
8 CISCO_7940
9 CISCO_7935
12 CISCO_ATA_186
20 SCCP_PHONE
61 H323_PHONE
72 CTI_PORT
115 CISCO_7941
119 CISCO_7971
255 UNKNOWN
302 CISCO_7989
307 CISCO_7911
308 CISCO_7941G_GE
309 CISCO_7961G_GE
335 MOTOROLA_CN622
336 BASIC_3RD_PARTY_SIP_DEVICE
348 CISCO_7931
358 CISCO_UNIFIED_COMMUNICATOR
365 CISCO_7921
369 CISCO_7906
374 ADVANCED_3RD_PARTY_SIP_DEVICE
375 CISCO_TELEPRESENCE
404 CISCO_7962
412 CISCO_3951
431 CISCO_7937
434 CISCO_7942
435 CISCO_7945
436 CISCO_7965
437 CISCO_7975
446 CISCO_3911
468 CISCO_UNIFIED_MOBILE_COMMUNICATOR
478 CISCO_TELEPRESENCE_1000
479 CISCO_TELEPRESENCE_3000
480 CISCO_TELEPRESENCE_3200
481 CISCO_TELEPRESENCE_500
484 CISCO_7925
493 CISCO_9971
495 CISCO_6921
496 CISCO_6941
497 CISCO_6961
20000 CISCO_7905
30002 CISCO_7920
30006 CISCO_7970
30007 CISCO_7912
30008 CISCO_7902
30016 CISCO_IP_COMMUNICATOR
30018 CISCO_7961
30019 CISCO_7936
30035 IP_STE
Error Message
CallManager- 6 -DeviceDnInformation : List of directory numbers (DN) associated with this device. Device Name [String] Device type [Enum] Station Desc [String] Station Dn [String]

Explanation Provides a list of directory numbers (DN) associated with the device

Recommended Action Informational purposes only; no action is required

Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 CISCO_30SP+
2 CISCO_12SP+
3 CISCO_12SP
4 CISCO_12S
5 CISCO_30VIP
6 CISCO_7910
7 CISCO_7960
8 CISCO_7940
9 CISCO_7935
10 CISCO_VGC_PHONE
11 CISCO_VGC_VIRTUAL_PHONE
12 CISCO_ATA_186
20 SCCP_PHONE
21 STATION_PHONE_APPLICATION
30 ANALOG_ACCESS
40 DIGITAL_ACCESS
41 DIGITAL_ACCESS_T1
42 DIGITAL_ACCESS+
43 DIGITAL_ACCESS_WS-X6608
47 ANALOG_ACCESS_WS-X6624
48 VGC_GATEWAY
50 CONFERENCE_BRIDGE
51 CONFERENCE_BRIDGE_HARDWARE
52 CONFERENCE_BRIDGE_HARDWARE_HDV2
53 CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM
61 H323_PHONE
62 H323_GATEWAY
70 MUSIC_ON_HOLD
71 DEVICE_PILOT
72 CTI_PORT
73 CTI_ROUTE_POINT
80 VOICE_MAIL_PORT
83 SOFTWARE_MEDIA_TERMINATION_POINT_HDV2
84 CISCO_MEDIA_SERVER
85 CISCO_VIDEO_CONFERENCE_BRIDGE
90 ROUTE_LIST
100 LOAD_SIMULATOR
110 MEDIA_TERMINATION_POINT
111 MEDIA_TERMINATION_POINT_HARDWARE
112 MEDIA_TERMINATION_POINT_HDV2
113 MEDIA_TERMINATION_POINT_WS-SVC-CMM
115 CISCO_7941
119 CISCO_7971
120 MGCP_STATION
121 MGCP_TRUNK
122 GATEKEEPER
124 7914_14_BUTTON_LINE_EXPANSION_MODULE
125 TRUNK
126 TONE_ANNOUNCEMENT_PLAYER
131 SIP_TRUNK
132 SIP_GATEWAY
133 WSM_TRUNK
134 REMOTE_DESTINATION_PROFILE
254 UNKNOWN_MGCP_GATEWAY
255 UNKNOWN
302 CISCO_7989
307 CISCO_7911
308 CISCO_7941G_GE
309 CISCO_7961G_GE
335 MOTOROLA_CN622
336 BASIC_3RD_PARTY_SIP_DEVICE
358 CISCO_UNIFIED_COMMUNICATOR
365 CISCO_7921
369 CISCO_7906
374 ADVANCED_3RD_PARTY_SIP_DEVICE
375 CISCO_TELEPRESENCE
404 CISCO_7962
412 CISCO_3951
431 CISCO_7937
434 CISCO_7942
435 CISCO_7945
436 CISCO_7965
437 CISCO_7975
20000 CISCO_7905
30002 CISCO_7920
30006 CISCO_7970
30007 CISCO_7912
30008 CISCO_7902
30016 CISCO_IP_COMMUNICATOR
30018 CISCO_7961
30019 CISCO_7936
30027 ANALOG_PHONE
30028 ISDN_BRI_PHONE
30032 SCCP_GATEWAY_VIRTUAL_PHONE
30035 IP_STE
Error Message
CallManager- 6 -StationConnectionError : Station device is closing the connection. Device Name [String] Reason Code [Enum]

Explanation A station device is closing its connection with Unified CM because of the reason that is described in this alarm

Recommended Action Informational purposes only; no action is required. Also, refer to the reason code definition for additional information.

Reason Code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 deviceInitiatedReset - The device has initiated a reset, possibly due to a power cycle or internal error. No action is required; the device will re-register automatically.
1 sccpDeviceThrottling - (SCCP only) The indicated SCCP device has exceeded the maximum number of events allowed per-SCCP device. Events can be phone calls, KeepAlive messages, or excessive SCCP or non-SCCP messages. The maximum number of allowed events is controlled by the Cisco CallManager service parameter, Max Events Allowed. When an individual device exceeds the number configured in that service parameter, Unified CM closes the TCP connection to the device; automatic reregistration generally follows. This action is an attempt to stop malicious attacks on Unified CM or to ward off excessive CPU usage. No action is required; the device will re-register automatically.
2 keepAliveTimeout - Unified CM did not receive a KeepAlive message from the device. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify network connectivity between the device and Unified CM, and verify that CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT). No action is required; the device will re-register automatically.
3 dbChangeNotify - An ApplyConfig command was issued from Unified CM Administration resulting in an unregistration. No action is required; the device will re-register automatically.
4 deviceRegistrationSuperceded - An initial device registration request was received but authentication had not yet completed before a new registration request was received. The first registration request was discarded and re-registration should proceed normally. No action is required; the device will re-register automatically.
5 deepSleep - The device powered off as a result of the Power Save Plus feature that is enabled for this device. When the device powers off, it remains unregistered from Unified CM until the Phone On Time defined in the Product Specific Configuration for this device.
6 registrationSequenceError - (SCCP only) The device requested for a configuration information from the Unified CM at an unexpected time and the required information is no longer stored in the memory. No action is required; the device will re-register automatically.
7 invalidCapabilities - (SCCP only) Unified CM detected an error in the media capabilities reported in the StationCapabilitiesRes message by the device during registration. No action is required; the device will re-register automatically.
8 socketBroken - The TCP connection between the device and the Unified CM is broken. No action is required; the device will re-register automatically once the TCP connection is established.
Error Message
CallManager- 6 -StationAlarm : A station has sent an alarm to Unified CM for pass-through purposes. Protocol [String] TCP ProcessID [String] Device Text [String] Param1 [UInt] Param2 [UInt]

Explanation A station device sent an alarm to Unified CM, which acts as a conduit from the device to generate this alarm

Recommended Action To determine the appropriate action, refer to the specific device type and information passed from the device via this alarm

Error Message
CallManager- 4 -StationEventAlert : A station sent an alert to Unified CM for pass-through purposes. Protocol [String] TCP ProcessID [String] Device Text [String] Param1 [UInt] Param2 [UInt]

Explanation A station device sent an alert to Unified CM, which acts as a conduit from the device to generate this alarm

Recommended Action To determine the appropriate action, refer to the specific device type and information passed from the device via this alarm

Error Message
CallManager- 5 -MGCPGatewayGainedComm : MGCP communication to the gateway has been established. Device Name [String]

Explanation The MGCP gateway has established communication with Unified CM

Recommended Action Notification purposes only; no action is required

Error Message
CallManager- 2 -MGCPGatewayLostComm : MGCP gateway has lost communication with Unified CM. Device Name [String]

Explanation The MGCP gateway is no longer in communication with Unified CM. This could occur because Unified CM received an MGCP unregister signal from the gateway such as RSIP graceful/forced; Unified CM didn't receive the MGCP KeepAlive signal from the gateway; the MGCP gateway didn't response to an MGCP command sent by Unified CM three times; a speed and duplex mismatch exists on the Ethernet port between Unified CM and the MGCP gateway; or the gateway has reset.

Recommended Action Reset the MGCP gateway in an attempt to restore communication with Unified CM; check the speed and duplex settings on the Ethernet port. In the case of an unwanted reset of the gateway which caused communication to be lost, take precautions to ensure that no unauthorized personnel resets the gateway from Cisco Unified CM Administration or via the gateway terminal.

Error Message
CallManager- 2 -StationPortInitError : Station TCP initialization error.

Explanation An error during initialization was encountered

Recommended Action Verify that the Cisco Unified Communications Manager IP address is configured and is not configured as the loop back address for the IP version. Check the SCCP TCP port configuration to be sure the SCCP TCP port is accurately configured (be certain that there are no port conflicts where another port has the same number). If the IP and port settings are correct, collect SDL and SDI traces and contact the Cisco Technical Assistance Center (TAC).

Error Message
CallManager- 3 -DbInfoError : Configuration information may be out of sync for the device and Unified CM database. Name of Device [String]

Explanation Configuration information may be out of sync for the device and Unified CM database

Recommended Action Go to Unified CM Administration and confirm that the device specified in this alarm actually exists in the database. If it does not, add the device. If the device is found in Unified CM Administration, examine the device information on the Device Configuration page for this device to make certain that important device information such as MAC address, device name, device pool configuration, and so on are configured accurately. If you find a discrepancy, correct it and reset the device.

Error Message
CallManager- 3 -DbInfoTimeout : Unified CM did not receive a timely response from the database. Name of Device [String]

Explanation Unified CM requested information about the device specified in this alarm but the Unified CM Administration database did not respond before the internally-configured wait timer in Unified CM expired. Delays can occur because of congestion in accessing the database.

Recommended Action Go to the Cisco Unified Reporting web page, generate a Unified CM Database Status report and verify that the report shows that "Local and publisher databases are accessible" and that "all servers have a good replication status". If database status and DB replications look good, the database may be busy with auto-registrations or other intensive tasks. If you know that auto-registration is proceeding for a large number of devices, wait for it to complete (you can also monitor by watching the CPU level on the database server) and allow the phone to attempt to auto-register again.

Error Message
CallManager- 3 -DbInfoCorrupt : Configuration information may be out of sync for the device and Unified CM database. Name of Device [String]

Explanation Configuration information may be out of sync for the device and Unified CM database

Recommended Action Go to Unified CM Administration and confirm that the device specified in this alarm actually exists in the database. If it does not, add the device. If the device is found in Unified CM Administration, examine the device information on the Device Configuration page for this device to make certain that important device information such as MAC address, device name, device pool configuration, and so on are configured accurately. If you find a discrepancy, correct it and reset the device.

Error Message
CallManager- 4 -NotEnoughChans : Not enough channels. Device Name [String]

Explanation A call attempt was rejected because the requested gateway channel(s) could not be allocated. Some of the more common reasons for the lack of channel to place outgoing calls include: High call traffic volume that has the B-channels in the device fully utilized; B-channels have gone out of service for the following reasons: Taking the channel out of service intentionally to perform maintenance on either the near- or far-end; MGCP gateway returns an error code 501 or 510 for a MGCP command sent from Cisco Unified Communications Manager; MGCP gateway doesn't respond to an MGCP command sent by Unified CM three times; a speed and duplex mismatch exists on the Ethernet port between Unified CM and the MGCP gateway.

Recommended Action Add more gateway resources; Check the Cisco CallManager advanced service parameter, Change B-channel Maintenance Status to determine if the B-channel has been taken out of service intentionally; Check the Q.931 trace for PRI SERVICE message to determine whether a PSTN provider has taken the B-channel out of service; Reset the MGCP gateway; Check the speed and duplex settings on the Ethernet port.

Error Message
CallManager- 6 -DeviceResetInitiated : Device reset initiated on the specified device. Device name [String] Product type [String] Device type [Enum]

Explanation This alarm occurs when a device is reset via the Reset button in Cisco Unified CM Administration. Reset may cause the device to shut down and come back in service. A device can be reset only when it is registered with Unified CM.

Recommended Action Informational purposes only; no action is required

Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
10 CISCO_VGC_PHONE
11 CISCO_VGC_VIRTUAL_PHONE
30 ANALOG_ACCESS
40 DIGITAL_ACCESS
42 DIGITAL_ACCESS+
43 DIGITAL_ACCESS_WS-X6608
47 ANALOG_ACCESS_WS-X6624
48 VGC_GATEWAY
50 CONFERENCE_BRIDGE
51 CONFERENCE_BRIDGE_HARDWARE
52 CONFERENCE_BRIDGE_HARDWARE_HDV2
53 CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM
62 H323_GATEWAY
70 MUSIC_ON_HOLD
71 DEVICE_PILOT
73 CTI_ROUTE_POINT
80 VOICE_MAIL_PORT
83 SOFTWARE_MEDIA_TERMINATION_POINT_HDV2
84 CISCO_MEDIA_SERVER
85 CISCO_VIDEO_CONFERENCE_BRIDGE
90 ROUTE_LIST
100 LOAD_SIMULATOR
110 MEDIA_TERMINATION_POINT
111 MEDIA_TERMINATION_POINT_HARDWARE
112 MEDIA_TERMINATION_POINT_HDV2
113 MEDIA_TERMINATION_POINT_WS-SVC-CMM
120 MGCP_STATION
121 MGCP_TRUNK
122 GATEKEEPER
124 7914_14_BUTTON_LINE_EXPANSION_MODULE
125 TRUNK
126 TONE_ANNOUNCEMENT_PLAYER
131 SIP_TRUNK
132 SIP_GATEWAY
133 WSM_TRUNK
134 REMOTE_DESTINATION_PROFILE
227 7915_12_BUTTON_LINE_EXPANSION_MODULE
228 7915_24_BUTTON_LINE_EXPANSION_MODULE
229 7916_12_BUTTON_LINE_EXPANSION_MODULE
230 7916_24_BUTTON_LINE_EXPANSION_MODULE
232 CKEM_36_BUTTON_LINE_EXPANSION_MODULE
254 UNKNOWN_MGCP_GATEWAY
255 UNKNOWN
30027 ANALOG_PHONE
30028 ISDN_BRI_PHONE
30032 SCCP_GATEWAY_VIRTUAL_PHONE
Error Message
CallManager- 6 -EndPointResetInitiated : Endpoint reset initiated on the specified endpoint. Device name [String] Product type [String] Device type [Enum]

Explanation This alarm occurs when a device is reset via the Reset button in Cisco Unified CM Administration. Reset causes the device to shut down and come back in service. A device can be reset only when it is registered with Unified CM.

Recommended Action Informational purposes only; no action is required

Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 CISCO_30SP+
2 CISCO_12SP+
3 CISCO_12SP
4 CISCO_12S
5 CISCO_30VIP
6 CISCO_7910
7 CISCO_7960
8 CISCO_7940
9 CISCO_7935
12 CISCO_ATA_186
20 SCCP_PHONE
61 H323_PHONE
72 CTI_PORT
115 CISCO_7941
119 CISCO_7971
255 UNKNOWN
302 CISCO_7989
307 CISCO_7911
308 CISCO_7941G_GE
309 CISCO_7961G_GE
335 MOTOROLA_CN622
336 BASIC_3RD_PARTY_SIP_DEVICE
348 CISCO_7931
358 CISCO_UNIFIED_COMMUNICATOR
365 CISCO_7921
369 CISCO_7906
374 ADVANCED_3RD_PARTY_SIP_DEVICE
375 CISCO_TELEPRESENCE
404 CISCO_7962
412 CISCO_3951
431 CISCO_7937
434 CISCO_7942
435 CISCO_7945
436 CISCO_7965
437 CISCO_7975
446 CISCO_3911
468 CISCO_UNIFIED_MOBILE_COMMUNICATOR
478 CISCO_TELEPRESENCE_1000
479 CISCO_TELEPRESENCE_3000
480 CISCO_TELEPRESENCE_3200
481 CISCO_TELEPRESENCE_500
484 CISCO_7925
493 CISCO_9971
495 CISCO_6921
496 CISCO_6941
497 CISCO_6961
20000 CISCO_7905
30002 CISCO_7920
30006 CISCO_7970
30007 CISCO_7912
30008 CISCO_7902
30016 CISCO_IP_COMMUNICATOR
30018 CISCO_7961
30019 CISCO_7936
30035 IP_STE
Error Message
CallManager- 6 -DeviceRestartInitiated : Device restart initiated or Apply Config initiated on the specified device. Device name [String] Product type [String] Device type [Enum]

Explanation This alarm occurs when a device is restarted via the Restart button in Cisco Unified CM Administration window or when a system administrator presses the Apply Config button for a device that does not support conditional restart. Restart causes the device to unregister, receive updated configuration, and re-register with Cisco Unified Communications Manager (Unified CM) without shutting down. A device can be restarted only when it is registered with Unified CM.

Recommended Action Informational purposes only; no action is required

Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
10 CISCO_VGC_PHONE
11 CISCO_VGC_VIRTUAL_PHONE
30 ANALOG_ACCESS
40 DIGITAL_ACCESS
42 DIGITAL_ACCESS+
43 DIGITAL_ACCESS_WS-X6608
47 ANALOG_ACCESS_WS-X6624
48 VGC_GATEWAY
50 CONFERENCE_BRIDGE
51 CONFERENCE_BRIDGE_HARDWARE
52 CONFERENCE_BRIDGE_HARDWARE_HDV2
53 CONFERENCE_BRIDGE_HARDWARE_WS-SVC-CMM
62 H323_GATEWAY
70 MUSIC_ON_HOLD
71 DEVICE_PILOT
73 CTI_ROUTE_POINT
80 VOICE_MAIL_PORT
83 SOFTWARE_MEDIA_TERMINATION_POINT_HDV2
84 CISCO_MEDIA_SERVER
85 CISCO_VIDEO_CONFERENCE_BRIDGE
90 ROUTE_LIST
100 LOAD_SIMULATOR
110 MEDIA_TERMINATION_POINT
111 MEDIA_TERMINATION_POINT_HARDWARE
112 MEDIA_TERMINATION_POINT_HDV2
113 MEDIA_TERMINATION_POINT_WS-SVC-CMM
120 MGCP_STATION
121 MGCP_TRUNK
122 GATEKEEPER
124 7914_14_BUTTON_LINE_EXPANSION_MODULE
125 TRUNK
126 TONE_ANNOUNCEMENT_PLAYER
131 SIP_TRUNK
132 SIP_GATEWAY
133 WSM_TRUNK
134 REMOTE_DESTINATION_PROFILE
227 7915_12_BUTTON_LINE_EXPANSION_MODULE
228 7915_24_BUTTON_LINE_EXPANSION_MODULE
229 7916_12_BUTTON_LINE_EXPANSION_MODULE
230 7916_24_BUTTON_LINE_EXPANSION_MODULE
232 CKEM_36_BUTTON_LINE_EXPANSION_MODULE
254 UNKNOWN_MGCP_GATEWAY
255 UNKNOWN
30027 ANALOG_PHONE
30028 ISDN_BRI_PHONE
30032 SCCP_GATEWAY_VIRTUAL_PHONE
Error Message
CallManager- 6 -EndPointRestartInitiated : Endpoint restart initiated or Apply Config initiated on the specified endpoint. Device name [String] Product type [String] Device type [Enum]

Explanation This alarm occurs when an endpoint is restarted via the Restart button in Cisco Unified CM Administration window or when a system administrator presses the Apply Config button for an endpoint that does not support conditional restart. Restart causes the endpoint to unregister, receive an updated configuration file, and re-register with Cisco Unified Communications Manager (Unified CM) without shutting down. An endpoint can be restarted only when it is registered with Unified CM.

Recommended Action Informational purposes only; no action is required

Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 CISCO_30SP+
2 CISCO_12SP+
3 CISCO_12SP
4 CISCO_12S
5 CISCO_30VIP
6 CISCO_7910
7 CISCO_7960
8 CISCO_7940
9 CISCO_7935
12 CISCO_ATA_186
20 SCCP_PHONE
61 H323_PHONE
72 CTI_PORT
115 CISCO_7941
119 CISCO_7971
255 UNKNOWN
302 CISCO_7989
307 CISCO_7911
308 CISCO_7941G_GE
309 CISCO_7961G_GE
335 MOTOROLA_CN622
336 BASIC_3RD_PARTY_SIP_DEVICE
348 CISCO_7931
358 CISCO_UNIFIED_COMMUNICATOR
365 CISCO_7921
369 CISCO_7906
374 ADVANCED_3RD_PARTY_SIP_DEVICE
375 CISCO_TELEPRESENCE
404 CISCO_7962
412 CISCO_3951
431 CISCO_7937
434 CISCO_7942
435 CISCO_7945
436 CISCO_7965
437 CISCO_7975
446 CISCO_3911
468 CISCO_UNIFIED_MOBILE_COMMUNICATOR
478 CISCO_TELEPRESENCE_1000
479 CISCO_TELEPRESENCE_3000
480 CISCO_TELEPRESENCE_3200
481 CISCO_TELEPRESENCE_500
484 CISCO_7925
493 CISCO_9971
495 CISCO_6921
496 CISCO_6941
497 CISCO_6961
20000 CISCO_7905
30002 CISCO_7920
30006 CISCO_7970
30007 CISCO_7912
30008 CISCO_7902
30016 CISCO_IP_COMMUNICATOR
30018 CISCO_7961
30019 CISCO_7936
30035 IP_STE
Error Message
CallManager- 6 -DeviceApplyConfigInitiated : An Apply Config action was initiated by a system administrator for the specified device. Device name [String] Product type [String] Device type [Enum]

Explanation This alarm occurs when a system administrator presses the Apply Config button in Cisco Unified Communications Manager (Unified CM). The Apply Config button initiates a conditional restart on devices that support conditional restart. This button triggers the system to determine if any relevant configuration has changed for the device. If the configuration changes can be applied dynamically, they are made without service interruption. If a change requires that the device reregister with Unified CM, reregistration occurs automatically. If a change requires a restart, the device will be automatically restarted. If the load ID for a device changes, the device will initiate a background download of the new firmware. The new firmware can then be applied immediately or at a later time. For phones and devices that do not support conditional restart, clicking Apply Config causes these devices to restart.

Recommended Action Informational purposes only; no action is required

Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
493 CISCO_9971
Error Message
CallManager- 4 -DaTimeOut : The digit analysis component in Unified CM has timed out.

Explanation The digit analysis component in Unified CM has timed out. This can occur because Unified CM is busy and the resulting delay in processing request and response messages caused the digit analysis component to time out.

Recommended Action In the Service Parameter Configuration window in Cisco Unified CM Administration, check the Cisco CallManager service parameter, Digit Analysis Timer, to confirm that the default value is in use. Use RTMT to monitor the system resources and correct any system issues that might be contributing to high CPU utilization on Unified CM.

Error Message
CallManager- 5 -MaxCallDurationTimeout : Maximum call duration timer has expired. Maximum Call Duration (minutes) [UInt] Originating Device name [String] Destination Device name [String] Call start time [UInt] Call stop time [UInt] Calling Party Number [String] Called Party Number [String]

Explanation An active call was cleared because the amount of time specified in the Maximum Call Duration Timer service parameter has elapsed. If the allowed call duration is too short, you can increase the value. If you do not want a limit on the duration of an active call, you can disable the limit. If the duration is correct but you did not expect a call to ever exceed that duration, check the trace information around the time that this alarm occurred to try to determine if a gateway port had failed to release a call.

Recommended Action If the duration of the call is too short, increase the value in the Cisco CallManager service parameter or disable the maximum duration by setting the Maximum Call Duration Timer parameter to zero. If you suspect a hung gateway port, check the trace files around the time that this alarm occurred to search for the gateway that was involved in the call, then check the status of that gateway to determine if all ports are functioning normally.

Error Message
CallManager- 6 -MaxHoldDurationTimeout : Maximum Hold Duration Timer expired. Maximum Hold Duration (minutes) [Int] Originating Device Name [String] Destination Device Name [String] Hold start time [UInt] Hold stop time [UInt] Calling Party Number [String] Called Party Number [String]

Explanation A held call was cleared because the amount of time specified in the Maximum Hold Duration Timer service parameter has elapsed. If the allowed call-on-hold duration is too short, you can increase the value. If you do not want a limit on the duration of a held call, you can disable the limit.

Recommended Action If the duration of the hold time is too short, increase the value in the Cisco CallManager service parameter or disable the maximum duration by setting the Maximum Hold Duration Timer parameter to zero

Error Message
CallManager- 2 -TimerThreadSlowed : Timer thread has slowed beyond acceptable limits.

Explanation Verification of the Unified CM internal timing mechanism has slowed beyond acceptable limits. This generally indicates an increased load on the system or an internal anomaly.

Recommended Action If this alarm occurs at the same general day or time, or if it occurs with increasing frequency, collect all system performance data in Real-Time Monitoring Tool as well as all trace information for the 30 minutes prior to the time that this alarm occurred and contact the Cisco Technical Assistance Center (TAC)

Error Message
CallManager- 6 -DatabaseDefaultsRead : Database default information was read successfully.

Explanation Database default information was read successfully; this alarm will be removed in Unified CM release 10.0(0).

Recommended Action Informational purposes only; no action is required

Error Message
CallManager- 3 -DeviceInitTimeout : Device initialization timed out due to internal error. Device Name [String] Protocol [String] Side Number [UInt]

Explanation A device initialization timeout occurred because the device did not respond to an initialize request. If this alarm occurs in tandem with a configuration change, this may not indicate a problem unless this alarm recurs.

Recommended Action If you are making a configuration change around the time that this alarm occurred, determine whether the problem still exists by calling the phone or placing a call through the trunk or gateway. If the call fails, reset the device. If the alarm recurs after resetting the device, review the System Reports provided in the Cisco Unified Reporting tool, specifically the Unified CM Database Status report, for any anomalous activity. You can also go to Real-Time Reporting Tool (RTMT) and check the Replication Status in the Database Summary page. If status shows 2, then replication is working. Check network connectivity to the server that is running the database.

Error Message
CallManager- 3 -NumDevRegExceeded : The allowed number of registered devices has been exceeded. Maximum Devices [Int]

Explanation The allowed number of registered devices, as controlled by the Cisco CallManager service parameter Maximum Number of Registered Devices, has been exceeded

Recommended Action If you did not expect to exceed the number of devices and you have auto-registration enabled, go to Device > Phones in Cisco Unified CM Administration and search for phones starting with "auto". If you see any unexpected devices which may not belong in the system (such as intruder devices) locate that device using it's IP address and remove it from the system. Or, if your licenses and system resources allow, increase the value in the Cisco CallManager service parameter, Maximum Number of Registered Devices.

Error Message
CallManager- 5 -CallManagerOnline : Cisco CallManager service is online. CCM Version [String]

Explanation The Cisco CallManager service has completed initialization and is online

Recommended Action Informational purposes only; no action is required

Error Message
CallManager- 4 -MtpNoMoreResourcesAvailable : MTP or transcoder allocation failed. Media Resource List Name [String]

Explanation The alarm occurs when allocation of a media termination point (MTP) or transcoder fails for all the registered MTPs or transcoders belonging to the Media Resource Group List and Default List. Each MTP or transcoder may fail for different reasons. Following are some of the reasons that could cause an MTP or transcoder allocation to fail: a capability mismatch between the device endpoint and MTP/transcoder, codec mismatch between the endpoint and the MTP/transcoder; a lack of available bandwidth between the endpoint and the MTP/transcoder; or because the MTP/transcoders resources are already in use. A capability mismatch may be due to the MTP/transcoder not supporting one or more of the required capabilities for the call such as Transfer Relay Point (which is needed for QoS or firewall traversal), RFC 2833 DTMF (which is necessary when one side of the call does not support RFC 2833 format for transmitting DTMF digits and the other side must receive the DTMF digits in RFC 2833 format, resulting in conversion of the DTMF digits), RFC 2833 DTMF passthrough (in this case, the MTP or transcoder does not need to convert the DTMF digits from one format to another format but it needs to receive DTMF digits from one endpoint and transmit them to the other endpoint without performing any modifications), passthrough (where no codec conversion will occur, meaning the media device will receive media streams in any codec format and transmit them to the other side without performing any codec conversion), IPv4 to IPv6 conversion (when one side of the call supports only IPv4 and the other side of the call supports only IPv6 and so an MTP needs to be inserted to perform the necessary conversion between IPv4 and IPv6 packets), or multimedia capability (if a call involving video and/or data in addition to audio requires insertion of an MTP or transcoder then the MTP/transcoder which supports multimedia will be inserted).

Recommended Action If the MTP or transcoder allocation is failing due to a capability mismatch, it's possible that the media device does not support the capability (such as IPv4 to IPv6 conversion, passthrough) or the capability might not be configured in the device. Please check the user guide and documentation of the media device to make sure that device supports all the necessary capabilities. Also, caution should be taken if all the MTP or transcoders are configured with all the supported capabilities. There are certain capabilities (such as RFC 2833 DTMF or RFC 2833 DTMF passthrough or passthrough) which could be supported by most of the MTPs or transcoders and there may be certain capabilities (such as IPv4 to IPv6 conversion and vice versa or Transfer Relay Point or multimedia capability) which can be supported by only by a single MTP or transcoder depending on the devices that you have. For example, you may have IP phones that support only IPv4 protocol and there may also be IP phones that support only IPv6 protocol. To make a call between IPv4-only and IPv6-only phones, you need to have an MTP configured to perform the conversion of IPv4 to IPv6 and vice versa. However, suppose all the MTPs or transcoders are configured with all the supported capabilities and only one MTP supports IPv4 to IPv6 conversion; if this MTP is configured with all the supported capabilities (which all the other MTPs or transcoders in the same MRGL or default MRGL also support) it may happen that this MTP can get allocated for Transfer Relay Point or RFC 2833 DTMF or RFC 2833 DTMF passthrough or passthrough instead. As a result, when the need arises for IPv4 to IPv6 conversion (which other MTPs or transcoders in the same MRGL or default MRGL do not support), all the resources of MTP may be in use and the IPv4 to IPv6 conversion may fail. To avoid this kind of problem, setting the priority of the media resources may be a good idea. This can be done only in the Media Resource Group List and not in the Default List of the media resources. In any Media Resource Group List all the Media Resource Groups have different priorities; during allocation the first Media Resource Group is always checked for availability of the requested type of the media devices. The first Media Resource Group in the Media Resource Group List will have the highest priority, then the second one, and so on. To check all the Media Resource Groups and their priority go the Media Resources and Media Resource Group List of Cisco Unified CM Administration page and click the appropriate Media Resource Group List and check the Selected Media Resource Groups; the priority decreases from top to bottom. So, the MTP or transcoder that you want to be selected for the most basic functionalities should be positioned in the higher priority Media Resource Groups whereas the ones with more rare functionality should be positioned in the Media Resource Groups with lower priority. MTP/transcoder allocation may fail due to codec mismatch between the endpoint and the MTP/transcoder. A solution may be to configure the MTP/transcoder with all the supported codecs (as specified in the user guide of the MTP/transcoder), but be aware that doing so might result in too much bandwidth being allocated for calls. You'll need to weigh different factors such as the total amount of available bandwidth, the average number of calls, approximate bandwidth use per call (not involving MTP/transcoder), and so on, and accordingly calculate the maximum bandwidth that can be allocated per call involving an MTP/transcoder and take that into consideration when configuring the supported codecs in the MTPs and transcoders. It's a good idea to configure the media devices with all the supported codecs and set the region bandwidths to restrict too much bandwidth usage (refer to the Unified CM documentation for details on region and location settings). Also, there may be a codec mismatch between the endpoint and the MTP/transcoders after considering the region bandwidth between the MTP/transcoder and the endpoint. Increasing the region bandwidth may be a solution to the problem, but again, that decision should be made after careful consideration of the amount of bandwidth you're willing to allocate per call between the set of regions. Another possible cause that an MTP/transcoder did not get allocated is because there was not enough available bandwidth for the call. This can happen if the MTP/transcoder and endpoint belong to different locations and the bandwidth that is set between the locations is already in use by other calls. Examine the bandwidth requirements in your deployment to determine whether bandwidth between the locations can be increased. However, please note that increasing the bandwidth between these two locations means that you may need to reduce the bandwidth between other locations. Refer to the System Guide, SRNDs, and related Unified CM documentation for more details. Be aware that reducing the bandwidth or removing the higher bandwidth codecs from configuration may result in poor voice quality during call. Consider increasing the total amount of network bandwidth available. Finally, if MTP or transcoder allocation fails due to capability mismatch or all the resources being in use, consider installing additional MTP or transcoder devices.

Error Message
CallManager- 4 -MohNoMoreResourcesAvailable : MOH resource allocation failed. Media Resource List Name [String]

Explanation This alarm occurs when allocation of Music On Hold fails for all the registered MOH servers belonging to the Media Resource Group List and Default List. Each MOH server may fail for different reasons. Following are some of the reasons that could cause an MOH server allocation to fail: All the resources of MOH server are already in use; No matching codecs or capability mismatch between the held party and MOH server; Not enough bandwidth between the held party and MOH source; No audio stream available for the MOH server.

Recommended Action If all the resources of the MOH servers are already in use, check to be sure that all the MOH servers that belong to the Media Resource Groups of the indicated Media Resource Group List and Default List are configured and registered in all the applicable Unified CM nodes. To check the registration status go to the Media Resources > Music On Hold Server menu and click the Find button. It will display all the MOH servers with their status, device pool, and so on. Check the status field to discover whether it is registered with Unified CM. Note that the display on the status field is not a confirmation that the device is registered to Unified CM. It may happen in a Unified CM cluster that the Publisher can only write to the Unified CM database and the Publisher goes down. Because the Subscriber may not be able to write to the database, the devices may still display as registered in Unified CM Administration after they are actually unregistered. However, if the Publisher is down that should generate another alarm with higher priority than this alarm. The MOH allocation can also fail due to codec mismatch or capability mismatch between the endpoint and the MOH server. If there is a codec mismatch or capability mismatch (such as the endpoint using IPv6 addressing but MOH server supporting only IPv4), an MTP or transcoder should be allocated. If the MTP or transcoder is not allocated, either MediaResourceListExhausted (with Media Resource Type as media termination point or transcoder) or MtpNoMoreResourcesAvailable alarm will be generated for the same Media Resource Group List and you should first concentrate on that alarm. The MOH allocation may even fail after checking the region bandwidth between the regions to which the held party belongs and the region to which the MOH server belongs. Increasing the region bandwidth may be a solution to the problem, but that decision should be made after careful consideration of the amount of bandwidth you're willing to allocate per call between the set of regions. You'll need to weigh different factors such as the total amount of available bandwidth, the average number of calls, the average number of calls using the MOH servers, approximate bandwidth use per call, and so on, and accordingly calculate the region bandwidth. Another possible cause is that the bandwidth needed for the call may not be available. This can occur if the MOH server and endpoint belong to different locations and the bandwidth that is set between the locations is already in use by other calls. Examine the bandwidth requirements in your deployment to determine whether bandwidth between the locations can be increased. However, please note that increasing the bandwidth between these two locations means that you may need to reduce the bandwidth between other locations. Refer to the System Guide, SRNDs, and related Unified CM documentation for more details. Be aware that reducing the bandwidth or removing the higher bandwidth codecs from configuration may result in poor voice quality during call. Consider increasing the total amount of network bandwidth. Another reason for the MOH allocation failure may be due to meeting the maximum number of unicast or multicast streams supported by the MOH server. If all available streams are already in use, none can be allocated. Finally, check the Music On Hold Audio Source Configuration window in Cisco Unified CM Administration to confirm that at least one audio source is configured. If an audio source is not configured, upload an audio file and then configure the audio source in Cisco Unified CM Administration (refer to the Music On Hold configuration documentation for specific details).

Error Message
CallManager- 4 -ConferenceNoMoreResourcesAvailable : Conference resource allocation failed. Media Resource List Name [String]

Explanation Conference resource allocation failed for one or more of the following reasons: The required number of conference resources were not available; For an IOS-based conference bridge, the number of participants to be added to the conference bridge exceeded the maximum number of participants allowed per conference; No lower precedence conference was available for preemption although MLPP preemption was enabled; A lower-precedence conference bridge was not preempted

Recommended Action For IOS-based conference bridges, make sure that the maximum number of participants configured in a conference bridge does not exceed the number of participants allowed per conference; please check the IOS-based conference bridge user manual for limitations on the number of participants. Also, be sure to educate end users about the maximum number of participants allowed. For IOS-based and non-IOS-based, consider installing additional conference resources.

Error Message
CallManager- 4 -AnnunciatorNoMoreResourcesAvailable : Annunciator resource allocation failed. Media Resource List Name [String]

Explanation Annunciator resource allocation failed for one or more of the following reasons: All Annunciator resources are already in use; There was a codec or capability mismatch (such as the endpoint using one type of IP addressing such as IPv6, while the Annunciator supports only IPv4) between the endpoint and the Annunciator resource; Not enough bandwidth existed between the endpoint and the Annunciator.

Recommended Action If all the resources of the Annunciator are already in use, check to be sure that all the Annunciators that belong to the Media Resource Groups of the indicated Media Resource Group List and Default List are configured and registered in all the applicable Unified CM nodes of the cluster. To check the registration status go to Media Resources > Annunciator and click the Find button. It will display all the Annunciators with their status, device pool, and so on. Check the status field to see whether it is registered with Unified CM. Note that the display on the status field is not a confirmation that the device is registered to Unified CM. It may happen in a Unified CM cluster that the Publisher can only write to the Unified CM database before the Publisher goes down. Because the Subscriber may not be able to write to the database, the devices may still display registered in Unified CM Administration after they are actually unregistered. However, if the Publisher is down that should generate another alarm with higher priority than this alarm. The Annunciator allocation can fail due to codec mismatch or capability mismatch between the endpoint and the Annunciator. If there is a codec mismatch or capability mismatch (such as the endpoint using IPv6 addressing but Annunciator supporting only IPv4), an MTP or transcoder should be allocated. If the MTP or transcoder is not allocated, either MediaResourceListExhausted (with Media Resource Type as media termination point or transcoder) or MtpNoMoreResourcesAvailable alarm will be generated for the same Media Resource Group List and you should first concentrate on that. The Annunciator allocation may even fail after checking the region bandwidth between the regions to which the held party belongs and the region to which the Annunciator belongs. Increasing the region bandwidth may be a solution to the problem, but that decision should be made after careful consideration of the amount of bandwidth you're willing to allocate per call between the set of regions. You'll need to weigh different factors such as the total amount of available bandwidth, the average number of calls, the average number of calls using the Annunciator, approximate bandwidth use per call, and so on, and accordingly calculate the region bandwidth. Another possible cause is that the bandwidth needed for the call may not be available. This can happen if the Annunciator and endpoint belong to different locations and the bandwidth that is set between the locations is already in use by other calls. Examine the bandwidth requirements in your deployment to determine whether bandwidth between the locations can be increased. However, note that increasing the bandwidth between these two locations means that you may need to reduce the bandwidth between other locations. Refer to the System Guide, SRNDs, and related Unified CM documentation for more details. Be aware that reducing the bandwidth or removing the higher bandwidth codecs from configuration may result in poor voice quality during call. Consider increasing the total amount of network bandwidth.

Error Message
CallManager- 3 -RsvpNoMoreResourcesAvailable : RSVP Agent resource allocation failed. Media Resource List Name [String]

Explanation This alarm occurs when allocation of an RSVP Agent fails for all the registered RSVP Agents (RSVP Agents are basically MTPs or transcoder devices which provide RSVP functionalities) belonging to the Media Resource Group List and Default List. Each RSVP Agent may fail for different reasons. Following are some of the reasons that could cause an RSVP Agent allocation to fail: Available MTP/transcoders do not support RSVP functionality; A capability mismatch between the device endpoint and MTP/transcoder, Codec mismatch between the endpoint and the MTP/transcoder; A lack of available bandwidth between the endpoint and the MTP/transcoder; Or because the MTP/transcoder resources are already in use. A capability mismatch may be due to the MTP/transcoder not supporting one or more of the required capabilities for the call such as Transfer Relay Point (which is needed for QoS or firewall traversal), RFC 2833 DTMF (which is necessary when one side of the call does not support RFC 2833 format for transmitting DTMF digits and the other side must receive the DTMF digits in RFC 2833 format, resulting in conversion of the DTMF digits), RFC 2833 DTMF passthrough (in this case, the MTP or transcoder does not need to convert the DTMF digits from one format to another format but it needs to receive DTMF digits from one endpoint and transmit them to the other endpoint without performing any modifications), passthrough (where no codec conversion will occur, meaning the media device will receive media streams in any codec format and transmit them to the other side without performing any codec conversion), IPv4 to IPv6 conversion (when one side of the call supports only IPv4 and the other side of the call supports only IPv6 and so MTP needs to be inserted to perform the necessary conversion between IPv4 and IPv6 packets), or multimedia capability (if a call involving video and/or data in addition to audio requires insertion of an MTP or transcoder then the MTP/transcoder which supports multimedia will be inserted).

Recommended Action RSVP Agents are basically Cisco IOS MTPs or transcoder devices which provide RSVP functionalities. Check the user manual of the configured MTPs and transcoders to see whether they support RSVP functionality. If none of them support RSVP functionality either they need to be upgraded (if an upgraded version supports RSVP functionality) or additional MTP or transcoders need to be installed which support RSVP functionality. If the RSVP Agent (MTP or transcoder) allocation is failing due to a capability mismatch, it's possible that the media device does not support the requested capability (such as IPv4 to IPv6 conversion, passthrough) or the capability might not be configured in the device. Please check the user guide and documentation of the media device to make sure that device supports all the necessary capabilities. Also, caution should be taken if all the MTP or transcoders are configured with all the supported capabilities. There are certain capabilities (such as RFC 2833 DTMF or RFC 2833 DTMF passthrough or passthrough) which could be supported by most of the MTPs or transcoders and there may be certain capabilities (such as IPv4 to IPv6 conversion and vice versa or RSVP Agent functionality or Transfer Relay Point or multimedia capability) which can be supported by only by a single MTP or transcoder depending on the devices that you have. For example, you may have end devices belonging to different locations and may need to reserve the bandwidth only between two locations; calls between other locations may not need to reserve the bandwidth. Now, suppose all the MTPs or transcoders are configured with all the supported capabilities and only one MTP/transcoder supports RSVP functionality; if this MTP/transcoder is configured with all the supported capabilities (which all the other MTPs or transcoders in the same MRGL or default MRGL also support) it may happen that this MTP can get allocated for Transfer Relay Point or RFC 2833 DTMF or RFC 2833 DTMF passthrough or passthrough instead. As a result, when a need arises to reserve the bandwidth (which other MTPs or transcoders in the same MRGL or default MRGL do not support), all the resources of this MTP/transcoder may be in use and the RSVP Agent allocation may fail. To avoid this situation, set the priority of the media resources appropriately. This can only be done in the Media Resource Group List and not in the Default List of the media resources. In any Media Resource Group List all the Media Resource Groups have different priorities and during allocation the first Media Resource Group is checked for availability of the requested type of the media devices. The first Media Resource Group in the Media Resource Group List will have the highest priority, then the second one and so on. To check all the Media Resource Groups and their priority go the Media Resources and Media Resource Group List in Cisco Unified CM Administration and click the appropriate Media Resource Group List, then check the Selected Media Resource Groups; the priority decreases from top to bottom. Position the MTP or transcoder that you want to be selected for the basic functionalities in the higher priority Media Resource Groups whereas the ones with more rare functionality can be positioned in the Media Resource Groups with lower priority. RSVP Agent allocation may fail due to codec mismatch between the endpoint and the RSVP Agent or MTP/transcoder. A solution may be to configure the MTP/transcoder with all the supported codecs (as specified in the user guide of the MTP/transcoder), but be aware that doing so might result in too much bandwidth being allocated for calls. You'll need to weigh different factors such as the total amount of available bandwidth, the average number of calls, approximate bandwidth use per call (not involving MTP/transcoder), and so on, and accordingly calculate the maximum bandwidth that can be allocated per call involving an MTP/transcoder and take that into consideration when configuring the supported codecs in the MTPs and transcoders. A good idea is to configure the media devices with all the supported codecs and set the region bandwidths to restrict too much bandwidth usage (refer to the Unified CM documentation for details on region and location settings). Also, there may be a codec mismatch between the endpoint and the MTP/transcoders after considering the region bandwidth between the MTP/transcoder and the endpoint. Increasing the region bandwidth may be a solution to the problem, but that decision should be made after careful consideration of the amount of bandwidth you're willing to allocate per call between the set of regions. Another possible cause that an MTP/transcoder did not get allocated is because there was not enough available bandwidth for the call. This can happen if the MTP/transcoder and endpoint belong to different locations and the bandwidth that is set between the locations is already in use by other calls. Examine the bandwidth requirements in your deployment to determine whether bandwidth between the locations can be increased. However, note that increasing the bandwidth between these two locations means that you may need to reduce the bandwidth between other locations. Refer to the System Guide, SRNDs, and related Unified CM documentation for more details. Be aware that reducing the bandwidth or removing the higher bandwidth codecs from configuration may result in poor voice quality during call. Consider increasing the total amount of network bandwidth. Finally, if RSVP Agent allocation fails due to MTP/transcoder not supporting RSVP functionality or capability mismatch or all the resources being in use, consider installing additional MTP or transcoder devices which support RSVP functionality.

Error Message
CallManager- 2 -MaxCallsReached : Maximum calls of simultaneous calls in this node has been reached. Description [Int]

Explanation The maximum number of simultaneous connections in a Unified CM node has been reached. This is an internally-set value and when it is exceeded, Unified CM starts throttling calls to keep the number of calls below the internal threshold.

Recommended Action In the Real-Time Monitoring Tool, check the CallsActive counter in the Cisco CallManager object for an unusually high number of calls. Internal mechanisms will attempt to correct this condition. If this alarm continues to occur, collect existing SDL and CCM trace files and check to be sure that CM Services trace collection in Cisco Unified CM Serviceability is set to Detailed level.

Error Message
CallManager- 1 -DBLException : An error occurred while performing database activities. ErrorCode [Int] ExceptionString [String]

Explanation A severe database layer interface error occurred. Possible causes for this include the database being unreachable or down or a DNS error.

Recommended Action Review the System Reports provided in the Cisco Unified Reporting tool, specifically the Unified CM Database Status report, for any anomalous activity. You can also go to Real-Time Reporting Tool (RTMT) and check the Replication Status in the Database Summary page. If status shows 2, then replication is working. Check network connectivity to the server that is running the database. If your system uses DNS, check the DNS configuration for any errors. If the cause is still not identified, collect SDL and SDI traces and contact the Cisco Technical Assistance Center (TAC).

Error Message
CallManager- 3 -ICTCallThrottlingStart : Unified CM stops handling calls for the indicated H.323 device due to heavy traffic or a route loop over the H.323 trunk. Device Name [String] IP Address [String] Device type [Enum] Device description [String]

Explanation Unified CM has detected a route loop over the H.323 trunk indicated in this alarm. As a result, Unified CM has temporarily stopped accepting calls for the indicated H.323 trunk. It's also possible that a high volume of calls are occurring over the intercluster trunk, which has triggered throttling.

Recommended Action In Real-Time Monitoring Tool, check the CallsActive and CallsInProgress counters for unusual activity on the indicated H.323 trunk. If the CallsActive count is significantly higher than usual, a traffic load issue may be occurring where the demand to send calls over the trunk is greater than the trunk's capacity. Monitor the situation and collect existing trace files. If the ICTCallThrottlingEnd alarm is not issued in a reasonable amount of time as deemed by your organization, contact the Cisco Technical Assistance Center (TAC) and supply the trace information you have collected. For a routing loop condition, the CallsInProgress counter will be significantly higher than usual. By examining trace files and CDR data for calls that occurred over the indicated trunk, you may be able to detect a translation pattern, route list or other routing mechanism that is part of the loop. Update the routing mechanism that resulted in the loop (generally the same number is configured on both near end and far end devices) and then reset the affected route list in an attempt to clear the route loop and if that fails, reset the affected trunk.

Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
125 TRUNK
Error Message
CallManager- 5 -ICTCallThrottlingEnd : Unified CM starts handling calls again for the indicated H.323 device. Device Name [String] IP Address [String] Device type [Enum] Device description [String]

Explanation Unified CM has ceased throttling calls on the indicated H.323 device

Recommended Action Notification purposes only; no action is required

Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
125 TRUNK
Error Message
CallManager- 2 -CodeYellowEntry : Unified CM has entered Code Yellow state. Expected Average Delay [UInt] Entry Latency [UInt] Exit Latency [UInt] Sample Size [UInt] Total Code Yellow Entry [UInt] High Priority Queue Depth [Long] Normal Priority Queue Depth [Long] Low Priority Queue Depth [Long]

Explanation Unified CM has initiated call throttling due to unacceptably high delay in handling incoming calls

Recommended Action Memory problems or high CPU usage are generally at the root of a Code Yellow condition. A bad disk could also be the cause. Also, trace level settings can consume tremendous amounts of CPU (especially when the Enable SDL TCP Event Trace checkbox is enabled on the SDL Trace Configuration window in Cisco Unified Serviceability). Use RTMT to check for memory leaks, causes of any CPU spikes, and determine whether the server has sufficient memory for the tasks expected of this server. Run server diagnostics to determine if the disk is bad, and examine/reconfigure the SDL trace settings in Unified Serviceability to ensure that trace settings are not contributing to Code Yellow. You can determine the level of fragmentation on the hard disk by issuing the File Fragmentation command from the CLI for the trace directories. After taking one or more of these corrective actions, monitor the situation and collect existing trace files. If the CodeYellowExit alarm is not issued in a reasonable amount of time as deemed by your organization, or if the system is frequently triggering the CodeYellowEntry alarm, contact the Cisco Technical Assistance Center (TAC) and supply the trace information you have collected

Error Message
CallManager- 5 -CodeYellowExit : Unified CM has exited Code Yellow. Expected Average Delay [UInt] Entry Latency [UInt] Exit Latency [UInt] Sample Size [UInt] Time Spent in Code Yellow [UInt] Number of Calls Rejected Due to Call Throttling [UInt] Total Code Yellow Exit [UInt] High Priority Queue Depth [Long] Normal Priority Queue Depth [Long] Low Priority Queue Depth [Long]

Explanation Unified CM has ceased throttling calls and has exited the Code Yellow state

Recommended Action Notification purposes only; no action is required

Error Message
CallManager- 2 -CodeRedEntry : Unified CM has entered Code Red condition and will restart. Expected Average Delay [UInt] Entry Latency [UInt] Exit Latency [UInt] Sample Size [UInt] Code Yellow Duration [UInt] Number of Calls Rejected Due to Call Throttling [UInt] Total Code Yellow Entry [UInt] Total Code Yellow Exit [UInt] High Priority Queue Depth [Long] Normal Priority Queue Depth [Long] Low Priority Queue Depth [Long]

Explanation Unified CM has been in Code Yellow state for an extended period and is unlikely to recover on its own. The Cisco CallManager service automatically restarts in an attempt to clear the condition that is causing the Code Yellow state. The amount of time that the system will remain in Code Yellow state is configurable in the Code Yellow Duration service parameter. If the duration of this parameter is set to 99999, Code Red condition will never occur.

Recommended Action Make certain that you have attempted the steps in the recommended actions defined in the CodeYellowEntry alarm. If you have not, try those after the system is online. There is no other action for Code Red because the only action is to restart which occurs automatically.

Error Message
CallManager- 2 -SignalCongestionEntry : Unified CM has detected signal congestion in an internal thread and has throttled activities for that thread. Thread [String] Expected Average Delay [UInt] Entry Latency [UInt] Exit Latency [UInt] Sample Size [UInt] Total Signal Congestion Entry [UInt] High Priority Queue Depth [Long] Normal Priority Queue Depth [Long] Low Priority Queue Depth [Long]

Explanation Unified CM has initiated throttling for an internal thread due to unacceptably high delay in handling signals

Recommended Action Memory problems or high CPU usage are generally at the root of signal congestion. A bad disk could also be the cause. Also, trace level settings can consume tremendous amounts of CPU (especially when the Enable SDL TCP Event Trace checkbox is enabled on the SDL Trace Configuration window in Cisco Unified Serviceability). Use RTMT to check for memory leaks, causes of any CPU spikes, and determine whether the server has sufficient memory for the tasks expected of this server. Run server diagnostics to determine if the disk is bad, and examine/reconfigure the SDL trace settings in Unified Serviceability to ensure that trace settings are not contributing to the signal congestion. You can determine the level of fragmentation on the hard disk by issuing the File Fragmentation command from the CLI for the trace directories. After taking one or more of these corrective actions, monitor the situation and collect existing trace files. If the SignalCongestionExit alarm is not issued in a reasonable amount of time as deemed by your organization, or if the system is frequently triggering the SignalCongestionEntry alarm, contact the Cisco Technical Assistance Center (TAC) and supply the trace information you have collected.

Error Message
CallManager- 5 -SignalCongestionExit : Unified CM has exited throttling caused by a previous signal congestion condition. Thread [String] Expected Average Delay [UInt] Entry Latency [UInt] Exit Latency [UInt] Sample Size [UInt] Time Spent in Signal Congestion [UInt] Number of Calls Rejected Due to Call Throttling [UInt] Total Signal Congestion Exit [UInt] High Priority Queue Depth [Long] Normal Priority Queue Depth [Long] Low Priority Queue Depth [Long]

Explanation Unified CM has exited the throttling state caused by signal congestion on a threaded process within Unified CM

Recommended Action Notification purposes only; no action is required

Error Message
CallManager- 2 -MemoryThrottlingEntry : Unified CM has entered a memory throttling state; new call attempts are being rejected. Configured Virtual Memory Size [Int] Configured Free Ordinary Blocks [Int] Virtual Memory Size [Int] Free Ordinary Blocks [Int]

Explanation Unified CM has initiated call throttling due to unacceptably high memory usage

Recommended Action High traffic usage is generally the root cause of a memory throttling condition. Evaluate the load balancing amongst the servers in your deployment to determine if additional nodes are needed to handle the traffic. If the MemoryThrottlingExit alarm is not issued in a reasonable amount of time as deemed by your organization, or if the system is frequently triggering the MemoryThrottlingEntry alarm, contact the Cisco Technical Assistance Center (TAC) for assistance

Error Message
CallManager- 5 -MemoryThrottlingExit : Unified CM has exited a memory throttling state. Configured Virtual Memory Size [Int] Configured Free Ordinary Blocks [Int] Virtual Memory Size [Int] Free Ordinary Blocks [Int] Memory Throttling Exit Reason [String]

Explanation Unified CM has ceased throttling calls and has exited the memory throttling state

Recommended Action Notification purposes only; no action is required

Error Message
CallManager- 3 -DeviceCloseMaxEventsExceeded : The TCP socket for the SCCP device has been closed due to excessive events in a 5-second period; under normal conditions, the device will reregister automatically. Total Events Received [UInt] IP Address [String] TCP Handle [String] Max Events Allowed [UInt] Number of SCCP Devices Throttled [UInt]

Explanation The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. Events can be phone calls, KeepAlive messages, or excessive SCCP or non-SCCP messages. The maximum number of allowed events is controlled by the Cisco CallManager service parameter, Max Events Allowed. When an individual device exceeds the number configured in that service parameter, Unified CM closes the TCP connection to the device; automatic reregistration generally follows. This action is an attempt to stop malicious attacks on Unified CM or to ward off excessive CPU usage.

Recommended Action Check the CCM trace data for the indicated SCCP device to determine the reason for the high number of events. Confirm that the value configured in the Cisco CallManager service parameter, Max Events Allowed, is a suitable number for your deployment.

Error Message
CallManager- 4 -MaliciousCall : A malicious call has been identified. Called Party Number [String] Called Device Name [String] Called Display Name [String] Calling Party Number [String] Calling Device Name [String] Calling Display Name [String]

Explanation A user presses the MCID softkey to alert you that the call indicated in this alarm contained disturbing content. This is not to indicate a voice quality issue on the call but to alert you to a potentially abusive or offensive occurrence involving the calling party device.

Recommended Action After a user presses the MCID softkey, the MCID service flags the call detail record (CDR) with the MCID notice and sends a notification to the PSTN that a malicious call is in progress. Take appropriate action as defined by your company policy regarding disturbing/abusive calls.

Error Message
CallManager- 4 -BeginThrottlingCallListBLFSubscriptions : Unified CM has initiated throttling of CallList BLF subscriptions as a preventive measure to avoid overloading the system. Active External Presence Subscriptions [UInt] CallList BLF Subscriptions Throttling Threshold [UInt] CallList BLF Subscriptions Resume Threshold [UInt] Total Begin Throttling CallList BLF Subscriptions [UInt]

Explanation Unified CM has initiated throttling of Call List BLF subscriptions as a preventive measure to avoid overloading the system. This alarm occurs when the total number of active BLF subscriptions exceeds the configured limit set by the Presence Subscription Throttling Threshold service parameter.

Recommended Action Determine if CPU and memory resources are available to meet the higher demand for CallList BLF subscriptions. If so, increase the value in the Cisco CallManager service parameter Presence Subscription Throttling Threshold and correspondingly reduce the value in the Presence Subscription Resume Threshold service parameter. If you do not have sufficient CPU and memory resources to increase the throttling threshold value, evaluate a plan to increase system resources to meet the demand.

Error Message
CallManager- 5 -EndThrottlingCallListBLFSubscriptions : EndThrottlingCallListBLFSubscriptions. Active External Presence Subscriptions [UInt] CallList BLF Subscriptions Throttling Threshold [UInt] CallList BLF Subscriptions Resume Threshold [UInt] Time Duration Of Throttling CallList BLF Subscriptions [UInt] Number of CallList BLF Subscriptions Rejected Due To Throttling [UInt] Total End Throttling CallList BLF Subscriptions [UInt]

Explanation Unified CM has resumed accepting CallList BLF subscriptions subsequent to prior throttling

Recommended Action Notification purposes only; no action is required

Error Message
CallManager- 5 -PktCapServiceStarted : Packet capture service has started.

Explanation The packet capture feature has been enabled on the Unified CM server. A Cisco CallManager service parameter, Packet Capture Enable, must be set to True for packet capture to occur.

Recommended Action Informational purposes only; no action is required

Error Message
CallManager- 5 -PktCapServiceStopped : Packet capture service has stopped.

Explanation The packet capture feature has been disabled in Unified CM

Recommended Action Informational purposes only; no action is required

Error Message
CallManager- 5 -PktCapOnDeviceStarted : Packet capture has started on the device. Device Name [String] Packet Capture Mode [String] Packet Capture Duration [String]

Explanation Packet capture has been enabled on the device indicated in this alarm

Recommended Action Informational purposes only; no action is required

Error Message
CallManager- 5 -PktCapOnDeviceStopped : Packet capture stopped on the device. Device Name [String] Packet Capture Mode [String] Packet Capture Duration [String]

Explanation Packet capture has been disabled on the indicated device

Recommended Action Informational purposes only; no action is required

Error Message
CallManager- 4 -UserUserPrecedenceAlarm : User-to-User Precedence passing violation. Device Name [String] Reason Code [Enum]

Explanation User-to-User IE was not successfully tunneled to destination; please refer to reason code for additional details

Recommended Action Refer to the information (help text) in the reason code in this alarm for detailed actions

Reason Code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
2 HopCountExceeded - The hop count field in passing User-to-User IE exceeded the maximum value of 10. The reason could be the presence of routing loops across the Unified CM trunk interfaces (PRI, intercluster trunk, and so on). The recommended action is to check that no routing loops exist across the Unified CM trunk interfaces (PRI, intercluster trunk, and so on) and gateway (H.323) devices related to the indicated failed call. By examining trace files and CDR data in all Unified CM nodes and route patterns in gateways (H.323) that are involved in routing of the indicated failed call, you may be able to detect a translation pattern, route list or other routing mechanism that is part of the loop. Update the routing mechanism that resulted in the loop, and then if the looping route pattern was on a Unified CM, reset the affected route list/pattern in an attempt to clear the route loop; if that fails, reset the affected trunk/gateway or if the looping route pattern was on an H.323 gateway, restart the gateway.
3 UserUserIEDropped - The passing UserUserIE is dropped. If the indicated device is an H.323 intercluster trunk then the possible reason could be that the Passing Precedence Level Through UUIE checkbox in the Trunk Configuration window in Unified CM is not enabled; the recommended action is to verify that the Passing Precedence Level Through UUIE checkbox has been enabled. If the indicated device is an MGCP gateway with Device Protocol set to Digital Access PRI, the possible reason could be that in the incoming UUIE message, either the IE ID is not set to USER_USER_IE (126) or the User specific protocol ID value is not set to PRI_4ESS_UUIE_DEFAULT_PROT_DISC (0x00); the recommended action is to verify that the far-end side of the configured PRI trunk interface supports PRI 4ESS UUIE-based MLPP and sends the UUIE message with IEID value set to USER_USER_IE (126) and the User specific protocol ID value is set to PRI_4ESS_UUIE_DEFAULT_PROT_DISC (0x00).
Error Message
CallManager- 3 -MultipleSIPTrunksToSamePeerAndLocalPort : A conflict occurred because multiple trunks have been configured to the same destination and local port. Peer IP Address [String] Local IP Port [UInt] Old Device name [String] Old Device Instance [String] New Device name [String] New Device Instance [String]

Explanation Multiple trunks have been configured to the same destination and local port, which resulted in a conflict. Only one trunk is allowed for one destination/local port combination. The new trunk invalidated the old trunk.

Recommended Action Check the SIP Trunk Configuration in Cisco Unified CM Administration and ensure that only one SIP trunk is configured to the same destination address and local port

Error Message
CallManager- 0 -NoFeatureLicense : No feature license found.

Explanation Unified CM requires a license to function. Also, Unified CM licenses are version-specific so be certain that the license is for the version you are trying to run. You can run a license unit report in Cisco Unified CM Administration (System > Licensing > License Unit Report).

Recommended Action Request license generation for Cisco Unified Communications Manager SW FEATURE for your version of Unified CM and upload the license in Cisco Unified CM Administration (System > Licensing > License File Upload)

Error Message
CallManager- 6 -CMInitializationStateTime : Indicates the amount of time it took for Unified CM to initialize each state in the initialization process. Initialization State [String] Initialization Time [String] Initialization Time in Milliseconds [UInt]

Explanation Indicates the amount of time required to complete initialization for the specified state

Recommended Action Informational purposes only; no action is required

Error Message
CallManager- 6 -CMTotalInitializationStateTime : Total amount of time it took for Unified CM to complete initialization. Total Initialization Time [String] Total Initialization Time in Milliseconds [UInt]

Explanation Indicates the amount of time required to complete the total system initialization

Recommended Action Informational purposes only; no action is required

Error Message
CallManager- 1 -CMOverallInitTimeExceeded : Initialization of the Unified CM system has taken longer than allowed by the System Initialization Timer service parameter; the system automatically restarts to attempt initialization again. Cisco Unified Communications Manager Overall Initialization Time (in minutes) [Int]

Explanation The required time to initialize Unified CM has exceeded the time allowed by the Cisco CallManager service parameter, System Initialization Timer; as a result, the system will automatically restart to attempt initialization again. Initialization may have failed due to an increase in system size, due a database error, due to a large amount of new devices added to the system, or any number of other potential causes.

Recommended Action Use RTMT to discover the number of devices and number of users in the system and evaluate whether the numbers seem accurate. Try increasing the value of the Cisco CallManager service parameter, System Initialization Timer, in the Service Parameters Configuration window in Cisco Unified CM Administration. If increasing the time in the System Initialization Timer service parameter does not correct this issue, contact the Cisco Technical Assistance Center (TAC).

Error Message
CallManager- 4 -DigitAnalysisTimeoutAwaitingResponse : Unified CM sent a routing request to the policy decision point but the request timed out without a response. Translation Pattern Triggering Point [String] Policy Decision Point [String]

Explanation Unified CM was unable to complete the routing request before timing out. This timeout could occur due to low system resources, high CPU usage, or a high volume of call activities on this Unified CM node. Unified CM applies the Call Treatment on Failure that is configured for the External Call Control Profile associated with this call.

Recommended Action Check the External Call Control object in Real-Time Monitoring Tool (RTMT) to see whether the ExternalCallControlEnabledCallAttempted counter is spiking. A dramatic increase in that counter indicates an unusually high number of calls at this time which could result in reduced system resources. Check the QueueSignalsPresent2-Normal counter for persistent (long) high signal queue. If the long signal queue exists, check whether the Code Yellow alarm has already issued and check the system CPU and memory usage for this Unified CM node. Follow the recommended actions for Code Yellow alarm if the Code Yellow alarm has fired. For high CPU usage, use RTMT to determine which areas may be contributing to the high CPU usage. If this alarm persists, collect system performance data (such as the percentage of Memory, Page and VM usage, partition read and write bytes per second, the percentage of CPU usages of all the processes, and the processor IOWait percentage) and contact Cisco Technical Assistance Center (TAC).

Error Message
CallManager- 3 -InvalidIPNetPattern : An invalid IP address is configured in one or more SIP route patterns in Cisco Unified CM Administration. Description [String] IPAddress [String] DeviceName [String]

Explanation An invalid IP address is configured in one or more SIP route patterns in Cisco Unified CM Administration

Recommended Action In Cisco Unified CM Administration, verify that the route pattern associated with the device that is identified in this alarm has an accurate and working IP address. You can learn more how to ensure that the IP address is valid by reviewing RFC 2373.

Error Message
CallManager- 4 -FailedToFulfillDirectiveFromPDP : Unified CM cannot fulfill the call routing directive returned by the policy decision point. Policy Decision Point [String] Reason, Unified CM failed to fulfill the directive [String] Called Party Number [String] Calling Party Number [String] Calling User ID [String]

Explanation A routing directive from the policy decision point (PDP) cannot be fulfilled. This could occur because the call was cleared by a CTI application before Unified CM was able to route it to the location defined by the PDP; because a call that was allowed by a policy server was redirected by the CTI application to a destination; because the annunciator ID was misconfigured in the PDP; or because Unified CM attempted to invoke a media resource such as Annunciator but no resources were available.

Recommended Action In many cases, a failure to fulfill a routing directive occurs because of intervention by a CTI application which scoops up the call before Unified CM is able to fulfill the routing directive in the PDP. If CTI interaction is having a negative effect, examine the CTI application to ensure that the call is in alerting or connected state before CTI begins to interact with the call. If the failure is caused by a problem with the annunciator ID, check to be sure the ID has been accurately configured in the PDP and that it exists in Unified CM Administration. If the failure was caused by a lack of media resources, try increasing the Annunciator Call Count service parameter in the Cisco IP Voice Media Streaming App service.

Error Message
CallManager- 3 -FailureResponseFromPDP : The policy decision point returned a 4xx (client) or 5xx (server) status code in the HTTP response. Policy Decision Point URL [String] The status code and reason phrase for the failure [String]

Explanation Unified CM received a 4xx or 5xx response from the policy decision point (PDP). A 4xx response indicates errors in the call routing request from Unified CM, for example: a 400 response indicates the call routing request could not be understood by the PDP; a 404 indicates that the PDP did not find a matching request URI. A 5xx error indicates a PDP server error, for example: a 500 response indicates a PDP internal error; a 501 response indicates that the PDP does not support the functionality to generate a call routing response; a 503 indicates that the PDP is busy and temporarily cannot generate a response; a 505 indicates that the HTTP version number included in the call routing request from Unified CM is not supported. Other such errors may be responsible; please refer to generally available guidelines on HTTP or check RFC 2616 for detailed explanations about HTTP Status Code definitions.

Recommended Action If a 4xx response caused the alarm, verify that the PDP has been accurately configured for the functionality and call routing that you expect it to perform. If a 500 response causes the alarm, check whether the PDP service is active and check the PDP server's log files for any errors. If a 503 causes the alarm, the PDP may be overloaded by requests. Take appropriate action to reduce the load on the PDP by following some or all of these recommendations: 1) consider adding more PDPs and provisioning Unified CM with additional external call control profiles and external call control trigger points in the various configuration pages under the Call Routing menu in Cisco Unified CM Administration; 2) provision a pair of policy servers per external call control profile to enable load balancing; or 3) verify that the PDP server in your deployment meets or exceed the hardware requirements specified in the documentation for Cisco Enterprise Policy Manager (CEPM) or the third-party PDP solution you have deployed. If a 505 response causes the alarm, check to be sure that the PDP supports HTTP version 1.1.

Error Message
CallManager- 3 -ConnectionFailureToPDP : A connection request from Unified CM to the policy decision point failed. Policy Decision Point [String] The cause of the connection failure [String]

Explanation A connection request to the policy decision point (PDP) failed. Failure may have been due to a network error causing limited or no connectivity between Unified CM and the PDP; because of authentication errors when Unified CM established an HTTPS connection to the PDP; or because the PDP was not in service.

Recommended Action Verify that network connectivity exists between Unified CM and the PDP by pinging the policy server host from Cisco Unified OS Administration and take steps to establish connectivity if it has been lost. If the connection failure is due to an authentication problem, verify that the valid certificate of the PDP has been imported to Cisco Unified OS Administration and certificates from every node in the Unified CM cluster have been imported to every node in the PDP. Also, make sure that the PDP service is active.

Error Message
CallManager- 6 -ConnectionToPDPInService : A connection was successfully established between Unified CM and the policy decision point. Policy Decision Point [String]

Explanation A successful connection from Unified CM to the policy decision point (PDP) has been established

Recommended Action Informational purposes only; no action is required

Error Message
CallManager- 3 -AwaitingResponseFromPDPTimeout : Unified CM timed out waiting for the routing response from the policy decision point. Policy Decision Point [String]

Explanation Unified CM did not receive a call routing response from the policy decision point (PDP) within the time specified by either the Cisco CallManager service parameter, Call Intercept Routing Request Timer, or on the Call Intercept Profile Configuration window in Cisco Unified CM Administration.

Recommended Action Check whether the PDP is in service and working normally. Verify that the PDP is not overloaded; if it is, take appropriate action to reduce the load on the PDP by following some or all of these recommendations: 1) consider adding more PDPs and provisioning Unified CM with additional call intercept profiles and call intercept trigger points in the various configuration pages under the Call Routing menu in Cisco Unified CM Administration; 2) provision a pair of policy servers per call-intercept profile to enable load balancing; or 3) verify that the PDP server in your deployment meets or exceed the hardware requirements specified in the documentation for Cisco Enterprise Policy Manager (CEPM) or the third-party PDP solution you have deployed. If necessary, increase the value in the Cisco CallManager service parameter, Call Intercept Routing Request Timer or the value in the Call Intercept Profile for this PDP.

Error Message
CallManager- 3 -ErrorParsingDirectiveFromPDP : Unified CM failed to parse the call routing directive or the diversion destination in the call routing response from the policy decision point. Policy Decision Point [String] Called Party Number [String] Calling Party Number [String] Calling User ID [String] Response XML Data [String]

Explanation A routing response was received but Unified CM failed to parse the mandatory elements in the response. This means that a call routing directive or the call diversion destination could not be parsed correctly, or that the call routing directive was not recognized. The error may due to a syntax error or because the call routing directive is missing or the call diversion destination is missing in the call routing response.

Recommended Action Check the external call control documentation, including any applicable API documentation, to determine whether the call routing directive that was included as part of the policy obligations in the call routing response are correctly entered according to the information defined in the external call control documentation.

Error Message
CallManager- 4 -ErrorParsingResponseFromPDP : Unified CM failed to parse one or multiple optional elements or attributes in the call routing response from the policy decision point. Policy Decision Point [String] Called Party Number [String] Calling Party Number [String] Calling User ID [String] Request XML Data [String]

Explanation A routing response was received from the policy decision point (PDP) but Unified CM failed to parse the optional elements in the response. Optional elements may include modified calling numbers or called numbers, call reject or call diversion reasons, and so on. The cause may be a syntax error or missing attributes in the call routing response.

Recommended Action Confirm that the call routing response from the policy decision point complies with the guidelines specified for external call control in the Cisco Unified Communications Manager documentation. Confirm that any optional elements included as the policy obligations in the call routing response are correctly entered according to the external call control documentation, including any applicable API documentation.

Error Message
CallManager- 4 -CallAttemptBlockedByPolicy : A call was attempted but blocked or rejected by the policy decision point. Policy Decision Point [String] Reject Reason [String] Called Party Number [String] Calling Party Number [String] Calling User ID [String]

Explanation A call was rejected or blocked because it violated the enterprise policy as defined in a policy decision point (PDP) that was configured in Unified CM. The policy server returns a call reject decision stating that a policy violation was the reason for rejecting the call. Calls may be rejected because an unauthorized user attempted to dial a DN or pattern that is not allowed for him or her or because a call forward directive was invoked and the destination specified in the call forward operation violated the policy. Depending on email configuration in Real-Time Monitoring Tool (RTMT), the system may have generated an email alert when the call was rejected.

Recommended Action Evaluate the information provided in this alarm (caller's user ID, to and from DNs, and so on) to determine if the call attempt was an innocent mistake to dial a number that the user didn't realize was not routable for him or her, or to discover whether the user is intentionally trying to circumvent the policy restrictions. If the rejected call was caused by an innocent mistake, educate the affected user about the numbers that he or she is allowed to dial. Your organization may have a policy or guidelines to follow when investigating call rejects. In addition to or instead of the steps recommended here, please refer to your company's guidelines.

Error Message
CallManager- 5 -ServicePortOnline : A Cisco CallManager service port is online. Protocol [String] Port Number [UInt]

Explanation Unified CM has successfully opened a socket port to provide service

Recommended Action Notification purposes only; no action is required

Error Message
CallManager- 2 -ServicePortOffline : A Unified CM service port is offline. Protocol [String] Port Number [UInt] Error Number [Int]

Explanation A Unified CM socket port that is used to provide service has unexpectedly closed; Unified CM will attempt to reopen this port. Normally, this port should never be closed. An unexpected closing of this port generally indicates an operating system failure or an external attack on Unified CM.

Recommended Action Verify that Unified CM is able to reopen this socket port and provide service. You can watch for an instance of the notice level alarm, ServicePortOnline, when service to the port has been restored. If the port is not reopened and service restored, restart the Cisco CallManager service. If this alarm occurs for an extended duration, collect the existing trace files and contact the Cisco Technical Assistance Center (TAC).

Error Message
CallManager- 4 -SuspiciousIPAddress : Unified CM has identified suspicious connection attempts from an IP address. Port Number [UInt] IP Address [String]

Explanation Unified CM has identified suspicious connection attempts from an IP address and has temporarily blocked the address. This alarm is an indication that a Denial-of-Service attack may have been attempted from this IP address.

Recommended Action Examine network activity for repeated attempts to access the port number specified in this alarm. Using the IP address specified in this alarm, attempt to identify the device that has been sending connection attempts to the port. If the IP address belongs to a device that is configured in Unified CM, evaluate the possible reason for such numerous connection attempts. Generally, no device that is functioning properly will trigger this alarm. Reset the device or remove the device from the network.

Error Message
CallManager- 3 -LostConnectionToSAFForwarder : Connection to the SAF Forwarder has been lost. IP Address [String] SafClientHandle [UInt]

Explanation A TCP connection failure caused the connection between the SAF Forwarder and Unified CM to be lost. When the TCP connection is restored, Unified CM attempts to connect to the SAF Forwarder automatically. If IP connectivity is unreachable for longer than the duration of the Cisco CallManager service parameter CCD Learned Pattern IP Reachable Duration, calls to learned patterns will be routed through the PSTN instead. Calls through the PSTN to learned patterns will be maintained for a certain period of time before the PSTN failover times out.

Recommended Action Investigate possible causes of a TCP connection failure, such as power failure, loose cables, incorrect switch configuration, and so on, and correct any issues that you find. After the connection is restored, CCD will try to register/sync with the SAF Forwarder automatically.

Error Message
CallManager- 3 -SAFForwarderError : SAF Forwarder error response sent to Unified CM. IP Address [String] SafClientHandle [UInt] Application User Name [String] Reason Code and Description [Enum] SAF Protocol Version Number [String] Service ID [UInt] Sub Service ID [UInt]

Explanation Unified CM received an error from the SAF Forwarder

Recommended Action Refer to the reason code and description (help text) for specific information and actions (where applicable) for this alarm

Reason Code and Description-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
400 SAF_BAD_REQUEST - SAF Forwarder was unable to accept the request due to incorrect syntax (malformed), missing required attributes, and other similar reasons. Investigate the configuration between the SAF Forwarder and Unified CM to be certain that all settings are correct for your deployment. In particular, check the Client Label configured on the router to make certain that it matches the Client Label configured in Cisco Unified CM Administration on the SAF Forwarder Configuration window (SAF > SAF Forwarder).
431 SAF_INTEGRITY_CHECK_FAILURE - A message failed to pass SAF Forwarder security validation. This can occur because of misconfiguration, a potential attack, or more commonly by incorrect provisioning of the password on the Forwarder and SAF client. Reprovision the password and keep a watch on further SAF INTEGRITY CHECK FAILURE alarms. If you receive a persistent number of SAF INTEGRITY CHECK FAILURE alarms, close the interface between SAF Forwarder and Unified CM and investigate the source of the IP packets.
435 **INFO LEVEL** SAF_MISSING_NONCE - A nonce (a random parameter generated when the message is sent) is missing from the message. The system will resend with a new nonce automatically. No action is required.
436 SAF_UNKNOWN_USERNAME - Unified CM sent the SAF Forwarder an Application User name that is not configured on the router or that does not match the router's configuration. Check the Application User Name on the router and in the Application User Configuration window in Cisco Unified CM Administration to be sure they match.
438 **INFO LEVEL** SAF_STALE_NONCE - A nonce (a random parameter generated when the message is sent) has aged out (gone stale). The system will resend with a new nonce automatically. No action is required.
471 **INFO LEVEL** SAF_BAD_CLIENT_HANDLE - SAF_BAD_CLIENT_HANDLE - Unified CM sent the SAF Forwarder a Register message (for KeepAlive purposes) or unregister message with the mandatory CLIENT_HANDLE value, but the SAF Forwarder did not recognize the client handle. Unified CM will attempt to reregister with the SAF Forwarder without a client handle. This alarm is for informational purposes only; no action is required.
472 **INFO LEVEL** SAF_VERSION_NUMBER_TOO_LOW - Unified CM published a service (such as Hosted DN) whose version number is now lower than when it was previously published to the SAF Forwarder. The service is out of sync with the SAF Forwarder. Unified CM will republish the service in an attempt to resynch with the SAF Forwarder. This alarm is for informational purposes only; no action is required.
473 **INFO LEVEL** SAF_UNKNOWN_SERVICE - Unified CM attempted to unpublish a service from the SAF network but the SAF Forwarder does not have a publish record for that service. This alarm is for informational purposes only; no action is required.
474 **INFO LEVEL** SAF_UNREGISTERED - Unified CM attempted to publish or subscribe to the SAF Forwarder, but Unified CM is not registered with SAF Forwarder. Unified CM will automatically reregister with the SAF Forwarder before attempting to publish or subscribe. This alarm is for informational purposes only; no action is required.
475 **INFO LEVEL** SAF_BAD_FILTER - Unified CM attempted to subscribe to the SAF Forwarder with a filter that does not match any of the SAF Forwarder's current filters. Unified CM will resend the subscribe message with the appropriate filter value. This alarm is for informational purposes only; no action is required.
476 SAF_UNKNOWN_SUBSCRIPTION - Unified CM sent a subscribe or unsubscribe message to the SAF Forwarder but the message contained a Service ID that was not familiar to the SAF Forwarder. Without a recognized Service ID, Unified CM cannot subscribe to the SAF Forwarder. Recommended action is to contact the Cisco Technical Assistance Center (TAC).
477 **INFO LEVEL** SAF_ALREADY_REGISTERED - Unified CM attempted to register with the SAF Forwarder but SAF Forwarder indicates that Unified CM is already registered. Unified CM will close and reopen the TCP connection and send a new register request without a client handle to SAF Forwarder. This alarm is for informational purposes only; no action is required.
478 SAF_UNSUPPORTED_PROTOCOL_VERSION - Unified CM attempted to register with the SAF Forwarder using a SAF protocol version number that is greater than the protocol version number supported by the SAF Forwarder. Issue a show version command on the SAF Forwarder CLI to determine the SAF Forwarder protocol version; refer to the information in this alarmfor the SAF protocol version number. If the versions do not match, check the Cisco Unified Communications Manager Software Compatibility Matrix (available on Cisco.com) to determine whether the SAF protocol version number that is in use on this Unified CM is compatible with the SAF Forwarder protocol version. If it is not, upgrade the lower-versioned component so that both Unified CM and the SAF Forwarder use the same, compatible version.
479 SAF_UNKNOWN_AS - Unified CM attempted to register to the SAF Forwarder but the registration message contained a Client Label that was not familiar to the Autonomous System (AS) on the SAF Forwarder router. Recommended action is to issue the appropriate CLI commands on the SAF Forwarder to associate the Client Label with the autonomous system on the router (refer to the Configuration Guide for the router) and configure the same Client Label in the Client Label field on the SAF Forwarder Configuration window in Cisco Unified CM Administration and click Save. When the Client Label is saved in Cisco Unified CM Administration, Unified CM automatically sends a new registration request to the SAF Forwarder with the updated Client Label information.
500 **INFO LEVEL** SAF_RESPONDER_ERROR - Unified CM sent a message (such as register/unregister/publish/unpublish/subscribe) to the SAF Forwarder but the SAF Forwarder responded that it is unable to process the message at this time. This might be due to heavy message queuing, internal resource issues, and so on. Unified CM will wait several seconds and then retry the request. This alarm is for informational purposes only; no action is required.
1000 SAF_INVALID_CONNECTION_DETAILS")
Error Message
CallManager- 6 -SAFUnknownService : Unified CM does not recognize the service ID in a Publish Revoke or Withdraw message. Client Handle [String] Service ID [UInt] Sub Service ID [UInt] InstanceID1 [UInt] InstancID2 [UInt] InstanceID3 [UInt] InstanceID4 [UInt]

Explanation Unified CM received a Publish Revoke message or Withdraw message from the SAF Forwarder but the service ID in the message is not recognized by Unified CM. Unified CM may not recognize the service ID if the service ID was mistyped in the Publish Revoke CLI command, or if the service was previously withdrawn.

Recommended Action This alarm is for informational purposes only; no action is required

Error Message
CallManager- 6 -SAFPublishRevoke : A CLI command revoked the publish action for the specified service or subservice ID. Client Handle [String] Service ID [UInt] Sub Service ID [UInt] InstanceID1 [UInt] InstancID2 [UInt] InstanceID3 [UInt] InstanceID4 [UInt]

Explanation A system administrator issued a CLI command on the SAF Forwarder router to revoke the publish action for the service or subservice ID specified in this alarm

Recommended Action Informational purposes only; no action is required

Error Message
CallManager- 3 -SAFResponderError : SAF Responder Error 500. Client Handle [String] Service Id [UInt] Sub Service ID [UInt] Instance ID1 [UInt] Instance ID2 [UInt] Instance ID3 [UInt] Instance ID4 [UInt]

Explanation This is raised when SAF forwarder doesn't know the transaction ID within SAF response from this Unified CM

Recommended Action No action is required

Error Message
CallManager- 3 -DuplicateLearnedPattern : CCD requesting service received a duplicate Hosted DN. Client Handle [String] Service ID [UInt] Sub Service ID [UInt] InstanceID1 [UInt] InstancID2 [UInt] InstanceID3 [UInt] InstanceID4 [UInt]

Explanation The Call Control Discovery (CCD) requesting service received the same hosted DN from multiple call control entities such as Unified CM Express or another Unified CM cluster. The Cisco CallManager service parameter, Issue Alarm for Duplicate Learned Patterns, controls whether this alarm gets issued.

Recommended Action In RTMT, check the Pattern Report (CallManager > Report > Learned Pattern) and look for the duplicate pattern identified in this alarm. Learned patterns must be unique. Determine which call control entity (such as Unified CM or Unified CM Express) needs to be changed so that there is no duplicate pattern. Refer to the call control entity's configuration guide (help text) to learn how to update a hosted DN pattern. In Unified CM, to change the Hosted DN Pattern go to Cisco Unified CM Administration to update the Hosted DN Pattern configuration (Call Routing > Call Control Discovery > Hosted DN Patterns).

Error Message
CallManager- 3 -CCDIPReachableTimeOut : CCD Requesting Service IP Reachable Duration Time Out.

Explanation The CCD requesting service detected that it can no longer reach the learned patterns through IP. All learned patterns from this forward will be marked as unreachable (via IP) and to allow calls to learned patterns to continue to be routed until IP becomes reachable again, all calls to learned patterns will be routed through the PSTN. Calls can be routed through the PSTN for a certain period of time before PSTN failover times out.

Recommended Action Check IP connectivity and resolve any TCP or IP problems in the network

Error Message
CallManager- 3 -CCDPSTNFailOverDurationTimeOut : The internal limit on PSTN failover has expired.

Explanation When learned patterns are not reachable through IP, Unified CM routes calls through the PSTN instead. Calls can be routed through PSTN for an internally-controlled duration. When this alarm occurs, the PSTN failover duration has expired and calls to learned patterns cannot be routed. All learned patterns will be purged from Unified CM.

Recommended Action Troubleshoot your network to get IP connectivity restored. After IP connectivity is restored, Unified CM will automatically relearn Hosted DN patterns and calls to learned patterns will proceed through IP.

Error Message
CallManager- 4 -CCDLearnedPatternLimitReached : CCD has reached the maximum number of learned patterns allowed. CCD Maximum Numbers of Learned Patterns [UInt] System Limit of CCD Learned Patterns [UInt]

Explanation The CCD requesting service has limited the number of learned patterns to a number defined in the service parameter, CCD Maximum Numbers of Learned Patterns. This alarm inidcates that the CCD requesting service has met the maximum number of learned patterns allowed.

Recommended Action This alarm displays the value that is configured in the Cisco CallManager service parameter, CCD Maximum Numbers of Learned Patterns, as well as the maximum number of learned patterns that are allowed by the system (an internally-controlled maximum). Consider whether the specified maximum number of learned patterns is correct for your deployment. If it is too low, compare it with the number shown in the SystemLimitCCDLearnedPatterns in this alarm. If the Max number is below the System Limit, you can go to the Service Parameters Configuration window and increase the CCD Maximum Numbers of Learned Patterns service parameter. If the Max and System Limit numbers match, the system is already configured to run at capacity of learned patterns; no action is required.

Error Message
CallManager- 5 -DbInsertValidatedDIDFailure : The Insertion of an IME-provided E.164 DID has failed. E.164 DID [String] Granting Domain [String]

Explanation A failure occurred attempting to insert a Cisco Unified Active Link learned DID

Recommended Action Verify the DID and the granting domain. Check other associated alarms. Verify the database integrity.

Error Message
CallManager- 2 -TCPSetupToIMEFailed : Connection Failure to IME server. IP address [String] Port number [UInt]

Explanation This alarm occurs when Unified CM is unable to establish a TCP connection to an IME server. It typically occurs when the IP address and port of the IME server are misconfigured or an Intranet connectivity problem is preventing the connection from being set up.

Recommended Action Check to make sure that the IP address and port of the IME server - which are present in the alarm - are valid. If so, this may be due to a network connectivity problem. Test the connectivity between Unified CM servers and the IME server.

Error Message
CallManager- 1 -TLSConnectionToIMEFailed : TLS Failure to IME service. SSL Error Code [UInt] SSL Error Text [String]

Explanation A TLS connection to the IME server could not be established because of a problem with the certificate presented by the IME server. (For example, not in the Unified CM CTL, or is in the CTL but has expired).

Recommended Action Check to see that the certificate of the IME server is configured properly in the UCM.

Error Message
CallManager- 1 -InvalidCredentials : Credential Failure to IME server. User name [String] IP address [String] Server name [String]

Explanation The connection to the IME server could not be completed, because the username and/or password configured on Unified CM do not match those configured on the IME server

Recommended Action The alarm will include the username and password which were used to connect to the IME server, along with the IP address of the target IME server and its name. Log into the IME server and check that the username and password configured there match those configured in Unified CM.

Error Message
CallManager- 1 -IMEOverQuota : IME over quota. Server name [String] Current quota [UInt] Maximum target quota [UInt]

Explanation Each IME server has a fixed quota on the total number of DIDs it can write into the IME distributed cache. When this alarm is generated, it means that, across all of the Unified CM clusters which are utilizing the same IME server, the quota for the IME distributed cache has been exceeded.

Recommended Action The alarm will include the name of the IME server, and the current and target quota values. The first thing to check is to make sure that you have correctly provisioned the right set of DID prefixes on all of the Unified CM clusters sharing that same IME server. If that is correct, it means you have exceeded the capacity of your IME server, and you require another. Once you have another, you can now split your DID prefixes across two different IME client instances, each on a different IME server. That will alleviate the quota problem.

Error Message
CallManager- 3 -PublishFailedOverQuota : Publish Failed - over Quota. The DID for which the Publish was attempted [String] Server name [String] Current quota [UInt] Maximum target quota [UInt]

Explanation Each IME server has a fixed quota on the total number of DIDs it can write into the IME distributed cache. When this alarm is generated, it means that, even though you should be under quota, due to an extremely unlikely statistical anomaly, the IME distributed cache rejected your publication, believing you were over quota. You should only see this alarm if you are near, but below, your quota. This error is likely to be persistent, so that the corresponding E.164 number from the alarm will not be published into the IME distributed cache. This means that you will not receive VoIP calls towards that number - they will remain over the PSTN.

Recommended Action The alarm will include the name of the IME server, and the current and target quota values. The first thing to check is to make sure that you have correctly provisioned the right set of DID prefixes on all of the Unified CM clusters sharing that same IME server on the same IME distributed cache. If that is correct, it means you have exceeded the capacity of your IME server, and you require another. Once you have another, you can now split your DID prefixes across two different IME client instances, each on a different IME server. That will alleviate the quota problem.

Error Message
CallManager- 4 -PublishFailed : Publish Failed. DID [String]

Explanation Unified CM attempted to store a number into the IME distributed cache, but the attempt failed. This is typically due to a transient problem in the IME distributed cache. The problem will self-repair under normal conditions. However, you should be aware that, as a consequence of this failure, the E.164 DID listed as part of the alarm will not be present in the IME distributed cache for a brief interval. Consequently, this may delay the amount of time until which you will receive VoIP calls made to that number - they may continue over the PSTN for some callers. It is useful to be aware of this, in case you are trying to understand why a call is not being made over VoIP.

Recommended Action If you notice single small numbers of this alarm in isolation, no action is required on your part. However, a large number of them indicates a problem in the IME distributed cache, most likely due to problems with Internet connectivity. Check your Internet connectivity.

Error Message
CallManager- 3 -IMEDistributedCacheInactive : Inactive IME distributed cache .

Explanation This alarm is generated when Unified CM attempts to connect to the IME server, however, the IME distributed cache is not currently active

Recommended Action Check to make sure that the IME certificate is provisioned on the IME server. Check to make sure that the IME distributed cache has been activated via the CLI on the IME server.

Error Message
CallManager- 4 -RejectedRoutes : Rejected route due to Untrusted status. Domain name [String] Phone number [String]

Explanation This alarm is generated when Unified CM learned a route from the IME server. However, due to the configured Trusted/Untrusted list, the route was rejected.

Recommended Action This condition is not an error. However, it indicates to you that one of your users called a number which was reachable over IME, however, due to your configured Trusted/Untrusted list, a IME call will not be made. You might wish to consider adding the domain or prefix to your Trusted list or removing it from the Untrusted list.

Error Message
CallManager- 6 -PublicationRunCompleted : Completion of publication of published DID patterns. Start time [String] End time [String] DID count [UInt] Failed DID count [UInt] Failed DIDs [String]

Explanation This alarm is generated when Unified CM completes a publication of the DID patterns into the Cisco Intercompany Media Network

Recommended Action This alarm is provided for historic and informational purposes. It can be used to give you feedback that the system is working and is correctly publishing numbers into the Cisco Intercompany Media Network. It can also be used for troubleshooting. If some of the publishes fail for some reason, the alarm will contain a list of those numbers which were not published. If your users are receiving calls, and they are not over IP but you think they ought to be, you can check the history of these alarms to see if the number failed to be published into the network.

Error Message
CallManager- 6 -RouteRemoved : Route removed automatically. E.164 number [String] Domain name [String] Route learned time [String] Reason Code [Enum]

Explanation This alarm is generated when Unified CM removes a route from Unified CM Administration because the route is stale and has expired, or because the far end has indicated the number is no longer reachable at that domain

Recommended Action This alarm is provided for historic and informational purposes. It helps you understand why certain numbers are in your routing tables, and why others are not. This historical information is useful to help determine why a call to a particular number is not going over IP, when you expect it to.

Reason Code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Expired
2 Unreachable
Error Message
CallManager- 3 -InsufficientFallbackIdentifiers : Cannot allocate fallback identifier. Fallback profile name [String] Fallback E.164 number [String]

Explanation This alarm is generated when Unified CM is processing a IME call, and is attempting to allocate a PSTN fallback DID and a DTMF digit sequence to associate with this call. However, there are too many IME calls currently in progress which are utilizing this same fallback DID, and as a result, there are no more DTMF digit sequences which could be allocated to this call. As such, this call will proceed, however mid-call fallback will not be possible for this call.

Recommended Action Your first course of action should be to identify the fallback profile associated with this call. Its name will be present in the alarm. Check that profile in Cisco Unified CM Administration and examine the current setting for "Fallback Number of Correlation DTMF Digits". Increase that value by one, and check if that eliminates these alarms. In general, this parameter should be large enough such that the number of simultaneous IME calls made to enrolled numbers associated with that profile is always substantially less than 10 raised to the power of this number. "Substantially" should be at least a factor of ten. For example, if you always have less than 10,000 simultaneous IME calls for the patterns associated with this fallback profile, setting this value to 5 (10 to the power of 5 is 100,000) will give you plenty of headroom and you will not see this alarm. However, increasing this value also results in a small increase in the amount of time it takes to perform the fallback. As such, it should not be set arbitrarily large; it should be set just large enough to keep clear of this alarm. Another alternative to increasing this parameter is to add another fallback profile with a different fallback DID, and associate that fallback profile with a smaller number of enrolled DID patterns. This will allow you to get by with a smaller number of digits.

Error Message
CallManager- 3 -IMEQualityAlertEntry : IME call quality problem. Active IME call count [UInt] Fallback call count [UInt] Setup attempts count [UInt] Failed attempts [UInt]

Explanation This alarm is generated when Unified CM is seeing a substantial number of IME calls fail back to PSTN, or fail to be set up, due to IP network quality problems. There are two triggers for this alarm. One is when a large fraction of the currently active IME calls have all requested fallback, or have fallen back, to the PSTN. The other is when a large fraction of the recent call attempts have not been made over IP, and instead have gone to the PSTN.

Recommended Action Check your IP connectivity, and make sure it is good. If it looks good in general, you may need to look at CDRs, CMRs, and logs from the firewalls to determine what happened.

Error Message
CallManager- 5 -IMEQualityAlertExit : IME call quality problem cleared. Active IME call count [UInt] Fallback call count [UInt] Setup attempts count [UInt] Failed attempts [UInt]

Explanation This alarm is generated when the Unified CM sees a significant reduction in the number of failed IME calls following generation of the IMEQualityAlertEntry alarm. This notice alarm indicates that the IP connectivity issues causing the initial generation of the IMEQualityAlertEntry alarm have abated.

Recommended Action Continue to monitor IP connectivity for recurring issues

Error Message
CallManager- 4 -InvalidSubscription : A message has been received from an IME server that contains a subscription identifier that is not handled by this node. Subscription Identifier [UInt] IME Server [String]

Explanation Each node that communicates with a IME server saves a subscription identifier associated with each IME client instance. A IME server has sent a message with a subscription identifier that does not match any of the previously sent subscription identifiers.

Recommended Action This may be a race condition if a IME client instance has been recently added or deleted. If this error continues, there may be a synchronization issue between this node and the IME server sending this message.

Error Message
CallManager- 3 -FirewallMappingFailure : Firewall unreachable. IP address [String] Port number [UInt]

Explanation This alarm indicates that Unified CM was unable to contact the firewall in order to make a IME call. As a consequence, outbound calls are being sent over the PSTN, and inbound calls may be routed over the PSTN by your partner enterprises.

Recommended Action Check to see that your firewall is up. Make sure the mapping service is enabled. Check that the IP address and port on the firewall for that mapping service match the configuration in Unified CM Administration. Check general IP connectivity between Unified CM and the firewall.

Error Message
CallManager- 3 -ConflictingDataIE : A call has been rejected because the incoming PRI/BRI Setup message had an invalid IE. Device Name [String]

Explanation A call has been rejected because an incoming PRI/BRI Setup message contained an invalid Coding Standard value in the Bearer Capability information element (IE). Unified CM only accepts PRI/BRI Setup messages with Coding Standard values of 0 or 1. When an invalid IE is received, Unified CM rejects the call setup and issues this alarm.

Recommended Action Notify the service provider responsible for sending the Setup message that an IE with Coding Standard values of 0 or 1 must be included in Setup messages

Error Message
CallManager- 6 -CalledPartyTracing : Called Party Tracing Match found..

Explanation A call attempt has been made to a called party number being traced. Please check the Called Party Tracing log.

Recommended Action Use the Real Time Monitoring Tool to check the Called Party Tracing log.

Error Message
CallManager- 4 -SIP IPPortConflict : The local port for this device is already in use. Device Name [String] Port Number [String] Device type [Enum]

Explanation The local port specified for this device is already in use, or Cisco Unified CM Communications Manager is unable to bind to the configured port. Either the SIP device is configured incorrectly or the domain name system (DNS) is incorrectly configured.

Recommended Action In Cisco Unified CM Administration, check the port number for the SIP device.

Device type-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
131 SIP_TRUNK
Error Message
CallManager- 6 -ConferenceCreated : An application controlled conference is created.. Conference Name [String] Conference ID [UInt] Video Enabled [UInt] Application ID [UInt] Number of Streams [UInt] Status [Int] Reason [Int]

Explanation An application controlled conference is created.

Recommended Action No action is required.

Error Message
CallManager- 6 -ConferenceDeleted : An application controlled conference is deleted.. Conference Name [String] Conference ID [UInt] Reason [Int]

Explanation An application controlled conference is deleted.

Recommended Action No action is required.

Error Message
CallManager- 4 -CtiCallAcceptTimeout : Call Accept Timeout. Call Accept Timer [UInt] Device Name [String] Calling Party DN [String] Called Party DN [String]

Explanation The application failed to accept the call within the CallAcceptTimer time period.

Recommended Action Configure the CallAcceptTimer service parameter appropriately based on the expected response time of the application.

Error Message
CallManager- 6 -CtiStaleCallHandle : CTI stale call handle.. Description [String]

Explanation This alarm is issued by audit when it finds invalid call handles that the CTI application didn't close when calls go to idle state.

Recommended Action No action is required. It is recommended that the CTI applications explicitly close the calls when the call goes to idle state.

Error Message
CallManager- 6 -DatabaseAuditInfo_074 : Database audit information.. Number [Int]

Explanation Database audit information error occurred.

Recommended Action No action is required.

Error Message
CallManager- 5 -DatabaseDeviceNoDirNum : No directory number for database device.. Text [String]

Explanation No directory number(s) are associated with identified device.

Recommended Action No action is required.

Error Message
CallManager- 1 -DatabaseInternalDataError_06e : Database internal data error.. DeviceName [String]

Explanation Database internal data error occurred.

Recommended Action No action is required.

Error Message
CallManager- 5 -DatabaseInternalDataError_06f : Database internal data error.. Route Group Name [String]

Explanation Database internal data error occurred.

Recommended Action No action is required.

Error Message
CallManager- 6 -DatabaseInternalDataError_070 : Database internal data error.. Device Name [String]

Explanation Database internal data error occurred.

Recommended Action No action is required.

Error Message
CallManager- 6 -DatabaseInternalDataError_071 : Database internal data error.. Device Name [String]

Explanation Database internal data error occurred.

Recommended Action No action is required.

Error Message
CallManager- 6 -DatabaseInternalDataError_072 : Database internal data error.. Device Name [String]

Explanation Database internal data error occurred.

Recommended Action No action is required.

Error Message
CallManager- 6 -DatabaseInternalDataError_073 : Database internal data error.. Device Type [String]

Explanation Database internal data error occurred.

Recommended Action No action is required.

Error Message
CallManager- 6 -DatabaseInternalDataError_075 : Database internal data error.. Text [String]

Explanation Database internal data error occurred.

Recommended Action No action is required.

Error Message
CallManager- 3 -DnTimeout : DN Timeout.. Port IsoEthPort [UInt] Port DSL [UInt]

Explanation Timeout was encountered while trying to read pattern or directory number configuration.

Recommended Action Investigate configuration for identified device.

Error Message
CallManager- 4 -H323AddressResolutionError : H323 address not resolved.. Device Name. [String]

Explanation An H323 device address could not be resolved. Cisco CallManager cannot handle calls to/from the indicated H323 device.

Recommended Action Either the H323 device entry is configured incorrectly, or the domain name system (DNS) is incorrectly configured.

Error Message
CallManager- 4 -H323CallFailureAlarm : H323 Call failure. Peer IP Address [String] Peer IP Port [UInt] Reason Code [Enum]

Explanation H.323 inbound call fails because information required to route the call, including the source E.164 address, call signaling address, or H.323 ID, is missing.

Recommended Action No action needed.

Reason Code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Unknown
2 SourceE164AddressNotFound
3 CallSignallingAddressNotFound
4 H323IdNotFound
5 SourceE164AddressOrCallSignallingAddressNotFound
Error Message
CallManager- 4 -MWIParamMisMatch : MWI parameter mismatch..

Explanation Message waiting indicator number configuration error occurred.

Recommended Action Investigate message waiting indicator configuration.

Error Message
CallManager- 4 -OutOfDnForAutoRegistration : Out of directory numbers for auto-registration..

Explanation Cisco CallManager ran out of directory numbers for auto-registration.

Recommended Action Investigate auto-registration configuration.

Error Message
CallManager- 6 -PktCapDownloadOK : Downloaded captured packet or key file.. Packet/Key file name [String]

Explanation Indicated the packet or key file has been downloaded.

Recommended Action No action is required.

Error Message
CallManager- 3 -PktCapDownloadFailed : Did not get captured packet or key file.. Packet/Key file name [String] Failed Reason [String]

Explanation Indicated reasons for the packet or key file could not be downloaded.

Recommended Action

Error Message
CallManager- 6 -PktCapLoginOK : Login OK for getting captured packet or key file.. User ID [String]

Explanation Indicated the user can get the packet or key file.

Recommended Action No action is required.

Error Message
CallManager- 3 -PktCapLoginFailed : Login failed for getting captured packet or key file.. User ID [String] Login Failed Reson [String]

Explanation Indicated the user cannot get the packet or key file.

Recommended Action It is required that the user is an valid End User under the user group called Standard Packet Sniffer Users.

Error Message
CallManager- 3 -ThrottlingSampleActivity : ThrottlingSampleActivity. Throttling Sample Activity [Int]

Explanation CallManager has initiated call throttling due to unacceptably high delay in handling incoming calls.

Recommended Action Determine the reason for high CPU usage in the High priority and Normal priority queues (Cisco CallManager System Performance object).

Error Message
CallManager- 6 -GatewayAlarm : Gateway alarm.. Device Name [String] TCP Handle [VoidPtr] Device Text [String] Param1 [UInt] Param2 [UInt]

Explanation Gateway device sent an alarm to Cisco CallManager.

Recommended Action No action is required.

Error Message
CallManager- 6 -NoConnection : No TCP connection..

Explanation Disconnect or release request attempt occurred on unknown TCP connection.

Recommended Action No action is required.

Error Message
CallManager- 6 -TotalCodeYellowEntry : TotalCodeYellowEntry. Total Code Yellow Entry [Int]

Explanation CallManager has initiated call throttling due to unacceptably high delay in handling incoming calls.

Recommended Action Determine the reason for high CPU usage in the High priority and Normal priority queues (Cisco CallManager System Performance object).

Error Message
CallManager- 5 -DestinationCodeControlCallBlocked : Call blocked by the Destination Code Control feature. . Route Pattern [String] Blocked Call Percentage [UInt] Calls Attempted [UInt] CallsRejected [UInt]

Explanation Cisco Unified Communications Manager generates this alarm when a Destination Code Control feature enabled Route Pattern blocks a call.The route pattern blocks a call when it comes in at a time when the number of call attempts has reached the percentage of calls set to be blocked on this route pattern.

Recommended Action This alarm is provided for historic and informational purposes. It helps understand why certain calls through the DCC feature enabled route patterns are rejected. This historical information is useful to help determine how many calls to a particular route pattern were attempted and how many out of them were blocked. This data would help the administrator verify whether the percentage of Calls Blocked by the DCC feature is as per the configured percentage.

Error Message
CallManager- 4 -Redirection : Redirection Manager cannot register with the Call Control.. Redirection Error Message [String]

Explanation The registration error occurs either when it registers itself or the REDIRECTION_OPERATIONIE_ID with the Call Control.

Recommended Action It is a code bug. No Action is Required.

Error Message
CallManager- 3 -CorruptedIncomingDMPropagationMessage : Unified CM received a corrupted DMRemoteDeviceRegisterUnRegister message in internode communication. Corrupted Register Elements Count [UInt] Corrupted UnRegister Elements Count [UInt] RemoteNodeID [UInt]

Explanation Unified CM examines the incoming DMRemoteDeviceRegisterUnRegister messages to detect values in the message that are outside the normal expected range. Unified CM issues this alarm when the message is determined by Unified CM to contain values outside the normal range. Unified CM has discarded part of the contents of the incoming DMRemoteDeviceRegisterUnRegsister message due to the values that were out of range. This may cause an out-of-synch condition for the registered device's information between the sending node and this node, which in turn can lead to phone calls being routed incorrectly

Recommended Action Make a note of the IP address/name of the remote CM node that generated this message. Around the timestamp of this alarm, save the SDL/SDI logs from this node and the remote node for analysis by Cisco TAC personnel. Next, at the first opportunity, restart the Cisco CallManager service on this node to ensure that the registered devices information throughout the cluster are in synch. Also, in Cisco Unified Serviceability, make sure to set the Unified CM SDI logs setting to Detailed to ensure collecting relevant logs should this alarm recur. If this alarm does occur again, contact Cisco TAC to help determine the source of DMRemoteDeviceRegisterUnRegister message corruption.

Error Message
CARAlarmCatalog- 3 -CARSchedulerJobFailed : Critical CAR scheduled job failed.. Job Name [String] Job Failure Cause [String] Job Failure Detail [String]

Explanation A critical CAR scheduled job failed for some reasons.

Recommended Action 1. Check the status of Cisco CAR DB service. 2. Check the status of Cisco CAR Scheduler service. 3. Check the Event Log from CAR page. 4. Check the contents in tbl_system_preferences table. 5. Check the number of records in tbl_billing_data, tbl_billing_error, and tbl_error_id_map tables. 6. Check if the scheduled job configuration is correct from CAR page. 7. Collect and check the CAR Scheduler traces for more details.

Error Message
CARAlarmCatalog- 3 -CARSchedulerJobError : CAR scheduled job failed.. Job Name [String] Job Failure Cause [String] Job Failure Detail [String]

Explanation A normal CAR scheduled job failed for some reasons.

Recommended Action 1. Check the status of Cisco CAR Scheduler service. 2. Check the Event Log from CAR page. 3. Check the contents in tbl_system_preferences table. 4. Check the number of records in tbl_billing_data, tbl_billing_error, and tbl_error_id_map tables. 5. Check if the scheduled job configuration is correct from CAR page. 6. Collect and check the CAR Scheduler traces for more details.

Error Message
CARAlarmCatalog- 3 -BadCDRFileFound : Bad CDR or CMR flat file found during CDR Load to CAR database.. File Name [String] First Bad Record Cause [String] File Summary [String]

Explanation A bad CDR or CMR flat file is found during loading to CAR database, the file could be corrupted for some reasons. However, CAR loader is able to skip the bad record(s) and load the good ones to CAR database.

Recommended Action 1. Find the bad file from the cdr_repository folders, and check its problematic record(s) based on the information given by the cause and summary. 2. Collect the associated SDI and SDL traces for the bad record(s) found in this file as soon as possible. 3. Collect and check the CAR Scheduler traces for more details.

Error Message
CARAlarmCatalog- -CARIDSEngineDebug : Indicates debug events from CAR IDS database engine.. Event Specific Message [String] Event class message [String] Event Class ID [String]

Explanation This alarm provides low-level debugging information from CAR IDS database engine. System administrator can disregard this alarm.

Recommended Action This is for debug information purposes only; no action is required.

Error Message
CARAlarmCatalog- 6 -CARIDSEngineInformation : No error has occurred but some routine event completed in CAR IDS database engine.. Event Specific Message [String] Event class message [String] Event Class ID [String]

Explanation This alarm is informational. No error has occurred but some routine event completed in CAR IDS database engine.

Recommended Action This is for information purposes only; no action is required.

Error Message
CARAlarmCatalog- 2 -CARIDSEngineCritical : Pay Attention. This alarm does not compromise data or prevent the use of the system.. Event Specific Message [String] Event class message [String] Event Class ID [String]

Explanation Pay Attention. This alarm does not compromise data or prevent the use of the system.

Recommended Action This alarm needs monitoring by the CAR DB admin.

Error Message
CARAlarmCatalog- 3 -CARIDSEngineFailure : Combined alarm for emergency and error situations. Something unexpected occurred that might compromise data or access to data or cause CAR IDS to fail.. Event Specific Message [String] Event class message [String] Event Class ID [String]

Explanation This alarm indicates combined alarm for emergency and error situations. Something unexpected occurred that might compromise data or access to data or cause CAR IDS to fail.

Recommended Action Requires CAR DB admin intervention.

Error Message
CDPAlarmCatalog- 2 -DUPLEX_MISMATCH : Duplex Mismatch Alarm. Switch Duplex Settings [String] Local Interface Duplex Settings [String]

Explanation This alarm is generated by Cisco CDP whenver there is a duplex mismatch between local inetrface and switch interface.

Recommended Action Ensure that Duplex settings are set to auto or full on local inetrface as well as switch interface

Error Message
CDRMamangementAlarmCatalog- 3 -CDRFileDeliveryFailed : (s)FTP delivery of CDR files to the outside billing server failed.. BillingServerAddress [String]

Explanation (s)FTP develiry of CDR files to the Billing Server outside of the cluster failed because of timeout or other reasons. Email alert will be sent to the admin.

Recommended Action 1. Check network link status. 2. Check if billing server is alive. 3. Check if (s)FTP Server on the billing server is running and accepting request. 4. Check if CDRM Configuration is correct - under Serviceability->Tools. 5. check CDR Repository Manager trace.

Error Message
CDRMamangementAlarmCatalog- 3 -CDRAgentSendFileFailed : CDR Agent cannot send CDR files from CCM node to CDR Repository node within the CCM cluster. CDRRepositoryNodeAddress [String] CDRAgentNodeAddress [String]

Explanation CDR Agent cannot send CDR files from CCM node to CDR Repository node within the cluster because of timeout or other reasons. Email alert will be sent to the admin.

Recommended Action 1. Check network link status. 2. Check if CDR Repository node (first node in the cluster) is alive. 3. Check if CDR Repository Manager is activated on the first node. 4. Check CDRM Configuration under Serviceability->Tools. 5. Check CDR Agent trace on the specific node where error occurred. 6. Check CDR Repository Manager trace. 7. Check if the Publisher is being upgraded. If the CDRAgentSendFileFailureContinues alarm is no longer present, the condition is corrected.

Error Message
CDRMamangementAlarmCatalog- 4 -CDRHWMExceeded : High Water Mark for CDR files reached, some successfully delivered CDR files have been deleted. DiskUsageInMB [String]

Explanation The CDR files disk usage has exceeded the High Water Mark. CDRM deleted some successfully delivered CDR files that are still within the preservation duration, in order to bring the disk usage down to below HWM. Email alert will be sent to the admin.

Recommended Action 1. The preservation duration may be too long. Reduce it at Serviceability->Tools->CDR Management. 2. Or to raise maximum allocated disk space and/or HWM for CDR files.

Error Message
CDRMamangementAlarmCatalog- 2 -CDRMaximumDiskSpaceExceeded : The CDR files disk usage exceeded maximum disk allocation. Some undelivered files may have been deleted to bring disk usage down.. DiskUsageInMB [String]

Explanation The CDR files disk usage has exceeded the maximum allocated disk space. CDRM may have deleted some CDR files that have not been sent to the outside billing servers yet, in order to bring the disk usage down to below High Water Mark. The decision whether to delete undelivered files or not depends on how deletionDisable flag is configured at CDRM Configuration page. Email alert will be sent to the admin.

Recommended Action 1. Check if there are too many undelivered CDR files accumulated due to some condition. 2. Check network link status. 3. Check if billing server is alive. 4. Check if (s)FTP Server on the billing server is running and accepting request. 5. Check if CDRM Configuration for billing servers is correct - under Serviceability->Tools. 6. Check if CDR files maximum disk allocation is too low - under Serviceability->Tools. 7. Check CDR Repository Manager trace under /var/log/active/cm/trace/cdrrep/log4j.

Error Message
CDRMamangementAlarmCatalog- 3 -CDRFileDeliveryFailureContinues : (s)FTP delivery of CDR files failed on retries.. BillingServerAddress [String]

Explanation (s)FTP develiry of CDR files to the Billing Server outside of the cluster failed on retries after the initial failure.

Recommended Action 1. Check network link status. 2. Check if billing server is alive. 3. Check if (s)FTP Server on the billing server is running and accepting request. 4. Check if CDRM Configuration is correct - under Serviceability->Tools. 5. check CDR Repository Manager trace.

Error Message
CDRMamangementAlarmCatalog- 3 -CDRAgentSendFileFailureContinues : CDR Agent cannot send CDR files from CCM node to CDR Repository node on retries.. CDRRepositoryNodeAddress [String] CDRAgentNodeAddress [String]

Explanation CDR Agent cannot send CDR files on retries after the initial failure from CCM node to CDR Repository node within the cluster.

Recommended Action 1. Check network link status. 2. Check if CDR Repository node (first node in the cluster) is alive. 3. Check if CDR Repository Manager is activated on the first node. 4. Check CDRM Configuration under Serviceability->Tools. 5. Check CDR Agent trace on the specific node where error occurred. 6. Check CDR Repository Manager trace. 7. Check if the Publisher is being upgraded.

Error Message
CEFAlarmCatalog- 4 -QRTRequest : User submitted problem report using Quality Report Tool.. Category [String] Reason Code [String] Report Timestamp [String] Device name. [String] Device IP address. [String] Directory number [String]

Explanation User has experienced a problem with Phone and has submitted problem report.

Recommended Action Investigate the cause for problem report.

Error Message
CertMonitorAlarmCatalog- 6 -CertExpiryApproaching : Information Alarm that Indicates a Certificate Validity Period is approaching and the expiry date is within the notification window configured . Message [String]

Explanation Certificate Expiry Date is approaching shortly and Certificate is going to be invalid.

Recommended Action Re-generate the certificate that is about to Expire from Certificate Management UI from CUOS Administration web Page. If the Certificate is issued by a CA, Generate a CSR, Submit CSR to CSA ,obtain a fresh certificate from CA and upload it to CUCM

Error Message
CertMonitorAlarmCatalog- 0 -CertExpired : Certificate has Expired and needs to be changed at the earliest. Message [String]

Explanation The Validity Date of the Certificate indicated is over and the Certificate is expired.

Recommended Action Re-generate the certificate that is about to Expire from Certificate Management UI from CUOS Administration web Page. If the Certificate is issued by a CA, obtain a fresh certificate from CA and upload it to CUCM.

Error Message
CertMonitorAlarmCatalog- 1 -CertValidLessthanADay : Certificate is about to Expire in less than 24 hours or has Expired . Message [String]

Explanation The Validity of the Certificate indicated in the notification message is less than 24 hours .

Recommended Action Re-generate the certificate that is about to Expire from Certificate Management UI from CUOS Administration web Page. If the Certificate is issued by a CA, Generate a CSR, Submit CSR to CA, obtain a fresh certificate from CA and upload it to CUCM

Error Message
CertMonitorAlarmCatalog- 2 -CertValidfor7days : Alarm to indicate that Certificate has Expired or Expires in less than seven days. Message [String]

Explanation The Certifciate is invalid or Validity of the Certificate indicated in the notification less than 7 days.

Recommended Action Re-generate the certificate that is about to Expire from Certificate Management UI from CUOS Administration web Page. If the Certificate is issued by a CA, Generate a CSR, Submit CSR to CA, obtain a fresh certificate from CA and upload it to CUCM

Error Message
CertMonitorAlarmCatalog- -CertExpiryDebug : Alarm to Debug Certificate Management . Message [String]

Explanation Alarm used for Debug Purpose

Recommended Action None

Error Message
CertMonitorAlarmCatalog- 3 -CertExpiryError : Alarm that Indicating erros in certificate Expiry Monitor Process . Message [String]

Explanation Certificate is expiring

Recommended Action Regenerate or reimport certificate.

Error Message
CertMonitorAlarmCatalog- 5 -CertValidityOver30Days : Alarm to Indicate certificate to Expiry is approaching but expiry date is more than 30 days . Message [String]

Explanation Information Alarm that Indicates a Certificate Validity Period is approaching and validity of certificate is more than 30 days

Recommended Action Re-generate the certificate that is about to Expire from Certificate Management UI from CUOS Administration web Page. If the Certificate is issued by a CA, Generate a CSR, Submit CSR to CA, obtain a fresh fresh certificate from CA and upload it to CUCM

Error Message
CertMonitorAlarmCatalog- 4 -CertValidLessThanMonth : Alarm that indicates Certificate Expire in 30 days or lesser . Message [String]

Explanation The Expiry date of the Certificate indicated in the notification is less than a month

Recommended Action Re-generate the certificate that is about to Expire from Certificate Management UI from CUOS Administration web Page. If the Certificate is issued by a CA, Generate a CSR, Submit CSR to CA, obtain a fresh certificate from CA and upload it to CUCM.

Error Message
CertMonitorAlarmCatalog- 2 -TomcatCertRegen : Alarm that indicates the tomcat certificate is regenerated. Message [String]

Explanation This alarm indicates that tomcat certificate has been regenerated or CA signed Tomcat Certificate has been uploaded.

Recommended Action Restart the tomcat service for the new tomcat certificate to be effective. If EMCC feature is enabled for the communication across the clusters, perform the bulk certificate management provisioning for tomcat unit from Cisco Unified OS Administration Webpage

Error Message
CertMonitorAlarmCatalog- 0 -CertificateRevoked : Alarm indicates that recently uploaded certificate is revoked and needs to be changed at the earliest.. Message [String]

Explanation This alarm indicates that recently uploaded third party signed certificate or trust certificate is revoked.

Recommended Action Delete revoked trust certificate and re-upload it from Cisco Unified OS Administration Webpage. In case of third party signed (own) certifiate, just re-upload new certificate.

Error Message
CertMonitorAlarmCatalog- 4 -CertificateRevokationStatusByOCSP : Alarm indicates that CUCM could not determine OCSP revocation status of recently uploaded certificate.. Message [String]

Explanation This alarm indicates that CUCM failed to determine revocation status of recently uploaded third party signed certificate or trust certificate.

Recommended Action Evaluate reason of certificate revocation failure. Delete and re-upload certificate if required.

Error Message
PlatformCatalog- 6 -CLM_IPSecCertUpdated : IPSec self-signed cert updated. . Node's Name or IP [String]

Explanation The IPSec self-signed cert from a peer node in the cluster has been imported due to a change.

Recommended Action No action is required.

Error Message
PlatformCatalog- 6 -CLM_IPAddressChange : IP address change in cluster. . Node's Name [String] Node's Old IP [String] Node's New IP [String]

Explanation The IP address of a peer node in the cluster has changed.

Recommended Action No action is required.

Error Message
PlatformCatalog- 6 -CLM_PeerState : Current ClusterMgr session state.. Node's Name or IP [String] Node's State [String]

Explanation The ClusterMgr session state with another node in the cluster has changed to the current state.

Recommended Action No action is required.

Error Message
PlatformCatalog- 1 -CLM_MsgIntChkError : ClusterMgr message integrity check error. . Sender's IP address [String]

Explanation ClusterMgr has received a message which has failed a message integrity check. This can be an indication that another node in the cluster is configured with the wrong security password.

Recommended Action Verify message is coming from an expected IP address. Verify the security password on that node.

Error Message
PlatformCatalog- 3 -CLM_UnrecognizedHost : ClusterMgr unrecognized host.. Node's IP address [String]

Explanation ClusterMgr has received a message from an IP address which is not configured as a node in this cluster.

Recommended Action Verify that this IP address is currently configured as a server in this cluster.

Error Message
PlatformCatalog- 4 -CLM_ConnectivityTest : CLM Connectivity Test Failed. . Node's IP [String] Error description [String]

Explanation Cluster Manager detected a network error.

Recommended Action Verify connectivity between cluster nodes and fix any network issues.

Error Message
CMIAlarmCatalog- 6 -CMIServiceStatus : Service is running and working properly. Service Priority [String]

Explanation CMI service is running and working properly

Recommended Action Informational purpose only; no action is required

Error Message
CMIAlarmCatalog- 1 -StopBitConfigurationError : The Cisco Messaging Interface service parameter, Stop Bits, has an invalid configuration. Illegal Stop Bit [String]

Explanation An invalid stop bit has been configured for the serial port that CMI uses to connect to the voice messaging system. It is possible that the Stop Bits value has been updated via AXL or a CLI command where validation of the value was not performed. For this reason, it is best to set this value in the Service Parameter Configuration window in Cisco Unified CM Administration so that the value can be validated against the accepted range of values for this field.

Recommended Action Verify that the Cisco Messaging Interface service parameter Stop Bits is set to a valid (allowable) value

Error Message
CMIAlarmCatalog- 1 -ParityConfigurationError : The CMI service parameter, Parity, has an invalid configuration. Illegal Parity [String]

Explanation An invalid parity has been configured for the serial port that CMI uses to connect to the voice messaging system. It is possible that the parity value has been updated via AXL or a CLI command where validation of the value was not performed. For this reason, it is best to set this value in the Service Parameter Configuration window in Cisco Unified CM Administration so that the value can be validated against the accepted range of values for this field.

Recommended Action Verify that the Cisco Messaging Interface service parameter Parity is set to a valid (allowable) value

Error Message
CMIAlarmCatalog- 5 -SMDIMessageError : SMDI message contains invalid DN. Invalid DN [String]

Explanation Some voice messaging systems send SMDI messages to Cisco Unified Communications Manager (Unified CM) with an invalid DN specifically for the purpose of verifying that Unified CM is functioning properly. In such cases, if the Validate DNs service parameter is set to True, CMI triggers this alarm because the DN cannot be found in the Unified CM database.

Recommended Action Verify that the Cisco Messaging Interface service parameter Validate DNs is set to false

Error Message
CMIAlarmCatalog- 5 -SMDICmdError : CMI receives an invalid incoming SMDI message. Invalid SMDI command [String]

Explanation There are two kinds of incoming messages that Cisco Unified Communications Manager can accept from the voice messaging system; they are OP:MWI(SP)nnnnnnn!(D) and RMV:MWI(SP)nnnnnnn!(D) (where:nnnnnnnnnn = station number (can be 7 or 10 digits), (D) = End Of Transmission, (SP) = space). The first message activates the message waiting indicator (MWI). The second deactivates the message waiting indicator. CMI triggers this alarm if the received MWI message doesn't have one of the acceptable formats as described.

Recommended Action Contact the vendor of the third-party voice messaging system and discover why it is sending SMDI message with an invalid format

Error Message
CMIAlarmCatalog- 1 -SerialPortOpeningError : When CMI tries to open the serial port, the operating system returns an error. Serial Port Opening Error [String]

Explanation For a system running CMI, the serial port through which the voice messaging system is connected is always USB0, and that value is configured in the Cisco Messaging Interface service parameter, Serial Port. It is possible that the Serial Port value has been updated via AXL or a CLI command where validation of the value was not performed. CMI triggers this alarm if the value in the Serial Port service parameter is anything other than USB0.

Recommended Action Ensure that USB0 is configured in the Cisco Messaging Interface service parameter Serial Port. Also, physically confirm that the cable is firmly connected to the USB0 port.

Error Message
CMIAlarmCatalog- 3 -SerialPortGetStatusError : When CMI tries to get the status of serial port, the operating system returns an error. Serial Port Getting Status Error [String]

Explanation CMI triggers this alarm when it can't get the status of the serial port. An inability to receive serial port status information could be caused by a loose or disconnected USB cable.

Recommended Action Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message
CMIAlarmCatalog- 3 -SerialPortSetStatusError : When CMI tries to set the status of serial port, the operating system returns an error. Serial Port Setting Status Error [String]

Explanation CMI triggers this alarm when it can't set the status of the serial port. An inability to receive serial port status information could be caused by a loose or disconnected USB cable.

Recommended Action Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message
CMIAlarmCatalog- 3 -WritingFileFailure : CMI failed to write SMDI messages to the serial port. Error Information [String]

Explanation CMI opened the serial port, however it failed to successfully write data to the serial port because the serial port returned an invalid handle value to CMI. The serial port may have returned an invalid handle because the system did not properly detect the USB cable.

Recommended Action Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message
CMIAlarmCatalog- 3 -ReadingFileFailure : CMI failed to read SMDI messages from the serial port. Error Information [String]

Explanation CMI opened the serial port, however it failed to successfully read data from the serial port because the serial port returned an invalid handle value to CMI. The serial port may have returned an invalid handle because the system did not properly detect the USB cable.

Recommended Action Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message
CMIAlarmCatalog- 3 -InvalidPortHandle : The handle for the opened serial port is invalid. Error Information [String]

Explanation CMI cannot read/write to the serial port because the serial port returned an invalid handle value to CMI. The serial port may have returned an invalid handle because the system did not properly detect the USB cable.

Recommended Action Make sure that the cable connecting the USB0 port and voice messaging system is firmly connected.

Error Message
CMIAlarmCatalog- 1 -VMDNConfigurationError : The Voice Mail DN for CMI is invalid. Invalid Voice Mail DN [String]

Explanation CMI can't register with Cisco Unified Communications Manager because of an invalid Voice Mail DN. This alarm occurs because the Cisco Messaging Interface service parameter, Voice Mail DN, is empty or has invalid characters other than digits (0-9). It is possible that the Voice Mail DN value has been updated via AXL or a CLI command where validation of the value was not performed. For this reason, it is best to set this value in the Service Parameter Configuration window in Cisco Unified CM Administration so that the value can be validated against the accepted range of values for this field.

Recommended Action Check the CMI service parameter Voice Mail DN to confirm that a valid directory number has been configured.

Error Message
CMIAlarmCatalog- 4 -ThreadKillingError : An error occurred when CMI tried to stop the CMI service. Error Information [String]

Explanation As a normal part of the process of stopping the CMI service, open threads are closed (killed). This alarm indicates that a timeout occurred which means that the shutdown process is taking longer than expected, causing the operating system to return an error.

Recommended Action Try restarting the CMI service. If the problem persists, collect the system/application event logs and the performance (perfmon) logs and report to Cisco Technical Assistance Center (TAC).

Error Message
CMIAlarmCatalog- 4 -MemAllocFailed : CMI tried to allocate memory and failed. Memory Allocation Failure [String]

Explanation Cisco Unified Communications Manager tried to read the Cisco Messaging Interface service parameters but not enough memory was allocated for the task and so the information could not be read.

Recommended Action Use the Real-Time Monitoring Tool to check performance counters related to system memory to learn whether any memory leaks or spikes in CPU are occurring. Correct any anomalous memory issues you find. If you do not find any issues with memory, collect the system/application event logs and the performance (perfmon) logs and report this alarm to the Cisco Technical Assistance Center (TAC).

Error Message
CMIAlarmCatalog- 1 -DBLException : Unable to connect to the DB. DBL Exception [String]

Explanation When CMI service is started, it tries to read CMI Service Parameters from DB. During this, if CMI cannot connect to the database, it triggers this alarm.

Recommended Action Check Database connection, then restart CMI.

Error Message
CMIAlarmCatalog- 1 -CMIException : Error while reading the database. CMI Exception [String]

Explanation This alarm is always associated with other alarms, which are triggered due to configuring CMI service parameter with invalid values or due to invalid handle value returned by the serial port.

Recommended Action Refer to the associated alarm for further information.

Error Message
CMIAlarmCatalog- 1 -UnknownException : Unknown error while connecting to DB.

Explanation When CMI service is started, it tries to read CMI service parameters from DB. During this, if there is an unknown error, CMI triggers this alarm.

Recommended Action Report to Customer Service representative.

Error Message
CMIAlarmCatalog- 5 -CMIServiceStarted : Service is now running.

Explanation CMI service has been started and running

Recommended Action Informational purpose only; no action is required

Error Message
CMIAlarmCatalog- 5 -CMIServiceStopped : Service is now stopping..

Explanation CMI Service has been stopped.

Recommended Action Informational purpose only; no action is required.

Error Message
CMIAlarmCatalog- -CMIDebugAlarm : This alarm is generated only for the purpose of debugging. Debug Message [String]

Explanation CMI has several debug messages which simulate the real-time situations

Recommended Action Report to Customer Service representative

Error Message
CMIAlarmCatalog- 3 -CCMConnectionError : CMI can't establish connection with the Cisco Unified Communications Manager. CallManager Name [String]

Explanation CMI can't establish connection with the Unified Communications Manager

Recommended Action Check the address/status of the CallManager and the network

Error Message
CMIAlarmCatalog- 3 -DisconnectionToCCM : CMI loses the connection with Unified Communications Manager. CallManager Name [String]

Explanation CMI loses the connection with the Cisco Unified Communications Manager

Recommended Action Check the status of the Unified Communications Manager and the Network

Error Message
CMIAlarmCatalog- 2 -WSAStartupFailed : Windows Socket startup failed. Error Information [String]

Explanation WinSock could not be started

Recommended Action Report to Customer Service representative.

Error Message
CMIAlarmCatalog- 5 -ConfigParaNotFound : CMI service configuration parameter is not found in Database. Parameter Name and Information [String]

Explanation CMI cannot find this process configuration parameter in process configuration table.

Recommended Action Report to Customer Service representative to get the database upgrade

Error Message
CMIAlarmCatalog- 1 -COMException : CMI catches an COM exception.. COM Exception [String]

Explanation

Recommended Action Check system setting and resource, then restart system.

Error Message
CtiManagerAlarmCatalog- 4 -ApplicationConnectionDropped : Application has dropped the connection to CTIManager. Last QBE PDU number [Long]

Explanation TCP or TLS connection between CTIManager and Application is disconnected

Recommended Action Possible causes include Application server power outage, network power outage, network configuration error, network delay, packet drops or packet corruption. It is also possible to get this error if the Unified CM node or application server is experiencing high CPU usage. Verify the application is up and running, verify network connectivity between the application server and Unified CM, and verify the CPU utilization is in the safe range for application server and Unified CM (this can be monitored using RTMT via CPU Pegging Alert)

Error Message
CtiManagerAlarmCatalog- 4 -CtiMaxConnectionReached : Maximum number of application connections is reached; application connection rejected.

Explanation Maximum number of CTI connections has been reached, no new connection will be accepted unless an existing connection is closed

Recommended Action Check the CTI Manager service parameter Maximum CTI Connections for the maximum number of connections. Carefully consider increasing the service parameter value or disconnecting CTI applications that are unnecessary. Refer to Unified CM Solution Reference Network Design document in www.cisco.com based on the version you are using for maximum number of applications and devices supported by CTI

Error Message
CtiManagerAlarmCatalog- 4 -InvalidQBEMessage : An invalid QBE PDU is received. CTI Connection type [String] Instance number [Long] QBE PDU number [Long]

Explanation QBE PDU from application is invalid

Recommended Action This alarm indicates that TSP/JTAPI has reported a QBE PDU that cannot be recognized by CTIManager. Contact the support organization for the affected application, install the JTAPI or TSP plugin and restart the application. JTAPI/TSP plugins are available from the Find and List Plugins window in Cisco Unified CM Administration (Application > Plugins)

Error Message
CtiManagerAlarmCatalog- 3 -CtiProviderOpenFailure : CTI application failed to open provider; application startup failed. CTIconnectionId [Long] Login User Id [String] Reason code. [Enum] IPaddress [String] IPv6address [String]

Explanation The application is unable to open provider. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode

Recommended Action Review the reason code and the recommended action within the reason code

Reason code.-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 Unknown
0x8CCC0075 (2362179701) Login request to authenticate user has timed out. Possible causes include LDAP server misconfiguration such as LDAP server referrals misconfiguration or Unified CM node experiencing high CPU usage. Recommended action is to verify the CPU utilization is in the safe range for Unified CM (this can be monitored using RTMT via CPU Pegging Alert)
0x8CCC0060 (2362179680) Directory login failed. Verify that credentials are not misconfigured, check the userID and password configured in the application matches with what is configured in Unified CM Admin under (User Management > End User or Application User)
0x8CCC005E (2362179678) Directory is unavailable. Verify that the LDAP server is reachable from Unified CM node, make sure that the network connectivity between Unified CM and the LDAP server by pinging the LDAP server host from Cisco Unified OS Administration and take steps to establish connectivity if it has been lost
0x8CCC00D1 (2362179793) Application is connecting to a non secure port but has security priviledges enabled for the user associated with the application. Check the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and verify the associated permissions information
0x8CCC005F (2362179679) Standard CTI Use permission is not enabled. Users associated with applications are required to be included in "Standard CTI Enabled" user group. Verify the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and review the associated permissions information
0x8CCC00D0 (2362179792) User is not enabled for a secure connection but the application connecting to secure port. Consider the application configuration and security configuration for the user, for TAPI applications review the Control Panel >Phone and Modem Options > Advanced > select a CiscoTSP > Configure... > Security and disable "Secure Connection to CTIManager". For JTAPI applications from JTPrefs choose Security and disable "Enable Secure Connection". Also check the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and verify the associated permissions information
0x8CCC011D (2362179869) Directory login failed - Password expired. The user's login credentials have expired. The user can change the password by logging into the Cisco Unified CM User Options website using his/her existing credentials. The Cisco Unified CM User Options website will display the logon status indicating that the password has expired and will prompt the user to enter a new password
0x8CCC011F (2362179871) Directory login failed - Account locked. A user has been locked out of his or her account. Lockouts can occur for one of the following reasons: 1) Too many tries: a user made too many login attempts using invalid credentials. Contact the user to confirm that he or she has been attempting to login. You can verify a user's login credential in Cisco Unified CM Administration (User Management > End User/Application User), select the User and click the Edit Credential button, then, under Credential Information, enable the Reset Hack Count checkbox to reset the hack count for this user and clear the Time Locked Due to Failed Login Attempts field. After the counter resets, notify the user that he or she can try logging in again. 2) Account locked by administrator: when warranted, an administrator can lockout a user's access. To do so, go to Cisco Unified CM Administration and click User Management > End User/Application User, select the user and click the Edit Credential button, then . To lock or unlock a user's account, under the Credential Information page, select or deselect the Locked by Administrator checkbox. 3) Account locked due to an extended period of inactivity: the Administrator must notify the user that his or her account has been locked due to inactivity. To unlock the user's account, the Administrator must change the password in Cisco Unified CM Administration by clicking under (User Management > End User/Application User), selecting the User and modifying the password in the End User/Application User Configuration window. After changing the password, notify the user about of his or her new password and encourage the user to change the password in Cisco Unified CM User Options to a new password of the user's choosing
Error Message
CtiManagerAlarmCatalog- 4 -CtiQbeFailureResponse : Requested operation from the application has failed. Error code [ULong] Sequence number [Long] Error message [String]

Explanation The requested operation from the application could not be performed because of a normal or abnormal condition

Recommended Action Verify whether the affected application is experiencing a problem. Contact the support organization for the affected application if the problem persists and provide sequence number and error message for further investigation

Error Message
CtiManagerAlarmCatalog- 6 -CtiProviderClosed : CTI application connection has been closed. Login User ID [String] Sequence number [Long] CTI connection Id [Long] IPAddress [String] IPv6Address [String] Reason code [Enum]

Explanation Application closed the provider. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode

Recommended Action This alarm is for informational purposes only; no action is required.

Reason code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 Unknown
1 Heart beat from application missed. Possible causes include network connectivity issues or Unified CM node experiencing high CPU usage. Make sure that the network connectivity between Unified CM and the application by pinging the application server host from Cisco Unified OS Administration and take steps to establish connectivity if it has been lost. Also check for and fix any network issues or high CPU usage on the application server
2 Unexpected shutdown; possibly cause is application disconnected the TCP connection. Also check for and fix any network issues or high CPU usage on the application server
3 Application requested provider close
4 Provider open failure; application could not be initialized
5 User deleted. User associated with the application is deleted from the Unified CM Administration
6 SuperProvider permission associated with the application is removed. Verify the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and review the associated permissions information
7 Duplicate certificate used by application. Verify the CAPF profile configuration for the user in Unified CM Admin under (User Management > End User CAPF Profile/Application User CAPF Profile), select the CAPF profile of the user and review the associated information
8 CAPF information unavailable. Verify the CAPF profile configuration for the user in Unified CM Admin under (User Management > End User CAPF Profile/Application User CAPF Profile), select the CAPF profile of the user and review the associated information
9 Certificate compromised. Verify the CAPF profile configuration for the user in Unified CM Admin under (User Management > End User CAPF Profile/Application User CAPF Profile), select the CAPF profile of the user and review the associated information
11 User is not authorized to connect to CTI using TLS. Consider the application configuration and security configuration for the user, for TAPI applications review the Control Panel >Phone and Modem Options > Advanced > select a CiscoTSP > Configure... > Security and disable "Secure Connection to CTIManager". For JTAPI applications from JTPrefs choose Security and disable "Enable Secure Connection". Also check the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and verify the associated permissions information
12 Standard CTI Use permission removed. Users associated with applications are required to be included in "Standard CTI Enabled" user group. Verify the user group configuration for the user in Unified CM Admin under (User Management > End User/Application User), select the user and review the associated permissions information
Error Message
CtiManagerAlarmCatalog- 6 -CtiProviderOpened : CTI application connection opened.. Login User Id [String] Sequence Number [Long] Version Number [String] CTI Connection Id [Long] IPAddress [String] IPv6Address [String] Unified CM-AssignedAppID [Long]

Explanation Application opened the provider successfully. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode.

Recommended Action This alarm is for informational purposes only; no action is required.

Error Message
CtiManagerAlarmCatalog- 3 -UnableToRegisterwithCallManagerService : Unable to communicate with the Cisco CallManager service. Unified CM Node ID [Long]

Explanation CTI cannot communicate with Cisco CallManager service to register supplementary service features

Recommended Action Check the status of the Cisco CallManager service in Cisco Unified Serviceability > Tools > Control Center - Featured Services. At least one Cisco CallManager service should be running in the cluster for CTIManager to register feature managers. Restart the CTIManager service if the problem persists. If CallManager service is active, verify network connectivity between the Unified CM node that hosts CTIManager service and Unified CM node that hosts CallManager service

Error Message
CtiManagerAlarmCatalog- 4 -CtiProviderCloseHeartbeatTimeout : CTI heartbeat timed out; application disconnected.

Explanation CTI heartbeat timeout occurred causing CTIManager to close the application connection

Recommended Action Heartbeat timeout could occur due to high CPU usage or network connectivity problems. Check for and fix any network issues or high CPU usage on the application server. If the application server is running the Microsoft Windows OS use Task Manager or Perfmon to determine the CPU usage. For applications in Linux use the top command to review CPU usage

Error Message
CtiManagerAlarmCatalog- 4 -CtiIncompatibleProtocolVersion : Incompatible protocol version. Message Version [VoidPtr] Compatible Versions [VoidPtr] Current Version [VoidPtr] Unified CM Version [String] IPAddress [String] IPv6Address [String]

Explanation The JTAPI/TAPI application version is not compatible with this version of CTIManager, so the received message has been rejected. The IP address is shown in either IPv4 or IPv6 format depending on the Application's IP addressing mode

Recommended Action Verify that the correct version of the application is being used. If you're unsure of the correct version, contact the application vendor and upgrade the JTAPI/TSP to the version provided by Cisco Unified Communications Manager. JTAPI/TSP plugins are available in Cisco Unified CM Administration (Application > Plugins)

Error Message
CtiManagerAlarmCatalog- 6 -CtiDeviceOpened : Device opened. Device Name [String] Sequence Number [Long] Device ID [Long] Device Type [Long] CTI connection Id [Long] MediaControlled [Bool] RTP Address [String] CmAssignedAppID [Long]

Explanation Application opened a device

Recommended Action This alarm is for informational purposes only; no action is required

Error Message
CtiManagerAlarmCatalog- 6 -CtiDeviceClosed : Device closed. Device Name [String] Device ID [Long] Device Type [Long] CTI Connection Id [Long] MediaControlled [Bool] RTP Address [String] Reason code. [Enum]

Explanation Application closed a device

Recommended Action This alarm is for informational purposes only; no action is required

Reason code.-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 Unknown
1 CallManager service is not available to process request; verify that the CallManager service is active. Check the Cisco Unified Serviceability Control Center section in Cisco Unified CM Administration (Tools > Control Center - Feature Services)
2 Device has unregistered with Cisco Unified Communications Manager
3 Device failed to rehome to Cisco Unified Communications Manager; verify that the device is registered
4 Device is removed from the Unified CM database
5 Application controlling the device has closed the connection
6 Route Point already registered by another application
7 CTI Port already registered by another application
8 CTI Port/Route Point already registered with dyamic port media termination
9 Enabling softkey failed for device; verify that the device is registered
10 Multiple applications have registered the device with media capability that do not match
11 This device is already controlled by another application
12 Protocol used by the device is not supported
13 Device is restricted for control by any application
14 Unable to communicate with database to retrieve device information
15 Device is resetting
16 Unable to register the device as specified media type is not supported
17 Unsuppported device configuration
18 Device is being reset
19 IPAddress mode does not match what is configured in Unified CM
Error Message
CtiManagerAlarmCatalog- 4 -CtiDeviceOpenFailure : Device Open failed. CTI Connection Id [Long] Device Name [String] ReasonCode [Enum]

Explanation Application is unable to open the device

Recommended Action Check the reason code and take appropriate action to resolve the issue

ReasonCode-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0x8CCC0013 (2362179603) Device is already opened by another application; identify the application that is controlling this device. You can determine this information from RTMT (CallManager->CTI Manager and CallManager->CTI Search)
0x8CCC00DA (2362179802) Unable to communicate with database; verify the CPU utilization is in the safe range for (this can be monitored using RTMT via CPU Pegging Alert)
0x8CCC009A (2362179738) Device is unregistering; wait for the device to register. Due to user initiated reset or restart of the device from Unified CM. Device should automatically register wait for few moments for the device to register
0x8CCC0018 (2362179608) Device is not in the user control list; verify whether the device is configured for control by this application. For the application to control the device it should be included in the user control list. To check whether the device is in the user control list, if the application uses an End User, check the Device Association section under the End User Configuration in Cisco Unified CM Administration (User Management > End User). If the application uses an Application User, check under Device Information section for that Application User in Cisco Unified CM Administration (User Management > Application User)
0x8CCC00F3 (2362179827) IPAddress mode (IPv4 or IPv6 or both) specified by the application does not match with IP Addressing mode that is configured in Unified CM Administration; check the IP addressing mode of the device in Cisco Unified CM Administration (Device > Device Settings > Common Device Configuration)
Error Message
CtiManagerAlarmCatalog- 6 -CtiDeviceOutofService : Device is out of service. Device ID [Long] CTI Connection Id [Long] Device Name [String]

Explanation Device is out of service

Recommended Action This alarm is for informational purposes only; no action is required

Error Message
CtiManagerAlarmCatalog- 6 -CtiDeviceInService : Device in service.. Device ID [Long] CTI Connection Id [Long] Device Name [String] Call Manager Id [Long]

Explanation Device is back in service

Recommended Action This alarm is for informational purposes only; no action is required

Error Message
CtiManagerAlarmCatalog- 6 -CtiLineOpened : Line opened. Sequence Number [Long] Directory Number [String] Partition [String] Device Name [String] CTI Connection Id [Long]

Explanation Application opened the line

Recommended Action This alarm is for informational purposes only; no action is required

Error Message
CtiManagerAlarmCatalog- 4 -CtiLineOpenFailure : Unable to open the line. CTI Connection Id [Long] Device Name [String] Directory Number [String] Partition [String] Reason [Enum]

Explanation Application is unable to open the line

Recommended Action Review the reason code and take appropriate action to resolve the issue

Reason-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 Unknown
0x8CCC0018 (2362179608) Device is not in the user control list; verify whether the device is configured for control by this application. For the application to control the device it should be included in the user control list. To check whether the device is in the user control list, if the application uses an End User, check the Device Association section under the End User Configuration in Cisco Unified CM Administration (User Management > End User). If the application uses an Application User, check under Device Information section for that Application User in Cisco Unified CM Administration (User Management > Application User)
0x8CCC0005 (2362179589) Line is not found in the device; possible cause could be that the line that previously existed on this device is not available. This could be due to a extension mobility login or logout
0x8CCC00D3 (2362179795) Administrator has restricted the Line to be controllable by application. If the intent of the Administrator is to allow control of this line, enable the check box labelled Allow control of Device from CTI, in Unified CM Administration under Call Routing > Directory Number and choose the line that should be controlled by this application
Error Message
CtiManagerAlarmCatalog- 6 -CtiLineClosed : Line closed.. Directory Number [String] Partition [String] CTI Connection Id [Long] Device Name [String] Reason code [Enum]

Explanation Application closed the line

Recommended Action This alarm is for informational purposes only; no action is required

Reason code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
0 Unknown
1 CallManager failure
2 Device has unregistered with Cisco Unified Communications Manager; wait for the device to register
3 CTI failed to rehome the line; verify that the device is registered
4 Undefined line, possible cause could be that line is no more active on that device due to extension mobility login or logout
5 Device removed
6 Provider controlling the device is closed
7 Protocol used by the device is not supported
8 Application cannot control this line as CTI Allow Control is not enabled. Administrator has restricted the Line to be controllable by application. If the intent of the Administrator is to allow control of this line, enable the check box labelled Allow control of Device from CTI, in Unified CM Administration under Call Routing > Directory Number and choose the line that should be controlled by this application
9 Unable to register the device; application specified media type is not supported
10 Device is being reset; verify that the device is registered before opening the line
11 Unsuppported device configuration
Error Message
CtiManagerAlarmCatalog- 6 -CtiLineOutOfService : Line is out of service. Directory Number [String] Partition [String] CTI Connection Id [Long] Device Name [String]

Explanation Line is going out of service

Recommended Action This alarm is for informational purposes only; no action is required

Error Message
CtiManagerAlarmCatalog- 6 -CtiLineInService : Line in service. Line ID [Long] CTI Connection Id [Long]

Explanation Line is back in service

Recommended Action This alarm is for informational purposes only; no action is required

Error Message
CtiManagerAlarmCatalog- 4 -UnableToSetorResetMWI : Error in setting message waiting indicator. Directory Number [String]

Explanation An error occurred when setting the message waiting indication (MWI) lamp

Recommended Action The line issuing the request to set the MWI lamp on the target line might not have the proper partitions/calling search space settings to allow it to reach the target line. Check the partitions and calling search space of the line that is requesting to set MWI on the target line. The target line should be able to receive a call from the line that is attempting to set MWI

Error Message
CtiManagerAlarmCatalog- 6 -RedirectCallRequestFailed : Request from application to redirect a call has failed. Sequence Number [Long] Directory Number [String] Partition [String]

Explanation CTIManager is unable to redirect a call

Recommended Action This alarm is for informational purposes only; no action is required

Error Message
CtiManagerAlarmCatalog- 4 -MaxDevicesPerProviderExceeded : Application has opened more devices than allowed.

Explanation An application has opened more devices than the limit set in the CTIManager service parameter, Maximum Devices Per Provider

Recommended Action The application is controlling more devices than the CTI support allows. Review the application configuration and remove devices that are not required to be controlled. The stability of the system will be impacted if the application does not restrict support to the device limit specified by CTI in the CTIManager service parameter, Maximum Devices Per Provider

Error Message
CtiManagerAlarmCatalog- 4 -MaxDevicesPerNodeExceeded : Application has opened more devices than the limit for each node.

Explanation An application has opened more devices than the limit set in the CTIManager service parameter, Maximum Devices Per Node.

Recommended Action One or more applications are controlling more devices than the CTI support allows on the specified Unified CM node. Review the application configuration and remove devices that are not required to be controlled. The stability of the system will be impacted if the total number of devices controlled by applications is not properly restricted to the device limit specified by the CTIManager service parameter, Maximum Devices Per Node

Error Message
CtiManagerAlarmCatalog- 4 -ApplicationConnectionError : CTIManager is unable to allow connections from Applications.. CTI Connection type [String] Instance number [Long]

Explanation CTIManager is unable to accept connections from applications

Recommended Action CTIManager has encountered problems initializing TCP connections. Restart the CTIManager service to resolve this problem

Error Message
CtiManagerAlarmCatalog- 3 -kCtiQbeLengthMisMatch : OutputQbeMessage: length mismatch..

Explanation QBE header length mismatch exists.

Recommended Action This alarm indicates that TSP/JTAPI is incompatible with the version of CTIManager. Contact the support organization for the affected application, install the JTAPI or TSP plugin and restart the application. JTAPI/TSP plugins are available from the Find and List Plugins window in Cisco Unified CM Administration (Application > Plugins).

Error Message
CtiManagerAlarmCatalog- 3 -kCtiInvalidQbeSizeAndOffsets : InvalidQBESizeAndOffsets; QBE message decoding encountered illegal size or offset..

Explanation QBE Packet received from the application is not encoded correctly.

Recommended Action A TSP/JTAPI interface error occurred; the QBE message may not be formatted correctly. TSP/JTAPI might be incompatible with the version of CTIManager. Install the JTAPI or TSP plugin (Cisco Unified CM Administration > Application > Plugins) and restart the application.

Error Message
CtiManagerAlarmCatalog- 3 -kCtiSsRegisterManagerErr : Unable to register CtiLine with SSAPI..

Explanation CTI cannot register CtiLine with SSAPI.

Recommended Action Check the status of the Cisco CallManager service in Cisco Unified Serviceability > Tools > Control Center - Featured Services. At least one Cisco CallManager service should be running in the cluster for CTIManager to register feature managers. Restart the CTIManager service if the problem persists.

Error Message
CtiManagerAlarmCatalog- 4 -kCtiMytcpErrSocketBroken : Socket connection has been broken..

Explanation The TCP connection has been lost.

Recommended Action Although connection to the application is lost, no action is required if lost connection was intentional. If loss of connectivity was unintentional, investigate what might have caused connectivity to be lost and restore the connection.

Error Message
CtiManagerAlarmCatalog- 4 -kCtiDirectoryLoginFailure : CTI directory login failure.. Sequence number [Long]

Explanation CTI Manager is unable to login to directory. As a result, the application may not be able to access the controlled device list.

Recommended Action In Cisco Unified CM Administration, verify that the correct username and password has been configured and is being used for CTIManager login. If LDAP is used for authentication, check to confirm that the LDAP synchronization is configured and is working.

Error Message
CtiManagerAlarmCatalog- 4 -kCtiDeviceOpenFailAccessDenied : DeviceOpenRequest failure.. User ID [String] Device Name [String] Device Type [Long]

Explanation Application is trying to access a device that is not in its control.

Recommended Action Check the application sending the request or add the device to the user control list.

Error Message
CtiManagerAlarmCatalog- 3 -kCtiIllegalQbeHeader : Illegal QBE header..

Explanation Because of illegal QBE header, QBE message has been rejected.

Recommended Action QBE header could be fragmented due to TCP fragmentation. Review your network configuration to fix any TCP fragmentation issue.

Error Message
CtiManagerAlarmCatalog- 4 -kCtiLineOpenFailAccessDenied : Line open failed.. Sequence Number [Int] Directory Number [String] Partition [String] Device Name [String] login ID of the user [String]

Explanation Application failed to open a line.

Recommended Action Add the device associated with the line to the user device control list.

Error Message
CtiManagerAlarmCatalog- 4 -kCtiIllegalEnumHandle : Enumeration handle is not valid.. Enumeration handle [Long] Enumeration object type [String]

Explanation The enumeration handle associated with the process of enumerating devices, lines or DNs is invalid.

Recommended Action Check whether all devices, lines or DNs configured for the application are available to the application. If the application uses an End User, check the Device Association section under the End User Configuration in Cisco Unified CM Administration (User Management > End User). If the application uses an Application User, check under Device Information section for that Application User in Cisco Unified CM Administration (User Management > Application User).

Error Message
CtiManagerAlarmCatalog- 4 -kCtiQbeMessageTooLong : Incoming QBE message exceeds input buffer size. CTI Connection type [String] Instance number [Long] Message length [Long]

Explanation An incoming QBE message exceeds the input buffer size and then gets dropped.

Recommended Action The size of the QBE packet could exceed the suggested size when the JTAPI/TSP version is not compatible with the version of CTIManager. Contact the application vendor and verify that the application is compatible with the version of Cisco Unified Communications Manager (Unified CM). If the application vendor requests you to, install the JTAPI or TSP plugin (Cisco Unified CM Administration > Application > Plugins) and restart the application.

Error Message
CtiManagerAlarmCatalog- 4 -kCtiNullTcpHandle : TranslateCtiQbeInputMessage: NULL TCP HANDLE!!! (QBE packet is dropped). PDU number [Long]

Explanation A null TCP handle is preventing the QBE packets to be reported to applications.

Recommended Action This problem typically happens due to a network connectivity failure. Check for and resolve any connectivity issues in your network.

Error Message
CtiManagerAlarmCatalog- 3 -kCtiEnvProcDevListRegTimeout : Directory change notification request time out..

Explanation CTIManager registration request to EnvProcDevList timed out; CTIManager will send another registration request.

Recommended Action Check and resolve network connectivity problems between Cisco Unified Communications Manager nodes.

Error Message
CtiManagerAlarmCatalog- 3 -kCtiMYTCPSendError : MYTCP_Send: send error..

Explanation TCP socket connection has been broken.

Recommended Action This problem occurs when an application is abruptly shut down or has lost network connectivity to CTIManager. Review your application and network connectivity and resolve any issues.

Error Message
CtiManagerAlarmCatalog- 2 -kCtiSdlErrorvException : Failed to create an internal process that is required to service CTI applications..

Explanation An unexpected internal SDL error caused a failure in creating CTIManager Service SDL Process.

Recommended Action An internal CTIManager error has occurred. Try Restarting the CTIManager service to resolve this problem, if it does resolve the problem restart the Unified CM Server.

Error Message
CtiManagerAlarmCatalog- 3 -kCtiTcpInitError : CTIManager service is unable to initialize TCP connection. Error Code [Int]

Explanation CTIManager service is unable to initialize TCP connection

Recommended Action CTIManager has encountered difficulty initializing TCP connections. Restart the CTIManager service to resolve this problem.

Error Message
CtiManagerAlarmCatalog- 3 -kCtiIllegalFilterSize : ProviderOpenRequest; illegal filter size..

Explanation ProviderOpenRequest has an illegal filter size.

Recommended Action The application is using an incompatible version of JTAPI/TSP and Cisco Unified Communications Manager. Install the JTAPI or TSP plugin (Cisco Unified CM Administration > Application > Plugins) and restart the application.

Error Message
CtiManagerAlarmCatalog- 4 -kCtiNewCallNotifyArrayOverflow : Possible internal array overflow condition while generating CTI NewCall event..

Explanation An unexpected internal error occurred.

Recommended Action Restart the CTIManager service if the problem persists.

Error Message
CtiManagerAlarmCatalog- 4 -kCtiExistingCallNotifyArrayOverflow : Possible internal array overflow condition while generating CTI ExistingCall event..

Explanation An unexpected internal error occurred.

Recommended Action Restart the CTIManager service if the problem persists.

Error Message
CtiManagerAlarmCatalog- 4 -kCtiLineCallInfoResArrayOverflow : Possible internal array overflow condition while generating response to application request for call information..

Explanation An unexpected internal error occurred.

Recommended Action Restart the CTIManager service if the problem persists.

Error Message
CtiManagerAlarmCatalog- 4 -kCtiUnknownConnectionHandle : Connection handle is not valid.. CTI Connection type [String] Instance number [Long]

Explanation A message has been received from an unknown connection, and then dropped.

Recommended Action This alarm occurs when a QBE packet is received from a connection that is already disconnected. This packet will be ignored by CTIManager and no action is required.

Error Message
CtiManagerAlarmCatalog- 3 -kCtiProviderOpenInvalidUserNameSize : Invalid userName size in ProviderOpen request.. login user Name size [Long]

Explanation User name length is invalid.

Recommended Action Ask user of CTI application to use correct userName and to check the user name in configuration. It should not be more than 31 characters.

Error Message
CTIStorageServer- 1 -STORAGE1000 : Could not create thread.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
CTIStorageServer- 1 -STORAGE1001 : Unexpected error. WaitForSingleObject failed.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
CTIStorageServer- 1 -STORAGE1002 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 1 -STORAGE1004 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 1 -STORAGE1005 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 1 -STORAGE1006 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 3 -STORAGE2002 : Lost connection to the CTI Server. Recover connection.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended 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 Message
CTIStorageServer- 3 -STORAGE2016 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 3 -STORAGE2017 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 3 -STORAGE2018 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (CPU and memory). Check log file for any ACMI related errors prior to this error. Set Threshold=DEBUG in this program's configuration file and attempt to recreate the problem.

Error Message
CTIStorageServer- 3 -STORAGE2019 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (CPU and memory). Check log file for any ACMI related errors prior to this error. Set Threshold=DEBUG in this program's configuration file and attempt to recreate the problem.

Error Message
CTIStorageServer- 3 -STORAGE2020 : An unexpected exception occurred.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
CTIStorageServer- 3 -STORAGE2021 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 3 -STORAGE2028 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 3 -STORAGE2029 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 3 -STORAGE2030 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 3 -STORAGE2033 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 3 -STORAGE2034 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 3 -STORAGE2035 : Failed to perform LDAP operation.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
CTIStorageServer- 3 -STORAGE2036 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 3 -STORAGE2038 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 3 -STORAGE2039 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 3 -STORAGE2050 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 3 -STORAGE2051 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 3 -STORAGE2052 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (CPU and memory). Check log file for any ACMI related errors prior to this error. Set Threshold=DEBUG in this program's configuration file and attempt to recreate the problem.

Error Message
CTIStorageServer- 3 -STORAGE2053 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (CPU and memory). Check log file for any ACMI related errors prior to this error. Set Threshold=DEBUG in this program's configuration file and attempt to recreate the problem.

Error Message
CTIStorageServer- 3 -STORAGE2054 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (CPU and memory). Check log file for any ACMI related errors prior to this error. Set Threshold=DEBUG in this program's configuration file and attempt to recreate the problem.

Error Message
CTIStorageServer- 3 -STORAGE2055 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (CPU and memory). Check log file for any ACMI related errors prior to this error. Set Threshold=DEBUG in this program's configuration file and attempt to recreate the problem.

Error Message
CTIStorageServer- 3 -STORAGE2056 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (CPU and memory). Check log file for any ACMI related errors prior to this error. Set Threshold=DEBUG in this program's configuration file and attempt to recreate the problem.

Error Message
CTIStorageServer- 3 -STORAGE2057 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (CPU and memory). Check log file for any ACMI related errors prior to this error. Set Threshold=DEBUG in this program's configuration file and attempt to recreate the problem.

Error Message
CTIStorageServer- 4 -STORAGE3000 : Could not detach thread.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
CTIStorageServer- 4 -STORAGE3001 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 4 -STORAGE3002 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 4 -STORAGE3003 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
CTIStorageServer- 6 -STORAGE4000 : Begin Enterprise Service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -STORAGE4001 : End Enterprise Service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -STORAGE4003 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -STORAGE4004 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -STORAGE4008 : Post install has populated LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -STORAGE4017 : Capacity reports.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -STORAGE4027 : Enterprise Server changing modes.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -STORAGE4028 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -STORAGE4029 : Lost connection to the CTI Server. Recover connection.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -STORAGE4030 : The state of the LDAP server is [1|0]. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -STORAGE4032 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -STORAGE4034 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -STORAGE4035 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -STORAGE4036 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -STORAGE4037 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -STORAGE4038 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -STORAGE4039 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -STORAGE4040 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -STORAGE4041 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -SKILLSTATENT0000 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -SKILLSTATENT0001 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -SKILLSTATENT2020 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -SKILLSTATENT2022 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -SKILLSTATENT2023 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -SKILLSTATENT2024 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -SKILLSTATENT2025 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -SKILLSTATENT2026 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -SKILLSTATENT2027 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -SKILLSTATENT2029 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -SKILLSTATENT2031 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
CTIStorageServer- 6 -SKILLSTATENT2033 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DBAlarmCatalog- 3 -kDbConnectionFailed : Database connection failed.. Additional Information [String]

Explanation An attempt to connect to database failed.

Recommended Action Enable trace for the database layer monitor to get specific error information.

Error Message
DBAlarmCatalog- 1 -NoDbConnectionAvailable : No database connection available..

Explanation Database layer could not find any working database connection.

Recommended Action In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for the Cisco Database Layer Monitor service. Check network connectivity and operation of SQL Server services.

Error Message
DBAlarmCatalog- 2 -ErrorChangeNotifyClientBlock : A change notification client is busy (blocked). If the change notification client continues to be blocked for 10 minutes, the system automatically clears the block and change notification should resume successfully..

Explanation Changes made to the database are not being consumed by one of the recipients. This does not always represent an issue. However, if the change notification client continues to be blocked for 10 minutes, the system automatically clears the block for all clients except the blocked one, which means that change notifications should resume successfully for all other clients. To clear the blocked client, you must restart the server.

Recommended Action At the command line interface (CLI) on the database server, execute the following command: show tech notify. The CLI command output will provide information about the block. Use Cisco Unified Serviceability to restart the server that was indicated in the alarm. You may also want to gather traces to examine them for anomalous activity during the time that client was blocked. In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for the Cisco Database Layer Monitor service. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message
DBAlarmCatalog- 3 -ErrorReadingInstalledRPMS : Could not read installed RPMs to populate component version table.

Explanation The function that reads the rpm version information and populates database failed

Recommended Action Please report this error to the administrator.

Error Message
DBAlarmCatalog- 3 -ErrorChangeNotifyClientTimeout : A change notification client was responding slowly and has been removed..

Explanation A change notification recipient hasn't responded to change notification in several minutes and was thus removed. This may delay call processing features, such as call forwarding and so on.

Recommended Action Rebooting the box will clear this situation. Alternatively, dbnotify trace could be analyzed to find the client that was removed and that service could be restarted in Cisco Unified Serviceability.

Error Message
DBAlarmCatalog- 1 -ErrorChangeNotifyReconcile : A change notification shared memory reconciliation has occurred..

Explanation The change notification buffers in shared memory have been rebuilt due to conflicts.

Recommended Action This problem may have been already corrected. If unexpected behavior is observed, restart all Cisco services in the cluster.

Error Message
DBAlarmCatalog- 6 -IDSEngineDebug : Indicates debug events from IDS database engine.. Event Class ID [String] Event class message [String] Event Specific Message [String]

Explanation This alarm provides low-level debugging information from IDS database engine. System administrator can disregard this alarm.

Recommended Action This is for debug information purposes only; no action is required.

Error Message
DBAlarmCatalog- 6 -IDSEngineInformation : No error has occurred but some routine event completed in IDS database engine.. Event Class ID [String] Event class message [String] Event Specific Message [String]

Explanation This alarm is informational. No error has occurred but some routine event completed in IDS database engine.

Recommended Action This is for information purposes only; no action is required.

Error Message
DBAlarmCatalog- 3 -IDSEngineCritical : Pay Attention. This alarm does not compromise data or prevent the use of the system.. Event Class ID [String] Event class message [String] Event Specific Message [String]

Explanation Pay Attention. This alarm does not compromise data or prevent the use of the system.

Recommended Action This alarm needs monitoring by the db admin

Error Message
DBAlarmCatalog- 3 -IDSEngineFailure : Combined alarm for emergency and error situations. Something unexpected occurred that might compromise data or access to data or cause IDS to fail. Event Class ID [String] Event class message [String] Event Specific Message [String]

Explanation This alarm indicates combined alarm for emergency and error situations. Something unexpected occurred that might compromise data or access to data or cause IDS to fail

Recommended Action Requires db admin intervention

Error Message
DBAlarmCatalog- 6 -IDSReplicationInformation : Information about IDS replication. Event Class ID [String] Event class message [String] Event Specific Message [String]

Explanation This alarm provides information about IDS replication.

Recommended Action Informational purposes only; no action is required

Error Message
DBAlarmCatalog- 3 -IDSReplicationFailure : Combined alarm for emergency and error situations. IDS Replication has failed. Event Class ID [String] Event class message [String] Event Specific Message [String]

Explanation This alarm indicates combined alarm for emergency and error situations. It indicates failure in IDS Replication

Recommended Action Requires db admin intervention

Error Message
DBAlarmCatalog- 3 -CUPImportFailure : Combined alarm for Integration, CUP import files has failed. Event Class ID [String] Event class message [String] Event Specific Message [String]

Explanation Combined alarm for Integration, CUP import files has failed

Recommended Action Check the network and files in the CUP server

Error Message
DBAlarmCatalog- 3 -DBUserLimitExceeded : An application or endpoint is using too many database resources. Database User [String]

Explanation This alarm indicates an error situation. Resources are not exhausted. The application will not be granted more connections to the database until the ones used are freed up.

Recommended Action Collect the trace using file get activelog cm/trace/dbl/sdi/limitexceeded*.tar.gz or by collecting the Cisco Database Layer Monitor trace in RTMT to determine the application or endpoint causing issues.

Error Message
DesktopMonitor- 3 -VOIP2000 : Mutex for CFCDMCritSection object. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2001 : Shutdown event.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2002 : LDAP Up/Down event. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2003 : Desktop Monitor adapter name in the Registry not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that installation has been completed and all required values are in the registry.

Error Message
DesktopMonitor- 3 -VOIP2005 : IOR Hostname entry in the Registry not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that installation has been completed and all required values are in the registry.

Error Message
DesktopMonitor- 3 -VOIP2007 : initialization event not created. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2008 : Desktop Monitoring initialization thread not created. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2009 : CDesktopMonitor object not created. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2010 : CFCDMMonitorServerList object not created. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2011 : Corba listening thread not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2012 : CFCDMCritSection object not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2013 : CFCDMSniffer object not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2014 : Periodic Cleanup thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2015 : LDAP Connection Monitoring thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2016 : Logout event creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2017 : Login thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2019 : Login thread ended. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the log and debug files for related errors and restart.

Error Message
DesktopMonitor- 3 -VOIP2021 : Desktop monitoring enabled for extension. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Subsystem will recover automatically, no action needed unless further errors occur.

Error Message
DesktopMonitor- 3 -VOIP2023 : LDAP thread ended. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the log and debug files for related errors and restart.

Error Message
DesktopMonitor- 3 -VOIP2033 : Sniffing event object creation error. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2034 : Sniffer session shutdown event object creation error. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2035 : SnifferSession thread creation error. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2036 : Sniffer Session thread termination. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2037 : error opening NIC adapter. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
DesktopMonitor- 3 -VOIP2038 : network information not availabale. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
DesktopMonitor- 3 -VOIP2039 : Error while setting the sniffing filter. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
DesktopMonitor- 3 -VOIP2041 : Error receiving packets. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
DesktopMonitor- 3 -VOIP2042 : NIC adapter opened. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action required

Error Message
DesktopMonitor- 3 -VOIP2043 : packet sniffing started. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action required

Error Message
DesktopMonitor- 3 -VOIP2044 : packet sniffing stopped. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action required

Error Message
DesktopMonitor- 3 -VOIP2046 : socket creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart the VoIP Monitor service.

Error Message
DesktopMonitor- 3 -VOIP2048 : MAC Address not found. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Perform the following actions: 1. Check the CallManager database for changes. 2. Verify the FCVoIP ODBC DSN is correct. 3. Verify that the CallManager database is running. 4. Verify that a record for the extension exists in the CallManager database. 5. Reinstall the monitor service if it requires a new username or password.

Error Message
DesktopMonitor- 3 -VOIP2049 : Registry entries not found.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that installation has been completed and all required values are in the registry.

Error Message
DesktopMonitor- 3 -VOIP2050 : NIC monitoring adapter name not found. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action The VoIP Service is missing information required for start up.

Error Message
DesktopMonitor- 3 -VOIP2051 : process creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2052 : LRM thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2053 : VPN thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2054 : Corba thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2055 : NIC adapter opening failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
DesktopMonitor- 3 -VOIP2056 : NIC adapter not configured correctly . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
DesktopMonitor- 3 -VOIP2057 : error while setting the filter. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
DesktopMonitor- 3 -VOIP2061 : LDAP Monitor thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
DesktopMonitor- 3 -VOIP2062 : Fail to create Client interface. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action If problems continue, restart the service.

Error Message
DesktopMonitor- 3 -VOIP2063 : Fail to connect or reconnect to the current CM. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the status of the CallManager processes. There must be at least one CallManager with an active AXL database service in the cluster.

Error Message
DesktopMonitor- 3 -VOIP2064 : ODBC's failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify that the CallManager database is running.

Error Message
DesktopMonitor- 3 -VOIP2065 : OmniOrbUseHostName invalid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Contact TAC for assistance.

Error Message
DesktopMonitor- 3 -VOIP2066 : CallManager database connection initialization failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify that the CallManager database is running and that VoIP is configured correctly.

Error Message
DesktopMonitor- 3 -VOIP2067 : Unable to monitor agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Monitor service is running and active.

Error Message
DesktopMonitor- 3 -VOIP2068 : Unable to monitor agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Retry when the VoIP Monitor service recovery completes.

Error Message
DesktopMonitor- 3 -VOIP2069 : Unable to monitor agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
DesktopMonitor- 3 -VOIP2070 : Unable to monitor agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
DesktopMonitor- 3 -VOIP2071 : Unable to refresh the monitoring session with the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
DesktopMonitor- 3 -VOIP2072 : Unable to refresh the monitoring session with the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
DesktopMonitor- 3 -VOIP2073 : Unable to refresh the monitoring session with the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
DesktopMonitor- 3 -VOIP2074 : Unable to stop the monitoring session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
DesktopMonitor- 3 -VOIP2075 : Unable to stop the monitoring session for supervisor. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
DesktopMonitor- 3 -VOIP2076 : Unable to stop the monitoring session for supervisor. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
DesktopMonitor- 3 -VOIP2077 : Caught a Corba exception while testing the connection to the VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
DesktopMonitor- 3 -VOIP2079 : Unable to record Agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
DesktopMonitor- 3 -VOIP2080 : Unable to record Agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart

Error Message
DesktopMonitor- 3 -VOIP2081 : Corba exception Unable to record the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart

Error Message
DesktopMonitor- 3 -VOIP2082 : Unknown Corba exception.Unable to record the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart

Error Message
DesktopMonitor- 3 -VOIP2083 : Unable to record agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
DesktopMonitor- 3 -VOIP2084 : Unable to record agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running

Error Message
DesktopMonitor- 3 -VOIP2085 : Unable to record the agent with rtpAddress. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
DesktopMonitor- 3 -VOIP2086 : Unable to record the agent with rtpAddress. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
DesktopMonitor- 3 -VOIP2087 : Unable to record the agent with rtpAddress. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
DesktopMonitor- 3 -VOIP2088 : Unable to stop the recording session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
DesktopMonitor- 3 -VOIP2089 : Corba exception. Unable to stop the recording session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
DesktopMonitor- 3 -VOIP2090 : Unknown Corba exception. Unable to stop the recording session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
DesktopMonitor- 3 -VOIP2091 : Unable to get connection information for the VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
DesktopMonitor- 3 -VOIP2092 : Unable to get connection information for the VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
DesktopMonitor- 3 -VOIP2093 : Unable to initialize the Corba connection for VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
DesktopMonitor- 3 -VOIP2095 : Unable to get the VPN IP address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
DesktopMonitor- 3 -VOIP2096 : Error getting the MAC address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and configured correctly and restart.

Error Message
DesktopMonitor- 3 -VOIP2097 : Unknown Corba exception while looking for MAC address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
DesktopMonitor- 3 -VOIP2098 : Unable to get the MAC address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the VoIP Service logs

Error Message
DesktopMonitor- 3 -VOIP2099 : Error while looking for MAC address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the VoIP Service logs.

Error Message
DesktopMonitor- 3 -VOIP2100 : Invalid connection information for the VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
DesktopMonitor- 3 -VOIP2101 : Unable to initialize the Corba connection. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
DesktopMonitor- 3 -VOIP2102 : Unable to initialize Corba connection for desktop monitoring. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the Client is running and restart.

Error Message
DesktopMonitor- 3 -VOIP2103 : Unable to initialize Corba connection for recording extension. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the Client is running and restart.

Error Message
DesktopMonitor- 3 -VOIP2104 : Failed to start thread.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart.

Error Message
DesktopMonitor- 4 -VOIP3001 : Failed to create socket for VPN service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.

Error Message
DesktopMonitor- 4 -VOIP3002 : Unable to stop the monitoring session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.

Error Message
DesktopMonitor- 4 -VOIP3003 : Could not create the LDAP recovery thread. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.

Error Message
DesktopMonitor- 4 -VOIP3004 : Unsupported Codec format.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Use one of the supported codec formats. G279,aLaw or uLaw

Error Message
DesktopMonitor- 6 -VOIP4000 : Desktop Monitor name. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4001 : Desktop Monitoring module initialized. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4002 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4003 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4004 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4005 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4006 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4007 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4008 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4009 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4010 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4011 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4012 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4013 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4014 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4015 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4016 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4017 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4018 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4019 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DesktopMonitor- 6 -VOIP4020 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
DirAccessSynSvr- 1 -SYNC1000 : Could not install a Windows NT service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the error code provided in the message.Make sure the Sync service is not already running in the system.

Error Message
DirAccessSynSvr- 1 -SYNC1001 : Could not uninstall a Windows NT service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
DirAccessSynSvr- 1 -SYNC1002 : The argument passed to the program is invalid and the program will exit.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the argument passed to the Sync in the command line.

Error Message
DirAccessSynSvr- 1 -SYNC1003 : The Windows NT service is not able to register itself with the Windows NT service manager.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (CPU and memory).Make sure the Sync service properties are correct.Check the System Event Viewer for errors.

Error Message
DirAccessSynSvr- 1 -SYNC1004 : The initialization of the Windows NT service was unsuccessful.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
DirAccessSynSvr- 3 -SYNC2000 : The initialization of the Windows NT service was unsuccessful.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
DirAccessSynSvr- 3 -SYNC2001 : An error occurred while synchronizing agents.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
DirAccessSynSvr- 3 -SYNC2002 : An error occurred while synchronizing teams.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
DirAccessSynSvr- 3 -SYNC2003 : An error occurred while synchronizing queues.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
DirAccessSynSvr- 3 -SYNC2004 : An invalid request was received by the Windows NT service from the Windows NT service manager.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the System Event Viewer for errors.

Error Message
DirAccessSynSvr- 3 -SYNC2005 : Could not get CSQ description.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.

Error Message
DirAccessSynSvr- 3 -SYNC2006 : Failed to allocate memory for DirAccessSynSvr_i.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (memory).Search for other error messages.

Error Message
DirAccessSynSvr- 3 -SYNC2007 : Could not get resource list from the database.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Search the log for database related errors.

Error Message
DirAccessSynSvr- 3 -SYNC2008 : Could not get resource description from the database.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Search the log for database related errors.

Error Message
DirAccessSynSvr- 3 -SYNC2009 : Could not get CSQ list from the database.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Search the log for database related errors.

Error Message
DirAccessSynSvr- 3 -SYNC2010 : Could not get CSQ description from the database.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Search the log for database related errors.

Error Message
DirAccessSynSvr- 3 -SYNC2011 : Could not get MAC list from the database.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Search the log for database related errors.

Error Message
DirAccessSynSvr- 3 -SYNC2012 : Failed to allocate memory for SDeviceInfo.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (memory).Search for other error messages.

Error Message
DirAccessSynSvr- 3 -SYNC2013 : Failed to get periodic synchronization object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Search for other error messages.

Error Message
DirAccessSynSvr- 3 -SYNC2015 : Caught sync_server_exception.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read exception description.

Error Message
DirAccessSynSvr- 3 -SYNC2016 : Caught exception.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read exception description.

Error Message
DirAccessSynSvr- 3 -SYNC2017 : Failed to initialize the LCC object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read error description.Make sure the LDAP Monitor Service is up and running.

Error Message
DirAccessSynSvr- 3 -SYNC2018 : Failed to synchronize the LCC object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read error description.

Error Message
DirAccessSynSvr- 3 -SYNC2019 : Could not initialize ORB runtime (INITIALIZE).. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the log for network errors.Make sure that all appropriate Cisco services are up and running.Check system resource availability (memory, CPU)

Error Message
DirAccessSynSvr- 3 -SYNC2020 : A CORBA exception was caught.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read error description.Check for network communication errors.Make sure that all appropriate Cisco services are up and running.

Error Message
DirAccessSynSvr- 3 -SYNC2021 : Caught omniORB::fatalException.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read error description.Check for network communication errors.Make sure that all appropriate Cisco services are up and running.

Error Message
DirAccessSynSvr- 3 -SYNC2022 : CORBA server instance is null.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Search for other error messages.Check for network communication errors. Make sure that all appropriate Cisco services are up and running.

Error Message
DirAccessSynSvr- 3 -SYNC2023 : A CORBA error was caught.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check for network communication errors.Make sure that all appropriate Cisco services are up and running.

Error Message
DirAccessSynSvr- 3 -SYNC2024 : Could not connect to database, first try.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Search for database related error messages.Check the 'Logger Database' configuration section of the 'Cisco Agent Desktop Configuration Setup' application for proper values.

Error Message
DirAccessSynSvr- 3 -SYNC2025 : Could not connect to database, second try.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Search for database related error messages.

Error Message
DirAccessSynSvr- 3 -SYNC2026 : Failed to create synchronization thread.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Search for other error messages.Check system resource availability (memory, CPU).

Error Message
DirAccessSynSvr- 3 -SYNC2027 : An unexpected exception occurred when synchronizing LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
DirAccessSynSvr- 3 -SYNC2028 : An unexpected exception occurred when getting resource list from the SQL MGR.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Search the log for ODBC related errors.

Error Message
DirAccessSynSvr- 3 -SYNC2029 : An unexpected exception occurred when initializing the Sync service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the System Event Viewer for errors.

Error Message
DirAccessSynSvr- 3 -SYNC2030 : The Windows NT service was not removed successfully.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the System Event Viewer for errors.

Error Message
DirAccessSynSvr- 3 -SYNC2031 : An error occurred during synchronization of reason codes.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
DirAccessSynSvr- 3 -SYNC2032 : Failed to allocate memory for SSQL object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (memory).Search for other error messages.

Error Message
DirAccessSynSvr- 3 -SYNC2033 : Agent not found in ldap map.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Search for other error messages.

Error Message
DirAccessSynSvr- 4 -SYNC3000 : Could not delete agent from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.Make sure that the LDAP Monitor Service is up and running.

Error Message
DirAccessSynSvr- 4 -SYNC3001 : Could not add agent to LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.Make sure that the LDAP Monitor Service is up and running.

Error Message
DirAccessSynSvr- 4 -SYNC3002 : Could not add supervisor to LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.Make sure that the LDAP Monitor Service is up and running.

Error Message
DirAccessSynSvr- 4 -SYNC3003 : Could not update agent in LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.Make sure that the LDAP Monitor Service is up and running.

Error Message
DirAccessSynSvr- 4 -SYNC3004 : Could not delete supervisor from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.Make sure that the LDAP Monitor Service is up and running.

Error Message
DirAccessSynSvr- 4 -SYNC3005 : Could not update team in LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.Make sure that the LDAP Monitor Service is up and running.

Error Message
DirAccessSynSvr- 4 -SYNC3006 : Could not add team to LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.Make sure that the LDAP Monitor Service is up and running.

Error Message
DirAccessSynSvr- 4 -SYNC3007 : Could not delete team from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.Make sure that the LDAP Monitor Service is up and running.

Error Message
DirAccessSynSvr- 4 -SYNC3008 : Could not delete skill from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.Make sure that the LDAP Monitor Service is up and running.

Error Message
DirAccessSynSvr- 4 -SYNC3009 : Could not add skill to LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.Make sure that the LDAP Monitor Service is up and running.

Error Message
DirAccessSynSvr- 4 -SYNC3010 : Could not update skill in LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.Make sure that the LDAP Monitor Service is up and running.

Error Message
DirAccessSynSvr- 4 -SYNC3011 : Could not get resource list from SQL MGR.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.Check the communication with the ICM SQL Logger Database.

Error Message
DirAccessSynSvr- 4 -SYNC3012 : Could not allocate resource list.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (memory).Check for other error messsages.

Error Message
DirAccessSynSvr- 4 -SYNC3013 : Could not get resource description from the database.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.Check the communication with the ICM SQL Logger Database.

Error Message
DirAccessSynSvr- 4 -SYNC3014 : Could not get CSQ list from the database.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.Check the communication with the ICM SQL Logger Database.

Error Message
DirAccessSynSvr- 4 -SYNC3015 : Failed to reset periodic synchronizer.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Search for other errors.Check system resource availability (memory, CPU).

Error Message
DirAccessSynSvr- 4 -SYNC3016 : Failed to reset synchronizer.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Search the log for LDAP related errors.

Error Message
DirAccessSynSvr- 4 -SYNC3017 : Failed to reset the object synchronizer.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Search the log for LDAP related errors.

Error Message
DirAccessSynSvr- 4 -SYNC3018 : The peripheral not expected.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Search for other error messages.

Error Message
DirAccessSynSvr- 4 -SYNC3019 : ResetLog failed.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.

Error Message
DirAccessSynSvr- 4 -SYNC3020 : An unexpected exception occurred.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended 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 Message
DirAccessSynSvr- 4 -SYNC3021 : The program could not get the driver list from ODBC.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the System Event Viewer for system errors. Check system resource availability (memory, CPU). Check the communication with the ICM SQL Logger Database.

Error Message
DirAccessSynSvr- 4 -SYNC3022 : The program could not get the system data sources from ODBC.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the System Event Viewer for system errors. Check system resource availability (memory, CPU). Check the communication with the ICM SQL Logger Database.

Error Message
DirAccessSynSvr- 4 -SYNC3023 : The ODBC operation failed.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
DirAccessSynSvr- 4 -SYNC3024 : The program could not get the record values when fetching database columns.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check for other ODBC error messages. Check the System Event Viewer for system errors.

Error Message
DirAccessSynSvr- 4 -SYNC3025 : The program could not get the next record from the database.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check for other ODBC error messages. Check the System Event Viewer for system errors. Check system resource availability (memory, CPU).

Error Message
DirAccessSynSvr- 4 -SYNC3026 : The program could not get the table name from the database.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check for other ODBC error messages. Check the System Event Viewer for system errors. Check system resource availability (memory, CPU).

Error Message
DirAccessSynSvr- 4 -SYNC3027 : The program could not get the next table from the database.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check for other ODBC error messages. Check the System Event Viewer for system errors. Check system resource availability (memory, CPU).

Error Message
DirAccessSynSvr- 4 -SYNC3028 : The program could not get the list of tables from the database.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check for other ODBC error messages. Check the System Event Viewer for system errors. Check system resource availability (memory, CPU).

Error Message
DirAccessSynSvr- 4 -SYNC3029 : The program could not get the column description from the database.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check for other ODBC error messages. Check the System Event Viewer for system errors. Check system resource availability (memory, CPU).

Error Message
DirAccessSynSvr- 4 -SYNC3030 : The program could not get the number of columns returned from the query.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check for other ODBC error messages. Check the System Event Viewer for system errors.

Error Message
DirAccessSynSvr- 4 -SYNC3031 : The program could not execute the SQL statement.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check for other ODBC error messages.

Error Message
DirAccessSynSvr- 4 -SYNC3032 : The program could not prepare the SQL statement.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check for other ODBC error messages.

Error Message
DirAccessSynSvr- 4 -SYNC3033 : Unable to connect to the database.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check for other ODBC error messages. Check the communication with the ICM SQL Logger Database.

Error Message
DirAccessSynSvr- 4 -SYNC3034 : The query failed on second try.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the log for SQL error messages.

Error Message
DirAccessSynSvr- 4 -SYNC3035 : There is insufficient memory to handle the ODBC statement.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check for other ODBC error messages. Check the System Event Viewer for system errors. Check system resource availability (memory, CPU).

Error Message
DirAccessSynSvr- 4 -SYNC3036 : There is insufficient memory to establish an ODBC connection with the Enterprise host.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
DirAccessSynSvr- 4 -SYNC3037 : The program cannot communicate with the Enterprise host via ODBC.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
DirAccessSynSvr- 4 -SYNC3038 : There is insufficient memory to handle the ODBC statement.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
DirAccessSynSvr- 4 -SYNC3039 : Failed to get the switch type from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description. Make sure that the LDAP Monitor Service is up and running.

Error Message
DirAccessSynSvr- 4 -SYNC3040 : Failed to get the default LCC from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description. Make sure that the LDAP Monitor Service is up and running.

Error Message
DirAccessSynSvr- 4 -SYNC3041 : Failed to get the list of CallManagers from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description. Make sure that the LDAP Monitor Service is up and running.

Error Message
DirAccessSynSvr- 4 -SYNC3042 : Failed to add the CallManager to LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description. Make sure that the LDAP Monitor Service is up and running.

Error Message
DirAccessSynSvr- 4 -SYNC3043 : Failed to update the CallManager in LDAP. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description. Make sure that the LDAP Monitor Service is up and running.

Error Message
DirAccessSynSvr- 4 -SYNC3044 : Failed to remove the CallManager from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description. Make sure that the LDAP Monitor Service is up and running.

Error Message
DirAccessSynSvr- 4 -SYNC3045 : Failed to synchronize CallManagers.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the log for other error messages. Make sure that the LDAP Monitor Service is up and running.

Error Message
DirAccessSynSvr- 4 -SYNC3046 : Failed to get CallManager list from CRS.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the log for other error messages. Make sure that the CRS services are up and running.

Error Message
DirAccessSynSvr- 6 -SYNC4000 : Currently the service is not connected to LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action If this message repeats many consecutive times then look for other LDAP related messages.

Error Message
DirAccessSynSvr- 6 -SYNC4001 : Failed to run the SQL query for the second time.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check for other error messages. Make sure the MS SQL server name, database and port have correct values.

Error Message
DirAccessSynSvr- 6 -SYNC4003 : Service and version information.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4004 : The service is installed.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4005 : This service is already installed.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4006 : This service was installed.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4007 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4008 : This service has been uninstalled.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4009 : The Windows NT service was removed successfully.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4011 : The Windows NT service has started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4012 : The Windows NT service received a stop message from the Windows NT service manager.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4013 : The Windows NT service received a pause message from the Windows NT service manager.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4014 : The Windows NT service is paused.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4015 : The Windows NT service has stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4016 : The Windows NT service received a continue message from the Windows NT service manager.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4017 : The Windows NT service received a shutdown message from the Windows NT service manager.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4018 : The Windows NT service received a user control message from the Windows NT service manager.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4019 : cwsRscID length is zero.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4020 : CSQID length is zero.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4021 : Server is not active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4022 : Could not read server's registry values setting root path relative.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4023 : Could not reset LDAP server.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4024 : DetectRegistryChg encountered an error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4025 : Waiting for IOR hostname to be populated in registry.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4026 : Change server to standby.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4027 : Change server to active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4028 : Could not create ODBC object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4029 : The program cannot communicate with the Enterprise host via ODBC.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4030 : There is insufficient memory to establish an ODBC connection with the Enterprise host.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4031 : The program failed to connect to the ODBC client on the PC.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4032 : IOR hostname set in registry.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4033 : This reason code is reserved and will not be added to LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4034 : A change happened to a CallManager.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4035 : A new CallManager was detected.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DirAccessSynSvr- 6 -SYNC4036 : Team ID for an Agent was NULL. Setting to default.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
DRFAlarmsCatalog- 3 -DRFTruststoreMissing : DRF uses ipsec truststore certificate for securing communication between the MA and LA service. This certificate is missing on the node. Reason [String]

Explanation DRF uses ipsec truststore certificate for securing communication between the MA and LA service. This certificate is missing on the node, DRF LA will not be able to connect to MA

Recommended Action Download ipsec.pem file from Publisher and upload it as ipsec-trust only on the missing node then restart Cisco DRF Local service.

Error Message
DRFAlarmsCatalog- 3 -DRFUnknownClient : The DRF Master Agent running on the Publisher has received a Client connection request from an unknown server outside the cluster.The request has been rejected. Reason [String]

Explanation The DRF Master Agent running on the Publisher has received a Client connection request from an unknown server outside the cluster.The request has been rejected.

Recommended Action Remove the suspect server from the network. Refer to the Reason section for suspect servers: Hostname and IP Address

Error Message
DRFAlarmsCatalog- 3 -DRFSecurityViolation : The DRF System has detected a malicious pattern which could result in a security violation. Reason [String]

Explanation The DRF Network Message contains a malicious pattern which could result in a security violation like code injection or directory traversal. DRF Network Message has been blocked.

Recommended Action Stop the Cisco DRF Master and Cisco DRF Local Agent Services

Error Message
DRFAlarmsCatalog- 3 -DRFMasterAgentStartFailure : DRF Master Agent was unable to start because it was unable to open port 4040.. Reason [String]

Explanation DRF Master Agent was unable to start because it was unable to open port 4040.

Recommended Action Check if port 4040 is not already in use.

Error Message
DRFAlarmsCatalog- 3 -DRFLocalAgentStartFailure : DRF Local Agent was not able to start because it was unable to connect to the Master Agent on port 4040. Reason [String]

Explanation DRF Local Agent was not able to start because it was unable to connect to the Master Agent on port 4040

Recommended Action Check if the CiscoDRFMaster and CiscoDRFLocal services are running

Error Message
DRFAlarmsCatalog- 3 -DRFLA2MAFailure : DRF Local Agent is not able to connect to Master Agent.. Reason [String]

Explanation DRF Local Agent is not able to connect to Master Agent.

Recommended Action Check if the Master Agent is up and the port is authorized.

Error Message
DRFAlarmsCatalog- 3 -DRFMA2LAFailure : Master Agent was unable to send a backup/restore request to the local agent.. Reason [String]

Explanation Master Agent was unable to send a backup/restore request to the local agent.

Recommended Action Restart the corresponding local agents and the master agent.

Error Message
DRFAlarmsCatalog- 3 -DRFBackupFailure : Cisco DRF Backup process failed.. Reason [String]

Explanation DRF Backup process encountered errors.

Recommended Action Check DRF logs for further details.

Error Message
DRFAlarmsCatalog- 3 -DRFRestoreFailure : DRF Restore process failed.. Reason [String]

Explanation DRF Restore process encountered errors.

Recommended Action Check DRF logs for further details.

Error Message
DRFAlarmsCatalog- 3 -DRFBackupDeviceError : DRF Backup process is failed due to backup device error.. Reason [String]

Explanation DRF Backup process is failed due to backup device error.

Recommended Action Check if the proper device has been specified in the DRF configurations.

Error Message
DRFAlarmsCatalog- 3 -DRFTapeDeviceError : DRF is unable to access tape device.. Reason [String]

Explanation DRF is unable to access tape device.

Recommended Action Check if tape drive is working properly and it contains a valid tape.

Error Message
DRFAlarmsCatalog- 3 -DRFLocalDeviceError : DRF is unable to access local device.. Reason [String]

Explanation DRF is unable to access local device.

Recommended Action Check if local location exists and is accessible.

Error Message
DRFAlarmsCatalog- 3 -DRFInternalProcessFailure : DRF internal process has encountered an error.. Reason [String]

Explanation DRF internal process has encountered an error.

Recommended Action Check DRF logs for details.

Error Message
DRFAlarmsCatalog- 3 -DRFRestoreInternalError : DRF Restore operation has encountered an error. Restore cancelled internally.. Reason [String]

Explanation DRF Restore operation has encountered an error. Restore cancelled internally.

Recommended Action Check DRF logs for details.

Error Message
DRFAlarmsCatalog- 3 -DRFMABackupComponentFailure : DRF was unable to backup at least one component.. Reason [String]

Explanation DRF requested a component to backup its' data. However, there was an error during the backup process and the component was not backed up.

Recommended Action Please check the component backup logs and contact support if needed.

Error Message
DRFAlarmsCatalog- 3 -DRFMARestoreComponentFailure : DRF was unable to restore at least one component.. Reason [String]

Explanation DRF requested a component to restore its' data. However, there was an error during the restore process and the component was not restored.

Recommended Action Please check the component restore logs and contact support if needed.

Error Message
DRFAlarmsCatalog- 3 -DRFMABackupNodeDisconnect : The node being backed up disconnected from the Master Agent prior to being fully backed up.. Reason [String]

Explanation The DRF Master Agent was running a backup operation on a CCM cluster, when one of the nodes disconnected before the backup operation was completed.

Recommended Action Please check the computer that disconnected during backup. If the computer was accidentally shutdown, restart the backup.

Error Message
DRFAlarmsCatalog- 3 -DRFNoRegisteredComponent : No registered components available, backup failed.. Reason [String]

Explanation DRF backup failed since no registered components are available.

Recommended Action Ensure at least one component is registered before attempting a backup.

Error Message
DRFAlarmsCatalog- 3 -DRFNoRegisteredFeature : No feature selected for backup.. Reason [String]

Explanation No feature selected for backup

Recommended Action Ensure at least one feature is configured before attempting a backup.

Error Message
DRFAlarmsCatalog- 3 -DRFMARestoreNodeDisconnect : The node being restored disconnected from the Master Agent prior to being fully restored.. Reason [String]

Explanation The DRF Master Agent was running a restore operation on a CCM cluster, when one of the nodes disconnected before the restore operation was completed.

Recommended Action Please check the computer that disconnected during restore. If the computer was accidentally shutdown, restart the restore.

Error Message
DRFAlarmsCatalog- 3 -DRFSftpFailure : DRF sftp operation has failed.. Reason [String]

Explanation DRF sftp operation has failed.

Recommended Action Ensure that the destination server is available, has appropriate permissions and sftp daemon is running.

Error Message
DRFAlarmsCatalog- 3 -DRFRegistrationFailure : DRF Registration operation failed.. Reason [String]

Explanation DRF Registration operation failed.

Recommended Action DRF Registration failed for a component due to some internal error. Check the DRF logs and contact support if needed.

Error Message
DRFAlarmsCatalog- 3 -DRFBackupCancelInternalError : DRF Backup operation has encountered an error. Backup cancelled internally.. Reason [String]

Explanation DRF Backup operation has encountered an error. Backup cancelled internally.

Recommended Action Check DRF logs for details.

Error Message
DRFAlarmsCatalog- 4 -DRFLogDirAccessFailure : DRF couldn't access the log directory.. Reason [String]

Explanation DRF couldn't access the log directory.

Recommended Action Ensure that the DRF user has required permission/enough space on DRF Log and Trace directory

Error Message
DRFAlarmsCatalog- 4 -DRFComponentDeRegistered : DRF succesfully de-registered the requested component.. Reason [String]

Explanation DRF succesfully de-registered the requested component.

Recommended Action Ensure that the component deregistered is not needed for further backup/restore operation.

Error Message
DRFAlarmsCatalog- 4 -DRFDeRegistrationFailure : DRF de-registration request for a component failed.. Reason [String]

Explanation DRF de-registration request for a component failed.

Recommended Action Please check the DRF logs and contact support if needed.

Error Message
DRFAlarmsCatalog- 4 -DRFDeRegisteredServer : DRF automatically de-registered all the components for a server.. Reason [String]

Explanation This server might have got disconnected from CCM cluster.

Recommended Action Nothing.

Error Message
DRFAlarmsCatalog- 4 -DRFSchedulerDisabled : DRF Scheduler is disabled because no configured features available for backup.. Reason [String]

Explanation DRF Scheduler is disabled because no configured features available for backup.

Recommended Action Ensure at least one feature is configured for the scheduled backup to run.

Error Message
DRFAlarmsCatalog- 6 -DRFComponentRegistered : DRF Succesfully Registered the requested component.. Reason [String]

Explanation DRF Succesfully Registered the requested component.

Recommended Action Ensure that the registered component is needed for backup/restore operation.

Error Message
DRFAlarmsCatalog- 6 -DRFSchedulerUpdated : DRF Scheduled backup configurations is updated automatically due to feature DeRegistration.. Reason [String]

Explanation DRF Scheduled backup configurations is updated automatically due to feature DeRegistration.

Recommended Action Ensure that the new configurations is appropriate one for the backup/restore operation.

Error Message
DRFAlarmsCatalog- 6 -DRFBackupCompleted : DRF backup completed successfully.. Reason [String]

Explanation DRF backup completed successfully.

Recommended Action Ensure that the backup operation completed successfully.

Error Message
DRFAlarmsCatalog- 6 -DRFRestoreCompleted : DRF restore completed successfully.. Reason [String]

Explanation DRF restore completed successfully.

Recommended Action Ensure that the restore operation completed successfully.

Error Message
DRFAlarmsCatalog- 3 -DRFFailure : DRF Backup or Restore process has failed.. Reason [String]

Explanation DRF Backup or Restore process encountered errors.

Recommended Action Check DRF logs for further details.

Error Message
DRFAlarmsCatalog- 4 -DRFNoBackupTaken : A valid backup of the current system was not found.. Reason [String]

Explanation A valid backup of the current system was not found after an Upgarde/Migration or Fresh Install.

Recommended Action It is recommended to perform a Backup using the Disaster Recovery System.

Error Message
EEMServer- 1 -EEM1000 : A connection to the IMAP service could not be made. The host name specified could not be resolved to an IP address.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check 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 Message
EEMServer- 1 -EEM1001 : A connection to the IMAP service could not be made, An attempt was made to connect to the server but was unsuccessful.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action This may be 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.Check 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 e.g. 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 Message
EEMServer- 1 -EEM1002 : A connection to the IMAP service could not be made, The user name and password are not valid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
EEMServer- 1 -EEM1003 : A connection to the IMAP service could not be made, An attempt was made to connect to the server but was unsuccessful.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action This is a catch all error for any error conditon not described by EEM1000-EEM1002 The message will be in the form of java exceptions which should provide an indicaiton as to why the conneciton 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.

Error Message
EEMServer- 1 -EEM1004 : A connection to the SMTP service could not be made. The host name specified could not be resolved to an IP address.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check 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 Message
EEMServer- 1 -EEM1005 : A connection to the SMTP service could not be made, An attempt was made to connect to the server but was unsuccessful.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action This may be be 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.Check 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 SMTP server.Try running the following command from the command line of your CAD server using your IMAP address and port e.g. telnet mail.mysmtpserver.com 25 If successful this should return something like: 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 Message
EEMServer- 1 -EEM1006 : A connection to the SMTP service could not be made.The user name and password are not valid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check to make sure the user name and password specified are valid.On an exchange server SMTP usernames are typically just a login ID.They are not as complicated as the IMAP user id For example, if your email address is "J.User@server.com", your Windows NT login name is "juser", your NT domain name is "dom", and your Exchange mailbox name is "Joe User", then you would need to use a username of "juser" when logging into the SMTP server. You may verify your usename an password using an email client like outlook or you can validate it by connecting to the server by using telnet See Microsoft Technet topic "How to Use Telnet to Test SMTP Communication" for details. A sumnmary 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 like: 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: Type EHLO mysmtpserver.com If successful this should return a bunch of lines beginning with 250 that last one should be the following: 250 OK Next try to log into the SMTP server To do this you will tye AUTH LOGIN into your telnet session. The server will respond with an encrypted prompt for your user name. You will need to enter your user name encrypted in base 64. There are many tools online to do this. Try doing a web search on the keywords: base64 converter The server will respond 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 usoing these will look something like the following: AUTH LOGIN 334 VXNlcm5hbWU6 bXluYW1l 334 UGFzc3dvcmQ6 bXlwYXNzd29yZA== If successful you will see the following: 235 2.7.0 Authentication successful. You may also wish to test whether you can actually send an email with this account by doing the following MAIL FROM:myname@mysmtpserver.com 250 2.1.0 myname@mysmtpserver.com....Sender OK RCPT TO:recipient@mysmtpserver.com 250 2.1.5 recipient@mysmtpserver.com....Recpient OK DATA 354 Please start mail input. Test of telnet smtp . 250 Mail queued for delivery.

Error Message
EEMServer- 1 -EEM1007 : A connection to the SMTP server could not be made, An attempt was made to connect to the server but was unsuccessful.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action This is a catch all error for any error conditon not described by EEM1004-EEM1006 The message will be in the form of java exceptions which should provide an indicaiton as to why the conneciton 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 Message
EEMServer- 1 -EEM1008 : The user specified does not have a mailbox located on the configured server. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the configured account can login and access their mailbox on the configured server.

Error Message
EEMServer- 3 -EEM2000 : Could not retrieve specified information from the data buffer.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Look for disruptions in the connection between the EEM Server and the Email Manager.

Error Message
EEMServer- 3 -EEM2001 : There is insufficient memory to run the EEM applet.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
EEMServer- 3 -EEM2002 : 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.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
EEMServer- 3 -EEM2003 : 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.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Manually remove this message from the mail store using a 3rd 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.

Error Message
EEMServer- 3 -EEM2004 : Client cannot retrieve specified event information from the socket message.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended 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 Message
EEMServer- 3 -EEM2005 : This is an internal error. The client is not configured with the information that it needs to locate the service.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
EEMServer- 3 -EEM2006 : A message in the outbox could not be sent because of an SMTP failure. This message is then moved to the "Not Sendable" folder on the mail store and will not be sent. This typically occurs because the SMTP server is not allowing the Agent E-mail Service user to send using the specified e-mail address.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure that the send-as address in CAD admin is correct for each CSQ and that the SMTP server allows you to send e-mails using that address.

Error Message
EEMServer- 3 -EEM2007 : A message in the outbox could not be sent because of an SMTP failure. This message is then moved to the "Not Sendable" folder on the mail store and will not be sent. This typically occurs because recipient e-mail address is invalid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
EEMServer- 4 -EEM3000 : Specifies that the IMAP connection attempt failed when trying the specified security type, and attempt will be made with the other security type.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action If you feel this attempt should have succeeded check the error message that occured prior to this, you may not have the securty set correctly on you IMAP server.

Error Message
EEMServer- 4 -EEM3001 : Specifies that the IMAP connection attempt failed when trying the specified security type, and attempt will be made with the other security type.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action If you feel this attempt should have succeeded check the error message that occured prior to this, you may not have the securty set correctly on you IMAP server.

Error Message
EEMServer- 4 -EEM3002 : Indicates that an email could not be transfered because of an error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the log to see the type of error.

Error Message
EEMServer- 4 -EEM3003 : The EmailUtils caught a TRYCREATE exception and will attempt to recover.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Under normal circumstances the application 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 Message
EEMServer- 4 -EEM3004 : 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.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
EEMServer- 6 -EEM0000 : Specifies the host, port and username and whether the connection is secure for the IMAP message store connection attempt.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is required.

Error Message
EEMServer- 6 -EEM0001 : Specifies the host, port and username and whether the connection is secure for the SMTP server connection attempt.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is required.

Error Message
EEMServer- 6 -EEM0002 : Indicates the message was sent successfully to the SMTP server. Note: Some virus checkers may intercept the message and spoof the SMTP protocol so as to make it seem the message was sent when it really wasn't there is no way to tell this is happening unless you sniff the SMTP protocol messages using a program like ethereal. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is required.

Error Message
EEMServer- 6 -EEM0003 : Specifies the host, port and username for the IMAP message store. Action: No action is required.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is required.

Error Message
EEMServer- 6 -EEM0004 : Specifies the host, port and username for the IMAP message store.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is required.

Error Message
EEMServer- 6 -EEM0005 : The socket client is shutting down.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is required.

Error Message
EEMServer- 6 -EEM0006 : Specifies the host, port and username and whether the connection is secure for the IMAP message store connection attempt.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is required.

Error Message
EEMServer- 6 -EEM0007 : Specifies the host, port and username and whether the connection is secure for the SMTP server connection attempt.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is required.

Error Message
EEMServer- 1 -EEMS1000 : The SocketService could not be started. . Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
EEMServer- 1 -EEMS1001 : The Java process could not be initialized. . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that a valid JRE is installed and that the JavaHome registry key for EEMServer is set correctly.

Error Message
EEMServer- 1 -EEMS1002 : The Java Email Manager service could not be started. . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the JVM was initialized and that all of the necessary jar files and configuration values are present.

Error Message
EEMServer- 1 -EEMS1003 : The Java Email Manager service could not be restarted during autorecovery.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart the EEM Service

Error Message
EEMServer- 3 -EEMS2001 : The Java Email Manager service could not determine the ID of the host.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the IOR hostname matches an LDAP Host N value in the Site setup registry.

Error Message
EEMServer- 3 -EEMS2002 : The Java Email Manager service could be initialized . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the Java process is running and that the connection is stable.

Error Message
EEMServer- 3 -EEMS2003 : The service was unable to connect to the RASCAL Service.This will cause email logging to fail for newly arrived messages. . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the RASCAL Service is active, and troubleshoot the connection using the RASCAL error message.

Error Message
EEMServer- 3 -EEMS2004 : The service has not received a heartbeat message from the java service in 30 seconds, the java service will be restarted. . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Service should recover automatically. If it doesn't, the entire EEM Service may need to be restarted.

Error Message
EEMServer- 3 -EEMS2005 : The service received an error communicating with the java service, the java service will be restarted.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Service should recover automatically. If it doesn't, the entire EEM Service may need to be restarted.

Error Message
EEMServer- 4 -EEMS3000 : Information for the agent that logged in could not be found.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check log for errors; this probably means that the agent logged out before login could complete.

Error Message
EEMServer- 4 -EEMS3001 : A message could not be assigned to an agent.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Probably means that the agent disconnected without logging out after requesting a message. Check that the agent sees the message when logging back in.

Error Message
EEMServer- 4 -EEMS3002 : No Email CSQs could be loaded.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the server has an active LDAP connection and that valid Email Skills exist in LDAP.

Error Message
EEMServer- 4 -EEMS3003 : The JVM specified by the JavaHome registry key could not be found.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the value is correct or that the correct version of the JVM was loaded anyway.

Error Message
EEMServer- 4 -EEMS3004 : The Java Email Manager service could not be stopped normally.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action The EEMService may need to be restarted if is not functioning correctly.

Error Message
EEMServer- 6 -EEMS0000 : Starting preference change event dispatch thread.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
EEMServer- 6 -EEMS0001 : Socket service has been started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
EEMServer- 6 -EEMS0002 : Socket service has been stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
EEMServer- 6 -EEMS0003 : An administrator client has logged in.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
EEMServer- 6 -EEMS0004 : An administrator client has logged out. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
EEMServer- 6 -EEMS0005 : An administrator has requested that the specified property be updated.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
EEMServer- 6 -EEMS0006 : An agent client has logged in.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
EEMServer- 6 -EEMS0007 : An agent client has logged out.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
EEMServer- 6 -EEMS0008 : A supervisor client has logged in.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
EEMServer- 6 -EEMS0009 : A supervisor client has logged ou. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
EEMServer- 6 -EEMS0010 : The service has become active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
EEMServer- 6 -EEMS0011 : The service has become inactive.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
EEMServer- 6 -EEMS0012 : The service side has been determined.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
EEMServer- 6 -EEMS0013 : The Java Email Manager process has been started. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
EEMServer- 6 -EEMS0014 : The Java Email Manager process has been stopped. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
EEMServer- 6 -EEMS0015 : The specified csq has been loaded from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
EEMServer- 6 -EEMS0016 : The connection to the JavaMailManager has been dropped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
EMAlarmCatalog- 3 -EMCCFailedInLocalCluster : EMCC Login failure in local Call Manager.. Device Name [String] Login Date/Time [String] Login UserID [String] Reason [String]

Explanation EMCC login could fail due to 1. Using devices incompatile with EMCC feature. 2. Unable to retrieve remote cluster information. 3. EMCC is restricted by the local cluster. 4. Untrusted Certificate received from the remote end while trying to establish a connection

Recommended Action 1. Validate if the device model supports EMCC (EMCC Documentation). 2. Ensure that every remote cluster added for EMCC has valid hostname/IP address(es) for EM and PSTN Access in the RemoteCluster administration page (Logon to CUCM Administration page -> System -> EMCC -> Remote Cluster). Also, ensure that these entries are enabled. 3. Ensure that a bundle of all tomcat certificates (PKCS12) has been imported into the local tomcat-trust keystore (Logon to OS Administration page -> Security -> Certificate Management -> Check the certificates in tomcat-trust).

Error Message
EMAlarmCatalog- 4 -EMCCFailedInRemoteCluster : EMCC Login failure at a remote Call Manager.. Device Name [String] Login Date/Time [String] Login UserID [String] Reason [String]

Explanation EMCC login could fail due to 1. User does not exist in any of the configured remote cluster. 2. User is not enabled for EMCC. 3. No free EMCC Base Device. 4. EMCC Access was prevented by remote cluster. 5. Untrusted Certificate received from the remote end while trying to establish a connection

Recommended Action 1. Ensure that the user is a valid EMCC user and make sure that user's home cluster is added as a EMCC remote cluster(Logon to CUCM Administration page -> System -> EMCC -> Remote Cluster -> Add New). 2. Contact remote site administrator to enable user for EMCC (Logon to CUCM Administration page -> User Management -> End User -> Select User -> Enable Extension mobility cross cluster checkbox) 3. Contact remote site administrator for adding / freeing up EMCC Base Devices (Logon to CUCM Administration page -> Bulk Administration -> EMCC -> Insert/Update EMCC). 4. Contact remote site administrator to validate the remote cluster setting for this cluster. 5. Ensure that a bundle of all tomcat certificates (PKCS12) has been imported into the local tomcat-trust keystore (Logon to OS Administration Page -> Security -> Certificate Management -> Check for all tomcat certificates in tomcat-trust).

Error Message
EMAlarmCatalog- 4 -UserInputFailure : EMCC Login failure due to invalid user input.. Device Name [String] Login Date/Time [String] Login UserID [String] Reason [String]

Explanation EMCC Login failed due to error in user input. This situation can arise due to 1. Invalid User Credentials. 2. Credentials have expired.

Recommended Action 1. Try again with valid credentials or try resetting the credentils.

Error Message
EMAlarmCatalog- 6 -EMCCUserLoggedIn : EMCC login was successful.. Device Name [String] Login Date/Time [String] Login UserID [String]

Explanation The user has successfully logged in to extension mobility cross-cluster (EMCC).

Recommended Action Informational purposes only; no action is required.

Error Message
EMAlarmCatalog- 6 -EMCCUserLoggedOut : EMCC logout was successful.. Device Name [String] Login Date/Time [String] UserID [String]

Explanation The user has successfully logged out of extension mobility cross-cluster (EMCC).

Recommended Action Informational purposes only; no action is required.

Error Message
EMAlarmCatalog- 6 -EMAppStarted : EM Application started . Servlet Name [String]

Explanation Application started successfully.

Recommended Action No action required.

Error Message
EMAlarmCatalog- 5 -EMAppStopped : EM Application stopped. Servlet Name [String]

Explanation Application is shutting down gracefully because of an unloaded from Tomcat.

Recommended Action No action required on this application.

Error Message
EMAlarmCatalog- 3 -EMAppInitializationFailed : EM Application not started. Servlet Name [String]

Explanation Error occurred while starting application.

Recommended Action See application logs for error. Default location for the logs are at /var/log/active/tomcat/logs/em/log4j/

Error Message
EMAlarmCatalog- 3 -EMServiceConnectionError : EM Service not reachable. Servlet Name [String]

Explanation EM Service might be down in one or more nodes in the cluster.

Recommended Action Check if Cisco Extension Mobility service is running on all nodes of the cluster where the service is activated.

Error Message
EMAlarmCatalog- 3 -NodeNotTrusted : Untrusted Node was contacted. Date/Time [String] Hostname/Ip Address [String]

Explanation Application could not establish secure connection (SSL handshake failure) with another application. It could be due to 1. Certificate for tomcat service where the application is hosted is not trusted (not present in the keytore)

Recommended Action 1. Ensure that "tomcat-trust" keystore on each CCM node contains the tomcat certificates for every other node within a cluster (Logon to OS Administration Page -> Security -> Certificate Management -> Check the certificates in tomcat-trust). 2. If EMCC is enabled, then ensure that a bundle of all tomcat certificates (PKCS12) has been imported into the local tomcat-trust keystore (Logon to OS Administration Page -> Security -> Certificate Management -> Look for certificates in tomcat-trust).

Error Message
FCCClient- 3 -FCCC2002 : Unable to create thread.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCClient- 3 -FCCC2003 : Unexpected error. WaitForSingleObject failed.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCClient- 3 -FCCC2004 : Unexpected error. WaitForMultipleObjects failed.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCClient- 3 -FCCC2005 : Network communication error.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCClient- 3 -FCCC2009 : Unexpected exception.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCClient- 3 -FCCC2009 : Unexpected exception.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCClient- 3 -FCCC2010 : Unable to open registry key.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCClient- 3 -FCCC2011 : Unable to read registry value.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended 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 Message
FCCClient- 3 -FCCC2014 : Unable to determine the local IP address. The program will continue to function, but VPN desktops will not be supported.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart the program if this is a VPN desktop (CAD/CSD). I 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 Message
FCCClient- 3 -FCCC2015 : The connection to the Desktop Chat Service has been lost. The program will attempt to reconnect automatically.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCClient- 3 -FCCC2016 : The transcript directory doesn't exist and was unable to be created.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check file permissions.

Error Message
FCCClient- 3 -FCCC2017 : The transcript file doesn't exist and was unable to be created.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check file permissions.

Error Message
FCCClient- 4 -FCCC3000 : Unable to close thread handle.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action The program should continue to function normally. Check system resource availability (CPU and memory). Monitor handle usage by this service.

Error Message
FCCClient- 4 -FCCC3001 : A failure occurred while starting to monitor a presence group.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Presence chatting may not work, check presence server status.

Error Message
FCCClient- 4 -FCCC3002 : A failure occurred while stopping to monitor a presence group.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Presence chatting may not work, check presence server status.

Error Message
FCCClient- 6 -FCCC0000 : Information message from FCCClient.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCCClient- 6 -FCCC0001 : Successfully connected to the Desktop Chat Service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCCClient- 6 -FCCC0013 : Unable to open registry key. Using default values.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCCClient- 6 -FCCC0014 : Unable to open registry key. Using default values.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCCClient- 6 -FCCC0029 : CORBA server started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCCServer- 1 -FCCS1001 : Unable to create thread.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCServer- 1 -FCCS1002 : Unable to start any working threads.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCServer- 1 -FCCS1003 : Error handling command line arguments.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCServer- 1 -FCCS1007 : Unexpected error.WaitForMultipleObjects failed.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCServer- 1 -FCCS1008 : Unexpected network communication error (omniORB fatalException).. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (CPU and memory). Check network settings.

Error Message
FCCServer- 1 -FCCS1009 : Unable to open registry key.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended 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 Message
FCCServer- 1 -FCCS1010 : Unable to read registry value.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended 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 Message
FCCServer- 1 -FCCS1011 : Unable to initialize log files.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action The service was unable to set up it's logging files. Check the INSTALLATION DIRECTORY registry value under HKEY_LOCAL_MACHINE\SOFTWARE\Spanlink\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 Message
FCCServer- 1 -FCCS1012 : Unexpected exception during network communication initialization (omniORB).. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify that the HKEY_LOCAL_MACHINE\SOFTWARE\Spanlink\CAD\Site Setup\IOR HOSTNAME registry value specify's a valid local hostname or IP address. Check system resource availability (CPU and memory).

Error Message
FCCServer- 1 -FCCS1013 : Unexpected exception in the main network communcation thread (fcCorbaServer).. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCServer- 3 -FCCS2000 : Registry error (DetectRegistryChg::Open). Unable to open registry location.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCServer- 3 -FCCS2001 : Unable to connect to the LDAP service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify that the LDAP Monitor Service is running. Check the LDAP Monitor Service logs for errors.

Error Message
FCCServer- 3 -FCCS2002 : Unable to create a new working thread.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCServer- 3 -FCCS2003 : Unexpected exception in a working thread.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCServer- 3 -FCCS2004 : Unexpected exception in the manager thread.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCServer- 3 -FCCS2009 : Unexpected exception.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCServer- 3 -FCCS2010 : Unable to open registry key.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCServer- 3 -FCCS2011 : Unable to read registry value.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended 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 Message
FCCServer- 3 -FCCS2012 : Unable to set the process priority for this service to high. The service will run at normal priority.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCServer- 3 -FCCS2013 : Unable to initialize the network communication library. The service will continue to function, but VPN desktops will not be supported.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCCServer- 3 -FCCS2014 : Unable to determine the local IP address. The service will continue to function, but VPN desktops will not be supported.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended 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 Message
FCCServer- 3 -FCCS2015 : Unexpected network communication error in the VPN-support thread. The service will continue to function, but VPN desktops will not be supported.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended 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 Message
FCCServer- 3 -FCCS2016 : Unexpected exception in the VPN-support thread. The service will continue to function, but VPN desktops will not be supported.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended 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 Message
FCCServer- 4 -FCCS3000 : Unable to close thread handle.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action The service should continue to function normally. Check system resource availability (CPU and memory). Monitor handle usage by this service.

Error Message
FCCServer- 4 -FCCS3008 : Network communication error sending message to application. The application will be logged out.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check network connectivity between the chat service and the indicated application (typically an agent or supervisor) in both directions. 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 Message
FCCServer- 6 -FCCS0000 : Waiting for the installation to complete (checking if IOR Hostname has been set.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCCServer- 6 -FCCS0001 : The installation has completed (IOR Hostname has been set).. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCCServer- 6 -FCCS0004 : Program started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCCServer- 6 -FCCS0005 : Program stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCCServer- 6 -FCCS0013 : Unable to open optional registry key. Using default values.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCCServer- 6 -FCCS0014 : Unable to read optional registry value. Using default value.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCCServer- 6 -FCCS0025 : Attempting to register this service in LDAP.... Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCCServer- 6 -FCCS0026 : Service registered in LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCCServer- 6 -FCCS0027 : Service going into active mode. Incoming requests will be accepted.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCCServer- 6 -FCCS0028 : Service going into inactive mode. Incoming requests will be rejected.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCCServer- 6 -FCCS0029 : CORBA server started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasServer- 1 -FCRasServer1001 : Unable to create thread.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 1 -FCRasServer1012 : Unexpected exception during network communication initialization. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 1 -FCRasServer1013 : Unable to create thread.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2000 : Registry error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2002 : The ADS query queue is full. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2009 : Unexpected exception. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2010 : Unable to open registry key. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2012 : Unable to set the process priority for this service to high. The service will run at normal priority.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2015 : Unable to write registry value. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2016 : The name of the ADS SQL named instance was not found in LDAP. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2017 : An error occurred trying to populate the cache from the ADS database. Will retry.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2018 : An error occurred while attempting to register this service in LDAP. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2019 : SQL Query failed.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2020 : The Admin Workstation Database connection has not been configured. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2100 : Unable to establish a connection to the FCRasSvr database. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2102 : Unable to delete data. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2103 : The Admin Workstation Database connection has not been configured. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2104 : Unable to update data.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2105 : Caught an exception retrieving the last replication time from the database.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2106 : Caught an exception retrieving a list of agent IDs from the database. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2107 : HDS Server has gone offline; retrying connection.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2108 : HDS Server has gone offline; retrying connection.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2109 : Failure when executing query. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 3 -FCRasServer2110 : EEM Database Connectivity. Remainder of message gives more detail.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0000 : Waiting for the installation to complete. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0001 : The installation has completed.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0002 : Populating the statistics cache from table data.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0003 : Cache population complete.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0004 : Program started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0005 : Program stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0006 : SQL queries in the ADS queue waiting to be run.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0007 : SQL queries in the ADS queue waiting to be run.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0009 : SQL queries in the ADS queue waiting to be run.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0010 : Notified to change ADS servers, aborting current connection sequence.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0011 : Signalled to disconnect from the DataSource.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0012 : Signalled to connect to the DataSource.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0015 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0016 : Daily cleanup complete.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0017 : APC statments in queue waiting to be run. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0018 : Connected to the Admin Workstation Database. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0026 : Service registered in LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0027 : Service going into active mode.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0028 : Service going into inactive mode.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0029 : CORBA server started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0030 : Unable to retrieve the list of skill groups from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0031 : Unable to close thread handle. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0032 : Found unterminated email agent state record. Terminating it now.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0033 : Starting XXX thread. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasServer- 6 -FCRasServer0034 : Stopping XXX thread. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None

Error Message
FCRasServer- 6 -FCRasServer0035 : Starting DataSource. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasServer- 6 -FCRasServer0036 : Forcing DataSource to Online. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasServer- 6 -FCRasServer0037 : Setting DataSource to Not Authorized; waiting for CVD message before going online.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasServer- 6 -FCRasServer0038 : The DataSource state is being set to %ls.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasServer- 6 -FCRasServer0039 : Performing (forced, scheduled) (hourly,daily) tasks.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasServer- 6 -FCRasServer0040 : DataStoreConnectionRecoveryThread. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasServer- 6 -FCRasServer0041 : DataStoreUpdateQueue. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasServer- 6 -FCRasServer0042 : DataStoreUpdateQueue. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasServer- 6 -FCRasServer0043 : DataStore statistics:. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasServer- 6 -FCRasServer0044 : LDAP message.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasServer- 6 -FCRasServer0225 : Rascal Replication.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 6 -FCRasServer0226 : Rascal Database size is approaching the maximum size limit. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action 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 serve agent jobs manually.

Error Message
FCRasServer- 6 -FCRasServer0227 : Rascal Database records are not being purged. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCRasServer- 4 -FCRasServer3000 : Unable to close thread handle. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 4 -FCRasServer3001 : Launched thread status. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasServer- 4 -FCRasServer3002 : Database warning.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action See the error message for description on what ocurred and what to do.

Error Message
FCRasSvr- 1 -FCRasServer1001 : Unable to create thread.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 1 -FCRasServer1012 : Unexpected exception during network communication initialization. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 1 -FCRasServer1013 : Unable to create thread.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2000 : Registry error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2002 : The ADS query queue is full. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2009 : Unexpected exception. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2010 : Unable to open registry key. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2012 : Unable to set the process priority for this service to high. The service will run at normal priority.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2015 : Unable to write registry value. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2016 : The name of the ADS SQL named instance was not found in LDAP. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2017 : An error occurred trying to populate the cache from the ADS database. Will retry.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2018 : An error occurred while attempting to register this service in LDAP. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2019 : SQL Query failed.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2020 : The Admin Workstation Database connection has not been configured. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2100 : Unable to establish a connection to the FCRasSvr database. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2102 : Unable to delete data. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2103 : The Admin Workstation Database connection has not been configured. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2104 : Unable to update data.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2105 : Caught an exception retrieving the last replication time from the database.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2106 : Caught an exception retrieving a list of agent IDs from the database. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2107 : HDS Server has gone offline; retrying connection.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2108 : HDS Server has gone offline; retrying connection.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2109 : Failure when executing query. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 3 -FCRasServer2110 : EEM Database Connectivity. Remainder of message gives more detail.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0000 : Waiting for the installation to complete. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0001 : The installation has completed.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0002 : Populating the statistics cache from table data.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0003 : Cache population complete.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0004 : Program started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0005 : Program stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0006 : SQL queries in the ADS queue waiting to be run.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0007 : SQL queries in the ADS queue waiting to be run.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0009 : SQL queries in the ADS queue waiting to be run.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0010 : Notified to change ADS servers, aborting current connection sequence.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0011 : Signalled to disconnect from the DataSource.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0012 : Signalled to connect to the DataSource.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0015 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0016 : Daily cleanup complete.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0017 : APC statments in queue waiting to be run. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0018 : Connected to the Admin Workstation Database. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0026 : Service registered in LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0027 : Service going into active mode.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0028 : Service going into inactive mode.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0029 : CORBA server started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0030 : Unable to retrieve the list of skill groups from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0031 : Unable to close thread handle. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0032 : Found unterminated email agent state record. Terminating it now.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0033 : Starting XXX thread. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasSvr- 6 -FCRasServer0034 : Stopping XXX thread. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None

Error Message
FCRasSvr- 6 -FCRasServer0035 : Starting DataSource. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasSvr- 6 -FCRasServer0036 : Forcing DataSource to Online. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasSvr- 6 -FCRasServer0037 : Setting DataSource to Not Authorized; waiting for CVD message before going online.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasSvr- 6 -FCRasServer0038 : The DataSource state is being set to %ls.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasSvr- 6 -FCRasServer0039 : Performing (forced, scheduled) (hourly,daily) tasks.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasSvr- 6 -FCRasServer0040 : DataStoreConnectionRecoveryThread. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasSvr- 6 -FCRasServer0041 : DataStoreUpdateQueue. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasSvr- 6 -FCRasServer0042 : DataStoreUpdateQueue. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasSvr- 6 -FCRasServer0043 : DataStore statistics:. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasSvr- 6 -FCRasServer0044 : LDAP message.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
FCRasSvr- 6 -FCRasServer0225 : Rascal Replication.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 6 -FCRasServer0226 : Rascal Database size is approaching the maximum size limit. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action 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 serve agent jobs manually.

Error Message
FCRasSvr- 6 -FCRasServer0227 : Rascal Database records are not being purged. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
FCRasSvr- 4 -FCRasServer3000 : Unable to close thread handle. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 4 -FCRasServer3001 : Launched thread status. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
FCRasSvr- 4 -FCRasServer3002 : Database warning.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action See the error message for description on what ocurred and what to do.

Error Message
FCVoIPMonClientRec- 3 -VOIP2000 : Mutex for CFCDMCritSection object. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2001 : Shutdown event.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2002 : LDAP Up/Down event. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2003 : Desktop Monitor adapter name in the Registry not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that installation has been completed and all required values are in the registry.

Error Message
FCVoIPMonClientRec- 3 -VOIP2005 : IOR Hostname entry in the Registry not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that installation has been completed and all required values are in the registry.

Error Message
FCVoIPMonClientRec- 3 -VOIP2007 : initialization event not created. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2008 : Desktop Monitoring initialization thread not created. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2009 : CDesktopMonitor object not created. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2010 : CFCDMMonitorServerList object not created. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2011 : Corba listening thread not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2012 : CFCDMCritSection object not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2013 : CFCDMSniffer object not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2014 : Periodic Cleanup thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2015 : LDAP Connection Monitoring thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2016 : Logout event creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2017 : Login thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2019 : Login thread ended. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the log and debug files for related errors and restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2021 : Desktop monitoring enabled for extension. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Subsystem will recover automatically, no action needed unless further errors occur.

Error Message
FCVoIPMonClientRec- 3 -VOIP2023 : LDAP thread ended. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the log and debug files for related errors and restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2033 : Sniffing event object creation error. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2034 : Sniffer session shutdown event object creation error. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2035 : SnifferSession thread creation error. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2036 : Sniffer Session thread termination. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2037 : error opening NIC adapter. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2038 : network information not availabale. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2039 : Error while setting the sniffing filter. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2041 : Error receiving packets. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2042 : NIC adapter opened. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action required

Error Message
FCVoIPMonClientRec- 3 -VOIP2043 : packet sniffing started. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action required

Error Message
FCVoIPMonClientRec- 3 -VOIP2044 : packet sniffing stopped. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action required

Error Message
FCVoIPMonClientRec- 3 -VOIP2046 : socket creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart the VoIP Monitor service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2048 : MAC Address not found. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Perform the following actions: 1. Check the CallManager database for changes. 2. Verify the FCVoIP ODBC DSN is correct. 3. Verify that the CallManager database is running. 4. Verify that a record for the extension exists in the CallManager database. 5. Reinstall the monitor service if it requires a new username or password.

Error Message
FCVoIPMonClientRec- 3 -VOIP2049 : Registry entries not found.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that installation has been completed and all required values are in the registry.

Error Message
FCVoIPMonClientRec- 3 -VOIP2050 : NIC monitoring adapter name not found. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action The VoIP Service is missing information required for start up.

Error Message
FCVoIPMonClientRec- 3 -VOIP2051 : process creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2052 : LRM thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2053 : VPN thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2054 : Corba thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2055 : NIC adapter opening failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2056 : NIC adapter not configured correctly . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2057 : error while setting the filter. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2061 : LDAP Monitor thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2062 : Fail to create Client interface. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action If problems continue, restart the service.

Error Message
FCVoIPMonClientRec- 3 -VOIP2063 : Fail to connect or reconnect to the current CM. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the status of the CallManager processes. There must be at least one CallManager with an active AXL database service in the cluster.

Error Message
FCVoIPMonClientRec- 3 -VOIP2064 : ODBC's failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify that the CallManager database is running.

Error Message
FCVoIPMonClientRec- 3 -VOIP2065 : OmniOrbUseHostName invalid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Contact TAC for assistance.

Error Message
FCVoIPMonClientRec- 3 -VOIP2066 : CallManager database connection initialization failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify that the CallManager database is running and that VoIP is configured correctly.

Error Message
FCVoIPMonClientRec- 3 -VOIP2067 : Unable to monitor agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Monitor service is running and active.

Error Message
FCVoIPMonClientRec- 3 -VOIP2068 : Unable to monitor agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Retry when the VoIP Monitor service recovery completes.

Error Message
FCVoIPMonClientRec- 3 -VOIP2069 : Unable to monitor agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2070 : Unable to monitor agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2071 : Unable to refresh the monitoring session with the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2072 : Unable to refresh the monitoring session with the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2073 : Unable to refresh the monitoring session with the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2074 : Unable to stop the monitoring session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2075 : Unable to stop the monitoring session for supervisor. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2076 : Unable to stop the monitoring session for supervisor. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2077 : Caught a Corba exception while testing the connection to the VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2079 : Unable to record Agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2080 : Unable to record Agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart

Error Message
FCVoIPMonClientRec- 3 -VOIP2081 : Corba exception Unable to record the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart

Error Message
FCVoIPMonClientRec- 3 -VOIP2082 : Unknown Corba exception.Unable to record the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart

Error Message
FCVoIPMonClientRec- 3 -VOIP2083 : Unable to record agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2084 : Unable to record agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running

Error Message
FCVoIPMonClientRec- 3 -VOIP2085 : Unable to record the agent with rtpAddress. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2086 : Unable to record the agent with rtpAddress. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2087 : Unable to record the agent with rtpAddress. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2088 : Unable to stop the recording session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2089 : Corba exception. Unable to stop the recording session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2090 : Unknown Corba exception. Unable to stop the recording session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2091 : Unable to get connection information for the VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2092 : Unable to get connection information for the VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2093 : Unable to initialize the Corba connection for VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2095 : Unable to get the VPN IP address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2096 : Error getting the MAC address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and configured correctly and restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2097 : Unknown Corba exception while looking for MAC address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2098 : Unable to get the MAC address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the VoIP Service logs

Error Message
FCVoIPMonClientRec- 3 -VOIP2099 : Error while looking for MAC address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the VoIP Service logs.

Error Message
FCVoIPMonClientRec- 3 -VOIP2100 : Invalid connection information for the VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2101 : Unable to initialize the Corba connection. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2102 : Unable to initialize Corba connection for desktop monitoring. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the Client is running and restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2103 : Unable to initialize Corba connection for recording extension. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the Client is running and restart.

Error Message
FCVoIPMonClientRec- 3 -VOIP2104 : Failed to start thread.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart.

Error Message
FCVoIPMonClientRec- 4 -VOIP3001 : Failed to create socket for VPN service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.

Error Message
FCVoIPMonClientRec- 4 -VOIP3002 : Unable to stop the monitoring session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.

Error Message
FCVoIPMonClientRec- 4 -VOIP3003 : Could not create the LDAP recovery thread. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.

Error Message
FCVoIPMonClientRec- 4 -VOIP3004 : Unsupported Codec format.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Use one of the supported codec formats. G279,aLaw or uLaw

Error Message
FCVoIPMonClientRec- 6 -VOIP4000 : Desktop Monitor name. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4001 : Desktop Monitoring module initialized. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4002 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4003 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4004 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4005 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4006 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4007 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4008 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4009 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4010 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4011 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4012 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4013 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4014 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4015 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4016 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4017 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4018 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4019 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClientRec- 6 -VOIP4020 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 3 -VOIP2000 : Mutex for CFCDMCritSection object. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2001 : Shutdown event.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2002 : LDAP Up/Down event. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2003 : Desktop Monitor adapter name in the Registry not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that installation has been completed and all required values are in the registry.

Error Message
FCVoIPMonClient- 3 -VOIP2005 : IOR Hostname entry in the Registry not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that installation has been completed and all required values are in the registry.

Error Message
FCVoIPMonClient- 3 -VOIP2007 : initialization event not created. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2008 : Desktop Monitoring initialization thread not created. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2009 : CDesktopMonitor object not created. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2010 : CFCDMMonitorServerList object not created. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2011 : Corba listening thread not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2012 : CFCDMCritSection object not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2013 : CFCDMSniffer object not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2014 : Periodic Cleanup thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2015 : LDAP Connection Monitoring thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2016 : Logout event creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2017 : Login thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2019 : Login thread ended. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the log and debug files for related errors and restart.

Error Message
FCVoIPMonClient- 3 -VOIP2021 : Desktop monitoring enabled for extension. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Subsystem will recover automatically, no action needed unless further errors occur.

Error Message
FCVoIPMonClient- 3 -VOIP2023 : LDAP thread ended. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the log and debug files for related errors and restart.

Error Message
FCVoIPMonClient- 3 -VOIP2033 : Sniffing event object creation error. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2034 : Sniffer session shutdown event object creation error. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2035 : SnifferSession thread creation error. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2036 : Sniffer Session thread termination. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2037 : error opening NIC adapter. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonClient- 3 -VOIP2038 : network information not availabale. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonClient- 3 -VOIP2039 : Error while setting the sniffing filter. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonClient- 3 -VOIP2041 : Error receiving packets. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonClient- 3 -VOIP2042 : NIC adapter opened. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action required

Error Message
FCVoIPMonClient- 3 -VOIP2043 : packet sniffing started. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action required

Error Message
FCVoIPMonClient- 3 -VOIP2044 : packet sniffing stopped. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action required

Error Message
FCVoIPMonClient- 3 -VOIP2046 : socket creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart the VoIP Monitor service.

Error Message
FCVoIPMonClient- 3 -VOIP2048 : MAC Address not found. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Perform the following actions: 1. Check the CallManager database for changes. 2. Verify the FCVoIP ODBC DSN is correct. 3. Verify that the CallManager database is running. 4. Verify that a record for the extension exists in the CallManager database. 5. Reinstall the monitor service if it requires a new username or password.

Error Message
FCVoIPMonClient- 3 -VOIP2049 : Registry entries not found.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that installation has been completed and all required values are in the registry.

Error Message
FCVoIPMonClient- 3 -VOIP2050 : NIC monitoring adapter name not found. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action The VoIP Service is missing information required for start up.

Error Message
FCVoIPMonClient- 3 -VOIP2051 : process creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2052 : LRM thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2053 : VPN thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2054 : Corba thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2055 : NIC adapter opening failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonClient- 3 -VOIP2056 : NIC adapter not configured correctly . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonClient- 3 -VOIP2057 : error while setting the filter. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonClient- 3 -VOIP2061 : LDAP Monitor thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2062 : Fail to create Client interface. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action If problems continue, restart the service.

Error Message
FCVoIPMonClient- 3 -VOIP2063 : Fail to connect or reconnect to the current CM. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the status of the CallManager processes. There must be at least one CallManager with an active AXL database service in the cluster.

Error Message
FCVoIPMonClient- 3 -VOIP2064 : ODBC's failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify that the CallManager database is running.

Error Message
FCVoIPMonClient- 3 -VOIP2065 : OmniOrbUseHostName invalid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Contact TAC for assistance.

Error Message
FCVoIPMonClient- 3 -VOIP2066 : CallManager database connection initialization failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify that the CallManager database is running and that VoIP is configured correctly.

Error Message
FCVoIPMonClient- 3 -VOIP2067 : Unable to monitor agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Monitor service is running and active.

Error Message
FCVoIPMonClient- 3 -VOIP2068 : Unable to monitor agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Retry when the VoIP Monitor service recovery completes.

Error Message
FCVoIPMonClient- 3 -VOIP2069 : Unable to monitor agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClient- 3 -VOIP2070 : Unable to monitor agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClient- 3 -VOIP2071 : Unable to refresh the monitoring session with the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClient- 3 -VOIP2072 : Unable to refresh the monitoring session with the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClient- 3 -VOIP2073 : Unable to refresh the monitoring session with the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClient- 3 -VOIP2074 : Unable to stop the monitoring session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClient- 3 -VOIP2075 : Unable to stop the monitoring session for supervisor. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClient- 3 -VOIP2076 : Unable to stop the monitoring session for supervisor. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClient- 3 -VOIP2077 : Caught a Corba exception while testing the connection to the VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClient- 3 -VOIP2079 : Unable to record Agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonClient- 3 -VOIP2080 : Unable to record Agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart

Error Message
FCVoIPMonClient- 3 -VOIP2081 : Corba exception Unable to record the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart

Error Message
FCVoIPMonClient- 3 -VOIP2082 : Unknown Corba exception.Unable to record the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart

Error Message
FCVoIPMonClient- 3 -VOIP2083 : Unable to record agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClient- 3 -VOIP2084 : Unable to record agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running

Error Message
FCVoIPMonClient- 3 -VOIP2085 : Unable to record the agent with rtpAddress. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClient- 3 -VOIP2086 : Unable to record the agent with rtpAddress. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClient- 3 -VOIP2087 : Unable to record the agent with rtpAddress. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClient- 3 -VOIP2088 : Unable to stop the recording session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClient- 3 -VOIP2089 : Corba exception. Unable to stop the recording session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClient- 3 -VOIP2090 : Unknown Corba exception. Unable to stop the recording session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClient- 3 -VOIP2091 : Unable to get connection information for the VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClient- 3 -VOIP2092 : Unable to get connection information for the VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClient- 3 -VOIP2093 : Unable to initialize the Corba connection for VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClient- 3 -VOIP2095 : Unable to get the VPN IP address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClient- 3 -VOIP2096 : Error getting the MAC address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and configured correctly and restart.

Error Message
FCVoIPMonClient- 3 -VOIP2097 : Unknown Corba exception while looking for MAC address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClient- 3 -VOIP2098 : Unable to get the MAC address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the VoIP Service logs

Error Message
FCVoIPMonClient- 3 -VOIP2099 : Error while looking for MAC address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the VoIP Service logs.

Error Message
FCVoIPMonClient- 3 -VOIP2100 : Invalid connection information for the VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClient- 3 -VOIP2101 : Unable to initialize the Corba connection. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonClient- 3 -VOIP2102 : Unable to initialize Corba connection for desktop monitoring. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the Client is running and restart.

Error Message
FCVoIPMonClient- 3 -VOIP2103 : Unable to initialize Corba connection for recording extension. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the Client is running and restart.

Error Message
FCVoIPMonClient- 3 -VOIP2104 : Failed to start thread.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart.

Error Message
FCVoIPMonClient- 4 -VOIP3001 : Failed to create socket for VPN service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.

Error Message
FCVoIPMonClient- 4 -VOIP3002 : Unable to stop the monitoring session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.

Error Message
FCVoIPMonClient- 4 -VOIP3003 : Could not create the LDAP recovery thread. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.

Error Message
FCVoIPMonClient- 4 -VOIP3004 : Unsupported Codec format.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Use one of the supported codec formats. G279,aLaw or uLaw

Error Message
FCVoIPMonClient- 6 -VOIP4000 : Desktop Monitor name. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4001 : Desktop Monitoring module initialized. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4002 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4003 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4004 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4005 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4006 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4007 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4008 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4009 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4010 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4011 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4012 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4013 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4014 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4015 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4016 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4017 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4018 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4019 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonClient- 6 -VOIP4020 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 3 -VOIP2000 : Mutex for CFCDMCritSection object. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2001 : Shutdown event.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2002 : LDAP Up/Down event. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2003 : Desktop Monitor adapter name in the Registry not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that installation has been completed and all required values are in the registry.

Error Message
FCVoIPMonSvr- 3 -VOIP2005 : IOR Hostname entry in the Registry not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that installation has been completed and all required values are in the registry.

Error Message
FCVoIPMonSvr- 3 -VOIP2007 : initialization event not created. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2008 : Desktop Monitoring initialization thread not created. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2009 : CDesktopMonitor object not created. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2010 : CFCDMMonitorServerList object not created. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2011 : Corba listening thread not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2012 : CFCDMCritSection object not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2013 : CFCDMSniffer object not available. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2014 : Periodic Cleanup thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2015 : LDAP Connection Monitoring thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2016 : Logout event creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2017 : Login thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2019 : Login thread ended. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the log and debug files for related errors and restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2021 : Desktop monitoring enabled for extension. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Subsystem will recover automatically, no action needed unless further errors occur.

Error Message
FCVoIPMonSvr- 3 -VOIP2023 : LDAP thread ended. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the log and debug files for related errors and restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2033 : Sniffing event object creation error. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2034 : Sniffer session shutdown event object creation error. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2035 : SnifferSession thread creation error. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2036 : Sniffer Session thread termination. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2037 : error opening NIC adapter. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonSvr- 3 -VOIP2038 : network information not availabale. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonSvr- 3 -VOIP2039 : Error while setting the sniffing filter. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonSvr- 3 -VOIP2041 : Error receiving packets. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonSvr- 3 -VOIP2042 : NIC adapter opened. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action required

Error Message
FCVoIPMonSvr- 3 -VOIP2043 : packet sniffing started. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action required

Error Message
FCVoIPMonSvr- 3 -VOIP2044 : packet sniffing stopped. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action required

Error Message
FCVoIPMonSvr- 3 -VOIP2046 : socket creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart the VoIP Monitor service.

Error Message
FCVoIPMonSvr- 3 -VOIP2048 : MAC Address not found. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Perform the following actions: 1. Check the CallManager database for changes. 2. Verify the FCVoIP ODBC DSN is correct. 3. Verify that the CallManager database is running. 4. Verify that a record for the extension exists in the CallManager database. 5. Reinstall the monitor service if it requires a new username or password.

Error Message
FCVoIPMonSvr- 3 -VOIP2049 : Registry entries not found.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that installation has been completed and all required values are in the registry.

Error Message
FCVoIPMonSvr- 3 -VOIP2050 : NIC monitoring adapter name not found. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action The VoIP Service is missing information required for start up.

Error Message
FCVoIPMonSvr- 3 -VOIP2051 : process creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2052 : LRM thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2053 : VPN thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2054 : Corba thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2055 : NIC adapter opening failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonSvr- 3 -VOIP2056 : NIC adapter not configured correctly . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonSvr- 3 -VOIP2057 : error while setting the filter. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the configuration and restart the VoIPMonitor service.

Error Message
FCVoIPMonSvr- 3 -VOIP2061 : LDAP Monitor thread creation failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2062 : Fail to create Client interface. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action If problems continue, restart the service.

Error Message
FCVoIPMonSvr- 3 -VOIP2063 : Fail to connect or reconnect to the current CM. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the status of the CallManager processes. There must be at least one CallManager with an active AXL database service in the cluster.

Error Message
FCVoIPMonSvr- 3 -VOIP2064 : ODBC's failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify that the CallManager database is running.

Error Message
FCVoIPMonSvr- 3 -VOIP2065 : OmniOrbUseHostName invalid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Contact TAC for assistance.

Error Message
FCVoIPMonSvr- 3 -VOIP2066 : CallManager database connection initialization failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify that the CallManager database is running and that VoIP is configured correctly.

Error Message
FCVoIPMonSvr- 3 -VOIP2067 : Unable to monitor agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Monitor service is running and active.

Error Message
FCVoIPMonSvr- 3 -VOIP2068 : Unable to monitor agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Retry when the VoIP Monitor service recovery completes.

Error Message
FCVoIPMonSvr- 3 -VOIP2069 : Unable to monitor agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2070 : Unable to monitor agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2071 : Unable to refresh the monitoring session with the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2072 : Unable to refresh the monitoring session with the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2073 : Unable to refresh the monitoring session with the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2074 : Unable to stop the monitoring session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2075 : Unable to stop the monitoring session for supervisor. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2076 : Unable to stop the monitoring session for supervisor. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2077 : Caught a Corba exception while testing the connection to the VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2079 : Unable to record Agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2080 : Unable to record Agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart

Error Message
FCVoIPMonSvr- 3 -VOIP2081 : Corba exception Unable to record the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart

Error Message
FCVoIPMonSvr- 3 -VOIP2082 : Unknown Corba exception.Unable to record the agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart

Error Message
FCVoIPMonSvr- 3 -VOIP2083 : Unable to record agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2084 : Unable to record agent. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running

Error Message
FCVoIPMonSvr- 3 -VOIP2085 : Unable to record the agent with rtpAddress. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2086 : Unable to record the agent with rtpAddress. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2087 : Unable to record the agent with rtpAddress. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2088 : Unable to stop the recording session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2089 : Corba exception. Unable to stop the recording session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2090 : Unknown Corba exception. Unable to stop the recording session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2091 : Unable to get connection information for the VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2092 : Unable to get connection information for the VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2093 : Unable to initialize the Corba connection for VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2095 : Unable to get the VPN IP address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2096 : Error getting the MAC address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and configured correctly and restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2097 : Unknown Corba exception while looking for MAC address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2098 : Unable to get the MAC address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the VoIP Service logs

Error Message
FCVoIPMonSvr- 3 -VOIP2099 : Error while looking for MAC address. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the VoIP Service logs.

Error Message
FCVoIPMonSvr- 3 -VOIP2100 : Invalid connection information for the VoIP service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2101 : Unable to initialize the Corba connection. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the VoIP Service is running and restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2102 : Unable to initialize Corba connection for desktop monitoring. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the Client is running and restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2103 : Unable to initialize Corba connection for recording extension. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the Client is running and restart.

Error Message
FCVoIPMonSvr- 3 -VOIP2104 : Failed to start thread.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the system resources and restart.

Error Message
FCVoIPMonSvr- 4 -VOIP3001 : Failed to create socket for VPN service. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.

Error Message
FCVoIPMonSvr- 4 -VOIP3002 : Unable to stop the monitoring session. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.

Error Message
FCVoIPMonSvr- 4 -VOIP3003 : Could not create the LDAP recovery thread. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included error description.

Error Message
FCVoIPMonSvr- 4 -VOIP3004 : Unsupported Codec format.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Use one of the supported codec formats. G279,aLaw or uLaw

Error Message
FCVoIPMonSvr- 6 -VOIP4000 : Desktop Monitor name. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4001 : Desktop Monitoring module initialized. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4002 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4003 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4004 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4005 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4006 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4007 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4008 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4009 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4010 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4011 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4012 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4013 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4014 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4015 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4016 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4017 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4018 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4019 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FCVoIPMonSvr- 6 -VOIP4020 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the included message

Error Message
FIPSModeChangeAlarmCatalog- 5 -FipsModeEnable : FIPS mode has been successfully enabled in the Cisco Unified Communications Manager. Certifcates for CUCM, CAPF, Tomcat, Ipsec , TVS and SSH services have been regenerated. . Message [String]

Explanation This alarm is generated when the Cisco Unified Communications Manager OS administrator enables FIPS mode. Once FIPS mode has been enabled the system will reboot. After the reboot the system runs in compliance with the FIPS 140-2 Level 1 Standards.

Recommended Action The authorized administration should check all the FIPS logs to ensure that all FIPS related operations including the power up self tests completed successfully.

Error Message
FIPSModeChangeAlarmCatalog- 5 -FipsModeDisable : FIPS mode has been successfully disabled in the Cisco Unified Communications Manager. Certifcates for CUCM, CAPF, Tomcat, Ipsec , TVS and SSH services have been regenerated. . Message [String]

Explanation This alarm is generated when the Cisco Unified Communications Manager OS administrator disables FIPS mode. Once FIPS mode has been disabledthe system will reboot.

Recommended Action The authorized administrator should check the FIPS logs to ensure there are no errors.

Error Message
GenericAlarmCatalog- 0 -OutOfMemory : Out of memory..

Explanation The process has requested memory from the operating system, and there was not enough memory available.

Recommended Action No action is required.

Error Message
GenericAlarmCatalog- 6 -PermissionDenied : Permission has been denied..

Explanation An operation could not be completed because the process did not have authority to perform it.

Recommended Action This alarm is for information purposes only; no action is required.

Error Message
GenericAlarmCatalog- 0 -ServiceNotInstalled : Service is not installed.. Service Name [String]

Explanation An executable is trying to start but cannot because it is not configured as a service in the service control manager. The service name is %s.

Recommended Action Reinstall the service.

Error Message
GenericAlarmCatalog- 6 -ServiceStopped : Service stopped.. IP Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Process ID [ULong]

Explanation A service has stopped.

Recommended Action This alarm is for information purposes only; no action is required.

Error Message
GenericAlarmCatalog- 6 -ServiceStarted : Service started.. Process ID [ULong] IP Address of hosting node. [String] IPV6 Address of hosting node. [String] Host name of hosting node. [String] Service Name [String] Version Information. [String]

Explanation A service has started.

Recommended Action This alarm is for information purposes only; no action is required.

Error Message
GenericAlarmCatalog- 4 -ServiceStartupFailed : Service startup failure.. Service Name [String]

Explanation An attempt to start the specified service failed.

Recommended Action Restart the service.

Error Message
GenericAlarmCatalog- 0 -FileWriteError : Cannot write into a file.. Primary File Path [String]

Explanation Failed to write into the primary file path.

Recommended Action Ensure that the primary file path is valid and the corresponding drive has sufficient disk space. Also, make sure that the path has security permissions similar to default log file path.

Error Message
ILSAlarmCatalog- 3 -ILSDBLException : An error occurred while the ILS was performing database activities. DBL Exception [String]

Explanation A severe database layer interface error occurred. Some possible causes for this include the database being unreachable or down or a DNS error.

Recommended Action Review the System Reports provided in the Cisco Unified Reporting tool, specifically the Unified CM Database Status report, for any anomalous activity. You can also go to Real-Time Reporting Tool (RTMT) and check the Replication Status in the Database Summary page. If status shows 2, then replication is working. Check network connectivity to the server that is running the database. If your system uses DNS, check the DNS configuration for any errors. If the cause is still not identified, collect SDL and SDI traces and contact the Cisco Technical Assistance Center (TAC).

Error Message
ILSAlarmCatalog- 3 -ILSTLSAuthenticationFailed : TLS authentication failure to cluster in this ILS network. Cluster Name [String]

Explanation A TLS connection to a cluster in the ILS network could not be established, mostly likely because of a problem with the certificate presented by the publisher Unified CM in the remote cluster. (For example, not in the Unified CM CTL, or is in the CTL but has expired).

Recommended Action Verify that the certificate of the remote cluster Unified CM is installed and configured properly on the local Unified CM.

Error Message
ILSAlarmCatalog- 3 -ILSPwdAuthenticationFailed : Password authentication failure to cluster in this ILS network. IP address [String]

Explanation A password authentication failure has occurred on a connection to a remote cluster.

Recommended Action Verify that ILS at the remote server is configured to use password authentication. Reenter the ILS password if needed. The ILS password must be identical at all clusters that will participate in the same ILS network.

Error Message
ILSAlarmCatalog- 3 -ILSDuplicateClusterID : Duplicate Enterprise Cluster ID found in ILS network. Enterprise Cluster ID [String]

Explanation A duplicate Enterprise Cluster ID has been found in this ILS network.

Recommended Action Check that the Enterprise Cluster ID is not set to the default value. Assign each cluster in the ILS network a unique Enterprise Cluster ID.

Error Message
ILSAlarmCatalog- 4 -ILSDuplicateURIOnLookup : Duplicate URI found in ILS network during URI lookup. URI [String] Routing string returned [String] Duplicate routing strings [String]

Explanation A duplicate URI has been found in this ILS network.

Recommended Action Check that the same URI does not exist on multiple clusters in the ILS network.

Error Message
ILSAlarmCatalog- 4 -ILSDuplicateURIOnReplication : Duplicate URI found in ILS network during URI replication. URI [String] Duplicate routing string [String]

Explanation A duplicate URI has been found in this ILS network.

Recommended Action Check that the same URI does not exist on multiple clusters in the ILS network.

Error Message
ILSAlarmCatalog- 3 -ILSHubClusterUnreachable : Hub cluster unreachable.. Hub Cluster [String] Host List [String]

Explanation This alarm indicates that the ILS was unable to reach the remote hub cluster. ILS will periodically re-attempt to connect to the hub cluster. If the condition is due to a temporary Internet connectivity issue, the problem will self-repair. However, if it is due to a persistent condition, action must be taken.

Recommended Action Review the ILS Configuration at the remote cluster. Ensure ILS is activated and running on at least one server found in the HostList parameter of this alarm. Verify that your firewall is allowing access to the remote hosts. Try pinging the listed hosts and diagnose any network issues from there. If no valid hosts are listed then ILS may need to be reconfigured locally with a new registration server.

Error Message
ILSAlarmCatalog- 2 -ILSTCPInUse : ILS failed while initializing a TCP port because the port is already in use.. TCP Port [UInt]

Explanation This alarm indicates that ILS was unable to bind to a TCP port because the port is already in use. It will occur during service startup if the ports that ILS tries to initialize are already in use. ILS will terminate when this error occurs.

Recommended Action Make sure that no other services have been configured to use the same ports that ILS has been configured to use. Correct the problem and restart ILS.

Error Message
ILSAlarmCatalog- 2 -ILSTCPListenError : ILS failed while initializing a TCP port.. TCP Port [UInt]

Explanation This alarm indicates that ILS was unable to initialize a TCP port. It will occur during service startup when it tries to initialize TCP ports. ILS will terminate when this error occurs.

Recommended Action Consult the diagnostics for details.

Error Message
ILSAlarmCatalog- 4 -ILSRemoteHostUnresponsive : No response from host at remote cluster.. Remote Cluster [String] Connection Details [String]

Explanation ILS was able to establish a connection but the remote host was unresponsive. The connection has been dropped and ILS will periodically re-attempt to connect to remote cluster. If the condition is due to a temporary Internet connectivity issue, the problem will self-repair. However, if it is due to a persistent condition, action must be taken.

Recommended Action Verify the ILS configuration at the remote cluster. Check the remote cluster's syslog for additional details. Diagnose any network issues between the two IP addresses provided in the connection details of this alarm.

Error Message
ILSAlarmCatalog- 3 -ILSUnacceptableConnectionAttempt : A connection from a remote ILS server has been rejected.. Reason [String] Connection Details [String]

Explanation ILS received a connection attempt that was not acceptable. The connection has been dropped. Typically this alarm indicates a misconfiguration or incompatibility of ILS between the local and remote clusters.

Recommended Action Use the reason message provided to further diagnose the issue. The connection details will include the IP address of the remote ILS.

Error Message
ILSAlarmCatalog- 3 -ILSProtocolVersion : Incompatible ILS protocol used by remote cluster.. remote cluster [String] connection details [String]

Explanation ILS protocol used by remote system is not compatible with the local cluster. The connection has been dropped.

Recommended Action Upgrade the lower version component so that both clusters use the same or compatible version.

Error Message
IMSAlarmCatalog- 4 -authFail : An attempt to authenticate this user with the given credentials failed.. Authentication failure [String] Invalid Ticket [String]

Explanation Failed to authenticate this user.

Recommended Action Determine correct credentials and retry.

Error Message
IMSAlarmCatalog- 4 -SSONullTicket : A null ticket was passed.. Invalid UserID [String]

Explanation Failed to authenticate this user.

Recommended Action Get non null ticket and retry.

Error Message
IMSAlarmCatalog- 4 -SSOServerUnreachable : SSO server could not be reached.. SSO server could not be reached. [String]

Explanation SSO server could not be reached.

Recommended Action Check reachability to SSO server.

Error Message
IMSAlarmCatalog- 4 -LDAPServerUnreachable : Authentication server could not be reached.. Authentication server could not be reached. [String]

Explanation Authentication server could not be reached.

Recommended Action Check reachability to Authentication server.

Error Message
IMSAlarmCatalog- 4 -SSOuserNotInDB : User was not found in DB.. User was not found in DB. [String]

Explanation User was not found in DB.

Recommended Action Perform sync manually or wait till next scheduled sync.

Error Message
IMSAlarmCatalog- 4 -SSODisabled : SSO disabled on CUCM.. SSO disabled on CUCM. [String]

Explanation SSO disabled on CUCM.

Recommended Action run CLI command to enable SSO.

Error Message
IMSAlarmCatalog- 4 -SSOInternal : Failedto open a file.. File open failure [String]

Explanation Failed to authenticate this user.

Recommended Action Try again after some time.

Error Message
IMSAlarmCatalog- 6 -authSuccess : User successfully authenticated.. Authentication successful [String]

Explanation Successfully authenticated this user.

Recommended Action No action required.

Error Message
IMSAlarmCatalog- 4 -authLdapInactive : Authentication failed due to the user existing in the local database, but system is configured for LDAP authentication.. Authentication failure due to LDAP inactive [String]

Explanation A directory sync was likely done in the immediate past (1 day), This user has yet to be removed from the database. No action should be necessary. This should clear itself within 24 hours.

Recommended Action No action should be necessary.

Error Message
IMSAlarmCatalog- 4 -authAdminLock : The Administrator has locked this credential, therfore the authentication failed.. Authentication failure due to administrative lock [String]

Explanation User is locked out by administrator.

Recommended Action Administrator may unlock this credential.

Error Message
IMSAlarmCatalog- 4 -authHackLock : This user attempted to login unsuccessfully the number of times set by the administrator. At that time the credential is locked.. Authentication failure due to hack lock. [String]

Explanation User attempted too many incorrect authentications in the time frame set by the administrator.

Recommended Action Wait for administrator specified time to retry, or have administrator unlock the credential.

Error Message
IMSAlarmCatalog- 5 -authExpired : The authentication failed because this credential has expired.. Authentication failure due to expired soft lock. [String]

Explanation This user's credentials have expired.

Recommended Action Administrator may reset the credential.

Error Message
IMSAlarmCatalog- 4 -authInactiveLock : Authentication failed because the credential is locked due to inactivity.. Authentication Failure due to inactive lock. [String]

Explanation User has been inactive for the administrator specified time. The credential is locked.

Recommended Action Administrator may reset the credential.

Error Message
IMSAlarmCatalog- 5 -authMustChange : Authentication failed because it is marked that it must be changed by the user at this time.. Authentication Failure due to User Must Change. [String]

Explanation User Must Change is set on this credential. The user can gain access after changing the credential.

Recommended Action User or Administrator may reset credential.

Error Message
IMSAlarmCatalog- 6 -credUpdateFailure : There are a number of reasons an update of a credential could fail. Likely cause is that the credential doesn't pass security requirements (too short for example), has been used previously, etc.. Credential Update Failure for [String]

Explanation Some problem updating the credential.

Recommended Action Determine issue (check length requirements, etc.) for this credential and retry.

Error Message
IMSAlarmCatalog- 6 -credUpdateSuccess : The credential has been updated.. Credential Update success for [String]

Explanation Credential was successfully updated.

Recommended Action No action required.

Error Message
IMSAlarmCatalog- 6 -credFullUpdateSuccess : Fields associated with this credential have been successfully updated.. Credential fields update success [String]

Explanation Credential was successfully updated.

Recommended Action No action required.

Error Message
IMSAlarmCatalog- 6 -credFullUpdateFailure : The update for the fields associated with this credential failed.. Credential fields update failure [String]

Explanation An error was encountered during update of credential fields.

Recommended Action Determine issue and retry.

Error Message
IMSAlarmCatalog- 5 -credReadFailure : Some error was encountered when attempting to read credential from the database. This could be a network or database issue.. Credential read failure for [String] DB query failure SSO [String]

Explanation Error occured attempting to read a credential.

Recommended Action Ensure credential (user name) exists. Could be database problem.

Error Message
IMSAlarmCatalog- 6 -credReadSuccess : This credential was successfully accessed from the databse.. Credential read success for [String]

Explanation Successfully read a credential.

Recommended Action No action required.

Error Message
IMSAlarmCatalog- 6 -AdminPassword : Administrative password changed successfully, or unsuccessfully based on message displayed.. [String]

Explanation Password change succeeded or failed based on message displayed.

Recommended Action No further recommendation.

Error Message
IPHOST-IP_HOST_CHANGE- 3 -CONFIG_UPDATE_FAILED : Node Config update failed. IP/Host Name will not be chnaged. Exception [String]

Explanation Node Config update failed. IP/Host Name will not be chnaged

Recommended Action No actions needed

Error Message
IPPAClient- 1 -BIPPA1000 : Unable to create CORBA service for the BIPPA service to receive requests from IP Phone Agent clients.. Service Name [String] error Id [String] Message [String]

Explanation The SocketService could not be started.

Recommended Action Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPAClient- 1 -BIPPA1001 : Unable to create TCP socket listener for the BIPPA service to receive requests from CAD-BE clients.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action 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 (59012) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
IPPAClient- 1 -BIPPA1002 : TCP socket dispatcher in BIPPA service for receiving requests from CAD-BE clients failed to run.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action 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 (59012) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
IPPAClient- 1 -BIPPA1003 : TCP socket listener used for receiving requests from CAD-BE clients could not be added to BIPPA socket dispatcher.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action 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 (59012) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
IPPAClient- 3 -BIPPA2000 : An error occurred while performing specified action.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPAClient- 3 -BIPPA2001 : An error occurred while setting up communication with the LRM service.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPAClient- 3 -BIPPA2002 : An error occurred while registering with the LRM service for BIPPA events.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPAClient- 3 -BIPPA2003 : Could not open the BIPPA service information file used by the IPPA JSP client and CAD-BE to communicate with the BIPPA service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the registry to see if the /HKLM/SOFTWARE/Spanlink/CAD/IPPA/Config/TOMCAT HOME registry value is the location of the Tomcat directory. By default, it is set to the folder C:\Program Files\Cisco\Desktop\Tomcat\ for UCCE and C:\Program Files\wfavvid\tomcat_appadmin\ for UCCX. Ensure the directory exists. Check the registry to see if the /HKLM/SOFTWARE/Spanlink/CAD/Site Setup/Install Directory registry value is the location of CAD software. By default, it is C:\Program Files\Cisco\Desktop\. 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 Message
IPPAClient- 3 -BIPPA2004 : The BIPPA service was unable to change its process priority to high because of the specified Windows error.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPAClient- 3 -BIPPA2005 : An error occurred while registering with the LRM service for LRM events.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPAClient- 3 -BIPPA2006 : An error occurred while registering BIPPA service with the LRM service.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPAClient- 3 -BIPPA2007 : The machine running the BIPPA service ran out of available memory.. Service Name [String] error Id [String] Message [String]

Explanation .

Recommended Action Stop unnecessary processes on the machine. Restart the BIPPA service. Run a memory check. See "Memory Check" on page 206. Add more memory to the machine.

Error Message
IPPAClient- 3 -BIPPA2008 : There is no default configuration for specified toolbar type.. Service Name [String] error Id [String] Message [String]

Explanation The SocketService could not be started.

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

Error Message
IPPAClient- 3 -BIPPA2009 : BIPPA service could not obtain license from LRM service because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPAClient- 3 -BIPPA2010 : BIPPA service could not accept connection because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the CAD-BE client terminated the connection. If so, it is not a problem. 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 (59012) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
IPPAClient- 3 -BIPPA2011 : BIPPA service could not initialize socket connection from client because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the CAD-BE client terminated the connection. If so, it is not a problem. 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 (59012) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
IPPAClient- 3 -BIPPA2012 : Specified thread could not be started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the machine is low on memory. Stop unnecessary processes on the machine. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPAClient- 3 -BIPPA2013 : A waitable event is invalid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the machine is low on memory. Stop unnecessary processes on the machine. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPAClient- 3 -BIPPA2014 : CTI service is not available.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Nothing needs to be done if CTI service fails over successfully or was shutdown intentionally. Restart CTI service if it is not running. If CTI service is running, run Network Checks specified in Troubleshooting manual to determine why BIPPA service computer could not reach CTI service computer. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPAClient- 3 -BIPPA2015 : The CORBA connection information for the BIPPA service obtained from LRM service is invalid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure BIPPA service is running and active. Run Network Checks specified in Troubleshooting manual to ensure BIPPA service is reachable from client computer. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPAClient- 3 -BIPPA2016 : BIPPA service failed to get switch type from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure LDAP service is running and active. Run Network Checks specified in Troubleshooting manual to ensure LDAP service is reachable from BIPPA service computer. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPAClient- 3 -BIPPA2017 : Client socket descriptor is invalid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPAClient- 3 -BIPPA2018 : Specified thread could not be stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the machine is low on memory. Stop unnecessary processes on the machine. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPAClient- 4 -BIPPA3000 : Unable to allocate memory.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPAClient- 4 -BIPPA3001 : Unable to initialize registry watcher. BIPPA service is unable to detect changes to registry.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure that the user that the BIPPA service is running as has permission to read from registry. Restart the BIPPA service. If this does not correct the problem, contact technical support.

Error Message
IPPAClient- 4 -BIPPA3002 : Unable to check registry for local IP address BIPPA should use to create its CORBA service. It will try again every 10 seconds.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure that the user that the BIPPA service is running as has permission to read from registry. Restart the BIPPA service. If this does not correct the problem, contact technical support.

Error Message
IPPAClient- 4 -BIPPA3003 : Unable to get local IP address BIPPA should use to create its CORBA service from registry.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure that the user that the BIPPA service is running as has permission to read from registry. Restart the BIPPA service. If this does not correct the problem, contact technical support.

Error Message
IPPAClient- 4 -BIPPA3004 : Unable to enable NT Event logging for specified application name.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure that the user that the BIPPA service is running as has permission to read from registry. Restart the BIPPA service. If this does not correct the problem, contact technical support.

Error Message
IPPAClient- 4 -BIPPA3005 : The BIPPA service cannot communicate with the Directory Services server or the data was not found in Directory Services.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Nothing needs to be done if the data type is marked as optional. Default values will be used. Verify that the Directory Services server is running. If not, start it. (UCCE only) Verify that Directory Services has been populated using CAD Configuration Setup. Restart Directory Services. Restart BIPPA service. Verify the data exists in LDAP. If the data does not exist, it might need to be added using the Sync service (for agent and team information), Cisco Desktop Administrator (for workgroup and other settings), from previous backups/upgrades, or reinstall CAD. If this does not correct the problem, contact technical support.

Error Message
IPPAClient- 4 -BIPPA3006 : Specified icon file has unknown file format.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Action: Do the following: Ensure the file is an ICO or PNG file. Reload or replace icon file if needed. If this does not correct the problem, contact technical support.

Error Message
IPPAClient- 4 -BIPPA3007 : Unable to load icon file with specified format and size.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure the file is an ICO file. Ensure the file has an icon of specified size. Reload or replace icon file if needed. If this does not correct the problem, contact technical support.

Error Message
IPPAClient- 4 -BIPPA3008 : Unable to convert ICO icon with at specified index into PNG icon.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the file is an ICO file. Ensure the file has an icon at specified index. Reload or replace icon file if needed. If this does not correct the problem, contact technical support.

Error Message
IPPAClient- 4 -BIPPA3009 : Unable to read specified file.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the file exists. Ensure the file is readable by user BIPPA service is running as. Restart BIPPA service.

Error Message
IPPAClient- 4 -BIPPA3010 : Specified PNG icon file is empty.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Reload or replace PNG icon with non empty icon file.

Error Message
IPPAClient- 4 -BIPPA3011 : Unable to write specified file.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the directory exists. Ensure the file/directory is writable by user BIPPA service is running as. Restart BIPPA service.

Error Message
IPPAClient- 4 -BIPPA3012 : Unable to convert ICO icon to large PNG icon.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the file is an ICO file. Ensure the file has a small image in index 0 and large image in index 1. Reload or replace icon file if needed. If this does not correct the problem, contact technical support.

Error Message
IPPAClient- 4 -BIPPA3013 : There are no more licenses available.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: 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 minutes 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.

Error Message
IPPAClient- 4 -BIPPA3014 : 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.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the file exists. If this does not correct the problem, contact technical support.

Error Message
IPPAClient- 4 -BIPPA3015 : Unable to send specified CTI action to CTI service for specified agent/extension because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the CTI service is running, active, and reachable from BIPPA service computer. Check that the CTI service is a supported version for this version of BIPPA service. If this does not correct the problem, contact technical support.

Error Message
IPPAClient- 4 -BIPPA3016 : The IDs of response to CTI request do not match for specified agent ID/extension.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Retry CTI action to see if it happens again. Restart BIPPA service. If this does not correct the problem, contact technical support.

Error Message
IPPAClient- 4 -BIPPA3017 : Specified CTI action failed for specified agent ID/extension because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Check the error code and description for cause of problem.

Error Message
IPPAClient- 4 -BIPPA3018 : The maximum conference parties has been reached for specified agent extension.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Increase the maximum number of conference parties allowed for the extension. Do not attempt to conference more than maximum conference parties allowed.

Error Message
IPPAClient- 4 -BIPPA3019 : BIPPA client unable to communicate with BIPPA service because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure BIPPA service is running and active. Run Network Checks specified in Troubleshooting manual to ensure BIPPA service is reachable from client computer. Restart BIPPA service, wait until it is running and active before restarting BIPPA client.

Error Message
IPPAClient- 4 -BIPPA3020 : BIPPA client unable to communicate with BIPPA service because they are of different version.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action The client has to shutdown and restart again.

Error Message
IPPAClient- 4 -BIPPA3021 : BIPPA service could not get all the changed LDAP data from a replicated LDAP service before timeout (20 seconds) occurred.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify LDAP replication is working. Restart BIPPA service.

Error Message
IPPAClient- 6 -BIPPA0000 : BIPPA service is starting.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0001 : LRM service on specified host and port became inactive.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0002 : LRM service on specified host and port became active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0003 : BIPPA service on specified host and IOR became inactive.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0004 : BIPPA service on specified host and IOR became active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0005 : BIPPA service on this computer became active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0006 : BIPPA service on this computer became inactive.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0007 : BIPPA service is reloading LDAP information after reconnecting to LDAP service after LDAP service came up.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0008 : BIPPA service has lost connection to LDAP service. It will automatically attempt to recover connection to LDAP service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0009 : Specifies language used at this site obtained from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0010 : Specifies language used at this site obtained from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0011 : Specifies switch type used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0012 : Specifies default CCM version used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0013 : Specifies default CCM port used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0014 : Specifies CCM IP address and version used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0015 : Specifies CCM authentication URL used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0016 : Specifies BIPPA service information file used by IPPA JSP client and CAD-BE.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0017 : BIPPA service is waiting for post install to populate LDAP before BIPPA service can complete its startup.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0018 : BIPPA service is aborting initialization because shutdown was called.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0019 : .. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0020 : BIPPA service is waiting for IOR hostname to be populated in registry before BIPPA service can complete its startup.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0021 : Specifies IOR hostname obtained from registry that will be used to create BIPPA CORBA service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0022 : BIPPA service is not using IOR hostname from registry because it is empty.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0023 : Specifies CORBA IOR for BIPPA CORBA service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0024 : BIPPA service is shutting down.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0025 : BIPPA service received specified console control event.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0026 : BIPPA service could not set console event handler.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0027 : BIPPA service created specified object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0028 : BIPPA service destroyed specified object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0029 : Specified object was not initialized.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0030 : BIPPA service initialized specified object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0031 : BIPPA service shutdown specified object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0033 : Specified interface/service became available.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0034 : Specified interface/service became unavailable.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0035 : Specified thread has started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0036 : Specified thread has stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0037 : There is no Enterprise data for this call.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0038 : BIPPA service is stopped. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0039 : BIPPA socket service has shut down.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0040 : Specified CTI action timed out for specified agent ID/extension while waiting for response from CTI service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action This may happen ocasionly under heavy load. Agent can retry action again. If this happens often, run Basic Checks, CPU Checks and Memory Checks specified in Troubleshooting manual.

Error Message
IPPAClient- 6 -BIPPA0041 : Specified agent has already logged in.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check whether agent is logged in via a different interface. If so, logout from the other interface or do a force login from current interface. A BIPPA service or CTI service component may have stopped or restarted while an agent is logged in such that BIPPA service thinks the agent is not logged in when agent is still logged into the CTI service. In this case, do a force login.

Error Message
IPPAClient- 6 -BIPPA0042 : Specified agent could not change to desired state from current state.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check whether desired state is one that can be changed to from current state. If not, no action is needed. If it fails again, log the agent out and then back in, and then try again. Verify that the CTI service is running and active. If the error continues to occur, restart the CTI and IPPA services and try again. If the error persists, open a TAC case.

Error Message
IPPAClient- 6 -BIPPA0043 : Agent is unable to change state because the extension is incorrect or used by another agent.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check whether the extension entered is correct. Check whether another agent is using the extension.

Error Message
IPPAClient- 6 -BIPPA0044 : Agent is unable to change state because the extension is not configured correctly on Call Manager.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check whether the extension exists in Call Manager. Check whether the extension is configured correctly in Call Manager.

Error Message
IPPAClient- 6 -BIPPA0045 : Client connected to BIPPA service at specified host using specified IOR.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0046 : Specifies product offering used by BIPPA service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAClient- 6 -BIPPA0047 : CadBERequestHandlerFactory is now using specified connection session info.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 1 -BIPPA1000 : Unable to create CORBA service for the BIPPA service to receive requests from IP Phone Agent clients.. Service Name [String] error Id [String] Message [String]

Explanation The SocketService could not be started.

Recommended Action Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPASvr- 1 -BIPPA1001 : Unable to create TCP socket listener for the BIPPA service to receive requests from CAD-BE clients.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action 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 (59012) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
IPPASvr- 1 -BIPPA1002 : TCP socket dispatcher in BIPPA service for receiving requests from CAD-BE clients failed to run.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action 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 (59012) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
IPPASvr- 1 -BIPPA1003 : TCP socket listener used for receiving requests from CAD-BE clients could not be added to BIPPA socket dispatcher.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action 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 (59012) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
IPPASvr- 3 -BIPPA2000 : An error occurred while performing specified action.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPASvr- 3 -BIPPA2001 : An error occurred while setting up communication with the LRM service.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPASvr- 3 -BIPPA2002 : An error occurred while registering with the LRM service for BIPPA events.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPASvr- 3 -BIPPA2003 : Could not open the BIPPA service information file used by the IPPA JSP client and CAD-BE to communicate with the BIPPA service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the registry to see if the /HKLM/SOFTWARE/Spanlink/CAD/IPPA/Config/TOMCAT HOME registry value is the location of the Tomcat directory. By default, it is set to the folder C:\Program Files\Cisco\Desktop\Tomcat\ for UCCE and C:\Program Files\wfavvid\tomcat_appadmin\ for UCCX. Ensure the directory exists. Check the registry to see if the /HKLM/SOFTWARE/Spanlink/CAD/Site Setup/Install Directory registry value is the location of CAD software. By default, it is C:\Program Files\Cisco\Desktop\. 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 Message
IPPASvr- 3 -BIPPA2004 : The BIPPA service was unable to change its process priority to high because of the specified Windows error.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPASvr- 3 -BIPPA2005 : An error occurred while registering with the LRM service for LRM events.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPASvr- 3 -BIPPA2006 : An error occurred while registering BIPPA service with the LRM service.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPASvr- 3 -BIPPA2007 : The machine running the BIPPA service ran out of available memory.. Service Name [String] error Id [String] Message [String]

Explanation .

Recommended Action Stop unnecessary processes on the machine. Restart the BIPPA service. Run a memory check. See "Memory Check" on page 206. Add more memory to the machine.

Error Message
IPPASvr- 3 -BIPPA2008 : There is no default configuration for specified toolbar type.. Service Name [String] error Id [String] Message [String]

Explanation The SocketService could not be started.

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

Error Message
IPPASvr- 3 -BIPPA2009 : BIPPA service could not obtain license from LRM service because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPASvr- 3 -BIPPA2010 : BIPPA service could not accept connection because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the CAD-BE client terminated the connection. If so, it is not a problem. 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 (59012) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
IPPASvr- 3 -BIPPA2011 : BIPPA service could not initialize socket connection from client because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the CAD-BE client terminated the connection. If so, it is not a problem. 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 (59012) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
IPPASvr- 3 -BIPPA2012 : Specified thread could not be started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the machine is low on memory. Stop unnecessary processes on the machine. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPASvr- 3 -BIPPA2013 : A waitable event is invalid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the machine is low on memory. Stop unnecessary processes on the machine. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPASvr- 3 -BIPPA2014 : CTI service is not available.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Nothing needs to be done if CTI service fails over successfully or was shutdown intentionally. Restart CTI service if it is not running. If CTI service is running, run Network Checks specified in Troubleshooting manual to determine why BIPPA service computer could not reach CTI service computer. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPASvr- 3 -BIPPA2015 : The CORBA connection information for the BIPPA service obtained from LRM service is invalid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure BIPPA service is running and active. Run Network Checks specified in Troubleshooting manual to ensure BIPPA service is reachable from client computer. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPASvr- 3 -BIPPA2016 : BIPPA service failed to get switch type from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure LDAP service is running and active. Run Network Checks specified in Troubleshooting manual to ensure LDAP service is reachable from BIPPA service computer. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPASvr- 3 -BIPPA2017 : Client socket descriptor is invalid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPASvr- 3 -BIPPA2018 : Specified thread could not be stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the machine is low on memory. Stop unnecessary processes on the machine. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPASvr- 4 -BIPPA3000 : Unable to allocate memory.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPASvr- 4 -BIPPA3001 : Unable to initialize registry watcher. BIPPA service is unable to detect changes to registry.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure that the user that the BIPPA service is running as has permission to read from registry. Restart the BIPPA service. If this does not correct the problem, contact technical support.

Error Message
IPPASvr- 4 -BIPPA3002 : Unable to check registry for local IP address BIPPA should use to create its CORBA service. It will try again every 10 seconds.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure that the user that the BIPPA service is running as has permission to read from registry. Restart the BIPPA service. If this does not correct the problem, contact technical support.

Error Message
IPPASvr- 4 -BIPPA3003 : Unable to get local IP address BIPPA should use to create its CORBA service from registry.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure that the user that the BIPPA service is running as has permission to read from registry. Restart the BIPPA service. If this does not correct the problem, contact technical support.

Error Message
IPPASvr- 4 -BIPPA3004 : Unable to enable NT Event logging for specified application name.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure that the user that the BIPPA service is running as has permission to read from registry. Restart the BIPPA service. If this does not correct the problem, contact technical support.

Error Message
IPPASvr- 4 -BIPPA3005 : The BIPPA service cannot communicate with the Directory Services server or the data was not found in Directory Services.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Nothing needs to be done if the data type is marked as optional. Default values will be used. Verify that the Directory Services server is running. If not, start it. (UCCE only) Verify that Directory Services has been populated using CAD Configuration Setup. Restart Directory Services. Restart BIPPA service. Verify the data exists in LDAP. If the data does not exist, it might need to be added using the Sync service (for agent and team information), Cisco Desktop Administrator (for workgroup and other settings), from previous backups/upgrades, or reinstall CAD. If this does not correct the problem, contact technical support.

Error Message
IPPASvr- 4 -BIPPA3006 : Specified icon file has unknown file format.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Action: Do the following: Ensure the file is an ICO or PNG file. Reload or replace icon file if needed. If this does not correct the problem, contact technical support.

Error Message
IPPASvr- 4 -BIPPA3007 : Unable to load icon file with specified format and size.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure the file is an ICO file. Ensure the file has an icon of specified size. Reload or replace icon file if needed. If this does not correct the problem, contact technical support.

Error Message
IPPASvr- 4 -BIPPA3008 : Unable to convert ICO icon with at specified index into PNG icon.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the file is an ICO file. Ensure the file has an icon at specified index. Reload or replace icon file if needed. If this does not correct the problem, contact technical support.

Error Message
IPPASvr- 4 -BIPPA3009 : Unable to read specified file.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the file exists. Ensure the file is readable by user BIPPA service is running as. Restart BIPPA service.

Error Message
IPPASvr- 4 -BIPPA3010 : Specified PNG icon file is empty.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Reload or replace PNG icon with non empty icon file.

Error Message
IPPASvr- 4 -BIPPA3011 : Unable to write specified file.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the directory exists. Ensure the file/directory is writable by user BIPPA service is running as. Restart BIPPA service.

Error Message
IPPASvr- 4 -BIPPA3012 : Unable to convert ICO icon to large PNG icon.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the file is an ICO file. Ensure the file has a small image in index 0 and large image in index 1. Reload or replace icon file if needed. If this does not correct the problem, contact technical support.

Error Message
IPPASvr- 4 -BIPPA3013 : There are no more licenses available.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: 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 minutes 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.

Error Message
IPPASvr- 4 -BIPPA3014 : 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.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the file exists. If this does not correct the problem, contact technical support.

Error Message
IPPASvr- 4 -BIPPA3015 : Unable to send specified CTI action to CTI service for specified agent/extension because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the CTI service is running, active, and reachable from BIPPA service computer. Check that the CTI service is a supported version for this version of BIPPA service. If this does not correct the problem, contact technical support.

Error Message
IPPASvr- 4 -BIPPA3016 : The IDs of response to CTI request do not match for specified agent ID/extension.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Retry CTI action to see if it happens again. Restart BIPPA service. If this does not correct the problem, contact technical support.

Error Message
IPPASvr- 4 -BIPPA3017 : Specified CTI action failed for specified agent ID/extension because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Check the error code and description for cause of problem.

Error Message
IPPASvr- 4 -BIPPA3018 : The maximum conference parties has been reached for specified agent extension.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Increase the maximum number of conference parties allowed for the extension. Do not attempt to conference more than maximum conference parties allowed.

Error Message
IPPASvr- 4 -BIPPA3019 : BIPPA client unable to communicate with BIPPA service because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure BIPPA service is running and active. Run Network Checks specified in Troubleshooting manual to ensure BIPPA service is reachable from client computer. Restart BIPPA service, wait until it is running and active before restarting BIPPA client.

Error Message
IPPASvr- 4 -BIPPA3020 : BIPPA client unable to communicate with BIPPA service because they are of different version.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action The client has to shutdown and restart again.

Error Message
IPPASvr- 4 -BIPPA3021 : BIPPA service could not get all the changed LDAP data from a replicated LDAP service before timeout (20 seconds) occurred.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify LDAP replication is working. Restart BIPPA service.

Error Message
IPPASvr- 6 -BIPPA0000 : BIPPA service is starting.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0001 : LRM service on specified host and port became inactive.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0002 : LRM service on specified host and port became active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0003 : BIPPA service on specified host and IOR became inactive.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0004 : BIPPA service on specified host and IOR became active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0005 : BIPPA service on this computer became active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0006 : BIPPA service on this computer became inactive.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0007 : BIPPA service is reloading LDAP information after reconnecting to LDAP service after LDAP service came up.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0008 : BIPPA service has lost connection to LDAP service. It will automatically attempt to recover connection to LDAP service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0009 : Specifies language used at this site obtained from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0010 : Specifies language used at this site obtained from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0011 : Specifies switch type used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0012 : Specifies default CCM version used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0013 : Specifies default CCM port used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0014 : Specifies CCM IP address and version used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0015 : Specifies CCM authentication URL used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0016 : Specifies BIPPA service information file used by IPPA JSP client and CAD-BE.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0017 : BIPPA service is waiting for post install to populate LDAP before BIPPA service can complete its startup.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0018 : BIPPA service is aborting initialization because shutdown was called.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0019 : .. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0020 : BIPPA service is waiting for IOR hostname to be populated in registry before BIPPA service can complete its startup.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0021 : Specifies IOR hostname obtained from registry that will be used to create BIPPA CORBA service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0022 : BIPPA service is not using IOR hostname from registry because it is empty.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0023 : Specifies CORBA IOR for BIPPA CORBA service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0024 : BIPPA service is shutting down.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0025 : BIPPA service received specified console control event.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0026 : BIPPA service could not set console event handler.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0027 : BIPPA service created specified object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0028 : BIPPA service destroyed specified object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0029 : Specified object was not initialized.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0030 : BIPPA service initialized specified object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0031 : BIPPA service shutdown specified object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0033 : Specified interface/service became available.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0034 : Specified interface/service became unavailable.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0035 : Specified thread has started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0036 : Specified thread has stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0037 : There is no Enterprise data for this call.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0038 : BIPPA service is stopped. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0039 : BIPPA socket service has shut down.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0040 : Specified CTI action timed out for specified agent ID/extension while waiting for response from CTI service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action This may happen ocasionly under heavy load. Agent can retry action again. If this happens often, run Basic Checks, CPU Checks and Memory Checks specified in Troubleshooting manual.

Error Message
IPPASvr- 6 -BIPPA0041 : Specified agent has already logged in.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check whether agent is logged in via a different interface. If so, logout from the other interface or do a force login from current interface. A BIPPA service or CTI service component may have stopped or restarted while an agent is logged in such that BIPPA service thinks the agent is not logged in when agent is still logged into the CTI service. In this case, do a force login.

Error Message
IPPASvr- 6 -BIPPA0042 : Specified agent could not change to desired state from current state.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check whether desired state is one that can be changed to from current state. If not, no action is needed. If it fails again, log the agent out and then back in, and then try again. Verify that the CTI service is running and active. If the error continues to occur, restart the CTI and IPPA services and try again. If the error persists, open a TAC case.

Error Message
IPPASvr- 6 -BIPPA0043 : Agent is unable to change state because the extension is incorrect or used by another agent.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check whether the extension entered is correct. Check whether another agent is using the extension.

Error Message
IPPASvr- 6 -BIPPA0044 : Agent is unable to change state because the extension is not configured correctly on Call Manager.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check whether the extension exists in Call Manager. Check whether the extension is configured correctly in Call Manager.

Error Message
IPPASvr- 6 -BIPPA0045 : Client connected to BIPPA service at specified host using specified IOR.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0046 : Specifies product offering used by BIPPA service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPASvr- 6 -BIPPA0047 : CadBERequestHandlerFactory is now using specified connection session info.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 1 -BIPPA1000 : Unable to create CORBA service for the BIPPA service to receive requests from IP Phone Agent clients.. Service Name [String] error Id [String] Message [String]

Explanation The SocketService could not be started.

Recommended Action Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPAUtil- 1 -BIPPA1001 : Unable to create TCP socket listener for the BIPPA service to receive requests from CAD-BE clients.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action 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 (59012) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
IPPAUtil- 1 -BIPPA1002 : TCP socket dispatcher in BIPPA service for receiving requests from CAD-BE clients failed to run.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action 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 (59012) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
IPPAUtil- 1 -BIPPA1003 : TCP socket listener used for receiving requests from CAD-BE clients could not be added to BIPPA socket dispatcher.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action 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 (59012) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
IPPAUtil- 3 -BIPPA2000 : An error occurred while performing specified action.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPAUtil- 3 -BIPPA2001 : An error occurred while setting up communication with the LRM service.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPAUtil- 3 -BIPPA2002 : An error occurred while registering with the LRM service for BIPPA events.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPAUtil- 3 -BIPPA2003 : Could not open the BIPPA service information file used by the IPPA JSP client and CAD-BE to communicate with the BIPPA service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the registry to see if the /HKLM/SOFTWARE/Spanlink/CAD/IPPA/Config/TOMCAT HOME registry value is the location of the Tomcat directory. By default, it is set to the folder C:\Program Files\Cisco\Desktop\Tomcat\ for UCCE and C:\Program Files\wfavvid\tomcat_appadmin\ for UCCX. Ensure the directory exists. Check the registry to see if the /HKLM/SOFTWARE/Spanlink/CAD/Site Setup/Install Directory registry value is the location of CAD software. By default, it is C:\Program Files\Cisco\Desktop\. 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 Message
IPPAUtil- 3 -BIPPA2004 : The BIPPA service was unable to change its process priority to high because of the specified Windows error.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPAUtil- 3 -BIPPA2005 : An error occurred while registering with the LRM service for LRM events.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPAUtil- 3 -BIPPA2006 : An error occurred while registering BIPPA service with the LRM service.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPAUtil- 3 -BIPPA2007 : The machine running the BIPPA service ran out of available memory.. Service Name [String] error Id [String] Message [String]

Explanation .

Recommended Action Stop unnecessary processes on the machine. Restart the BIPPA service. Run a memory check. See "Memory Check" on page 206. Add more memory to the machine.

Error Message
IPPAUtil- 3 -BIPPA2008 : There is no default configuration for specified toolbar type.. Service Name [String] error Id [String] Message [String]

Explanation The SocketService could not be started.

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

Error Message
IPPAUtil- 3 -BIPPA2009 : BIPPA service could not obtain license from LRM service because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPAUtil- 3 -BIPPA2010 : BIPPA service could not accept connection because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the CAD-BE client terminated the connection. If so, it is not a problem. 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 (59012) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
IPPAUtil- 3 -BIPPA2011 : BIPPA service could not initialize socket connection from client because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the CAD-BE client terminated the connection. If so, it is not a problem. 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 (59012) as BIPPA service. If so, stop that service. If that service needs to be running, contact technical support. Check whether a firewall or security software is preventing BIPPA service from using the port. If the error persists, contact technical support.

Error Message
IPPAUtil- 3 -BIPPA2012 : Specified thread could not be started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the machine is low on memory. Stop unnecessary processes on the machine. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPAUtil- 3 -BIPPA2013 : A waitable event is invalid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the machine is low on memory. Stop unnecessary processes on the machine. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPAUtil- 3 -BIPPA2014 : CTI service is not available.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Nothing needs to be done if CTI service fails over successfully or was shutdown intentionally. Restart CTI service if it is not running. If CTI service is running, run Network Checks specified in Troubleshooting manual to determine why BIPPA service computer could not reach CTI service computer. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPAUtil- 3 -BIPPA2015 : The CORBA connection information for the BIPPA service obtained from LRM service is invalid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure BIPPA service is running and active. Run Network Checks specified in Troubleshooting manual to ensure BIPPA service is reachable from client computer. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPAUtil- 3 -BIPPA2016 : BIPPA service failed to get switch type from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure LDAP service is running and active. Run Network Checks specified in Troubleshooting manual to ensure LDAP service is reachable from BIPPA service computer. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPAUtil- 3 -BIPPA2017 : Client socket descriptor is invalid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPAUtil- 3 -BIPPA2018 : Specified thread could not be stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if the machine is low on memory. Stop unnecessary processes on the machine. Restart the BIPPA service. If the error persists, contact technical support.

Error Message
IPPAUtil- 4 -BIPPA3000 : Unable to allocate memory.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
IPPAUtil- 4 -BIPPA3001 : Unable to initialize registry watcher. BIPPA service is unable to detect changes to registry.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure that the user that the BIPPA service is running as has permission to read from registry. Restart the BIPPA service. If this does not correct the problem, contact technical support.

Error Message
IPPAUtil- 4 -BIPPA3002 : Unable to check registry for local IP address BIPPA should use to create its CORBA service. It will try again every 10 seconds.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure that the user that the BIPPA service is running as has permission to read from registry. Restart the BIPPA service. If this does not correct the problem, contact technical support.

Error Message
IPPAUtil- 4 -BIPPA3003 : Unable to get local IP address BIPPA should use to create its CORBA service from registry.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure that the user that the BIPPA service is running as has permission to read from registry. Restart the BIPPA service. If this does not correct the problem, contact technical support.

Error Message
IPPAUtil- 4 -BIPPA3004 : Unable to enable NT Event logging for specified application name.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure that the user that the BIPPA service is running as has permission to read from registry. Restart the BIPPA service. If this does not correct the problem, contact technical support.

Error Message
IPPAUtil- 4 -BIPPA3005 : The BIPPA service cannot communicate with the Directory Services server or the data was not found in Directory Services.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Nothing needs to be done if the data type is marked as optional. Default values will be used. Verify that the Directory Services server is running. If not, start it. (UCCE only) Verify that Directory Services has been populated using CAD Configuration Setup. Restart Directory Services. Restart BIPPA service. Verify the data exists in LDAP. If the data does not exist, it might need to be added using the Sync service (for agent and team information), Cisco Desktop Administrator (for workgroup and other settings), from previous backups/upgrades, or reinstall CAD. If this does not correct the problem, contact technical support.

Error Message
IPPAUtil- 4 -BIPPA3006 : Specified icon file has unknown file format.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Action: Do the following: Ensure the file is an ICO or PNG file. Reload or replace icon file if needed. If this does not correct the problem, contact technical support.

Error Message
IPPAUtil- 4 -BIPPA3007 : Unable to load icon file with specified format and size.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure the file is an ICO file. Ensure the file has an icon of specified size. Reload or replace icon file if needed. If this does not correct the problem, contact technical support.

Error Message
IPPAUtil- 4 -BIPPA3008 : Unable to convert ICO icon with at specified index into PNG icon.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the file is an ICO file. Ensure the file has an icon at specified index. Reload or replace icon file if needed. If this does not correct the problem, contact technical support.

Error Message
IPPAUtil- 4 -BIPPA3009 : Unable to read specified file.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the file exists. Ensure the file is readable by user BIPPA service is running as. Restart BIPPA service.

Error Message
IPPAUtil- 4 -BIPPA3010 : Specified PNG icon file is empty.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Reload or replace PNG icon with non empty icon file.

Error Message
IPPAUtil- 4 -BIPPA3011 : Unable to write specified file.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the directory exists. Ensure the file/directory is writable by user BIPPA service is running as. Restart BIPPA service.

Error Message
IPPAUtil- 4 -BIPPA3012 : Unable to convert ICO icon to large PNG icon.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the file is an ICO file. Ensure the file has a small image in index 0 and large image in index 1. Reload or replace icon file if needed. If this does not correct the problem, contact technical support.

Error Message
IPPAUtil- 4 -BIPPA3013 : There are no more licenses available.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: 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 minutes 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.

Error Message
IPPAUtil- 4 -BIPPA3014 : 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.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the file exists. If this does not correct the problem, contact technical support.

Error Message
IPPAUtil- 4 -BIPPA3015 : Unable to send specified CTI action to CTI service for specified agent/extension because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Ensure the CTI service is running, active, and reachable from BIPPA service computer. Check that the CTI service is a supported version for this version of BIPPA service. If this does not correct the problem, contact technical support.

Error Message
IPPAUtil- 4 -BIPPA3016 : The IDs of response to CTI request do not match for specified agent ID/extension.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Retry CTI action to see if it happens again. Restart BIPPA service. If this does not correct the problem, contact technical support.

Error Message
IPPAUtil- 4 -BIPPA3017 : Specified CTI action failed for specified agent ID/extension because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Check the error code and description for cause of problem.

Error Message
IPPAUtil- 4 -BIPPA3018 : The maximum conference parties has been reached for specified agent extension.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Do the following: Increase the maximum number of conference parties allowed for the extension. Do not attempt to conference more than maximum conference parties allowed.

Error Message
IPPAUtil- 4 -BIPPA3019 : BIPPA client unable to communicate with BIPPA service because of specified error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure BIPPA service is running and active. Run Network Checks specified in Troubleshooting manual to ensure BIPPA service is reachable from client computer. Restart BIPPA service, wait until it is running and active before restarting BIPPA client.

Error Message
IPPAUtil- 4 -BIPPA3020 : BIPPA client unable to communicate with BIPPA service because they are of different version.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action The client has to shutdown and restart again.

Error Message
IPPAUtil- 4 -BIPPA3021 : BIPPA service could not get all the changed LDAP data from a replicated LDAP service before timeout (20 seconds) occurred.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify LDAP replication is working. Restart BIPPA service.

Error Message
IPPAUtil- 6 -BIPPA0000 : BIPPA service is starting.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0001 : LRM service on specified host and port became inactive.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0002 : LRM service on specified host and port became active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0003 : BIPPA service on specified host and IOR became inactive.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0004 : BIPPA service on specified host and IOR became active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0005 : BIPPA service on this computer became active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0006 : BIPPA service on this computer became inactive.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0007 : BIPPA service is reloading LDAP information after reconnecting to LDAP service after LDAP service came up.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0008 : BIPPA service has lost connection to LDAP service. It will automatically attempt to recover connection to LDAP service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0009 : Specifies language used at this site obtained from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0010 : Specifies language used at this site obtained from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0011 : Specifies switch type used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0012 : Specifies default CCM version used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0013 : Specifies default CCM port used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0014 : Specifies CCM IP address and version used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0015 : Specifies CCM authentication URL used at this site.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0016 : Specifies BIPPA service information file used by IPPA JSP client and CAD-BE.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0017 : BIPPA service is waiting for post install to populate LDAP before BIPPA service can complete its startup.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0018 : BIPPA service is aborting initialization because shutdown was called.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0019 : .. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0020 : BIPPA service is waiting for IOR hostname to be populated in registry before BIPPA service can complete its startup.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0021 : Specifies IOR hostname obtained from registry that will be used to create BIPPA CORBA service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0022 : BIPPA service is not using IOR hostname from registry because it is empty.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0023 : Specifies CORBA IOR for BIPPA CORBA service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0024 : BIPPA service is shutting down.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0025 : BIPPA service received specified console control event.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0026 : BIPPA service could not set console event handler.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0027 : BIPPA service created specified object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0028 : BIPPA service destroyed specified object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0029 : Specified object was not initialized.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0030 : BIPPA service initialized specified object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0031 : BIPPA service shutdown specified object.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0033 : Specified interface/service became available.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0034 : Specified interface/service became unavailable.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0035 : Specified thread has started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0036 : Specified thread has stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0037 : There is no Enterprise data for this call.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0038 : BIPPA service is stopped. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0039 : BIPPA socket service has shut down.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0040 : Specified CTI action timed out for specified agent ID/extension while waiting for response from CTI service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action This may happen ocasionly under heavy load. Agent can retry action again. If this happens often, run Basic Checks, CPU Checks and Memory Checks specified in Troubleshooting manual.

Error Message
IPPAUtil- 6 -BIPPA0041 : Specified agent has already logged in.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check whether agent is logged in via a different interface. If so, logout from the other interface or do a force login from current interface. A BIPPA service or CTI service component may have stopped or restarted while an agent is logged in such that BIPPA service thinks the agent is not logged in when agent is still logged into the CTI service. In this case, do a force login.

Error Message
IPPAUtil- 6 -BIPPA0042 : Specified agent could not change to desired state from current state.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check whether desired state is one that can be changed to from current state. If not, no action is needed. If it fails again, log the agent out and then back in, and then try again. Verify that the CTI service is running and active. If the error continues to occur, restart the CTI and IPPA services and try again. If the error persists, open a TAC case.

Error Message
IPPAUtil- 6 -BIPPA0043 : Agent is unable to change state because the extension is incorrect or used by another agent.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check whether the extension entered is correct. Check whether another agent is using the extension.

Error Message
IPPAUtil- 6 -BIPPA0044 : Agent is unable to change state because the extension is not configured correctly on Call Manager.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check whether the extension exists in Call Manager. Check whether the extension is configured correctly in Call Manager.

Error Message
IPPAUtil- 6 -BIPPA0045 : Client connected to BIPPA service at specified host using specified IOR.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0046 : Specifies product offering used by BIPPA service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IPPAUtil- 6 -BIPPA0047 : CadBERequestHandlerFactory is now using specified connection session info.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgUserLocaleEnterpriseSvcParm : Error reading enterprise default user locale configuration.

Explanation A database exception was encountered when reading the default Enterprise User Locale setting. Default of US English will be used.

Recommended Action Verify that the Enterprise parameter setting for User Locale is configured using the CCM Admin web page. Restart the Cisco IP Voice Media Streaming App service.

Error Message
IpVmsAlarmCatalog- 6 -kANNICMPErrorNotification : ANN stream ICMP port unreachable error.. Call ID [ULong] Party ID [ULong] Destination IP Address [String] IP Port [ULong]

Explanation An announcement RTP stream had an ICMP (Internet Control Message Protocol) port unreachable error. The stream has been terminated. This ICMP error is a result of the destination end-point not having the receiving UDP/RTP port open to receive packets.

Recommended Action No action is required. This may occur at times when connections are being stopped or redirected.

Error Message
IpVmsAlarmCatalog- 3 -kANNDeviceRecordNotFound : ANN device record not found..

Explanation A device record for the announcer device was not found in the database. The ANN device is normally automatically added when the server is added to the database.

Recommended Action To add the ANN device to database you will need to remove/delete the server and re-add the server. WARNING: This may result in having to manually reconfigure many different settings such as Media Resource Groups, CallManager Groups and many others.

Error Message
IpVmsAlarmCatalog- 3 -kPWavMgrThreadxFailed : WAV playing manager thread creation failed. LastError [ULong] OS Error Description [String]

Explanation The process component used for playing WAV files failed to start, possibly due to low system resources.

Recommended Action Restart the Cisco IP Voice Media Streaming App service or restart server.

Error Message
IpVmsAlarmCatalog- 3 -kPWavMgrExitEventCreateFailed : Creation of needed event failed.. Error [ULong]

Explanation The needed events could not be created,; the service will exit.

Recommended Action The service needs to be restarted; if the error occurs again, the system needs to be rebooted.

Error Message
IpVmsAlarmCatalog- 3 -kPWavMgrThreadException : WAV file manager thread exception. Exception Code [ULong] EAX Register [ULong] EBX Register [ULong] ECX Register [ULong] EDX Register [ULong] ESI Register [ULong] EDI Register [ULong] EIP Register [ULong] ESP Register [ULong] EBP Register [ULong] Flags Register [ULong] CS Register [ULong] DS Register [ULong] ES Register [ULong] SS Register [ULong] FS Register [ULong] GS Register [ULong]

Explanation An unknown program exception has caused the background WAV file stream processing for announcement files to terminate.

Recommended Action Restart the Cisco IP Media Streaming App service and if the problem continues, report it to Cisco. Include CMS traces and Application Event log.

Error Message
IpVmsAlarmCatalog- 3 -ANNDeviceRecoveryCreateFailed : ANN device recovery create failure.. OS Error Code [Int] OS Error Description [String]

Explanation The ANN device startup failed, possibly due to lack of memory. If the error code is non-zero it may help determine the cause of the error. The announcement device will not be available.

Recommended Action Restart the Cisco IP Voice Media Streaming App service or restart server.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgANNListUnknownException : Unknown exception.. Device Name [String]

Explanation An unknown exception occurred while trying to read ANN device Cisco Unified Communications Manager list information.

Recommended Action Device will not start; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgANNListComException : COM error.. Device Name [String] COM Description String [String]

Explanation A COM error occurred while trying to read ANN device Cisco Unified Communications Manager list information.

Recommended Action Device will not start; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgANNListDblException : Database exception.. Device Name [String] Exception String [String] Exception ID [ULong]

Explanation A database exception occurred while trying to read ANN device Cisco Unified Communications Manager list information.

Recommended Action Device will not start; fix database problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgANNUnknownException : Unknown exception.. Device Name [String]

Explanation An unknown exception occurred while trying to read ANN device configuration information.

Recommended Action Device will not start; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgANNComException : COM error.. Device Name [String] COM Description String [String]

Explanation A COM error occurred while trying to read ANN device configuration information.

Recommended Action Device will not start; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgANNDblException : Database exception.. Device Name [String] Exception String [String] Exception ID [ULong]

Explanation A database exception occurred while trying to read ANN device configuration information.

Recommended Action Device will not start; fix database problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgEnterpriseException : Enterprisewide configuration exception.

Explanation An unknown exception occured reading Enterjprisewide configuration settings.

Recommended Action Verify the enterprise configuration settings and restart the IP Media Streaming Service.

Error Message
IpVmsAlarmCatalog- 3 -kCfgListUnknownException : Unknown Configuration Exception.

Explanation An exception error was generated reading the service parameter settings.

Recommended Action Restart the server.

Error Message
IpVmsAlarmCatalog- 3 -kCfgListComException : Configuration COM Exception. Exception description [String]

Explanation A COM exception error was generated reading the service parameter settings for devices.

Recommended Action Verify that service parameters can be viewed using CCM Administration. If they can then restart the service or server.

Error Message
IpVmsAlarmCatalog- 3 -kCfgListDblException : Configuration DBL Exception. Exception description [String] Exception identifier [ULong]

Explanation An exception error was generated reading the service parameter settings for devices.

Recommended Action Verify that service parameters can be viewed using CCM Administration. If they can then restart the service or server.

Error Message
IpVmsAlarmCatalog- 4 -kANNDeviceStartingDefaults : ANN device configuration not found. Parameter Name [String] Value Used [String]

Explanation A service parameter for Cisco IP Voice Media Streaming App service related to the ANN device configuration was not found. The system will start with the given default setting.

Recommended Action Review the service parameter settings and configure the ANN device settings properly using the CUCM Administration.

Error Message
IpVmsAlarmCatalog- 3 -kRequestedANNStreamsFailed : ANN requested streams failure.. Requested streams [ULong] Allocated streams [ULong]

Explanation The requested resources for the configured number of annunciator calls (Call Count service parameter) was not available. If the value shown as "Allocated" is non-zero

Recommended Action Verify the ANN Call Count service parameter is correct. A server restart may be needed to recover resources.

Error Message
IpVmsAlarmCatalog- 4 -kANNAudioCreateDirFailed : ANN create local path error. OS Error Code [ULong] OS Error Text [String] Path Name [String]

Explanation Unable to create a subdirectory to contain announcement files. This may be caused by insufficient disk storage. Announcements may not play correctly as a result of this error.

Recommended Action Check for available free space on the common data storage area. If full, take action to remove old trace files to free space. Restart the Cisco IP Voice Media Streaming App service.

Error Message
IpVmsAlarmCatalog- 3 -kANNAudioThreadWaitFailed : ANN TFTP event wait error. LastError [ULong]

Explanation An error was reported while waiting for a list of events. Announcement files will not be automatically updated.

Recommended Action Restart the Cisco IP Voice Media Streaming App service. If the error continues, restart the serverr.

Error Message
IpVmsAlarmCatalog- 3 -kANNAudioThreadException : ANN TFTP transfer exception failure. Exception Code [ULong] EAX Register [ULong] EBX Register [ULong] ECX Register [ULong] EDX Register [ULong] ESI Register [ULong] EDI Register [ULong] EIP Register [ULong] ESP Register [ULong] EBP Register [ULong] Flags Register [ULong] CS Register [ULong] DS Register [ULong] ES Register [ULong] SS Register [ULong] FS Register [ULong] GS Register [ULong]

Explanation An unknown program exception has caused the background TFTP file transfer processing for announcement files to terminate. Announcement files will not be automatically updated.

Recommended Action Restart the Cisco IP Media Streaming App service and if the problem continues, report it to Cisco. Include CMS traces and Application Event log.

Error Message
IpVmsAlarmCatalog- 3 -kANNAudioThreadxFailed : ANN TFTP transfer thread creation failed. LastError [ULong]

Explanation The ANN background TFTP file transfer processing thread failed to create possibly due to low system resources.

Recommended Action Reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kANNAudioComException : ANN TFTP COM exception. File name [String] Reason [String]

Explanation A COM exception occured while processing the specified file.

Recommended Action Review the file for possible format errors or missing elements.

Error Message
IpVmsAlarmCatalog- 3 -kANNAudioXmlLoadFailed : ANN XML parsing error. File name [String] Reason [String]

Explanation There is a syntax error in the specified file.

Recommended Action Correct the syntax error.

Error Message
IpVmsAlarmCatalog- 3 -kANNAudioXmlSyntax : ANN XML invalid element . File name [String]

Explanation There is an invalid element in the specified file.

Recommended Action Correct the error.

Error Message
IpVmsAlarmCatalog- 3 -kANNAudioTftpFileMissing : ANN TFTP file missing. File name [String]

Explanation A file was not found on the TFTP server to be downloaded to the announcement server.

Recommended Action Correct the error.

Error Message
IpVmsAlarmCatalog- 3 -kANNAudioTftpMgrStartFailed : TFTP start file transfer failed. File name [String]

Explanation Unable to start transfering a file from TFTP server.

Recommended Action Verify the file name exists on the TFTP server.

Error Message
IpVmsAlarmCatalog- 3 -kANNAudioTftpMgrCreate : Unable to create TFTP client. TFTP Server [String]

Explanation Unable to create a client TFTP session with the TFTP server.. This may be due to the server not running, or an incorrect server name configuration setting in service paramenters. This operation will be retried periodically.

Recommended Action Verify the TFTP server is operating and configuration settings are correct.

Error Message
IpVmsAlarmCatalog- 3 -kANNAudioOpenFailed : Open announcement file failed. OS Error Code [ULong] OS Error Description [String] File name [String]

Explanation An error was reported when attempting to open an announcement file for reading.

Recommended Action Verify the file exists and the Cisco IP Voice Media Streaming App service has proper access rights to open the file for reading.

Error Message
IpVmsAlarmCatalog- 4 -kANNAudioUndefinedLocale : Unknown ANN Locale. Locale identifier [ULong] Locale Type [String]

Explanation The requested Locale for an announcement is not installed. For network locale you use the platform CLI interface to run (run sql select * from typecountry where enum = #), #=locale. This will tell you what country locale is being requested.

Recommended Action Install the locale package or check device settings for an incorrect locale value.

Error Message
IpVmsAlarmCatalog- 4 -kANNAudioUndefinedAnnID : Requested announcement not found. Locale name [ULong] Announcement identifier [ULong]

Explanation The requested announcement is unknown. This may be caused by using an incorrect announcement identifier for a custom announcement. Use the CUCM Admin to view a list of custom announcement identifiers and verify the correct one is being used.

Recommended Action Correct the announcement identifier chosen from the custom announcement list.

Error Message
IpVmsAlarmCatalog- 3 -CFBDeviceRecoveryCreateFailed : CFB device recovery create failure.. OS Error Code [Int] OS Error Description [String]

Explanation The CFB device startup failed, possibly due to lack of memory. If the error code is non-zero it may help determine the cause of the error. The conference bridge device will not be available.

Recommended Action Restart the Cisco IP Voice Media Streaming App service or restart server.

Error Message
IpVmsAlarmCatalog- 3 -kAddIpVmsRenderFailed : Add IP VMS render filter-to-filter graph failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to add the IP VMS render filter-to-filter graph failed; audio source will not play possibly due to the lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kCFBDeviceRecordNotFound : CFB device record not found..

Explanation A device record for the software conference bridge device was not found in the database. The CFB device is normally automatically added when the server is added to the database.

Recommended Action To add the CFB device to database you will need to remove/delete the server and re-add the server. WARNING: This may result in having to manually reconfigure many different settings such as Media Resource Groups, CallManager Groups and many others.

Error Message
IpVmsAlarmCatalog- 4 -kCFBDeviceStartingDefualts : CFB device configuration not found.. Parameter Name [String] Value Used [String]

Explanation A service parameter for Cisco IP Voice Media Streaming App service related to the CFB device configuration was not found. The system will use the given default setting.

Recommended Action Review the service parameter settings and configure the CFB device settings properly using the CUCM Administration.

Error Message
IpVmsAlarmCatalog- 6 -kCFBICMPErrorNotification : CFB stream ICMP error.. Call ID [ULong] Party ID [ULong] Destination IP Address [String] IP Port [ULong]

Explanation A SW CFB RTP stream had an ICMP (Internet Control Message Protocol) port unreachable error. The stream has been terminated. This ICMP error is a result of the destination end-point does not have the receiving UDP/RTP port open to receive packets.

Recommended Action No action is required. This may occur at times when connections are being stopped or redirected.

Error Message
IpVmsAlarmCatalog- 4 -kChangeNotifyServiceCreationFailed : Database change notification subsystem not starting.. OS Error Code [Int] OS Error Description [String]

Explanation The background process to activate database changes has failed to start. Database changes affecting the Cisco IP Voice Media Streaming App service will not automatically take effect.

Recommended Action Restart the Cisco IP Voice Media Streaming App service to get the DB notification reenabled.

Error Message
IpVmsAlarmCatalog- 4 -kChangeNotifyServiceGetEventFailed : Invalid notification event returned by database change notification.. OS Error Code [Int] OS Error Description [String]

Explanation The change notification subsystem returned an invalid notification event. The Cisco IP Voice Media Streaming App service will terminate. The SW media devices (ANN, CFB, MOH, MTP) will be temporarily out of service and calls in progress may be dropped.

Recommended Action Check the current status of the Cisco IP Voice Media Streaming App service and monitor for repeated occurances.

Error Message
IpVmsAlarmCatalog- 4 -kChangeNotifyServiceRestartFailed : Database change notification restart failure.. OS Error Code [Int] OS Error Description [String]

Explanation The change notification subsystem failed to restart.

Recommended Action This service has change notification disabled, it may be reenabled at a later time or restart Cisco IP Voice Media Streaming App service to reenable immediately.

Error Message
IpVmsAlarmCatalog- 3 -kCreateAudioSourcesFailed : Creating audio source class failed.. OS Error Code [Int] OS Error Description [String]

Explanation Unable to create audio source subcombonent to provide audio for streaming. This may be due to lack of memory.

Recommended Action Restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message
IpVmsAlarmCatalog- 3 -kCreateControlFailed : Stream Control create failure.. Audio Source ID [ULong] Codec Type [String] OS Error Code [Int] OS Error Description [String]

Explanation Create stream control subcomponent. The error may possibly be due to lack of memory.

Recommended Action Reset the MOH device. If continues to fail restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message
IpVmsAlarmCatalog- 3 -kCreateGraphManagerFailed : Get graph manager failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get the graph manager failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 6 -kReadCfgIpTosMediaResourceToCmNotFound : IP TOS MediaResource to Cm value not found..

Explanation The IP Type-of-Service Media Resource To Call Manager service parameter value was not found in the database. Defaulting its value to 0x60 for CS3(precedence 3) DSCP (011000).

Recommended Action Set the Ip Type-of-Service Media Resource To Call Manager service parameter for the Cisco IP Voice Media Streaming App service.

Error Message
IpVmsAlarmCatalog- 4 -kDeviceDriverError : IP voice media streaming device driver error.. Error [String]

Explanation The IP voice media streaming device driver returned an error. This may indicate a significant media error or resource shortage.

Recommended Action Restarting the Cisco IP Voice Media Streaming App service or possibly restarting the server may resolve the error condition.

Error Message
IpVmsAlarmCatalog- 4 -kDeviceMgrCreateFailed : Device connection manager failed to start.. Device Name [String] Server Number [ULong] Server Name [String]

Explanation The device controller was unable to start a connection to control device registration with CallManager. This is possibly due to lack of memory.

Recommended Action Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server.

Error Message
IpVmsAlarmCatalog- 4 -kDeviceMgrExitEventCreationFailed : Creation of device manager exit event failed.. Device Name [String] Trace Name [String] Error [ULong] OS Error Text [String]

Explanation An error was reported when allocating an exit-control event for a SW media device. The device will not be registered with CallManager or active.

Recommended Action This error may be due to a memory resource shortage. Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server.

Error Message
IpVmsAlarmCatalog- 6 -kDeviceMgrLockoutWithCallManager : Cisco Unified Communications Manager in lockout.. Trace Name [String]

Explanation The specified Cisco Unified Communications Manager has failed to respond to control messages. The TCP control connection to CUCM is being suspended. This will cause a switch to another CUCM if one is available otherwise the device will be unavailable. There may be a shortage of CPU resource or some other error condition on the CUCM server.

Recommended Action Check the status of the Cisco Unified Communications Manager service. You may have to restart the CUCM service or the CUCM server.

Error Message
IpVmsAlarmCatalog- 5 -kDeviceMgrMoreThan50SocketEvents : More than 50 events returned from TCP link.. Trace Name [String]

Explanation The specified Cisco Unified Communications Manager TCP link has returned a large number of TCP events. This indicates an unexpected flood of events.

Recommended Action No action is required. Monitor for reoccurance. This could be an indication of a security issue.

Error Message
IpVmsAlarmCatalog- 4 -kDeviceMgrOpenReceiveFailedOutOfStreams : Open receive failure.. Trace Name [String] Conference ID [ULong] Party ID [ULong]

Explanation The open receive channel failed. This may indicate a missmatch of media resources between Cisco Unified Call Manager and the Cisco IP Voice Media Streaming App service.

Recommended Action Check the performance monitor counters for resource availability on CUCM and on Cisco IP Voice Media Streaming App. Also, you might run the Platform CLI command "Show Media Streams" to identify possible media connection resource leaks. Possibly reset the media device or restart Cisco IP Voice Media Streaming App or restart the CUCM server.

Error Message
IpVmsAlarmCatalog- 4 -kDeviceMgrRegisterKeepAliveResponseError : Cisco Unified Communications Manager not responding.. Trace Name [String]

Explanation The specified Cisco Unified Communications Manager is not responding to the keepalive messages. The connection with CUCM is being terminated and the media device will reregister with another Cisco Unified Call Manager if a secondary is configured. Otherwise, the media device will be unavailable until the device is able to reregister with CUCM.

Recommended Action Cisco Unified Communications Manager may have gone down or is unable to respond. Check status of CUCM. The media device should automatically reregister.

Error Message
IpVmsAlarmCatalog- 6 -kDeviceMgrRegisterWithCallManager : Registered with Cisco Unified Communications Manager.. Trace Name [String]

Explanation The software media device registered with the specified Cisco Unified Communications Manager.

Recommended Action No action is required.

Error Message
IpVmsAlarmCatalog- 4 -kDeviceMgrRegisterWithCallManagerError : Connection error with Cisco Unified Communications Manager.. Trace Name [String]

Explanation The media device was registered with the specified Cisco Unified Communications Manager and received a socket error or disconnect. This may occur normally when Cisco Unified Communications Manager is stopped.

Recommended Action No action is required. The media device will reregister.

Error Message
IpVmsAlarmCatalog- 4 -kDeviceMgrSocketDrvNotifyEvtCreateFailed : Create driver notification event failure.. Device Name [String] Trace Name [String] Error [ULong] OS Error Description [String]

Explanation An error was returned when creating a signaling event for communication with the media streaming kernel driver. This may be due to memory or system resource shortage.

Recommended Action Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server.

Error Message
IpVmsAlarmCatalog- 4 -kDeviceMgrSocketNotifyEventCreateFailed : Creation socket event failure.. Device Name [String] Trace Name [String] Error [ULong] OS Error Description [String]

Explanation An error was reported when creating a notification event for a socket interface. This may be due to a resource shortage. The media device will remain unavailable.

Recommended Action Restart the Cisco IP Voice Media Streaming App service and monitor for reoccurance or restart the CUCM server.

Error Message
IpVmsAlarmCatalog- 4 -kDeviceMgrStartTransmissionOutOfStreams : Start transmission failure.. Trace Name [String] Conference ID [ULong] Party ID [ULong]

Explanation An error was encountered while starting an RTP transmission audio stream. This may indicate a missmatch of resources between Cisco Unified Communications Manager and Cisco IP Voice Media Streaming App service.

Recommended Action Check the performance counters for the media resources on CUCM and Cisco IP Voice Media Streaming App to determine if there is a resource leak. You should also use the platform CLI command "Show Media Streams" to check for orphaned media RTP connections.

Error Message
IpVmsAlarmCatalog- 3 -kDeviceMgrThreadException : Exception in device manager thread.. Trace Name [String] Exception Code [ULong] EAX Register [ULong] EBX Register [ULong] ECX Register [ULong] EDX Register [ULong] ESI Register [ULong] EDI Register [ULong] EIP Register [ULong] ESP Register [ULong] EBP Register [ULong] Flags Register [ULong] CS Register [ULong] DS Register [ULong] ES Register [ULong] SS Register [ULong] FS Register [ULong] GS Register [ULong]

Explanation An exception occurred in the specified device manager thread.

Recommended Action MOH will automatically reset.

Error Message
IpVmsAlarmCatalog- 6 -kDeviceMgrThreadWaitFailed : Wait call failure in device manager thread.. Trace Name [String] OS Error Code [Int] OS Error Description [String]

Explanation An error was reported during a system request to wait on an event, the media device will be restarted.

Recommended Action No action is required.

Error Message
IpVmsAlarmCatalog- 4 -kDeviceMgrThreadxFailed : Creation of thread failure.. Device Name [String] Trace Name [String] OS Error Code [Int] OS Error Description [String]

Explanation An error was reported when starting a process for the specified media device. This may be due to a system resource shortage.

Recommended Action Restart the Cisco IP Voice Media Streaming App service or restart the CUCM server to recover from this error.

Error Message
IpVmsAlarmCatalog- 6 -kDeviceMgrUnregisterWithCallManager : Unregister with Cisco Unified Communications Manager.. Trace Name [String]

Explanation A media device has unregistered with the specified Cisco Unified Communications Manager.

Recommended Action No action is required. The media device will automatically reregister.

Error Message
IpVmsAlarmCatalog- 3 -kDownloadMOHFileFailed : Download request failure.. File Name [String]

Explanation The TFTP download request failed.

Recommended Action Validate the TFTP IP address in the database and that the file exists.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputAddAudioCaptureDeviceFailed : Add fixed audio source to filter graph failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to add the fixed audio source to the filter graph failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputAddG711AlawIpVmsRenderFailed : Add fixed G711 a-law IP VMS render filter-to-filter graph failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to add the fixed G711 a-law IP VMS render filter-to-filter graph failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputAddG711UlawIpVmsRenderFailed : Add fixed G711 ulaw IP VMS render filter to filter graph failed. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to add the fixed G711 mu-law IP VMS render filter-to-filter graph failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputAddG729IpVmsRenderFailed : Add fixed G729 IP VMS render filter-to-filter graph failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to add the fixed G729 IP VMS render filter-to-filter graph failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputAddMOHEncoderFailed : Add fixed MOH encode filter-to-filter graph failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to add the fixed MOH encode filter-to-filter graph failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputAddWideBandIpVmsRenderFailed : Add fixed wideband IP VMS render filter-to-filter graph failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to add the fixed wideband IP VMS render filter-to-filter graph failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputAudioCapMOHEncoderConnFailed : Connect fixed audio capture device to MOH encoder failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to connect the fixed audio source device to the MOH encoder failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputAudioCaptureCreateFailed : Get fixed system device enumerator failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get the fixed system device enumerator failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputClassEnumeratorCreateFailed : Create fixed class enumerator failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to create the fixed class enumerator failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 4 -kFixedInputCreateControlFailed : Fixed MOH stream control failed to start.. Audio Source ID [ULong] Codec Type [String]

Explanation The audio stream control subsystem for the Fixed MOH audio source failed to start. Audio from the MOH Fixed audio source will not be provided for streaming out. This may be due to resource shortage such as memory or availability of the Fixed MOH audio source device.

Recommended Action Reset MOH device, if failure continues restart the server. Monitor for errors in trace files and system log.

Error Message
IpVmsAlarmCatalog- 4 -kFixedInputCreateSoundCardFailed : Fixed stream sound card interface failed to start.. Audio Source ID [ULong] Codec Type [String]

Explanation An error was encountered when starting the interface to access the sound card for providing MOH fixed audio. The audio source will not play possibly due to shortage of memory.

Recommended Action Reset MOH device, or restart the Cisco IP Voice Media Streaming App service, or restart the server. Check the system log and possibly the traces for Cisco IP Voice Media Streaming App service.

Error Message
IpVmsAlarmCatalog- 4 -kFixedInputInitSoundCardFailed : Fixed stream sound card interface initialization failure.. Audio Source ID [ULong] System error code [ULong] Error text [String] Device name [String]

Explanation Initialization of sound card failed. Fixed audio source will not play possibly due to missing or unconfigured USB sound device.

Recommended Action Check that the USB sound is installed. Reset MOH device, or restart Cisco IP Voice Media Streaming App service, or restart the server. The system log and traces from Cisco IP Voice Media Streaming App may contain additionsl information.

Error Message
IpVmsAlarmCatalog- 4 -kFixedInputCodecStreamFailed : Fixed input codec stream initialization failure.. Audio Source ID [ULong] System error code [ULong] Error text [String] Codec Type [String]

Explanation Initialization of sound card codec source transcoding process failed. The fixed audio source will not play possibly due to memory or resource shortage.

Recommended Action Reset MOH device, or restart Cisco IO Voice Media Streaming App service, or restart server.

Error Message
IpVmsAlarmCatalog- 4 -kFixedInputTranscoderFailed : Fixed input audio stream transcoder failure.. Audio Source ID [ULong] System error code [ULong] Error text [String]

Explanation An error was encountered while transcoding audio from the sound card. The audio source will not play possibly due an error accessing the sound card.

Recommended Action Check that the USB sound device is properly installed. Unplug the USB sound device and replug back into the USB connector. Reset MOH device, restart Cisco IP Voice Media Streaming App service, or restart the server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputCreateGraphManagerFailed : Get fixed graph manager failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get the fixed graph manager failed, and audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputFindAudioCaptureDeviceFailed : Unable to find fixed audio source device.. Audio Source ID [ULong] Codec Type [String] Fixed audio source device name [String]

Explanation The specified fixed audio source device was not found; audio source will not play.

Recommended Action Make sure the proper device name is specified.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputGetEventNotificationFailed : Get fixed notification event failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get the fixed notification event failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputGetFileNameFailed : Get fixed audio source device name failure.. Audio Source ID [ULong] Codec Type [String]

Explanation The call to get the fixed audio source device name failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputGetG711AlawIpVmsRenderFailed : Get fixed G711 a-law IP VMS render filter failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get the fixed G711 a-law IP VMS render filter failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputGetG711AlawIpVmsRendInfFailed : Get fixed G711 a-law IP VMS render filter private interface failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get the fixed G711 a-law IP VMS render filter private interface failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputGetG711UlawIpVmsRenderFailed : Get fixed G711 mu-law IP VMS render filter failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get the fixed G711 ulaw ipvms render filter failed, audio source will not play, possibly due to lack of memory.

Recommended Action Reset MOH device, if out of resources reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputGetG711UlawIpVmsRendInfFailed : Get fixed G711 mu-aw IP VMS render filter private interface failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get the fixed G711 mu-law IP VMS render filter private interface failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputGetG729IpVmsRenderFailed : Get fixed G729 IP VMS render filter failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get the fixed G729 IP VMS render filter failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputGetG729IpVmsRendInfFailed : Get fixed G729 IP VMS render filter private interface failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get the fixed G729 IP VMS render filter private interface failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputGetMediaControlFailed : Get fixed media control failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get fixed media control failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputGetMediaPositionFailed : Get fixed media position failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get fixed media position failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputGetMOHEncoderFailed : Get fixed MOH encode filter failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get the fixed MOH encode filter failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputGetWideBandIpVmsRenderFailed : Get fixed wideband IP VMS render filter failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get the fixed wideband IP VMS render filter failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputGetWideBandIpVmsRendInfFailed : Get fixed wideband IP VMS render filter private interface failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get the fixed wideband IP VMS render filter private interface failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputMOHEncG711AlawRenderConnFail : Connect fixed MOH encoder to G711 a-law IP VMS render filter failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to connect the fixed MOH encoder to G711 a-law IP VMS render filter failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputMOHEncG711UlawRenderConnFail : Connect fixed MOH encoder to G711 u-law IP VMS render filter failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to connect the fixed MOH encoder to G711 u-law IP VMS render filter failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputMOHEncG729RenderConnFailed : Connect fixed MOH encoder to G729 IP VMS render filter failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to connect the fixed MOH encoder to G729 IP VMS render filter failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputMOHEncWidebandRenderConnFail : Connect fixed MOH encoder to wideband IP VMS render filter failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to connect the fixed MOH encoder to wideband IP VMS render filter failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kFixedInputSetNotifyWindowFailed : Set fixed notify window failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to set the fixed notify window failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kGetEventNotificationFailed : Get notification event failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get the notification event failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 4 -kGetFileNameFailed : Get audio source file name failure.. Audio Source ID [ULong] Codec Type [String]

Explanation The Music-on-Hold audio source is not assigned to an audio file.

Recommended Action Assign the audio source to an audio file or change the value of the MOH audio source to a value that has been configured.

Error Message
IpVmsAlarmCatalog- 3 -kGetIpVmsRenderFailed : Get IP VMS render filter failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get the IP VMS render filter failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kGetIpVmsRenderInterfaceFailed : Get IP VMS render filter private interface failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get the IP VMS render filter private interface failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kGetMediaControlFailed : Get media control failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get media control failed; audio source will not play, possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kGetMediaPositionFailed : Get media position failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to get media position failed; audio source will not play, possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 3 -kIPVMSDeviceDriverNotFound : Cisco IP voice media streaming driver not found..

Explanation The Cisco IP voice media streaming driver was not found or is not installed. The Cisco IP Voice Media Streaming App service cannot run until this error is resolved. All software media devices (ANN, CFB, MOH, MTP) for this server will not be available.

Recommended Action Check the system log for an error when the system attempted to load IpVms driver at the last server startup. A server restart is required to cause the driver to be loaded.

Error Message
IpVmsAlarmCatalog- 4 -kIPVMSMgrEventCreationFailed : Creation of required signaling event failed.. OS Error [ULong] OS Error Description [String]

Explanation An error was encountered when creating a signaling event component. This may be due to a resource shortage. The Cisco IP Voice Media Streaming App service will terminate.

Recommended Action Check the trace files for more information. The service should automatically be restarted. If this error continues to reoccur the server may need to be restarted.

Error Message
IpVmsAlarmCatalog- 4 -kIpVmsMgrThreadWaitFailed : Error while waiting for asynchronous notifications of events..

Explanation An error was reported while the primary control process for Cisco IP Voice Media Streaming App was waiting on asynchronous events to be signaled. The service will terminate and should automatically be restarted. This will cause a temporary loss of availability for the software media devices (ANN, CFB, MOH, MTP).

Recommended Action Monitor the service and status of the software media devices. The service should automatically restart. If the problem continues, review the trace files for additional information. A server restart may be required if this repeats.

Error Message
IpVmsAlarmCatalog- 3 -kIpVmsMgrNoLocalHostName : Unable to retrieve the local host server name..

Explanation Unable to obtain the local host server name. The Cisco IP Voice Media Streaming App service will terminate. No software media devices (ANN, CFB, MOH, MTP) will be available while the service is stopped.

Recommended Action Check the configuration settings for the server name, DHCP, or DNS. Monitor the status of Cisco IP Voice Media Streaming App service. The service will not operate without a valid server name.

Error Message
IpVmsAlarmCatalog- 3 -kIpVmsMgrNoLocalNetworkIPAddr : Unable to retrieve the network IP address for host server..

Explanation Unable to obtain the network IP (dotted) address. The Cisco IP Voice Media Streaming App service will terminate. The software media devices (ANN, CFB, MOH, MTP) will be unavailable while this service is stopped.

Recommended Action Monitor the status of the Cisco IP Voice Media Streaming App service. It should be automatically restarted. If the error occurs again, check the server IP configuration (DHCP, IP address).

Error Message
IpVmsAlarmCatalog- 4 -kIPVMSMgrThreadxFailed : Creation of the IPVMSMgr thread failed.. OS Error [ULong] OS Error Description [String]

Explanation An error was encountered while starting a process thread. The Cisco IP Voice Media Streaming App service will terminate. The software media devices (ANN, CFB, MOH, MTP) will be unavailable while the service is stopped.

Recommended Action Monitor the status of the Cisco IP Voice Media Streaming App service. It should automatically be restarted. If the error reoccurs, restart the server.

Error Message
IpVmsAlarmCatalog- 3 -kIPVMSMgrWrongDriverVersion : Wrong version of device driver.. Version Found Running [ULong] Version Needed [ULong]

Explanation An incompatible device driver was found. The Cisco IP Voice Media Streaming App service will terminate. The software media devices (ANN, CFB, MOH, MTP) will be unavailable while the service is stopped.

Recommended Action Restart the server to ensure the most recent driver is started. If the error continues, then reinstall Cisco Unified Communications Manager to get the proper driver version installed.

Error Message
IpVmsAlarmCatalog- 6 -kIPVMSStarting : IP voice media streaming application starting.. Version [String] IPAddress [String] Hostname [String] ServiceName [String] ProcessID [ULong]

Explanation The Cisco IP Voice Media Streaming App service is starting.

Recommended Action No action is required.

Error Message
IpVmsAlarmCatalog- 6 -kIPVMSStopping : The IP voice media streaming application shutting down.. Version [String] IPAddress [String] Hostname [String] ServiceName [String] ProcessID [ULong]

Explanation The Cisco IP Voice Media Streaming App service is shutting down.

Recommended Action No action is required.

Error Message
IpVmsAlarmCatalog- 4 -kMOHBadMulticastIP : Invalid multicast IP address.. MOH Audio Source ID [ULong] Call/Conference ID [ULong] Codec Type [String] Multicast IP Address [String] Multicast IP Port [ULong]

Explanation An invalid multicast IP address (out of range) was found.

Recommended Action Correct the setting on the Music-on-Hold device configuration for multicast address.

Error Message
IpVmsAlarmCatalog- 4 -kMOHDeviceRecordNotFound : MOH device record not found..

Explanation A Music-on-Hold device was not found for this server. This device is normally automatically added when a server is added to the configuration.

Recommended Action If Music-on-Hold functionality is required, you will need to remove and readd server to the database. WARNING: This may impact many other configuration settings (CM Groups, Media Resource Groups, etc...).

Error Message
IpVmsAlarmCatalog- 3 -kMOHFilterNotifyError : Error on DirectShow returned or user abort.. Audio Source ID [ULong] Codec Type [String]

Explanation The DirectShow filter returned an error or user abort. Audio source may quit playing.

Recommended Action No action is required; audio should start back up when requested to play the next time.

Error Message
IpVmsAlarmCatalog- 6 -kMOHICMPErrorNotification : MOH stream ICMP error.. Call ID [ULong] Party ID [ULong] Destination IP Address [String] IP Port [ULong]

Explanation A Music-on-Hold transmission stream had an ICMP (Internet Control Message Protocol) port unreachable error. The stream has been terminated. This may occur occasionally depending on call termination sequences.

Recommended Action No action is required.

Error Message
IpVmsAlarmCatalog- 4 -kMOHMgrCreateFailed : Error starting MOH Audio source subcomponent.. OS Error [ULong] OS Error Description [String]

Explanation A error was encountered by the Music-on-Hold device while starting the sub-component that provides audio from files or sound card. This may be due to shortage of resources (memory).

Recommended Action Restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message
IpVmsAlarmCatalog- 4 -kMOHMgrExitEventCreationFailed : Creation of MOH manager exit event failed.. OS Error [ULong] OS Error Description [String]

Explanation An error was encountered when allocating a signaling event. This may be caused by a resource shortage.

Recommended Action Restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message
IpVmsAlarmCatalog- 6 -kMOHMgrIsAudioSourceInUseThisIsNULL : Synchronization error detected in MOH audio manager..

Explanation A synchronization error was detected. Condition has been resolved automatically.

Recommended Action No action is required.

Error Message
IpVmsAlarmCatalog- 3 -kMOHMgrThreadCreateWindowExFailed : Creation of MOH manager message window failure.. Error [ULong]

Explanation The creation of the MOH manager message window failed. MOH device is being restarted.

Recommended Action No action is required; if this continues, check whether system is out of resources; reboot system if needed.

Error Message
IpVmsAlarmCatalog- 6 -kMOHMgrThreadWaitFailed : Wait call failure in MOH manager thread.. OS Error [ULong] OS Error Description [String]

Explanation An error was encountered in Music-on-Hold audio manager subcomponent while waiting for aynchronous event signaling. The MOH device will be restarted.

Recommended Action No action is required.

Error Message
IpVmsAlarmCatalog- 4 -kMOHMgrThreadxFailed : Starting of MOH audio manager failed.. OS Error [ULong] OS Error Description [String]

Explanation An error was encountered when starting the Music-on-Hold audio manager subcomponent. Music-on-Hold audio services will not be avaliable.

Recommended Action Restart the Cisco IP Voice Media Streaming App service.

Error Message
IpVmsAlarmCatalog- 3 -kMOHPlayStreamControlNull : Stream Control pointer is NULL. Audio Source ID [ULong] Codec Type [String]

Explanation The stream control pointer is null, unable to play stream.

Recommended Action Reset MOH device.

Error Message
IpVmsAlarmCatalog- 3 -kMOHPlayStreamMediaControlObjectNull : Media Position COM interface is NULL. Audio Source ID [ULong] Codec Type [String]

Explanation The media position COM interface is null and unable to play stream.

Recommended Action Reset MOH device.

Error Message
IpVmsAlarmCatalog- 6 -kMOHRewindStreamControlNull : Attempted to rewind an inactive MOH audio source.. Audio Source ID [ULong] Codec Type [String]

Explanation An attempt was made to rewind or restart the Music-on-Hold audio source that is inactive. This has been ignored.

Recommended Action No action required.

Error Message
IpVmsAlarmCatalog- 6 -kMOHRewindStreamMediaPositionObjectNull : Error rewinding MOH audio source that is not playing.. Audio Source ID [ULong] Codec Type [String]

Explanation An attempt was made to rewind or restart a Music-on-Hold wav file that was not being played. This has been ignored.

Recommended Action No action is required.

Error Message
IpVmsAlarmCatalog- 3 -kMOHTFTPGoRequestFailed : Transfer of MOH source file to working path failed.. Error Description [String] File Name [String] Source Path [String] Destination Path [String] OS Error Code [Int] OS Error Description [String]

Explanation An error was encountered when trying to copy or update a Music-on-Hold audio source file.

Recommended Action Use the Platform CLI to verify the source path and file exist. If the file does not exist then use CUCMAdmin to reupload the missing audio source to this specific server. Reinstall the Cisco Unified Communications Manager to have all required paths created.

Error Message
IpVmsAlarmCatalog- 3 -kMOHThreadException : Exception in MOH manager thread.. Exception Code [ULong] EAX Register [ULong] EBX Register [ULong] ECX Register [ULong] EDX Register [ULong] ESI Register [ULong] EDI Register [ULong] EIP Register [ULong] ESP Register [ULong] EBP Register [ULong] Flags Register [ULong] CS Register [ULong] DS Register [ULong] ES Register [ULong] SS Register [ULong] FS Register [ULong] GS Register [ULong]

Explanation An exception occurred in MOH manager thread.

Recommended Action MOH will automatically reset.

Error Message
IpVmsAlarmCatalog- 4 -kMTPDeviceRecordNotFound : MTP device record not found..

Explanation A device record for the software media termination point device was not found in the database. This is normally automatically added to the database when a server is added to the database. The software MTP device will be disabled.

Recommended Action If MTP functionality is required, you will need to delete the server and re-add the server back to the database using CCMAdmin. WARNING: This may require many additional configuration settings to be reapplied such as CallManager Groups, Media Resource groups and more.

Error Message
IpVmsAlarmCatalog- 6 -kMTPDeviceStartingDefualts : MTP device configuration not found, starting with defaults.. MTP Call Count [ULong] MTP Run Flag [String]

Explanation One or more Cisco IP Voice Media Streaming App service parameter settings for the MTP device were not found in the database. The default values are included here.

Recommended Action Configure the service parameter settings for the MTP device.

Error Message
IpVmsAlarmCatalog- 6 -kMTPICMPErrorNotification : MTP stream ICMP error.. Call ID [ULong] Party ID [ULong] Destination IP Address [String] IP Port [ULong]

Explanation An MTP stream had an ICMP error; stream has been terminated.

Recommended Action No action is required.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgCFBComException : COM error.. Device Name [String] COM Description String [String]

Explanation A COM error occurred while trying to read CFB configuration information.

Recommended Action Device will not start; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgCFBDblException : Database exception.. Device Name [String] Exception String [String] Exception ID [ULong]

Explanation A database exception occurred while trying to read CFB configuration information.

Recommended Action Device will not start; fix database problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgCFBListComException : COM error.. Device Name [String] COM Description String [String]

Explanation A COM error occurred while trying to read CFB Cisco Unified Communications Manager list information.

Recommended Action Device will not start; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgCFBListDblException : Database exception.. Device Name [String] Exception String [String] Exception ID [ULong]

Explanation A database exception occurred while trying to read CFB Cisco Unified Communications Manager list information.

Recommended Action Device will not start; fix database problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgCFBListUnknownException : Unknown exception.. Device Name [String]

Explanation An unknown exception occurred while trying to read CFB Cisco Unified Communications Manager list information.

Recommended Action Device will not start; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgCFBUnknownException : Unknown exception.. Device Name [String]

Explanation An unknown exception occurred while trying to read CFB configuration information.

Recommended Action Device will not start; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 6 -kReadCfgDblGetChgNotifyFailed : Get change notification port failure..

Explanation The database layer was unable to find change notification port and is using default.

Recommended Action If default change notification is incorrect or change notification does not work, add value into database and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgDblGetNodeNameFailed : Database layer select my process node failed..

Explanation The database layer was unable to find/determine the current node on which this service is running.

Recommended Action Make sure the database is configured properly.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgMOHAudioSourceComException : COM error.. Device Name [String] COM Description String [String]

Explanation A COM error occurred while trying to read MOH audio sources.

Recommended Action Audio sources will be disabled; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgMOHAudioSourceDblException : Database exception.. Device Name [String] Exception String [String] Exception ID [ULong]

Explanation A database exception occurred while trying to read MOH audio sources.

Recommended Action Audio sources will be disabled; fix database problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgMOHAudioSourceUnknownException : Unknown exception.. Device Name [String]

Explanation An unknown exception occurred while trying to read MOH audio sources.

Recommended Action Audio sources will be disabled; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgMOHComException : COM error.. Device Name [String] COM Description String [String]

Explanation A COM error occurred while trying to read MOH configuration information.

Recommended Action Device will not start; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgMOHDblException : Database exception.. Device Name [String] Exception String [String] Exception ID [ULong]

Explanation A database exception occurred while trying to read MOH configuration information.

Recommended Action Device will not start; fix database problem and restart service.

Error Message
IpVmsAlarmCatalog- 6 -kReadCfgMOHEnabledCodecsNotFound : MOH enabled codecs not found..

Explanation The Music-on-Hold service parameter for codec selection could not be read from database. Defaulting to G.711 mu-law codec.

Recommended Action Set the Music-on-Hold service parameter for Cisco IP Voice Media Streaming App service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgEnterpriseComException : COM error.. COM Description String [String]

Explanation A COM error occurred while trying to read clsterwide service parameters.

Recommended Action MOH or ANN audio sources may be unavailable; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgEnterpriseDblException : Database exception.. Exception String [String] Exception ID [ULong]

Explanation A database exception occurred while trying to read clusterwide service parameters.

Recommended Action MOH or ANN audio sources may be unavailable; fix database problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgEnterpriseUnknownException : Unknown exception..

Explanation An unknown exception occurred while tring to read clusterwide service parameters.

Recommended Action MOH or ANN audio sources may be unavailable; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgMOHListComException : COM error.. Device Name [String] COM Description String [String]

Explanation A COM error occurred while trying to read MOH Cisco Unified Communications Manager list information.

Recommended Action Device will not start; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgMOHListDblException : Database exception.. Device Name [String] Exception String [String] Exception ID [ULong]

Explanation A database exception occurred while trying to read MOH Cisco Unified Communications Manager list information.

Recommended Action Device will not start; fix database problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgMOHListUnknownException : Unknown exception.. Device Name [String]

Explanation An unknown exception occurred while trying to read MOH Cisco Unified Communications Manager list information.

Recommended Action Device will not start; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgMOHServerComException : COM error.. Device Name [String] COM Description String [String]

Explanation A COM error occurred while trying to read MOH device information.

Recommended Action Device will not start; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgMOHServerDblException : Database exception.. Device Name [String] Exception String [String] Exception ID [ULong]

Explanation A database exception occurred while trying to read MOH device information.

Recommended Action Device will not start; fix database problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgMOHServerUnknownException : Unknown exception.. Device Name [String]

Explanation An unknown exception occurred while trying to read MOH device information.

Recommended Action Device will not start; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgMOHTFTIPAddressNotFound : MOH TFTP IP address not found..

Explanation The default MOH TFTP IP address was not found in the database.

Recommended Action Audio sources may be unavailable; create proper value in database and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgMOHUnknownException : Unknown exception.. Device Name [String]

Explanation An unknown exception occurred while trying to read MOH configuration information.

Recommended Action Device will not start; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgMTPComException : COM error.. Device Name [String] COM Description String [String]

Explanation A COM error occurred while trying to read MTP configuration information.

Recommended Action Device will not start; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgMTPDblException : Database exception.. Device Name [String] Exception String [String] Exception ID [ULong]

Explanation A database exception occurred while trying to read MTP configuration information.

Recommended Action Device will not start; fix database problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgMTPListComException : COM error.. Device Name [String] COM Description String [String]

Explanation A COM error occurred while trying to read MTP Cisco Unified Communications Manager list information.

Recommended Action Device will not start; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgMTPListDblException : Database exception.. Device Name [String] Exception String [String] Exception ID [ULong]

Explanation A database exception occurred while trying to read MTP Cisco Unified Communications Manager list information.

Recommended Action Device will not start; fix database problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgMTPListUnknownException : Unknown exception.. Device Name [String]

Explanation An unknown exception occurred while trying to read MTP Cisco Unified Communications Manager list information.

Recommended Action Device will not start; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kReadCfgMTPUnknownException : Unknown exception.. Device Name [String]

Explanation An unknown exception occurred while trying to read MTP configuration information.

Recommended Action Device will not start; fix problem and restart service.

Error Message
IpVmsAlarmCatalog- 3 -kRenderFileFailed : Render file-to-filter graph failure.. Audio Source ID [ULong] Filename [String] Codec Type [String] COM Error [ULong]

Explanation The COM call to render the audio source file-to-filter graph failed; audio source will not play, possibly due to missing audio source or lack of memory.

Recommended Action Check to see if the audio source exists. Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 4 -kRequestedCFBStreamsFailed : CFB requested streams failure.. Requested streams [ULong] Allocated streams [ULong]

Explanation The resources for the number of requested full-duplex streams was not available.

Recommended Action Verify the Cisco IP Voice Media Streaming App service parameter for number of CFB calls. Restart the server to reset the stream resources.

Error Message
IpVmsAlarmCatalog- 4 -kRequestedMOHStreamsFailed : MOH requested streams failure.. Requested streams [ULong] Allocated streams [ULong]

Explanation The resources for the number of requested streams was not available.

Recommended Action Verify the number of calls configuration setting for Music-on-Hold device. Restart the server to reset the resources.

Error Message
IpVmsAlarmCatalog- 4 -kRequestedMTPStreamsFailed : MTP requested streams failure.. Requested streams [ULong] Allocated streams [ULong]

Explanation The resources for the number of requested full-duplex Media Termination Point streams was not available.

Recommended Action Verify the Cisco IP Voice Media Streaming App service parameter setting for number of MTP calls is correct. Restart the server to reset the available resources.

Error Message
IpVmsAlarmCatalog- 3 -kSetNotifyWindowFailed : Set notify window failure.. Audio Source ID [ULong] Codec Type [String] COM Error [ULong]

Explanation The COM call to set the notify window failed; audio source will not play possibly due to lack of memory.

Recommended Action Reset MOH device; if out of resources, reboot server.

Error Message
IpVmsAlarmCatalog- 4 -MOHDeviceRecoveryCreateFailed : MOH device recovery create failure.. OS Error Code [ULong] OS Error Description [String]

Explanation An error was encountered restarting the Music-on-Hold device. This may be caused by a shortage of memory resources.

Recommended Action Check the status of the Music-on-Hold device. If the MOH device is not registered and available, Restart the Cisco IP Voice Media Streaming App service or restart the server.

Error Message
IpVmsAlarmCatalog- 4 -MTPDeviceRecoveryCreateFailed : MTP device recovery create failure.. OS Error Code [ULong] OS Error Description [String]

Explanation An error was encountered trying to restart the Media Termination Point device. This may be due to a shortage of application memory.

Recommended Action Restart the IP Voice Media Streaming App service or restart the server.

Error Message
IpVmsAlarmCatalog- 4 -SoftwareLicenseNotValid : Invalid Software License..

Explanation There is no valid software license; the Cisco IP Voice Media Streaming App service requires a valid software license to operate.

Recommended Action Install a valid software license and restart Cisco IP Voice Media Streaming App service.

Error Message
IpVmsAlarmCatalog- 6 -SoftwareLicenseValid : Valid Software License Found..

Explanation A valid software license has been detected by the IP Voice Media Streaming App service.

Recommended Action No action required. This informational message indicates alarm SoftwareLicenseNotValid is cleared.

Error Message
IpVmsAlarmCatalog- 4 -kANNAudioFileMissing : Announcement file not found.. Missing filename [String] Announcement Identifier [ULong] User locale [ULong] Network locale [ULong]

Explanation The annunciator was unable to access an announcement audio file. This may be caused by not uploading a custom announcement to each server in the cluster or a locale has not been installed on the server.

Recommended Action Upload the custom announcement to the server or install the missing locale package.

Error Message
IpVmsAlarmCatalog- 3 -CryptoCapabilityFailed : Failed to initialize sRTP crypto.. Media Device Name [String]

Explanation The media device shown in this alarm attempted to load and initialize crypto capabilities within the operating system kernel, however, a failure, such as the OS lacking encryption configuration, a memory shortage, or crypto self-test failure, occurred during initialization. Secure media encryption for this device has been disabled as a result, but unencrypted media is still supported. All media streams are non-secure (unencrypted) for this device. This alarm is capable of occurring when the crypto failure occurs because the Cisco IP Voice Media Streaming App service parameter Force Annunciator to be Non-secure or Force MOH to be Non-secure is enabled.

Recommended Action Use the Cisco Unified Real-Time Monitoring Tool (RTMT) to retrieve the system log. Review the system log and respond to error messages containing sRTP or IpVms.

Error Message
IpVmsAlarmCatalog- 4 -PlayAnnouncementFailure : Unable to play a requested announcement or tone. Reason code [ULong] Announcement identifier [String] Locale name [String] Announcement enumerated number [ULong] Announcement file name [String] Custom file name [String]

Explanation Reason code explanations: [1] Announcement requested is undefined. The announcement enum number is unknown. [2] Locale requested is unknown. The requested locale has not been installed on this node. [3] The customized announcement file does not exist on this server node for the locale. If a default system announcement is assigned, it will be used in place of the customized announcement. [4] Internal annunciator resource shortage has caused the announcement to fail. [5] System announcement or tone file not found.

Recommended Action Recommendations based on reason code: [1] this is usually a system design issue and cannot be resolved by normal means; [2] Be sure the requested locale is installed on each CUCM server node; [3] Upload the customized announcement wav file to this server node using CCM Administration on this node; [4] Review the annunciator device configuration for maximum number of calls and/or schedule an annunciator device reset as a temporary workaround to ensure orphanned resources are released or restart the Cisco IP Voice Media Streaming App service; [5] Check locale is installed on CUCM server node or possible missing file not installed properly.

Error Message
JavaApplications- 6 -IPMAStarted : IPMA Application started . Servlet Name [String] Reason [String]

Explanation Application started successfully

Recommended Action No action required.

Error Message
JavaApplications- 4 -IPMAStopped : IPMA Application stopped. Servlet Name [String] Reason [String]

Explanation Application was unloaded from Tomcat

Recommended Action Check if Tomcat service is up.

Error Message
JavaApplications- 0 -IPMANotStarted : IPMA Application not started. Servlet Name [String] Reason [String]

Explanation Error occurred while starting application

Recommended Action See application logs for error

Error Message
JavaApplications- 3 -IPMAApplicationError : IPMA Application error. Servlet Name [String] Reason [String]

Explanation IPMA application error

Recommended Action See application logs for details

Error Message
JavaApplications- 4 -IPMAManagerLogout : IPMA Manager Logged out. Servlet Name [String] Reason [String]

Explanation IPMA Manager Logged out by application

Recommended Action To re-login the user, click update in the CCMAdmin IPMA Service configuration page for this user.

Error Message
JavaApplications- 3 -IPMAOverloaded : IPMA Application overloaded. Servlet Name [String] Reason [String]

Explanation IPMA application overloaded

Recommended Action See application logs for details

Error Message
JavaApplications- 3 -IPMAFilteringDown : IPMA Application filtering is down. Servlet Name [String] Reason [String]

Explanation IPMA Application filtering is down

Recommended Action Restart Cisco IP Manager Assistant Service

Error Message
JavaApplications- 6 -IPMAInformation : IPMA Information . Servlet Name [String] Reason [String]

Explanation Application information

Recommended Action No action required.

Error Message
JavaApplications- 6 -BDIStarted : BDI Application started .

Explanation Application started successfully

Recommended Action No action required.

Error Message
JavaApplications- 4 -BDIStopped : BDI Application stopped.

Explanation Application was unloaded from Tomcat

Recommended Action Check if Tomcat service is up.

Error Message
JavaApplications- 0 -BDINotStarted : BDI Application not started. Reason [String]

Explanation Error occurred while starting application

Recommended Action See application logs for error

Error Message
JavaApplications- 3 -BDIApplicationError : BDI Application error. Reason [String]

Explanation BDI application error

Recommended Action See application logs for details

Error Message
JavaApplications- 3 -BDIOverloaded : BDI Application overloaded. Reason [String]

Explanation BDI application overloaded

Recommended Action See application logs for details

Error Message
JavaApplications- 6 -WDStarted : WebDialer Application started . Servlet Name [String] Reason [String]

Explanation Application started successfully

Recommended Action No action required.

Error Message
JavaApplications- 4 -WDStopped : WebDialer Application stopped. Servlet Name [String] Reason [String]

Explanation Application was unloaded from Tomcat

Recommended Action Check if Tomcat service is up.

Error Message
JavaApplications- 0 -WDNotStarted : Failed to startup WebDialer application. Servlet Name [String] Reason [String]

Explanation Error occurred while starting application

Recommended Action See application logs for error

Error Message
JavaApplications- 3 -WDApplicationError : WebDialer Application error. Servlet Name [String] Reason [String]

Explanation WebDialer application error

Recommended Action See application logs for details

Error Message
JavaApplications- 3 -WDOverloaded : WebDialer Application overloaded. Servlet Name [String] Reason [String]

Explanation WebDialer application overloaded

Recommended Action See application logs for details

Error Message
JavaApplications- 6 -WDInformation : WebDialer informational alarm. Servlet Name [String] Reason [String]

Explanation WebDialer application informational alarm

Recommended Action No action required

Error Message
JavaApplications- 6 -CiscoDirSyncStarted : Cisco DirSync Application started .

Explanation Application started successfully

Recommended Action No action required.

Error Message
JavaApplications- 0 -CiscoDirSyncStartFailure : Cisco DirSymc application failed to start successfully.

Explanation Error occurred while starting application

Recommended Action See application logs for error, may require restarting the application

Error Message
JavaApplications- 6 -CiscoDirSyncProcessStarted : LDAPSync process started on particular sync agreement. AgreementId [String]

Explanation LDAPSync process started to sync user data on the configured agreement id

Recommended Action No action required

Error Message
JavaApplications- 2 -CiscoDirSyncProcessFailToStart : LDAPSync process failed to start on particular sync agreement. AgreementId [String]

Explanation LDAPSync process failed to start on the configured agreement id

Recommended Action See application logs for error

Error Message
JavaApplications- 6 -CiscoDirSyncProcessCompleted : LDAPSync process completed on particular sync agreement. AgreementId [String]

Explanation LDAPSync process completed to sync user data on the configured agreement id

Recommended Action No action required

Error Message
JavaApplications- 6 -CiscoDirSyncProcessStoppedManually : LDAPSync process stopped manually on particular sync agreement. AgreementId [String]

Explanation LDAPSync process stopped manually on the configured agreement id

Recommended Action No action required

Error Message
JavaApplications- 6 -CiscoDirSyncProcessStoppedAuto : LDAPSync process stopped automatically on particular sync agreement. AgreementId [String]

Explanation LDAPSync process stopped automatically on the configured agreement id, it will be restarted automatically

Recommended Action No action required

Error Message
JavaApplications- 3 -CiscoDirSyncProcessFailedRetry : LDAPSync process failed on particular sync agreement. AgreementId [String] Reason [String]

Explanation LDAPSync process failed to sync user data on the configured agreement id

Recommended Action No action required. The sync process will automatic retry See application logs for details

Error Message
JavaApplications- 3 -CiscoDirSyncProcessFailedNoRetry : LDAPSync process failed on particular sync agreement. AgreementId [String] Reason [String]

Explanation LDAPSync process failed to sync user data on the configured agreement id

Recommended Action See application logs for details, the application will try to sync again in the next scheduled time

Error Message
JavaApplications- 3 -CiscoDirSyncProcessConnectionFailed : LDAPSync process failed to connect to LDAP server. AgreementId [String] LDAPHost [String] Reason [String]

Explanation LDAPSync process failed to connect to LDAP host

Recommended Action Please make sure the LDAP server is online. If SSL is used, please make sure the required certificate is available on local CM server. The application will automatically retry

Error Message
JavaApplications- 3 -CiscoDirSyncDBAccessFailure : LDAPSync process failed to access local database. AgreementId [String] Reason [String]

Explanation CiscoDirSync failed to access local database

Recommended Action Please make sure the local CallManager database is working properly. The failed sync process will restart at the next scheduled time.

Error Message
JavaApplications- 6 -CiscoDirsyncZeroUsersSynced : LDAPSync process synced zero users for the sync agreement. AgreementId [String] Reason [String]

Explanation CiscoDirSync synced zero users

Recommended Action Check the application logs for details

Error Message
JavaApplications- 6 -UserUpdated : LDAPSync process found a user with the same userid synced from a different LDAP agreement. Updated the already existing user in the DB with the new user synced . AgreementId [String] Userid [String] Reason [String]

Explanation LDAPSync process found a user with the same userid synced from a different LDAP agreement. Updated the already existing user in the DB with the new user synced

Recommended Action No action required

Error Message
JavaApplications- 4 -DirSyncNoSchedulesFound : No schedules found in DB for directory synchronization. ScheduleTableName [String]

Explanation No automatic LDAP directory synchronization possible

Recommended Action Check the DirSync configuration

Error Message
JavaApplications- 6 -DirSyncScheduledTaskOver : Directory synchronization operation got over. SchedulerID [String] TaskID [String]

Explanation Information of the directory synchronization started

Recommended Action No action required

Error Message
JavaApplications- 4 -DirSyncScheduledTaskTimeoutOccured : Timeout occurred for directory synchronization task. SchedulerID [String] TaskID [String]

Explanation Timeout occurred for directory synchronization task

Recommended Action Check the DirSync configuration

Error Message
JavaApplications- 3 -DirSyncScheduledTaskFailed : Directory synchronization task failed. SchedulerID [String] ErrorMessage [String]

Explanation Directory synchronization task failed

Recommended Action Check the DirSync configuration and logs

Error Message
JavaApplications- 3 -DirSyncSchedulerFailedToGetDBSchedules : Failed to get directory synchronization schedules from DB. Message [String]

Explanation Failed to get directory synchronization schedules from DB

Recommended Action Check the DirSync configuration and logs

Error Message
JavaApplications- 3 -DirSyncSchedulerInvalidEventReceived : Invalid event received by DirSync scheduler from database. Action [String] Message [String]

Explanation Invalid event received by DirSync scheduler from database

Recommended Action Check the DirSync configuration and logs

Error Message
JavaApplications- 3 -DirSyncInvalidScheduleFound : Invalid schedule read by DirSync scheduler from database. ScheduleID [String]

Explanation Invalid schedule read by DirSync scheduler from database

Recommended Action Check the DirSync configuration and logs

Error Message
JavaApplications- 3 -DirSyncSchedulerFailedToRegisterDBEvents : DirSync scheduler failed to register DB notifications. ScheduleTable [String]

Explanation Invalid schedule read by DirSync scheduler from database

Recommended Action Check the DirSync configuration and logs

Error Message
JavaApplications- 3 -DirSyncSchedulerEngineFailedToStart : DirSync scheduler engine failed to start. ScheduleTable [String]

Explanation DirSync scheduler engine failed to start

Recommended Action Check the DirSync configuration and logs

Error Message
JavaApplications- 6 -DirSyncSchedulerEngineStopped : DirSync scheduler engine stopped. DirSyncSchedulerVersion [String]

Explanation DirSync scheduler engine stopped

Recommended Action No action required

Error Message
JavaApplications- 3 -DirSyncScheduleDeletionFailed : DirSync schedule deletion request failed. ScheduleID [String]

Explanation DirSync schedule deletion request failed

Recommended Action Check the DirSync configuration and logs

Error Message
JavaApplications- 6 -DirSyncNewScheduleInserted : New schedule inserted in the DirSync Scheduler Engine. ScheduleID [String]

Explanation New schedule inserted in the DirSync Scheduler Engine

Recommended Action No Action Required

Error Message
JavaApplications- 3 -DirSyncScheduleUpdateFailed : DirSync schedule update request failed. ScheduleID [String]

Explanation DirSync schedule deletion update failed

Recommended Action Check the DirSync configuration and logs

Error Message
JavaApplications- 3 -CiscoDRFDBAccessFailure : DRF process failed to access local database. Reason [String]

Explanation CiscoDirSync failed to access local database

Recommended Action Please make sure the local CallManager database is working properly. The failed sync process will restart at the next scheduled time.

Error Message
JavaApplications- 3 -CiscoDRFMasterAgentStartFailure : DRF Master Agent was not able to start. Reason [String]

Explanation DRF Master Agent might be down

Recommended Action Check if the Master Agent is running or port 4040 is in use.

Error Message
JavaApplications- 3 -CiscoDRFLocalAgentStartFailure : DRF Local Agent was not able to start. Reason [String]

Explanation DRF Local Agent might be down

Recommended Action Check if the Local Agent is running or port 4343 is in use.

Error Message
JavaApplications- 6 -CiscoDRFLA2MAFailure : DRF LA to MA connection has some problems.. Reason [String]

Explanation DRF LA to MA connection has some problems.

Recommended Action Check if the Master Agent is up and the port is authorized.

Error Message
JavaApplications- 6 -CiscoDRFMA2LAFailure : DRF MA to LA connection has some problems.. Reason [String]

Explanation DRF MA to LA connection has some problems.

Recommended Action Check if the Local Agent is up and the port is authorized.

Error Message
JavaApplications- 3 -CiscoDRFBackupFailure : DRF Backup process has some problems.. Reason [String]

Explanation DRF Backup process has some problems.

Recommended Action Check if the disk is full or tape is not online.

Error Message
JavaApplications- 3 -CiscoDRFRestoreFailure : DRF Restore process has some problems.. Reason [String]

Explanation DRF Restore process has some problems.

Recommended Action Check if the disk is full or tape is not online.

Error Message
JavaApplications- 4 -CiscoDRFUnknownMessage : DRF process has received an unknown message, and discard.. Reason [String]

Explanation DRF process has received an unknown message, and discard.

Recommended Action None.

Error Message
JavaApplications- 3 -CiscoDRFDeviceError : DRF process has the problem with device.. Reason [String]

Explanation DRF process has the problem with device.

Recommended Action Check if the proper device has been defined in the DB.

Error Message
JavaApplications- 3 -CiscoDRFInternalProcessFailure : DRF internal process has some problems.. Reason [String]

Explanation DRF internal process has some problems.

Recommended Action Check the reason, and restart Master Agent.

Error Message
JavaApplications- 6 -CiscoDRFHistory : DRF History Report.. Reason [String]

Explanation DRF History Report.

Recommended Action None.

Error Message
JavaApplications- 3 -CiscoDhcpdFailure : DHCP Daemon stop running.. Reason [String]

Explanation DHCP Daemon can't be brought up due to configuration error or crashed when it's running

Recommended Action Check application log for error message and correct the configuration. May require restarting the application if nothing found during the previous steps

Error Message
JavaApplications- 6 -CiscoDhcpdRestarted : DHCP Daemon restarted.. Reason [String]

Explanation DHCP Daemon restarted successfully.

Recommended Action None.

Error Message
JavaApplications- 3 -CiscoLicenseManagerDown : License Manager Down. Reason [String]

Explanation License Manager down - license provisioning will fail

Recommended Action Restart License Manager service on specified node

Error Message
JavaApplications- 1 -CiscoLicenseOverDraft : Overdraft licenses in use. Reason [String]

Explanation Overdraft licenses in use

Recommended Action None

Error Message
JavaApplications- 1 -CiscoLicenseApprochingLimit : License units consumption approaching its authorized limit. Reason [String]

Explanation License units consumption approaching its authorized limit

Recommended Action None

Error Message
JavaApplications- 3 -CiscoLicenseRequestFailed : License Request Unsuccessful. Reason [String]

Explanation License Manager cannot fulfill the license request

Recommended Action See application logs for error

Error Message
JavaApplications- 3 -CiscoLicenseDataStoreError : License Database error. Reason [String]

Explanation License application cannot fulfill the request - database error

Recommended Action See application logs for error

Error Message
JavaApplications- 3 -CiscoLicenseInternalError : Licensing Internal Error. Reason [String]

Explanation License application internal error

Recommended Action See application logs for error

Error Message
JavaApplications- 3 -CiscoLicenseFileError : License File Error. Reason [String]

Explanation Invalid or tampered license file

Recommended Action See application logs, verify that the license file is proper

Error Message
JavaApplications- 4 -CiscoElmNotConnected : The system has not synchronized successfully with Enterprise License Manager for many days.. Reason [String]

Explanation The system has not synchronized successfully to the Enterprise License Manager.

Recommended Action Check if Enterprise License Manager is connected to the product

Error Message
JavaApplications- 3 -CiscoNoProvisionTimeout : The system is operating with an insufficient number of licenses.. Reason [String]

Explanation The system is operating with an insufficient number of licenses.

Recommended Action Configure additional licenses in your Enterprise License Manager in order to restore the ability to provision users and devices. Check if Enterprise License Manager is connected to the product.

Error Message
JavaApplications- 6 -CiscoSystemTimeChange : System time has changed. Reason [String]

Explanation System Time has changed.

Recommended Action Check why the system time changed

Error Message
JavaApplications- 6 -CiscoGraceTimeLeft : Grace period countdown towards no provisioning allowed. Reason [String]

Explanation Grace period countdown towards no provisioning allowed.

Recommended Action Upload additional licenses. Check if Enterprise License Manager is connected to the product.

Error Message
JavaApplications- 4 -CiscoSystemInOverage : The system is operating with an insufficient number of licenses.. Reason [String]

Explanation The system is operating with an insufficient number of licenses. If additional licenses to cover the shortage are not configured in your Enterprise License Manager within a few days, you will no longer be able to provision users and devices.

Recommended Action Configure additional licenses in your Enterprise License Manager. Check if Enterprise License Manager is connected to the product.

Error Message
JavaApplications- 3 -CiscoSystemSecurityMismatch : Due to a certificate mismatch, the system has not synchronized successfully with Enterprise License Manager for many days.. Reason [String]

Explanation Certficate Mismatch between Cisco Unified Communications Manager and Enterprise License Manager

Recommended Action Verify Enterprise License Manager certificates. This could be a man-in-the-middle attack.

Error Message
JavaApplications- 4 -CiscoSystemInDemo : The system is operating on demo licenses that will expire soon.. Reason [String]

Explanation License files have not been uploaded on the Enterprise License Manager.

Recommended Action Upload license files on Enterprise License Manager. Check if Enterprise License Manager is connected to the product.

Error Message
JavaApplications- 6 -CiscoLicenseFileInvalid : License File Invalid. Reason [String]

Explanation Invalid license file due to MAC Address

Recommended Action License files need to be rehosted.

Error Message
JavaApplications- 6 -CiscoHardwareLicenseInvalid : Invalid / Obsolete Hardware. Cannot upload license files. . Reason [String]

Explanation Installation on invalid / obsolete hardware. Cannot upload license files.

Recommended Action Please obtain correct hardware and re-install.

Error Message
JavaApplications- 3 -DirSyncSchedulerFailedToUpdateNextExecTime : Scheduler failed to update next execution time. Message [String]

Explanation Scheduler failed to update next execution time

Recommended Action Check the DirSync configuration and logs

Error Message
JavaApplications- 6 -DirSyncScheduleInsertFailed : DirSync schedule insertion failed. ScheduleID [String]

Explanation DirSync schedule insertion failed

Recommended Action Check the DirSync configuration and logs

Error Message
JavaApplications- 6 -DirSyncSchedulerEngineStarted : DirSync scheduler engine started. DirSyncSchedulerVersion [String]

Explanation DirSync scheduler engine started

Recommended Action No action required

Error Message
JavaApplications- 3 -SendEmailAuthenticationError : Unable to autheticate to the SMTP server. Unable to autheticate SMTP [String] Reason [String]

Explanation Unable to autheticate to the SMTP server

Recommended Action See application logs for details

Error Message
JavaApplications- 3 -SendEmailNotificationError : Send Email error. Unable to reach SMTP [String] Reason [String]

Explanation Send Email error

Recommended Action See application logs for details

Error Message
JavaApplications- 3 -SendEmailNotificationUnknownError : Send Email error. Unable to send email [String] Reason [String]

Explanation Send Email error

Recommended Action See application logs for details

Error Message
JavaApplications- 4 -DuplicateUserHomeCluster : User has more than one cluster marked as their home cluster. User ID [String] Home Cluster [String]

Explanation User has more than one cluster marked as their home cluster

Recommended Action Select only one home cluster for a user

Error Message
LBMAlarmCatalog- 2 -LocationBandwidthManagerFailure : Indicates an internal failure in LBM. Additional Text [String] Host Name of Hosting Node [String] Host Node IP Address [String] Reason code [Enum]

Explanation This alarm indicates that an internal failure occurred in the Cisco Location Bandwidth Manager Service. The service should restart in an attempt to clear the failure.

Recommended Action Monitor for other alarms and restart Cisco Location Bandwidth Manager Service, if necessary. Collect the core file if available, SDL and CCM/SDI trace files (you can gather these from Trace and Log Central in RTMT using the Collect Files feature) and contact the Cisco Technical Assistance Center (TAC).

Reason code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Unknown - LBM has failed for an unknown reason
2 HeartBeatStopped - An internal heart beat has stopped after the preceding heart beat interval
3 RouterThreadDied - An internal thread has failed
4 TimerThreadDied - An internal thread has failed
5 CriticalThreadDied - An internal thread has failed
Error Message
LBMAlarmCatalog- 5 -LBMLinkISV : LBM link to remote application restored. Remote Application IP Address [String] Unique Link ID [String] Local Node ID [UInt] Local Application ID [Enum] Remote Application ID [Enum]

Explanation This alarm indicates that the LBM has gained communication with the remote LBM. Note that the remote LBM should also indicate LBMLinkISV.

Recommended Action Informational only; no action is required

Local Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
700 LocationBandwidthManager
Remote Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
700 LocationBandwidthManager
Error Message
LBMAlarmCatalog- 1 -LBMLinkOOS : LBM link to remote application is out of service. Remote Application IP Address [String] Unique Link ID [String] Local Node ID [UInt] Local Application ID [Enum] Remote Node ID [UInt] Remote Application ID [Enum]

Explanation This alarm indicates that the local LBM has lost communication with the remote LBM. This alarm usually indicates that a node has gone out of service (whether intentionally for maintenance or to install a new load for example; or unintentionally due to a service failure or connectivity failure).

Recommended Action In the Cisco Unified Reporting tool, run a CM Cluster Overview report and check to see if all servers can communicate with the Publisher. Also check for any alarms that might have indicated a CallManager OR location bandwidth manager failure and take appropriate action for the indicated failure. If the node was taken out of service intentionally, bring the node back into service.

Local Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
700 LocationBandwidthManager
Remote Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
700 LocationBandwidthManager
Error Message
LBMAlarmCatalog- 1 -LBMVersionMismatch : One or more Unified LBM nodes in a cluster are running different LBM versions. Remote Application Link Protocol Version [String] Local Application Link Protocol Version [String] Remote Node ID [UInt] Remote Application ID [Enum] Remote Application Version [String]

Explanation This alarm indicates that the local LBM is unable to establish communication with the remote LBM due to a software version mismatch. This is generally a normal occurrence when you are upgrading a LBM node.

Recommended Action The alarm details include the versions of the local and remote LBM nodes. Compare the versions and upgrade the node if necessary.

Remote Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
700 LocationBandwidthManager
Error Message
LBMAlarmCatalog- 4 -PrimaryHubUnreachable : Primary LBM Hub Node Unreachable.. LBM Hub Node [String]

Explanation This alarm indicates that the LBM spoke node was unable to connect to Primary LBM Hub Node configured in LBM Hub Group table. The LBM Node will attempt to connect to Secondary and Tertiary LBM Hub Node. If the condition is due to a temporary Network connectivity issue, the problem will self-repair. However, if it is due to a persistent condition, action must be taken.

Recommended Action Make sure that your firewall configuration is allowing the LBM Node to access the Primary LBM Hub node. If firewall configurations are correct, try pinging the configured IP address and port of the Primary LBM Hub Node, and diagnose any network issues from there. The IP address and port of the Primary LBM Hub Node that was tried by the LBM Node is included as name/value pair in the alarm.

Error Message
LBMAlarmCatalog- 4 -SecondaryHubUnreachable : Secondary LBM Hub Node Unreachable.. LBM Hub Node [String]

Explanation This alarm indicates that the LBM spoke node was unable to connect to Secondary LBM Hub Node configured in LBM Hub Group table. The LBM Node will attempt to connect back to Primary Hub Node.

Recommended Action No action is required on your part.

Error Message
LBMAlarmCatalog- 4 -TertiaryHubUnreachable : Tertiary LBM Hub Node Unreachable.. LBM Hub Node [String]

Explanation This alarm indicates that the LBM spoke node was unable to connect to Tertiary LBM Hub Node configured in LBM Hub Group table. The LBM Node will attempt to connect back to Primary Hub Node.

Recommended Action No action is required on your part.

Error Message
LBMAlarmCatalog- 2 -LBMHubUnreachable : LBM Hub Nodes Unreachable.. Primary Hub Node [String] Secondary Hub Nodes [String] Tertiary Hub Nodes [String]

Explanation This alarm indicates that the LBM spoke node was unable to connect to any of the LBM Hub Nodes configured in LBM Hub Group table. The LBM Spoke Node will periodically re-attempt to connect to the LBM Hub Nodes. If the condition is due to a temporary Network connectivity issue, the problem will self-repair. However, if it is due to a persistent condition, action must be taken.

Recommended Action Make sure that your firewall configuration is allowing the LBM Spoke Node to access the LBM Hub Nodes. If firewall configurations are correct, try pinging the configured IP addresses and ports of the LBM Hub Nodes, and diagnose any network issues from there. The IP addresses and ports of the LBM Hub Nodes that were tried by the LBM Spoke node are included as name/value pairs in the alarm.

Error Message
LBMAlarmCatalog- 4 -SuspiciousIPAddress : LBM has identified suspicious connection attempts from an IP address. Port Number [UInt] IP Address [String]

Explanation LBM has identified suspicious connection attempts from an IP address and has temporarily blocked the address. This alarm is an indication that a Denial-of-Service attack may have been attempted from this IP address.

Recommended Action Examine network activity for repeated attempts to access the port number specified in this alarm. Using the IP address specified in this alarm, attempt to identify the device that has been sending connection attempts to the port. If the IP address belongs to a device that is configured in IME, evaluate the possible reason for such numerous connection attempts. Generally, no device that is functioning properly will trigger this alarm. Reset the device or remove the device from the network.

Error Message
LBMAlarmCatalog- 2 -LBMServicePortFailedToOpen : LBM service port fails to be opened. Protocol [String] Port Number [UInt] Error Number [Int]

Explanation LBM socket port that is used to provide service fails to open.

Recommended Action Please check the LBM configuration to make sure that this port is not used by other applications. If this alarm occurs repeatly, collect the existing trace files and contact the Cisco Technical Assistance Center (TAC).

Error Message
LBMAlarmCatalog- 4 -LocationOutOfResource : All bandwidth allocated to the location/link is used up and no resources are available. Location or Link Name [String] Type of Resource that is unavailable [Enum]

Explanation The Location or Link connecting locations has run out of audio/video/immersive bandwidth and hence no further calls can originate or pass through the location/link. The out of resource condition may be temporary due to high number of calls during peak hours and may correct by itself when calls terminate and bandwidth is freed up.

Recommended Action Consider adding additional bandwidth to the location/link.

Type of Resource that is unavailable-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Audio bandwidth out of resource
2 Video bandwidth out of resource
3 Immersive bandwidth out of resource
Error Message
LBMAlarmCatalog- 3 -NoSuchLocation : A location name is unknown to the LBM service.. Location or Link Name [String] FullKey [String] Local Node ID [UInt] Local Application ID [Enum]

Explanation No such location exists or is recognized by LBM service.

Recommended Action Check whether the device supports assignment to the location (Shadow and Phantom are special). If the location is defined in a remote cluster, check the connectivity to that cluster ; check whether LBM services in the remote cluster are active; check LBM security mode mismatch between clusters; log off and log back in if this is an EMCC device.

Local Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
700 LocationBandwidthManager
Error Message
LBMAlarmCatalog- 3 -NoPathExists : A LBM service determined that no path exists between location 1 and location 2.. Location Name 1 [String] Location Name 2 [String] FullKey [String] Local Node ID [UInt] Local Application ID [Enum]

Explanation Location 1 and Location 2 are not connected.

Recommended Action Check whether the two locations are connected. If locations and/or links are defined in different clusters, check the connectivity to these clusters; check whether LBM services in all the affected remote clusters are active; check LBM security mode mismatch between clusters; log off and log back in if this is an EMCC device.

Local Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
700 LocationBandwidthManager
Error Message
LBMAlarmCatalog- 5 -LBMRemoteHubNoSecureConnectionAlarm : Lost LBM secure connection to remote LBM application. Remote Application IP Address [String] Local Node ID [UInt] Local Application ID [Enum] Remote Application ID [Enum]

Explanation This alarm indicates that the local LBM has lost secure communication with the remote LBM. This alarm usually indicates that a node has gone out of service (whether intentionally for maintenance or to install a new load for example; or unintentionally due to a service failure or connectivity failure); networking issues; or certificate issues.

Recommended Action In the Cisco Unified Reporting tool, run a CM Cluster Overview report and check to see if all servers can communicate with the Publisher. Also check for any alarms that might have indicated LBM failure and take appropriate action for the indicated failure. If the node was taken out of service intentionally, bring the node back into service.

Local Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
700 LocationBandwidthManager
Remote Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
700 LocationBandwidthManager
Error Message
LBMAlarmCatalog- 5 -LBMRemoteHubSecureConnectionRestoredAlarm : Restored LBM secure connection to remote LBM application. Remote Application IP Address [String] Local Node ID [UInt] Local Application ID [Enum] Remote Application ID [Enum]

Explanation This alarm indicates that the LBM has gained secure communication with the remote LBM. Note that the remote LBM should also indicate LBMRemoteHubSecureConnectionAlarm.

Recommended Action Informational only; no action is required

Local Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
700 LocationBandwidthManager
Remote Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
700 LocationBandwidthManager
Error Message
LBMAlarmCatalog- 5 -LBMRemoteHubNoInsecureConnectionAlarm : Lost LBM insecure connection to the remote LBM application. Remote Application IP Address [String] Local Node ID [UInt] Local Application ID [Enum] Remote Application ID [Enum]

Explanation This alarm indicates that the local LBM has lost insecure communication with the remote LBM. This alarm usually indicates that a node has gone out of service (whether intentionally for maintenance or to install a new load for example; or unintentionally due to a service failure or connectivity failure).

Recommended Action In the Cisco Unified Reporting tool, run a CM Cluster Overview report and check to see if all servers can communicate with the Publisher. Also check for any alarms that might have indicated LBM failure and take appropriate action for the indicated failure. If the node was taken out of service intentionally, bring the node back into service.

Local Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
700 LocationBandwidthManager
Remote Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
700 LocationBandwidthManager
Error Message
LBMAlarmCatalog- 5 -LBMRemoteHubInsecureConnectionRestoredAlarm : Restored LBM insecure connection to remote LBM. Remote Application IP Address [String] Local Node ID [UInt] Local Application ID [Enum] Remote Application ID [Enum]

Explanation This alarm indicates that the LBM has gained secure communication with the remote LBM. Note that the remote LBM should also indicate LBMRemoteHubSecureConnectionAlarm.

Recommended Action Informational only; no action is required

Local Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
700 LocationBandwidthManager
Remote Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
700 LocationBandwidthManager
Error Message
LBMAlarmCatalog- 3 -LBMRemoteHubNoConnectionAlarm : Lost LBM all connection to the remote LBM application. Remote Application IP Address [String] Local Node ID [UInt] Local Application ID [Enum] Remote Application ID [Enum]

Explanation This alarm indicates that the local LBM has lost all communications with the remote LBM. This alarm usually indicates that a node has gone out of service (whether intentionally for maintenance or to install a new load for example; or unintentionally due to a service failure or connectivity failure).

Recommended Action In the Cisco Unified Reporting tool, run a CM Cluster Overview report and check to see if all servers can communicate with the Publisher. Also check for any alarms that might have indicated LBM failure and take appropriate action for the indicated failure. If the node was taken out of service intentionally, bring the node back into service.

Local Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
700 LocationBandwidthManager
Remote Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
700 LocationBandwidthManager
Error Message
LBMAlarmCatalog- 5 -LBMRemoteHubConnectionRestoredAlarm : Restored LBM connection to remote LBM application. Remote Application IP Address [String] Local Node ID [UInt] Local Application ID [Enum] Remote Application ID [Enum]

Explanation This alarm indicates that the LBM has gained secure communication with the remote LBM. Note that the remote LBM should also indicate LBMRemoteHubSecureConnectionAlarm.

Recommended Action Informational only; no action is required

Local Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
700 LocationBandwidthManager
Remote Application ID-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
700 LocationBandwidthManager
Error Message
LdapClient- 6 -LC0000 : Starting preference change event dispatch thread.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapClient- 4 -LC0001 : Error occurred while performing an LDAP operation.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Review the debug log file. The debug log file will contain specific information about this error.

Error Message
LdapClient- 4 -LC0002 : The LDAP host name index %d is invalid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
LdapClient- 4 -LC0003 : Currently in recovery to [service] service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action LdapClient is trying to connect to the service. Check the log file after a small durtation. If LdapClient still can't connect to the service, restart the service.

Error Message
LdapClient- 6 -LC0004 : Auto recovery to [service] service is not enabled.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Restart the service, and/or restart the client application that is attempting to connect to the service.

Error Message
LdapClient- 6 -LC0006 : Gives index of LDAP server being used.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
LdapClient- 6 -LC0007 : Invalid Value.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
LdapClient- 6 -LC0009 : Failed to connect to LDAP service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
LdapClient- 6 -LC0010 : Insufficient access.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
LdapClient- 6 -LC0011 : Initialization of connection failed.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
LdapClient- 6 -LC0012 : Initialization of connection failed.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
LdapClient- 6 -LC0021 : Initialization of connection failed.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
LdapClient- 6 -LC0048 : File open failed.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
LdapClient- 6 -LC0069 : Internal Error. LCC needs to be set before calling this operation.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
LdapMonClient- 3 -LMS2000 : The LDAP replication check has failed. . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify both LDAP servers are running and able to communicate with each other.

Error Message
LdapMonClient- 3 -LMS2001 : The setup of the specified LDAP replication strategy failed. . Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
LdapMonClient- 4 -LMS3000 : The process could not be started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonClient- 4 -LMS3001 : The process has unexpectedly stopped running.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonClient- 4 -LMS3002 : Before starting the process, the setup step failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonClient- 6 -LMS0000 : The process has been successfully started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonClient- 6 -LMS0001 : The process has finished running.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonClient- 6 -LMS0002 : A request to configure replication has been received from another LdapMonitor Server in the cluster.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonClient- 6 -LMS0003 : A state update for a node in the cluster has been received from CVD.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonClient- 6 -LMS0004 : A new replication strategy has been successfully configured.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonSvrLib- 3 -LMS2000 : The LDAP replication check has failed. . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify both LDAP servers are running and able to communicate with each other.

Error Message
LdapMonSvrLib- 3 -LMS2001 : The setup of the specified LDAP replication strategy failed. . Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
LdapMonSvrLib- 4 -LMS3000 : The process could not be started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonSvrLib- 4 -LMS3001 : The process has unexpectedly stopped running.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonSvrLib- 4 -LMS3002 : Before starting the process, the setup step failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonSvrLib- 6 -LMS0000 : The process has been successfully started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonSvrLib- 6 -LMS0001 : The process has finished running.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonSvrLib- 6 -LMS0002 : A request to configure replication has been received from another LdapMonitor Server in the cluster.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonSvrLib- 6 -LMS0003 : A state update for a node in the cluster has been received from CVD.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonSvrLib- 6 -LMS0004 : A new replication strategy has been successfully configured.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonSvr- 3 -LMS2000 : The LDAP replication check has failed. . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify both LDAP servers are running and able to communicate with each other.

Error Message
LdapMonSvr- 3 -LMS2001 : The setup of the specified LDAP replication strategy failed. . Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
LdapMonSvr- 4 -LMS3000 : The process could not be started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonSvr- 4 -LMS3001 : The process has unexpectedly stopped running.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonSvr- 4 -LMS3002 : Before starting the process, the setup step failed. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonSvr- 6 -LMS0000 : The process has been successfully started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonSvr- 6 -LMS0001 : The process has finished running.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonSvr- 6 -LMS0002 : A request to configure replication has been received from another LdapMonitor Server in the cluster.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonSvr- 6 -LMS0003 : A state update for a node in the cluster has been received from CVD.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LdapMonSvr- 6 -LMS0004 : A new replication strategy has been successfully configured.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LoginAlarmCatalog- 4 -AuthenticationFailed : Login Authentication failed.. Login IP Address/Hostname [String] Login Date/Time [String] Login UserID [String] Login Interface [String]

Explanation Authentication failure for login attempt is detected.

Recommended Action If this event happens repeatedly, investigate the source of the failed login attempts.

Error Message
LoginAlarmCatalog- 6 -AuthenticationSucceeded : Login Authentication succeeded.. Login IP Address/Hostname [String] Login Date/Time [String] Login UserID [String] Login Interface [String]

Explanation Authentication success for login attempt is detected.

Recommended Action If this event is expected, no action is required; otherwise, notify the administrator.

Error Message
LpmTctCatalog- 4 -LogPartitionLowWaterMarkExceeded : The percentage of used disk space in the log partition has exceeded the configured low water mark.. UsedDiskSpace [String] MessageString [Optional]. [String]

Explanation The percentage of used disk space in the log partition has exceeded the configured low water mark.

Recommended Action Login into RTMT and check the configured threshold value for LogPartitionLowWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. Also, examine the trace and log file setting for each of the application in trace configuration page under CCM Serviceability. If the number of configured traces / logs is set to greater than 1000, adjust the trace settings from trace configuration page to default. Also, clean up the trace files that are less than a week old. You can clean up the traces using cli "file delete" or using Remote Browse from RTMT Trace and Log Central function.

Error Message
LpmTctCatalog- 2 -LogPartitionHighWaterMarkExceeded : The percentage of used disk space in the log partition has exceeded the configured high water mark.. UsedDiskSpace [String] MessageString [Optional]. [String]

Explanation The percentage of used disk space in the log partition has exceeded the configured high water mark. Some of the core file and / or trace files will be purged until the percentage of used disk space in the log partition gets below the configured low water mark.

Recommended Action Login into RTMT and check the configured threshold value for LogPartitionHighWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. If you continue to receive this alert for half an hour after receiving the 1st alert, check for the disk usage for Common partition under "Disk Usage" tab in RTMT. If the disk usage shown under that tab is higher than configured value in LogPartitionLowWaterMarkExceeded alert configuration, contact Cisco TAC to troubleshoot the cause of high disk usage in Common partition.

Error Message
LpmTctCatalog- 6 -LogFileSearchStringFound : The search string has been found in the log file.. SearchString [String]

Explanation Trace and Log Central has found the search string that the user has configured

Recommended Action If sysadmin is interested in collecting the traces around the time of generation of alert, use Trace and Log Central to collect the traces for that service.

Error Message
LpmTctCatalog- 4 -LogCollectionJobLimitExceeded : The number of Log Collection Jobs have excceded the allowed limit. JobType [String]

Explanation The number of concurrent trace collection from the server has exceeded the allowed limit of trace collection. The allowed limit is defined in the documentation for Trace and Log Central, however this limit can not be changed by sysadmin.

Recommended Action Cancel one or more of the currently running queries and try again to configure the trace collection.

Error Message
LpmTctCatalog- 3 -ScheduledCollectionError : An error occurred while executing scheduled collection.. JobID [String] Reason [String]

Explanation Scheduled collection encountered an error during execution.

Recommended Action Review configuration for scheduled collection job under Job Status window.

Error Message
LpmTctCatalog- 2 -CoreDumpFileFound : The new core dump file(s) have been found in the system.. TotalCoresFound [String] CoreDetails [String] Core1 [String] Core2 [String] Core3 [String] Core4 [String] Core5 [String] Core6 [String]

Explanation One of the component has crashed and generated a core dump. Use admin cli or RTMT to featch the backtrace.

Recommended Action This serious internal error should be investigated by the Cisco Technical Assistance Center (TAC). Before contacting TAC, Login to cli on CCM serve and run "active analyze core file name" to generate the backtrace of the core dump. The core file name is listed in the alert details. After the analyze command is executed, collect the backtrace using cli command "file get activelog analyze" or "Collect Traces" option from RTMT. Send these backtraces to Cisco TAC for further analysis.

Error Message
LpmTctCatalog- 3 -SparePartitionLowWaterMarkExceeded : The percentage of used disk space in the spare partition has exceeded the configured low water mark.. UsedDiskSpace [String] MessageString [Optional]. [String]

Explanation The percentage of used disk space in the spare partition has exceeded the configured low water mark.

Recommended Action Login into RTMT and check the configured threshold value for SparePartitionLowWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. Also, examine the trace and log file setting for each of the application in trace configuration page under CCM Serviceability. If the number of configured traces / logs is set to greater than 1000, adjust the trace settings from trace configuration page to default. Also, clean up the trace files that are less than a week old. You can clean up the traces using cli "file delete" or using Remote Browse from RTMT Trace and Log Central function.

Error Message
LpmTctCatalog- 4 -SparePartitionHighWaterMarkExceeded : The percentage of used disk space in the spare partition has exceeded the configured high water mark.. UsedDiskSpace [String] MessageString [Optional]. [String]

Explanation The percentage of used disk space in the spare partition has exceeded the configured high water mark. Some of the trace files will be purged until the percentage of used disk space in the spare partition gets below the configured low water mark

Recommended Action Login into RTMT and cheek the configured threshold value for SparePartitionHighWaterMarkExceeded alert in Alert Central. If the configured value is set to a lower than the default threshold value unintentionally, change the value to default. If you continue to receive this alert for half an hour after receiving the 1st alert, check for the disk usage for Spare partition under "Disk Usage" tab in RTMT. If the disk usage shown under that tab is higher than configured value in SparePartitionLowWaterMarkExceeded alert configuration, contact Cisco TAC to troubleshoot the cause of high disk usage in Common partition.

Error Message
LRMClient- 1 -LRMS1000 : The SocketService could not be started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended 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

Error Message
LRMClient- 3 -LRMS2000 : The LRM Service could not get a list of local hostnames.. Service Name [String] error Id [String] Message [String]

Explanation The LRM Service could not determine the local host addresses.

Recommended Action Check that the server's network connection is functioning correctly and that it has a valid Ip Address and Hostname.

Error Message
LRMClient- 3 -LRMS2001 : The LRM Client could not connect to any services.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the client is configured properly and that the lrm server is running..

Error Message
LRMClient- 4 -LRMS3000 : Information for the agent that logged in could not be found.. Function Name [String]

Explanation The LRM Service could not determine the local host addresses.

Recommended Action Check log for errors; this probably means that the agent logged out before login could complete.

Error Message
LRMClient- 6 -LRMS0000 : The socket service has been started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMClient- 6 -LRMS0001 : Socket Service has been stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMClient- 6 -LRMS0002 : The LRM Service has become active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMClient- 6 -LRMS0003 : The LRM Service has become inactive.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMClient- 6 -LRMS0004 : The LRM Client has connected to the specified service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMClient- 6 -LRMS0005 : The LRM Client has been disconnected from the specified service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the LRM Server is active and that the client recovers correctly.

Error Message
LRMCommon- 1 -LRMS1000 : The SocketService could not be started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended 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

Error Message
LRMCommon- 3 -LRMS2000 : The LRM Service could not get a list of local hostnames.. Service Name [String] error Id [String] Message [String]

Explanation The LRM Service could not determine the local host addresses.

Recommended Action Check that the server's network connection is functioning correctly and that it has a valid Ip Address and Hostname.

Error Message
LRMCommon- 3 -LRMS2001 : The LRM Client could not connect to any services.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the client is configured properly and that the lrm server is running..

Error Message
LRMCommon- 4 -LRMS3000 : Information for the agent that logged in could not be found.. Function Name [String]

Explanation The LRM Service could not determine the local host addresses.

Recommended Action Check log for errors; this probably means that the agent logged out before login could complete.

Error Message
LRMCommon- 6 -LRMS0000 : The socket service has been started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMCommon- 6 -LRMS0001 : Socket Service has been stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMCommon- 6 -LRMS0002 : The LRM Service has become active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMCommon- 6 -LRMS0003 : The LRM Service has become inactive.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMCommon- 6 -LRMS0004 : The LRM Client has connected to the specified service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMCommon- 6 -LRMS0005 : The LRM Client has been disconnected from the specified service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the LRM Server is active and that the client recovers correctly.

Error Message
LRMEvent- 1 -LRMS1000 : The SocketService could not be started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended 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

Error Message
LRMEvent- 3 -LRMS2000 : The LRM Service could not get a list of local hostnames.. Service Name [String] error Id [String] Message [String]

Explanation The LRM Service could not determine the local host addresses.

Recommended Action Check that the server's network connection is functioning correctly and that it has a valid Ip Address and Hostname.

Error Message
LRMEvent- 3 -LRMS2001 : The LRM Client could not connect to any services.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the client is configured properly and that the lrm server is running..

Error Message
LRMEvent- 4 -LRMS3000 : Information for the agent that logged in could not be found.. Function Name [String]

Explanation The LRM Service could not determine the local host addresses.

Recommended Action Check log for errors; this probably means that the agent logged out before login could complete.

Error Message
LRMEvent- 6 -LRMS0000 : The socket service has been started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMEvent- 6 -LRMS0001 : Socket Service has been stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMEvent- 6 -LRMS0002 : The LRM Service has become active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMEvent- 6 -LRMS0003 : The LRM Service has become inactive.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMEvent- 6 -LRMS0004 : The LRM Client has connected to the specified service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMEvent- 6 -LRMS0005 : The LRM Client has been disconnected from the specified service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the LRM Server is active and that the client recovers correctly.

Error Message
LRMServer- 1 -LRMS1000 : The SocketService could not be started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended 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

Error Message
LRMServer- 3 -LRMS2000 : The LRM Service could not get a list of local hostnames.. Service Name [String] error Id [String] Message [String]

Explanation The LRM Service could not determine the local host addresses.

Recommended Action Check that the server's network connection is functioning correctly and that it has a valid Ip Address and Hostname.

Error Message
LRMServer- 3 -LRMS2001 : The LRM Client could not connect to any services.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the client is configured properly and that the lrm server is running..

Error Message
LRMServer- 4 -LRMS3000 : Information for the agent that logged in could not be found.. Function Name [String]

Explanation The LRM Service could not determine the local host addresses.

Recommended Action Check log for errors; this probably means that the agent logged out before login could complete.

Error Message
LRMServer- 6 -LRMS0000 : The socket service has been started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMServer- 6 -LRMS0001 : Socket Service has been stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMServer- 6 -LRMS0002 : The LRM Service has become active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMServer- 6 -LRMS0003 : The LRM Service has become inactive.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMServer- 6 -LRMS0004 : The LRM Client has connected to the specified service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMServer- 6 -LRMS0005 : The LRM Client has been disconnected from the specified service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the LRM Server is active and that the client recovers correctly.

Error Message
LRMStress- 1 -LRMS1000 : The SocketService could not be started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended 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

Error Message
LRMStress- 3 -LRMS2000 : The LRM Service could not get a list of local hostnames.. Service Name [String] error Id [String] Message [String]

Explanation The LRM Service could not determine the local host addresses.

Recommended Action Check that the server's network connection is functioning correctly and that it has a valid Ip Address and Hostname.

Error Message
LRMStress- 3 -LRMS2001 : The LRM Client could not connect to any services.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the client is configured properly and that the lrm server is running..

Error Message
LRMStress- 4 -LRMS3000 : Information for the agent that logged in could not be found.. Function Name [String]

Explanation The LRM Service could not determine the local host addresses.

Recommended Action Check log for errors; this probably means that the agent logged out before login could complete.

Error Message
LRMStress- 6 -LRMS0000 : The socket service has been started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMStress- 6 -LRMS0001 : Socket Service has been stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMStress- 6 -LRMS0002 : The LRM Service has become active.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMStress- 6 -LRMS0003 : The LRM Service has become inactive.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMStress- 6 -LRMS0004 : The LRM Client has connected to the specified service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
LRMStress- 6 -LRMS0005 : The LRM Client has been disconnected from the specified service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check that the LRM Server is active and that the client recovers correctly.

Error Message
MADM-ADM_CFG- 3 -ADM_EXCEPTION : Unknown ADM Exception. Exception [String]

Explanation Unknown ADM Exception

Recommended Action Verify and update the configuration

Error Message
MADM-ADM_SRV- 3 -ADM_EXCEPTION : Unknown ADM Exception. Exception [String]

Explanation Unknown ADM Exception

Recommended Action Verify and update the configuration

Error Message
MADM-ADM_TEL- 3 -ADM_EXCEPTION : Unknown ADM Exception. Exception [String]

Explanation Unknown ADM Exception

Recommended Action Verify and update the configuration

Error Message
MADM-ADM_CFG- 3 -ADM_EXCEPTION : Unknown ADM Exception. Exception [String]

Explanation Unknown ADM Exception

Recommended Action Verify and update the configuration

Error Message
MADM-BOOTSTRAP_MGR- 1 -MGR_PARTIAL_SERVICE : Bootstrap Manager in partial service.

Explanation The Bootstrap Manager is in partial service

Recommended Action Investigate as required

Error Message
MADM-BOOTSTRAP_MGR- 3 -BOOTSTRAP_NODE_JOIN_ERROR : Failed to sync bootstrap repository during node join. A description for the nature of the exception [String] Exception [String]

Explanation Failed to sync bootstrap repository during node join

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-BOOTSTRAP_MGR- 3 -BOOTSTRAP_SYNC_ERROR : Synchronize bootstrap repository error. A description for the nature of the exception [String] Exception [String]

Explanation Failed to synchronize the bootstrap repository between nodes

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-BOOTSTRAP_MGR- 3 -BOOTSTRAP_REMOVE_LISTENER_ERROR : Failed to remove the BootstrapListener. A description for the nature of the exception [String] Exception [String]

Explanation Failed to remove the BootstrapListener

Recommended Action Restart server

Error Message
MADM-BOOTSTRAP_MGR- 6 -MGR_IN_SERVICE : Bootstrap Manager in service.

Explanation The Bootstrap Manager is in service

Recommended Action No actions needed

Error Message
MADM-BOOTSTRAP_MGR- 3 -BOOTSTRAP_ADD_LISTENER_ERROR : Failed to add the BootstrapListener. A description for the nature of the exception [String] Exception [String]

Explanation Failed to add the BootstrapListener

Recommended Action Restart server

Error Message
MADM-BOOTSTRAP_MGR- 3 -BOOTSTRAP_INIT_ERROR : Bootstrap Manager initialization error. A description for the nature of the exception [String] Exception [String]

Explanation The Bootstrap Manager has failed on initialzation

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-BOOTSTRAP_MGR- 5 -MGR_SHUTDOWN : Bootstrap Manager in shutdown.

Explanation The Bootstrap Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MADM-BOOTSTRAP_MGR- 3 -BOOTSTRAP_NODE_REMOVE_ERROR : Bootstrap failed to remove node from cluster profile. A description for the nature of the exception [String] Exception [String]

Explanation Bootstrap failed to remove node from cluster profile

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-BOOTSTRAP_MGR- 6 -MGR_INITIALIZING : Bootstrap Manager initializing.

Explanation The Bootstrap Manager is initializing

Recommended Action No actions needed

Error Message
MADM-BOOTSTRAP_MGR- 2 -MGR_OUT_OF_SERVICE : Bootstrap Manager in out of service.

Explanation The Bootstrap Manager is out of service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-BOOTSTRAP_MGR- 5 -MGR_SHUTTING_DOWN : Bootstrap Manager shutting down.

Explanation The Bootstrap Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MADM-BOOTSTRAP_MGR- 3 -BOOTSTRAP_NODE_ADD_ERROR : Bootstrap failed to add new node to cluster profile. A description for the nature of the exception [String] Exception [String]

Explanation Bootstrap failed to add new node to cluster profile

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CFG_MGR- 3 -REPOSITORY_ACCESSOR_INIT_ERROR : Failed to initialize the accessor. Name [String]

Explanation Error in initializing repository accessor

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 1 -MGR_PARTIAL_SERVICE : Config Manager in partial service. Reason [String]

Explanation The Config Manager is in partial service due to CDS not yet activated or failed to register RMI for notification

Recommended Action Please check whether CDS is activated in the clusteror CVD to regsiter RMI for notification

Error Message
MADM-CFG_MGR- 3 -DB_ACCESS_ERROR : Database Access error. Action [String] Table [String] Exception [String]

Explanation Error while accessing Data Base

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 3 -BULK_UPDATE_ERROR : Error in Bulk update. action [String] Exception [String]

Explanation Error in bulk update

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 6 -STUB_HASCHANGED : ConfigStubImpl hasChanged(). Exception [String]

Explanation information

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 3 -SAVE_FAILED : saving failed . Exception [String]

Explanation ConfigObject saving failed

Recommended Action ConfigObject saving failed

Error Message
MADM-CFG_MGR- 6 -CONFIG_SCHEMA_CHANGE : ConfigSchema change. Schema_Ver [String]

Explanation Change in ConfigSchema

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 3 -CLUSTER_INFO_PORT_SAVE_ERR : Error in updating Bootstrap ini file. value [String] Exception [String]

Explanation Error in updating Bootstrap ini file with RMI port

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 3 -CLUSTER_INFO_HOST_SAVE_ERR : Error in updating Bootstrap ini file. Exception [String]

Explanation Error in updating Bootstrap ini file with local host ip

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 3 -GET_ACCESSOR_ERR : Error in finding repository accessors. Name [String] Exception [String]

Explanation Error in finding repository accessors information

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 6 -SCHEMA_EXISTS : ConfigSchema Register failed. Exception [String]

Explanation information

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 6 -MGR_INITIALIZING : Config Manager initializing.

Explanation The Config Manager is initializing

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 5 -MGR_SHUTTING_DOWN : Config Manager shutting down.

Explanation The Config Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 2 -MGR_OUT_OF_SERVICE : Config Manager in out of service.

Explanation The Config Manager is out of service; configuration will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CFG_MGR- 6 -NO_BASERECORD : No base record.

Explanation No base record for this config object

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 3 -LOCAL_AND_REMOTE_PROPERTIES_HAVE_DIFFERENT_VERSIONS : Local and remote properties have different versions. Properties name [String] Remote properties version [String] Local properties version [String] Merge result [String]

Explanation The properties being merged are of different versions

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-CFG_MGR- 3 -CONFIG_SCHEMAS_LOAD_ERROR : Interrupted while loading configschemas. Name [String] Exception [String]

Explanation Error in loading config schemas

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 3 -READ_REAPOSIOTRY_ACCCESSORS : Error in reading repository accessors from applciation properties. Name [String] Exception [String]

Explanation Error in reading repository accessors information from applciation properties

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 6 -MGR_IN_SERVICE : Config Manager in service.

Explanation The Config Manager is in service

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 3 -CONFIG_MGR_GET_REMOTEPROP_ERROR : Config Manager get remote properties failed. Properties name [String] Exception [String]

Explanation Config Manager get remote properties failed

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-CFG_MGR- 3 -CONFIG_OBJECT_SAVE_FAIL : saving failed due to missing values for keys defined in configSchema. configObejct [String] Reason [String] Exception [String]

Explanation saving failed due to missing values for keys defined in configSchema

Recommended Action Check the values for keys defined in the configSchema

Error Message
MADM-CFG_MGR- 5 -MGR_SHUTDOWN : Config Manager in shutdown.

Explanation The Config Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 3 -PARSE_ERROR : Error in converiting data. ToBeParsed [String] Table [String] Exception [String]

Explanation Error in parsing

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 3 -PROFILE_INFO_ACCESS_ERR : Error in accessing profile ini file. Exception [String]

Explanation Error in accessing profile ini file

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 2 -CFG_MGR_INSTANCE_NULL : Config Manager instance is null.

Explanation The Config Manager instance is null; configuration will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CFG_MGR- 3 -CLUSTER_DOWN_ERROR : Cluster Manager is not initialized. Description [String] Exception [String]

Explanation Cluster Manager is not initialized

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-CFG_MGR- 3 -DELETE_ERROR : Delete failed. Exception [String]

Explanation ConfigObjects deletion for this query failed

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 3 -INVALID_REPOSITORY_ACCESSOR : Repository accessor is invalid. Exception [String]

Explanation Repository accessor is invalid

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 3 -READ_ERROR : object read error. Exception [String]

Explanation Error in reading

Recommended Action Error in reading

Error Message
MADM-CFG_MGR- 3 -CONFIG_OBJECT_CORRUPTED : Error while reading config. Probably it was corrupt. Config Class [String] Exception [String]

Explanation Error while reading the blob data of the config

Recommended Action Run the CLI command 'show uccx tech dbserver integrity' to check and recover from any corrupted config objects

Error Message
MADM-CFG_MGR- 3 -CONFIG_MGR_GENERAL_ERROR : Config Manager has exception. Error message [String] Exception [String]

Explanation Config Manager has exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-CFG_MGR- 3 -CLUSTER_RMI_REBIND_FAILED : Unable to register remote interface in cluster space. Exception [String]

Explanation A remote interface could not be binded to the cluster space; Config data may not be accessible form Editor

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CFG_MGR- 6 -NO_DB_RECORD : No record in DB.

Explanation No record in DB

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 3 -NOTIFICATION_ERROR : Failed to notify other remote config managers. Action [String] Exception [String]

Explanation Error in notifying other remote config managers

Recommended Action No actions needed

Error Message
MADM-CFG_MGR- 2 -CONFIG_MGR_OUT_OF_SERVICE : Config Manager in out of service. Exception [String]

Explanation The Config Manager is out of service; configuration will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CLUSTER_MGR- 3 -MANAGER_INITIALIZING_ERROR : Cluster Manager is not initialized. Exception [String]

Explanation Cluster Manager is not initialized

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CLUSTER_MGR- 4 -REMOTE_EXCEPTION_1 : Can not communicate with CVD. errCnt [Int] Cmd [String] Exception [String]

Explanation Cluster Manager can not communicate with CVD on the local node

Recommended Action No actions needed

Error Message
MADM-CLUSTER_MGR- 3 -REMOTE_EXCEPTION_2 : Can not communicate with CVD. errCnt [Int] Exception [String]

Explanation Cluster Manager can not communicate with CVD on the local node

Recommended Action No actions needed

Error Message
MADM-CLUSTER_MGR- 3 -LICENSE_OBSERVER_ERROR : Cluster Manager can not register license observer. Exception [String]

Explanation Cluster Manager can not register license observer

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CLUSTER_MGR- 2 -RESTART_REQUESTED : Cluster Manager requests to restart process. reason [String]

Explanation Cluster Manager detects some problem that prevents its functionality, and requests restart

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-CLUSTER_MGR- 3 -COMPONENT_PRIMARY_CHANGED_ERROR : Component change primary, but it is not supported. type [String] nodeId [Int]

Explanation Component change primary, but it is not supported

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-CLUSTER_MGR- 3 -COMPONENT_CLEAR_PRIMARY_NOT_SUPPORTED : Clear Primary operation is not supported for the Component. type [String] nodeId [Int]

Explanation Clear Primary operation is not supported for the Component

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-CLUSTER_MGR- 6 -MANAGER_INITIALIZING_COMPLETED : Cluster Manager initialization successfully completed.

Explanation Cluster Manager initialization successfully completed

Recommended Action No actions needed

Error Message
MADM-CLUSTER_MGR- 3 -READ_ERROR_CLUSTER_NAME : Cannot read cluster name. Exception [String]

Explanation Cannot read cluster name from ccndir.ini

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CLUSTER_MGR- 3 -GET_PUBLISHER_TIMEOUT_ERROR : Cluster Manager can not get Timeout value from Windows Registry. Exception [String]

Explanation Cluster Manager can not get Timeout value from Windows Registry. Use default timeout: 2 hours

Recommended Action No actions needed

Error Message
MADM-CLUSTER_MGR- 3 -MASTER_SERVICE_NOT_FOUND : Master service not found. UniqueId [Int] nodeId [Int] Cmd [String]

Explanation Master service not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CLUSTER_MGR- 3 -ILLEGAL_CLUSTER_NAME : Cluster name is illegal. name [String]

Explanation Cluster name is illegal

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CLUSTER_MGR- 3 -CONVERGENCE_NOT_FOUND_ERROR : Convergence not found. name [String]

Explanation Convergence not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CLUSTER_MGR- 3 -GET_NODE_UPDATE_ERRORR : Can not communicate with CVD. Exception [String]

Explanation Cluster Manager can not communicate with CVD on the local node

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-CLUSTER_MGR- 3 -NODE_NOT_FOUND_FOR_CMD : Cluster Manager dispatcher can not process cmd: unknown Node. Cmd [String]

Explanation Cluster Manager dispatcher can not process cmd: unknown Node

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CLUSTER_MGR- 4 -COMPONENT_ALREADY_PRIMARY : Component is already primary. type [String] nodeId [Int]

Explanation Component is already primary

Recommended Action No actions needed

Error Message
MADM-CLUSTER_MGR- 4 -MASTER_UPDATE_ERROR : Cluster Manager can not update master. nodeId [Int] Cmd [String]

Explanation Cluster Manager can not update master, it try to re-sync all states with CVD on the local Node

Recommended Action No actions needed

Error Message
MADM-CLUSTER_MGR- 3 -SET_VMOPTION_ERROR : Cluster Manager can not execute SetVMOption. Exception [String]

Explanation Cluster Manager can not execute SetVMOption

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CLUSTER_MGR- 3 -SERVICE_ID_NOT_FOUND_ERROR : Service not found. UniqueId [Int] nodeId [Int] Cmd [String]

Explanation Service not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CLUSTER_MGR- 3 -COMPONENT_CLEAR_PRIMARY_ERROR : Clear Primary operation is not applicable to non-primary Component. type [String] nodeId [Int]

Explanation Clear Primary operation is not applicable to non-primary Component

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-CLUSTER_MGR- 3 -NODE_UPDATE_ERROR : Cluster Manager can not update node from command. nodeId [Int] Cmd [String]

Explanation Cluster Manager can not update node from command

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CLUSTER_MGR- 3 -COMPONENT_ID_NOT_FOUND_ERROR : Component not found. UniqueId [Int] nodeId [Int] Cmd [String]

Explanation Component not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CLUSTER_MGR- 3 -REMOTE_NOTIFY_1 : Can not communicate with CVD. Context [String] Cmd [String] Exception [String]

Explanation Cluster Manager can not communicate with CVD on the local node

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-CLUSTER_MGR- 6 -COMPONENT_PRIMARY_REMOVED : Component is removed, but it is primary. type [String] nodeId [Int]

Explanation Component is removed, but it is primary

Recommended Action No actions needed

Error Message
MADM-CLUSTER_MGR- 3 -CLUSTER_SNAPSHOT_ON_ERROR : Cluster snapshot when error. cluster [String]

Explanation Cluster snapshot when error

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-CLUSTER_MGR- 3 -READ_CLUSTER_ERROR : Cluster Manager can not read Cluster data from ClusterSnapshotCmdImpl. Exception [String]

Explanation Cluster Manager can not read Cluster data from ClusterSnapshotCmdImpl

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CLUSTER_MGR- 3 -COMPONENT_SET_PRIMARY_NOT_SUPPORTED : Set Primary operation is not supported for the Component. type [String] nodeId [Int]

Explanation Set Primary operation is not supported for the Component

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-CLUSTER_MGR- 3 -NODE_READ_ERROR : Cluster Manager can not read node from command. Cmd [String] Exception [String]

Explanation Cluster Manager can not read node from command

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CLUSTER_MGR- 0 -JMS_BROKER_SERVICE_START_ERROR : A KeepAlive exception has been thrown in Manager Manager. Exception [String]

Explanation Due to JMS service start failure a KeepAlive exception has been thrown in Cluster Manager

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-CLUSTER_MGR- 2 -MASTER_ELECTION_ERROR : Master Election Error - too many masters. Context [String] name [String] nodeId [Int] otherNodeId [Int] reason [String]

Explanation Master Election Error - too many masters. Cluster Manager restart process

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CLUSTER_MGR- 3 -MEMORY_DUMP_ERROR : Cluster Manager can not execute Memory Dump. Exception [String]

Explanation Cluster Manager can not execute Memory Dump

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CLUSTER_MGR- 3 -SEMAPHORE_NOT_FOUND_ERROR : Cluster Manager can not find semaphore. Cmd [String]

Explanation Cluster Manager can not find semaphore

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-CLUSTER_MGR- 4 -NODE_INVALID : Node Is invalid. nodeId [Int] reason [String]

Explanation Node Is invalid, it should be recovered from Installer

Recommended Action Reinstall server

Error Message
MADM-CLUSTER_MGR- 3 -NODE_SYNCHRONIZE_STATE_ERROR : Cluster Manager can not synchronize state for node. nodeId [Int]

Explanation Cluster Manager can not synchronize state for node, and will be restarted.

Recommended Action No actions needed

Error Message
MADM-CLUSTER_MGR- 3 -ACCESS_CONFIG_DATA_ERROR : Cluster Manager can not access configuration data. Exception [String]

Explanation Cluster Manager can not access configuration data

Recommended Action Verify that Configuration data is available. If problem persist contact Cisco technical assistance center

Error Message
MADM-CLUSTER_MGR- 4 -DYNAMIC_LICENSE_NOT_DEFINED : Dynamic license is not defined.

Explanation Dynamic license is not defined

Recommended Action No actions needed

Error Message
MADM-CLUSTER_MGR- 2 -THROWS_KEEP_ALIVE_EXCEPTION : Cluster Manager throws KeepAlive Exception. Exception [String]

Explanation Cluster Manager detects some problem that prevents its functionality, and will be restarted

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-CLUSTER_MGR- 3 -MANAGER_DISPATCH_ERROR : Can not process command. Cmd [String] Exception [String]

Explanation Cluster Manager can not process command from CVD

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-DB_MGR- 1 -MGR_PARTIAL_SERVICE : Database Manager in partial service.

Explanation The Database Manager is in partial service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-DB_MGR- 6 -DATASOURCE_STATE : state change. change [String]

Explanation state change

Recommended Action No actions needed

Error Message
MADM-DB_MGR- 6 -MGR_IN_SERVICE : Database Manager in service.

Explanation The Database Manager is in service

Recommended Action No actions needed

Error Message
MADM-DB_MGR- 5 -MGR_SHUTDOWN : Database Manager in shutdown.

Explanation The Database Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MADM-DB_MGR- 3 -DATASOURCE_INIT_ERROR : Failed to db server. Type [String] Exception [String]

Explanation Failed to initialize the db server

Recommended Action Please check db server

Error Message
MADM-DB_MGR- 3 -UPDATE_CLUSTERDEPENDENTCONFIG_FAILED : Failed to update DBVersion in ClusterDependentConfig . Exception [String]

Explanation Failed to update DBVersion in ClusterDependentConfig

Recommended Action No actions needed

Error Message
MADM-DB_MGR- 3 -DS_PRIMARY_READ_ERROR : Failed to read Datasource primary. Type [String] Exception [String]

Explanation Failed to read Datasource primary from cluster profile

Recommended Action Please check cluser profile info

Error Message
MADM-DB_MGR- 3 -CREATE_SERVICE_CONVERGENCE_FAILED : Failed to create convergence service . Name [String]

Explanation Failed to create convergence service

Recommended Action Please check cluster manager

Error Message
MADM-DB_MGR- 3 -SQL_PROPERTIES_READ_ERR : Error in reading SQL properties from cluster info. Exception [String]

Explanation Error in reading SQL properties such as SQL instance name , port

Recommended Action Check DB components are configured

Error Message
MADM-DB_MGR- 6 -MGR_INITIALIZING : Database Manager initializing.

Explanation The Database Manager is initializing

Recommended Action No actions needed

Error Message
MADM-DB_MGR- 2 -MGR_OUT_OF_SERVICE : Database Manager in out of service.

Explanation The Database Manager is out of service;

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-DB_MGR- 5 -MGR_SHUTTING_DOWN : Database Manager shutting down.

Explanation The Database Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MADM-DB_MGR- 6 -NO_CLUSTER_MGR : No cluster Manager.

Explanation There is no cluster Manager running

Recommended Action No actions needed

Error Message
MADM-DB_MGR- 3 -ERROR_JDBC_DRVER_LOAD : Error in loading jTDS Driver. Exception [String]

Explanation Error in loading jTDS Driver

Recommended Action Check whether driver is avaialble

Error Message
MADM-DOC_MGR- 1 -UNAUTHORISED_ACCESS : Unauthorised access. Name [String] Exception [String]

Explanation The Document Manager found that requested resource is not a legitimate one

Recommended Action Investigate as required

Error Message
MADM-DOC_MGR- 1 -MGR_PARTIAL_SERVICE : Document Manager in partial service.

Explanation The Document Manager is in partial service; synchronization of files with document repository is in progress

Recommended Action No actions needed

Error Message
MADM-DOC_MGR- 3 -UNABLE_LOAD_USER_DOC : Unable to load the user document file. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to load the specified user document file

Recommended Action Verify and update the configuration

Error Message
MADM-DOC_MGR- 6 -MGR_IN_SERVICE : Document Manager in service.

Explanation The Document Manager is in service

Recommended Action No actions needed

Error Message
MADM-DOC_MGR- 2 -INVALID_USER_DIR : Invalid user document directory configured. Directory [String] Exception [String]

Explanation The configured user document directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-DOC_MGR- 2 -WEBAPP_INIT_FAILURE : Unable to initialize the specified web application. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to initialize the specified web applicaton; it will not be available to HTTP-triggered applications

Recommended Action Verify and update the configuration and restart server

Error Message
MADM-DOC_MGR- 6 -NO_WEBAPPS_APPS : Webapps directory is empty.

Explanation No apps in the webapps directory of the repository to process

Recommended Action No actions needed

Error Message
MADM-DOC_MGR- 6 -NO_WEBAPPS : Webapps directory not found.

Explanation No webapps directory in the repository to process

Recommended Action No actions needed

Error Message
MADM-DOC_MGR- 3 -UNDEFINED_USER_DOC : Undefined user document. Name [String] Language [String] Exception [String]

Explanation A user document cannot be located

Recommended Action Verify and update the configuration

Error Message
MADM-DOC_MGR- 5 -MGR_SHUTDOWN : Document Manager in shutdown.

Explanation The Document Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MADM-DOC_MGR- 1 -WEBAPPS_MONITOR_FAILURE : Webapps directory monitoring failure. Exception [String]

Explanation The Document Manager can no longer monitor dynamic updates to the webapps directory of the repository; updates to war files will require restarting the local Unified CCX Engine Service

Recommended Action Investigate as required

Error Message
MADM-DOC_MGR- 3 -DOC_FILE_SUPPORT_FAILURE : Document file support failure. Exception [String]

Explanation The Document Manager can not register file support for user document files; user documents will not be synchronized on local server

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-DOC_MGR- 3 -UNDEFINED_SYSTEM_DOC : Undefined system document. Name [String] Language [String] Exception [String]

Explanation A system document cannot be located

Recommended Action Verify and update the configuration

Error Message
MADM-DOC_MGR- 3 -UNABLE_LOAD_SYSTEM_DOC : Unable to load the system document file. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to load the specified system document file

Recommended Action Verify and update the configuration

Error Message
MADM-DOC_MGR- 2 -WAR_EXPAND_FAILURE : Unable to expand the specified war file. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to expand the specified war file; the corresponding web application will not be available to HTTP-triggered applications

Recommended Action Verify and update the configuration and restart server

Error Message
MADM-DOC_MGR- 3 -WEBAPP_REMOVE_FAILURE : Unable to remove the specified web application. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to remove the specified web applicaton

Recommended Action Verify and update the configuration and restart server

Error Message
MADM-DOC_MGR- 6 -MGR_INITIALIZING : Document Manager initializing.

Explanation The Document Manager is initializing

Recommended Action No actions needed

Error Message
MADM-DOC_MGR- 2 -MGR_OUT_OF_SERVICE : Document Manager in out of service.

Explanation The Document Manager is out of service; documents won't be accessible

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-DOC_MGR- 5 -MGR_SHUTTING_DOWN : Document Manager shutting down.

Explanation The Document Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MADM-DOC_MGR- 3 -WEBSERVICES_ERROR : Exception thrown while processing web services for Document. Exception [String]

Explanation The Document Manager is unable to initialize the web services; external access to the document repository will not be possible andsupport for forwarding HTTP requests will also not be supported

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-DOC_MGR- 2 -INVALID_SYSTEM_DIR : Invalid system document directory configured. Directory [String] Exception [String]

Explanation The configured system document directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-EXECUTOR_MGR- 1 -MGR_PARTIAL_SERVICE : Executor Manager in partial service.

Explanation The Executor Manager is in partial service; thread priorities will not be properly set

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-EXECUTOR_MGR- 4 -INVALID_THREAD_PRIORITY_CHANGE : Invalid thread priority change. Facility [String] Sub-Facility [String] Executor id [String] Thread [String] Thread priority [Int] Original thread priority [Int]

Explanation The specified thread had an unsupported priority changed; user's code should not attempt to manually change the priority of threads for whatever reasons

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-EXECUTOR_MGR- 6 -MGR_INITIALIZING : Executor Manager initializing.

Explanation The Executor Manager is initializing

Recommended Action No actions needed

Error Message
MADM-EXECUTOR_MGR- 5 -MGR_SHUTTING_DOWN : Executor Manager shutting down.

Explanation The Executor Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MADM-EXECUTOR_MGR- 2 -MGR_OUT_OF_SERVICE : Executor Manager in out of service.

Explanation The Executor Manager is out of service; executors won't be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-EXECUTOR_MGR- 4 -CMD_BLOCKED : Invoking blocked execution handler. Facility [String] Sub-Facility [String] Executor id [String] Mnemonic [String] Thread [String] Thread priority [Int] Time [Long] Handler [String]

Explanation The specified blocked execution handler is being invoked for the specified command as the executor queue could not accept it

Recommended Action No actions needed

Error Message
MADM-EXECUTOR_MGR- 6 -MGR_IN_SERVICE : Executor Manager in service.

Explanation The Executor Manager is in service

Recommended Action No actions needed

Error Message
MADM-EXECUTOR_MGR- 4 -MISSING_RESOURCE : Missing thread priority resource. Facility [String] Sub-Facility [String] Executor id [String] Exception [String]

Explanation The executor manager is unable to locate internal thread priority resources

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-EXECUTOR_MGR- 4 -CMD_EXCEPTION : Un-handled command exception. Facility [String] Sub-Facility [String] Executor id [String] Mnemonic [String] Thread [String] Thread priority [Int] Time [Long] Exception [String]

Explanation The specified command did not handled the specified exception

Recommended Action No actions needed

Error Message
MADM-EXECUTOR_MGR- 4 -INVALID_THREAD_NAME_CHANGE : Invalid thread name change. Facility [String] Sub-Facility [String] Executor id [String] Thread [String] Original Thread [String]

Explanation The specified thread had an unsupported name changed; user's code should not attempt to manually change the name of threads for whatever reasons

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-EXECUTOR_MGR- 4 -ATTEMPT_FAILED : Attempt failed. Facility [String] Sub-Facility [String] Executor id [String] Mnemonic [String] Time [Long] Exception [String]

Explanation Attempt to execute the specified command failed

Recommended Action No actions needed

Error Message
MADM-EXECUTOR_MGR- 5 -MGR_SHUTDOWN : Executor Manager in shutdown.

Explanation The Executor Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MADM-EXECUTOR_MGR- 4 -EXECUTE_FAILED : Execute failed. Facility [String] Sub-Facility [String] Executor id [String] Mnemonic [String] Time [Long] Exception [String]

Explanation Request to execute the specified command failed

Recommended Action No actions needed

Error Message
MADM-EXPR_MGR- 1 -MGR_PARTIAL_SERVICE : Expression Manager in partial service.

Explanation The Expression Manager is in partial service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-EXPR_MGR- 6 -MGR_IN_SERVICE : Expression Manager in service.

Explanation The Expression Manager is in service

Recommended Action No actions needed

Error Message
MADM-EXPR_MGR- 3 -EXPR_NOT_LICENSED : Expression not licensed. Non terminal token id [String] Expression type [String] Token [String] Line [Int] Column [Int] Exception [String]

Explanation The specified expression is not licensed

Recommended Action Verify and update the script

Error Message
MADM-EXPR_MGR- 6 -MGR_INITIALIZING : Expression Manager initializing.

Explanation The Expression Manager is initializing

Recommended Action No actions needed

Error Message
MADM-EXPR_MGR- 5 -MGR_SHUTTING_DOWN : Expression Manager shutting down.

Explanation The Expression Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MADM-EXPR_MGR- 2 -MGR_OUT_OF_SERVICE : Expression Manager in out of service.

Explanation The Expression Manager is out of service; expressions won't be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-EXPR_MGR- 5 -MGR_SHUTDOWN : Expression Manager in shutdown.

Explanation The Expression Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 3 -DATA_SOURCE_CANNOT_BE_INITIALIZED : Repository Datastore data source cannot be initialized. Exception [String]

Explanation The file manager could not get the datasource initialized for Repository Datastore.

Recommended Action If problem persists.Please contact Cisco Technical Assistance Center(TAC)

Error Message
MADM-FILE_MGR- 3 -STATE_CHECKER_THREAD_CREATION_FAILED : Unable to start the File Manager's state monitor thread. Exception [String]

Explanation Unable to start the File Manager state monitor thread;FileManager functionality not available.

Recommended Action If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MADM-FILE_MGR- 1 -MGR_PARTIAL_SERVICE : File Manager in partial service.

Explanation The File Manager is in partial service; file synchronization will notbe available

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-FILE_MGR- 3 -UNABLE_UPLOAD_FILE : Unable to upload the specified file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The file manager could not upload the specified file

Recommended Action Investigate as required

Error Message
MADM-FILE_MGR- 6 -DELETE_FILE_FOLDER_REQ_BY_USER : A file or folder delete was initiated by user. Class [String] Domain [String] Directory [String] Name [String] User Id [String]

Explanation The file manager is requested to delete folder or file by user

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 3 -REFRESH_FAILED : File refresh operation failed. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation Unable to download and create the specified file

Recommended Action Investigate as required

Error Message
MADM-FILE_MGR- 3 -RDS_SQL_EXCEPTION_INFO : SQL Exception. Exception details [String]

Explanation SQL Exception occurred in File Manager

Recommended Action Investigate as required

Error Message
MADM-FILE_MGR- 4 -CLASSPATH_SYNC_FAILED : Custom classpath files synchronization failed. Exception [String]

Explanation The remote file manager was unable to synchronize the custom classpath files and <default><webapps> folder from the cluster's document repository

Recommended Action Investigate as required

Error Message
MADM-FILE_MGR- 2 -CUSTOM_FILES_CLASSPATH_WEB_APPS_SYNC_FAILED : Unable to synchronize custom files/jars from Repository Datastore. Class [String] Exception [String]

Explanation Unable to do synchronization of <default><classpath> and<default><webapps> folders under <Documents><user>

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-FILE_MGR- 6 -SYNC_FOUND_LOCAL_FILE_NOT_IN_REPOSITORY : The local file found during synchronization is not present in Repository Datastore. Class [String] Extra local file [String]

Explanation The extra local file found during synchronization is being deleted.

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 5 -CUSTOM_FILES_CLASSPATH_WEB_APPS_SYNC_SUCCEEDED : Synchronization of custom files/jars from Repository Datastore done.

Explanation Synchronization of <default><classpath> and<default><webapps> folders under <Documents><user> completed.

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 6 -MGR_INITIALIZING : File Manager initializing.

Explanation The File Manager is initializing

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 2 -MGR_OUT_OF_SERVICE : File Manager in out of service.

Explanation The File Manager is out of service; files won't be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-FILE_MGR- 3 -UNABLE_DOWNLOAD_FILE : Unable to download the specified file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The file manager could not download the specified file

Recommended Action Investigate as required

Error Message
MADM-FILE_MGR- 4 -SYNC_FAILED_TO_CREATE_FILE : Synchronization failed to create file. Class [String] Reason [String] Exception [String]

Explanation Creation of files failed during synchronization.

Recommended Action If problem persists contact.Please Cisco Technical Assistance Center(TAC).If files are missing you may have to restart the CVD Service.

Error Message
MADM-FILE_MGR- 3 -SYNC_THREAD_CREATION_FAILED : Unable to start the File Manager's local disk synchronization thread for a file type.. Class [String] Exception [String]

Explanation Unable to start the File Manager sychronization thread;synchronization will not be available for the file type

Recommended Action If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MADM-FILE_MGR- 6 -CLASSPATH_SYNC_START : Custom classpath and <default><webapps> files are being synchronized.

Explanation The remote file manager is synchronizing the custom classpath files and webapps folders files from the cluster's document repository

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 4 -ORIGINAL_FILE_NOT_FOUND : Original file not found while copying with new version. Original file: [String]

Explanation The file manager was unable to copy a new version file since the original file was not found.

Recommended Action Investigate as required

Error Message
MADM-FILE_MGR- 3 -UNABLE_GET_REPOSITORY_STATISTICS : Unable to get the repository size information. Space information requested: [String] Exception [String]

Explanation The File Manager could not get the repository size information

Recommended Action Investigate as required

Error Message
MADM-FILE_MGR- 6 -REMOTE_STANDALONE_MODE : Remote File Manager initialized in stand-alone mode.

Explanation The remote file manager is being initialized in stand-alone mode; it will attempt to synchronized custom classpaths with the cluster

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 6 -MGR_IN_SERVICE : File Manager in service.

Explanation The File Manager is in service

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 3 -UNABLE_RENAME_FILE : Unable to rename the specified file. Class [String] Domain [String] Directory [String] Name [String] Destination Domain [String] Destination Directory [String] Destination Name [String] Exception [String]

Explanation The file manager could not rename the specified file

Recommended Action Investigate as required

Error Message
MADM-FILE_MGR- 3 -CLEANUP_THREAD_CREATION_FAILED : Unable to start the File Manager's cleanup thread. Exception [String]

Explanation Unable to start the cleanup background thread; will not be able to perform the disk cleanup operations

Recommended Action If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MADM-FILE_MGR- 4 -GET_RDS_DB_CONNECTION_FAILED : Unable to get connection to the Repository Datastore. Failure Reason [String]

Explanation Unable to get connection to Repository Datastore access; will not be able to perform prompts,grammars, documents related operations

Recommended Action Check Repository Datastore is activated.If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MADM-FILE_MGR- 6 -CLASSPATH_SYNC_DONE : Custom classpath files synchronized.

Explanation The remote file manager successfully synchronized the custom classpath files and webapps folder files from the cluster's document repository

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 3 -UNABLE_GET_FILE_MODIFIED_TIME : Unable to get the last modified time of the file or directory. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not get the file or directory's last modified time

Recommended Action Verify the path of the file or directory

Error Message
MADM-FILE_MGR- 4 -EXCEPTION_IN_TEMP_FILES_HANDLING_METHOD : Method generated exception. Exception [String]

Explanation File Manager temporary files-cleanup handling, generated exception.

Recommended Action If problem persists please contact Cisco Technical Assistance Center(TAC).

Error Message
MADM-FILE_MGR- 3 -UNABLE_GET_LAST_MODIFIED_USER : Unable to get the last modified user of the file or folder . Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not get the file or folder

Recommended Action Verify the file or folder exists in repository

Error Message
MADM-FILE_MGR- 4 -LAST_SYNC_TIME_CHECK_FAILED : Error while checking the replication LastSynchedTime. Exception [String]

Explanation Could not get the replication sync time while updating repository statistics

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 6 -NO_FOLDER_FILE_TO_DELETE_BY_CLEANUP_TASK_RUN : Current run of daily cleanup found no files,folders to delete. Exception [String]

Explanation The File Manager daily cleanup task, to cleanup deleted (folder,files) on local disk,found not files,folders to delete .

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 3 -UNABLE_DELETE_FILE : Unable to delete the specified file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The file manager could not delete the specified file

Recommended Action Investigate as required

Error Message
MADM-FILE_MGR- 6 -UPLOAD_ARCHIVE_FILE_SUCCESS : Success progress of upload archive file. Class [String] status [String]

Explanation Archive file each file type upload status

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 4 -COPY_FILES_TO_ORIG_LOCATION : Copying of files to original location errored. Exception [String]

Explanation The task to copy files from <temp> directory to original location failed

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 3 -CLUSTER_RMI_REBIND_FAILED : Unable to register remote interface in cluster space. Exception [String]

Explanation A remote interface could not be binded to the cluster space; automatic synchronization of files will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-FILE_MGR- 3 -UNABLE_MAKE_DIR : Unable to make directory. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not create the directory

Recommended Action Verify that path of the directory

Error Message
MADM-FILE_MGR- 3 -SYNC_REMOTE_NOTIFICATION_FAILED : Notifying remote File Manager service objects failed. Class [String] Node Id [String] Exception [String]

Explanation Synchronization notifications using remote File Manager Service failed for one or more nodes.

Recommended Action If problem persists contact.Please Cisco Technical Assistance Center(TAC).

Error Message
MADM-FILE_MGR- 6 -SYNC_OPERATION_STARTED : Synchronization started.. Class [String] Synchronization status [String]

Explanation Repository Datastore to local disk synchronization started.

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 3 -UNABLE_UPLOAD_ARCHIVE_FILE : Unable to upload the archive file. Archive File Name [String] Reason [String] Archive Length [String] Exception [String]

Explanation The File Manager could not upload the specified file

Recommended Action Investigate as required

Error Message
MADM-FILE_MGR- 4 -DELETED_FOLDER_FILE_CLEANUP_TASK_RUN_FAILED : Current run of daily cleanup task failed. Exception [String]

Explanation The File Manager daily cleanup task, to clean deleted (folder,files) on local disk errored.The files,folders can get deleted in next daily run.

Recommended Action Investigate as required

Error Message
MADM-FILE_MGR- 4 -SYNC_INVALID_STATE : Synchronization detected invalid state. Class [String] Reason [String]

Explanation Invalid state detected during synchronization

Recommended Action Investigate as required

Error Message
MADM-FILE_MGR- 3 -UNABLE_LIST_FILES : Unable to list the files denoted by the specified file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The file manager could not list the files denoted by the specified file

Recommended Action Investigate as required

Error Message
MADM-FILE_MGR- 6 -RECOVERY_COMPLETED_EVENT : File Manager recieved recovery completed event, full synchronization will be performed..

Explanation File Manager detected recovery completed event.Repository changes will be synched to local disk now.

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 1 -CLUSTER_COMM_FAILED : Cluster communication failure. Exception [String]

Explanation Unable to communicate with the cluster; will not be able to access the cluster repository files

Recommended Action Investigate as required

Error Message
MADM-FILE_MGR- 3 -DUPLICATE_FILE_SUPPORT : Duplicate file support detected. Class [String] Exception [String]

Explanation An attempt is being made at registering a duplicate file support

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-FILE_MGR- 3 -UNABLE_GET_FILE_LENGTH : Unable to get the length of the file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not get the file length

Recommended Action Verify the path of the file

Error Message
MADM-FILE_MGR- 3 -UNABLE_TO_CREATE_TEMP_DIR : Unable to make temp directory. Class [String] Name [String] Exception [String]

Explanation The File Manager could not create temp directory

Recommended Action Verify that Unified CCX prompts, documents, grammars and scripts folder are proper

Error Message
MADM-FILE_MGR- 4 -ERROR_WHILE_SYNCH : An error occurred while synchronizing. Class [String] Method [String] Exception [String]

Explanation An error occurred while File Manager is synchronizing disk from RDS

Recommended Action If problem persists please contact Cisco Technical Assistance Center(TAC).

Error Message
MADM-FILE_MGR- 3 -INVALID_FILE : Invalid file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The specified file is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-FILE_MGR- 3 -FAIL_TO_CREATE_RDS_SERVICE_CONVERGENCE : Repository Datastore Service convergence object cannot be created.

Explanation The file manager cannot create Repository Datastore convergence object.Repository Datastore failover functionality will not be available.

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-FILE_MGR- 4 -SYNC_LOCAL_FILE_LATEST_THAN_IN_REPOSITORY : The local file is found to be newer than one in the Repository Datastore. Class [String] Local file [String] Repository Datastore file [String]

Explanation Local file is being replaced by the one in Repository Datastore

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 4 -SYNC_NOT_COMPLETE : Synchronization did not complete.. Class [String] Exception [String]

Explanation This indicates some of the synchronization operation failed.

Recommended Action If problem persists contact.Please Cisco Technical Assistance Center(TAC).

Error Message
MADM-FILE_MGR- 6 -SYNC_OPERATION_COMPLETED : Synchronization completed.. Class [String] Synchronization status [String]

Explanation Repository Datastore to local disk synchronization completed.

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 6 -DELETED_TEMP_FILE_FOLDER : Temp file or folder was deleted. Temporary file or folder: [String]

Explanation The file manager deleted temporary file or folder

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 3 -UNABLE_SET_LAST_MODIFIED : Unable to set last modified time of the file or directory. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not set the last modified time of the file or directory.

Recommended Action Verify the path of the file or directory

Error Message
MADM-FILE_MGR- 5 -MGR_SHUTTING_DOWN : File Manager shutting down.

Explanation The File Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 3 -UNABLE_FILE_EXISTS_CHECK : Check for file or directory existence failed. Class [String] Domain [String] Directory [String] Name [String] Error reason [String]

Explanation The File Manager could not find whether file or directory exists

Recommended Action Verify the path of the file or directory

Error Message
MADM-FILE_MGR- 6 -RECOVERY_DETECTED : File Manager detected an archive request in the system;synchronization from Repository to local disk not performed..

Explanation File Manager detected an archive request in the system

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 3 -INVALID_FILE_CLASS : Invalid file class. Class [String] Exception [String]

Explanation The specified file class is not supported by the file manager

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-FILE_MGR- 4 -RMI_REBIND_FAILED : Unable to register remote interface. Exception [String]

Explanation A remote interface could not be binded to the RMI registry; remote access to files from the editor will not be available

Recommended Action Verify the RMI configuration and restart server

Error Message
MADM-FILE_MGR- 3 -FILE_MANAGER_REGISTRATION_WITH_CLUSTER_FAILED : Unable to register the File Manager's Service remote object with the cluster.. Exception [String]

Explanation Unable to register the File Manager's remote service object.

Recommended Action If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MADM-FILE_MGR- 4 -SYNC_FAILED_TO_MKDIR : Synchronization failed to make directory. Class [String] Reason [String]

Explanation Creation of directories failed during synchronization.

Recommended Action If files are missing you may have to restart the CVD Service.If problem persists contact.Please Cisco Technical Assistance Center(TAC)

Error Message
MADM-FILE_MGR- 4 -RDS_DETERMINATION_FAILED : Repository Datastore cannot be initalized.. Exception [String]

Explanation The file manager could not initialize datastore to store prompts, grammars and documents within the cluster.This may happen if Repository Datastore component is not available in the cluster or configured properly.

Recommended Action Investigate as required

Error Message
MADM-FILE_MGR- 6 -REMOTE_COLLOCATED_MODE : Remote File Manager initialized in collocated mode.

Explanation The remote file manager is being initialized in collocated mode; it will not attempt to synchronized custom classpaths with the cluster

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 5 -MGR_SHUTDOWN : File Manager in shutdown.

Explanation The File Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 4 -NEW_VERSION_FILE_NOT_FOUND : Newer version of file not found in <temp> directory. New version file(<temp>): [String]

Explanation The file manager was unable to find newer verion of file in <temp> while updating to original location

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 6 -SYNC_FOUND_LOCAL_FOLDER_NOT_IN_REPOSITORY : The local folder found during synchronization is not present in Repository Datastore. Class [String] Extra local folder [String]

Explanation The extra local folder found during synchronization is being deleted.

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 3 -SYNC_CANNOT_INITIALIZE_LOCAL_STORE : Unable to initialize local disk info when performing Repository Sync. Class [String] Exception [String]

Explanation Local store intialization failed during synchronization

Recommended Action If problem persists contactCisco Technical Assistance Center(TAC)

Error Message
MADM-FILE_MGR- 3 -SYNC_CANNOT_INITIALIZE_DB_STORE : Unable to initialize Repository Datastore access when performing Synchronization. Class [String] Exception [String]

Explanation Accessing Repository Datastore failed.

Recommended Action Check if the RDS component is activated.If problem persists contact.Please Cisco Technical Assistance Center(TAC)

Error Message
MADM-FILE_MGR- 6 -SYNCHRONIZATION_UPDATE : FileManager RDS to local disk synchronization. Class [String] Information [String]

Explanation progress message related to FileManager synchronization of local disk from RDS

Recommended Action No actions needed

Error Message
MADM-FILE_MGR- 3 -REP_DATASTORE_INIT_FAILED : Unable to initialize the Repository Datastore access. Exception [String]

Explanation Unable to initialize Repository Datastore access; will not be able to perform prompts,grammars, documents related operations

Recommended Action Check Repository Datastore is enabled.If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MADM-FILE_MGR- 6 -FILE_MARK_FOR_DELETION : Deleted file. Class [String] Domain [String] Directory [String] Name [String]

Explanation File Manager found the file marked for deletion

Recommended Action Operation cannot be preformed

Error Message
MADM-FILE_MGR- 4 -MASTER_RDS_NOT_FOUND : Repository Datastore not found.. Reason [String]

Explanation The file manager could not find Repository Datastore to store prompts, grammars and documents within the cluster.This may happen if Repository Datastore component is not activated or Master RDS is not determined.

Recommended Action Investigate as required

Error Message
MADM-GENERIC- 5 -ProcessStart : Process Starting. Process Identifier [UInt] Module Name [String]

Explanation This notification signifies that a process has just started. This notification is intended to work in conjunction with the ProcessStop notification to notify the start and stop status of a particular process.

Recommended Action No actions needed

Error Message
MADM-GENERIC- 5 -ModuleStart : Module has successfully started. Module Name [String]

Explanation This notification signifies a module has started successfully and transitioned into the in-service state

Recommended Action No actions needed

Error Message
MADM-GENERIC- 3 -ModuleRunTimeFailure : Run-time Failure. Module Name [String] Module Run-time Failure Cause [Enum] Module Failure Name [String] Module Failure Message [String]

Explanation This notification signifies a run-time failure has occured

Recommended Action Investigate as required

Module Run-time Failure Cause-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Other or Unspecified Failure
2 Read Access Failure
3 Write Access Failure
4 Create Failure
5 Delete Failure
6 Update Failure
7 Init Failure
8 Load Failure
9 Out of Resource
10 Call Process Failure
11 Registration Failure
12 De-registration Failure
13 Connection Failure
14 Disconnection Failure
15 Unknown Target
16 Un-reacheable Target
Error Message
MADM-GENERIC- 1 -ModuleStop : Module has stopped. Module Name [String] Module Failure Cause [Enum]

Explanation This notification signifies a module has stopped

Recommended Action Investigate as required

Module Failure Cause-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Other or Unspecified Failure
2 Graceful Shutdown
3 Heartbeat Failure
4 Initialization Failure
5 Out of Resource
6 Partial Failure
Error Message
MADM-GENERIC- 1 -ProcessStop : Process Stopped. Process Identifier [UInt] Module Name [String]

Explanation This notification signifies that a process has just stopped. This notification is intended to work in conjunction with the ProcessStart notification to notify the start and stop status of a particular process.

Recommended Action Investigate as required

Error Message
MADM-GRAMMAR_MGR- 3 -GRAMMAR_LEXICAL_ERROR : Template grammar lexical error. Name [String] Template [String] Language [String] Exception [String]

Explanation The specified lexical error occured while parsing a template grammar

Recommended Action Verify and update the application

Error Message
MADM-GRAMMAR_MGR- 1 -MGR_PARTIAL_SERVICE : Grammar Manager in partial service.

Explanation The Grammar Manager is in partial service; synchronization of files with grammar repository is in progress

Recommended Action No actions needed

Error Message
MADM-GRAMMAR_MGR- 6 -MGR_IN_SERVICE : Grammar Manager in service.

Explanation The Grammar Manager is in service

Recommended Action No actions needed

Error Message
MADM-GRAMMAR_MGR- 2 -INVALID_USER_DIR : Invalid user grammar directory configured. Directory [String] Exception [String]

Explanation The configured user grammar directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-GRAMMAR_MGR- 3 -GRAMMAR_PARSING_ERROR : Template grammar parsing error. Name [String] Template [String] Language [String] Exception [String]

Explanation The specified error occured while parsing a template grammar

Recommended Action Verify and update the application

Error Message
MADM-GRAMMAR_MGR- 3 -UNDEFINED_NAME_GRAMMAR : Undefined user or system grammar. Name [String] Type [String] Language [String] Exception [String]

Explanation A user or system grammar cannot be located

Recommended Action Verify and update the configuration

Error Message
MADM-GRAMMAR_MGR- 3 -GRAMMAR_FILE_SUPPORT_FAILURE : Grammar file support failure. Exception [String]

Explanation The Grammar Manager can not register file support for user grammar files; user grammars will not be synchronized on local server

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-GRAMMAR_MGR- 5 -MGR_SHUTDOWN : Grammar Manager in shutdown.

Explanation The Grammar Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MADM-GRAMMAR_MGR- 3 -UNABLE_PARSE_GRAMMAR : Unable to parse the grammar. Grammar [String] Type [String] Exception [String]

Explanation The Grammar Manager is unable to parse the specified grammar

Recommended Action Verify and update the configuration

Error Message
MADM-GRAMMAR_MGR- 3 -UNSUPPORTED_GRAMMAR : Unsupported grammar type. Name [String] Type [String] Language [String] Exception [String]

Explanation The specified grammar type is not supported

Recommended Action Verify and update the application

Error Message
MADM-GRAMMAR_MGR- 6 -MGR_INITIALIZING : Grammar Manager initializing.

Explanation The Grammar Manager is initializing

Recommended Action No actions needed

Error Message
MADM-GRAMMAR_MGR- 5 -MGR_SHUTTING_DOWN : Grammar Manager shutting down.

Explanation The Grammar Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MADM-GRAMMAR_MGR- 2 -MGR_OUT_OF_SERVICE : Grammar Manager in out of service.

Explanation The Grammar Manager is out of service; grammars won't be accessible

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-GRAMMAR_MGR- 3 -SYSGRAMMAR_FILE_SUPPORT_FAILURE : System grammar file support failure. Exception [String]

Explanation The Grammar Manager can not register file support for system grammar files; system grammars will not be synchronized on local server

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-GRAMMAR_MGR- 3 -WEBSERVICES_ERROR : Exception thrown while processing web services for Grammar. Exception [String]

Explanation Exception thrown while processing web services for Grammar

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-GRAMMAR_MGR- 2 -INVALID_SYSTEM_DIR : Invalid system grammar directory configured. Directory [String] Exception [String]

Explanation The configured system grammar directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-GRAMMAR_MGR- 3 -UNABLE_LOAD_GRAMMAR : Unable to load the grammar file. Name [String] Type [String] Language [String] Exception [String]

Explanation The Grammar Manager is unable to load the specified grammar file

Recommended Action Verify and update the configuration

Error Message
MADM-GRAMMAR_MGR- 3 -UNSUPPORTED_CONVERSION : Unsupported grammar conversion. Type [String] Conversion Type [String] Exception [String]

Explanation The specified grammar conversion is not supported

Recommended Action Verify and update the application

Error Message
MADM-LIB_APPADMINVALVE- 3 -VALVE_EXCEPTION : Directory Error. Exception [String]

Explanation Directory Error

Recommended Action Verify and update the configuration

Error Message
MADM-LIB_AXL- 3 -SLEEP_AXL_EXCEPTION : Exception while sleeping for AXL. Exception [String]

Explanation Exception while sleeping for AXL

Recommended Action Verify and update the configuration

Error Message
MADM-LIB_AXL- 3 -DUPLICATE_VALUE_AXL_EXCEPTION : Entered Duplicate Value. Exception [String]

Explanation Entered Duplicate Value

Recommended Action Verify and update the configuration

Error Message
MADM-LIB_AXL- 3 -IO_AXL_EXCEPTION : IO AXL Exception. Exception [String]

Explanation IO AXL Exception

Recommended Action Verify and update the configuration

Error Message
MADM-LIB_AXL- 3 -AXL_CONFIF_EXCEPTION : AXL Configuration Exception. Exception [String]

Explanation AXL Configuration Exception

Recommended Action Verify and update the configuration

Error Message
MADM-LIB_AXL- 3 -RESOURCE_UNAVAILABLE_AXL_EXCEPTION : CCM AXL Server is busy. Exception [String]

Explanation CCM AXL Server is busy

Recommended Action Verify and update the configuration

Error Message
MADM-LIB_AXL- 3 -UNKNOWN_HOST_AXL_EXCEPTION : Invalid CCM Hostname. Exception [String]

Explanation Invalid CCM Hostname

Recommended Action Verify and update the configuration

Error Message
MADM-LIB_AXL- 3 -INVALID_USER_AXL_EXCEPTION : IIS Authentication failed on CCM. Exception [String]

Explanation IIS Authentication failed on CCM

Recommended Action Verify and update the configuration

Error Message
MADM-LIB_AXL- 4 -AXL_TIMEOUT_DETECTED : AXL Timeout Detected. Cmd [String]

Explanation AXL Timeout Detected

Recommended Action No actions needed

Error Message
MADM-LIB_AXL- 3 -AXL_EXCEPTION : Unknown AXL Exception. Exception [String]

Explanation Unknown AXL Exception

Recommended Action Verify and update the configuration

Error Message
MADM-LIB_AXL- 3 -AXL_SOCKET_POOL_EXCEPTION : AXL can not initializa socket pool. Exception [String]

Explanation AXL can not initializa socket pool

Recommended Action Verify and update the configuration

Error Message
MADM-LIB_CFG- 3 -NOTIFY_FAIL : Fail Notifying Remote Object. Exception [String]

Explanation Fail Notifying Remote Object

Recommended Action Verify and update the configuration

Error Message
MADM-LIB_CFG- 4 -CUIC_REPORT_PERMISSIONS_ERROR : Grant or Revoke permissions to CUIC Folders and Reports failed. Exception [String]

Explanation Grant or Revoke permissions to CUIC Folders and Reports failed

Recommended Action No actions needed

Error Message
MADM-LIB_CFG- 3 -INVALID_USER : User is invalid. User [String] Exception [String]

Explanation User could not be retrieved

Recommended Action Verify and update the configuration

Error Message
MADM-LIB_CFG- 3 -INVALID_DATA_TYPE : DB operation failed because data type is invalid. ICD Config Data Type [String]

Explanation DB operation failed because data type is invalid

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-LIB_CFG- 6 -UNABLE_TO_ACQUIRE_CLUSTER_MUTEX : Cluster mutex lock could not be acquired. Name of thread trying to acquire lock [String] Exception [String]

Explanation Cluster mutex lock could not be acquired

Recommended Action No actions needed

Error Message
MADM-LIB_CFG- 3 -REPOS_CFG_FAIL : Fail to access repository profile configuration. Exception [String]

Explanation Fail to create/retrieve/update/remove repository profile configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MADM-LIB_CFG- 3 -GED_CONFIG_FAIL : Fail to retrieve GED 125 configuration. Exception [String]

Explanation Fail to retrieve GED 125 configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MADM-LIB_CFG- 1 -UCCX_TO_CUIC_SYNC_FAILED : Notification to CUIC failed. UCCX TO CUIC SYNC failed for these resources::: [String]

Explanation Notification to CUIC on resource change failed

Recommended Action EXECUTE Resource sync command from CLI

Error Message
MADM-LIB_CFG- 3 -JTAPI_CFG_FAIL : Fail to access JTAPI configuration. Exception [String]

Explanation Fail to create/retrieve/update/remove JTAPI configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MADM-LIB_CFG- 3 -TAPI_GRP_CONFIG_FAIL : Fail to retrieve TAPI Port Group configuration. Exception [String]

Explanation Fail to retrieve TAPI Port Group configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MADM-LIB_CFG- 6 -MASTER_CDS_CHANGE : The master CDS has changed. Master CDS Name [String]

Explanation The master CDS has changed

Recommended Action No actions needed

Error Message
MADM-LIB_CFG- 3 -TELE_CFG_FAIL : Fail to create telephony application configuration. Exception [String]

Explanation Fail to create telephony application configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MADM-LIB_CFG- 3 -ENG_SAVE_FAIL : Fail to save LDAP engine configuration. Exception [String]

Explanation Fail to save LDAP engine configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MADM-LIB_CFG- 3 -PROFILE_CFG_FAIL : Fail to access profile configuration. Exception [String]

Explanation Fail to create/retrieve/update/remove profile configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MADM-LIB_CFG- 3 -CONFIG_FAIL : Fail to load ldap configuration file. Exception [String]

Explanation Fail to load ldap configuration file

Recommended Action Verify and update the configuration

Error Message
MADM-LIB_CFG- 3 -GED_SCRIPT_CFG_FAIL : Fail to retrieve GED 125 Script configuration. Exception [String]

Explanation Fail to retrieve GED 125 Script configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MADM-LIB_CFG- 3 -VOICE_CFG_FAIL : Fail to access Voice configuration. Exception [String]

Explanation Fail to create/retrieve/update/remove Voice configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MADM-LIB_CFG- 3 -GED_ROUTE_CFG_FAIL : Fail to retrieve GED 125 Route configuration. Exception [String]

Explanation Fail to retrieve GED 125 Route configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MADM-LIB_CFG- 3 -PROVIDER_UNAVAILABLE : LDAP provider is unavailable. ldap url base [String] Exception [String]

Explanation LDAP provider is unavailable

Recommended Action Verify and update the configuration

Error Message
MADM-LIB_CFG- 3 -HTTP_CFG_FAIL : Fail to access HTTP configuration. Exception [String]

Explanation Fail to create/retrieve/update/remove HTTP configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MADM-LIB_CFG- 4 -REMOTE_OBJ_FAIL : Remote object could not be retrieved. remote object name [String] Exception [String]

Explanation Remote object could not be retrieved

Recommended Action No actions needed

Error Message
MADM-LIB_CFG- 3 -INI_SAVE_FAIL : Fail to save ini ldap configuration file. Exception [String]

Explanation Fail to save ini ldap configuration file

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-LIB_CFG- 3 -ENGINE_CONFIG_FAIL : LDAP Engine Configuration fail to initialize. Exception [String]

Explanation LDAP Engine Configuration fail to initialize

Recommended Action Verify and update the configuration

Error Message
MADM-LIB_CLUSTER_CFG- 6 -MUTEX_SUCCESSFULLY_RENEWED : Mutex successfully renewed. owner [String] usage [String] userInfo [String] leaseDate [String]

Explanation Mutex successfully renewed

Recommended Action No actions needed

Error Message
MADM-LIB_CLUSTER_CFG- 4 -INVALID_MUTEX_OWNER : Invalid Mutex owner. cmd [String] lockOwner [String] owner [String] usage [String] userInfo [String]

Explanation The specified cmd was requested by a different owner than the original owner who acquired the mutex, which is not permitted

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-LIB_CLUSTER_CFG- 3 -CONFIG_ERROR : Error while accessing LockConfig. owner [String] usage [String] userInfo [String] Exception [String]

Explanation Error while accessing LockConfig

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-LIB_CLUSTER_CFG- 4 -MUTEX_EXPIRED : Mutex expired. cmd [String] lockOwner [String] leaseDate [String] owner [String] usage [String] userInfo [String]

Explanation The mutex lease has expired when the specified cmd is received

Recommended Action No actions needed

Error Message
MADM-LIB_CLUSTER_CFG- 6 -MUTEX_SUCCESSFULLY_ACQUIRED : Mutex successfully acquired. owner [String] usage [String] userInfo [String]

Explanation Mutex successfully acquired

Recommended Action No actions needed

Error Message
MADM-LIB_CLUSTER_CFG- 6 -MUTEX_SUCCESSFULLY_RELEASED : Mutex successfully released. owner [String] usage [String] userInfo [String]

Explanation Mutex successfully released

Recommended Action No actions needed

Error Message
MADM-LIB_CRTP- 3 -CRTP_INTERCEPT_ERROR : CRTP interceptor error operation. Error reason [String] Exception [String]

Explanation CRTP interceptor encountered an error while performing the following operation

Recommended Action No actions needed

Error Message
MADM-LIB_CRTP- 3 -CRTP_SERVLET_ERROR : CRTP servlet error. Error reason [String] Exception [String]

Explanation CRTP servlet encountered an error while performing the following operation

Recommended Action No actions needed

Error Message
MADM-LIB_DATABASE- 6 -RECOVERY_COMPLETED_EVENT : Received recovery completed event; DB alias will be synched now.

Explanation Database component detected recovery completed event; DB alias will be synched now.

Recommended Action No actions needed

Error Message
MADM-LIB_DATABASE- 3 -SUBSCRIBER_DB_UNAVAILABLE : Subscriber database is not running or inaccessible.

Explanation An attempt to connect to the subscriber database has failed. Verify that the subscriber database is functioning and network connectivity is available to the subscriber node.

Recommended Action Investigate as required

Error Message
MADM-LIB_DATABASE- 6 -UPLOAD_USER_FILE_FAILED : Database Archive Component fails to upload the corresponding file or directory to Repository Datastore. It will be copied to the specified temporary location. file or directory name [String] temporary directory name [String] Exception [String]

Explanation Database Archive Component fails to upload the corresponding file or directory to Repostiory Datastore during upgrade migration. The file or directory will be copied to the specified temporary directory.

Recommended Action Investigate as required

Error Message
MADM-LIB_DATABASE- 3 -DATABASE_ERROR : A generic database error. Exception [String]

Explanation A generic database error occured, this could be related to SQL or none-SQL related.

Recommended Action Investigate as required

Error Message
MADM-LIB_DATABASE- 3 -UPDATE_ERROR : update error. Exception [String]

Explanation Error in updating the cluster info

Recommended Action Investigate as required

Error Message
MADM-LIB_DATABASE- 3 -COPYING_USER_FILES_FAILED : Database Archive Component fails to copy the corresponding file or directory to temporary location. file or directory name [String] temporary directory name [String] Exception [String]

Explanation Database Archive Component fails to copy the corresponding file or directory to temporary location, in an attempt to save the file after it fails to upload it to Repository datastore.

Recommended Action Investigate as required

Error Message
MADM-LIB_DATABASE- 3 -DB_REPLICATION_ERROR : A generic database replication error. Exception [String]

Explanation A generic database replication error occured, this could be related to SQL or none-SQL related.

Recommended Action Investigate as required

Error Message
MADM-LIB_DATABASE- 1 -DB_REPLICATION_STOPPED : Database replication stopped. Reason for Stopping Replication [String] Exception [String]

Explanation Database replication is stopped. Please Setup Replication from DataStore Control Center, after bringing the other node up.

Recommended Action Investigate as required

Error Message
MADM-LIB_DATABASE- 6 -SCRIPT_NOT_FOUND : Database Archive Component could not find the corresponding file or directory to upload during restore. file or directory location [String]

Explanation Database Archive Component could not find the corresponding file or directory to upload during restore

Recommended Action Investigate as required

Error Message
MADM-LIB_DATABASE- 1 -DB_NOT_IN_SYNC : Database is not in sync on both nodes.

Explanation One of more tables in Database are not in sync across nodes. Please Check whether replication is working fine. If replication is broken, reset replication else synchronize data on both nodes using forced data sync from CLI

Recommended Action Investigate as required

Error Message
MADM-LIB_DATABASE- 6 -DB_REPLICATION_INITIALIZING : DB Replication is getting initialized.

Explanation DB Replication is getting initialized

Recommended Action No actions needed

Error Message
MADM-LIB_DATABASE- 3 -INIT_ERROR : read error. Exception [String]

Explanation error in reading

Recommended Action Investigate as required

Error Message
MADM-LIB_DATABASE- 4 -REPLICATION_OLD_PUBLISHER_CLEANUP_FAIL : DB Replication old publisher cleanup failed. Old Publisher [Int] Exception [String]

Explanation Failed to cleanup the old publisher role while performing a switch publisher

Recommended Action No actions needed

Error Message
MADM-LIB_DATABASE- 6 -RECOVERY_DETECTED : Detected a recovery archive request in the system; DB alias sync is postponed until recovery is complete..

Explanation Database component detected a recovery archive request in the system; DB alias sync is postponed until recovery is complete.

Recommended Action No actions needed

Error Message
MADM-LIB_EVENT- 3 -DISPATCH_FAILURE : A failure occured while dispatching an event. Event [String] Event source [String] Event listener [String] Exception [String]

Explanation An uncaught error occured while dispatching an event

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-LIB_EVENT- 5 -TOO_LONG_IN_QUEUE : Event queue time exceeded. Event [String] Queue Time [Long]

Explanation The specified event stayed in queue for too long

Recommended Action No actions needed

Error Message
MADM-LIB_EVENT- 4 -EVENT_INIT_FAILURE : Unable to initialize the system event queue logger. Exception [String]

Explanation The logger could not be registered with the system event queue; the traces for the event queue will not be available

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-LIB_JASPER- 6 -MSG : . Message [String] Exception [String]

Explanation See log message for more info.

Recommended Action Investigate as required

Error Message
MADM-LIB_JASPER- 6 -MMSG : . Module [String] Message [String] Exception [String]

Explanation See module's log message for more info.

Recommended Action Investigate as required

Error Message
MADM-LIB_LDAP- 3 -LDAP_CON_ERROR : Error accessing LDAP. ldap url [String] Exception [String]

Explanation An error occurred while accessing LDAP

Recommended Action No actions needed

Error Message
MADM-LIB_LDAP- 4 -LDAP_CON_WARNING : Problem accessing LDAP. ldap url [String] Exception [String]

Explanation An problem occurred while accessing LDAP

Recommended Action No actions needed

Error Message
MADM-LIB_LICENSE- 3 -LICENSE_CONFIG_UNAVAILABLE_ERROR : LicenseConfig unavailable or retrieve error. Exception [String]

Explanation LicenseConfig was not accessible or the license object does not exist

Recommended Action Investigate as required

Error Message
MADM-LIB_LICENSE- 3 -LICENSE_VM_CONFIG_ERROR : OVA Template Mismatched. VM configuration does not match the OVA Profile..

Explanation OVA Template Mismatched. VM configuration does not match the OVA Profile.

Recommended Action Please refer to the Unified CCX Virtualization DocWiki for the supported VM configurations.

Error Message
MADM-LIB_LICENSE- 6 -NO_LICENSE : No Licenses were found. Error reason [String]

Explanation objFile returned from LDAP is null or it does not contain any valid licenses

Recommended Action No actions needed

Error Message
MADM-LIB_LICENSE- 2 -LICENSE_PACKAGE_NONE : Upload a valid license through the Cisco Unified CCX Application Administration.. Error reason [String]

Explanation Cisco Unified CCX license package is None.Upload a valid license through Cisco Unified CCX Application Administration.

Recommended Action Verify and update the licences

Error Message
MADM-LIB_LICENSE- 3 -RMI_LICENSE_ERROR : RMI Remote License error. Exception [String]

Explanation A problem occurred while trying to register RMI Remote License Implementation

Recommended Action Verify the RMI configuration and restart server

Error Message
MADM-LIB_LICENSE- 3 -LICENSE_REPOSITORY_UNAVAILABLE_ERROR : Config repository inaccessible. Exception [String]

Explanation A problem occurred when trying to read licenses from the Config repository

Recommended Action Investigate as required

Error Message
MADM-LIB_LICENSE- 3 -LICENSE_CONFIG_ERROR : Access license config error. Exception [String]

Explanation A problem occurred when trying to retrieve licenses from the license config object

Recommended Action Investigate as required

Error Message
MADM-LIB_LICENSE- 3 -LICENSE_READ_ERROR : License read error. Exception [String]

Explanation A problem occurred when trying to read license files

Recommended Action Investigate as required

Error Message
MADM-LIB_LICENSE- 3 -LICENSE_REPOSITORY_ERROR : License Repository error. Exception [String]

Explanation A problem occurred when trying to read licenses from the Config repository

Recommended Action Investigate as required

Error Message
MADM-LIB_LICENSE- 6 -LICENSE_INFO : License Information. Licenses [String]

Explanation The cluster was configured with the specified licenses enabled.

Recommended Action No actions needed

Error Message
MADM-LIB_LICENSE- 3 -LICENSE_TIME_EXPIRED : Upload a valid license through the Cisco Unified CCX Application Administration.. Error reason [String]

Explanation One or More Temporary License(s) have expired. The corresponding features would become unusable. Please upload valid license for the same through Cisco Unified CCX Application Administration.

Recommended Action Verify and update the licences

Error Message
MADM-LIB_RMI- 5 -RMI_LOG_MONITOR_FAIL : RMI log configuration monitoring failure.

Explanation RMI layer can no longer monitor dynamic update to its log configuration; debug messages disabled

Recommended Action No actions needed

Error Message
MADM-LIB_SERVLET- 6 -MSG : . Message [String] Exception [String]

Explanation See log message for more info.

Recommended Action Investigate as required

Error Message
MADM-LIB_SERVLET- 6 -MMSG : . Module [String] Message [String] Exception [String]

Explanation See module's log message for more info.

Recommended Action Investigate as required

Error Message
MADM-LIB_TC- 6 -MSG : . Message [String] Exception [String]

Explanation See log message for more info.

Recommended Action Investigate as required

Error Message
MADM-LIB_TC- 6 -MMSG : . Module [String] Message [String] Exception [String]

Explanation See module's log message for more info.

Recommended Action Investigate as required

Error Message
MADM-LIB_TPL- 6 -TPL_INFO : TPL_LOG4J Info log. A specific description for a trace [String]

Explanation TPL_LOG4J Info log

Recommended Action No actions needed

Error Message
MADM-LIB_TPL- 3 -TPL_ERROR : Error in ThirdParty library. A specific description for a trace [String] A description for the nature of the exception [String] Exception [String]

Explanation Error in ThirdParty library

Recommended Action No actions needed

Error Message
MADM-LIB_TPL- 5 -TPL_LOG4J_LOG_MONITOR_FAIL : TPL log configuration monitoring failure.

Explanation TPL logs layer can no longer monitor dynamic update to its log configuration; debug messages disabled

Recommended Action No actions needed

Error Message
MADM-LIB_TPL- 6 -TPL_LOG4J_LOG_MONITOR : TPL log. message [String] error_desc [String]

Explanation Hibernate and Atomikos logs

Recommended Action No actions needed

Error Message
MADM-LOG_MGR- 2 -MGR_PARTIAL_SERVICE : Log Manager in partial service.

Explanation The Log Manager is in partial service; logs won't be completely availablew

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-LOG_MGR- 3 -XML_PARSING_ERROR : XML parsing error. Catalog [String] Public identifier [String] System identifier [String] Line number [Int] Column number [Int] Exception [String] Nested Exception [String]

Explanation The log manager could not parse the XML log catalog

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-LOG_MGR- 6 -MGR_IN_SERVICE : Log Manager in service.

Explanation The Log Manager is in service

Recommended Action No actions needed

Error Message
MADM-LOG_MGR- 4 -INTERRUPT : Log generation interrupted. Catalog [String] Mnemonic [String] Exception [String]

Explanation The generation of a log was interrupted

Recommended Action Restart server

Error Message
MADM-LOG_MGR- 4 -LOG_CFG_MONITOR_FAIL : Log levels configuration monitoring failure. Exception [String]

Explanation The Log Manager can no longer monitor dynamic update to the log levels configuration; tracing can no longer be turned on or off

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-LOG_MGR- 4 -TO_STRING_FAILURE : Log toString() conversion failure. Catalog [String] Mnemonic [String] Parameter index [Int] Exception [String]

Explanation The log writer is unable to convert the given parameter in the specified log to a string

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-LOG_MGR- 5 -MGR_SHUTDOWN : Log Manager in shutdown.

Explanation The Log Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MADM-LOG_MGR- 6 -MGR_INITIALIZING : Log Manager initializing.

Explanation The Log Manager is initializing

Recommended Action No actions needed

Error Message
MADM-LOG_MGR- 2 -MGR_OUT_OF_SERVICE : Log Manager in out of service.

Explanation The Log Manager is out of service; logs won't be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-LOG_MGR- 5 -MGR_SHUTTING_DOWN : Log Manager shutting down.

Explanation The Log Manager is in the process of shutting down; pending logs are being flushed out

Recommended Action No actions needed

Error Message
MADM-LOG_MGR- 3 -UNABLE_LOAD_CATALOG : Unable to load log catalog. Catalog [String] Exception [String] Nested Exception [String]

Explanation The log manager could not load the log catalog

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-LOG_MGR- 6 -CATALOG_LOADED : Log catalog loaded. Catalog [String]

Explanation The specified log catalog was loaded in memory

Recommended Action No actions needed

Error Message
MADM-LOG_MGR- 3 -WRITER_FAILURE : Log writer failure. Catalog [String] Exception [String]

Explanation The log writer failed to properly initialize for the log catalog

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-MGR_MGR- 6 -MGR_ALREADY_INIT : Manager initialization failed. Exception [String]

Explanation A manager in the Manager Manager failed to initialize because it has already been loaded.

Recommended Action Investigate as required

Error Message
MADM-MGR_MGR- 1 -MGR_PARTIAL_SERVICE : Manager Manager in partial service.

Explanation Some managers are currently out of service

Recommended Action Investigate as required

Error Message
MADM-MGR_MGR- 2 -NETWORK_FAILURE_DETECTED : lookup on local host resolved to loopback address. Please check network connectivity.

Explanation lookup on local host resolved to loopback address. Please check network connectivity.

Recommended Action Investigate as required

Error Message
MADM-MGR_MGR- 1 -MGR_CONFIG_ERROR : Error while reading configuration file for ManagerManager. Exception [String]

Explanation Error while reading configuration file for ManagerManager

Recommended Action Verify and update the configuration and restart server

Error Message
MADM-MGR_MGR- 3 -MGR_XML_PARSE_ERROR : Could not create URL while parsing xml data. Exception [String]

Explanation Could not create URL while parsing xml data

Recommended Action Verify and update the configuration and restart server

Error Message
MADM-MGR_MGR- 1 -RMI_FAILURE_RETRY : RMI could not be configured at the specified port. Will attempt to retry.. Exception [String]

Explanation RMI could not be configured at the specified port. Will attempt to retry.

Recommended Action Verify the RMI configuration and restart server

Error Message
MADM-MGR_MGR- 3 -THREAD_DEATH_EXCEPTION : An uncaught exception has be thrown in a thread. Thread name [String] Exception [String]

Explanation An uncaught exception has be thrown in a thread

Recommended Action Investigate as required

Error Message
MADM-MGR_MGR- 0 -MGRMGR_KEEPALIVE_EXCPT : A KeepAlive exception has been thrown in Manager Manager. Exception [String]

Explanation A KeepAlive exception has been thrown in Manager Manager

Recommended Action Investigate as required

Error Message
MADM-MGR_MGR- 0 -MGRMGR_START_FAIL : Fail to start Application startable class. Exception [String]

Explanation Manager Manager fail to start the startable class

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-MGR_MGR- 4 -CLASSPATH_NOT_LOADED : A classpath was not loaded during initialization. Exception [String]

Explanation A classpath was not loaded during initialization

Recommended Action No actions needed

Error Message
MADM-MGR_MGR- 6 -MGR_INITIALIZING : Manager Manager initializing.

Explanation The Manager Manager is initializing

Recommended Action No actions needed

Error Message
MADM-MGR_MGR- 2 -MGR_OUT_OF_SERVICE : Manager Manager in out of service.

Explanation All primary managers are out of service

Recommended Action Investigate as required

Error Message
MADM-MGR_MGR- 3 -MANAGER_INTERCEPT_ERROR : Manager interceptor error operation. Error reason [String] Exception [String]

Explanation Manager interceptor encountered an error while performing the following operation

Recommended Action No actions needed

Error Message
MADM-MGR_MGR- 0 -MGRMGR_INIT_FAIL : Fail to initialize Manager Manager and start main thread. Exception [String]

Explanation Fail to initialize Manager Manager and start main thread

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-MGR_MGR- 6 -MGR_IN_SERVICE : Manager Manager in service.

Explanation The Manager Manager is in service

Recommended Action No actions needed

Error Message
MADM-MGR_MGR- 0 -APP_SVC_INIT_ERROR : Application services initialization error. Exception [String]

Explanation The Application services could not be initialized because the RMI registry could not be accessed

Recommended Action Verify the RMI configuration and restart server

Error Message
MADM-MGR_MGR- 6 -MGRMGR_PERFMON_INIT_SUCCESS : Application successfully initialized perfmon dll.

Explanation The Application services loaded the WFCCNPerfWin32 dll

Recommended Action No actions needed

Error Message
MADM-MGR_MGR- 1 -BOOTSTRAP_INIT_ERROR : Error occurred while initializing bootstrap information. Exception [String]

Explanation Error occurred while initializing bootstrap information

Recommended Action Verify and update the configuration and restart server

Error Message
MADM-MGR_MGR- 1 -CURRENCY_CFG_MONITOR_FAIL : Currency configuration monitoring failure. Exception [String]

Explanation The system default currency can no longer be updated dynamically

Recommended Action Investigate as required

Error Message
MADM-MGR_MGR- 1 -WEB_SERVICE_ERROR : Web service initialization error. Error reason [String]

Explanation Web service initialization error

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-MGR_MGR- 4 -IP_HOSTNAME_UPDATE : Host Name of one of the UCCX Servers in cluster is changed. Old Host Name [String] New Host Name [String]

Explanation Host Name of one of the UCCX Servers in cluster is changed

Recommended Action No actions needed

Error Message
MADM-MGR_MGR- 3 -CLASSPATH_NOT_FOUND : Configured classpath is not found. Exception [String]

Explanation Configured classpath is not found

Recommended Action Verify and update the configuration and restart server

Error Message
MADM-MGR_MGR- 3 -HOSTFILE_ERROR : An error occurred while trying to access host file. Exception [String]

Explanation An error occurred while trying to access host file

Recommended Action Verify and update the configuration

Error Message
MADM-MGR_MGR- 3 -MGRMGR_ROOTDIR_ERROR : No root directory path found in properties file.

Explanation No root directory path found in properties file

Recommended Action No actions needed

Error Message
MADM-MGR_MGR- 1 -HIGH_MEM_USAGE : JVM heap memory usage is high. Facility [String] Current usage [String] Maximum available [String] percentage Old Gen Memory used [Int]

Explanation JVM heap memory usage is high

Recommended Action Investigate as required

Error Message
MADM-MGR_MGR- 5 -MGRMGR_KEEPALIVE_EXCPT_CANCEL : Manager Manager is attempting to cancel KeepAlive exception. Exception [String]

Explanation KeepAlive exception is cancelled in ManagerManager because the manager in question return from a timeout. Note that this does not mean Node Manager did not detect the KeepAlive exception. It might be that Node Manager detected the exception while ManagerManager is cancelling it.

Recommended Action No actions needed

Error Message
MADM-MGR_MGR- 1 -APP_CFG_SYNC_FAIL : Application configuration failure. Exception [String]

Explanation The Manager Manager could not retrieve configuration information from the Config Framework. Using local configuration.

Recommended Action Investigate as required

Error Message
MADM-MGR_MGR- 1 -RMI_PORT_CONFIGURATION_FAILURE : Failed to configure new rmi port. Old Port [String] New Port [String]

Explanation Cannot modify rmi port to the configured value since port is in use by another application. Please change rmi port configuration using CRS Administrator.

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-MGR_MGR- 6 -DEFAULT_CURRENCY_UPDATE : System default currency updated. Currency [String]

Explanation The system default currency was updated

Recommended Action No actions needed

Error Message
MADM-MGR_MGR- 5 -MGR_SHUTTING_DOWN : Manager Manager in shutting down.

Explanation The Manager Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MADM-MGR_MGR- 1 -REGISTRY_INIT_ERROR : An error occurred during initialization of registry. Exception [String]

Explanation RMI Registry could not be initialized.

Recommended Action Verify the RMI configuration and restart server

Error Message
MADM-MGR_MGR- 4 -CUSTOM_PROP_NOT_FOUND : CustomFileClasspath.properties file is not found.

Explanation CustomFileClasspath.properties file is not found

Recommended Action No actions needed

Error Message
MADM-MGR_MGR- 1 -REGISTRY_RETRY_ERROR : Maximum retries reached trying to create registry. No registry created.. Registry retry value [String]

Explanation Maximum retries reached trying to create registry. No registry created.

Recommended Action Verify the RMI configuration and restart server

Error Message
MADM-MGR_MGR- 6 -REGISTRY_RETRY_INFO : Could not create registry at specified port. Will retry at different port. Port [String]

Explanation ManagerManager could not create registry at specified port. Will retry at different port

Recommended Action No actions needed

Error Message
MADM-MGR_MGR- 1 -BOOTSTRAP_SYNC_ERROR : ManagerManager bootstrap sync failure. Exception [String]

Explanation ManagerManager cannot synchronize the bootstrap information due to the following problem

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-MGR_MGR- 4 -MANAGER_INTERCEPT_WARNING : Manager interceptor warning. Reason for this warning [String]

Explanation Manager interceptor warning log info

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-MGR_MGR- 1 -APP_CFG_MONITOR_FAIL : Application configuration monitoring failure. Exception [String]

Explanation The Manager Manager can no longer monitor dynamic update to some of its configuration

Recommended Action Investigate as required

Error Message
MADM-MGR_MGR- 1 -MGR_INIT_ERROR : Manager initialization error. Exception [String]

Explanation A manager in the Manager Manager cannot be instantiated and will not be available

Recommended Action Investigate as required

Error Message
MADM-MGR_MGR- 0 -UNRECOVERABLE_ERROR : An unrecoverable error has occurred. Exception [String]

Explanation An unrecoverable error has occurred

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-MGR_MGR- 3 -MGRMGR_SHUTDOWN_FAIL : An exception occurred while shutting down Manager Manager. Exception [String]

Explanation An exception occurred while shutting down Manager Manager

Recommended Action Investigate as required

Error Message
MADM-MGR_MGR- 5 -MGR_SHUTDOWN : Manager Manager in shutdown.

Explanation The Manager Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MADM-MGR_MGR- 4 -IP_ADDRESS_UPDATE : IP Address of one of the UCCX Servers in cluster is changed. Old IP Address [String] New IP Address [String]

Explanation IP Address of one of the UCCX Servers in cluster is changed

Recommended Action No actions needed

Error Message
MADM-MGR_MGR- 3 -MGRMGR_BEAN_ERROR : Error setting design time bean. Exception [String]

Explanation There was an error setting the design time bean

Recommended Action No actions needed

Error Message
MADM-MGR_MGR- 0 -THREADS_DUMP : Java Virtual Machine Threads Dump. Message [String] Exception [String]

Explanation A dump of all running threads was just produced in JVM.log. Collect all existing logs and the JVM.log file and forward them to Cisco.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-MGR_MGR- 3 -GET_DEFAULT_USER_ERROR : Default User could not be retrieved. Exception [String]

Explanation Default User could not be retrieved due to the following error

Recommended Action No actions needed

Error Message
MADM-MGR_MGR- 1 -MEMORY_USAGE_EXCEEDED_THRESHOLD : Memory usage exceeded the threshold set. Facility [String] Current usage [String] Maximum available [String] percentage Heap memory used [Int]

Explanation Memory usage exceeded the threshold set

Recommended Action Investigate as required

Error Message
MADM-MGR_MGR- 1 -SYS_CFG_SYNC_FAIL : System configuration failure. Exception [String]

Explanation The Manager Manager could not retrieve system configuration from the Config Framework. Using local configuration.

Recommended Action Investigate as required

Error Message
MADM-MGR_MGR- 1 -RMI_CREATE_ERROR : Cannot create rmi registry at specified port location. Port [String] Exception [String]

Explanation Cannot create rmi registry at specified port location since port is in use by another application. Please change rmi port configuration using CRS Administrator or shutdown the process using the specified port.

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-MGR_MGR- 1 -SYS_CFG_MONITOR_FAIL : System configuration monitoring failure. Exception [String]

Explanation The Manager Manager can no longer monitor dynamic update to the system configuration

Recommended Action Investigate as required

Error Message
MADM-NODE_MGR- 3 -NODE_MGR_STOPNODE_ERROR : Can't stop and restart the node manager and its controlled processes. Exception [String]

Explanation Can't stop and restart the node manager and its controlled processes

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-NODE_MGR- 3 -NODE_MGR_SERVICE_START_ERROR : Can't start service. service name [String] Exception [String]

Explanation Can't start service

Recommended Action Retry the operation and if problem persist contact Cisco Technical Assistance Center

Error Message
MADM-NODE_MGR- 3 -NODE_MGR_REMOVE_LISTENER_ERROR : Could not remove Node listener. Exception [String]

Explanation Could not remove node listener from node manager

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-NODE_MGR- 0 -NODE_MGR_SERVICE_CRASH_DETECTED : Node manager detected service crash. service name [String]

Explanation Node manager detected service crash

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-NODE_MGR- 1 -NODE_MGR_DESTROY_ERROR : Destroy Node Manager failed. Exception [String]

Explanation Destroy the native node manager failed

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-NODE_MGR- 1 -MEDIASENSE_STATUS_DOWN : One or more configured Mediasense nodes are down or unreachable from this CCX..

Explanation One or more configured Mediasense nodes are down or unreachable from this CCX.

Recommended Action Bring Mediasense node(s) UP, then update Recording Server Configuration to re-subscribe CCX for Mediasense session events.

Error Message
MADM-NODE_MGR- 3 -NODE_MGR_SERVICE_ACTIVATE_ERROR : Can't activate the service. service name [String] Exception [String]

Explanation Can't activate the service

Recommended Action Retry the operation and if problem persist contact Cisco Technical Assistance Center

Error Message
MADM-NODE_MGR- 3 -NODE_MGR_SERVICE_DEACTIVATE_ERROR : Can't deactivate the service. process name [String] Exception [String]

Explanation Can't deactivate the service

Recommended Action Retry the operation and if problem persist contact Cisco Technical Assistance Center

Error Message
MADM-NODE_MGR- 3 -NODE_MGR_SETFAILUREREASON_ERROR : Set service failure reason failed. Exception [String]

Explanation Set a service failure reason to display in Unified CCX Administration failed

Recommended Action No actions needed

Error Message
MADM-NODE_MGR- 3 -NODE_MGR_STARTNODE_ERROR : Can't start the node manager and its controlled processes. opeartion failure source [String]

Explanation Can't start the node manager and its controlled processes

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-NODE_MGR- 1 -NODE_MGR_KEEP_ALIVE_ERROR : Node Manager keep alive ping failed. Exception [String]

Explanation Node manager keep alive ping failed

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-NODE_MGR- 3 -NODE_MGR_SERVICE_RESTART_ERROR : Can't restart service. service name [String] Exception [String]

Explanation Can't restart service

Recommended Action Retry the operation and if problem persist contact Cisco Technical Assistance Center

Error Message
MADM-NODE_MGR- 0 -NODE_MGR_SERVICE_MONITOR_THREAD_FAILED : Node manager service Monitor thread failed. Exception [String]

Explanation Node manager service Monitor thread failed

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-NODE_MGR- 3 -NODE_MGR_SERVICE_STOP_ERROR : Can't stop service. service name [String] Exception [String]

Explanation Can't stop service

Recommended Action Retry the operation and if problem persist contact Cisco Technical Assistance Center

Error Message
MADM-NODE_MGR- 0 -GENERAL_JVM_DEADLOCK_ERROR : A JVM deadlock has been detected. Exception [String]

Explanation A JVM deadlock has been detected. Copy out any JVM.log under log/MCVD MADM MIVR directory

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-NODE_MGR- 3 -NODE_MGR_ADD_LISTENER_ERROR : Could not add Node listener. Exception [String]

Explanation Could not add node listener to node manager

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-PROMPT_MGR- 1 -MGR_PARTIAL_SERVICE : Prompt Manager in partial service.

Explanation The Prompt Manager is in partial service; synchronization of files with prompt repository is in progress

Recommended Action Investigate as required

Error Message
MADM-PROMPT_MGR- 3 -INVALID_TTS_PROVIDER : Invalid TTS prompt provider. Name [String] Exception [String]

Explanation The specified TTS prompt provider is invalid

Recommended Action Verify and update the configuration

Error Message
MADM-PROMPT_MGR- 2 -INVALID_USER_DIR : Invalid user prompt directory configured. Directory [String] Exception [String]

Explanation The configured user prompt directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-PROMPT_MGR- 3 -UNDEFINED_GENERATED_PROMPT : Undefined generated prompt. Generated Prompt [String] Language [String] Exception [String]

Explanation Unable to resolve the generated prompt

Recommended Action Verify and update the application and if problem persist contact Cisco technical assistance center

Error Message
MADM-PROMPT_MGR- 6 -GENERATOR_FALLBACK : Falling back to system prompt generators. Generated Prompt [String] Generator Constructor [String] Bundle [String] Language [String] Exception [String]

Explanation The Prompt Manager failed to use the prompt generator bundle specified by the generated prompt and is falling back to the systemprompt generators

Recommended Action Verify and update the application

Error Message
MADM-PROMPT_MGR- 3 -UNSUPPORTED_PROMPT : Unsupported prompt type. Name [String] Type [String] Language [String] Exception [String]

Explanation The specified prompt type is not supported

Recommended Action Verify and update the application

Error Message
MADM-PROMPT_MGR- 3 -PROMPT_LEXICAL_ERROR : Template prompt lexical error. Name [String] Template [String] Language [String] Exception [String]

Explanation The specified lexical error occured while parsing a template prompt

Recommended Action Verify and update the application

Error Message
MADM-PROMPT_MGR- 3 -UNDEFINED_NAME_PROMPT : Undefined user or system prompt. Name [String] Type [String] Transcription [String] Language [String] Exception [String]

Explanation A user or system prompt cannot be located

Recommended Action Verify and update the configuration

Error Message
MADM-PROMPT_MGR- 3 -UNDEFINED_TTS_PROMPT : Undefined TTS prompt. Name [String] Transcription [String] Language [String] Exception [String]

Explanation A TTS prompt cannot be generated

Recommended Action Verify and update the configuration and restart server

Error Message
MADM-PROMPT_MGR- 3 -UNDEFINED_SILENCE_PROMPT : Undefined silence prompt. Silence Duration [Long] Exception [String]

Explanation A silence prompt cannot be located

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-PROMPT_MGR- 3 -PROMPT_FILE_SUPPORT_FAILURE : Prompt file support failure. Exception [String]

Explanation The Prompt Manager can not register file support for user prompt files; user prompts will not be synchronized on local server

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-PROMPT_MGR- 6 -MGR_INITIALIZING : Prompt Manager initializing.

Explanation The Prompt Manager is initializing

Recommended Action No actions needed

Error Message
MADM-PROMPT_MGR- 2 -MGR_OUT_OF_SERVICE : Prompt Manager in out of service.

Explanation The Prompt Manager is out of service; prompts won't be accessible

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-PROMPT_MGR- 5 -MGR_SHUTTING_DOWN : Prompt Manager shutting down.

Explanation The Prompt Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MADM-PROMPT_MGR- 6 -SYSTEM_TTS_PROVIDER : System TTS provider registered. Name [String]

Explanation A system TTS prompt provider has been registered

Recommended Action No actions needed

Error Message
MADM-PROMPT_MGR- 6 -MGR_IN_SERVICE : Prompt Manager in service.

Explanation The Prompt Manager is in service

Recommended Action No actions needed

Error Message
MADM-PROMPT_MGR- 5 -MGR_SHUTDOWN : Prompt Manager in shutdown.

Explanation The Prompt Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MADM-PROMPT_MGR- 3 -UNABLE_CREATE_TTS : Unable to instantiate TTS prompt provider. Name [String] Classname [String] Exception [String]

Explanation The specified TTS prompt provider cannot be located or instantiated

Recommended Action Verify and update the configuration and restart server

Error Message
MADM-PROMPT_MGR- 3 -PROMPT_PARSING_ERROR : Template prompt parsing error. Name [String] Template [String] Language [String] Exception [String]

Explanation The specified error occured while parsing a template prompt

Recommended Action Verify and update the application

Error Message
MADM-PROMPT_MGR- 6 -NO_SYSTEM_TTS_PROVIDER : No system TTS provider registered.

Explanation There is no system TTS prompt provider currently registered

Recommended Action Verify and update the configuration

Error Message
MADM-PROMPT_MGR- 6 -TTS_PROVIDER_FALLBACK : Falling back to system configured TTS provider. Transcription [String] Language [String] Name [String] Exception [String]

Explanation The Prompt Manager failed to use the TTS prompt provider specified by the TTS prompt and is falling back to the system TTS prompt provider

Recommended Action Verify and update the application

Error Message
MADM-PROMPT_MGR- 3 -UNDEFINED_GENERATOR : Undefined prompt generator. Generated Prompt [String] Generator Constructor [String] Bundle [String] Language [String] Exception [String]

Explanation The Prompt Manager failed to locate a prompt generator as requested

Recommended Action Verify and update the application and if problem persist contact Cisco technical assistance center

Error Message
MADM-PROMPT_MGR- 3 -INVALID_GENERATOR : Invalid prompt generator. Generated Prompt [String] Generator Name [String] Generator Constructor [String] Language [String] Exception [String]

Explanation The Prompt Manager failed to instantiate the rquested prompt generator

Recommended Action Verify and update the application and if problem persist contact Cisco technical assistance center

Error Message
MADM-PROMPT_MGR- 3 -WEBSERVICES_ERROR : Exception thrown while processing web services for Prompt. Exception [String]

Explanation Exception thrown while processing web services for Prompt

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-PROMPT_MGR- 2 -INVALID_SYSTEM_DIR : Invalid system prompt directory configured. Directory [String] Exception [String]

Explanation The configured system prompt directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-PURGING- 1 -AUTO_PURGE_COMPLETE : Auto purge completion information.. Message Description [String]

Explanation Auto purge completion information.

Recommended Action No actions needed

Error Message
MADM-PURGING- 3 -PURGE_ERROR : An exception has been caught.. Message Description [String] Exception [String]

Explanation An exception has been caught.

Recommended Action An exception has been caught.

Error Message
MADM-PURGING- 3 -EMAIL_NOTIFY_ERROR : Error in sending email notification. Exception [String]

Explanation Not able to read email server info

Recommended Action Check the email server config

Error Message
MADM-PURGING- 6 -PURGE_PROCESS_INFO : Purge process information.. Message Description [String]

Explanation Purge process information.

Recommended Action No actions needed

Error Message
MADM-PURGING- 6 -SET_PURGE_CONFIG : Set purge config information.. Message Description [String]

Explanation Set purge config information.

Recommended Action No actions needed

Error Message
MADM-PURGING- 6 -PURGE_INFO : Purging information. Message Description [String]

Explanation Purging information

Recommended Action No actions needed

Error Message
MADM-PURGING- 6 -GET_PURGE_CONFIG : Auto purge config information.. Message Description [String]

Explanation Auto purge config information.

Recommended Action No actions needed

Error Message
MADM-REST_CLIENT- 0 -REST_CLIENT_ERROR : Unable to invoke the rest API. Exception [String]

Explanation Invoking the rest API failed with errors

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-REST_CLIENT- 1 -UCCX_TO_CUIC_SYNC_FAILED : Notification to CUIC failed. UCCX TO CUIC SYNC failed for these resources::: [String]

Explanation Notification to CUIC on resource change failed

Recommended Action EXECUTE Resource sync command from CLI

Error Message
MADM-RTPPORT_MGR- 2 -INVALID_RTPPORT : Invalid initial RTP port configured. Number [Int] Exception [String]

Explanation The configured initial RTP port is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-RTPPORT_MGR- 1 -MGR_PARTIAL_SERVICE : RTP Port Manager in partial service.

Explanation The RTP Port Manager is in partial service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-RTPPORT_MGR- 6 -INSTALLED_PAYLOAD_TYPES : The payload of the prompt installed on this system. Payload [String]

Explanation The payload of the prompt installed on this system

Recommended Action No actions needed

Error Message
MADM-RTPPORT_MGR- 6 -MGR_IN_SERVICE : RTP Port Manager in service.

Explanation The RTP Port Manager is in service

Recommended Action No actions needed

Error Message
MADM-RTPPORT_MGR- 6 -MGR_INITIALIZING : RTP Port Manager initializing.

Explanation The RTP Port Manager is initializing

Recommended Action No actions needed

Error Message
MADM-RTPPORT_MGR- 2 -RTPPORT_CFG_ERROR : RTP port configuration failure. Exception [String]

Explanation The RTP Port Manager is unable to load its configuration

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-RTPPORT_MGR- 2 -MGR_OUT_OF_SERVICE : RTP Port Manager in out of service.

Explanation The RTP Port Manager is out of service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-RTPPORT_MGR- 5 -MGR_SHUTTING_DOWN : RTP Port Manager shutting down.

Explanation The RTP Port Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MADM-RTPPORT_MGR- 5 -MGR_SHUTDOWN : RTP Port Manager in shutdown.

Explanation The RTP Port Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MADM-RTPPORT_MGR- 2 -PAYLOAD_CFG_ERROR : RTP codec configuration failure. Exception [String]

Explanation The RTP Port Manager is unable to load its codec configuration

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-RTPPORT_MGR- 3 -INVALID_PAYLOAD_TYPE : Payload type supported in the system is invalid. Payload [String]

Explanation The specified system supported payload type is invalid

Recommended Action Reinstall server

Error Message
MADM-RTPPORT_MGR- 6 -RECOVERY_DETECTED : RTP Port Manager detected an archive request in the system.

Explanation RTP Port Manager detected an archive request in the system

Recommended Action No actions needed

Error Message
MADM-SCRIPT_MGR- 1 -MGR_PARTIAL_SERVICE : Script Manager in partial service.

Explanation The Script Manager is in partial service; synchronization of files with script repository is in progress

Recommended Action No actions needed

Error Message
MADM-SCRIPT_MGR- 3 -STEP_COPY_FAILURE : Unable to copy a step. Script [String] Step id [Long] Step Class [String] Step Description [String] Exception [String]

Explanation The specified step could not be copied

Recommended Action Verify and update the configuration

Error Message
MADM-SCRIPT_MGR- 3 -UNSUPPORTED_SCRIPT : Unsupported script type. Script [String] Type [String] Domain [String] Exception [String]

Explanation The specified script type is not supported

Recommended Action Verify and update the script

Error Message
MADM-SCRIPT_MGR- 2 -INVALID_USER_DIR : Invalid user script directory configured. Directory [String] Exception [String]

Explanation The configured user script directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-SCRIPT_MGR- 3 -INVALID_FINAL_CFG_VAR : Variable defined as a final variable. Application [String] Script [String] Variable [String] Exception [String]

Explanation The script variable is defined as final which cannot be modified

Recommended Action Verify and update the configuration

Error Message
MADM-SCRIPT_MGR- 4 -HIDDEN_STEP_FOUND : Script contains an hidden step. Script [String] Step id [Long] Step Class [String] Step Description [String]

Explanation The specified script contains the specified hidden step

Recommended Action Load the script in the Unified CCX Editor and save it back; this will removethe hidden step

Error Message
MADM-SCRIPT_MGR- 3 -INVALID_SCRIPT : Invalid script. Script [String] Exception [String]

Explanation The script configured is invalid and cannot be loaded

Recommended Action Verify and update the script

Error Message
MADM-SCRIPT_MGR- 4 -CFG_VAR_NOT_DEFINED : Variable not defined in script. Application [String] Script [String] Variable [String]

Explanation A configured variable is not defined in the script

Recommended Action Verify and update the configuration

Error Message
MADM-SCRIPT_MGR- 3 -SCRIPT_NOT_DEFINED : Script not defined. Script [String] Exception [String]

Explanation The specified script is not configured in the repository

Recommended Action Verify and update the script

Error Message
MADM-SCRIPT_MGR- 3 -NOT_A_CFG_VAR : Variable not defined as a configuration variable. Application [String] Script [String] Variable [String]

Explanation A configured variable is not defined as a configuration variable in the script

Recommended Action Verify and update the configuration

Error Message
MADM-SCRIPT_MGR- 2 -NO_SCRIPT_CTX : No context defined in script. Application [String] Script [String]

Explanation The specified script doesn't have a context of variables defined

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-SCRIPT_MGR- 6 -MGR_INITIALIZING : Script Manager initializing.

Explanation The Script Manager is initializing

Recommended Action No actions needed

Error Message
MADM-SCRIPT_MGR- 2 -MGR_OUT_OF_SERVICE : Script Manager in out of service.

Explanation The Script Manager is out of service; Scripts won't be accessible

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-SCRIPT_MGR- 5 -MGR_SHUTTING_DOWN : Script Manager shutting down.

Explanation The Script Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MADM-SCRIPT_MGR- 3 -RMI_REBIND_FAILED : Unable to register remote interface. Exception [String]

Explanation A remote interface could not be bound to the RMI registry; remote access for dynamic update or other functions will not be available

Recommended Action Verify the RMI configuration and restart server

Error Message
MADM-SCRIPT_MGR- 6 -MGR_IN_SERVICE : Script Manager in service.

Explanation The Script Manager is in service

Recommended Action No actions needed

Error Message
MADM-SCRIPT_MGR- 3 -CUSTOMIZER_ERROR : Exception thrown while processing customizer of a step in Script. Application [String] Script [String]

Explanation Exception thrown while processing customizer of a step in Script

Recommended Action Verify and update the configuration

Error Message
MADM-SCRIPT_MGR- 5 -MGR_SHUTDOWN : Script Manager in shutdown.

Explanation The Script Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MADM-SCRIPT_MGR- 3 -UNABLE_LOAD_SCRIPT : Unable to load script. Script [String] Exception [String]

Explanation The script manager could not load the specified script

Recommended Action Verify and update the script

Error Message
MADM-SCRIPT_MGR- 3 -INVALID_LICENSES : Invalid licenses. Script [String] Exception [String]

Explanation The script configured cannot be loaded because of missing licenses

Recommended Action Verify and update the licences

Error Message
MADM-SCRIPT_MGR- 3 -INCOMPATIBLE_CFG_VAR_TYPES : Incompatible configuration variable types. Application [String] Script [String] Variable [String] Variable type defined [String] Variable type configured [String] Exception [String]

Explanation A configured variable type is incompatible with the variable defined script

Recommended Action Verify and update the configuration

Error Message
MADM-SCRIPT_MGR- 3 -UNDEFINED_NAME_SCRIPT : Undefined user or system script. Script [String] Type [String] Domain [String] Exception [String]

Explanation A user or system script cannot be located

Recommended Action Verify and update the configuration

Error Message
MADM-SCRIPT_MGR- 3 -CORRUPTED_SCRIPT : The script is corrupted. Script [String] Exception [String]

Explanation The specified script or the last script that the system attempted to load is corrupted and cannot be sucessfully loaded

Recommended Action Please Contact Cisco technical assistance center to recover the script

Error Message
MADM-SCRIPT_MGR- 3 -WEBSERVICES_ERROR : Exception thrown while processing web services for Script. Exception [String]

Explanation Exception thrown while processing web services for Script

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-SCRIPT_MGR- 2 -INVALID_SYSTEM_DIR : Invalid system script directory configured. Directory [String] Exception [String]

Explanation The configured system script directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-SCRIPT_MGR- 3 -SCRIPT_FILE_SUPPORT_FAILURE : Script file support failure. Exception [String]

Explanation The Script Manager can not register file support for script files; scripts will not be accesible from the script repository

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-SOCKET_MGR- 1 -MGR_PARTIAL_SERVICE : Socket Manager in partial service.

Explanation The Socket Manager is in partial service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-SOCKET_MGR- 6 -MGR_IN_SERVICE : Socket Manager in service.

Explanation The Socket Manager is in service

Recommended Action No actions needed

Error Message
MADM-SOCKET_MGR- 4 -MISSING_RESOURCE : Missing socket resources. Facility [String] Sub-Facility [String] Socket allocator id [String] Exception [String]

Explanation The socket manager is unable to locate internal socket resources

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-SOCKET_MGR- 5 -MGR_SHUTDOWN : Socket Manager in shutdown.

Explanation The Socket Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MADM-SOCKET_MGR- 4 -REQUEST_TIMEOUT : Requesting a socket timed out. Facility [String] Sub-Facility [String] Socket allocator id [String] Mnemonic [String] Thread [String] Time [Long]

Explanation Request to get a socket timed out

Recommended Action No actions needed

Error Message
MADM-SOCKET_MGR- 4 -REQUEST_FAILED : Requesting a socket failed. Facility [String] Sub-Facility [String] Socket allocator id [String] Mnemonic [String] Thread [String] Time [Long] Exception [String]

Explanation Request to get a socket failed

Recommended Action No actions needed

Error Message
MADM-SOCKET_MGR- 4 -REQUEST_BLOCKED : Invoking blocked allocation handler. Facility [String] Sub-Facility [String] Socket allocator id [String] Mnemonic [String] Thread [String] Time [Long] Handler [String]

Explanation The specified blocked allocation handler is being invoked for the specified socket request as the allocator queue could not accept it

Recommended Action No actions needed

Error Message
MADM-SOCKET_MGR- 6 -MGR_INITIALIZING : Socket Manager initializing.

Explanation The Socket Manager is initializing

Recommended Action No actions needed

Error Message
MADM-SOCKET_MGR- 2 -MGR_OUT_OF_SERVICE : Socket Manager in out of service.

Explanation The Socket Manager is out of service; allocators won't be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-SOCKET_MGR- 5 -MGR_SHUTTING_DOWN : Socket Manager shutting down.

Explanation The Socket Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MADM-SS_MRCP_ASR- 5 -SS_SHUTDOWN : Mrcp ASR subsystem is SHUTDOWN.

Explanation The Mrcp ASR subsystem has completed its shutdown

Recommended Action No actions needed

Error Message
MADM-SS_MRCP_ASR- 3 -SUBSYSTEM_MRCP_MEDIA_MANAGER_ERROR : MRCP Media Manager Error. Exception [String]

Explanation MRCP Media Manager Error

Recommended Action Stop Media Driver, restart system, if problem persist contact Cisco

Error Message
MADM-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_CHANNEL_ADDED_TO_GRP : Channel added to Group. Group Channel Type [String] Group id [Int] channel count [Int]

Explanation Channel added to Group

Recommended Action No actions needed

Error Message
MADM-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_MODIFY_PRVD_FAILED : Unable to modify provider. Provider Name [String] Exception [String]

Explanation Unable to modify

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-SS_MRCP_ASR- 3 -SS_OUT_OF_SERVICE : Mrcp ASR subsystem is OUT_OF_SERVICE.

Explanation Mrcp ASR subsystem is either disabled or failed to be loaded

Recommended Action Verify and update the configuration

Error Message
MADM-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_DESTROY_PRVD_FAILED : Specified provider could not be destroyed. Provider Name [String] Exception [String]

Explanation Specified provider could not be destroyed

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_CREATE_GRP_FAILED : Create Group failed. Group id [Int] Group Channel Type [String] Exception [String]

Explanation Create Group failed

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_SS_INIT_FAILED : Unable to initialize the Mrcp SS. Exception [String]

Explanation Unable to initialize the Mrcp SS

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-SS_MRCP_ASR- 6 -SS_ALREADY_INIT : Mrcp ASR Subsystem is already initialized.. Subsystem Name [String]

Explanation Mrcp ASR Subsystem is already initialized.

Recommended Action No actions needed

Error Message
MADM-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_CREAT_CHANNEL_FAILED : Create Channel failed. Channel Type [String] Exception [String]

Explanation Create Channel failed

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_NO_SERVER_FOUND : No MRCP Speech Server found for group.. Group id [Int]

Explanation No MRCP Speech Server found for group.

Recommended Action Verify and update the configuration

Error Message
MADM-SS_MRCP_ASR- 1 -SS_PARTIAL_SERVICE : Mrcp ASR subsystem is in PART_SERVICE.

Explanation The Mrcp ASR subsystem is in partial service

Recommended Action Verify and update the configuration

Error Message
MADM-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_REMOVE_GRP_LISTENER : Mrcp ASR removes self as a group listener. Channel Type [String]

Explanation Mrcp ASR removes self as a group listener

Recommended Action No actions needed

Error Message
MADM-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_ADD_CHANNEL_TO_GRP_FAILED : Add Channel to group failed. Group Channel Type [String] Group id [Int] channel count [Int] Exception [String]

Explanation Add Channel to group failed

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_REFRESH_PRVD_FAILED : Could not refresh specified provider. Method Name [String] Provider Name [String] Exception [String]

Explanation Could not refresh specified provider

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_DISPOSE_GRP : Mrcp ASR disposed this Group during shutdown. Group id [Int]

Explanation Mrcp ASR disposed this Group during shutdown

Recommended Action No actions needed

Error Message
MADM-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_GROUP_TYPE_NULL : Group Type is null. Method Name [String] Group id [Int]

Explanation Group Type is null

Recommended Action No actions needed

Error Message
MADM-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_DISPOSE_GRP_FAILED : Mrcp ASR failed to dispose a group. Group id [Int] Exception [String]

Explanation Mrcp ASR failed to dispose a group

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-SS_MRCP_ASR- 6 -SS_IN_SERVICE : Mrcp ASR subsystem IN_SERVICE.

Explanation The Mrcp ASR subsystem is in full service

Recommended Action No actions needed

Error Message
MADM-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_NEED_REMOVE_CHANNEL_FROM_GROUP : Notified By AppAdmin to remove some channels. Group id [Int] Group Channel Type [String] CHANNEL REMOVE [Int]

Explanation Notified By AppAdmin to remove some channels

Recommended Action No actions needed

Error Message
MADM-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_CHANNEL_TYPE_NULL : Channel Type is null. Channel id [Int]

Explanation Channel Type is null

Recommended Action No actions needed

Error Message
MADM-SS_MRCP_ASR- 6 -SS_INITIALIZING : Mrcp ASR subsystem initializing.

Explanation The Mrcp ASR subsystem is initializing

Recommended Action No actions needed

Error Message
MADM-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_MODIFY_GRP_FAILED : Modify group failed, group could not be added.. Provider Name [String] Group id [Int] Exception [String]

Explanation Modify group failed, group could not be added.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_START_MONITOR_FAILED : Monitor for the specified provider could not be started. Provider Name [String] Exception [String]

Explanation Monitor for the specified provider could not be started

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_GET_GRP_FAILED : Could not get the group with the specified id. Group id [Int] Exception [String]

Explanation Could not get the group with the specified id

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_COULD_NOT_CHANGE_GRP_STATE : Unable to change state of Group. Channel id [Int] Provider Name [String]

Explanation Unable to change state of Group

Recommended Action No actions needed

Error Message
MADM-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_CHANNEL_CREATED : Channel created. Channel Type [String] Channel id [Int]

Explanation Channel created

Recommended Action No actions needed

Error Message
MADM-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_GRP_REPOSITORY_DATA_NULL : Data received from Group repository is null. Method Name [String]

Explanation Data received from Group repository is null

Recommended Action No actions needed

Error Message
MADM-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_GROUP_TYPE_NOT_SUPPORTED : Group Type not supported. Method Name [String] Group id [Int] Group Channel Type [String]

Explanation Group Type not supported

Recommended Action No actions needed

Error Message
MADM-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_CREATE_PRVD_FAILED : Could not create provider. Method Name [String] Provider Name [String] Exception [String]

Explanation Could not create provider

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_MODIFICATION_NOT_NEED : Currently has exact nbr of channels as req by AppAdmin. Group id [Int] Group Channel Type [String]

Explanation Currently has exact nbr of channels as req by AppAdmin

Recommended Action No actions needed

Error Message
MADM-SS_MRCP_ASR- 5 -SS_SHUTTING_DOWN : Mrcp ASR subsystem is SHUTTING_DOWN.

Explanation The Mrcp ASR subsystem is in the process of shutting down

Recommended Action No actions needed

Error Message
MADM-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_DISPOSE_CHANNEL_FAILED : Mrcp ASR failed to dispose a Channel. Exception [String]

Explanation Mrcp ASR failed to dispose a Channel

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_GET_PRVD_FAILED : Error retrieving provider data. Method Name [String] Provider Name [String] Exception [String]

Explanation Error retrieving provider data

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_NEED_ADD_CHANNEL_TO_GROUP : Notified By AppAdmin to add more channels. Group id [Int] Group Channel Type [String] CHANNEL ADD [Int]

Explanation Notified By AppAdmin to add more channels

Recommended Action No actions needed

Error Message
MADM-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_REGISTER_SS_MRCP_ASR_AS_GRP_LISTENER : Mrcp ASR registered self as a Group event listener. Method Name [String] Channel Type [String]

Explanation Mrcp ASR registered self as a Group event listener

Recommended Action No actions needed

Error Message
MADM-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_CREATE_GRP_MAP_FAILED : Error creating group-server mapping for the specified provider. Provider Name [String] Exception [String]

Explanation Error creating group-server mapping for the specified provider

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_CLASS_DIALOGCHANNEL_NOT_FOUND : Class for the specified Dialog Channel was not found. Method Name [String] DIALOG CHANNEL CLASS [String] Exception [String]

Explanation Class for the specified Dialog Channel was not found

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-USER_MGR- 4 -NAME_GRAMMAR_GENERATION_NOT_ALLOWED : Name Grammar Generation not allowed unless in MIVR or MADM.

Explanation Name Grammar Generation not allowed unless in MIVR or MADM

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-USER_MGR- 1 -MGR_PARTIAL_SERVICE : User Manager in partial service.

Explanation The User Manager is in partial service

Recommended Action Investigate as required

Error Message
MADM-USER_MGR- 4 -DB_CORRUPTION_ILLEGAL_VALUE : Possible Call Manager database corruption due to an illegal value. Table name [String] Column name [String] Column value [String]

Explanation Possible Call Manager database corruption due to an illegal value

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-USER_MGR- 3 -NAME_GRAMMAR_SCHEDULE_UPDATE_FAILED : Name Grammar schedule update failed. Exception [String]

Explanation The User Manager failed to update automatic Name Grammar Generator schedule; Name To User may not function

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-USER_MGR- 3 -UNEXPECTED_EXCEPTION : Unexpected exception thrown. Exception [String]

Explanation Unexpected exception thrown

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-USER_MGR- 4 -FILE_IO_ERROR : Error occurred during file I/O. Exception [String]

Explanation Error occurred during file I/O

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-USER_MGR- 4 -DB_CORRUPTION_EMPTY_VALUE : Possible Call Manager database corruption due to empty required value. Table name [String] Column name [String] Row [Int]

Explanation Possible Call Manager database corruption due to empty required value

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-USER_MGR- 4 -NAME_GRAMMAR_UPDATE_STATUS_FAILED : Name Grammar Generation status update failed. Exception [String]

Explanation The User Manager failed to update Name Grammar Generation Status. The status information may be incorrect.

Recommended Action No actions needed

Error Message
MADM-USER_MGR- 6 -MGR_INITIALIZING : User Manager initializing.

Explanation The User Manager is initializing

Recommended Action No actions needed

Error Message
MADM-USER_MGR- 5 -MGR_SHUTTING_DOWN : User Manager shutting down.

Explanation The User Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MADM-USER_MGR- 2 -MGR_OUT_OF_SERVICE : User Manager in out of service.

Explanation The User Manager is out of service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-USER_MGR- 3 -INIT_FAILED : User Manager failed to initialize. Exception [String]

Explanation An exception has occurred during the initialization of the User Manager

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-USER_MGR- 3 -NAME_GRAMMAR_UPDATE_CONFIG_FAILED : Name Grammar configuration update failed. Exception [String]

Explanation The User Manager failed to update Name Grammar Generation Configuration; Name To User may not function

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-USER_MGR- 1 -CANNOT_CREATE_SYSTEM_USER : Caller cannot create a System User. Exception [String]

Explanation An unauthorized class has attempted to create an instance of a System User.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-USER_MGR- 4 -AUDIO_FORMAT_ERROR : Wrong audio format in stream. Exception [String]

Explanation Wrong audio format in stream

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-USER_MGR- 3 -NAME_GRAMMAR_GENERATION_FAILED : Name Grammar generation failed. Exception [String]

Explanation The User Manager was unable to generate the Name Grammars; Name To User may not function

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MADM-USER_MGR- 6 -MGR_IN_SERVICE : User Manager in service.

Explanation The User Manager is in service

Recommended Action No actions needed

Error Message
MADM-USER_MGR- 4 -STREAM_IO_ERROR : Error occurred during stream I/O. Exception [String]

Explanation Error occurred during stream I/O

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-USER_MGR- 5 -MGR_SHUTDOWN : User Manager in shutdown.

Explanation The User Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MADM-USER_MGR- 4 -DB_CORRUPTION_BAD_VALUE_FORMAT : Possible Call Manager database corruption due to bad value format. Table name [String] Column name [String] Column value [String] Exception [String]

Explanation Possible Call Manager database corruption due to bad value format

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-USER_MGR- 4 -DB_CORRUPTION_MISSING_COLUMN : Possible Call Manager database corruption due to missing column. Table name [String] Column name [String] Exception [String]

Explanation Possible Call Manager database corruption due to missing column

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-USER_MGR- 3 -CONFIG_LISTENER_INIT_FAILED : Unable to register config listener. Exception [String]

Explanation Unable to register config listener for UserGrammarConfig; Name To User may not function

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-USER_MGR- 3 -NO_SYSTEM_PAYLOAD : System payload type could not be determined.

Explanation System payload type could not be determined

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MADM-USER_MGR- 5 -CLUSTER_ID_CHANGED : Cluster ID has changed.. Previous Cluster ID [String] Current Cluster ID [String]

Explanation Cluster ID has changed. This is a rare but normal condition. It can occur after a restore operation following a re-install. Users whose cluster specific data was modified after the re-install but before the restore will lose those modifications.

Recommended Action No actions needed

Error Message
MADM-USER_MGR- 4 -DB_CORRUPTION_NON_UNIQUE_KEY : Possible Call Manager database corruption due to non unique key. Table name [String] Column name [String] Key value [String]

Explanation Possible Call Manager database corruption due to non unique key

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MBSP-BOOTSTRAP_MGR- 1 -MGR_PARTIAL_SERVICE : Bootstrap Manager in partial service.

Explanation The Bootstrap Manager is in partial service

Recommended Action Investigate as required

Error Message
MBSP-BOOTSTRAP_MGR- 3 -BOOTSTRAP_NODE_JOIN_ERROR : Failed to sync bootstrap repository during node join. A description for the nature of the exception [String] Exception [String]

Explanation Failed to sync bootstrap repository during node join

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MBSP-BOOTSTRAP_MGR- 3 -BOOTSTRAP_SYNC_ERROR : Synchronize bootstrap repository error. A description for the nature of the exception [String] Exception [String]

Explanation Failed to synchronize the bootstrap repository between nodes

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MBSP-BOOTSTRAP_MGR- 3 -BOOTSTRAP_REMOVE_LISTENER_ERROR : Failed to remove the BootstrapListener. A description for the nature of the exception [String] Exception [String]

Explanation Failed to remove the BootstrapListener

Recommended Action Restart server

Error Message
MBSP-BOOTSTRAP_MGR- 6 -MGR_IN_SERVICE : Bootstrap Manager in service.

Explanation The Bootstrap Manager is in service

Recommended Action No actions needed

Error Message
MBSP-BOOTSTRAP_MGR- 3 -BOOTSTRAP_ADD_LISTENER_ERROR : Failed to add the BootstrapListener. A description for the nature of the exception [String] Exception [String]

Explanation Failed to add the BootstrapListener

Recommended Action Restart server

Error Message
MBSP-BOOTSTRAP_MGR- 3 -BOOTSTRAP_INIT_ERROR : Bootstrap Manager initialization error. A description for the nature of the exception [String] Exception [String]

Explanation The Bootstrap Manager has failed on initialzation

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MBSP-BOOTSTRAP_MGR- 5 -MGR_SHUTDOWN : Bootstrap Manager in shutdown.

Explanation The Bootstrap Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MBSP-BOOTSTRAP_MGR- 3 -BOOTSTRAP_NODE_REMOVE_ERROR : Bootstrap failed to remove node from cluster profile. A description for the nature of the exception [String] Exception [String]

Explanation Bootstrap failed to remove node from cluster profile

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MBSP-BOOTSTRAP_MGR- 6 -MGR_INITIALIZING : Bootstrap Manager initializing.

Explanation The Bootstrap Manager is initializing

Recommended Action No actions needed

Error Message
MBSP-BOOTSTRAP_MGR- 2 -MGR_OUT_OF_SERVICE : Bootstrap Manager in out of service.

Explanation The Bootstrap Manager is out of service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MBSP-BOOTSTRAP_MGR- 5 -MGR_SHUTTING_DOWN : Bootstrap Manager shutting down.

Explanation The Bootstrap Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MBSP-BOOTSTRAP_MGR- 3 -BOOTSTRAP_NODE_ADD_ERROR : Bootstrap failed to add new node to cluster profile. A description for the nature of the exception [String] Exception [String]

Explanation Bootstrap failed to add new node to cluster profile

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCET-BOOTSTRAP_MGR- 1 -MGR_PARTIAL_SERVICE : Bootstrap Manager in partial service.

Explanation The Bootstrap Manager is in partial service

Recommended Action Investigate as required

Error Message
MCET-BOOTSTRAP_MGR- 3 -BOOTSTRAP_NODE_JOIN_ERROR : Failed to sync bootstrap repository during node join. A description for the nature of the exception [String] Exception [String]

Explanation Failed to sync bootstrap repository during node join

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCET-BOOTSTRAP_MGR- 3 -BOOTSTRAP_SYNC_ERROR : Synchronize bootstrap repository error. A description for the nature of the exception [String] Exception [String]

Explanation Failed to synchronize the bootstrap repository between nodes

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCET-BOOTSTRAP_MGR- 3 -BOOTSTRAP_REMOVE_LISTENER_ERROR : Failed to remove the BootstrapListener. A description for the nature of the exception [String] Exception [String]

Explanation Failed to remove the BootstrapListener

Recommended Action Restart server

Error Message
MCET-BOOTSTRAP_MGR- 6 -MGR_IN_SERVICE : Bootstrap Manager in service.

Explanation The Bootstrap Manager is in service

Recommended Action No actions needed

Error Message
MCET-BOOTSTRAP_MGR- 3 -BOOTSTRAP_ADD_LISTENER_ERROR : Failed to add the BootstrapListener. A description for the nature of the exception [String] Exception [String]

Explanation Failed to add the BootstrapListener

Recommended Action Restart server

Error Message
MCET-BOOTSTRAP_MGR- 3 -BOOTSTRAP_INIT_ERROR : Bootstrap Manager initialization error. A description for the nature of the exception [String] Exception [String]

Explanation The Bootstrap Manager has failed on initialzation

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCET-BOOTSTRAP_MGR- 5 -MGR_SHUTDOWN : Bootstrap Manager in shutdown.

Explanation The Bootstrap Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MCET-BOOTSTRAP_MGR- 3 -BOOTSTRAP_NODE_REMOVE_ERROR : Bootstrap failed to remove node from cluster profile. A description for the nature of the exception [String] Exception [String]

Explanation Bootstrap failed to remove node from cluster profile

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCET-BOOTSTRAP_MGR- 6 -MGR_INITIALIZING : Bootstrap Manager initializing.

Explanation The Bootstrap Manager is initializing

Recommended Action No actions needed

Error Message
MCET-BOOTSTRAP_MGR- 2 -MGR_OUT_OF_SERVICE : Bootstrap Manager in out of service.

Explanation The Bootstrap Manager is out of service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCET-BOOTSTRAP_MGR- 5 -MGR_SHUTTING_DOWN : Bootstrap Manager shutting down.

Explanation The Bootstrap Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MCET-BOOTSTRAP_MGR- 3 -BOOTSTRAP_NODE_ADD_ERROR : Bootstrap failed to add new node to cluster profile. A description for the nature of the exception [String] Exception [String]

Explanation Bootstrap failed to add new node to cluster profile

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-ADM_CFG- 3 -ADM_EXCEPTION : Unknown ADM Exception. Exception [String]

Explanation Unknown ADM Exception

Recommended Action Verify and update the configuration

Error Message
MCVD-BOOTSTRAP_MGR- 1 -MGR_PARTIAL_SERVICE : Bootstrap Manager in partial service.

Explanation The Bootstrap Manager is in partial service

Recommended Action Investigate as required

Error Message
MCVD-BOOTSTRAP_MGR- 3 -BOOTSTRAP_NODE_JOIN_ERROR : Failed to sync bootstrap repository during node join. A description for the nature of the exception [String] Exception [String]

Explanation Failed to sync bootstrap repository during node join

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-BOOTSTRAP_MGR- 3 -BOOTSTRAP_SYNC_ERROR : Synchronize bootstrap repository error. A description for the nature of the exception [String] Exception [String]

Explanation Failed to synchronize the bootstrap repository between nodes

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-BOOTSTRAP_MGR- 3 -BOOTSTRAP_REMOVE_LISTENER_ERROR : Failed to remove the BootstrapListener. A description for the nature of the exception [String] Exception [String]

Explanation Failed to remove the BootstrapListener

Recommended Action Restart server

Error Message
MCVD-BOOTSTRAP_MGR- 6 -MGR_IN_SERVICE : Bootstrap Manager in service.

Explanation The Bootstrap Manager is in service

Recommended Action No actions needed

Error Message
MCVD-BOOTSTRAP_MGR- 3 -BOOTSTRAP_ADD_LISTENER_ERROR : Failed to add the BootstrapListener. A description for the nature of the exception [String] Exception [String]

Explanation Failed to add the BootstrapListener

Recommended Action Restart server

Error Message
MCVD-BOOTSTRAP_MGR- 3 -BOOTSTRAP_INIT_ERROR : Bootstrap Manager initialization error. A description for the nature of the exception [String] Exception [String]

Explanation The Bootstrap Manager has failed on initialzation

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-BOOTSTRAP_MGR- 5 -MGR_SHUTDOWN : Bootstrap Manager in shutdown.

Explanation The Bootstrap Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MCVD-BOOTSTRAP_MGR- 3 -BOOTSTRAP_NODE_REMOVE_ERROR : Bootstrap failed to remove node from cluster profile. A description for the nature of the exception [String] Exception [String]

Explanation Bootstrap failed to remove node from cluster profile

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-BOOTSTRAP_MGR- 6 -MGR_INITIALIZING : Bootstrap Manager initializing.

Explanation The Bootstrap Manager is initializing

Recommended Action No actions needed

Error Message
MCVD-BOOTSTRAP_MGR- 2 -MGR_OUT_OF_SERVICE : Bootstrap Manager in out of service.

Explanation The Bootstrap Manager is out of service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-BOOTSTRAP_MGR- 5 -MGR_SHUTTING_DOWN : Bootstrap Manager shutting down.

Explanation The Bootstrap Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MCVD-BOOTSTRAP_MGR- 3 -BOOTSTRAP_NODE_ADD_ERROR : Bootstrap failed to add new node to cluster profile. A description for the nature of the exception [String] Exception [String]

Explanation Bootstrap failed to add new node to cluster profile

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CFG_MGR- 3 -REPOSITORY_ACCESSOR_INIT_ERROR : Failed to initialize the accessor. Name [String]

Explanation Error in initializing repository accessor

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 1 -MGR_PARTIAL_SERVICE : Config Manager in partial service. Reason [String]

Explanation The Config Manager is in partial service due to CDS not yet activated or failed to register RMI for notification

Recommended Action Please check whether CDS is activated in the clusteror CVD to regsiter RMI for notification

Error Message
MCVD-CFG_MGR- 3 -DB_ACCESS_ERROR : Database Access error. Action [String] Table [String] Exception [String]

Explanation Error while accessing Data Base

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 3 -BULK_UPDATE_ERROR : Error in Bulk update. action [String] Exception [String]

Explanation Error in bulk update

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 6 -STUB_HASCHANGED : ConfigStubImpl hasChanged(). Exception [String]

Explanation information

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 3 -SAVE_FAILED : saving failed . Exception [String]

Explanation ConfigObject saving failed

Recommended Action ConfigObject saving failed

Error Message
MCVD-CFG_MGR- 6 -CONFIG_SCHEMA_CHANGE : ConfigSchema change. Schema_Ver [String]

Explanation Change in ConfigSchema

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 3 -CLUSTER_INFO_PORT_SAVE_ERR : Error in updating Bootstrap ini file. value [String] Exception [String]

Explanation Error in updating Bootstrap ini file with RMI port

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 3 -CLUSTER_INFO_HOST_SAVE_ERR : Error in updating Bootstrap ini file. Exception [String]

Explanation Error in updating Bootstrap ini file with local host ip

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 3 -GET_ACCESSOR_ERR : Error in finding repository accessors. Name [String] Exception [String]

Explanation Error in finding repository accessors information

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 6 -SCHEMA_EXISTS : ConfigSchema Register failed. Exception [String]

Explanation information

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 6 -MGR_INITIALIZING : Config Manager initializing.

Explanation The Config Manager is initializing

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 5 -MGR_SHUTTING_DOWN : Config Manager shutting down.

Explanation The Config Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 2 -MGR_OUT_OF_SERVICE : Config Manager in out of service.

Explanation The Config Manager is out of service; configuration will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CFG_MGR- 6 -NO_BASERECORD : No base record.

Explanation No base record for this config object

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 3 -LOCAL_AND_REMOTE_PROPERTIES_HAVE_DIFFERENT_VERSIONS : Local and remote properties have different versions. Properties name [String] Remote properties version [String] Local properties version [String] Merge result [String]

Explanation The properties being merged are of different versions

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CFG_MGR- 3 -CONFIG_SCHEMAS_LOAD_ERROR : Interrupted while loading configschemas. Name [String] Exception [String]

Explanation Error in loading config schemas

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 3 -READ_REAPOSIOTRY_ACCCESSORS : Error in reading repository accessors from applciation properties. Name [String] Exception [String]

Explanation Error in reading repository accessors information from applciation properties

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 6 -MGR_IN_SERVICE : Config Manager in service.

Explanation The Config Manager is in service

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 3 -CONFIG_MGR_GET_REMOTEPROP_ERROR : Config Manager get remote properties failed. Properties name [String] Exception [String]

Explanation Config Manager get remote properties failed

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CFG_MGR- 3 -CONFIG_OBJECT_SAVE_FAIL : saving failed due to missing values for keys defined in configSchema. configObejct [String] Reason [String] Exception [String]

Explanation saving failed due to missing values for keys defined in configSchema

Recommended Action Check the values for keys defined in the configSchema

Error Message
MCVD-CFG_MGR- 5 -MGR_SHUTDOWN : Config Manager in shutdown.

Explanation The Config Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 3 -PARSE_ERROR : Error in converiting data. ToBeParsed [String] Table [String] Exception [String]

Explanation Error in parsing

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 3 -PROFILE_INFO_ACCESS_ERR : Error in accessing profile ini file. Exception [String]

Explanation Error in accessing profile ini file

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 2 -CFG_MGR_INSTANCE_NULL : Config Manager instance is null.

Explanation The Config Manager instance is null; configuration will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CFG_MGR- 3 -CLUSTER_DOWN_ERROR : Cluster Manager is not initialized. Description [String] Exception [String]

Explanation Cluster Manager is not initialized

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CFG_MGR- 3 -DELETE_ERROR : Delete failed. Exception [String]

Explanation ConfigObjects deletion for this query failed

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 3 -INVALID_REPOSITORY_ACCESSOR : Repository accessor is invalid. Exception [String]

Explanation Repository accessor is invalid

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 3 -READ_ERROR : object read error. Exception [String]

Explanation Error in reading

Recommended Action Error in reading

Error Message
MCVD-CFG_MGR- 3 -CONFIG_OBJECT_CORRUPTED : Error while reading config. Probably it was corrupt. Config Class [String] Exception [String]

Explanation Error while reading the blob data of the config

Recommended Action Run the CLI command 'show uccx tech dbserver integrity' to check and recover from any corrupted config objects

Error Message
MCVD-CFG_MGR- 3 -CONFIG_MGR_GENERAL_ERROR : Config Manager has exception. Error message [String] Exception [String]

Explanation Config Manager has exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CFG_MGR- 3 -CLUSTER_RMI_REBIND_FAILED : Unable to register remote interface in cluster space. Exception [String]

Explanation A remote interface could not be binded to the cluster space; Config data may not be accessible form Editor

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CFG_MGR- 6 -NO_DB_RECORD : No record in DB.

Explanation No record in DB

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 3 -NOTIFICATION_ERROR : Failed to notify other remote config managers. Action [String] Exception [String]

Explanation Error in notifying other remote config managers

Recommended Action No actions needed

Error Message
MCVD-CFG_MGR- 2 -CONFIG_MGR_OUT_OF_SERVICE : Config Manager in out of service. Exception [String]

Explanation The Config Manager is out of service; configuration will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CLUSTER_MGR- 3 -MANAGER_INITIALIZING_ERROR : Cluster Manager is not initialized. Exception [String]

Explanation Cluster Manager is not initialized

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CLUSTER_MGR- 4 -REMOTE_EXCEPTION_1 : Can not communicate with CVD. errCnt [Int] Cmd [String] Exception [String]

Explanation Cluster Manager can not communicate with CVD on the local node

Recommended Action No actions needed

Error Message
MCVD-CLUSTER_MGR- 3 -REMOTE_EXCEPTION_2 : Can not communicate with CVD. errCnt [Int] Exception [String]

Explanation Cluster Manager can not communicate with CVD on the local node

Recommended Action No actions needed

Error Message
MCVD-CLUSTER_MGR- 3 -LICENSE_OBSERVER_ERROR : Cluster Manager can not register license observer. Exception [String]

Explanation Cluster Manager can not register license observer

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CLUSTER_MGR- 2 -RESTART_REQUESTED : Cluster Manager requests to restart process. reason [String]

Explanation Cluster Manager detects some problem that prevents its functionality, and requests restart

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CLUSTER_MGR- 3 -COMPONENT_PRIMARY_CHANGED_ERROR : Component change primary, but it is not supported. type [String] nodeId [Int]

Explanation Component change primary, but it is not supported

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CLUSTER_MGR- 3 -COMPONENT_CLEAR_PRIMARY_NOT_SUPPORTED : Clear Primary operation is not supported for the Component. type [String] nodeId [Int]

Explanation Clear Primary operation is not supported for the Component

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CLUSTER_MGR- 6 -MANAGER_INITIALIZING_COMPLETED : Cluster Manager initialization successfully completed.

Explanation Cluster Manager initialization successfully completed

Recommended Action No actions needed

Error Message
MCVD-CLUSTER_MGR- 3 -READ_ERROR_CLUSTER_NAME : Cannot read cluster name. Exception [String]

Explanation Cannot read cluster name from ccndir.ini

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CLUSTER_MGR- 3 -GET_PUBLISHER_TIMEOUT_ERROR : Cluster Manager can not get Timeout value from Windows Registry. Exception [String]

Explanation Cluster Manager can not get Timeout value from Windows Registry. Use default timeout: 2 hours

Recommended Action No actions needed

Error Message
MCVD-CLUSTER_MGR- 3 -MASTER_SERVICE_NOT_FOUND : Master service not found. UniqueId [Int] nodeId [Int] Cmd [String]

Explanation Master service not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CLUSTER_MGR- 3 -ILLEGAL_CLUSTER_NAME : Cluster name is illegal. name [String]

Explanation Cluster name is illegal

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CLUSTER_MGR- 3 -CONVERGENCE_NOT_FOUND_ERROR : Convergence not found. name [String]

Explanation Convergence not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CLUSTER_MGR- 3 -GET_NODE_UPDATE_ERRORR : Can not communicate with CVD. Exception [String]

Explanation Cluster Manager can not communicate with CVD on the local node

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CLUSTER_MGR- 3 -NODE_NOT_FOUND_FOR_CMD : Cluster Manager dispatcher can not process cmd: unknown Node. Cmd [String]

Explanation Cluster Manager dispatcher can not process cmd: unknown Node

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CLUSTER_MGR- 4 -COMPONENT_ALREADY_PRIMARY : Component is already primary. type [String] nodeId [Int]

Explanation Component is already primary

Recommended Action No actions needed

Error Message
MCVD-CLUSTER_MGR- 4 -MASTER_UPDATE_ERROR : Cluster Manager can not update master. nodeId [Int] Cmd [String]

Explanation Cluster Manager can not update master, it try to re-sync all states with CVD on the local Node

Recommended Action No actions needed

Error Message
MCVD-CLUSTER_MGR- 3 -SET_VMOPTION_ERROR : Cluster Manager can not execute SetVMOption. Exception [String]

Explanation Cluster Manager can not execute SetVMOption

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CLUSTER_MGR- 3 -SERVICE_ID_NOT_FOUND_ERROR : Service not found. UniqueId [Int] nodeId [Int] Cmd [String]

Explanation Service not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CLUSTER_MGR- 3 -COMPONENT_CLEAR_PRIMARY_ERROR : Clear Primary operation is not applicable to non-primary Component. type [String] nodeId [Int]

Explanation Clear Primary operation is not applicable to non-primary Component

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CLUSTER_MGR- 3 -NODE_UPDATE_ERROR : Cluster Manager can not update node from command. nodeId [Int] Cmd [String]

Explanation Cluster Manager can not update node from command

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CLUSTER_MGR- 3 -COMPONENT_ID_NOT_FOUND_ERROR : Component not found. UniqueId [Int] nodeId [Int] Cmd [String]

Explanation Component not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CLUSTER_MGR- 3 -REMOTE_NOTIFY_1 : Can not communicate with CVD. Context [String] Cmd [String] Exception [String]

Explanation Cluster Manager can not communicate with CVD on the local node

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CLUSTER_MGR- 6 -COMPONENT_PRIMARY_REMOVED : Component is removed, but it is primary. type [String] nodeId [Int]

Explanation Component is removed, but it is primary

Recommended Action No actions needed

Error Message
MCVD-CLUSTER_MGR- 3 -CLUSTER_SNAPSHOT_ON_ERROR : Cluster snapshot when error. cluster [String]

Explanation Cluster snapshot when error

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CLUSTER_MGR- 3 -READ_CLUSTER_ERROR : Cluster Manager can not read Cluster data from ClusterSnapshotCmdImpl. Exception [String]

Explanation Cluster Manager can not read Cluster data from ClusterSnapshotCmdImpl

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CLUSTER_MGR- 3 -COMPONENT_SET_PRIMARY_NOT_SUPPORTED : Set Primary operation is not supported for the Component. type [String] nodeId [Int]

Explanation Set Primary operation is not supported for the Component

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CLUSTER_MGR- 3 -NODE_READ_ERROR : Cluster Manager can not read node from command. Cmd [String] Exception [String]

Explanation Cluster Manager can not read node from command

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CLUSTER_MGR- 0 -JMS_BROKER_SERVICE_START_ERROR : A KeepAlive exception has been thrown in Manager Manager. Exception [String]

Explanation Due to JMS service start failure a KeepAlive exception has been thrown in Cluster Manager

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CLUSTER_MGR- 2 -MASTER_ELECTION_ERROR : Master Election Error - too many masters. Context [String] name [String] nodeId [Int] otherNodeId [Int] reason [String]

Explanation Master Election Error - too many masters. Cluster Manager restart process

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CLUSTER_MGR- 3 -MEMORY_DUMP_ERROR : Cluster Manager can not execute Memory Dump. Exception [String]

Explanation Cluster Manager can not execute Memory Dump

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CLUSTER_MGR- 3 -SEMAPHORE_NOT_FOUND_ERROR : Cluster Manager can not find semaphore. Cmd [String]

Explanation Cluster Manager can not find semaphore

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CLUSTER_MGR- 4 -NODE_INVALID : Node Is invalid. nodeId [Int] reason [String]

Explanation Node Is invalid, it should be recovered from Installer

Recommended Action Reinstall server

Error Message
MCVD-CLUSTER_MGR- 3 -NODE_SYNCHRONIZE_STATE_ERROR : Cluster Manager can not synchronize state for node. nodeId [Int]

Explanation Cluster Manager can not synchronize state for node, and will be restarted.

Recommended Action No actions needed

Error Message
MCVD-CLUSTER_MGR- 3 -ACCESS_CONFIG_DATA_ERROR : Cluster Manager can not access configuration data. Exception [String]

Explanation Cluster Manager can not access configuration data

Recommended Action Verify that Configuration data is available. If problem persist contact Cisco technical assistance center

Error Message
MCVD-CLUSTER_MGR- 4 -DYNAMIC_LICENSE_NOT_DEFINED : Dynamic license is not defined.

Explanation Dynamic license is not defined

Recommended Action No actions needed

Error Message
MCVD-CLUSTER_MGR- 2 -THROWS_KEEP_ALIVE_EXCEPTION : Cluster Manager throws KeepAlive Exception. Exception [String]

Explanation Cluster Manager detects some problem that prevents its functionality, and will be restarted

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CLUSTER_MGR- 3 -MANAGER_DISPATCH_ERROR : Can not process command. Cmd [String] Exception [String]

Explanation Cluster Manager can not process command from CVD

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 3 -COMPONENT_SWITCH_PUBLISHER_ERROR : Component replicationManager.switchPublisher error. type [String] nodeId [Int] Exception [String]

Explanation Component replicationManager.switchPublisher error

Recommended Action Repeat operation. Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -NODE_RESTART_ERROR : CVD can not restart local Node. Exception [String]

Explanation CVD can not restart Node

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 6 -HEARTBEAT_REMOVE_NODE : CVD is processing Remove Node cmd. nodeId [Int] ip [String]

Explanation CVD is processing Remove Node heartbeat

Recommended Action No actions needed

Error Message
MCVD-CVD- 3 -POSTPONED_CMD_TIMEOUT : CVD detects timeout while processing PostponedCmdQueue. dt [Long] Cmd [String]

Explanation CVD detects timeout while processing PostponedCmdQueue

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 4 -COMPONENT_ALREADY_DISABLED : Component already disabled. type [String] nodeId [Int]

Explanation Component already disabled

Recommended Action No actions needed

Error Message
MCVD-CVD- 3 -MODEL_NOT_FOUND : Model not found. model [String] points [String]

Explanation Model not found

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 3 -AUTO_ADD_TO_CLUSTER_ERROR : Auto Add to Cluster Error. Exception [String]

Explanation Auto Add to Cluster Error

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 3 -SERVICE_DEACTIVATE_ERROR : Node Manager can not deactivate service. name [String] Exception [String]

Explanation Node Manager can not deactivate service

Recommended Action Repeat operation. Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 2 -RESTART_REQUESTED : CVD requests to restart itself. reason [String]

Explanation CVD detects some problem that prevents its functionality, and requests restart

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 3 -NODE_CONFIG_ERROR : Cannot retrieve node configuration. Config [String] Exception [String]

Explanation Cannot retrieve node configuration from Config

Recommended Action Investigate as required

Error Message
MCVD-CVD- 3 -NODE_DEACTIVATE_ERROR : CVD can not deactivate local Node. Exception [String]

Explanation CVD can not deactivate local Node

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 5 -HEARTBEAT_MISSING_HEARTBEAT : CVD does not receive heartbeat from node for a long period. nodeId [Int] dt [Long]

Explanation CVD does not receive heartbeat from node for a long period

Recommended Action No actions needed

Error Message
MCVD-CVD- 3 -SERVICE_INVALID : Service became invalid. nodeId [Int] name [String]

Explanation Service became invalid, because it carashed a few times

Recommended Action Reinstall server

Error Message
MCVD-CVD- 4 -COMPONENT_MAX_ENABLED_REACHED : Component already enabled. type [String] nodeId [Int] enabledCnt [Int]

Explanation CVD can not enable Component, because max number of enabled components already has been reached

Recommended Action No actions needed

Error Message
MCVD-CVD- 4 -HEARTBEAT_SUSPECT_NODE_CRASH : CVD suspects node crash. state [String] nodeInfo [String] dt [Long]

Explanation CVD suspects node crash, because it does not receive heartbeats

Recommended Action No actions needed

Error Message
MCVD-CVD- 3 -NODE_MODIFY_CFGERROR : Cannot modify node configuration. Exception [String]

Explanation Cannot modify node configuration from Config

Recommended Action Investigate as required

Error Message
MCVD-CVD- 3 -COMPONENT_SET_CDS_ERROR : Component ConfigDataLinker.setCds error. type [String] nodeId [Int] Exception [String]

Explanation Component ConfigDataLinker.setCds error

Recommended Action Repeat operation. Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -SEND_CMD_ERROR : CVD can not send command to the subscriber. Cmd [String] subscriber [String] errCnt [Int]

Explanation CVD can not send command to the subscriber, max error number has been reached

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 3 -COMPONENT_REMOVE_ERROR : Component remove error. type [String] nodeId [Int] Exception [String]

Explanation Component remove error

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 6 -CVD_INITIALIZING_COMPLETED : CVD initialization successfully completed.

Explanation CVD initialization successfully completed

Recommended Action No actions needed

Error Message
MCVD-CVD- 4 -COMPONENT_ALREADY_ENABLED : Component already enabled. type [String] nodeId [Int]

Explanation Component already enabled

Recommended Action No actions needed

Error Message
MCVD-CVD- 3 -COMPONENT_DISABLE_ERROR : Component disabled error. type [String] nodeId [Int] Exception [String]

Explanation Component disabled error

Recommended Action Repeat operation. Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 4 -SERVICE_STOP_LAST_ADMIN : CVD can not stop last running AppAdmin service. name [String] nodeId [Int]

Explanation CVD can not stop last running AppAdmin service

Recommended Action No actions needed

Error Message
MCVD-CVD- 4 -COMPONENT_ALREADY_VALID : Component is already valid. type [String] nodeId [Int]

Explanation Component is already valid

Recommended Action No actions needed

Error Message
MCVD-CVD- 3 -NODE_REMOVE_ERROR : CVD can not remove node from Config. nodeId [Int] Exception [String]

Explanation CVD can not remove node from Config

Recommended Action Verify that Config is available. If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 3 -CVD_DISPATCH_POSTPONED_ERROR : CVD Can not process postponed command. Cmd [String] Exception [String]

Explanation CVD Can not process postponed command

Recommended Action Investigate as required

Error Message
MCVD-CVD- 3 -DB_REPLICATION_TEARDOWN_ERROR : Failed to teardown IDS Replication setup. Exception [String]

Explanation Failed to teardown IDS replication setup

Recommended Action Try IDS Replication teardown through CLI

Error Message
MCVD-CVD- 4 -REJOIN_CLUSTER_JOIN : ---reJoinCluster-- join Cluster.

Explanation CVD detects master conflict, and try to resolve it by leaving and joining cluster

Recommended Action No actions needed

Error Message
MCVD-CVD- 3 -SERVICE_START_ERROR : Node Manager can not start service. name [String] Exception [String]

Explanation Node Manager can not start service

Recommended Action Repeat operation. Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -COMPONENT_OPERATION_NOT_SUPPORTED : Component does not support operation. type [String] nodeId [Int] operation [String]

Explanation Component does not support operation

Recommended Action No actions needed

Error Message
MCVD-CVD- 2 -START_NODE_MANAGER_ERROR : CVD can not start Node Manager. Exception [String]

Explanation CVD can not start Node Manager

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 2 -DUBLICATE_COMPUTER_NAME : Two nodes have the same computer name. nodeId [Int] otherNodeId [Int] computerName [String]

Explanation Two nodes have the same computer name

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -WRONG_IP_ADDRESS : Wrong IP Address. ip [String] Exception [String]

Explanation Wrong IP Address

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 3 -COMPONENT_CLEAR_INVALID_DATABASE_ERROR : Component clearInvalidDatabase error. type [String] nodeId [Int] Exception [String]

Explanation Component clearInvalidDatabase error

Recommended Action Repeat operation. Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 6 -CVD_COMPLETED : CVD Stop completed.

Explanation CVD Stop completed

Recommended Action No actions needed

Error Message
MCVD-CVD- 3 -CVD_W1UPGRADE_LISTNER_REGISTER_ERROR : startCVD - can not register W1UpgradeListener:. Exception [String]

Explanation startCVD - can not register W1UpgradeListener:

Recommended Action Investigate as required

Error Message
MCVD-CVD- 3 -MASTER_SERVICE_NOT_FOUND : Master service not found. name [String] UniqueId [Int] nodeId [Int] Cmd [String]

Explanation Master service not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -NODE_NOT_FOUND_FOR_CMD : CVD dispatcher can not process cmd: unknown Node. Cmd [String]

Explanation CVD dispatcher can not process cmd: unknown Node

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -MASTER_UPDATE_ERROR : CVD can not update master. nodeId [Int] Exception [String]

Explanation CVD can not update master

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 4 -COMPONENT_HISTORICAL_ENABLED : 'Unified CCX Config Datastore' component can not be disabled, because 'Unified CCX Historical Datastore' is enabled on this node. type [String] nodeId [Int]

Explanation 'Unified CCX Config Datastore' component can not be disabled, because 'Unified CCX Historical Datastore' is enabled on this node

Recommended Action Disable Unified CCX Historical Datstore

Error Message
MCVD-CVD- 3 -SERVICE_OPERATION_NOT_SUPPORTED : Service does not support operation. name [String] nodeId [Int] operation [String]

Explanation Service does not support operation

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 3 -SERVICE_ACTIVATE_ERROR : Node Manager can not activate service. name [String] Exception [String]

Explanation Node Manager can not activate service

Recommended Action Repeat operation. Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -NODE_UPDATE_ERROR : CVD can not update node from command. nodeId [Int] Cmd [String]

Explanation CVD can not update node from command

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -SERVICE_NOT_FOUND : Service not found. name [String] nodeId [Int] Cmd [String]

Explanation Service not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -CVD_NODE_UPDATE_ERROR : CVD can not update Node. nodeId [Int] subscriber [String] Exception [String]

Explanation CVD can not update Node

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 4 -COMPONENT_ALREADY_INVALID : Component is already invalid. type [String] nodeId [Int]

Explanation Component is already invalid

Recommended Action No actions needed

Error Message
MCVD-CVD- 4 -MASTER_POSTPONED_CMD : Master postponed command. name [String] Cmd [String]

Explanation CVD detects that processing this command caused more than one master, so CVD postponed to process the command

Recommended Action No actions needed

Error Message
MCVD-CVD- 3 -WRONG_LOCAL_IP_ADDRESS : Wrong local IP Address. ip [String] reason [String]

Explanation Wrong local IP Address

Recommended Action Reinstall server

Error Message
MCVD-CVD- 4 -COMPONENT_PRIMARY_DISABLED : Component can not be primary, because it is disabled. type [String] nodeId [Int]

Explanation Component can not be primary, because it is disabled

Recommended Action Enable Component

Error Message
MCVD-CVD- 3 -INTRUSION_DETECTED : Intrusion detected. ip [String]

Explanation Intrusion from unknown IP address detected

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 3 -NODE_NOT_FOUND_IN_CONFIG : Node not found in CONFIG after refresh(). nodeId [Int]

Explanation Node not found in CONFIG after refresh()

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 4 -MASTER_REJECTS_NODE_JOIN : Master rejects node join, because more than one master detected. name [String] nodeId [Int]

Explanation CVD detects that processing node join command caused more than one master, so CVD rejects to process node join command

Recommended Action No actions needed

Error Message
MCVD-CVD- 4 -SUBSCRIBER_NOT_FOUND : Subscriber not found to execute command. name [String] Cmd [String]

Explanation Subscriber not found to execute command

Recommended Action No actions needed

Error Message
MCVD-CVD- 4 -MASTER_DETECTS_NODE_JOIN : More than one master detected, when processing node join. name [String] nodeId [Int] masterCnt [Int]

Explanation CVD detects that processing node join command caused more than one master

Recommended Action No actions needed

Error Message
MCVD-CVD- 3 -SERVICE_NOT_FOUND_ON_LOCAL_NODE : Service not found on local node. name [String]

Explanation Service not found on local node

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 2 -TIME_NOT_SYNCHRONIZED : Time is not synchronized. localNodeId [Int] otherNodeId [Int]

Explanation Time is not synchronized

Recommended Action Verify that Config is available. If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 4 -MASTER_REJECTS_UPDATE : More than one master detected. name [String] Cmd [String] masterCnt [Int]

Explanation CVD detects that processing this command caused more than one master, so CVD rejects to process the command

Recommended Action No actions needed

Error Message
MCVD-CVD- 3 -ACCESS_CONFIG_ERROR : CVD can not access Config. Exception [String]

Explanation CVD can not access Config

Recommended Action Verify that Config is available. If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 4 -REJOIN_CLUSTER_LEAVE : ---reJoinCluster-- leave Cluster. reason [String]

Explanation CVD detects master conflict, and try to resolve it by leaving and joining cluster

Recommended Action No actions needed

Error Message
MCVD-CVD- 2 -MULTIPLE_MASTERS_DETECTED : CVD detects Multiple masters. name [String] masterCnt [Int]

Explanation CVD detects Multiple masters, process will be restarted

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 3 -SERVICE_STOP_ERROR : Node Manager can not stop service. name [String] Exception [String]

Explanation Node Manager can not stop service

Recommended Action Repeat operation. Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -CVD_DISPATCH_CMD_ERROR : CVD Can not process command. Cmd [String] Exception [String]

Explanation CVD Can not process command

Recommended Action Investigate as required

Error Message
MCVD-CVD- 3 -NODE_NOT_FOUND : Node not found. nodeId [Int]

Explanation Node not found

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 3 -CVD_ARCHIVE_LISTNER_REGISTER_ERROR : startCVD - can not register archiveListener:. Exception [String]

Explanation startCVD - can not register archiveListener:

Recommended Action Investigate as required

Error Message
MCVD-CVD- 3 -NODE_IS_NOT_ACTIVE : CVD can not execute operation, because node is not active. nodeId [Int] operation [String]

Explanation CVD can not execute operation, because node is not active

Recommended Action Verify, that CVD is running on the node

Error Message
MCVD-CVD- 4 -COMPONENT_CONFIG_DISABLED : 'Unified CCX Historical Datastore component can not be enabled, because 'Unified CCX Config Datastore' is disabled on this node. type [String] nodeId [Int]

Explanation 'Unified CCX Historical Datastore component can not be enabled, because 'Unified CCX Config Datastore' is disabled on this node

Recommended Action Enable Unified CCX Config Datstore

Error Message
MCVD-CVD- 4 -CUIC_USERSYNC_ERROR : Reporting Capability User Sync to CUIC during component activation failed. Exception [String]

Explanation Reporting Capability User Sync to CUIC during component activation failed

Recommended Action Click update on the page for assigning Historical Reporting capability to sync Reporting Users to CUIC

Error Message
MCVD-CVD- 3 -HAZELCAST_START_ERROR : Error in starting Hazelcast instance. Exception [String]

Explanation Failed to start hazelcast instance and join cluster

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 3 -COMPONENT_ENABLE_ERROR : Component enabled error. type [String] nodeId [Int] reason [String]

Explanation Component enabled error

Recommended Action Repeat operation. Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -NODE_ADD_TO_CLUSTER_ERROR : Node Can not be added to the cluster. reason [String] Exception [String]

Explanation Node Can not be added to the cluster

Recommended Action Verify that Config is available. If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 4 -MUTEX_DROP : Local node drop mutex, because this mutex is acquired on other node. localNodeId [Int] mutexInfo [String] nodeId [Int]

Explanation Local node drop mutex, because this mutex is acquired on other node

Recommended Action No actions needed

Error Message
MCVD-CVD- 3 -NODE_NOT_IN_CLUSTER : Reject Node join, because its IP address is invalid. Cmd [String] nodeId [Int] ip [String] reason [String]

Explanation Reject Node join, because its IP address is invalid

Recommended Action No actions needed

Error Message
MCVD-CVD- 3 -NODE_START_ERROR : CVD can not start local Node Manager. Exception [String]

Explanation CVD can not start local Node Manager

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 3 -CVD_REGISTER_SUBSCRIBER_ERROR : CVD can not register subscriber on the remote node. nodeId [Int] Exception [String]

Explanation CVD can not register subscriber on the remote node

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 4 -SERVICE_CHANGE_STATE : Service change state. nodeId [Int] name [String] state [String]

Explanation Service change state

Recommended Action No actions needed

Error Message
MCVD-CVD- 3 -CLUSTER_INCONSISTENT : Cluster is inconsistenet. reason [String]

Explanation Cluster is inconsistent

Recommended Action Verify that Config is available. If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 0 -CHILD_SERVICE_NOT_FOUND : Child Service Not Found. name [String] Cmd [String]

Explanation Command could not be processed, because child Service not found

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 3 -NODE_GET_UPDATE_ERROR : CVD can not get Node update. nodeId [Int] errCnt [Int] Exception [String]

Explanation CVD can not update Node

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -ADD_SUBSCRIBER_ERROR : Add Subscriber error. nodeId [Int] publisher [String] Exception [String]

Explanation Add Subscriber error

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -REBOOT_ON_CVD_REGISTER_SUBSCRIBER_ERROR : CVD can not register subscriber on the remote node due to connection issue. System is being rebooted once to recover from the issue.. Exception [String]

Explanation CVD can not register subscriber on the remote node due to connection issue. System is being rebooted once to recover from the issue.

Recommended Action No actions needed

Error Message
MCVD-CVD- 4 -SAVE_IN_POSTPONED_QUEUE : Save cmd in postponedCmdQueue. Cmd [String]

Explanation Save cmd in postponedCmdQueue, do not process it

Recommended Action No actions needed

Error Message
MCVD-CVD- 3 -SERVICE_ID_NOT_FOUND : Service not found. UniqueId [Int] nodeId [Int] Cmd [String]

Explanation Service not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -NODE_REMOVE_CFGERROR : Cannot remove node configuration. Exception [String]

Explanation Cannot remove node configuration from Config

Recommended Action Investigate as required

Error Message
MCVD-CVD- 3 -MASTER_SESSION_ERROR : CVD Master session error. UniqueId [Int] Exception [String]

Explanation CVD Master session error

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 4 -COMPONENT_PRIMARY_NOT_ACTIVE : Component Controller can not execute operation, because primary is not active. type [String] nodeId [Int] operation [String]

Explanation Component Controller can not execute operation, because primary is not active

Recommended Action Activate Primary

Error Message
MCVD-CVD- 4 -COMPONENT_DISABLE_PRIMARY : Component can not be disabled, because it is primary. type [String] nodeId [Int]

Explanation Component can not be disabled, because it is primary

Recommended Action No actions needed

Error Message
MCVD-CVD- 4 -SERVICE_START_DISABLED : CVD can not start service, because it is disabled. name [String] nodeId [Int]

Explanation CVD can not start service, because it is disabled

Recommended Action Enable Component

Error Message
MCVD-CVD- 3 -NODE_LEAVE_CLUSTER : Node leave cluster. nodeId [Int]

Explanation CVD does not receive heartbeats from the node. Probably it crash or shutdown

Recommended Action No actions needed

Error Message
MCVD-CVD- 4 -COMPONENT_ALREADY_PRIMARY : Component is already primary. type [String] nodeId [Int]

Explanation Component is already primary

Recommended Action No actions needed

Error Message
MCVD-CVD- 3 -SERVICE_ILLEGAL_REQUEST : CVD Create Service received Illegal Request. Cmd [String] reason [String]

Explanation CVD Create Service received Illegal Request

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -SET_NTP_SERVER_ERROR : NTP server is not configured. Exception [String]

Explanation NTP server is not configured

Recommended Action Verify that Config is available. If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 3 -CLUSTER_CONFIG_ERROR : Cannot retrieve cluster configuration. Exception [String]

Explanation Cannot retrieve cluster configuration from Config

Recommended Action Investigate as required

Error Message
MCVD-CVD- 3 -COMPONENT_REPLICATION_ENABLE_ERROR : Component replicationManager.enable() error. type [String] nodeId [Int] Exception [String]

Explanation Component replicationManager.enable() error

Recommended Action Repeat operation. Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -COMPONENT_ID_NOT_FOUND : Component not found. UniqueId [Int] nodeId [Int] Cmd [String]

Explanation Component not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -CLUSTER_SNAPSHOT_ON_RESTART : Cluster snapshot when restart. cluster [String]

Explanation Cluster snapshot when restart

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 3 -VERIFY_SOURCE_ADDRESS_ERROR : CVD Publisher.verifySourceAddress: receives rmi request from unexpected address. nodeId [Int] ip [String] ips [String]

Explanation CVD Publisher.verifySourceAddress: receives rmi request from unexpected address

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -PUBLISHER_EXECUTE_ERROR : Publisher can not execute command. publisher [String] errCnt [Int] Exception [String]

Explanation Publisher can not execute command

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 4 -COMPONENT_INVALID_DATABASE : Component can not be primary, because it has invalidDatabase. type [String] nodeId [Int]

Explanation Component can not be primary, because it has invalidDatabase

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 3 -NODE_READ_ERROR : CVD can not read node from command. Cmd [String] Exception [String]

Explanation CVD can not read node from command

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -MUTEX_PROCESS_ERROR : Process Mutex cmd error. mutexInfo [String] Cmd [String] reason [String]

Explanation Process Mutex cmd error

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -MASTER_NOTIFICATION_ERROR : CVD Master publisher fail to notify external process. Exception [String]

Explanation CVD Master publisher fail to notify external process by TCP

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 6 -CVD_INITIALIZING : CVD starts initialization. localNodeId [Int]

Explanation Cluster View Daemon starts initialization

Recommended Action No actions needed

Error Message
MCVD-CVD- 3 -SERVICE_RESTART_ERROR : Node Manager can not restart service. name [String] Exception [String]

Explanation Node Manager can not restart service

Recommended Action Repeat operation. Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-CVD- 3 -NODE_SYNCHRONIZE_STATE_ERROR : CVD can not synchronize state for node. nodeId [Int]

Explanation CVD can not synchronize state for node. CVD will be restarted

Recommended Action No actions needed

Error Message
MCVD-CVD- 2 -THROWS_KEEP_ALIVE_EXCEPTION : CVD throws KeepAlive Exception. Exception [String]

Explanation CVD detects some problem that prevents its functionality, and will be restarted

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-CVD- 3 -INSTALL_JTAPI_ERROR : Jtapi Client is not installed. Exception [String]

Explanation Jtapi client is not installed

Recommended Action Verify that Config is available. If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-DB_MGR- 1 -MGR_PARTIAL_SERVICE : Database Manager in partial service.

Explanation The Database Manager is in partial service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-DB_MGR- 6 -DATASOURCE_STATE : state change. change [String]

Explanation state change

Recommended Action No actions needed

Error Message
MCVD-DB_MGR- 6 -MGR_IN_SERVICE : Database Manager in service.

Explanation The Database Manager is in service

Recommended Action No actions needed

Error Message
MCVD-DB_MGR- 5 -MGR_SHUTDOWN : Database Manager in shutdown.

Explanation The Database Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MCVD-DB_MGR- 3 -DATASOURCE_INIT_ERROR : Failed to db server. Type [String] Exception [String]

Explanation Failed to initialize the db server

Recommended Action Please check db server

Error Message
MCVD-DB_MGR- 3 -UPDATE_CLUSTERDEPENDENTCONFIG_FAILED : Failed to update DBVersion in ClusterDependentConfig . Exception [String]

Explanation Failed to update DBVersion in ClusterDependentConfig

Recommended Action No actions needed

Error Message
MCVD-DB_MGR- 3 -DS_PRIMARY_READ_ERROR : Failed to read Datasource primary. Type [String] Exception [String]

Explanation Failed to read Datasource primary from cluster profile

Recommended Action Please check cluser profile info

Error Message
MCVD-DB_MGR- 3 -CREATE_SERVICE_CONVERGENCE_FAILED : Failed to create convergence service . Name [String]

Explanation Failed to create convergence service

Recommended Action Please check cluster manager

Error Message
MCVD-DB_MGR- 3 -SQL_PROPERTIES_READ_ERR : Error in reading SQL properties from cluster info. Exception [String]

Explanation Error in reading SQL properties such as SQL instance name , port

Recommended Action Check DB components are configured

Error Message
MCVD-DB_MGR- 6 -MGR_INITIALIZING : Database Manager initializing.

Explanation The Database Manager is initializing

Recommended Action No actions needed

Error Message
MCVD-DB_MGR- 2 -MGR_OUT_OF_SERVICE : Database Manager in out of service.

Explanation The Database Manager is out of service;

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-DB_MGR- 5 -MGR_SHUTTING_DOWN : Database Manager shutting down.

Explanation The Database Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MCVD-DB_MGR- 6 -NO_CLUSTER_MGR : No cluster Manager.

Explanation There is no cluster Manager running

Recommended Action No actions needed

Error Message
MCVD-DB_MGR- 3 -ERROR_JDBC_DRVER_LOAD : Error in loading jTDS Driver. Exception [String]

Explanation Error in loading jTDS Driver

Recommended Action Check whether driver is avaialble

Error Message
MCVD-DBPURGE_MGR- 3 -PURGE_EXCEPTION : An exception has been caught.. Message Description [String] Exception [String]

Explanation Need to schedule purging

Recommended Action An exception has been caught.

Error Message
MCVD-DBPURGE_MGR- 3 -RMI_REBIND_FAILED : Unable to register remote interface. Exception [String]

Explanation A remote interface could not be bound to the RMI registry; remote access for dynamic update or other functions will not be available

Recommended Action Verify the RMI configuration and restart server

Error Message
MCVD-DBPURGE_MGR- 6 -INVOKED_PURGE : Invoked.

Explanation Invoked

Recommended Action No actions needed

Error Message
MCVD-DBPURGE_MGR- 3 -EXCEPTION : Exception in invoking purging. Exception [String]

Explanation Exception in invoking purging

Recommended Action Please check the database

Error Message
MCVD-DOC_MGR- 1 -UNAUTHORISED_ACCESS : Unauthorised access. Name [String] Exception [String]

Explanation The Document Manager found that requested resource is not a legitimate one

Recommended Action Investigate as required

Error Message
MCVD-DOC_MGR- 1 -MGR_PARTIAL_SERVICE : Document Manager in partial service.

Explanation The Document Manager is in partial service; synchronization of files with document repository is in progress

Recommended Action No actions needed

Error Message
MCVD-DOC_MGR- 3 -UNABLE_LOAD_USER_DOC : Unable to load the user document file. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to load the specified user document file

Recommended Action Verify and update the configuration

Error Message
MCVD-DOC_MGR- 6 -MGR_IN_SERVICE : Document Manager in service.

Explanation The Document Manager is in service

Recommended Action No actions needed

Error Message
MCVD-DOC_MGR- 2 -INVALID_USER_DIR : Invalid user document directory configured. Directory [String] Exception [String]

Explanation The configured user document directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-DOC_MGR- 2 -WEBAPP_INIT_FAILURE : Unable to initialize the specified web application. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to initialize the specified web applicaton; it will not be available to HTTP-triggered applications

Recommended Action Verify and update the configuration and restart server

Error Message
MCVD-DOC_MGR- 6 -NO_WEBAPPS_APPS : Webapps directory is empty.

Explanation No apps in the webapps directory of the repository to process

Recommended Action No actions needed

Error Message
MCVD-DOC_MGR- 6 -NO_WEBAPPS : Webapps directory not found.

Explanation No webapps directory in the repository to process

Recommended Action No actions needed

Error Message
MCVD-DOC_MGR- 3 -UNDEFINED_USER_DOC : Undefined user document. Name [String] Language [String] Exception [String]

Explanation A user document cannot be located

Recommended Action Verify and update the configuration

Error Message
MCVD-DOC_MGR- 5 -MGR_SHUTDOWN : Document Manager in shutdown.

Explanation The Document Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MCVD-DOC_MGR- 1 -WEBAPPS_MONITOR_FAILURE : Webapps directory monitoring failure. Exception [String]

Explanation The Document Manager can no longer monitor dynamic updates to the webapps directory of the repository; updates to war files will require restarting the local Unified CCX Engine Service

Recommended Action Investigate as required

Error Message
MCVD-DOC_MGR- 3 -DOC_FILE_SUPPORT_FAILURE : Document file support failure. Exception [String]

Explanation The Document Manager can not register file support for user document files; user documents will not be synchronized on local server

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-DOC_MGR- 3 -UNDEFINED_SYSTEM_DOC : Undefined system document. Name [String] Language [String] Exception [String]

Explanation A system document cannot be located

Recommended Action Verify and update the configuration

Error Message
MCVD-DOC_MGR- 3 -UNABLE_LOAD_SYSTEM_DOC : Unable to load the system document file. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to load the specified system document file

Recommended Action Verify and update the configuration

Error Message
MCVD-DOC_MGR- 2 -WAR_EXPAND_FAILURE : Unable to expand the specified war file. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to expand the specified war file; the corresponding web application will not be available to HTTP-triggered applications

Recommended Action Verify and update the configuration and restart server

Error Message
MCVD-DOC_MGR- 3 -WEBAPP_REMOVE_FAILURE : Unable to remove the specified web application. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to remove the specified web applicaton

Recommended Action Verify and update the configuration and restart server

Error Message
MCVD-DOC_MGR- 6 -MGR_INITIALIZING : Document Manager initializing.

Explanation The Document Manager is initializing

Recommended Action No actions needed

Error Message
MCVD-DOC_MGR- 2 -MGR_OUT_OF_SERVICE : Document Manager in out of service.

Explanation The Document Manager is out of service; documents won't be accessible

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-DOC_MGR- 5 -MGR_SHUTTING_DOWN : Document Manager shutting down.

Explanation The Document Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MCVD-DOC_MGR- 3 -WEBSERVICES_ERROR : Exception thrown while processing web services for Document. Exception [String]

Explanation The Document Manager is unable to initialize the web services; external access to the document repository will not be possible andsupport for forwarding HTTP requests will also not be supported

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-DOC_MGR- 2 -INVALID_SYSTEM_DIR : Invalid system document directory configured. Directory [String] Exception [String]

Explanation The configured system document directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-EXECUTOR_MGR- 1 -MGR_PARTIAL_SERVICE : Executor Manager in partial service.

Explanation The Executor Manager is in partial service; thread priorities will not be properly set

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-EXECUTOR_MGR- 4 -INVALID_THREAD_PRIORITY_CHANGE : Invalid thread priority change. Facility [String] Sub-Facility [String] Executor id [String] Thread [String] Thread priority [Int] Original thread priority [Int]

Explanation The specified thread had an unsupported priority changed; user's code should not attempt to manually change the priority of threads for whatever reasons

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-EXECUTOR_MGR- 6 -MGR_INITIALIZING : Executor Manager initializing.

Explanation The Executor Manager is initializing

Recommended Action No actions needed

Error Message
MCVD-EXECUTOR_MGR- 5 -MGR_SHUTTING_DOWN : Executor Manager shutting down.

Explanation The Executor Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MCVD-EXECUTOR_MGR- 2 -MGR_OUT_OF_SERVICE : Executor Manager in out of service.

Explanation The Executor Manager is out of service; executors won't be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-EXECUTOR_MGR- 4 -CMD_BLOCKED : Invoking blocked execution handler. Facility [String] Sub-Facility [String] Executor id [String] Mnemonic [String] Thread [String] Thread priority [Int] Time [Long] Handler [String]

Explanation The specified blocked execution handler is being invoked for the specified command as the executor queue could not accept it

Recommended Action No actions needed

Error Message
MCVD-EXECUTOR_MGR- 6 -MGR_IN_SERVICE : Executor Manager in service.

Explanation The Executor Manager is in service

Recommended Action No actions needed

Error Message
MCVD-EXECUTOR_MGR- 4 -MISSING_RESOURCE : Missing thread priority resource. Facility [String] Sub-Facility [String] Executor id [String] Exception [String]

Explanation The executor manager is unable to locate internal thread priority resources

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-EXECUTOR_MGR- 4 -CMD_EXCEPTION : Un-handled command exception. Facility [String] Sub-Facility [String] Executor id [String] Mnemonic [String] Thread [String] Thread priority [Int] Time [Long] Exception [String]

Explanation The specified command did not handled the specified exception

Recommended Action No actions needed

Error Message
MCVD-EXECUTOR_MGR- 4 -INVALID_THREAD_NAME_CHANGE : Invalid thread name change. Facility [String] Sub-Facility [String] Executor id [String] Thread [String] Original Thread [String]

Explanation The specified thread had an unsupported name changed; user's code should not attempt to manually change the name of threads for whatever reasons

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-EXECUTOR_MGR- 4 -ATTEMPT_FAILED : Attempt failed. Facility [String] Sub-Facility [String] Executor id [String] Mnemonic [String] Time [Long] Exception [String]

Explanation Attempt to execute the specified command failed

Recommended Action No actions needed

Error Message
MCVD-EXECUTOR_MGR- 5 -MGR_SHUTDOWN : Executor Manager in shutdown.

Explanation The Executor Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MCVD-EXECUTOR_MGR- 4 -EXECUTE_FAILED : Execute failed. Facility [String] Sub-Facility [String] Executor id [String] Mnemonic [String] Time [Long] Exception [String]

Explanation Request to execute the specified command failed

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 3 -DATA_SOURCE_CANNOT_BE_INITIALIZED : Repository Datastore data source cannot be initialized. Exception [String]

Explanation The file manager could not get the datasource initialized for Repository Datastore.

Recommended Action If problem persists.Please contact Cisco Technical Assistance Center(TAC)

Error Message
MCVD-FILE_MGR- 3 -STATE_CHECKER_THREAD_CREATION_FAILED : Unable to start the File Manager's state monitor thread. Exception [String]

Explanation Unable to start the File Manager state monitor thread;FileManager functionality not available.

Recommended Action If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MCVD-FILE_MGR- 1 -MGR_PARTIAL_SERVICE : File Manager in partial service.

Explanation The File Manager is in partial service; file synchronization will notbe available

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-FILE_MGR- 3 -UNABLE_UPLOAD_FILE : Unable to upload the specified file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The file manager could not upload the specified file

Recommended Action Investigate as required

Error Message
MCVD-FILE_MGR- 6 -DELETE_FILE_FOLDER_REQ_BY_USER : A file or folder delete was initiated by user. Class [String] Domain [String] Directory [String] Name [String] User Id [String]

Explanation The file manager is requested to delete folder or file by user

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 3 -REFRESH_FAILED : File refresh operation failed. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation Unable to download and create the specified file

Recommended Action Investigate as required

Error Message
MCVD-FILE_MGR- 3 -RDS_SQL_EXCEPTION_INFO : SQL Exception. Exception details [String]

Explanation SQL Exception occurred in File Manager

Recommended Action Investigate as required

Error Message
MCVD-FILE_MGR- 4 -CLASSPATH_SYNC_FAILED : Custom classpath files synchronization failed. Exception [String]

Explanation The remote file manager was unable to synchronize the custom classpath files and <default><webapps> folder from the cluster's document repository

Recommended Action Investigate as required

Error Message
MCVD-FILE_MGR- 2 -CUSTOM_FILES_CLASSPATH_WEB_APPS_SYNC_FAILED : Unable to synchronize custom files/jars from Repository Datastore. Class [String] Exception [String]

Explanation Unable to do synchronization of <default><classpath> and<default><webapps> folders under <Documents><user>

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-FILE_MGR- 6 -SYNC_FOUND_LOCAL_FILE_NOT_IN_REPOSITORY : The local file found during synchronization is not present in Repository Datastore. Class [String] Extra local file [String]

Explanation The extra local file found during synchronization is being deleted.

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 5 -CUSTOM_FILES_CLASSPATH_WEB_APPS_SYNC_SUCCEEDED : Synchronization of custom files/jars from Repository Datastore done.

Explanation Synchronization of <default><classpath> and<default><webapps> folders under <Documents><user> completed.

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 6 -MGR_INITIALIZING : File Manager initializing.

Explanation The File Manager is initializing

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 2 -MGR_OUT_OF_SERVICE : File Manager in out of service.

Explanation The File Manager is out of service; files won't be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-FILE_MGR- 3 -UNABLE_DOWNLOAD_FILE : Unable to download the specified file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The file manager could not download the specified file

Recommended Action Investigate as required

Error Message
MCVD-FILE_MGR- 4 -SYNC_FAILED_TO_CREATE_FILE : Synchronization failed to create file. Class [String] Reason [String] Exception [String]

Explanation Creation of files failed during synchronization.

Recommended Action If problem persists contact.Please Cisco Technical Assistance Center(TAC).If files are missing you may have to restart the CVD Service.

Error Message
MCVD-FILE_MGR- 3 -SYNC_THREAD_CREATION_FAILED : Unable to start the File Manager's local disk synchronization thread for a file type.. Class [String] Exception [String]

Explanation Unable to start the File Manager sychronization thread;synchronization will not be available for the file type

Recommended Action If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MCVD-FILE_MGR- 6 -CLASSPATH_SYNC_START : Custom classpath and <default><webapps> files are being synchronized.

Explanation The remote file manager is synchronizing the custom classpath files and webapps folders files from the cluster's document repository

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 4 -ORIGINAL_FILE_NOT_FOUND : Original file not found while copying with new version. Original file: [String]

Explanation The file manager was unable to copy a new version file since the original file was not found.

Recommended Action Investigate as required

Error Message
MCVD-FILE_MGR- 3 -UNABLE_GET_REPOSITORY_STATISTICS : Unable to get the repository size information. Space information requested: [String] Exception [String]

Explanation The File Manager could not get the repository size information

Recommended Action Investigate as required

Error Message
MCVD-FILE_MGR- 6 -REMOTE_STANDALONE_MODE : Remote File Manager initialized in stand-alone mode.

Explanation The remote file manager is being initialized in stand-alone mode; it will attempt to synchronized custom classpaths with the cluster

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 6 -MGR_IN_SERVICE : File Manager in service.

Explanation The File Manager is in service

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 3 -UNABLE_RENAME_FILE : Unable to rename the specified file. Class [String] Domain [String] Directory [String] Name [String] Destination Domain [String] Destination Directory [String] Destination Name [String] Exception [String]

Explanation The file manager could not rename the specified file

Recommended Action Investigate as required

Error Message
MCVD-FILE_MGR- 3 -CLEANUP_THREAD_CREATION_FAILED : Unable to start the File Manager's cleanup thread. Exception [String]

Explanation Unable to start the cleanup background thread; will not be able to perform the disk cleanup operations

Recommended Action If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MCVD-FILE_MGR- 4 -GET_RDS_DB_CONNECTION_FAILED : Unable to get connection to the Repository Datastore. Failure Reason [String]

Explanation Unable to get connection to Repository Datastore access; will not be able to perform prompts,grammars, documents related operations

Recommended Action Check Repository Datastore is activated.If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MCVD-FILE_MGR- 6 -CLASSPATH_SYNC_DONE : Custom classpath files synchronized.

Explanation The remote file manager successfully synchronized the custom classpath files and webapps folder files from the cluster's document repository

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 3 -UNABLE_GET_FILE_MODIFIED_TIME : Unable to get the last modified time of the file or directory. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not get the file or directory's last modified time

Recommended Action Verify the path of the file or directory

Error Message
MCVD-FILE_MGR- 4 -EXCEPTION_IN_TEMP_FILES_HANDLING_METHOD : Method generated exception. Exception [String]

Explanation File Manager temporary files-cleanup handling, generated exception.

Recommended Action If problem persists please contact Cisco Technical Assistance Center(TAC).

Error Message
MCVD-FILE_MGR- 3 -UNABLE_GET_LAST_MODIFIED_USER : Unable to get the last modified user of the file or folder . Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not get the file or folder

Recommended Action Verify the file or folder exists in repository

Error Message
MCVD-FILE_MGR- 4 -LAST_SYNC_TIME_CHECK_FAILED : Error while checking the replication LastSynchedTime. Exception [String]

Explanation Could not get the replication sync time while updating repository statistics

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 6 -NO_FOLDER_FILE_TO_DELETE_BY_CLEANUP_TASK_RUN : Current run of daily cleanup found no files,folders to delete. Exception [String]

Explanation The File Manager daily cleanup task, to cleanup deleted (folder,files) on local disk,found not files,folders to delete .

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 3 -UNABLE_DELETE_FILE : Unable to delete the specified file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The file manager could not delete the specified file

Recommended Action Investigate as required

Error Message
MCVD-FILE_MGR- 6 -UPLOAD_ARCHIVE_FILE_SUCCESS : Success progress of upload archive file. Class [String] status [String]

Explanation Archive file each file type upload status

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 4 -COPY_FILES_TO_ORIG_LOCATION : Copying of files to original location errored. Exception [String]

Explanation The task to copy files from <temp> directory to original location failed

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 3 -CLUSTER_RMI_REBIND_FAILED : Unable to register remote interface in cluster space. Exception [String]

Explanation A remote interface could not be binded to the cluster space; automatic synchronization of files will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-FILE_MGR- 3 -UNABLE_MAKE_DIR : Unable to make directory. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not create the directory

Recommended Action Verify that path of the directory

Error Message
MCVD-FILE_MGR- 3 -SYNC_REMOTE_NOTIFICATION_FAILED : Notifying remote File Manager service objects failed. Class [String] Node Id [String] Exception [String]

Explanation Synchronization notifications using remote File Manager Service failed for one or more nodes.

Recommended Action If problem persists contact.Please Cisco Technical Assistance Center(TAC).

Error Message
MCVD-FILE_MGR- 6 -SYNC_OPERATION_STARTED : Synchronization started.. Class [String] Synchronization status [String]

Explanation Repository Datastore to local disk synchronization started.

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 3 -UNABLE_UPLOAD_ARCHIVE_FILE : Unable to upload the archive file. Archive File Name [String] Reason [String] Archive Length [String] Exception [String]

Explanation The File Manager could not upload the specified file

Recommended Action Investigate as required

Error Message
MCVD-FILE_MGR- 4 -DELETED_FOLDER_FILE_CLEANUP_TASK_RUN_FAILED : Current run of daily cleanup task failed. Exception [String]

Explanation The File Manager daily cleanup task, to clean deleted (folder,files) on local disk errored.The files,folders can get deleted in next daily run.

Recommended Action Investigate as required

Error Message
MCVD-FILE_MGR- 4 -SYNC_INVALID_STATE : Synchronization detected invalid state. Class [String] Reason [String]

Explanation Invalid state detected during synchronization

Recommended Action Investigate as required

Error Message
MCVD-FILE_MGR- 3 -UNABLE_LIST_FILES : Unable to list the files denoted by the specified file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The file manager could not list the files denoted by the specified file

Recommended Action Investigate as required

Error Message
MCVD-FILE_MGR- 6 -RECOVERY_COMPLETED_EVENT : File Manager recieved recovery completed event, full synchronization will be performed..

Explanation File Manager detected recovery completed event.Repository changes will be synched to local disk now.

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 1 -CLUSTER_COMM_FAILED : Cluster communication failure. Exception [String]

Explanation Unable to communicate with the cluster; will not be able to access the cluster repository files

Recommended Action Investigate as required

Error Message
MCVD-FILE_MGR- 3 -DUPLICATE_FILE_SUPPORT : Duplicate file support detected. Class [String] Exception [String]

Explanation An attempt is being made at registering a duplicate file support

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-FILE_MGR- 3 -UNABLE_GET_FILE_LENGTH : Unable to get the length of the file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not get the file length

Recommended Action Verify the path of the file

Error Message
MCVD-FILE_MGR- 3 -UNABLE_TO_CREATE_TEMP_DIR : Unable to make temp directory. Class [String] Name [String] Exception [String]

Explanation The File Manager could not create temp directory

Recommended Action Verify that Unified CCX prompts, documents, grammars and scripts folder are proper

Error Message
MCVD-FILE_MGR- 4 -ERROR_WHILE_SYNCH : An error occurred while synchronizing. Class [String] Method [String] Exception [String]

Explanation An error occurred while File Manager is synchronizing disk from RDS

Recommended Action If problem persists please contact Cisco Technical Assistance Center(TAC).

Error Message
MCVD-FILE_MGR- 3 -INVALID_FILE : Invalid file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The specified file is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-FILE_MGR- 3 -FAIL_TO_CREATE_RDS_SERVICE_CONVERGENCE : Repository Datastore Service convergence object cannot be created.

Explanation The file manager cannot create Repository Datastore convergence object.Repository Datastore failover functionality will not be available.

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-FILE_MGR- 4 -SYNC_LOCAL_FILE_LATEST_THAN_IN_REPOSITORY : The local file is found to be newer than one in the Repository Datastore. Class [String] Local file [String] Repository Datastore file [String]

Explanation Local file is being replaced by the one in Repository Datastore

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 4 -SYNC_NOT_COMPLETE : Synchronization did not complete.. Class [String] Exception [String]

Explanation This indicates some of the synchronization operation failed.

Recommended Action If problem persists contact.Please Cisco Technical Assistance Center(TAC).

Error Message
MCVD-FILE_MGR- 6 -SYNC_OPERATION_COMPLETED : Synchronization completed.. Class [String] Synchronization status [String]

Explanation Repository Datastore to local disk synchronization completed.

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 6 -DELETED_TEMP_FILE_FOLDER : Temp file or folder was deleted. Temporary file or folder: [String]

Explanation The file manager deleted temporary file or folder

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 3 -UNABLE_SET_LAST_MODIFIED : Unable to set last modified time of the file or directory. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not set the last modified time of the file or directory.

Recommended Action Verify the path of the file or directory

Error Message
MCVD-FILE_MGR- 5 -MGR_SHUTTING_DOWN : File Manager shutting down.

Explanation The File Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 3 -UNABLE_FILE_EXISTS_CHECK : Check for file or directory existence failed. Class [String] Domain [String] Directory [String] Name [String] Error reason [String]

Explanation The File Manager could not find whether file or directory exists

Recommended Action Verify the path of the file or directory

Error Message
MCVD-FILE_MGR- 6 -RECOVERY_DETECTED : File Manager detected an archive request in the system;synchronization from Repository to local disk not performed..

Explanation File Manager detected an archive request in the system

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 3 -INVALID_FILE_CLASS : Invalid file class. Class [String] Exception [String]

Explanation The specified file class is not supported by the file manager

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-FILE_MGR- 4 -RMI_REBIND_FAILED : Unable to register remote interface. Exception [String]

Explanation A remote interface could not be binded to the RMI registry; remote access to files from the editor will not be available

Recommended Action Verify the RMI configuration and restart server

Error Message
MCVD-FILE_MGR- 3 -FILE_MANAGER_REGISTRATION_WITH_CLUSTER_FAILED : Unable to register the File Manager's Service remote object with the cluster.. Exception [String]

Explanation Unable to register the File Manager's remote service object.

Recommended Action If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MCVD-FILE_MGR- 4 -SYNC_FAILED_TO_MKDIR : Synchronization failed to make directory. Class [String] Reason [String]

Explanation Creation of directories failed during synchronization.

Recommended Action If files are missing you may have to restart the CVD Service.If problem persists contact.Please Cisco Technical Assistance Center(TAC)

Error Message
MCVD-FILE_MGR- 4 -RDS_DETERMINATION_FAILED : Repository Datastore cannot be initalized.. Exception [String]

Explanation The file manager could not initialize datastore to store prompts, grammars and documents within the cluster.This may happen if Repository Datastore component is not available in the cluster or configured properly.

Recommended Action Investigate as required

Error Message
MCVD-FILE_MGR- 6 -REMOTE_COLLOCATED_MODE : Remote File Manager initialized in collocated mode.

Explanation The remote file manager is being initialized in collocated mode; it will not attempt to synchronized custom classpaths with the cluster

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 5 -MGR_SHUTDOWN : File Manager in shutdown.

Explanation The File Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 4 -NEW_VERSION_FILE_NOT_FOUND : Newer version of file not found in <temp> directory. New version file(<temp>): [String]

Explanation The file manager was unable to find newer verion of file in <temp> while updating to original location

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 6 -SYNC_FOUND_LOCAL_FOLDER_NOT_IN_REPOSITORY : The local folder found during synchronization is not present in Repository Datastore. Class [String] Extra local folder [String]

Explanation The extra local folder found during synchronization is being deleted.

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 3 -SYNC_CANNOT_INITIALIZE_LOCAL_STORE : Unable to initialize local disk info when performing Repository Sync. Class [String] Exception [String]

Explanation Local store intialization failed during synchronization

Recommended Action If problem persists contactCisco Technical Assistance Center(TAC)

Error Message
MCVD-FILE_MGR- 3 -SYNC_CANNOT_INITIALIZE_DB_STORE : Unable to initialize Repository Datastore access when performing Synchronization. Class [String] Exception [String]

Explanation Accessing Repository Datastore failed.

Recommended Action Check if the RDS component is activated.If problem persists contact.Please Cisco Technical Assistance Center(TAC)

Error Message
MCVD-FILE_MGR- 6 -SYNCHRONIZATION_UPDATE : FileManager RDS to local disk synchronization. Class [String] Information [String]

Explanation progress message related to FileManager synchronization of local disk from RDS

Recommended Action No actions needed

Error Message
MCVD-FILE_MGR- 3 -REP_DATASTORE_INIT_FAILED : Unable to initialize the Repository Datastore access. Exception [String]

Explanation Unable to initialize Repository Datastore access; will not be able to perform prompts,grammars, documents related operations

Recommended Action Check Repository Datastore is enabled.If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MCVD-FILE_MGR- 6 -FILE_MARK_FOR_DELETION : Deleted file. Class [String] Domain [String] Directory [String] Name [String]

Explanation File Manager found the file marked for deletion

Recommended Action Operation cannot be preformed

Error Message
MCVD-FILE_MGR- 4 -MASTER_RDS_NOT_FOUND : Repository Datastore not found.. Reason [String]

Explanation The file manager could not find Repository Datastore to store prompts, grammars and documents within the cluster.This may happen if Repository Datastore component is not activated or Master RDS is not determined.

Recommended Action Investigate as required

Error Message
MCVD-GENERIC- 5 -ProcessStart : Process Starting. Process Identifier [UInt] Module Name [String]

Explanation This notification signifies that a process has just started. This notification is intended to work in conjunction with the ProcessStop notification to notify the start and stop status of a particular process.

Recommended Action No actions needed

Error Message
MCVD-GENERIC- 5 -ModuleStart : Module has successfully started. Module Name [String]

Explanation This notification signifies a module has started successfully and transitioned into the in-service state

Recommended Action No actions needed

Error Message
MCVD-GENERIC- 3 -ModuleRunTimeFailure : Run-time Failure. Module Name [String] Module Run-time Failure Cause [Enum] Module Failure Name [String] Module Failure Message [String]

Explanation This notification signifies a run-time failure has occured

Recommended Action Investigate as required

Module Run-time Failure Cause-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Other or Unspecified Failure
2 Read Access Failure
3 Write Access Failure
4 Create Failure
5 Delete Failure
6 Update Failure
7 Init Failure
8 Load Failure
9 Out of Resource
10 Call Process Failure
11 Registration Failure
12 De-registration Failure
13 Connection Failure
14 Disconnection Failure
15 Unknown Target
16 Un-reacheable Target
Error Message
MCVD-GENERIC- 1 -ModuleStop : Module has stopped. Module Name [String] Module Failure Cause [Enum]

Explanation This notification signifies a module has stopped

Recommended Action Investigate as required

Module Failure Cause-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Other or Unspecified Failure
2 Graceful Shutdown
3 Heartbeat Failure
4 Initialization Failure
5 Out of Resource
6 Partial Failure
Error Message
MCVD-GENERIC- 1 -ProcessStop : Process Stopped. Process Identifier [UInt] Module Name [String]

Explanation This notification signifies that a process has just stopped. This notification is intended to work in conjunction with the ProcessStart notification to notify the start and stop status of a particular process.

Recommended Action Investigate as required

Error Message
MCVD-GRAMMAR_MGR- 3 -GRAMMAR_LEXICAL_ERROR : Template grammar lexical error. Name [String] Template [String] Language [String] Exception [String]

Explanation The specified lexical error occured while parsing a template grammar

Recommended Action Verify and update the application

Error Message
MCVD-GRAMMAR_MGR- 1 -MGR_PARTIAL_SERVICE : Grammar Manager in partial service.

Explanation The Grammar Manager is in partial service; synchronization of files with grammar repository is in progress

Recommended Action No actions needed

Error Message
MCVD-GRAMMAR_MGR- 6 -MGR_IN_SERVICE : Grammar Manager in service.

Explanation The Grammar Manager is in service

Recommended Action No actions needed

Error Message
MCVD-GRAMMAR_MGR- 2 -INVALID_USER_DIR : Invalid user grammar directory configured. Directory [String] Exception [String]

Explanation The configured user grammar directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-GRAMMAR_MGR- 3 -GRAMMAR_PARSING_ERROR : Template grammar parsing error. Name [String] Template [String] Language [String] Exception [String]

Explanation The specified error occured while parsing a template grammar

Recommended Action Verify and update the application

Error Message
MCVD-GRAMMAR_MGR- 3 -UNDEFINED_NAME_GRAMMAR : Undefined user or system grammar. Name [String] Type [String] Language [String] Exception [String]

Explanation A user or system grammar cannot be located

Recommended Action Verify and update the configuration

Error Message
MCVD-GRAMMAR_MGR- 3 -GRAMMAR_FILE_SUPPORT_FAILURE : Grammar file support failure. Exception [String]

Explanation The Grammar Manager can not register file support for user grammar files; user grammars will not be synchronized on local server

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-GRAMMAR_MGR- 5 -MGR_SHUTDOWN : Grammar Manager in shutdown.

Explanation The Grammar Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MCVD-GRAMMAR_MGR- 3 -UNABLE_PARSE_GRAMMAR : Unable to parse the grammar. Grammar [String] Type [String] Exception [String]

Explanation The Grammar Manager is unable to parse the specified grammar

Recommended Action Verify and update the configuration

Error Message
MCVD-GRAMMAR_MGR- 3 -UNSUPPORTED_GRAMMAR : Unsupported grammar type. Name [String] Type [String] Language [String] Exception [String]

Explanation The specified grammar type is not supported

Recommended Action Verify and update the application

Error Message
MCVD-GRAMMAR_MGR- 6 -MGR_INITIALIZING : Grammar Manager initializing.

Explanation The Grammar Manager is initializing

Recommended Action No actions needed

Error Message
MCVD-GRAMMAR_MGR- 5 -MGR_SHUTTING_DOWN : Grammar Manager shutting down.

Explanation The Grammar Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MCVD-GRAMMAR_MGR- 2 -MGR_OUT_OF_SERVICE : Grammar Manager in out of service.

Explanation The Grammar Manager is out of service; grammars won't be accessible

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-GRAMMAR_MGR- 3 -SYSGRAMMAR_FILE_SUPPORT_FAILURE : System grammar file support failure. Exception [String]

Explanation The Grammar Manager can not register file support for system grammar files; system grammars will not be synchronized on local server

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-GRAMMAR_MGR- 3 -WEBSERVICES_ERROR : Exception thrown while processing web services for Grammar. Exception [String]

Explanation Exception thrown while processing web services for Grammar

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-GRAMMAR_MGR- 2 -INVALID_SYSTEM_DIR : Invalid system grammar directory configured. Directory [String] Exception [String]

Explanation The configured system grammar directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-GRAMMAR_MGR- 3 -UNABLE_LOAD_GRAMMAR : Unable to load the grammar file. Name [String] Type [String] Language [String] Exception [String]

Explanation The Grammar Manager is unable to load the specified grammar file

Recommended Action Verify and update the configuration

Error Message
MCVD-GRAMMAR_MGR- 3 -UNSUPPORTED_CONVERSION : Unsupported grammar conversion. Type [String] Conversion Type [String] Exception [String]

Explanation The specified grammar conversion is not supported

Recommended Action Verify and update the application

Error Message
MCVD-LIB_AXL- 3 -SLEEP_AXL_EXCEPTION : Exception while sleeping for AXL. Exception [String]

Explanation Exception while sleeping for AXL

Recommended Action Verify and update the configuration

Error Message
MCVD-LIB_AXL- 3 -DUPLICATE_VALUE_AXL_EXCEPTION : Entered Duplicate Value. Exception [String]

Explanation Entered Duplicate Value

Recommended Action Verify and update the configuration

Error Message
MCVD-LIB_AXL- 3 -IO_AXL_EXCEPTION : IO AXL Exception. Exception [String]

Explanation IO AXL Exception

Recommended Action Verify and update the configuration

Error Message
MCVD-LIB_AXL- 3 -AXL_CONFIF_EXCEPTION : AXL Configuration Exception. Exception [String]

Explanation AXL Configuration Exception

Recommended Action Verify and update the configuration

Error Message
MCVD-LIB_AXL- 3 -RESOURCE_UNAVAILABLE_AXL_EXCEPTION : CCM AXL Server is busy. Exception [String]

Explanation CCM AXL Server is busy

Recommended Action Verify and update the configuration

Error Message
MCVD-LIB_AXL- 3 -UNKNOWN_HOST_AXL_EXCEPTION : Invalid CCM Hostname. Exception [String]

Explanation Invalid CCM Hostname

Recommended Action Verify and update the configuration

Error Message
MCVD-LIB_AXL- 3 -INVALID_USER_AXL_EXCEPTION : IIS Authentication failed on CCM. Exception [String]

Explanation IIS Authentication failed on CCM

Recommended Action Verify and update the configuration

Error Message
MCVD-LIB_AXL- 4 -AXL_TIMEOUT_DETECTED : AXL Timeout Detected. Cmd [String]

Explanation AXL Timeout Detected

Recommended Action No actions needed

Error Message
MCVD-LIB_AXL- 3 -AXL_EXCEPTION : Unknown AXL Exception. Exception [String]

Explanation Unknown AXL Exception

Recommended Action Verify and update the configuration

Error Message
MCVD-LIB_AXL- 3 -AXL_SOCKET_POOL_EXCEPTION : AXL can not initializa socket pool. Exception [String]

Explanation AXL can not initializa socket pool

Recommended Action Verify and update the configuration

Error Message
MCVD-LIB_CFG- 3 -NOTIFY_FAIL : Fail Notifying Remote Object. Exception [String]

Explanation Fail Notifying Remote Object

Recommended Action Verify and update the configuration

Error Message
MCVD-LIB_CFG- 4 -CUIC_REPORT_PERMISSIONS_ERROR : Grant or Revoke permissions to CUIC Folders and Reports failed. Exception [String]

Explanation Grant or Revoke permissions to CUIC Folders and Reports failed

Recommended Action No actions needed

Error Message
MCVD-LIB_CFG- 3 -INVALID_USER : User is invalid. User [String] Exception [String]

Explanation User could not be retrieved

Recommended Action Verify and update the configuration

Error Message
MCVD-LIB_CFG- 3 -INVALID_DATA_TYPE : DB operation failed because data type is invalid. ICD Config Data Type [String]

Explanation DB operation failed because data type is invalid

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-LIB_CFG- 6 -UNABLE_TO_ACQUIRE_CLUSTER_MUTEX : Cluster mutex lock could not be acquired. Name of thread trying to acquire lock [String] Exception [String]

Explanation Cluster mutex lock could not be acquired

Recommended Action No actions needed

Error Message
MCVD-LIB_CFG- 3 -REPOS_CFG_FAIL : Fail to access repository profile configuration. Exception [String]

Explanation Fail to create/retrieve/update/remove repository profile configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MCVD-LIB_CFG- 3 -GED_CONFIG_FAIL : Fail to retrieve GED 125 configuration. Exception [String]

Explanation Fail to retrieve GED 125 configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MCVD-LIB_CFG- 1 -UCCX_TO_CUIC_SYNC_FAILED : Notification to CUIC failed. UCCX TO CUIC SYNC failed for these resources::: [String]

Explanation Notification to CUIC on resource change failed

Recommended Action EXECUTE Resource sync command from CLI

Error Message
MCVD-LIB_CFG- 3 -JTAPI_CFG_FAIL : Fail to access JTAPI configuration. Exception [String]

Explanation Fail to create/retrieve/update/remove JTAPI configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MCVD-LIB_CFG- 3 -TAPI_GRP_CONFIG_FAIL : Fail to retrieve TAPI Port Group configuration. Exception [String]

Explanation Fail to retrieve TAPI Port Group configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MCVD-LIB_CFG- 6 -MASTER_CDS_CHANGE : The master CDS has changed. Master CDS Name [String]

Explanation The master CDS has changed

Recommended Action No actions needed

Error Message
MCVD-LIB_CFG- 3 -TELE_CFG_FAIL : Fail to create telephony application configuration. Exception [String]

Explanation Fail to create telephony application configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MCVD-LIB_CFG- 3 -ENG_SAVE_FAIL : Fail to save LDAP engine configuration. Exception [String]

Explanation Fail to save LDAP engine configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MCVD-LIB_CFG- 3 -PROFILE_CFG_FAIL : Fail to access profile configuration. Exception [String]

Explanation Fail to create/retrieve/update/remove profile configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MCVD-LIB_CFG- 3 -CONFIG_FAIL : Fail to load ldap configuration file. Exception [String]

Explanation Fail to load ldap configuration file

Recommended Action Verify and update the configuration

Error Message
MCVD-LIB_CFG- 3 -GED_SCRIPT_CFG_FAIL : Fail to retrieve GED 125 Script configuration. Exception [String]

Explanation Fail to retrieve GED 125 Script configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MCVD-LIB_CFG- 3 -VOICE_CFG_FAIL : Fail to access Voice configuration. Exception [String]

Explanation Fail to create/retrieve/update/remove Voice configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MCVD-LIB_CFG- 3 -GED_ROUTE_CFG_FAIL : Fail to retrieve GED 125 Route configuration. Exception [String]

Explanation Fail to retrieve GED 125 Route configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MCVD-LIB_CFG- 3 -PROVIDER_UNAVAILABLE : LDAP provider is unavailable. ldap url base [String] Exception [String]

Explanation LDAP provider is unavailable

Recommended Action Verify and update the configuration

Error Message
MCVD-LIB_CFG- 3 -HTTP_CFG_FAIL : Fail to access HTTP configuration. Exception [String]

Explanation Fail to create/retrieve/update/remove HTTP configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MCVD-LIB_CFG- 4 -REMOTE_OBJ_FAIL : Remote object could not be retrieved. remote object name [String] Exception [String]

Explanation Remote object could not be retrieved

Recommended Action No actions needed

Error Message
MCVD-LIB_CFG- 3 -INI_SAVE_FAIL : Fail to save ini ldap configuration file. Exception [String]

Explanation Fail to save ini ldap configuration file

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-LIB_CFG- 3 -ENGINE_CONFIG_FAIL : LDAP Engine Configuration fail to initialize. Exception [String]

Explanation LDAP Engine Configuration fail to initialize

Recommended Action Verify and update the configuration

Error Message
MCVD-LIB_CLUSTER_CFG- 6 -MUTEX_SUCCESSFULLY_RENEWED : Mutex successfully renewed. owner [String] usage [String] userInfo [String] leaseDate [String]

Explanation Mutex successfully renewed

Recommended Action No actions needed

Error Message
MCVD-LIB_CLUSTER_CFG- 4 -INVALID_MUTEX_OWNER : Invalid Mutex owner. cmd [String] lockOwner [String] owner [String] usage [String] userInfo [String]

Explanation The specified cmd was requested by a different owner than the original owner who acquired the mutex, which is not permitted

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-LIB_CLUSTER_CFG- 3 -CONFIG_ERROR : Error while accessing LockConfig. owner [String] usage [String] userInfo [String] Exception [String]

Explanation Error while accessing LockConfig

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-LIB_CLUSTER_CFG- 4 -MUTEX_EXPIRED : Mutex expired. cmd [String] lockOwner [String] leaseDate [String] owner [String] usage [String] userInfo [String]

Explanation The mutex lease has expired when the specified cmd is received

Recommended Action No actions needed

Error Message
MCVD-LIB_CLUSTER_CFG- 6 -MUTEX_SUCCESSFULLY_ACQUIRED : Mutex successfully acquired. owner [String] usage [String] userInfo [String]

Explanation Mutex successfully acquired

Recommended Action No actions needed

Error Message
MCVD-LIB_CLUSTER_CFG- 6 -MUTEX_SUCCESSFULLY_RELEASED : Mutex successfully released. owner [String] usage [String] userInfo [String]

Explanation Mutex successfully released

Recommended Action No actions needed

Error Message
MCVD-LIB_DATABASE- 6 -RECOVERY_COMPLETED_EVENT : Received recovery completed event; DB alias will be synched now.

Explanation Database component detected recovery completed event; DB alias will be synched now.

Recommended Action No actions needed

Error Message
MCVD-LIB_DATABASE- 3 -SUBSCRIBER_DB_UNAVAILABLE : Subscriber database is not running or inaccessible.

Explanation An attempt to connect to the subscriber database has failed. Verify that the subscriber database is functioning and network connectivity is available to the subscriber node.

Recommended Action Investigate as required

Error Message
MCVD-LIB_DATABASE- 6 -UPLOAD_USER_FILE_FAILED : Database Archive Component fails to upload the corresponding file or directory to Repository Datastore. It will be copied to the specified temporary location. file or directory name [String] temporary directory name [String] Exception [String]

Explanation Database Archive Component fails to upload the corresponding file or directory to Repostiory Datastore during upgrade migration. The file or directory will be copied to the specified temporary directory.

Recommended Action Investigate as required

Error Message
MCVD-LIB_DATABASE- 3 -DATABASE_ERROR : A generic database error. Exception [String]

Explanation A generic database error occured, this could be related to SQL or none-SQL related.

Recommended Action Investigate as required

Error Message
MCVD-LIB_DATABASE- 3 -UPDATE_ERROR : update error. Exception [String]

Explanation Error in updating the cluster info

Recommended Action Investigate as required

Error Message
MCVD-LIB_DATABASE- 3 -COPYING_USER_FILES_FAILED : Database Archive Component fails to copy the corresponding file or directory to temporary location. file or directory name [String] temporary directory name [String] Exception [String]

Explanation Database Archive Component fails to copy the corresponding file or directory to temporary location, in an attempt to save the file after it fails to upload it to Repository datastore.

Recommended Action Investigate as required

Error Message
MCVD-LIB_DATABASE- 3 -DB_REPLICATION_ERROR : A generic database replication error. Exception [String]

Explanation A generic database replication error occured, this could be related to SQL or none-SQL related.

Recommended Action Investigate as required

Error Message
MCVD-LIB_DATABASE- 1 -DB_REPLICATION_STOPPED : Database replication stopped. Reason for Stopping Replication [String] Exception [String]

Explanation Database replication is stopped. Please Setup Replication from DataStore Control Center, after bringing the other node up.

Recommended Action Investigate as required

Error Message
MCVD-LIB_DATABASE- 6 -SCRIPT_NOT_FOUND : Database Archive Component could not find the corresponding file or directory to upload during restore. file or directory location [String]

Explanation Database Archive Component could not find the corresponding file or directory to upload during restore

Recommended Action Investigate as required

Error Message
MCVD-LIB_DATABASE- 1 -DB_NOT_IN_SYNC : Database is not in sync on both nodes.

Explanation One of more tables in Database are not in sync across nodes. Please Check whether replication is working fine. If replication is broken, reset replication else synchronize data on both nodes using forced data sync from CLI

Recommended Action Investigate as required

Error Message
MCVD-LIB_DATABASE- 6 -DB_REPLICATION_INITIALIZING : DB Replication is getting initialized.

Explanation DB Replication is getting initialized

Recommended Action No actions needed

Error Message
MCVD-LIB_DATABASE- 3 -INIT_ERROR : read error. Exception [String]

Explanation error in reading

Recommended Action Investigate as required

Error Message
MCVD-LIB_DATABASE- 4 -REPLICATION_OLD_PUBLISHER_CLEANUP_FAIL : DB Replication old publisher cleanup failed. Old Publisher [Int] Exception [String]

Explanation Failed to cleanup the old publisher role while performing a switch publisher

Recommended Action No actions needed

Error Message
MCVD-LIB_DATABASE- 6 -RECOVERY_DETECTED : Detected a recovery archive request in the system; DB alias sync is postponed until recovery is complete..

Explanation Database component detected a recovery archive request in the system; DB alias sync is postponed until recovery is complete.

Recommended Action No actions needed

Error Message
MCVD-LIB_EVENT- 3 -DISPATCH_FAILURE : A failure occured while dispatching an event. Event [String] Event source [String] Event listener [String] Exception [String]

Explanation An uncaught error occured while dispatching an event

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-LIB_EVENT- 5 -TOO_LONG_IN_QUEUE : Event queue time exceeded. Event [String] Queue Time [Long]

Explanation The specified event stayed in queue for too long

Recommended Action No actions needed

Error Message
MCVD-LIB_EVENT- 4 -EVENT_INIT_FAILURE : Unable to initialize the system event queue logger. Exception [String]

Explanation The logger could not be registered with the system event queue; the traces for the event queue will not be available

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-LIB_JASPER- 6 -MSG : . Message [String] Exception [String]

Explanation See log message for more info.

Recommended Action Investigate as required

Error Message
MCVD-LIB_JASPER- 6 -MMSG : . Module [String] Message [String] Exception [String]

Explanation See module's log message for more info.

Recommended Action Investigate as required

Error Message
MCVD-LIB_LDAP- 3 -LDAP_CON_ERROR : Error accessing LDAP. ldap url [String] Exception [String]

Explanation An error occurred while accessing LDAP

Recommended Action No actions needed

Error Message
MCVD-LIB_LDAP- 4 -LDAP_CON_WARNING : Problem accessing LDAP. ldap url [String] Exception [String]

Explanation An problem occurred while accessing LDAP

Recommended Action No actions needed

Error Message
MCVD-LIB_LICENSE- 3 -LICENSE_CONFIG_UNAVAILABLE_ERROR : LicenseConfig unavailable or retrieve error. Exception [String]

Explanation LicenseConfig was not accessible or the license object does not exist

Recommended Action Investigate as required

Error Message
MCVD-LIB_LICENSE- 3 -LICENSE_VM_CONFIG_ERROR : OVA Template Mismatched. VM configuration does not match the OVA Profile..

Explanation OVA Template Mismatched. VM configuration does not match the OVA Profile.

Recommended Action Please refer to the Unified CCX Virtualization DocWiki for the supported VM configurations.

Error Message
MCVD-LIB_LICENSE- 6 -NO_LICENSE : No Licenses were found. Error reason [String]

Explanation objFile returned from LDAP is null or it does not contain any valid licenses

Recommended Action No actions needed

Error Message
MCVD-LIB_LICENSE- 2 -LICENSE_PACKAGE_NONE : Upload a valid license through the Cisco Unified CCX Application Administration.. Error reason [String]

Explanation Cisco Unified CCX license package is None.Upload a valid license through Cisco Unified CCX Application Administration.

Recommended Action Verify and update the licences

Error Message
MCVD-LIB_LICENSE- 3 -RMI_LICENSE_ERROR : RMI Remote License error. Exception [String]

Explanation A problem occurred while trying to register RMI Remote License Implementation

Recommended Action Verify the RMI configuration and restart server

Error Message
MCVD-LIB_LICENSE- 3 -LICENSE_REPOSITORY_UNAVAILABLE_ERROR : Config repository inaccessible. Exception [String]

Explanation A problem occurred when trying to read licenses from the Config repository

Recommended Action Investigate as required

Error Message
MCVD-LIB_LICENSE- 3 -LICENSE_CONFIG_ERROR : Access license config error. Exception [String]

Explanation A problem occurred when trying to retrieve licenses from the license config object

Recommended Action Investigate as required

Error Message
MCVD-LIB_LICENSE- 3 -LICENSE_READ_ERROR : License read error. Exception [String]

Explanation A problem occurred when trying to read license files

Recommended Action Investigate as required

Error Message
MCVD-LIB_LICENSE- 3 -LICENSE_REPOSITORY_ERROR : License Repository error. Exception [String]

Explanation A problem occurred when trying to read licenses from the Config repository

Recommended Action Investigate as required

Error Message
MCVD-LIB_LICENSE- 6 -LICENSE_INFO : License Information. Licenses [String]

Explanation The cluster was configured with the specified licenses enabled.

Recommended Action No actions needed

Error Message
MCVD-LIB_LICENSE- 3 -LICENSE_TIME_EXPIRED : Upload a valid license through the Cisco Unified CCX Application Administration.. Error reason [String]

Explanation One or More Temporary License(s) have expired. The corresponding features would become unusable. Please upload valid license for the same through Cisco Unified CCX Application Administration.

Recommended Action Verify and update the licences

Error Message
MCVD-LIB_RMI- 5 -RMI_LOG_MONITOR_FAIL : RMI log configuration monitoring failure.

Explanation RMI layer can no longer monitor dynamic update to its log configuration; debug messages disabled

Recommended Action No actions needed

Error Message
MCVD-LIB_SERVLET- 6 -MSG : . Message [String] Exception [String]

Explanation See log message for more info.

Recommended Action Investigate as required

Error Message
MCVD-LIB_SERVLET- 6 -MMSG : . Module [String] Message [String] Exception [String]

Explanation See module's log message for more info.

Recommended Action Investigate as required

Error Message
MCVD-LIB_TC- 6 -MSG : . Message [String] Exception [String]

Explanation See log message for more info.

Recommended Action Investigate as required

Error Message
MCVD-LIB_TC- 6 -MMSG : . Module [String] Message [String] Exception [String]

Explanation See module's log message for more info.

Recommended Action Investigate as required

Error Message
MCVD-LIB_TPL- 6 -TPL_INFO : TPL_LOG4J Info log. A specific description for a trace [String]

Explanation TPL_LOG4J Info log

Recommended Action No actions needed

Error Message
MCVD-LIB_TPL- 3 -TPL_ERROR : Error in ThirdParty library. A specific description for a trace [String] A description for the nature of the exception [String] Exception [String]

Explanation Error in ThirdParty library

Recommended Action No actions needed

Error Message
MCVD-LIB_TPL- 5 -TPL_LOG4J_LOG_MONITOR_FAIL : TPL log configuration monitoring failure.

Explanation TPL logs layer can no longer monitor dynamic update to its log configuration; debug messages disabled

Recommended Action No actions needed

Error Message
MCVD-LIB_TPL- 6 -TPL_LOG4J_LOG_MONITOR : TPL log. message [String] error_desc [String]

Explanation Hibernate and Atomikos logs

Recommended Action No actions needed

Error Message
MCVD-LOG_MGR- 2 -MGR_PARTIAL_SERVICE : Log Manager in partial service.

Explanation The Log Manager is in partial service; logs won't be completely availablew

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-LOG_MGR- 3 -XML_PARSING_ERROR : XML parsing error. Catalog [String] Public identifier [String] System identifier [String] Line number [Int] Column number [Int] Exception [String] Nested Exception [String]

Explanation The log manager could not parse the XML log catalog

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-LOG_MGR- 6 -MGR_IN_SERVICE : Log Manager in service.

Explanation The Log Manager is in service

Recommended Action No actions needed

Error Message
MCVD-LOG_MGR- 4 -INTERRUPT : Log generation interrupted. Catalog [String] Mnemonic [String] Exception [String]

Explanation The generation of a log was interrupted

Recommended Action Restart server

Error Message
MCVD-LOG_MGR- 4 -LOG_CFG_MONITOR_FAIL : Log levels configuration monitoring failure. Exception [String]

Explanation The Log Manager can no longer monitor dynamic update to the log levels configuration; tracing can no longer be turned on or off

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-LOG_MGR- 4 -TO_STRING_FAILURE : Log toString() conversion failure. Catalog [String] Mnemonic [String] Parameter index [Int] Exception [String]

Explanation The log writer is unable to convert the given parameter in the specified log to a string

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-LOG_MGR- 5 -MGR_SHUTDOWN : Log Manager in shutdown.

Explanation The Log Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MCVD-LOG_MGR- 6 -MGR_INITIALIZING : Log Manager initializing.

Explanation The Log Manager is initializing

Recommended Action No actions needed

Error Message
MCVD-LOG_MGR- 2 -MGR_OUT_OF_SERVICE : Log Manager in out of service.

Explanation The Log Manager is out of service; logs won't be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-LOG_MGR- 5 -MGR_SHUTTING_DOWN : Log Manager shutting down.

Explanation The Log Manager is in the process of shutting down; pending logs are being flushed out

Recommended Action No actions needed

Error Message
MCVD-LOG_MGR- 3 -UNABLE_LOAD_CATALOG : Unable to load log catalog. Catalog [String] Exception [String] Nested Exception [String]

Explanation The log manager could not load the log catalog

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-LOG_MGR- 6 -CATALOG_LOADED : Log catalog loaded. Catalog [String]

Explanation The specified log catalog was loaded in memory

Recommended Action No actions needed

Error Message
MCVD-LOG_MGR- 3 -WRITER_FAILURE : Log writer failure. Catalog [String] Exception [String]

Explanation The log writer failed to properly initialize for the log catalog

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-MGR_MGR- 6 -MGR_ALREADY_INIT : Manager initialization failed. Exception [String]

Explanation A manager in the Manager Manager failed to initialize because it has already been loaded.

Recommended Action Investigate as required

Error Message
MCVD-MGR_MGR- 1 -MGR_PARTIAL_SERVICE : Manager Manager in partial service.

Explanation Some managers are currently out of service

Recommended Action Investigate as required

Error Message
MCVD-MGR_MGR- 2 -NETWORK_FAILURE_DETECTED : lookup on local host resolved to loopback address. Please check network connectivity.

Explanation lookup on local host resolved to loopback address. Please check network connectivity.

Recommended Action Investigate as required

Error Message
MCVD-MGR_MGR- 1 -MGR_CONFIG_ERROR : Error while reading configuration file for ManagerManager. Exception [String]

Explanation Error while reading configuration file for ManagerManager

Recommended Action Verify and update the configuration and restart server

Error Message
MCVD-MGR_MGR- 3 -MGR_XML_PARSE_ERROR : Could not create URL while parsing xml data. Exception [String]

Explanation Could not create URL while parsing xml data

Recommended Action Verify and update the configuration and restart server

Error Message
MCVD-MGR_MGR- 1 -RMI_FAILURE_RETRY : RMI could not be configured at the specified port. Will attempt to retry.. Exception [String]

Explanation RMI could not be configured at the specified port. Will attempt to retry.

Recommended Action Verify the RMI configuration and restart server

Error Message
MCVD-MGR_MGR- 3 -THREAD_DEATH_EXCEPTION : An uncaught exception has be thrown in a thread. Thread name [String] Exception [String]

Explanation An uncaught exception has be thrown in a thread

Recommended Action Investigate as required

Error Message
MCVD-MGR_MGR- 0 -MGRMGR_KEEPALIVE_EXCPT : A KeepAlive exception has been thrown in Manager Manager. Exception [String]

Explanation A KeepAlive exception has been thrown in Manager Manager

Recommended Action Investigate as required

Error Message
MCVD-MGR_MGR- 0 -MGRMGR_START_FAIL : Fail to start Application startable class. Exception [String]

Explanation Manager Manager fail to start the startable class

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-MGR_MGR- 4 -CLASSPATH_NOT_LOADED : A classpath was not loaded during initialization. Exception [String]

Explanation A classpath was not loaded during initialization

Recommended Action No actions needed

Error Message
MCVD-MGR_MGR- 6 -MGR_INITIALIZING : Manager Manager initializing.

Explanation The Manager Manager is initializing

Recommended Action No actions needed

Error Message
MCVD-MGR_MGR- 2 -MGR_OUT_OF_SERVICE : Manager Manager in out of service.

Explanation All primary managers are out of service

Recommended Action Investigate as required

Error Message
MCVD-MGR_MGR- 3 -MANAGER_INTERCEPT_ERROR : Manager interceptor error operation. Error reason [String] Exception [String]

Explanation Manager interceptor encountered an error while performing the following operation

Recommended Action No actions needed

Error Message
MCVD-MGR_MGR- 0 -MGRMGR_INIT_FAIL : Fail to initialize Manager Manager and start main thread. Exception [String]

Explanation Fail to initialize Manager Manager and start main thread

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-MGR_MGR- 6 -MGR_IN_SERVICE : Manager Manager in service.

Explanation The Manager Manager is in service

Recommended Action No actions needed

Error Message
MCVD-MGR_MGR- 0 -APP_SVC_INIT_ERROR : Application services initialization error. Exception [String]

Explanation The Application services could not be initialized because the RMI registry could not be accessed

Recommended Action Verify the RMI configuration and restart server

Error Message
MCVD-MGR_MGR- 6 -MGRMGR_PERFMON_INIT_SUCCESS : Application successfully initialized perfmon dll.

Explanation The Application services loaded the WFCCNPerfWin32 dll

Recommended Action No actions needed

Error Message
MCVD-MGR_MGR- 1 -BOOTSTRAP_INIT_ERROR : Error occurred while initializing bootstrap information. Exception [String]

Explanation Error occurred while initializing bootstrap information

Recommended Action Verify and update the configuration and restart server

Error Message
MCVD-MGR_MGR- 1 -CURRENCY_CFG_MONITOR_FAIL : Currency configuration monitoring failure. Exception [String]

Explanation The system default currency can no longer be updated dynamically

Recommended Action Investigate as required

Error Message
MCVD-MGR_MGR- 1 -WEB_SERVICE_ERROR : Web service initialization error. Error reason [String]

Explanation Web service initialization error

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-MGR_MGR- 4 -IP_HOSTNAME_UPDATE : Host Name of one of the UCCX Servers in cluster is changed. Old Host Name [String] New Host Name [String]

Explanation Host Name of one of the UCCX Servers in cluster is changed

Recommended Action No actions needed

Error Message
MCVD-MGR_MGR- 3 -CLASSPATH_NOT_FOUND : Configured classpath is not found. Exception [String]

Explanation Configured classpath is not found

Recommended Action Verify and update the configuration and restart server

Error Message
MCVD-MGR_MGR- 3 -HOSTFILE_ERROR : An error occurred while trying to access host file. Exception [String]

Explanation An error occurred while trying to access host file

Recommended Action Verify and update the configuration

Error Message
MCVD-MGR_MGR- 3 -MGRMGR_ROOTDIR_ERROR : No root directory path found in properties file.

Explanation No root directory path found in properties file

Recommended Action No actions needed

Error Message
MCVD-MGR_MGR- 1 -HIGH_MEM_USAGE : JVM heap memory usage is high. Facility [String] Current usage [String] Maximum available [String] percentage Old Gen Memory used [Int]

Explanation JVM heap memory usage is high

Recommended Action Investigate as required

Error Message
MCVD-MGR_MGR- 5 -MGRMGR_KEEPALIVE_EXCPT_CANCEL : Manager Manager is attempting to cancel KeepAlive exception. Exception [String]

Explanation KeepAlive exception is cancelled in ManagerManager because the manager in question return from a timeout. Note that this does not mean Node Manager did not detect the KeepAlive exception. It might be that Node Manager detected the exception while ManagerManager is cancelling it.

Recommended Action No actions needed

Error Message
MCVD-MGR_MGR- 1 -APP_CFG_SYNC_FAIL : Application configuration failure. Exception [String]

Explanation The Manager Manager could not retrieve configuration information from the Config Framework. Using local configuration.

Recommended Action Investigate as required

Error Message
MCVD-MGR_MGR- 1 -RMI_PORT_CONFIGURATION_FAILURE : Failed to configure new rmi port. Old Port [String] New Port [String]

Explanation Cannot modify rmi port to the configured value since port is in use by another application. Please change rmi port configuration using CRS Administrator.

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-MGR_MGR- 6 -DEFAULT_CURRENCY_UPDATE : System default currency updated. Currency [String]

Explanation The system default currency was updated

Recommended Action No actions needed

Error Message
MCVD-MGR_MGR- 5 -MGR_SHUTTING_DOWN : Manager Manager in shutting down.

Explanation The Manager Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MCVD-MGR_MGR- 1 -REGISTRY_INIT_ERROR : An error occurred during initialization of registry. Exception [String]

Explanation RMI Registry could not be initialized.

Recommended Action Verify the RMI configuration and restart server

Error Message
MCVD-MGR_MGR- 4 -CUSTOM_PROP_NOT_FOUND : CustomFileClasspath.properties file is not found.

Explanation CustomFileClasspath.properties file is not found

Recommended Action No actions needed

Error Message
MCVD-MGR_MGR- 1 -REGISTRY_RETRY_ERROR : Maximum retries reached trying to create registry. No registry created.. Registry retry value [String]

Explanation Maximum retries reached trying to create registry. No registry created.

Recommended Action Verify the RMI configuration and restart server

Error Message
MCVD-MGR_MGR- 6 -REGISTRY_RETRY_INFO : Could not create registry at specified port. Will retry at different port. Port [String]

Explanation ManagerManager could not create registry at specified port. Will retry at different port

Recommended Action No actions needed

Error Message
MCVD-MGR_MGR- 1 -BOOTSTRAP_SYNC_ERROR : ManagerManager bootstrap sync failure. Exception [String]

Explanation ManagerManager cannot synchronize the bootstrap information due to the following problem

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-MGR_MGR- 4 -MANAGER_INTERCEPT_WARNING : Manager interceptor warning. Reason for this warning [String]

Explanation Manager interceptor warning log info

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-MGR_MGR- 1 -APP_CFG_MONITOR_FAIL : Application configuration monitoring failure. Exception [String]

Explanation The Manager Manager can no longer monitor dynamic update to some of its configuration

Recommended Action Investigate as required

Error Message
MCVD-MGR_MGR- 1 -MGR_INIT_ERROR : Manager initialization error. Exception [String]

Explanation A manager in the Manager Manager cannot be instantiated and will not be available

Recommended Action Investigate as required

Error Message
MCVD-MGR_MGR- 0 -UNRECOVERABLE_ERROR : An unrecoverable error has occurred. Exception [String]

Explanation An unrecoverable error has occurred

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-MGR_MGR- 3 -MGRMGR_SHUTDOWN_FAIL : An exception occurred while shutting down Manager Manager. Exception [String]

Explanation An exception occurred while shutting down Manager Manager

Recommended Action Investigate as required

Error Message
MCVD-MGR_MGR- 5 -MGR_SHUTDOWN : Manager Manager in shutdown.

Explanation The Manager Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MCVD-MGR_MGR- 4 -IP_ADDRESS_UPDATE : IP Address of one of the UCCX Servers in cluster is changed. Old IP Address [String] New IP Address [String]

Explanation IP Address of one of the UCCX Servers in cluster is changed

Recommended Action No actions needed

Error Message
MCVD-MGR_MGR- 3 -MGRMGR_BEAN_ERROR : Error setting design time bean. Exception [String]

Explanation There was an error setting the design time bean

Recommended Action No actions needed

Error Message
MCVD-MGR_MGR- 0 -THREADS_DUMP : Java Virtual Machine Threads Dump. Message [String] Exception [String]

Explanation A dump of all running threads was just produced in JVM.log. Collect all existing logs and the JVM.log file and forward them to Cisco.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-MGR_MGR- 3 -GET_DEFAULT_USER_ERROR : Default User could not be retrieved. Exception [String]

Explanation Default User could not be retrieved due to the following error

Recommended Action No actions needed

Error Message
MCVD-MGR_MGR- 1 -MEMORY_USAGE_EXCEEDED_THRESHOLD : Memory usage exceeded the threshold set. Facility [String] Current usage [String] Maximum available [String] percentage Heap memory used [Int]

Explanation Memory usage exceeded the threshold set

Recommended Action Investigate as required

Error Message
MCVD-MGR_MGR- 1 -SYS_CFG_SYNC_FAIL : System configuration failure. Exception [String]

Explanation The Manager Manager could not retrieve system configuration from the Config Framework. Using local configuration.

Recommended Action Investigate as required

Error Message
MCVD-MGR_MGR- 1 -RMI_CREATE_ERROR : Cannot create rmi registry at specified port location. Port [String] Exception [String]

Explanation Cannot create rmi registry at specified port location since port is in use by another application. Please change rmi port configuration using CRS Administrator or shutdown the process using the specified port.

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-MGR_MGR- 1 -SYS_CFG_MONITOR_FAIL : System configuration monitoring failure. Exception [String]

Explanation The Manager Manager can no longer monitor dynamic update to the system configuration

Recommended Action Investigate as required

Error Message
MCVD-NODE_MGR- 3 -NODE_MGR_STOPNODE_ERROR : Can't stop and restart the node manager and its controlled processes. Exception [String]

Explanation Can't stop and restart the node manager and its controlled processes

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-NODE_MGR- 3 -NODE_MGR_SERVICE_START_ERROR : Can't start service. service name [String] Exception [String]

Explanation Can't start service

Recommended Action Retry the operation and if problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-NODE_MGR- 3 -NODE_MGR_REMOVE_LISTENER_ERROR : Could not remove Node listener. Exception [String]

Explanation Could not remove node listener from node manager

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-NODE_MGR- 0 -NODE_MGR_SERVICE_CRASH_DETECTED : Node manager detected service crash. service name [String]

Explanation Node manager detected service crash

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-NODE_MGR- 1 -NODE_MGR_DESTROY_ERROR : Destroy Node Manager failed. Exception [String]

Explanation Destroy the native node manager failed

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-NODE_MGR- 1 -MEDIASENSE_STATUS_DOWN : One or more configured Mediasense nodes are down or unreachable from this CCX..

Explanation One or more configured Mediasense nodes are down or unreachable from this CCX.

Recommended Action Bring Mediasense node(s) UP, then update Recording Server Configuration to re-subscribe CCX for Mediasense session events.

Error Message
MCVD-NODE_MGR- 3 -NODE_MGR_SERVICE_ACTIVATE_ERROR : Can't activate the service. service name [String] Exception [String]

Explanation Can't activate the service

Recommended Action Retry the operation and if problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-NODE_MGR- 3 -NODE_MGR_SERVICE_DEACTIVATE_ERROR : Can't deactivate the service. process name [String] Exception [String]

Explanation Can't deactivate the service

Recommended Action Retry the operation and if problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-NODE_MGR- 3 -NODE_MGR_SETFAILUREREASON_ERROR : Set service failure reason failed. Exception [String]

Explanation Set a service failure reason to display in Unified CCX Administration failed

Recommended Action No actions needed

Error Message
MCVD-NODE_MGR- 3 -NODE_MGR_STARTNODE_ERROR : Can't start the node manager and its controlled processes. opeartion failure source [String]

Explanation Can't start the node manager and its controlled processes

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-NODE_MGR- 1 -NODE_MGR_KEEP_ALIVE_ERROR : Node Manager keep alive ping failed. Exception [String]

Explanation Node manager keep alive ping failed

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-NODE_MGR- 3 -NODE_MGR_SERVICE_RESTART_ERROR : Can't restart service. service name [String] Exception [String]

Explanation Can't restart service

Recommended Action Retry the operation and if problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-NODE_MGR- 0 -NODE_MGR_SERVICE_MONITOR_THREAD_FAILED : Node manager service Monitor thread failed. Exception [String]

Explanation Node manager service Monitor thread failed

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-NODE_MGR- 3 -NODE_MGR_SERVICE_STOP_ERROR : Can't stop service. service name [String] Exception [String]

Explanation Can't stop service

Recommended Action Retry the operation and if problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-NODE_MGR- 0 -GENERAL_JVM_DEADLOCK_ERROR : A JVM deadlock has been detected. Exception [String]

Explanation A JVM deadlock has been detected. Copy out any JVM.log under log/MCVD MADM MIVR directory

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-NODE_MGR- 3 -NODE_MGR_ADD_LISTENER_ERROR : Could not add Node listener. Exception [String]

Explanation Could not add node listener to node manager

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-PROMPT_MGR- 1 -MGR_PARTIAL_SERVICE : Prompt Manager in partial service.

Explanation The Prompt Manager is in partial service; synchronization of files with prompt repository is in progress

Recommended Action Investigate as required

Error Message
MCVD-PROMPT_MGR- 3 -INVALID_TTS_PROVIDER : Invalid TTS prompt provider. Name [String] Exception [String]

Explanation The specified TTS prompt provider is invalid

Recommended Action Verify and update the configuration

Error Message
MCVD-PROMPT_MGR- 2 -INVALID_USER_DIR : Invalid user prompt directory configured. Directory [String] Exception [String]

Explanation The configured user prompt directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-PROMPT_MGR- 3 -UNDEFINED_GENERATED_PROMPT : Undefined generated prompt. Generated Prompt [String] Language [String] Exception [String]

Explanation Unable to resolve the generated prompt

Recommended Action Verify and update the application and if problem persist contact Cisco technical assistance center

Error Message
MCVD-PROMPT_MGR- 6 -GENERATOR_FALLBACK : Falling back to system prompt generators. Generated Prompt [String] Generator Constructor [String] Bundle [String] Language [String] Exception [String]

Explanation The Prompt Manager failed to use the prompt generator bundle specified by the generated prompt and is falling back to the systemprompt generators

Recommended Action Verify and update the application

Error Message
MCVD-PROMPT_MGR- 3 -UNSUPPORTED_PROMPT : Unsupported prompt type. Name [String] Type [String] Language [String] Exception [String]

Explanation The specified prompt type is not supported

Recommended Action Verify and update the application

Error Message
MCVD-PROMPT_MGR- 3 -PROMPT_LEXICAL_ERROR : Template prompt lexical error. Name [String] Template [String] Language [String] Exception [String]

Explanation The specified lexical error occured while parsing a template prompt

Recommended Action Verify and update the application

Error Message
MCVD-PROMPT_MGR- 3 -UNDEFINED_NAME_PROMPT : Undefined user or system prompt. Name [String] Type [String] Transcription [String] Language [String] Exception [String]

Explanation A user or system prompt cannot be located

Recommended Action Verify and update the configuration

Error Message
MCVD-PROMPT_MGR- 3 -UNDEFINED_TTS_PROMPT : Undefined TTS prompt. Name [String] Transcription [String] Language [String] Exception [String]

Explanation A TTS prompt cannot be generated

Recommended Action Verify and update the configuration and restart server

Error Message
MCVD-PROMPT_MGR- 3 -UNDEFINED_SILENCE_PROMPT : Undefined silence prompt. Silence Duration [Long] Exception [String]

Explanation A silence prompt cannot be located

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-PROMPT_MGR- 3 -PROMPT_FILE_SUPPORT_FAILURE : Prompt file support failure. Exception [String]

Explanation The Prompt Manager can not register file support for user prompt files; user prompts will not be synchronized on local server

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-PROMPT_MGR- 6 -MGR_INITIALIZING : Prompt Manager initializing.

Explanation The Prompt Manager is initializing

Recommended Action No actions needed

Error Message
MCVD-PROMPT_MGR- 2 -MGR_OUT_OF_SERVICE : Prompt Manager in out of service.

Explanation The Prompt Manager is out of service; prompts won't be accessible

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-PROMPT_MGR- 5 -MGR_SHUTTING_DOWN : Prompt Manager shutting down.

Explanation The Prompt Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MCVD-PROMPT_MGR- 6 -SYSTEM_TTS_PROVIDER : System TTS provider registered. Name [String]

Explanation A system TTS prompt provider has been registered

Recommended Action No actions needed

Error Message
MCVD-PROMPT_MGR- 6 -MGR_IN_SERVICE : Prompt Manager in service.

Explanation The Prompt Manager is in service

Recommended Action No actions needed

Error Message
MCVD-PROMPT_MGR- 5 -MGR_SHUTDOWN : Prompt Manager in shutdown.

Explanation The Prompt Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MCVD-PROMPT_MGR- 3 -UNABLE_CREATE_TTS : Unable to instantiate TTS prompt provider. Name [String] Classname [String] Exception [String]

Explanation The specified TTS prompt provider cannot be located or instantiated

Recommended Action Verify and update the configuration and restart server

Error Message
MCVD-PROMPT_MGR- 3 -PROMPT_PARSING_ERROR : Template prompt parsing error. Name [String] Template [String] Language [String] Exception [String]

Explanation The specified error occured while parsing a template prompt

Recommended Action Verify and update the application

Error Message
MCVD-PROMPT_MGR- 6 -NO_SYSTEM_TTS_PROVIDER : No system TTS provider registered.

Explanation There is no system TTS prompt provider currently registered

Recommended Action Verify and update the configuration

Error Message
MCVD-PROMPT_MGR- 6 -TTS_PROVIDER_FALLBACK : Falling back to system configured TTS provider. Transcription [String] Language [String] Name [String] Exception [String]

Explanation The Prompt Manager failed to use the TTS prompt provider specified by the TTS prompt and is falling back to the system TTS prompt provider

Recommended Action Verify and update the application

Error Message
MCVD-PROMPT_MGR- 3 -UNDEFINED_GENERATOR : Undefined prompt generator. Generated Prompt [String] Generator Constructor [String] Bundle [String] Language [String] Exception [String]

Explanation The Prompt Manager failed to locate a prompt generator as requested

Recommended Action Verify and update the application and if problem persist contact Cisco technical assistance center

Error Message
MCVD-PROMPT_MGR- 3 -INVALID_GENERATOR : Invalid prompt generator. Generated Prompt [String] Generator Name [String] Generator Constructor [String] Language [String] Exception [String]

Explanation The Prompt Manager failed to instantiate the rquested prompt generator

Recommended Action Verify and update the application and if problem persist contact Cisco technical assistance center

Error Message
MCVD-PROMPT_MGR- 3 -WEBSERVICES_ERROR : Exception thrown while processing web services for Prompt. Exception [String]

Explanation Exception thrown while processing web services for Prompt

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-PROMPT_MGR- 2 -INVALID_SYSTEM_DIR : Invalid system prompt directory configured. Directory [String] Exception [String]

Explanation The configured system prompt directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-PURGING- 1 -AUTO_PURGE_COMPLETE : Auto purge completion information.. Message Description [String]

Explanation Auto purge completion information.

Recommended Action No actions needed

Error Message
MCVD-PURGING- 3 -PURGE_ERROR : An exception has been caught.. Message Description [String] Exception [String]

Explanation An exception has been caught.

Recommended Action An exception has been caught.

Error Message
MCVD-PURGING- 3 -EMAIL_NOTIFY_ERROR : Error in sending email notification. Exception [String]

Explanation Not able to read email server info

Recommended Action Check the email server config

Error Message
MCVD-PURGING- 6 -PURGE_PROCESS_INFO : Purge process information.. Message Description [String]

Explanation Purge process information.

Recommended Action No actions needed

Error Message
MCVD-PURGING- 6 -SET_PURGE_CONFIG : Set purge config information.. Message Description [String]

Explanation Set purge config information.

Recommended Action No actions needed

Error Message
MCVD-PURGING- 6 -PURGE_INFO : Purging information. Message Description [String]

Explanation Purging information

Recommended Action No actions needed

Error Message
MCVD-PURGING- 6 -GET_PURGE_CONFIG : Auto purge config information.. Message Description [String]

Explanation Auto purge config information.

Recommended Action No actions needed

Error Message
MCVD-REST_CLIENT- 0 -REST_CLIENT_ERROR : Unable to invoke the rest API. Exception [String]

Explanation Invoking the rest API failed with errors

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-REST_CLIENT- 1 -UCCX_TO_CUIC_SYNC_FAILED : Notification to CUIC failed. UCCX TO CUIC SYNC failed for these resources::: [String]

Explanation Notification to CUIC on resource change failed

Recommended Action EXECUTE Resource sync command from CLI

Error Message
MCVD-SCRIPT_MGR- 1 -MGR_PARTIAL_SERVICE : Script Manager in partial service.

Explanation The Script Manager is in partial service; synchronization of files with script repository is in progress

Recommended Action No actions needed

Error Message
MCVD-SCRIPT_MGR- 3 -STEP_COPY_FAILURE : Unable to copy a step. Script [String] Step id [Long] Step Class [String] Step Description [String] Exception [String]

Explanation The specified step could not be copied

Recommended Action Verify and update the configuration

Error Message
MCVD-SCRIPT_MGR- 3 -UNSUPPORTED_SCRIPT : Unsupported script type. Script [String] Type [String] Domain [String] Exception [String]

Explanation The specified script type is not supported

Recommended Action Verify and update the script

Error Message
MCVD-SCRIPT_MGR- 2 -INVALID_USER_DIR : Invalid user script directory configured. Directory [String] Exception [String]

Explanation The configured user script directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-SCRIPT_MGR- 3 -INVALID_FINAL_CFG_VAR : Variable defined as a final variable. Application [String] Script [String] Variable [String] Exception [String]

Explanation The script variable is defined as final which cannot be modified

Recommended Action Verify and update the configuration

Error Message
MCVD-SCRIPT_MGR- 4 -HIDDEN_STEP_FOUND : Script contains an hidden step. Script [String] Step id [Long] Step Class [String] Step Description [String]

Explanation The specified script contains the specified hidden step

Recommended Action Load the script in the Unified CCX Editor and save it back; this will removethe hidden step

Error Message
MCVD-SCRIPT_MGR- 3 -INVALID_SCRIPT : Invalid script. Script [String] Exception [String]

Explanation The script configured is invalid and cannot be loaded

Recommended Action Verify and update the script

Error Message
MCVD-SCRIPT_MGR- 4 -CFG_VAR_NOT_DEFINED : Variable not defined in script. Application [String] Script [String] Variable [String]

Explanation A configured variable is not defined in the script

Recommended Action Verify and update the configuration

Error Message
MCVD-SCRIPT_MGR- 3 -SCRIPT_NOT_DEFINED : Script not defined. Script [String] Exception [String]

Explanation The specified script is not configured in the repository

Recommended Action Verify and update the script

Error Message
MCVD-SCRIPT_MGR- 3 -NOT_A_CFG_VAR : Variable not defined as a configuration variable. Application [String] Script [String] Variable [String]

Explanation A configured variable is not defined as a configuration variable in the script

Recommended Action Verify and update the configuration

Error Message
MCVD-SCRIPT_MGR- 2 -NO_SCRIPT_CTX : No context defined in script. Application [String] Script [String]

Explanation The specified script doesn't have a context of variables defined

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-SCRIPT_MGR- 6 -MGR_INITIALIZING : Script Manager initializing.

Explanation The Script Manager is initializing

Recommended Action No actions needed

Error Message
MCVD-SCRIPT_MGR- 2 -MGR_OUT_OF_SERVICE : Script Manager in out of service.

Explanation The Script Manager is out of service; Scripts won't be accessible

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-SCRIPT_MGR- 5 -MGR_SHUTTING_DOWN : Script Manager shutting down.

Explanation The Script Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MCVD-SCRIPT_MGR- 3 -RMI_REBIND_FAILED : Unable to register remote interface. Exception [String]

Explanation A remote interface could not be bound to the RMI registry; remote access for dynamic update or other functions will not be available

Recommended Action Verify the RMI configuration and restart server

Error Message
MCVD-SCRIPT_MGR- 6 -MGR_IN_SERVICE : Script Manager in service.

Explanation The Script Manager is in service

Recommended Action No actions needed

Error Message
MCVD-SCRIPT_MGR- 3 -CUSTOMIZER_ERROR : Exception thrown while processing customizer of a step in Script. Application [String] Script [String]

Explanation Exception thrown while processing customizer of a step in Script

Recommended Action Verify and update the configuration

Error Message
MCVD-SCRIPT_MGR- 5 -MGR_SHUTDOWN : Script Manager in shutdown.

Explanation The Script Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MCVD-SCRIPT_MGR- 3 -UNABLE_LOAD_SCRIPT : Unable to load script. Script [String] Exception [String]

Explanation The script manager could not load the specified script

Recommended Action Verify and update the script

Error Message
MCVD-SCRIPT_MGR- 3 -INVALID_LICENSES : Invalid licenses. Script [String] Exception [String]

Explanation The script configured cannot be loaded because of missing licenses

Recommended Action Verify and update the licences

Error Message
MCVD-SCRIPT_MGR- 3 -INCOMPATIBLE_CFG_VAR_TYPES : Incompatible configuration variable types. Application [String] Script [String] Variable [String] Variable type defined [String] Variable type configured [String] Exception [String]

Explanation A configured variable type is incompatible with the variable defined script

Recommended Action Verify and update the configuration

Error Message
MCVD-SCRIPT_MGR- 3 -UNDEFINED_NAME_SCRIPT : Undefined user or system script. Script [String] Type [String] Domain [String] Exception [String]

Explanation A user or system script cannot be located

Recommended Action Verify and update the configuration

Error Message
MCVD-SCRIPT_MGR- 3 -CORRUPTED_SCRIPT : The script is corrupted. Script [String] Exception [String]

Explanation The specified script or the last script that the system attempted to load is corrupted and cannot be sucessfully loaded

Recommended Action Please Contact Cisco technical assistance center to recover the script

Error Message
MCVD-SCRIPT_MGR- 3 -WEBSERVICES_ERROR : Exception thrown while processing web services for Script. Exception [String]

Explanation Exception thrown while processing web services for Script

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-SCRIPT_MGR- 2 -INVALID_SYSTEM_DIR : Invalid system script directory configured. Directory [String] Exception [String]

Explanation The configured system script directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-SCRIPT_MGR- 3 -SCRIPT_FILE_SUPPORT_FAILURE : Script file support failure. Exception [String]

Explanation The Script Manager can not register file support for script files; scripts will not be accesible from the script repository

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-SOCKET_MGR- 1 -MGR_PARTIAL_SERVICE : Socket Manager in partial service.

Explanation The Socket Manager is in partial service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-SOCKET_MGR- 6 -MGR_IN_SERVICE : Socket Manager in service.

Explanation The Socket Manager is in service

Recommended Action No actions needed

Error Message
MCVD-SOCKET_MGR- 4 -MISSING_RESOURCE : Missing socket resources. Facility [String] Sub-Facility [String] Socket allocator id [String] Exception [String]

Explanation The socket manager is unable to locate internal socket resources

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-SOCKET_MGR- 5 -MGR_SHUTDOWN : Socket Manager in shutdown.

Explanation The Socket Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MCVD-SOCKET_MGR- 4 -REQUEST_TIMEOUT : Requesting a socket timed out. Facility [String] Sub-Facility [String] Socket allocator id [String] Mnemonic [String] Thread [String] Time [Long]

Explanation Request to get a socket timed out

Recommended Action No actions needed

Error Message
MCVD-SOCKET_MGR- 4 -REQUEST_FAILED : Requesting a socket failed. Facility [String] Sub-Facility [String] Socket allocator id [String] Mnemonic [String] Thread [String] Time [Long] Exception [String]

Explanation Request to get a socket failed

Recommended Action No actions needed

Error Message
MCVD-SOCKET_MGR- 4 -REQUEST_BLOCKED : Invoking blocked allocation handler. Facility [String] Sub-Facility [String] Socket allocator id [String] Mnemonic [String] Thread [String] Time [Long] Handler [String]

Explanation The specified blocked allocation handler is being invoked for the specified socket request as the allocator queue could not accept it

Recommended Action No actions needed

Error Message
MCVD-SOCKET_MGR- 6 -MGR_INITIALIZING : Socket Manager initializing.

Explanation The Socket Manager is initializing

Recommended Action No actions needed

Error Message
MCVD-SOCKET_MGR- 2 -MGR_OUT_OF_SERVICE : Socket Manager in out of service.

Explanation The Socket Manager is out of service; allocators won't be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-SOCKET_MGR- 5 -MGR_SHUTTING_DOWN : Socket Manager shutting down.

Explanation The Socket Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MCVD-USER_MGR- 4 -NAME_GRAMMAR_GENERATION_NOT_ALLOWED : Name Grammar Generation not allowed unless in MIVR or MADM.

Explanation Name Grammar Generation not allowed unless in MIVR or MADM

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-USER_MGR- 1 -MGR_PARTIAL_SERVICE : User Manager in partial service.

Explanation The User Manager is in partial service

Recommended Action Investigate as required

Error Message
MCVD-USER_MGR- 4 -DB_CORRUPTION_ILLEGAL_VALUE : Possible Call Manager database corruption due to an illegal value. Table name [String] Column name [String] Column value [String]

Explanation Possible Call Manager database corruption due to an illegal value

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-USER_MGR- 3 -NAME_GRAMMAR_SCHEDULE_UPDATE_FAILED : Name Grammar schedule update failed. Exception [String]

Explanation The User Manager failed to update automatic Name Grammar Generator schedule; Name To User may not function

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-USER_MGR- 3 -UNEXPECTED_EXCEPTION : Unexpected exception thrown. Exception [String]

Explanation Unexpected exception thrown

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-USER_MGR- 4 -FILE_IO_ERROR : Error occurred during file I/O. Exception [String]

Explanation Error occurred during file I/O

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-USER_MGR- 4 -DB_CORRUPTION_EMPTY_VALUE : Possible Call Manager database corruption due to empty required value. Table name [String] Column name [String] Row [Int]

Explanation Possible Call Manager database corruption due to empty required value

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-USER_MGR- 4 -NAME_GRAMMAR_UPDATE_STATUS_FAILED : Name Grammar Generation status update failed. Exception [String]

Explanation The User Manager failed to update Name Grammar Generation Status. The status information may be incorrect.

Recommended Action No actions needed

Error Message
MCVD-USER_MGR- 6 -MGR_INITIALIZING : User Manager initializing.

Explanation The User Manager is initializing

Recommended Action No actions needed

Error Message
MCVD-USER_MGR- 5 -MGR_SHUTTING_DOWN : User Manager shutting down.

Explanation The User Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MCVD-USER_MGR- 2 -MGR_OUT_OF_SERVICE : User Manager in out of service.

Explanation The User Manager is out of service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-USER_MGR- 3 -INIT_FAILED : User Manager failed to initialize. Exception [String]

Explanation An exception has occurred during the initialization of the User Manager

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-USER_MGR- 3 -NAME_GRAMMAR_UPDATE_CONFIG_FAILED : Name Grammar configuration update failed. Exception [String]

Explanation The User Manager failed to update Name Grammar Generation Configuration; Name To User may not function

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-USER_MGR- 1 -CANNOT_CREATE_SYSTEM_USER : Caller cannot create a System User. Exception [String]

Explanation An unauthorized class has attempted to create an instance of a System User.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-USER_MGR- 4 -AUDIO_FORMAT_ERROR : Wrong audio format in stream. Exception [String]

Explanation Wrong audio format in stream

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-USER_MGR- 3 -NAME_GRAMMAR_GENERATION_FAILED : Name Grammar generation failed. Exception [String]

Explanation The User Manager was unable to generate the Name Grammars; Name To User may not function

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MCVD-USER_MGR- 6 -MGR_IN_SERVICE : User Manager in service.

Explanation The User Manager is in service

Recommended Action No actions needed

Error Message
MCVD-USER_MGR- 4 -STREAM_IO_ERROR : Error occurred during stream I/O. Exception [String]

Explanation Error occurred during stream I/O

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-USER_MGR- 5 -MGR_SHUTDOWN : User Manager in shutdown.

Explanation The User Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MCVD-USER_MGR- 4 -DB_CORRUPTION_BAD_VALUE_FORMAT : Possible Call Manager database corruption due to bad value format. Table name [String] Column name [String] Column value [String] Exception [String]

Explanation Possible Call Manager database corruption due to bad value format

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-USER_MGR- 4 -DB_CORRUPTION_MISSING_COLUMN : Possible Call Manager database corruption due to missing column. Table name [String] Column name [String] Exception [String]

Explanation Possible Call Manager database corruption due to missing column

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-USER_MGR- 3 -CONFIG_LISTENER_INIT_FAILED : Unable to register config listener. Exception [String]

Explanation Unable to register config listener for UserGrammarConfig; Name To User may not function

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-USER_MGR- 3 -NO_SYSTEM_PAYLOAD : System payload type could not be determined.

Explanation System payload type could not be determined

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MCVD-USER_MGR- 5 -CLUSTER_ID_CHANGED : Cluster ID has changed.. Previous Cluster ID [String] Current Cluster ID [String]

Explanation Cluster ID has changed. This is a rare but normal condition. It can occur after a restore operation following a re-install. Users whose cluster specific data was modified after the re-install but before the restore will lose those modifications.

Recommended Action No actions needed

Error Message
MCVD-USER_MGR- 4 -DB_CORRUPTION_NON_UNIQUE_KEY : Possible Call Manager database corruption due to non unique key. Table name [String] Column name [String] Key value [String]

Explanation Possible Call Manager database corruption due to non unique key

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-BOOTSTRAP_MGR- 1 -MGR_PARTIAL_SERVICE : Bootstrap Manager in partial service.

Explanation The Bootstrap Manager is in partial service

Recommended Action Investigate as required

Error Message
MEDT-BOOTSTRAP_MGR- 3 -BOOTSTRAP_NODE_JOIN_ERROR : Failed to sync bootstrap repository during node join. A description for the nature of the exception [String] Exception [String]

Explanation Failed to sync bootstrap repository during node join

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-BOOTSTRAP_MGR- 3 -BOOTSTRAP_SYNC_ERROR : Synchronize bootstrap repository error. A description for the nature of the exception [String] Exception [String]

Explanation Failed to synchronize the bootstrap repository between nodes

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-BOOTSTRAP_MGR- 3 -BOOTSTRAP_REMOVE_LISTENER_ERROR : Failed to remove the BootstrapListener. A description for the nature of the exception [String] Exception [String]

Explanation Failed to remove the BootstrapListener

Recommended Action Restart server

Error Message
MEDT-BOOTSTRAP_MGR- 6 -MGR_IN_SERVICE : Bootstrap Manager in service.

Explanation The Bootstrap Manager is in service

Recommended Action No actions needed

Error Message
MEDT-BOOTSTRAP_MGR- 3 -BOOTSTRAP_ADD_LISTENER_ERROR : Failed to add the BootstrapListener. A description for the nature of the exception [String] Exception [String]

Explanation Failed to add the BootstrapListener

Recommended Action Restart server

Error Message
MEDT-BOOTSTRAP_MGR- 3 -BOOTSTRAP_INIT_ERROR : Bootstrap Manager initialization error. A description for the nature of the exception [String] Exception [String]

Explanation The Bootstrap Manager has failed on initialzation

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-BOOTSTRAP_MGR- 5 -MGR_SHUTDOWN : Bootstrap Manager in shutdown.

Explanation The Bootstrap Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MEDT-BOOTSTRAP_MGR- 3 -BOOTSTRAP_NODE_REMOVE_ERROR : Bootstrap failed to remove node from cluster profile. A description for the nature of the exception [String] Exception [String]

Explanation Bootstrap failed to remove node from cluster profile

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-BOOTSTRAP_MGR- 6 -MGR_INITIALIZING : Bootstrap Manager initializing.

Explanation The Bootstrap Manager is initializing

Recommended Action No actions needed

Error Message
MEDT-BOOTSTRAP_MGR- 2 -MGR_OUT_OF_SERVICE : Bootstrap Manager in out of service.

Explanation The Bootstrap Manager is out of service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-BOOTSTRAP_MGR- 5 -MGR_SHUTTING_DOWN : Bootstrap Manager shutting down.

Explanation The Bootstrap Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MEDT-BOOTSTRAP_MGR- 3 -BOOTSTRAP_NODE_ADD_ERROR : Bootstrap failed to add new node to cluster profile. A description for the nature of the exception [String] Exception [String]

Explanation Bootstrap failed to add new node to cluster profile

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CFG_MGR- 3 -REPOSITORY_ACCESSOR_INIT_ERROR : Failed to initialize the accessor. Name [String]

Explanation Error in initializing repository accessor

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 1 -MGR_PARTIAL_SERVICE : Config Manager in partial service. Reason [String]

Explanation The Config Manager is in partial service due to CDS not yet activated or failed to register RMI for notification

Recommended Action Please check whether CDS is activated in the clusteror CVD to regsiter RMI for notification

Error Message
MEDT-CFG_MGR- 3 -DB_ACCESS_ERROR : Database Access error. Action [String] Table [String] Exception [String]

Explanation Error while accessing Data Base

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 3 -BULK_UPDATE_ERROR : Error in Bulk update. action [String] Exception [String]

Explanation Error in bulk update

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 6 -STUB_HASCHANGED : ConfigStubImpl hasChanged(). Exception [String]

Explanation information

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 3 -SAVE_FAILED : saving failed . Exception [String]

Explanation ConfigObject saving failed

Recommended Action ConfigObject saving failed

Error Message
MEDT-CFG_MGR- 6 -CONFIG_SCHEMA_CHANGE : ConfigSchema change. Schema_Ver [String]

Explanation Change in ConfigSchema

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 3 -CLUSTER_INFO_PORT_SAVE_ERR : Error in updating Bootstrap ini file. value [String] Exception [String]

Explanation Error in updating Bootstrap ini file with RMI port

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 3 -CLUSTER_INFO_HOST_SAVE_ERR : Error in updating Bootstrap ini file. Exception [String]

Explanation Error in updating Bootstrap ini file with local host ip

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 3 -GET_ACCESSOR_ERR : Error in finding repository accessors. Name [String] Exception [String]

Explanation Error in finding repository accessors information

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 6 -SCHEMA_EXISTS : ConfigSchema Register failed. Exception [String]

Explanation information

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 6 -MGR_INITIALIZING : Config Manager initializing.

Explanation The Config Manager is initializing

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 5 -MGR_SHUTTING_DOWN : Config Manager shutting down.

Explanation The Config Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 2 -MGR_OUT_OF_SERVICE : Config Manager in out of service.

Explanation The Config Manager is out of service; configuration will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CFG_MGR- 6 -NO_BASERECORD : No base record.

Explanation No base record for this config object

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 3 -LOCAL_AND_REMOTE_PROPERTIES_HAVE_DIFFERENT_VERSIONS : Local and remote properties have different versions. Properties name [String] Remote properties version [String] Local properties version [String] Merge result [String]

Explanation The properties being merged are of different versions

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-CFG_MGR- 3 -CONFIG_SCHEMAS_LOAD_ERROR : Interrupted while loading configschemas. Name [String] Exception [String]

Explanation Error in loading config schemas

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 3 -READ_REAPOSIOTRY_ACCCESSORS : Error in reading repository accessors from applciation properties. Name [String] Exception [String]

Explanation Error in reading repository accessors information from applciation properties

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 6 -MGR_IN_SERVICE : Config Manager in service.

Explanation The Config Manager is in service

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 3 -CONFIG_MGR_GET_REMOTEPROP_ERROR : Config Manager get remote properties failed. Properties name [String] Exception [String]

Explanation Config Manager get remote properties failed

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-CFG_MGR- 3 -CONFIG_OBJECT_SAVE_FAIL : saving failed due to missing values for keys defined in configSchema. configObejct [String] Reason [String] Exception [String]

Explanation saving failed due to missing values for keys defined in configSchema

Recommended Action Check the values for keys defined in the configSchema

Error Message
MEDT-CFG_MGR- 5 -MGR_SHUTDOWN : Config Manager in shutdown.

Explanation The Config Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 3 -PARSE_ERROR : Error in converiting data. ToBeParsed [String] Table [String] Exception [String]

Explanation Error in parsing

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 3 -PROFILE_INFO_ACCESS_ERR : Error in accessing profile ini file. Exception [String]

Explanation Error in accessing profile ini file

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 2 -CFG_MGR_INSTANCE_NULL : Config Manager instance is null.

Explanation The Config Manager instance is null; configuration will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CFG_MGR- 3 -CLUSTER_DOWN_ERROR : Cluster Manager is not initialized. Description [String] Exception [String]

Explanation Cluster Manager is not initialized

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-CFG_MGR- 3 -DELETE_ERROR : Delete failed. Exception [String]

Explanation ConfigObjects deletion for this query failed

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 3 -INVALID_REPOSITORY_ACCESSOR : Repository accessor is invalid. Exception [String]

Explanation Repository accessor is invalid

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 3 -READ_ERROR : object read error. Exception [String]

Explanation Error in reading

Recommended Action Error in reading

Error Message
MEDT-CFG_MGR- 3 -CONFIG_OBJECT_CORRUPTED : Error while reading config. Probably it was corrupt. Config Class [String] Exception [String]

Explanation Error while reading the blob data of the config

Recommended Action Run the CLI command 'show uccx tech dbserver integrity' to check and recover from any corrupted config objects

Error Message
MEDT-CFG_MGR- 3 -CONFIG_MGR_GENERAL_ERROR : Config Manager has exception. Error message [String] Exception [String]

Explanation Config Manager has exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-CFG_MGR- 3 -CLUSTER_RMI_REBIND_FAILED : Unable to register remote interface in cluster space. Exception [String]

Explanation A remote interface could not be binded to the cluster space; Config data may not be accessible form Editor

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CFG_MGR- 6 -NO_DB_RECORD : No record in DB.

Explanation No record in DB

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 3 -NOTIFICATION_ERROR : Failed to notify other remote config managers. Action [String] Exception [String]

Explanation Error in notifying other remote config managers

Recommended Action No actions needed

Error Message
MEDT-CFG_MGR- 2 -CONFIG_MGR_OUT_OF_SERVICE : Config Manager in out of service. Exception [String]

Explanation The Config Manager is out of service; configuration will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CLUSTER_MGR- 3 -MANAGER_INITIALIZING_ERROR : Cluster Manager is not initialized. Exception [String]

Explanation Cluster Manager is not initialized

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CLUSTER_MGR- 4 -REMOTE_EXCEPTION_1 : Can not communicate with CVD. errCnt [Int] Cmd [String] Exception [String]

Explanation Cluster Manager can not communicate with CVD on the local node

Recommended Action No actions needed

Error Message
MEDT-CLUSTER_MGR- 3 -REMOTE_EXCEPTION_2 : Can not communicate with CVD. errCnt [Int] Exception [String]

Explanation Cluster Manager can not communicate with CVD on the local node

Recommended Action No actions needed

Error Message
MEDT-CLUSTER_MGR- 3 -LICENSE_OBSERVER_ERROR : Cluster Manager can not register license observer. Exception [String]

Explanation Cluster Manager can not register license observer

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CLUSTER_MGR- 2 -RESTART_REQUESTED : Cluster Manager requests to restart process. reason [String]

Explanation Cluster Manager detects some problem that prevents its functionality, and requests restart

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-CLUSTER_MGR- 3 -COMPONENT_PRIMARY_CHANGED_ERROR : Component change primary, but it is not supported. type [String] nodeId [Int]

Explanation Component change primary, but it is not supported

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-CLUSTER_MGR- 3 -COMPONENT_CLEAR_PRIMARY_NOT_SUPPORTED : Clear Primary operation is not supported for the Component. type [String] nodeId [Int]

Explanation Clear Primary operation is not supported for the Component

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-CLUSTER_MGR- 6 -MANAGER_INITIALIZING_COMPLETED : Cluster Manager initialization successfully completed.

Explanation Cluster Manager initialization successfully completed

Recommended Action No actions needed

Error Message
MEDT-CLUSTER_MGR- 3 -READ_ERROR_CLUSTER_NAME : Cannot read cluster name. Exception [String]

Explanation Cannot read cluster name from ccndir.ini

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CLUSTER_MGR- 3 -GET_PUBLISHER_TIMEOUT_ERROR : Cluster Manager can not get Timeout value from Windows Registry. Exception [String]

Explanation Cluster Manager can not get Timeout value from Windows Registry. Use default timeout: 2 hours

Recommended Action No actions needed

Error Message
MEDT-CLUSTER_MGR- 3 -MASTER_SERVICE_NOT_FOUND : Master service not found. UniqueId [Int] nodeId [Int] Cmd [String]

Explanation Master service not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CLUSTER_MGR- 3 -ILLEGAL_CLUSTER_NAME : Cluster name is illegal. name [String]

Explanation Cluster name is illegal

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CLUSTER_MGR- 3 -CONVERGENCE_NOT_FOUND_ERROR : Convergence not found. name [String]

Explanation Convergence not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CLUSTER_MGR- 3 -GET_NODE_UPDATE_ERRORR : Can not communicate with CVD. Exception [String]

Explanation Cluster Manager can not communicate with CVD on the local node

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-CLUSTER_MGR- 3 -NODE_NOT_FOUND_FOR_CMD : Cluster Manager dispatcher can not process cmd: unknown Node. Cmd [String]

Explanation Cluster Manager dispatcher can not process cmd: unknown Node

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CLUSTER_MGR- 4 -COMPONENT_ALREADY_PRIMARY : Component is already primary. type [String] nodeId [Int]

Explanation Component is already primary

Recommended Action No actions needed

Error Message
MEDT-CLUSTER_MGR- 4 -MASTER_UPDATE_ERROR : Cluster Manager can not update master. nodeId [Int] Cmd [String]

Explanation Cluster Manager can not update master, it try to re-sync all states with CVD on the local Node

Recommended Action No actions needed

Error Message
MEDT-CLUSTER_MGR- 3 -SET_VMOPTION_ERROR : Cluster Manager can not execute SetVMOption. Exception [String]

Explanation Cluster Manager can not execute SetVMOption

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CLUSTER_MGR- 3 -SERVICE_ID_NOT_FOUND_ERROR : Service not found. UniqueId [Int] nodeId [Int] Cmd [String]

Explanation Service not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CLUSTER_MGR- 3 -COMPONENT_CLEAR_PRIMARY_ERROR : Clear Primary operation is not applicable to non-primary Component. type [String] nodeId [Int]

Explanation Clear Primary operation is not applicable to non-primary Component

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-CLUSTER_MGR- 3 -NODE_UPDATE_ERROR : Cluster Manager can not update node from command. nodeId [Int] Cmd [String]

Explanation Cluster Manager can not update node from command

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CLUSTER_MGR- 3 -COMPONENT_ID_NOT_FOUND_ERROR : Component not found. UniqueId [Int] nodeId [Int] Cmd [String]

Explanation Component not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CLUSTER_MGR- 3 -REMOTE_NOTIFY_1 : Can not communicate with CVD. Context [String] Cmd [String] Exception [String]

Explanation Cluster Manager can not communicate with CVD on the local node

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-CLUSTER_MGR- 6 -COMPONENT_PRIMARY_REMOVED : Component is removed, but it is primary. type [String] nodeId [Int]

Explanation Component is removed, but it is primary

Recommended Action No actions needed

Error Message
MEDT-CLUSTER_MGR- 3 -CLUSTER_SNAPSHOT_ON_ERROR : Cluster snapshot when error. cluster [String]

Explanation Cluster snapshot when error

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-CLUSTER_MGR- 3 -READ_CLUSTER_ERROR : Cluster Manager can not read Cluster data from ClusterSnapshotCmdImpl. Exception [String]

Explanation Cluster Manager can not read Cluster data from ClusterSnapshotCmdImpl

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CLUSTER_MGR- 3 -COMPONENT_SET_PRIMARY_NOT_SUPPORTED : Set Primary operation is not supported for the Component. type [String] nodeId [Int]

Explanation Set Primary operation is not supported for the Component

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-CLUSTER_MGR- 3 -NODE_READ_ERROR : Cluster Manager can not read node from command. Cmd [String] Exception [String]

Explanation Cluster Manager can not read node from command

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CLUSTER_MGR- 0 -JMS_BROKER_SERVICE_START_ERROR : A KeepAlive exception has been thrown in Manager Manager. Exception [String]

Explanation Due to JMS service start failure a KeepAlive exception has been thrown in Cluster Manager

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-CLUSTER_MGR- 2 -MASTER_ELECTION_ERROR : Master Election Error - too many masters. Context [String] name [String] nodeId [Int] otherNodeId [Int] reason [String]

Explanation Master Election Error - too many masters. Cluster Manager restart process

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CLUSTER_MGR- 3 -MEMORY_DUMP_ERROR : Cluster Manager can not execute Memory Dump. Exception [String]

Explanation Cluster Manager can not execute Memory Dump

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CLUSTER_MGR- 3 -SEMAPHORE_NOT_FOUND_ERROR : Cluster Manager can not find semaphore. Cmd [String]

Explanation Cluster Manager can not find semaphore

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-CLUSTER_MGR- 4 -NODE_INVALID : Node Is invalid. nodeId [Int] reason [String]

Explanation Node Is invalid, it should be recovered from Installer

Recommended Action Reinstall server

Error Message
MEDT-CLUSTER_MGR- 3 -NODE_SYNCHRONIZE_STATE_ERROR : Cluster Manager can not synchronize state for node. nodeId [Int]

Explanation Cluster Manager can not synchronize state for node, and will be restarted.

Recommended Action No actions needed

Error Message
MEDT-CLUSTER_MGR- 3 -ACCESS_CONFIG_DATA_ERROR : Cluster Manager can not access configuration data. Exception [String]

Explanation Cluster Manager can not access configuration data

Recommended Action Verify that Configuration data is available. If problem persist contact Cisco technical assistance center

Error Message
MEDT-CLUSTER_MGR- 4 -DYNAMIC_LICENSE_NOT_DEFINED : Dynamic license is not defined.

Explanation Dynamic license is not defined

Recommended Action No actions needed

Error Message
MEDT-CLUSTER_MGR- 2 -THROWS_KEEP_ALIVE_EXCEPTION : Cluster Manager throws KeepAlive Exception. Exception [String]

Explanation Cluster Manager detects some problem that prevents its functionality, and will be restarted

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-CLUSTER_MGR- 3 -MANAGER_DISPATCH_ERROR : Can not process command. Cmd [String] Exception [String]

Explanation Cluster Manager can not process command from CVD

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-DESKTOP- 5 -SHUTDOWN : Cisco Customer Response Solutions Editor stopped.

Explanation Cisco Customer Response Solutions Editor stopped

Recommended Action No actions needed

Error Message
MEDT-DESKTOP- 6 -IN_SERVICE : Cisco Customer Response Solutions Editor Desktop Manager started.

Explanation Cisco Customer Response Solutions Editor Desktop Manager started

Recommended Action No actions needed

Error Message
MEDT-DESKTOP- 3 -ENGINEHOSTNAME_ERROR : EngineHostName could not be found!. Exception [String]

Explanation EngineHostName could not be found!

Recommended Action Verify the RMI configuration and restart server

Error Message
MEDT-DESKTOP- 3 -OPEN_FILE_ERROR : File could not be found!. Exception [String]

Explanation File could not be found!

Recommended Action No actions needed

Error Message
MEDT-DOC_MGR- 1 -UNAUTHORISED_ACCESS : Unauthorised access. Name [String] Exception [String]

Explanation The Document Manager found that requested resource is not a legitimate one

Recommended Action Investigate as required

Error Message
MEDT-DOC_MGR- 1 -MGR_PARTIAL_SERVICE : Document Manager in partial service.

Explanation The Document Manager is in partial service; synchronization of files with document repository is in progress

Recommended Action No actions needed

Error Message
MEDT-DOC_MGR- 3 -UNABLE_LOAD_USER_DOC : Unable to load the user document file. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to load the specified user document file

Recommended Action Verify and update the configuration

Error Message
MEDT-DOC_MGR- 6 -MGR_IN_SERVICE : Document Manager in service.

Explanation The Document Manager is in service

Recommended Action No actions needed

Error Message
MEDT-DOC_MGR- 2 -INVALID_USER_DIR : Invalid user document directory configured. Directory [String] Exception [String]

Explanation The configured user document directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-DOC_MGR- 2 -WEBAPP_INIT_FAILURE : Unable to initialize the specified web application. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to initialize the specified web applicaton; it will not be available to HTTP-triggered applications

Recommended Action Verify and update the configuration and restart server

Error Message
MEDT-DOC_MGR- 6 -NO_WEBAPPS_APPS : Webapps directory is empty.

Explanation No apps in the webapps directory of the repository to process

Recommended Action No actions needed

Error Message
MEDT-DOC_MGR- 6 -NO_WEBAPPS : Webapps directory not found.

Explanation No webapps directory in the repository to process

Recommended Action No actions needed

Error Message
MEDT-DOC_MGR- 3 -UNDEFINED_USER_DOC : Undefined user document. Name [String] Language [String] Exception [String]

Explanation A user document cannot be located

Recommended Action Verify and update the configuration

Error Message
MEDT-DOC_MGR- 5 -MGR_SHUTDOWN : Document Manager in shutdown.

Explanation The Document Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MEDT-DOC_MGR- 1 -WEBAPPS_MONITOR_FAILURE : Webapps directory monitoring failure. Exception [String]

Explanation The Document Manager can no longer monitor dynamic updates to the webapps directory of the repository; updates to war files will require restarting the local Unified CCX Engine Service

Recommended Action Investigate as required

Error Message
MEDT-DOC_MGR- 3 -DOC_FILE_SUPPORT_FAILURE : Document file support failure. Exception [String]

Explanation The Document Manager can not register file support for user document files; user documents will not be synchronized on local server

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-DOC_MGR- 3 -UNDEFINED_SYSTEM_DOC : Undefined system document. Name [String] Language [String] Exception [String]

Explanation A system document cannot be located

Recommended Action Verify and update the configuration

Error Message
MEDT-DOC_MGR- 3 -UNABLE_LOAD_SYSTEM_DOC : Unable to load the system document file. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to load the specified system document file

Recommended Action Verify and update the configuration

Error Message
MEDT-DOC_MGR- 2 -WAR_EXPAND_FAILURE : Unable to expand the specified war file. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to expand the specified war file; the corresponding web application will not be available to HTTP-triggered applications

Recommended Action Verify and update the configuration and restart server

Error Message
MEDT-DOC_MGR- 3 -WEBAPP_REMOVE_FAILURE : Unable to remove the specified web application. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to remove the specified web applicaton

Recommended Action Verify and update the configuration and restart server

Error Message
MEDT-DOC_MGR- 6 -MGR_INITIALIZING : Document Manager initializing.

Explanation The Document Manager is initializing

Recommended Action No actions needed

Error Message
MEDT-DOC_MGR- 2 -MGR_OUT_OF_SERVICE : Document Manager in out of service.

Explanation The Document Manager is out of service; documents won't be accessible

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-DOC_MGR- 5 -MGR_SHUTTING_DOWN : Document Manager shutting down.

Explanation The Document Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MEDT-DOC_MGR- 3 -WEBSERVICES_ERROR : Exception thrown while processing web services for Document. Exception [String]

Explanation The Document Manager is unable to initialize the web services; external access to the document repository will not be possible andsupport for forwarding HTTP requests will also not be supported

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-DOC_MGR- 2 -INVALID_SYSTEM_DIR : Invalid system document directory configured. Directory [String] Exception [String]

Explanation The configured system document directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-EDT- 3 -INSTANCE_ALREADY_EXIST : Another instance of editor is already running.

Explanation Cannot create another instance of editor as one already exists

Recommended Action Investigate as required

Error Message
MEDT-EDT- 5 -SHUTDOWN : Cisco Customer Response Solutions Editor stopped.

Explanation Cisco Customer Response Solutions Editor stopped

Recommended Action No actions needed

Error Message
MEDT-EDT- 6 -IN_SERVICE : Cisco Customer Response Solutions Editor started.

Explanation Cisco Customer Response Solutions Editor started

Recommended Action No actions needed

Error Message
MEDT-EDT- 6 -INITIALIZING : Cisco Customer Response Solutions Editor starting.

Explanation Cisco Customer Response Solutions Editor starting

Recommended Action No actions needed

Error Message
MEDT-EDT- 4 -ERROR_IN_CUSTOMCONFIG : An error occurred while reading custom configuration file. Config Filename [String] Exception [String]

Explanation An error occurred while reading custom configuration file

Recommended Action Investigate as required

Error Message
MEDT-EDT- 3 -EDT_EXCPT : An exception occurred while running the editor. Exception [String]

Explanation An exception occurred while running the editor

Recommended Action Investigate as required

Error Message
MEDT-EDT- 4 -STEP_CREATION_ERROR : A step could not be created for the following reason. Step Class [String] Exception [String]

Explanation A step could not be created for the following reason

Recommended Action Investigate as required

Error Message
MEDT-EXECUTOR_MGR- 1 -MGR_PARTIAL_SERVICE : Executor Manager in partial service.

Explanation The Executor Manager is in partial service; thread priorities will not be properly set

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-EXECUTOR_MGR- 4 -INVALID_THREAD_PRIORITY_CHANGE : Invalid thread priority change. Facility [String] Sub-Facility [String] Executor id [String] Thread [String] Thread priority [Int] Original thread priority [Int]

Explanation The specified thread had an unsupported priority changed; user's code should not attempt to manually change the priority of threads for whatever reasons

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-EXECUTOR_MGR- 6 -MGR_INITIALIZING : Executor Manager initializing.

Explanation The Executor Manager is initializing

Recommended Action No actions needed

Error Message
MEDT-EXECUTOR_MGR- 5 -MGR_SHUTTING_DOWN : Executor Manager shutting down.

Explanation The Executor Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MEDT-EXECUTOR_MGR- 2 -MGR_OUT_OF_SERVICE : Executor Manager in out of service.

Explanation The Executor Manager is out of service; executors won't be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-EXECUTOR_MGR- 4 -CMD_BLOCKED : Invoking blocked execution handler. Facility [String] Sub-Facility [String] Executor id [String] Mnemonic [String] Thread [String] Thread priority [Int] Time [Long] Handler [String]

Explanation The specified blocked execution handler is being invoked for the specified command as the executor queue could not accept it

Recommended Action No actions needed

Error Message
MEDT-EXECUTOR_MGR- 6 -MGR_IN_SERVICE : Executor Manager in service.

Explanation The Executor Manager is in service

Recommended Action No actions needed

Error Message
MEDT-EXECUTOR_MGR- 4 -MISSING_RESOURCE : Missing thread priority resource. Facility [String] Sub-Facility [String] Executor id [String] Exception [String]

Explanation The executor manager is unable to locate internal thread priority resources

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-EXECUTOR_MGR- 4 -CMD_EXCEPTION : Un-handled command exception. Facility [String] Sub-Facility [String] Executor id [String] Mnemonic [String] Thread [String] Thread priority [Int] Time [Long] Exception [String]

Explanation The specified command did not handled the specified exception

Recommended Action No actions needed

Error Message
MEDT-EXECUTOR_MGR- 4 -INVALID_THREAD_NAME_CHANGE : Invalid thread name change. Facility [String] Sub-Facility [String] Executor id [String] Thread [String] Original Thread [String]

Explanation The specified thread had an unsupported name changed; user's code should not attempt to manually change the name of threads for whatever reasons

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-EXECUTOR_MGR- 4 -ATTEMPT_FAILED : Attempt failed. Facility [String] Sub-Facility [String] Executor id [String] Mnemonic [String] Time [Long] Exception [String]

Explanation Attempt to execute the specified command failed

Recommended Action No actions needed

Error Message
MEDT-EXECUTOR_MGR- 5 -MGR_SHUTDOWN : Executor Manager in shutdown.

Explanation The Executor Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MEDT-EXECUTOR_MGR- 4 -EXECUTE_FAILED : Execute failed. Facility [String] Sub-Facility [String] Executor id [String] Mnemonic [String] Time [Long] Exception [String]

Explanation Request to execute the specified command failed

Recommended Action No actions needed

Error Message
MEDT-EXPR_MGR- 1 -MGR_PARTIAL_SERVICE : Expression Manager in partial service.

Explanation The Expression Manager is in partial service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-EXPR_MGR- 6 -MGR_IN_SERVICE : Expression Manager in service.

Explanation The Expression Manager is in service

Recommended Action No actions needed

Error Message
MEDT-EXPR_MGR- 3 -EXPR_NOT_LICENSED : Expression not licensed. Non terminal token id [String] Expression type [String] Token [String] Line [Int] Column [Int] Exception [String]

Explanation The specified expression is not licensed

Recommended Action Verify and update the script

Error Message
MEDT-EXPR_MGR- 6 -MGR_INITIALIZING : Expression Manager initializing.

Explanation The Expression Manager is initializing

Recommended Action No actions needed

Error Message
MEDT-EXPR_MGR- 5 -MGR_SHUTTING_DOWN : Expression Manager shutting down.

Explanation The Expression Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MEDT-EXPR_MGR- 2 -MGR_OUT_OF_SERVICE : Expression Manager in out of service.

Explanation The Expression Manager is out of service; expressions won't be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-EXPR_MGR- 5 -MGR_SHUTDOWN : Expression Manager in shutdown.

Explanation The Expression Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 3 -DATA_SOURCE_CANNOT_BE_INITIALIZED : Repository Datastore data source cannot be initialized. Exception [String]

Explanation The file manager could not get the datasource initialized for Repository Datastore.

Recommended Action If problem persists.Please contact Cisco Technical Assistance Center(TAC)

Error Message
MEDT-FILE_MGR- 3 -STATE_CHECKER_THREAD_CREATION_FAILED : Unable to start the File Manager's state monitor thread. Exception [String]

Explanation Unable to start the File Manager state monitor thread;FileManager functionality not available.

Recommended Action If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MEDT-FILE_MGR- 1 -MGR_PARTIAL_SERVICE : File Manager in partial service.

Explanation The File Manager is in partial service; file synchronization will notbe available

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-FILE_MGR- 3 -UNABLE_UPLOAD_FILE : Unable to upload the specified file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The file manager could not upload the specified file

Recommended Action Investigate as required

Error Message
MEDT-FILE_MGR- 6 -DELETE_FILE_FOLDER_REQ_BY_USER : A file or folder delete was initiated by user. Class [String] Domain [String] Directory [String] Name [String] User Id [String]

Explanation The file manager is requested to delete folder or file by user

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 3 -REFRESH_FAILED : File refresh operation failed. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation Unable to download and create the specified file

Recommended Action Investigate as required

Error Message
MEDT-FILE_MGR- 3 -RDS_SQL_EXCEPTION_INFO : SQL Exception. Exception details [String]

Explanation SQL Exception occurred in File Manager

Recommended Action Investigate as required

Error Message
MEDT-FILE_MGR- 4 -CLASSPATH_SYNC_FAILED : Custom classpath files synchronization failed. Exception [String]

Explanation The remote file manager was unable to synchronize the custom classpath files and <default><webapps> folder from the cluster's document repository

Recommended Action Investigate as required

Error Message
MEDT-FILE_MGR- 2 -CUSTOM_FILES_CLASSPATH_WEB_APPS_SYNC_FAILED : Unable to synchronize custom files/jars from Repository Datastore. Class [String] Exception [String]

Explanation Unable to do synchronization of <default><classpath> and<default><webapps> folders under <Documents><user>

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-FILE_MGR- 6 -SYNC_FOUND_LOCAL_FILE_NOT_IN_REPOSITORY : The local file found during synchronization is not present in Repository Datastore. Class [String] Extra local file [String]

Explanation The extra local file found during synchronization is being deleted.

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 5 -CUSTOM_FILES_CLASSPATH_WEB_APPS_SYNC_SUCCEEDED : Synchronization of custom files/jars from Repository Datastore done.

Explanation Synchronization of <default><classpath> and<default><webapps> folders under <Documents><user> completed.

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 6 -MGR_INITIALIZING : File Manager initializing.

Explanation The File Manager is initializing

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 2 -MGR_OUT_OF_SERVICE : File Manager in out of service.

Explanation The File Manager is out of service; files won't be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-FILE_MGR- 3 -UNABLE_DOWNLOAD_FILE : Unable to download the specified file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The file manager could not download the specified file

Recommended Action Investigate as required

Error Message
MEDT-FILE_MGR- 4 -SYNC_FAILED_TO_CREATE_FILE : Synchronization failed to create file. Class [String] Reason [String] Exception [String]

Explanation Creation of files failed during synchronization.

Recommended Action If problem persists contact.Please Cisco Technical Assistance Center(TAC).If files are missing you may have to restart the CVD Service.

Error Message
MEDT-FILE_MGR- 3 -SYNC_THREAD_CREATION_FAILED : Unable to start the File Manager's local disk synchronization thread for a file type.. Class [String] Exception [String]

Explanation Unable to start the File Manager sychronization thread;synchronization will not be available for the file type

Recommended Action If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MEDT-FILE_MGR- 6 -CLASSPATH_SYNC_START : Custom classpath and <default><webapps> files are being synchronized.

Explanation The remote file manager is synchronizing the custom classpath files and webapps folders files from the cluster's document repository

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 4 -ORIGINAL_FILE_NOT_FOUND : Original file not found while copying with new version. Original file: [String]

Explanation The file manager was unable to copy a new version file since the original file was not found.

Recommended Action Investigate as required

Error Message
MEDT-FILE_MGR- 3 -UNABLE_GET_REPOSITORY_STATISTICS : Unable to get the repository size information. Space information requested: [String] Exception [String]

Explanation The File Manager could not get the repository size information

Recommended Action Investigate as required

Error Message
MEDT-FILE_MGR- 6 -REMOTE_STANDALONE_MODE : Remote File Manager initialized in stand-alone mode.

Explanation The remote file manager is being initialized in stand-alone mode; it will attempt to synchronized custom classpaths with the cluster

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 6 -MGR_IN_SERVICE : File Manager in service.

Explanation The File Manager is in service

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 3 -UNABLE_RENAME_FILE : Unable to rename the specified file. Class [String] Domain [String] Directory [String] Name [String] Destination Domain [String] Destination Directory [String] Destination Name [String] Exception [String]

Explanation The file manager could not rename the specified file

Recommended Action Investigate as required

Error Message
MEDT-FILE_MGR- 3 -CLEANUP_THREAD_CREATION_FAILED : Unable to start the File Manager's cleanup thread. Exception [String]

Explanation Unable to start the cleanup background thread; will not be able to perform the disk cleanup operations

Recommended Action If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MEDT-FILE_MGR- 4 -GET_RDS_DB_CONNECTION_FAILED : Unable to get connection to the Repository Datastore. Failure Reason [String]

Explanation Unable to get connection to Repository Datastore access; will not be able to perform prompts,grammars, documents related operations

Recommended Action Check Repository Datastore is activated.If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MEDT-FILE_MGR- 6 -CLASSPATH_SYNC_DONE : Custom classpath files synchronized.

Explanation The remote file manager successfully synchronized the custom classpath files and webapps folder files from the cluster's document repository

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 3 -UNABLE_GET_FILE_MODIFIED_TIME : Unable to get the last modified time of the file or directory. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not get the file or directory's last modified time

Recommended Action Verify the path of the file or directory

Error Message
MEDT-FILE_MGR- 4 -EXCEPTION_IN_TEMP_FILES_HANDLING_METHOD : Method generated exception. Exception [String]

Explanation File Manager temporary files-cleanup handling, generated exception.

Recommended Action If problem persists please contact Cisco Technical Assistance Center(TAC).

Error Message
MEDT-FILE_MGR- 3 -UNABLE_GET_LAST_MODIFIED_USER : Unable to get the last modified user of the file or folder . Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not get the file or folder

Recommended Action Verify the file or folder exists in repository

Error Message
MEDT-FILE_MGR- 4 -LAST_SYNC_TIME_CHECK_FAILED : Error while checking the replication LastSynchedTime. Exception [String]

Explanation Could not get the replication sync time while updating repository statistics

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 6 -NO_FOLDER_FILE_TO_DELETE_BY_CLEANUP_TASK_RUN : Current run of daily cleanup found no files,folders to delete. Exception [String]

Explanation The File Manager daily cleanup task, to cleanup deleted (folder,files) on local disk,found not files,folders to delete .

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 3 -UNABLE_DELETE_FILE : Unable to delete the specified file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The file manager could not delete the specified file

Recommended Action Investigate as required

Error Message
MEDT-FILE_MGR- 6 -UPLOAD_ARCHIVE_FILE_SUCCESS : Success progress of upload archive file. Class [String] status [String]

Explanation Archive file each file type upload status

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 4 -COPY_FILES_TO_ORIG_LOCATION : Copying of files to original location errored. Exception [String]

Explanation The task to copy files from <temp> directory to original location failed

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 3 -CLUSTER_RMI_REBIND_FAILED : Unable to register remote interface in cluster space. Exception [String]

Explanation A remote interface could not be binded to the cluster space; automatic synchronization of files will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-FILE_MGR- 3 -UNABLE_MAKE_DIR : Unable to make directory. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not create the directory

Recommended Action Verify that path of the directory

Error Message
MEDT-FILE_MGR- 3 -SYNC_REMOTE_NOTIFICATION_FAILED : Notifying remote File Manager service objects failed. Class [String] Node Id [String] Exception [String]

Explanation Synchronization notifications using remote File Manager Service failed for one or more nodes.

Recommended Action If problem persists contact.Please Cisco Technical Assistance Center(TAC).

Error Message
MEDT-FILE_MGR- 6 -SYNC_OPERATION_STARTED : Synchronization started.. Class [String] Synchronization status [String]

Explanation Repository Datastore to local disk synchronization started.

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 3 -UNABLE_UPLOAD_ARCHIVE_FILE : Unable to upload the archive file. Archive File Name [String] Reason [String] Archive Length [String] Exception [String]

Explanation The File Manager could not upload the specified file

Recommended Action Investigate as required

Error Message
MEDT-FILE_MGR- 4 -DELETED_FOLDER_FILE_CLEANUP_TASK_RUN_FAILED : Current run of daily cleanup task failed. Exception [String]

Explanation The File Manager daily cleanup task, to clean deleted (folder,files) on local disk errored.The files,folders can get deleted in next daily run.

Recommended Action Investigate as required

Error Message
MEDT-FILE_MGR- 4 -SYNC_INVALID_STATE : Synchronization detected invalid state. Class [String] Reason [String]

Explanation Invalid state detected during synchronization

Recommended Action Investigate as required

Error Message
MEDT-FILE_MGR- 3 -UNABLE_LIST_FILES : Unable to list the files denoted by the specified file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The file manager could not list the files denoted by the specified file

Recommended Action Investigate as required

Error Message
MEDT-FILE_MGR- 6 -RECOVERY_COMPLETED_EVENT : File Manager recieved recovery completed event, full synchronization will be performed..

Explanation File Manager detected recovery completed event.Repository changes will be synched to local disk now.

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 1 -CLUSTER_COMM_FAILED : Cluster communication failure. Exception [String]

Explanation Unable to communicate with the cluster; will not be able to access the cluster repository files

Recommended Action Investigate as required

Error Message
MEDT-FILE_MGR- 3 -DUPLICATE_FILE_SUPPORT : Duplicate file support detected. Class [String] Exception [String]

Explanation An attempt is being made at registering a duplicate file support

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-FILE_MGR- 3 -UNABLE_GET_FILE_LENGTH : Unable to get the length of the file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not get the file length

Recommended Action Verify the path of the file

Error Message
MEDT-FILE_MGR- 3 -UNABLE_TO_CREATE_TEMP_DIR : Unable to make temp directory. Class [String] Name [String] Exception [String]

Explanation The File Manager could not create temp directory

Recommended Action Verify that Unified CCX prompts, documents, grammars and scripts folder are proper

Error Message
MEDT-FILE_MGR- 4 -ERROR_WHILE_SYNCH : An error occurred while synchronizing. Class [String] Method [String] Exception [String]

Explanation An error occurred while File Manager is synchronizing disk from RDS

Recommended Action If problem persists please contact Cisco Technical Assistance Center(TAC).

Error Message
MEDT-FILE_MGR- 3 -INVALID_FILE : Invalid file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The specified file is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-FILE_MGR- 3 -FAIL_TO_CREATE_RDS_SERVICE_CONVERGENCE : Repository Datastore Service convergence object cannot be created.

Explanation The file manager cannot create Repository Datastore convergence object.Repository Datastore failover functionality will not be available.

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-FILE_MGR- 4 -SYNC_LOCAL_FILE_LATEST_THAN_IN_REPOSITORY : The local file is found to be newer than one in the Repository Datastore. Class [String] Local file [String] Repository Datastore file [String]

Explanation Local file is being replaced by the one in Repository Datastore

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 4 -SYNC_NOT_COMPLETE : Synchronization did not complete.. Class [String] Exception [String]

Explanation This indicates some of the synchronization operation failed.

Recommended Action If problem persists contact.Please Cisco Technical Assistance Center(TAC).

Error Message
MEDT-FILE_MGR- 6 -SYNC_OPERATION_COMPLETED : Synchronization completed.. Class [String] Synchronization status [String]

Explanation Repository Datastore to local disk synchronization completed.

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 6 -DELETED_TEMP_FILE_FOLDER : Temp file or folder was deleted. Temporary file or folder: [String]

Explanation The file manager deleted temporary file or folder

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 3 -UNABLE_SET_LAST_MODIFIED : Unable to set last modified time of the file or directory. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not set the last modified time of the file or directory.

Recommended Action Verify the path of the file or directory

Error Message
MEDT-FILE_MGR- 5 -MGR_SHUTTING_DOWN : File Manager shutting down.

Explanation The File Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 3 -UNABLE_FILE_EXISTS_CHECK : Check for file or directory existence failed. Class [String] Domain [String] Directory [String] Name [String] Error reason [String]

Explanation The File Manager could not find whether file or directory exists

Recommended Action Verify the path of the file or directory

Error Message
MEDT-FILE_MGR- 6 -RECOVERY_DETECTED : File Manager detected an archive request in the system;synchronization from Repository to local disk not performed..

Explanation File Manager detected an archive request in the system

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 3 -INVALID_FILE_CLASS : Invalid file class. Class [String] Exception [String]

Explanation The specified file class is not supported by the file manager

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-FILE_MGR- 4 -RMI_REBIND_FAILED : Unable to register remote interface. Exception [String]

Explanation A remote interface could not be binded to the RMI registry; remote access to files from the editor will not be available

Recommended Action Verify the RMI configuration and restart server

Error Message
MEDT-FILE_MGR- 3 -FILE_MANAGER_REGISTRATION_WITH_CLUSTER_FAILED : Unable to register the File Manager's Service remote object with the cluster.. Exception [String]

Explanation Unable to register the File Manager's remote service object.

Recommended Action If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MEDT-FILE_MGR- 4 -SYNC_FAILED_TO_MKDIR : Synchronization failed to make directory. Class [String] Reason [String]

Explanation Creation of directories failed during synchronization.

Recommended Action If files are missing you may have to restart the CVD Service.If problem persists contact.Please Cisco Technical Assistance Center(TAC)

Error Message
MEDT-FILE_MGR- 4 -RDS_DETERMINATION_FAILED : Repository Datastore cannot be initalized.. Exception [String]

Explanation The file manager could not initialize datastore to store prompts, grammars and documents within the cluster.This may happen if Repository Datastore component is not available in the cluster or configured properly.

Recommended Action Investigate as required

Error Message
MEDT-FILE_MGR- 6 -REMOTE_COLLOCATED_MODE : Remote File Manager initialized in collocated mode.

Explanation The remote file manager is being initialized in collocated mode; it will not attempt to synchronized custom classpaths with the cluster

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 5 -MGR_SHUTDOWN : File Manager in shutdown.

Explanation The File Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 4 -NEW_VERSION_FILE_NOT_FOUND : Newer version of file not found in <temp> directory. New version file(<temp>): [String]

Explanation The file manager was unable to find newer verion of file in <temp> while updating to original location

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 6 -SYNC_FOUND_LOCAL_FOLDER_NOT_IN_REPOSITORY : The local folder found during synchronization is not present in Repository Datastore. Class [String] Extra local folder [String]

Explanation The extra local folder found during synchronization is being deleted.

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 3 -SYNC_CANNOT_INITIALIZE_LOCAL_STORE : Unable to initialize local disk info when performing Repository Sync. Class [String] Exception [String]

Explanation Local store intialization failed during synchronization

Recommended Action If problem persists contactCisco Technical Assistance Center(TAC)

Error Message
MEDT-FILE_MGR- 3 -SYNC_CANNOT_INITIALIZE_DB_STORE : Unable to initialize Repository Datastore access when performing Synchronization. Class [String] Exception [String]

Explanation Accessing Repository Datastore failed.

Recommended Action Check if the RDS component is activated.If problem persists contact.Please Cisco Technical Assistance Center(TAC)

Error Message
MEDT-FILE_MGR- 6 -SYNCHRONIZATION_UPDATE : FileManager RDS to local disk synchronization. Class [String] Information [String]

Explanation progress message related to FileManager synchronization of local disk from RDS

Recommended Action No actions needed

Error Message
MEDT-FILE_MGR- 3 -REP_DATASTORE_INIT_FAILED : Unable to initialize the Repository Datastore access. Exception [String]

Explanation Unable to initialize Repository Datastore access; will not be able to perform prompts,grammars, documents related operations

Recommended Action Check Repository Datastore is enabled.If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MEDT-FILE_MGR- 6 -FILE_MARK_FOR_DELETION : Deleted file. Class [String] Domain [String] Directory [String] Name [String]

Explanation File Manager found the file marked for deletion

Recommended Action Operation cannot be preformed

Error Message
MEDT-FILE_MGR- 4 -MASTER_RDS_NOT_FOUND : Repository Datastore not found.. Reason [String]

Explanation The file manager could not find Repository Datastore to store prompts, grammars and documents within the cluster.This may happen if Repository Datastore component is not activated or Master RDS is not determined.

Recommended Action Investigate as required

Error Message
MEDT-GENERIC- 5 -ProcessStart : Process Starting. Process Identifier [UInt] Module Name [String]

Explanation This notification signifies that a process has just started. This notification is intended to work in conjunction with the ProcessStop notification to notify the start and stop status of a particular process.

Recommended Action No actions needed

Error Message
MEDT-GENERIC- 5 -ModuleStart : Module has successfully started. Module Name [String]

Explanation This notification signifies a module has started successfully and transitioned into the in-service state

Recommended Action No actions needed

Error Message
MEDT-GENERIC- 3 -ModuleRunTimeFailure : Run-time Failure. Module Name [String] Module Run-time Failure Cause [Enum] Module Failure Name [String] Module Failure Message [String]

Explanation This notification signifies a run-time failure has occured

Recommended Action Investigate as required

Module Run-time Failure Cause-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Other or Unspecified Failure
2 Read Access Failure
3 Write Access Failure
4 Create Failure
5 Delete Failure
6 Update Failure
7 Init Failure
8 Load Failure
9 Out of Resource
10 Call Process Failure
11 Registration Failure
12 De-registration Failure
13 Connection Failure
14 Disconnection Failure
15 Unknown Target
16 Un-reacheable Target
Error Message
MEDT-GENERIC- 1 -ModuleStop : Module has stopped. Module Name [String] Module Failure Cause [Enum]

Explanation This notification signifies a module has stopped

Recommended Action Investigate as required

Module Failure Cause-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Other or Unspecified Failure
2 Graceful Shutdown
3 Heartbeat Failure
4 Initialization Failure
5 Out of Resource
6 Partial Failure
Error Message
MEDT-GENERIC- 1 -ProcessStop : Process Stopped. Process Identifier [UInt] Module Name [String]

Explanation This notification signifies that a process has just stopped. This notification is intended to work in conjunction with the ProcessStart notification to notify the start and stop status of a particular process.

Recommended Action Investigate as required

Error Message
MEDT-GRAMMAR_MGR- 3 -GRAMMAR_LEXICAL_ERROR : Template grammar lexical error. Name [String] Template [String] Language [String] Exception [String]

Explanation The specified lexical error occured while parsing a template grammar

Recommended Action Verify and update the application

Error Message
MEDT-GRAMMAR_MGR- 1 -MGR_PARTIAL_SERVICE : Grammar Manager in partial service.

Explanation The Grammar Manager is in partial service; synchronization of files with grammar repository is in progress

Recommended Action No actions needed

Error Message
MEDT-GRAMMAR_MGR- 6 -MGR_IN_SERVICE : Grammar Manager in service.

Explanation The Grammar Manager is in service

Recommended Action No actions needed

Error Message
MEDT-GRAMMAR_MGR- 2 -INVALID_USER_DIR : Invalid user grammar directory configured. Directory [String] Exception [String]

Explanation The configured user grammar directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-GRAMMAR_MGR- 3 -GRAMMAR_PARSING_ERROR : Template grammar parsing error. Name [String] Template [String] Language [String] Exception [String]

Explanation The specified error occured while parsing a template grammar

Recommended Action Verify and update the application

Error Message
MEDT-GRAMMAR_MGR- 3 -UNDEFINED_NAME_GRAMMAR : Undefined user or system grammar. Name [String] Type [String] Language [String] Exception [String]

Explanation A user or system grammar cannot be located

Recommended Action Verify and update the configuration

Error Message
MEDT-GRAMMAR_MGR- 3 -GRAMMAR_FILE_SUPPORT_FAILURE : Grammar file support failure. Exception [String]

Explanation The Grammar Manager can not register file support for user grammar files; user grammars will not be synchronized on local server

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-GRAMMAR_MGR- 5 -MGR_SHUTDOWN : Grammar Manager in shutdown.

Explanation The Grammar Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MEDT-GRAMMAR_MGR- 3 -UNABLE_PARSE_GRAMMAR : Unable to parse the grammar. Grammar [String] Type [String] Exception [String]

Explanation The Grammar Manager is unable to parse the specified grammar

Recommended Action Verify and update the configuration

Error Message
MEDT-GRAMMAR_MGR- 3 -UNSUPPORTED_GRAMMAR : Unsupported grammar type. Name [String] Type [String] Language [String] Exception [String]

Explanation The specified grammar type is not supported

Recommended Action Verify and update the application

Error Message
MEDT-GRAMMAR_MGR- 6 -MGR_INITIALIZING : Grammar Manager initializing.

Explanation The Grammar Manager is initializing

Recommended Action No actions needed

Error Message
MEDT-GRAMMAR_MGR- 5 -MGR_SHUTTING_DOWN : Grammar Manager shutting down.

Explanation The Grammar Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MEDT-GRAMMAR_MGR- 2 -MGR_OUT_OF_SERVICE : Grammar Manager in out of service.

Explanation The Grammar Manager is out of service; grammars won't be accessible

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-GRAMMAR_MGR- 3 -SYSGRAMMAR_FILE_SUPPORT_FAILURE : System grammar file support failure. Exception [String]

Explanation The Grammar Manager can not register file support for system grammar files; system grammars will not be synchronized on local server

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-GRAMMAR_MGR- 3 -WEBSERVICES_ERROR : Exception thrown while processing web services for Grammar. Exception [String]

Explanation Exception thrown while processing web services for Grammar

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-GRAMMAR_MGR- 2 -INVALID_SYSTEM_DIR : Invalid system grammar directory configured. Directory [String] Exception [String]

Explanation The configured system grammar directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-GRAMMAR_MGR- 3 -UNABLE_LOAD_GRAMMAR : Unable to load the grammar file. Name [String] Type [String] Language [String] Exception [String]

Explanation The Grammar Manager is unable to load the specified grammar file

Recommended Action Verify and update the configuration

Error Message
MEDT-GRAMMAR_MGR- 3 -UNSUPPORTED_CONVERSION : Unsupported grammar conversion. Type [String] Conversion Type [String] Exception [String]

Explanation The specified grammar conversion is not supported

Recommended Action Verify and update the application

Error Message
MEDT-LIB_CRTP- 3 -CRTP_INTERCEPT_ERROR : CRTP interceptor error operation. Error reason [String] Exception [String]

Explanation CRTP interceptor encountered an error while performing the following operation

Recommended Action No actions needed

Error Message
MEDT-LIB_CRTP- 3 -CRTP_SERVLET_ERROR : CRTP servlet error. Error reason [String] Exception [String]

Explanation CRTP servlet encountered an error while performing the following operation

Recommended Action No actions needed

Error Message
MEDT-LIB_DATABASE- 6 -RECOVERY_COMPLETED_EVENT : Received recovery completed event; DB alias will be synched now.

Explanation Database component detected recovery completed event; DB alias will be synched now.

Recommended Action No actions needed

Error Message
MEDT-LIB_DATABASE- 3 -SUBSCRIBER_DB_UNAVAILABLE : Subscriber database is not running or inaccessible.

Explanation An attempt to connect to the subscriber database has failed. Verify that the subscriber database is functioning and network connectivity is available to the subscriber node.

Recommended Action Investigate as required

Error Message
MEDT-LIB_DATABASE- 6 -UPLOAD_USER_FILE_FAILED : Database Archive Component fails to upload the corresponding file or directory to Repository Datastore. It will be copied to the specified temporary location. file or directory name [String] temporary directory name [String] Exception [String]

Explanation Database Archive Component fails to upload the corresponding file or directory to Repostiory Datastore during upgrade migration. The file or directory will be copied to the specified temporary directory.

Recommended Action Investigate as required

Error Message
MEDT-LIB_DATABASE- 3 -DATABASE_ERROR : A generic database error. Exception [String]

Explanation A generic database error occured, this could be related to SQL or none-SQL related.

Recommended Action Investigate as required

Error Message
MEDT-LIB_DATABASE- 3 -UPDATE_ERROR : update error. Exception [String]

Explanation Error in updating the cluster info

Recommended Action Investigate as required

Error Message
MEDT-LIB_DATABASE- 3 -COPYING_USER_FILES_FAILED : Database Archive Component fails to copy the corresponding file or directory to temporary location. file or directory name [String] temporary directory name [String] Exception [String]

Explanation Database Archive Component fails to copy the corresponding file or directory to temporary location, in an attempt to save the file after it fails to upload it to Repository datastore.

Recommended Action Investigate as required

Error Message
MEDT-LIB_DATABASE- 3 -DB_REPLICATION_ERROR : A generic database replication error. Exception [String]

Explanation A generic database replication error occured, this could be related to SQL or none-SQL related.

Recommended Action Investigate as required

Error Message
MEDT-LIB_DATABASE- 1 -DB_REPLICATION_STOPPED : Database replication stopped. Reason for Stopping Replication [String] Exception [String]

Explanation Database replication is stopped. Please Setup Replication from DataStore Control Center, after bringing the other node up.

Recommended Action Investigate as required

Error Message
MEDT-LIB_DATABASE- 6 -SCRIPT_NOT_FOUND : Database Archive Component could not find the corresponding file or directory to upload during restore. file or directory location [String]

Explanation Database Archive Component could not find the corresponding file or directory to upload during restore

Recommended Action Investigate as required

Error Message
MEDT-LIB_DATABASE- 1 -DB_NOT_IN_SYNC : Database is not in sync on both nodes.

Explanation One of more tables in Database are not in sync across nodes. Please Check whether replication is working fine. If replication is broken, reset replication else synchronize data on both nodes using forced data sync from CLI

Recommended Action Investigate as required

Error Message
MEDT-LIB_DATABASE- 6 -DB_REPLICATION_INITIALIZING : DB Replication is getting initialized.

Explanation DB Replication is getting initialized

Recommended Action No actions needed

Error Message
MEDT-LIB_DATABASE- 3 -INIT_ERROR : read error. Exception [String]

Explanation error in reading

Recommended Action Investigate as required

Error Message
MEDT-LIB_DATABASE- 4 -REPLICATION_OLD_PUBLISHER_CLEANUP_FAIL : DB Replication old publisher cleanup failed. Old Publisher [Int] Exception [String]

Explanation Failed to cleanup the old publisher role while performing a switch publisher

Recommended Action No actions needed

Error Message
MEDT-LIB_DATABASE- 6 -RECOVERY_DETECTED : Detected a recovery archive request in the system; DB alias sync is postponed until recovery is complete..

Explanation Database component detected a recovery archive request in the system; DB alias sync is postponed until recovery is complete.

Recommended Action No actions needed

Error Message
MEDT-LIB_EVENT- 3 -DISPATCH_FAILURE : A failure occured while dispatching an event. Event [String] Event source [String] Event listener [String] Exception [String]

Explanation An uncaught error occured while dispatching an event

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-LIB_EVENT- 5 -TOO_LONG_IN_QUEUE : Event queue time exceeded. Event [String] Queue Time [Long]

Explanation The specified event stayed in queue for too long

Recommended Action No actions needed

Error Message
MEDT-LIB_EVENT- 4 -EVENT_INIT_FAILURE : Unable to initialize the system event queue logger. Exception [String]

Explanation The logger could not be registered with the system event queue; the traces for the event queue will not be available

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-LIB_LDAP- 3 -LDAP_CON_ERROR : Error accessing LDAP. ldap url [String] Exception [String]

Explanation An error occurred while accessing LDAP

Recommended Action No actions needed

Error Message
MEDT-LIB_LDAP- 4 -LDAP_CON_WARNING : Problem accessing LDAP. ldap url [String] Exception [String]

Explanation An problem occurred while accessing LDAP

Recommended Action No actions needed

Error Message
MEDT-LIB_LICENSE- 3 -LICENSE_CONFIG_UNAVAILABLE_ERROR : LicenseConfig unavailable or retrieve error. Exception [String]

Explanation LicenseConfig was not accessible or the license object does not exist

Recommended Action Investigate as required

Error Message
MEDT-LIB_LICENSE- 3 -LICENSE_VM_CONFIG_ERROR : OVA Template Mismatched. VM configuration does not match the OVA Profile..

Explanation OVA Template Mismatched. VM configuration does not match the OVA Profile.

Recommended Action Please refer to the Unified CCX Virtualization DocWiki for the supported VM configurations.

Error Message
MEDT-LIB_LICENSE- 6 -NO_LICENSE : No Licenses were found. Error reason [String]

Explanation objFile returned from LDAP is null or it does not contain any valid licenses

Recommended Action No actions needed

Error Message
MEDT-LIB_LICENSE- 2 -LICENSE_PACKAGE_NONE : Upload a valid license through the Cisco Unified CCX Application Administration.. Error reason [String]

Explanation Cisco Unified CCX license package is None.Upload a valid license through Cisco Unified CCX Application Administration.

Recommended Action Verify and update the licences

Error Message
MEDT-LIB_LICENSE- 3 -RMI_LICENSE_ERROR : RMI Remote License error. Exception [String]

Explanation A problem occurred while trying to register RMI Remote License Implementation

Recommended Action Verify the RMI configuration and restart server

Error Message
MEDT-LIB_LICENSE- 3 -LICENSE_REPOSITORY_UNAVAILABLE_ERROR : Config repository inaccessible. Exception [String]

Explanation A problem occurred when trying to read licenses from the Config repository

Recommended Action Investigate as required

Error Message
MEDT-LIB_LICENSE- 3 -LICENSE_CONFIG_ERROR : Access license config error. Exception [String]

Explanation A problem occurred when trying to retrieve licenses from the license config object

Recommended Action Investigate as required

Error Message
MEDT-LIB_LICENSE- 3 -LICENSE_READ_ERROR : License read error. Exception [String]

Explanation A problem occurred when trying to read license files

Recommended Action Investigate as required

Error Message
MEDT-LIB_LICENSE- 3 -LICENSE_REPOSITORY_ERROR : License Repository error. Exception [String]

Explanation A problem occurred when trying to read licenses from the Config repository

Recommended Action Investigate as required

Error Message
MEDT-LIB_LICENSE- 6 -LICENSE_INFO : License Information. Licenses [String]

Explanation The cluster was configured with the specified licenses enabled.

Recommended Action No actions needed

Error Message
MEDT-LIB_LICENSE- 3 -LICENSE_TIME_EXPIRED : Upload a valid license through the Cisco Unified CCX Application Administration.. Error reason [String]

Explanation One or More Temporary License(s) have expired. The corresponding features would become unusable. Please upload valid license for the same through Cisco Unified CCX Application Administration.

Recommended Action Verify and update the licences

Error Message
MEDT-LIB_RMI- 5 -RMI_LOG_MONITOR_FAIL : RMI log configuration monitoring failure.

Explanation RMI layer can no longer monitor dynamic update to its log configuration; debug messages disabled

Recommended Action No actions needed

Error Message
MEDT-LIB_TPL- 6 -TPL_INFO : TPL_LOG4J Info log. A specific description for a trace [String]

Explanation TPL_LOG4J Info log

Recommended Action No actions needed

Error Message
MEDT-LIB_TPL- 3 -TPL_ERROR : Error in ThirdParty library. A specific description for a trace [String] A description for the nature of the exception [String] Exception [String]

Explanation Error in ThirdParty library

Recommended Action No actions needed

Error Message
MEDT-LIB_TPL- 5 -TPL_LOG4J_LOG_MONITOR_FAIL : TPL log configuration monitoring failure.

Explanation TPL logs layer can no longer monitor dynamic update to its log configuration; debug messages disabled

Recommended Action No actions needed

Error Message
MEDT-LIB_TPL- 6 -TPL_LOG4J_LOG_MONITOR : TPL log. message [String] error_desc [String]

Explanation Hibernate and Atomikos logs

Recommended Action No actions needed

Error Message
MEDT-LOG_MGR- 2 -MGR_PARTIAL_SERVICE : Log Manager in partial service.

Explanation The Log Manager is in partial service; logs won't be completely availablew

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-LOG_MGR- 3 -XML_PARSING_ERROR : XML parsing error. Catalog [String] Public identifier [String] System identifier [String] Line number [Int] Column number [Int] Exception [String] Nested Exception [String]

Explanation The log manager could not parse the XML log catalog

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-LOG_MGR- 6 -MGR_IN_SERVICE : Log Manager in service.

Explanation The Log Manager is in service

Recommended Action No actions needed

Error Message
MEDT-LOG_MGR- 4 -INTERRUPT : Log generation interrupted. Catalog [String] Mnemonic [String] Exception [String]

Explanation The generation of a log was interrupted

Recommended Action Restart server

Error Message
MEDT-LOG_MGR- 4 -LOG_CFG_MONITOR_FAIL : Log levels configuration monitoring failure. Exception [String]

Explanation The Log Manager can no longer monitor dynamic update to the log levels configuration; tracing can no longer be turned on or off

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-LOG_MGR- 4 -TO_STRING_FAILURE : Log toString() conversion failure. Catalog [String] Mnemonic [String] Parameter index [Int] Exception [String]

Explanation The log writer is unable to convert the given parameter in the specified log to a string

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-LOG_MGR- 5 -MGR_SHUTDOWN : Log Manager in shutdown.

Explanation The Log Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MEDT-LOG_MGR- 6 -MGR_INITIALIZING : Log Manager initializing.

Explanation The Log Manager is initializing

Recommended Action No actions needed

Error Message
MEDT-LOG_MGR- 2 -MGR_OUT_OF_SERVICE : Log Manager in out of service.

Explanation The Log Manager is out of service; logs won't be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-LOG_MGR- 5 -MGR_SHUTTING_DOWN : Log Manager shutting down.

Explanation The Log Manager is in the process of shutting down; pending logs are being flushed out

Recommended Action No actions needed

Error Message
MEDT-LOG_MGR- 3 -UNABLE_LOAD_CATALOG : Unable to load log catalog. Catalog [String] Exception [String] Nested Exception [String]

Explanation The log manager could not load the log catalog

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-LOG_MGR- 6 -CATALOG_LOADED : Log catalog loaded. Catalog [String]

Explanation The specified log catalog was loaded in memory

Recommended Action No actions needed

Error Message
MEDT-LOG_MGR- 3 -WRITER_FAILURE : Log writer failure. Catalog [String] Exception [String]

Explanation The log writer failed to properly initialize for the log catalog

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-MGR_MGR- 6 -MGR_ALREADY_INIT : Manager initialization failed. Exception [String]

Explanation A manager in the Manager Manager failed to initialize because it has already been loaded.

Recommended Action Investigate as required

Error Message
MEDT-MGR_MGR- 1 -MGR_PARTIAL_SERVICE : Manager Manager in partial service.

Explanation Some managers are currently out of service

Recommended Action Investigate as required

Error Message
MEDT-MGR_MGR- 2 -NETWORK_FAILURE_DETECTED : lookup on local host resolved to loopback address. Please check network connectivity.

Explanation lookup on local host resolved to loopback address. Please check network connectivity.

Recommended Action Investigate as required

Error Message
MEDT-MGR_MGR- 1 -MGR_CONFIG_ERROR : Error while reading configuration file for ManagerManager. Exception [String]

Explanation Error while reading configuration file for ManagerManager

Recommended Action Verify and update the configuration and restart server

Error Message
MEDT-MGR_MGR- 3 -MGR_XML_PARSE_ERROR : Could not create URL while parsing xml data. Exception [String]

Explanation Could not create URL while parsing xml data

Recommended Action Verify and update the configuration and restart server

Error Message
MEDT-MGR_MGR- 1 -RMI_FAILURE_RETRY : RMI could not be configured at the specified port. Will attempt to retry.. Exception [String]

Explanation RMI could not be configured at the specified port. Will attempt to retry.

Recommended Action Verify the RMI configuration and restart server

Error Message
MEDT-MGR_MGR- 3 -THREAD_DEATH_EXCEPTION : An uncaught exception has be thrown in a thread. Thread name [String] Exception [String]

Explanation An uncaught exception has be thrown in a thread

Recommended Action Investigate as required

Error Message
MEDT-MGR_MGR- 0 -MGRMGR_KEEPALIVE_EXCPT : A KeepAlive exception has been thrown in Manager Manager. Exception [String]

Explanation A KeepAlive exception has been thrown in Manager Manager

Recommended Action Investigate as required

Error Message
MEDT-MGR_MGR- 0 -MGRMGR_START_FAIL : Fail to start Application startable class. Exception [String]

Explanation Manager Manager fail to start the startable class

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-MGR_MGR- 4 -CLASSPATH_NOT_LOADED : A classpath was not loaded during initialization. Exception [String]

Explanation A classpath was not loaded during initialization

Recommended Action No actions needed

Error Message
MEDT-MGR_MGR- 6 -MGR_INITIALIZING : Manager Manager initializing.

Explanation The Manager Manager is initializing

Recommended Action No actions needed

Error Message
MEDT-MGR_MGR- 2 -MGR_OUT_OF_SERVICE : Manager Manager in out of service.

Explanation All primary managers are out of service

Recommended Action Investigate as required

Error Message
MEDT-MGR_MGR- 3 -MANAGER_INTERCEPT_ERROR : Manager interceptor error operation. Error reason [String] Exception [String]

Explanation Manager interceptor encountered an error while performing the following operation

Recommended Action No actions needed

Error Message
MEDT-MGR_MGR- 0 -MGRMGR_INIT_FAIL : Fail to initialize Manager Manager and start main thread. Exception [String]

Explanation Fail to initialize Manager Manager and start main thread

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-MGR_MGR- 6 -MGR_IN_SERVICE : Manager Manager in service.

Explanation The Manager Manager is in service

Recommended Action No actions needed

Error Message
MEDT-MGR_MGR- 0 -APP_SVC_INIT_ERROR : Application services initialization error. Exception [String]

Explanation The Application services could not be initialized because the RMI registry could not be accessed

Recommended Action Verify the RMI configuration and restart server

Error Message
MEDT-MGR_MGR- 6 -MGRMGR_PERFMON_INIT_SUCCESS : Application successfully initialized perfmon dll.

Explanation The Application services loaded the WFCCNPerfWin32 dll

Recommended Action No actions needed

Error Message
MEDT-MGR_MGR- 1 -BOOTSTRAP_INIT_ERROR : Error occurred while initializing bootstrap information. Exception [String]

Explanation Error occurred while initializing bootstrap information

Recommended Action Verify and update the configuration and restart server

Error Message
MEDT-MGR_MGR- 1 -CURRENCY_CFG_MONITOR_FAIL : Currency configuration monitoring failure. Exception [String]

Explanation The system default currency can no longer be updated dynamically

Recommended Action Investigate as required

Error Message
MEDT-MGR_MGR- 1 -WEB_SERVICE_ERROR : Web service initialization error. Error reason [String]

Explanation Web service initialization error

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-MGR_MGR- 4 -IP_HOSTNAME_UPDATE : Host Name of one of the UCCX Servers in cluster is changed. Old Host Name [String] New Host Name [String]

Explanation Host Name of one of the UCCX Servers in cluster is changed

Recommended Action No actions needed

Error Message
MEDT-MGR_MGR- 3 -CLASSPATH_NOT_FOUND : Configured classpath is not found. Exception [String]

Explanation Configured classpath is not found

Recommended Action Verify and update the configuration and restart server

Error Message
MEDT-MGR_MGR- 3 -HOSTFILE_ERROR : An error occurred while trying to access host file. Exception [String]

Explanation An error occurred while trying to access host file

Recommended Action Verify and update the configuration

Error Message
MEDT-MGR_MGR- 3 -MGRMGR_ROOTDIR_ERROR : No root directory path found in properties file.

Explanation No root directory path found in properties file

Recommended Action No actions needed

Error Message
MEDT-MGR_MGR- 1 -HIGH_MEM_USAGE : JVM heap memory usage is high. Facility [String] Current usage [String] Maximum available [String] percentage Old Gen Memory used [Int]

Explanation JVM heap memory usage is high

Recommended Action Investigate as required

Error Message
MEDT-MGR_MGR- 5 -MGRMGR_KEEPALIVE_EXCPT_CANCEL : Manager Manager is attempting to cancel KeepAlive exception. Exception [String]

Explanation KeepAlive exception is cancelled in ManagerManager because the manager in question return from a timeout. Note that this does not mean Node Manager did not detect the KeepAlive exception. It might be that Node Manager detected the exception while ManagerManager is cancelling it.

Recommended Action No actions needed

Error Message
MEDT-MGR_MGR- 1 -APP_CFG_SYNC_FAIL : Application configuration failure. Exception [String]

Explanation The Manager Manager could not retrieve configuration information from the Config Framework. Using local configuration.

Recommended Action Investigate as required

Error Message
MEDT-MGR_MGR- 1 -RMI_PORT_CONFIGURATION_FAILURE : Failed to configure new rmi port. Old Port [String] New Port [String]

Explanation Cannot modify rmi port to the configured value since port is in use by another application. Please change rmi port configuration using CRS Administrator.

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-MGR_MGR- 6 -DEFAULT_CURRENCY_UPDATE : System default currency updated. Currency [String]

Explanation The system default currency was updated

Recommended Action No actions needed

Error Message
MEDT-MGR_MGR- 5 -MGR_SHUTTING_DOWN : Manager Manager in shutting down.

Explanation The Manager Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MEDT-MGR_MGR- 1 -REGISTRY_INIT_ERROR : An error occurred during initialization of registry. Exception [String]

Explanation RMI Registry could not be initialized.

Recommended Action Verify the RMI configuration and restart server

Error Message
MEDT-MGR_MGR- 4 -CUSTOM_PROP_NOT_FOUND : CustomFileClasspath.properties file is not found.

Explanation CustomFileClasspath.properties file is not found

Recommended Action No actions needed

Error Message
MEDT-MGR_MGR- 1 -REGISTRY_RETRY_ERROR : Maximum retries reached trying to create registry. No registry created.. Registry retry value [String]

Explanation Maximum retries reached trying to create registry. No registry created.

Recommended Action Verify the RMI configuration and restart server

Error Message
MEDT-MGR_MGR- 6 -REGISTRY_RETRY_INFO : Could not create registry at specified port. Will retry at different port. Port [String]

Explanation ManagerManager could not create registry at specified port. Will retry at different port

Recommended Action No actions needed

Error Message
MEDT-MGR_MGR- 1 -BOOTSTRAP_SYNC_ERROR : ManagerManager bootstrap sync failure. Exception [String]

Explanation ManagerManager cannot synchronize the bootstrap information due to the following problem

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-MGR_MGR- 4 -MANAGER_INTERCEPT_WARNING : Manager interceptor warning. Reason for this warning [String]

Explanation Manager interceptor warning log info

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-MGR_MGR- 1 -APP_CFG_MONITOR_FAIL : Application configuration monitoring failure. Exception [String]

Explanation The Manager Manager can no longer monitor dynamic update to some of its configuration

Recommended Action Investigate as required

Error Message
MEDT-MGR_MGR- 1 -MGR_INIT_ERROR : Manager initialization error. Exception [String]

Explanation A manager in the Manager Manager cannot be instantiated and will not be available

Recommended Action Investigate as required

Error Message
MEDT-MGR_MGR- 0 -UNRECOVERABLE_ERROR : An unrecoverable error has occurred. Exception [String]

Explanation An unrecoverable error has occurred

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-MGR_MGR- 3 -MGRMGR_SHUTDOWN_FAIL : An exception occurred while shutting down Manager Manager. Exception [String]

Explanation An exception occurred while shutting down Manager Manager

Recommended Action Investigate as required

Error Message
MEDT-MGR_MGR- 5 -MGR_SHUTDOWN : Manager Manager in shutdown.

Explanation The Manager Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MEDT-MGR_MGR- 4 -IP_ADDRESS_UPDATE : IP Address of one of the UCCX Servers in cluster is changed. Old IP Address [String] New IP Address [String]

Explanation IP Address of one of the UCCX Servers in cluster is changed

Recommended Action No actions needed

Error Message
MEDT-MGR_MGR- 3 -MGRMGR_BEAN_ERROR : Error setting design time bean. Exception [String]

Explanation There was an error setting the design time bean

Recommended Action No actions needed

Error Message
MEDT-MGR_MGR- 0 -THREADS_DUMP : Java Virtual Machine Threads Dump. Message [String] Exception [String]

Explanation A dump of all running threads was just produced in JVM.log. Collect all existing logs and the JVM.log file and forward them to Cisco.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-MGR_MGR- 3 -GET_DEFAULT_USER_ERROR : Default User could not be retrieved. Exception [String]

Explanation Default User could not be retrieved due to the following error

Recommended Action No actions needed

Error Message
MEDT-MGR_MGR- 1 -MEMORY_USAGE_EXCEEDED_THRESHOLD : Memory usage exceeded the threshold set. Facility [String] Current usage [String] Maximum available [String] percentage Heap memory used [Int]

Explanation Memory usage exceeded the threshold set

Recommended Action Investigate as required

Error Message
MEDT-MGR_MGR- 1 -SYS_CFG_SYNC_FAIL : System configuration failure. Exception [String]

Explanation The Manager Manager could not retrieve system configuration from the Config Framework. Using local configuration.

Recommended Action Investigate as required

Error Message
MEDT-MGR_MGR- 1 -RMI_CREATE_ERROR : Cannot create rmi registry at specified port location. Port [String] Exception [String]

Explanation Cannot create rmi registry at specified port location since port is in use by another application. Please change rmi port configuration using CRS Administrator or shutdown the process using the specified port.

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-MGR_MGR- 1 -SYS_CFG_MONITOR_FAIL : System configuration monitoring failure. Exception [String]

Explanation The Manager Manager can no longer monitor dynamic update to the system configuration

Recommended Action Investigate as required

Error Message
MEDT-PALETTE- 6 -IN_SERVICE : Cisco Customer Response Solutions Editor Pallete Manager started.

Explanation Cisco Customer Response Solutions Editor Pallete Manager started

Recommended Action No actions needed

Error Message
MEDT-PROMPT_MGR- 1 -MGR_PARTIAL_SERVICE : Prompt Manager in partial service.

Explanation The Prompt Manager is in partial service; synchronization of files with prompt repository is in progress

Recommended Action Investigate as required

Error Message
MEDT-PROMPT_MGR- 3 -INVALID_TTS_PROVIDER : Invalid TTS prompt provider. Name [String] Exception [String]

Explanation The specified TTS prompt provider is invalid

Recommended Action Verify and update the configuration

Error Message
MEDT-PROMPT_MGR- 2 -INVALID_USER_DIR : Invalid user prompt directory configured. Directory [String] Exception [String]

Explanation The configured user prompt directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-PROMPT_MGR- 3 -UNDEFINED_GENERATED_PROMPT : Undefined generated prompt. Generated Prompt [String] Language [String] Exception [String]

Explanation Unable to resolve the generated prompt

Recommended Action Verify and update the application and if problem persist contact Cisco technical assistance center

Error Message
MEDT-PROMPT_MGR- 6 -GENERATOR_FALLBACK : Falling back to system prompt generators. Generated Prompt [String] Generator Constructor [String] Bundle [String] Language [String] Exception [String]

Explanation The Prompt Manager failed to use the prompt generator bundle specified by the generated prompt and is falling back to the systemprompt generators

Recommended Action Verify and update the application

Error Message
MEDT-PROMPT_MGR- 3 -UNSUPPORTED_PROMPT : Unsupported prompt type. Name [String] Type [String] Language [String] Exception [String]

Explanation The specified prompt type is not supported

Recommended Action Verify and update the application

Error Message
MEDT-PROMPT_MGR- 3 -PROMPT_LEXICAL_ERROR : Template prompt lexical error. Name [String] Template [String] Language [String] Exception [String]

Explanation The specified lexical error occured while parsing a template prompt

Recommended Action Verify and update the application

Error Message
MEDT-PROMPT_MGR- 3 -UNDEFINED_NAME_PROMPT : Undefined user or system prompt. Name [String] Type [String] Transcription [String] Language [String] Exception [String]

Explanation A user or system prompt cannot be located

Recommended Action Verify and update the configuration

Error Message
MEDT-PROMPT_MGR- 3 -UNDEFINED_TTS_PROMPT : Undefined TTS prompt. Name [String] Transcription [String] Language [String] Exception [String]

Explanation A TTS prompt cannot be generated

Recommended Action Verify and update the configuration and restart server

Error Message
MEDT-PROMPT_MGR- 3 -UNDEFINED_SILENCE_PROMPT : Undefined silence prompt. Silence Duration [Long] Exception [String]

Explanation A silence prompt cannot be located

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-PROMPT_MGR- 3 -PROMPT_FILE_SUPPORT_FAILURE : Prompt file support failure. Exception [String]

Explanation The Prompt Manager can not register file support for user prompt files; user prompts will not be synchronized on local server

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-PROMPT_MGR- 6 -MGR_INITIALIZING : Prompt Manager initializing.

Explanation The Prompt Manager is initializing

Recommended Action No actions needed

Error Message
MEDT-PROMPT_MGR- 2 -MGR_OUT_OF_SERVICE : Prompt Manager in out of service.

Explanation The Prompt Manager is out of service; prompts won't be accessible

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-PROMPT_MGR- 5 -MGR_SHUTTING_DOWN : Prompt Manager shutting down.

Explanation The Prompt Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MEDT-PROMPT_MGR- 6 -SYSTEM_TTS_PROVIDER : System TTS provider registered. Name [String]

Explanation A system TTS prompt provider has been registered

Recommended Action No actions needed

Error Message
MEDT-PROMPT_MGR- 6 -MGR_IN_SERVICE : Prompt Manager in service.

Explanation The Prompt Manager is in service

Recommended Action No actions needed

Error Message
MEDT-PROMPT_MGR- 5 -MGR_SHUTDOWN : Prompt Manager in shutdown.

Explanation The Prompt Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MEDT-PROMPT_MGR- 3 -UNABLE_CREATE_TTS : Unable to instantiate TTS prompt provider. Name [String] Classname [String] Exception [String]

Explanation The specified TTS prompt provider cannot be located or instantiated

Recommended Action Verify and update the configuration and restart server

Error Message
MEDT-PROMPT_MGR- 3 -PROMPT_PARSING_ERROR : Template prompt parsing error. Name [String] Template [String] Language [String] Exception [String]

Explanation The specified error occured while parsing a template prompt

Recommended Action Verify and update the application

Error Message
MEDT-PROMPT_MGR- 6 -NO_SYSTEM_TTS_PROVIDER : No system TTS provider registered.

Explanation There is no system TTS prompt provider currently registered

Recommended Action Verify and update the configuration

Error Message
MEDT-PROMPT_MGR- 6 -TTS_PROVIDER_FALLBACK : Falling back to system configured TTS provider. Transcription [String] Language [String] Name [String] Exception [String]

Explanation The Prompt Manager failed to use the TTS prompt provider specified by the TTS prompt and is falling back to the system TTS prompt provider

Recommended Action Verify and update the application

Error Message
MEDT-PROMPT_MGR- 3 -UNDEFINED_GENERATOR : Undefined prompt generator. Generated Prompt [String] Generator Constructor [String] Bundle [String] Language [String] Exception [String]

Explanation The Prompt Manager failed to locate a prompt generator as requested

Recommended Action Verify and update the application and if problem persist contact Cisco technical assistance center

Error Message
MEDT-PROMPT_MGR- 3 -INVALID_GENERATOR : Invalid prompt generator. Generated Prompt [String] Generator Name [String] Generator Constructor [String] Language [String] Exception [String]

Explanation The Prompt Manager failed to instantiate the rquested prompt generator

Recommended Action Verify and update the application and if problem persist contact Cisco technical assistance center

Error Message
MEDT-PROMPT_MGR- 3 -WEBSERVICES_ERROR : Exception thrown while processing web services for Prompt. Exception [String]

Explanation Exception thrown while processing web services for Prompt

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-PROMPT_MGR- 2 -INVALID_SYSTEM_DIR : Invalid system prompt directory configured. Directory [String] Exception [String]

Explanation The configured system prompt directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-SCRIPT_MGR- 1 -MGR_PARTIAL_SERVICE : Script Manager in partial service.

Explanation The Script Manager is in partial service; synchronization of files with script repository is in progress

Recommended Action No actions needed

Error Message
MEDT-SCRIPT_MGR- 3 -STEP_COPY_FAILURE : Unable to copy a step. Script [String] Step id [Long] Step Class [String] Step Description [String] Exception [String]

Explanation The specified step could not be copied

Recommended Action Verify and update the configuration

Error Message
MEDT-SCRIPT_MGR- 3 -UNSUPPORTED_SCRIPT : Unsupported script type. Script [String] Type [String] Domain [String] Exception [String]

Explanation The specified script type is not supported

Recommended Action Verify and update the script

Error Message
MEDT-SCRIPT_MGR- 2 -INVALID_USER_DIR : Invalid user script directory configured. Directory [String] Exception [String]

Explanation The configured user script directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-SCRIPT_MGR- 3 -INVALID_FINAL_CFG_VAR : Variable defined as a final variable. Application [String] Script [String] Variable [String] Exception [String]

Explanation The script variable is defined as final which cannot be modified

Recommended Action Verify and update the configuration

Error Message
MEDT-SCRIPT_MGR- 4 -HIDDEN_STEP_FOUND : Script contains an hidden step. Script [String] Step id [Long] Step Class [String] Step Description [String]

Explanation The specified script contains the specified hidden step

Recommended Action Load the script in the Unified CCX Editor and save it back; this will removethe hidden step

Error Message
MEDT-SCRIPT_MGR- 3 -INVALID_SCRIPT : Invalid script. Script [String] Exception [String]

Explanation The script configured is invalid and cannot be loaded

Recommended Action Verify and update the script

Error Message
MEDT-SCRIPT_MGR- 4 -CFG_VAR_NOT_DEFINED : Variable not defined in script. Application [String] Script [String] Variable [String]

Explanation A configured variable is not defined in the script

Recommended Action Verify and update the configuration

Error Message
MEDT-SCRIPT_MGR- 3 -SCRIPT_NOT_DEFINED : Script not defined. Script [String] Exception [String]

Explanation The specified script is not configured in the repository

Recommended Action Verify and update the script

Error Message
MEDT-SCRIPT_MGR- 3 -NOT_A_CFG_VAR : Variable not defined as a configuration variable. Application [String] Script [String] Variable [String]

Explanation A configured variable is not defined as a configuration variable in the script

Recommended Action Verify and update the configuration

Error Message
MEDT-SCRIPT_MGR- 2 -NO_SCRIPT_CTX : No context defined in script. Application [String] Script [String]

Explanation The specified script doesn't have a context of variables defined

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-SCRIPT_MGR- 6 -MGR_INITIALIZING : Script Manager initializing.

Explanation The Script Manager is initializing

Recommended Action No actions needed

Error Message
MEDT-SCRIPT_MGR- 2 -MGR_OUT_OF_SERVICE : Script Manager in out of service.

Explanation The Script Manager is out of service; Scripts won't be accessible

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-SCRIPT_MGR- 5 -MGR_SHUTTING_DOWN : Script Manager shutting down.

Explanation The Script Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MEDT-SCRIPT_MGR- 3 -RMI_REBIND_FAILED : Unable to register remote interface. Exception [String]

Explanation A remote interface could not be bound to the RMI registry; remote access for dynamic update or other functions will not be available

Recommended Action Verify the RMI configuration and restart server

Error Message
MEDT-SCRIPT_MGR- 6 -MGR_IN_SERVICE : Script Manager in service.

Explanation The Script Manager is in service

Recommended Action No actions needed

Error Message
MEDT-SCRIPT_MGR- 3 -CUSTOMIZER_ERROR : Exception thrown while processing customizer of a step in Script. Application [String] Script [String]

Explanation Exception thrown while processing customizer of a step in Script

Recommended Action Verify and update the configuration

Error Message
MEDT-SCRIPT_MGR- 5 -MGR_SHUTDOWN : Script Manager in shutdown.

Explanation The Script Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MEDT-SCRIPT_MGR- 3 -UNABLE_LOAD_SCRIPT : Unable to load script. Script [String] Exception [String]

Explanation The script manager could not load the specified script

Recommended Action Verify and update the script

Error Message
MEDT-SCRIPT_MGR- 3 -INVALID_LICENSES : Invalid licenses. Script [String] Exception [String]

Explanation The script configured cannot be loaded because of missing licenses

Recommended Action Verify and update the licences

Error Message
MEDT-SCRIPT_MGR- 3 -INCOMPATIBLE_CFG_VAR_TYPES : Incompatible configuration variable types. Application [String] Script [String] Variable [String] Variable type defined [String] Variable type configured [String] Exception [String]

Explanation A configured variable type is incompatible with the variable defined script

Recommended Action Verify and update the configuration

Error Message
MEDT-SCRIPT_MGR- 3 -UNDEFINED_NAME_SCRIPT : Undefined user or system script. Script [String] Type [String] Domain [String] Exception [String]

Explanation A user or system script cannot be located

Recommended Action Verify and update the configuration

Error Message
MEDT-SCRIPT_MGR- 3 -CORRUPTED_SCRIPT : The script is corrupted. Script [String] Exception [String]

Explanation The specified script or the last script that the system attempted to load is corrupted and cannot be sucessfully loaded

Recommended Action Please Contact Cisco technical assistance center to recover the script

Error Message
MEDT-SCRIPT_MGR- 3 -WEBSERVICES_ERROR : Exception thrown while processing web services for Script. Exception [String]

Explanation Exception thrown while processing web services for Script

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-SCRIPT_MGR- 2 -INVALID_SYSTEM_DIR : Invalid system script directory configured. Directory [String] Exception [String]

Explanation The configured system script directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-SCRIPT_MGR- 3 -SCRIPT_FILE_SUPPORT_FAILURE : Script file support failure. Exception [String]

Explanation The Script Manager can not register file support for script files; scripts will not be accesible from the script repository

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-SOCKET_MGR- 1 -MGR_PARTIAL_SERVICE : Socket Manager in partial service.

Explanation The Socket Manager is in partial service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-SOCKET_MGR- 6 -MGR_IN_SERVICE : Socket Manager in service.

Explanation The Socket Manager is in service

Recommended Action No actions needed

Error Message
MEDT-SOCKET_MGR- 4 -MISSING_RESOURCE : Missing socket resources. Facility [String] Sub-Facility [String] Socket allocator id [String] Exception [String]

Explanation The socket manager is unable to locate internal socket resources

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-SOCKET_MGR- 5 -MGR_SHUTDOWN : Socket Manager in shutdown.

Explanation The Socket Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MEDT-SOCKET_MGR- 4 -REQUEST_TIMEOUT : Requesting a socket timed out. Facility [String] Sub-Facility [String] Socket allocator id [String] Mnemonic [String] Thread [String] Time [Long]

Explanation Request to get a socket timed out

Recommended Action No actions needed

Error Message
MEDT-SOCKET_MGR- 4 -REQUEST_FAILED : Requesting a socket failed. Facility [String] Sub-Facility [String] Socket allocator id [String] Mnemonic [String] Thread [String] Time [Long] Exception [String]

Explanation Request to get a socket failed

Recommended Action No actions needed

Error Message
MEDT-SOCKET_MGR- 4 -REQUEST_BLOCKED : Invoking blocked allocation handler. Facility [String] Sub-Facility [String] Socket allocator id [String] Mnemonic [String] Thread [String] Time [Long] Handler [String]

Explanation The specified blocked allocation handler is being invoked for the specified socket request as the allocator queue could not accept it

Recommended Action No actions needed

Error Message
MEDT-SOCKET_MGR- 6 -MGR_INITIALIZING : Socket Manager initializing.

Explanation The Socket Manager is initializing

Recommended Action No actions needed

Error Message
MEDT-SOCKET_MGR- 2 -MGR_OUT_OF_SERVICE : Socket Manager in out of service.

Explanation The Socket Manager is out of service; allocators won't be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-SOCKET_MGR- 5 -MGR_SHUTTING_DOWN : Socket Manager shutting down.

Explanation The Socket Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MEDT-STEPS_CALL_CONTACT- 4 -STEPS_CALL_CONTACT : A Call Contact step is running.. Task id [Long]

Explanation An Exception is thrown from a Call Contact Step.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-STEPS_CONTACT- 4 -STEPS_CONTACT : A contact step is running.. Task id [Long]

Explanation An Exception is thrown from a Contact Step.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-STEPS_DB- 3 -STEPS_DB : General DB Step Exception. Exception [String]

Explanation There is exception occured during a DB Step execution.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-STEPS_EMAIL- 3 -EMAIL_ATTACH_NO_DOC_EXISTS : Attached document for this local variable does not exist. Local Variable [String] Task id [Long]

Explanation The attached document for this local variable does not exist. It must exist in order to be sent.

Recommended Action Verify and update the configuration

Error Message
MEDT-STEPS_EMAIL- 3 -EMAIL_NOT_INITIATED : The step uses an eMail Variable Name that has not been initiated.. Local Variable [String] Task id [Long]

Explanation The step uses an eMail Variable Name that has not been initiated. The Create eMail step must initiate the email.

Recommended Action Verify and update the configuration

Error Message
MEDT-STEPS_EMAIL- 2 -EMAIL_STEP_GENERAL_EX : General exception from processing. Exception [String] Step [String] Task id [Long]

Explanation General exception in executing this step

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-STEPS_EMAIL- 3 -EMAIL_ATTACH_NOT_STR_OR_DOC : Attached document for this local variable is neither of type "java.lang.String" or "com.cisco.doc.Document.". Local Variable [String] Task id [Long]

Explanation The attached document for this local variable is not the proper type.

Recommended Action Verify and update the configuration

Error Message
MEDT-STEPS_EMAIL- 2 -EMAIL_PREPROCESS_EX : Exception from preprocessing expressions. Exception [String] Step [String]

Explanation Exception from preprocessing expressions on this step's customizer

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-STEPS_EMAIL- 3 -EMAIL_NOT_CONFIGURED : eMail Subsystem has not been configured. Step [String]

Explanation The eMail subsystem was not configured (needs Mail Server), therefore this workflow cannot be run

Recommended Action Verify and update the configuration

Error Message
MEDT-STEPS_GENERAL- 3 -EXECUTE_ANNOTATION_STEP : Expect comments. Exception [String] Step [String] Task id [Long]

Explanation Exception from preprocessing expressions on this step's customizer

Recommended Action No actions needed

Error Message
MEDT-STEPS_GRAMMAR- 3 -EXPECT_RECOGNIZABLE_VARIABLE : Expect Playable variable. Exception [String] Step [String] Task id [Long]

Explanation Exception from preprocessing expressions on this step's customizer

Recommended Action No actions needed

Error Message
MEDT-STEPS_GRAMMAR- 3 -GRAMMAR_STEP_EXCEPTION : Exception. Exception [String] Step [String] Task id [Long]

Explanation Exception from a grammar step

Recommended Action No actions needed

Error Message
MEDT-STEPS_JAVA- 3 -EXECUTE_ANNOTATION_STEP : Expect comments. Exception [String] Step [String] Task id [Long]

Explanation Exception from preprocessing expressions on this step's customizer

Recommended Action No actions needed

Error Message
MEDT-STEP_MEDIA_CONTROL- 3 -MEDIA_STEP_RUNNING : General Media Step Exception. Exception [String]

Explanation There is exception occured during a media step execution.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-STEP_MEDIA_CONTROL- 3 -RECORDING_GENERAL_EX : General Recording Exception. Exception [String]

Explanation There is exception occured during recording step execution.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-STEP_MEDIA_CONTROL- 3 -RECORDING_PREPROCESS_EX : Preprocess failed for Recording Step. Exception [String]

Explanation There is exception occured during recording step preprocess.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-STEP_MEDIA_CONTROL- 3 -MEDIA_STEP_STOPPING : General Media Step Exception. Exception [String]

Explanation There is exception occured during a media step stopping.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-STEP_MEDIA_CONTROL- 3 -RECORDING_CUSTOMIZER_EX : Customizer failed for Recording Step. Exception [String]

Explanation There is exception occured during recording step customizer.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-STEP_MEDIA_CONTROL- 3 -RECORDING_EXECUTE_EX : Execute failed for Recording Step. Exception [String] Task id [Long]

Explanation There is exception occured during recording step execute.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-STEPS_PROMPT- 3 -EXPECT_PLAYABLE_VARIABLE : Expect Playable variable. Exception [String] Step [String] Task id [Long]

Explanation Exception from preprocessing expressions on this step's customizer

Recommended Action No actions needed

Error Message
MEDT-STEPS_SESSION- 3 -SESSION_STEP_RUNNING : Session Step Running. Exception [String] Step [String] Task id [Long]

Explanation Exception from preprocessing expressions on this step's customizer

Recommended Action No actions needed

Error Message
MEDT-STEPS_USER- 2 -DATASTORE_IO_ACCESS_EX : General datastore search exception. Task id [Long] Step [String] Exception [String]

Explanation General datastore search exception in executing this step

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MEDT-STEPS_USER- 4 -SPOKEN_NAME_UPLOAD_ERROR : Unable to upload spoken name. Exception [String]

Explanation Unable to upload the spoken name to the Repository

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MEDT-STEPS_USER- 4 -USERS_NOT_UNIQUE : The Userbase has been incorrectly configured. Task id [Long] Step [String] User [String]

Explanation The directory lists several Users having the same Agent Extension, therefore the first User on the list is returned.

Recommended Action Verify and update the configuration

Error Message
MEDT-STEPS_USER- 3 -AUTHENTICATE_ERROR : Authenticating error. Exception [String]

Explanation A problem occur when authenticating password

Recommended Action No actions needed

Error Message
MIVR-APP_MGR- 1 -MGR_PARTIAL_SERVICE : Application Manager in partial service.

Explanation The Application Manager is in partial service; some applications could not be properly loaded from the repository

Recommended Action Verify and update the configuration

Error Message
MIVR-APP_MGR- 3 -INVALID_APP_TYPE : Invalid application type. Application [String] Type [String] Exception [String]

Explanation The application type configured is invalid and cannot be loaded

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-APP_MGR- 1 -CLUSTER_LICENSE_ACCESS_FAILED : Unable to access licenses from cluster. Exception [String]

Explanation Could not access licenses from cluster; applications will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-APP_MGR- 3 -TASK_ADD_CHANNEL_ERROR : Adding channel error. Application [String] Application Trigger [String] Task id [Long] Exception [String]

Explanation Attempting to add channel to the task failed

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-APP_MGR- 6 -APP_UNLOADED : Application unloaded. Application [String]

Explanation The specified application was unloaded from memory

Recommended Action No actions needed

Error Message
MIVR-APP_MGR- 1 -DEADLOCK_COUNT_EXCEEDED : Deadlock count exceeded. Deadlock info [String]

Explanation Deadlock count exceeded

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-APP_MGR- 6 -TERMINATING_CONTACT : Terminating contact. Application [String] Task id [Long] Contact id [Int] Contact implementation id [String] Contact Class [String] Contact Type [String] Exception [String]

Explanation The specified contact is being terminated because the task is no longer active

Recommended Action Verify and update the application

Error Message
MIVR-APP_MGR- 1 -DFLT_SCRIPT_LOAD_ERROR : Failed to load default script. Script [String] Exception [String]

Explanation The specified default script failed to be loaded in memory

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-APP_MGR- 3 -APP_NOT_DEFINED : Application not defined. Application [String]

Explanation The specified application is not configured in the repository

Recommended Action Verify and update the configuration

Error Message
MIVR-APP_MGR- 6 -DFLT_SCRIPT_LOADED : Default script loaded. Script [String]

Explanation The specified default script was loaded in memory

Recommended Action No actions needed

Error Message
MIVR-APP_MGR- 6 -MGR_INITIALIZING : Application Manager initializing.

Explanation The Application Manager is initializing

Recommended Action No actions needed

Error Message
MIVR-APP_MGR- 2 -NO_SCRIPT_CTX : No context defined in script. Application [String] Script [String]

Explanation The specified script doesn't have a context of variables defined

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-APP_MGR- 2 -MGR_OUT_OF_SERVICE : Application Manager in out of service.

Explanation The Application Manager is out of service; all applications are either disabled or failed to be loaded from the repository

Recommended Action Verify and update the configuration

Error Message
MIVR-APP_MGR- 3 -UNABLE_INVOKE_APP : Unable to invoke application. Application [String] Exception [String]

Explanation The application manager could not invoke the specified application

Recommended Action Verify and update the configuration

Error Message
MIVR-APP_MGR- 2 -UNABLE_CREATE_APP : Unable to create application. Application [String] Type [String] Application Class [String] Exception [String]

Explanation The application manager could not create the specified application of the specified type

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-APP_MGR- 3 -UNABLE_CREATE_TASK : Unable to create application task. Application [String] Application Trigger [String] Exception [String]

Explanation The application manager could not create a task for the specified application

Recommended Action Verify and update the configuration

Error Message
MIVR-APP_MGR- 6 -MGR_IN_SERVICE : Application Manager in service.

Explanation The Application Manager is in service

Recommended Action No actions needed

Error Message
MIVR-APP_MGR- 6 -SCRIPT_LOADED : Script loaded. Script [String]

Explanation The specified script was loaded in memory

Recommended Action No actions needed

Error Message
MIVR-APP_MGR- 4 -CFG_LISTENER_FAILURE : Unable to register a configuration listener. Exception [String]

Explanation The configuration for all applications cannot be dynamically reloaded and will require a restart of the service

Recommended Action No actions needed

Error Message
MIVR-APP_MGR- 3 -INVOKE_APP_TIMEOUT : Timeout trying to invoke application. Application [String] Timeout [Long] Exception [String]

Explanation The application manager timed out trying to invoke the specified application

Recommended Action Verify and update the configuration

Error Message
MIVR-APP_MGR- 3 -TASK_INITIALIZER_ERROR : Error calling a task initializer. Application [String] Application Trigger [String] Task id [Long] Exception [String]

Explanation An error occured while calling back a task initializer

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-APP_MGR- 3 -INVALID_TRIGGER_TYPE : Invalid type of trigger. Application [String] Application Trigger [String] Expected Application Trigger [String] Exception [String]

Explanation The requested application was triggered with an invalid type of trigger

Recommended Action Verify and update the application

Error Message
MIVR-APP_MGR- 3 -INCOMPATIBLE_APP_TYPES : Incompatible application types. Application [String] Current type [String] New type [String]

Explanation The new application type configured is incompatible with the current type

Recommended Action Verify and update the configuration and restart server

Error Message
MIVR-APP_MGR- 3 -TASK_ABORTED : Application task aborted. Application [String] Application Trigger [String] Task id [Long] Task Class [String] Exception [String]

Explanation An application task was aborted

Recommended Action Verify and update the application and if problem persist contact Cisco technical assistance center

Error Message
MIVR-APP_MGR- 3 -CLUSTER_RMI_REBIND_FAILED : Unable to register remote interface in cluster space. Exception [String]

Explanation A remote interface could not be binded to the cluster space; remote access for dynamic update or other functions will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-APP_MGR- 6 -APP_RELOADED : Application reloaded. Application [String]

Explanation The specified application was reloaded in memory

Recommended Action No actions needed

Error Message
MIVR-APP_MGR- 3 -STEP_FAILURE : Failure to execute a step. Application [String] Task id [Long] Step id [Long] Step Class [String] Step Description [String] Exception [String]

Explanation An error occured while executing the specified step

Recommended Action Verify and update the application and if problem persist contact Cisco technical assistance center

Error Message
MIVR-APP_MGR- 3 -UNABLE_INIT_APP : Unable to initialize application. Application [String] Type [String] Exception [String]

Explanation The application manager could not initialize the specified application of the specified type

Recommended Action Verify and update the configuration

Error Message
MIVR-APP_MGR- 4 -UNABLE_INVOKE_DFLT_TASK : Unable to invoke default application task. Application [String] Task id [Long] Exception [String]

Explanation The application manager could not invoke the default task for the specified application using the engine; and is falling back to using an internal thread to invoke the task

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-APP_MGR- 3 -TASK_DUPLICATE_CHANNEL_ERROR : Duplicate channel error. Application [String] Application Trigger [String] Task id [Long] Exception [String]

Explanation Attempting to add a duplicate channel to the task

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-APP_MGR- 1 -TASK_CLEANING_FAILURE : Failure to clean application task. Application [String] Task id [Long] Exception [String]

Explanation An error occured while cleaning up the task associated with a given application; as a result, channels and application sessions might be lost which would reduce the capacity of the system

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-APP_MGR- 3 -INCOMPATIBLE_VAR_TYPES : Incompatible variable types. Application [String] Script [String] Variable [String] Default variable type defined [String] Variable type defined [String] Exception [String]

Explanation A variable type is incompatible with the variable defined in the default script

Recommended Action Verify and update the configuration

Error Message
MIVR-APP_MGR- 3 -UNABLE_CREATE_SYS_TASK : Unable to create system default application task. Application [String] Application Trigger [String] Exception [String]

Explanation The application manager could not create a system default task for the specified application

Recommended Action Verify and update the configuration

Error Message
MIVR-APP_MGR- 5 -MGR_SHUTTING_DOWN : Application Manager shutting down.

Explanation The Application Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-APP_MGR- 4 -DETECTION_ERROR : Unexpected error in deadlock detection thread. Exception [String]

Explanation The deadlock detection thread detected and unexpected error

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-APP_MGR- 6 -DEADLOCK_AVOIDED : Potential deadlock avoided. Application [String] Task id [Long] Thread [String] Info [String]

Explanation Potential deadlock avoided for the specified application task and thread

Recommended Action No actions needed

Error Message
MIVR-APP_MGR- 3 -UNABLE_LOAD_APP : Unable to load application configuration. Application [String] Exception [String]

Explanation The application manager could not load the configuration for the specified application

Recommended Action Verify and update the configuration

Error Message
MIVR-APP_MGR- 6 -ABORTING_CONTACT : Aborting contact. Application [String] Task id [Long] Contact id [Int] Contact implementation id [String] Contact Class [String] Contact Type [String] Exception [String]

Explanation The specified contact is being aborted because the task is no longer active

Recommended Action Verify and update the application

Error Message
MIVR-APP_MGR- 3 -RMI_REBIND_FAILED : Unable to register remote interface. Exception [String]

Explanation A remote interface could not be binded to the RMI registry; remote access for dynamic update or other functions will not be available

Recommended Action Verify the RMI configuration and restart server

Error Message
MIVR-APP_MGR- 3 -MISSING_CHANNEL : Missing channel. Channel Class [String] Contact id [Int] Contact implementation id [String] Contact Class [String] Contact Type [String] Exception [String]

Explanation A channel of the specified class is not available with the given contact

Recommended Action Verify and update the application

Error Message
MIVR-APP_MGR- 2 -CONVERGENCE_INIT_FAILED : Unable to initialize convergence listener. Exception [String]

Explanation Could not initialize the convergence listener required to process manual fail over requests

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-APP_MGR- 2 -DEADLOCK_DETECTED : Potential deadlock detected. Application [String] Task id [Long] Thread [String] Info [String]

Explanation Potential deadlock detected for the specified application task and thread

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-APP_MGR- 3 -REMOTE_DEBUG_INIT_FAILED : Unable to initialize remote debugging. Exception [String]

Explanation The remote debugging could not be initialized; remote debugging of IVR Cisco Scripts will not be available

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-APP_MGR- 3 -INVALID_TASK_STATE_ERROR : Some action is performed when a task is in invalid state. Application [String] Task id [Long] Exception [String]

Explanation Some action is performed when a task is in invalid state, such as creating a new contact, etc.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-APP_MGR- 2 -ABORTING_CONTACT_FAILURE : Aborting contact failure. Application [String] Task id [Long] Contact id [Int] Contact implementation id [String] Contact Class [String] Contact Type [String] Exception [String]

Explanation An error occured while aborting the specified contact

Recommended Action Verify and update the application

Error Message
MIVR-APP_MGR- 5 -MGR_SHUTDOWN : Application Manager in shutdown.

Explanation The Application Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-APP_MGR- 1 -SCRIPT_LOAD_ERROR : Failed to load script. Script [String] Exception [String]

Explanation The specified script failed to be loaded in memory

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-APP_MGR- 2 -TERMINATING_CONTACT_FAILURE : Failure to terminate contact. Application [String] Task id [Long] Contact id [Int] Contact implementation id [String] Contact Class [String] Contact Type [String] Exception [String]

Explanation An error occured while terminating the specified contact

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-APP_MGR- 6 -APP_DISABLED : Application disabled. Application [String] Exception [String]

Explanation The specified application was disabled

Recommended Action No actions needed

Error Message
MIVR-APP_MGR- 3 -DFLT_TASK_ABORTED : Default application task aborted. Application [String] Application Trigger [String] Task id [Long] Task Class [String] Exception [String]

Explanation A default application task was aborted

Recommended Action Verify and update the application and if problem persist contact Cisco technical assistance center

Error Message
MIVR-APP_MGR- 6 -APP_LOADED : Application loaded. Application [String]

Explanation The specified application was loaded in memory

Recommended Action No actions needed

Error Message
MIVR-APP_MGR- 6 -TASK_INTERRUPTED : Application task was interrupted. Application [String] Task id [Long] Interruption [String]

Explanation An application task was interrupted

Recommended Action No actions needed

Error Message
MIVR-APP_MGR- 3 -UNABLE_CREATE_DFLT_TASK : Unable to create default application task. Application [String] Application Trigger [String] Exception [String]

Explanation The application manager could not create a default task for the specified application

Recommended Action Verify and update the configuration

Error Message
MIVR-BOOTSTRAP_MGR- 1 -MGR_PARTIAL_SERVICE : Bootstrap Manager in partial service.

Explanation The Bootstrap Manager is in partial service

Recommended Action Investigate as required

Error Message
MIVR-BOOTSTRAP_MGR- 3 -BOOTSTRAP_NODE_JOIN_ERROR : Failed to sync bootstrap repository during node join. A description for the nature of the exception [String] Exception [String]

Explanation Failed to sync bootstrap repository during node join

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-BOOTSTRAP_MGR- 3 -BOOTSTRAP_SYNC_ERROR : Synchronize bootstrap repository error. A description for the nature of the exception [String] Exception [String]

Explanation Failed to synchronize the bootstrap repository between nodes

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-BOOTSTRAP_MGR- 3 -BOOTSTRAP_REMOVE_LISTENER_ERROR : Failed to remove the BootstrapListener. A description for the nature of the exception [String] Exception [String]

Explanation Failed to remove the BootstrapListener

Recommended Action Restart server

Error Message
MIVR-BOOTSTRAP_MGR- 6 -MGR_IN_SERVICE : Bootstrap Manager in service.

Explanation The Bootstrap Manager is in service

Recommended Action No actions needed

Error Message
MIVR-BOOTSTRAP_MGR- 3 -BOOTSTRAP_ADD_LISTENER_ERROR : Failed to add the BootstrapListener. A description for the nature of the exception [String] Exception [String]

Explanation Failed to add the BootstrapListener

Recommended Action Restart server

Error Message
MIVR-BOOTSTRAP_MGR- 3 -BOOTSTRAP_INIT_ERROR : Bootstrap Manager initialization error. A description for the nature of the exception [String] Exception [String]

Explanation The Bootstrap Manager has failed on initialzation

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-BOOTSTRAP_MGR- 5 -MGR_SHUTDOWN : Bootstrap Manager in shutdown.

Explanation The Bootstrap Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-BOOTSTRAP_MGR- 3 -BOOTSTRAP_NODE_REMOVE_ERROR : Bootstrap failed to remove node from cluster profile. A description for the nature of the exception [String] Exception [String]

Explanation Bootstrap failed to remove node from cluster profile

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-BOOTSTRAP_MGR- 6 -MGR_INITIALIZING : Bootstrap Manager initializing.

Explanation The Bootstrap Manager is initializing

Recommended Action No actions needed

Error Message
MIVR-BOOTSTRAP_MGR- 2 -MGR_OUT_OF_SERVICE : Bootstrap Manager in out of service.

Explanation The Bootstrap Manager is out of service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-BOOTSTRAP_MGR- 5 -MGR_SHUTTING_DOWN : Bootstrap Manager shutting down.

Explanation The Bootstrap Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-BOOTSTRAP_MGR- 3 -BOOTSTRAP_NODE_ADD_ERROR : Bootstrap failed to add new node to cluster profile. A description for the nature of the exception [String] Exception [String]

Explanation Bootstrap failed to add new node to cluster profile

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CFG_MGR- 3 -REPOSITORY_ACCESSOR_INIT_ERROR : Failed to initialize the accessor. Name [String]

Explanation Error in initializing repository accessor

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 1 -MGR_PARTIAL_SERVICE : Config Manager in partial service. Reason [String]

Explanation The Config Manager is in partial service due to CDS not yet activated or failed to register RMI for notification

Recommended Action Please check whether CDS is activated in the clusteror CVD to regsiter RMI for notification

Error Message
MIVR-CFG_MGR- 3 -DB_ACCESS_ERROR : Database Access error. Action [String] Table [String] Exception [String]

Explanation Error while accessing Data Base

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 3 -BULK_UPDATE_ERROR : Error in Bulk update. action [String] Exception [String]

Explanation Error in bulk update

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 6 -STUB_HASCHANGED : ConfigStubImpl hasChanged(). Exception [String]

Explanation information

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 3 -SAVE_FAILED : saving failed . Exception [String]

Explanation ConfigObject saving failed

Recommended Action ConfigObject saving failed

Error Message
MIVR-CFG_MGR- 6 -CONFIG_SCHEMA_CHANGE : ConfigSchema change. Schema_Ver [String]

Explanation Change in ConfigSchema

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 3 -CLUSTER_INFO_PORT_SAVE_ERR : Error in updating Bootstrap ini file. value [String] Exception [String]

Explanation Error in updating Bootstrap ini file with RMI port

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 3 -CLUSTER_INFO_HOST_SAVE_ERR : Error in updating Bootstrap ini file. Exception [String]

Explanation Error in updating Bootstrap ini file with local host ip

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 3 -GET_ACCESSOR_ERR : Error in finding repository accessors. Name [String] Exception [String]

Explanation Error in finding repository accessors information

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 6 -SCHEMA_EXISTS : ConfigSchema Register failed. Exception [String]

Explanation information

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 6 -MGR_INITIALIZING : Config Manager initializing.

Explanation The Config Manager is initializing

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 5 -MGR_SHUTTING_DOWN : Config Manager shutting down.

Explanation The Config Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 2 -MGR_OUT_OF_SERVICE : Config Manager in out of service.

Explanation The Config Manager is out of service; configuration will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CFG_MGR- 6 -NO_BASERECORD : No base record.

Explanation No base record for this config object

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 3 -LOCAL_AND_REMOTE_PROPERTIES_HAVE_DIFFERENT_VERSIONS : Local and remote properties have different versions. Properties name [String] Remote properties version [String] Local properties version [String] Merge result [String]

Explanation The properties being merged are of different versions

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CFG_MGR- 3 -CONFIG_SCHEMAS_LOAD_ERROR : Interrupted while loading configschemas. Name [String] Exception [String]

Explanation Error in loading config schemas

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 3 -READ_REAPOSIOTRY_ACCCESSORS : Error in reading repository accessors from applciation properties. Name [String] Exception [String]

Explanation Error in reading repository accessors information from applciation properties

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 6 -MGR_IN_SERVICE : Config Manager in service.

Explanation The Config Manager is in service

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 3 -CONFIG_MGR_GET_REMOTEPROP_ERROR : Config Manager get remote properties failed. Properties name [String] Exception [String]

Explanation Config Manager get remote properties failed

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CFG_MGR- 3 -CONFIG_OBJECT_SAVE_FAIL : saving failed due to missing values for keys defined in configSchema. configObejct [String] Reason [String] Exception [String]

Explanation saving failed due to missing values for keys defined in configSchema

Recommended Action Check the values for keys defined in the configSchema

Error Message
MIVR-CFG_MGR- 5 -MGR_SHUTDOWN : Config Manager in shutdown.

Explanation The Config Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 3 -PARSE_ERROR : Error in converiting data. ToBeParsed [String] Table [String] Exception [String]

Explanation Error in parsing

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 3 -PROFILE_INFO_ACCESS_ERR : Error in accessing profile ini file. Exception [String]

Explanation Error in accessing profile ini file

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 2 -CFG_MGR_INSTANCE_NULL : Config Manager instance is null.

Explanation The Config Manager instance is null; configuration will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CFG_MGR- 3 -CLUSTER_DOWN_ERROR : Cluster Manager is not initialized. Description [String] Exception [String]

Explanation Cluster Manager is not initialized

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CFG_MGR- 3 -DELETE_ERROR : Delete failed. Exception [String]

Explanation ConfigObjects deletion for this query failed

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 3 -INVALID_REPOSITORY_ACCESSOR : Repository accessor is invalid. Exception [String]

Explanation Repository accessor is invalid

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 3 -READ_ERROR : object read error. Exception [String]

Explanation Error in reading

Recommended Action Error in reading

Error Message
MIVR-CFG_MGR- 3 -CONFIG_OBJECT_CORRUPTED : Error while reading config. Probably it was corrupt. Config Class [String] Exception [String]

Explanation Error while reading the blob data of the config

Recommended Action Run the CLI command 'show uccx tech dbserver integrity' to check and recover from any corrupted config objects

Error Message
MIVR-CFG_MGR- 3 -CONFIG_MGR_GENERAL_ERROR : Config Manager has exception. Error message [String] Exception [String]

Explanation Config Manager has exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CFG_MGR- 3 -CLUSTER_RMI_REBIND_FAILED : Unable to register remote interface in cluster space. Exception [String]

Explanation A remote interface could not be binded to the cluster space; Config data may not be accessible form Editor

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CFG_MGR- 6 -NO_DB_RECORD : No record in DB.

Explanation No record in DB

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 3 -NOTIFICATION_ERROR : Failed to notify other remote config managers. Action [String] Exception [String]

Explanation Error in notifying other remote config managers

Recommended Action No actions needed

Error Message
MIVR-CFG_MGR- 2 -CONFIG_MGR_OUT_OF_SERVICE : Config Manager in out of service. Exception [String]

Explanation The Config Manager is out of service; configuration will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CHANNEL_MGR- 1 -MGR_PARTIAL_SERVICE : Channel Manager in partial service.

Explanation The Channel Manager is in partial service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CHANNEL_MGR- 3 -ADD_CHANNEL_WITH_DIFFCLASS_FAILED : Unable to add a channel of different class. Group [String] Group Channel Class [String] Group Channel Type [String] Group id [Int] Group implementation id [String] Channel Class [String]

Explanation Cannot add a channel to a group with different channel class

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CHANNEL_MGR- 6 -NO_GROUPS_PROVIDED : No Groups provided in getIdleChannels.

Explanation All groups provided in getIdleChannels() are null

Recommended Action No actions needed

Error Message
MIVR-CHANNEL_MGR- 3 -CREATESTATE_EXCEPTION : Unhandled exception while creating a state. Channel [String] Channel Class [String] Channel Type [String] Channel id [Int] Channel implementation id [String] Exception [String]

Explanation The channel implementation has thrown an exception in the createState() method

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CHANNEL_MGR- 3 -NO_GROUPID_AVAILABLE : No Unique Group ID is available. Group Channel Class [String] Group Channel Type [String] Group id [Int]

Explanation The number of groups has reached the maximum limit and a unique id is not available

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CHANNEL_MGR- 3 -INVALID_GROUP_ID : Invalid Group ID. Group Channel Class [String] Group Channel Type [String] Group id [Int]

Explanation The Group ID specified is invalid. Valid range 0 to 65535

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CHANNEL_MGR- 3 -ASYNC_RELEASE_EXCEPTION : Unhandled exception while releasing a permit. Channel [String] Channel Class [String] Channel Type [String] Channel id [Int] Channel implementation id [String] Permit [String] Semaphore [String] Exception [String]

Explanation The channel implementation has thrown an exception in the Async.release() method

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CHANNEL_MGR- 3 -ADD_CHANNEL_WITH_DIFFTYPE_FAILED : Unable to add a channel of different type. Group [String] Group Channel Class [String] Group Channel Type [String] Group id [Int] Group implementation id [String] Channel Type [String]

Explanation Cannot add a channel to a group with different type

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CHANNEL_MGR- 6 -MGR_INITIALIZING : Channel Manager initializing.

Explanation The Channel Manager is initializing

Recommended Action No actions needed

Error Message
MIVR-CHANNEL_MGR- 5 -MGR_SHUTTING_DOWN : Channel Manager shutting down.

Explanation The Channel Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-CHANNEL_MGR- 2 -MGR_OUT_OF_SERVICE : Channel Manager in out of service.

Explanation The Channel Manager is out of service; channel management will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CHANNEL_MGR- 3 -GROUP_CREATION_ERROR : Group creation error. Group Channel Class [String] Group Channel Type [String] Group id [Int]

Explanation A Group with the given id already exists

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CHANNEL_MGR- 3 -CHANNEL_CREATION_ERROR : Channel creation error. Group Channel Class [String] Group Channel Type [String] Group id [Int] Group implementation id [String] Exception [String]

Explanation Error occured while attempting to create a dynamic channel

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CHANNEL_MGR- 3 -CREATED_INCORRECT_STATE : Channel impl created an incorrect state. Channel [String] Channel Class [String] Channel Type [String] Channel id [Int] Channel implementation id [String] Expected state [String] Incorrect state [String]

Explanation The channel implementation created an incorrect state object

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CHANNEL_MGR- 3 -ADD_CHANNEL_WITH_INVALIDID_FAILED : Unable to add a channel with invalid id. Group [String] Group Channel Class [String] Group Channel Type [String] Group id [Int] Group implementation id [String] Channel id [Int]

Explanation Cannot add a channel to a group with invalid id. Valid range 0 to 65535

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CHANNEL_MGR- 6 -MGR_IN_SERVICE : Channel Manager in service.

Explanation The Channel Manager is in service

Recommended Action No actions needed

Error Message
MIVR-CHANNEL_MGR- 3 -ABORT_EXCEPTION : Unhandled exception while aborting a channel. Channel [String] Channel Class [String] Channel Type [String] Channel id [Int] Channel implementation id [String] Exception [String]

Explanation The channel implementation has thrown an exception in the abort() method

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CHANNEL_MGR- 6 -GROUP_CREATED : Group created successfully. Group Channel Class [String] Group Channel Type [String] Group id [Int]

Explanation A Group was successfully created

Recommended Action No actions needed

Error Message
MIVR-CHANNEL_MGR- 5 -MGR_SHUTDOWN : Channel Manager in shutdown.

Explanation The Channel Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-CHANNEL_MGR- 3 -ADD_CHANNEL_WITH_DISPOSEDSTATE_FAILED : Unable to add a disposed channel. Group [String] Group Channel Class [String] Group Channel Type [String] Group id [Int] Group implementation id [String] Channel [String]

Explanation Cannot add a channel that is already disposed

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CHANNEL_MGR- 3 -ADD_CHANNEL_WITH_PRVGROUP_FAILED : Unable to add channel belonging to another group. Group [String] Group Channel Class [String] Group Channel Type [String] Group id [Int] Group implementation id [String] Channel [String] Previous Group id [Int]

Explanation Cannot add a channel that belongs to another group

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CHANNEL_MGR- 3 -INIT_EXCEPTION : Unhandled exception while initializing a channel. Channel [String] Channel Class [String] Channel Type [String] Channel id [Int] Channel implementation id [String] Exception [String]

Explanation The channel implementation has thrown an exception in the init() method

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CHANNEL_MGR- 6 -INVALID_OP_DISPOSED_GROUP : Trying to operate on a disposed group. Group [String] Group Channel Class [String] Group Channel Type [String] Group id [Int] Group implementation id [String] Invalid operation [String]

Explanation The operation acts on a group that is disposed

Recommended Action No actions needed

Error Message
MIVR-CHANNEL_MGR- 6 -INVALID_OP_DISPOSED_CHANNEL : Trying to operate on a disposed channel. Channel [String] Channel Class [String] Channel Type [String] Channel id [Int] Channel implementation id [String] Invalid operation [String]

Explanation The operation acts on a channel that is disposed

Recommended Action No actions needed

Error Message
MIVR-CLUSTER_MGR- 3 -MANAGER_INITIALIZING_ERROR : Cluster Manager is not initialized. Exception [String]

Explanation Cluster Manager is not initialized

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CLUSTER_MGR- 4 -REMOTE_EXCEPTION_1 : Can not communicate with CVD. errCnt [Int] Cmd [String] Exception [String]

Explanation Cluster Manager can not communicate with CVD on the local node

Recommended Action No actions needed

Error Message
MIVR-CLUSTER_MGR- 3 -REMOTE_EXCEPTION_2 : Can not communicate with CVD. errCnt [Int] Exception [String]

Explanation Cluster Manager can not communicate with CVD on the local node

Recommended Action No actions needed

Error Message
MIVR-CLUSTER_MGR- 3 -LICENSE_OBSERVER_ERROR : Cluster Manager can not register license observer. Exception [String]

Explanation Cluster Manager can not register license observer

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CLUSTER_MGR- 2 -RESTART_REQUESTED : Cluster Manager requests to restart process. reason [String]

Explanation Cluster Manager detects some problem that prevents its functionality, and requests restart

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CLUSTER_MGR- 3 -COMPONENT_PRIMARY_CHANGED_ERROR : Component change primary, but it is not supported. type [String] nodeId [Int]

Explanation Component change primary, but it is not supported

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CLUSTER_MGR- 3 -COMPONENT_CLEAR_PRIMARY_NOT_SUPPORTED : Clear Primary operation is not supported for the Component. type [String] nodeId [Int]

Explanation Clear Primary operation is not supported for the Component

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CLUSTER_MGR- 6 -MANAGER_INITIALIZING_COMPLETED : Cluster Manager initialization successfully completed.

Explanation Cluster Manager initialization successfully completed

Recommended Action No actions needed

Error Message
MIVR-CLUSTER_MGR- 3 -READ_ERROR_CLUSTER_NAME : Cannot read cluster name. Exception [String]

Explanation Cannot read cluster name from ccndir.ini

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CLUSTER_MGR- 3 -GET_PUBLISHER_TIMEOUT_ERROR : Cluster Manager can not get Timeout value from Windows Registry. Exception [String]

Explanation Cluster Manager can not get Timeout value from Windows Registry. Use default timeout: 2 hours

Recommended Action No actions needed

Error Message
MIVR-CLUSTER_MGR- 3 -MASTER_SERVICE_NOT_FOUND : Master service not found. UniqueId [Int] nodeId [Int] Cmd [String]

Explanation Master service not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CLUSTER_MGR- 3 -ILLEGAL_CLUSTER_NAME : Cluster name is illegal. name [String]

Explanation Cluster name is illegal

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CLUSTER_MGR- 3 -CONVERGENCE_NOT_FOUND_ERROR : Convergence not found. name [String]

Explanation Convergence not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CLUSTER_MGR- 3 -GET_NODE_UPDATE_ERRORR : Can not communicate with CVD. Exception [String]

Explanation Cluster Manager can not communicate with CVD on the local node

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CLUSTER_MGR- 3 -NODE_NOT_FOUND_FOR_CMD : Cluster Manager dispatcher can not process cmd: unknown Node. Cmd [String]

Explanation Cluster Manager dispatcher can not process cmd: unknown Node

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CLUSTER_MGR- 4 -COMPONENT_ALREADY_PRIMARY : Component is already primary. type [String] nodeId [Int]

Explanation Component is already primary

Recommended Action No actions needed

Error Message
MIVR-CLUSTER_MGR- 4 -MASTER_UPDATE_ERROR : Cluster Manager can not update master. nodeId [Int] Cmd [String]

Explanation Cluster Manager can not update master, it try to re-sync all states with CVD on the local Node

Recommended Action No actions needed

Error Message
MIVR-CLUSTER_MGR- 3 -SET_VMOPTION_ERROR : Cluster Manager can not execute SetVMOption. Exception [String]

Explanation Cluster Manager can not execute SetVMOption

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CLUSTER_MGR- 3 -SERVICE_ID_NOT_FOUND_ERROR : Service not found. UniqueId [Int] nodeId [Int] Cmd [String]

Explanation Service not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CLUSTER_MGR- 3 -COMPONENT_CLEAR_PRIMARY_ERROR : Clear Primary operation is not applicable to non-primary Component. type [String] nodeId [Int]

Explanation Clear Primary operation is not applicable to non-primary Component

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CLUSTER_MGR- 3 -NODE_UPDATE_ERROR : Cluster Manager can not update node from command. nodeId [Int] Cmd [String]

Explanation Cluster Manager can not update node from command

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CLUSTER_MGR- 3 -COMPONENT_ID_NOT_FOUND_ERROR : Component not found. UniqueId [Int] nodeId [Int] Cmd [String]

Explanation Component not found

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CLUSTER_MGR- 3 -REMOTE_NOTIFY_1 : Can not communicate with CVD. Context [String] Cmd [String] Exception [String]

Explanation Cluster Manager can not communicate with CVD on the local node

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CLUSTER_MGR- 6 -COMPONENT_PRIMARY_REMOVED : Component is removed, but it is primary. type [String] nodeId [Int]

Explanation Component is removed, but it is primary

Recommended Action No actions needed

Error Message
MIVR-CLUSTER_MGR- 3 -CLUSTER_SNAPSHOT_ON_ERROR : Cluster snapshot when error. cluster [String]

Explanation Cluster snapshot when error

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CLUSTER_MGR- 3 -READ_CLUSTER_ERROR : Cluster Manager can not read Cluster data from ClusterSnapshotCmdImpl. Exception [String]

Explanation Cluster Manager can not read Cluster data from ClusterSnapshotCmdImpl

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CLUSTER_MGR- 3 -COMPONENT_SET_PRIMARY_NOT_SUPPORTED : Set Primary operation is not supported for the Component. type [String] nodeId [Int]

Explanation Set Primary operation is not supported for the Component

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CLUSTER_MGR- 3 -NODE_READ_ERROR : Cluster Manager can not read node from command. Cmd [String] Exception [String]

Explanation Cluster Manager can not read node from command

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CLUSTER_MGR- 0 -JMS_BROKER_SERVICE_START_ERROR : A KeepAlive exception has been thrown in Manager Manager. Exception [String]

Explanation Due to JMS service start failure a KeepAlive exception has been thrown in Cluster Manager

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CLUSTER_MGR- 2 -MASTER_ELECTION_ERROR : Master Election Error - too many masters. Context [String] name [String] nodeId [Int] otherNodeId [Int] reason [String]

Explanation Master Election Error - too many masters. Cluster Manager restart process

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CLUSTER_MGR- 3 -MEMORY_DUMP_ERROR : Cluster Manager can not execute Memory Dump. Exception [String]

Explanation Cluster Manager can not execute Memory Dump

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CLUSTER_MGR- 3 -SEMAPHORE_NOT_FOUND_ERROR : Cluster Manager can not find semaphore. Cmd [String]

Explanation Cluster Manager can not find semaphore

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CLUSTER_MGR- 4 -NODE_INVALID : Node Is invalid. nodeId [Int] reason [String]

Explanation Node Is invalid, it should be recovered from Installer

Recommended Action Reinstall server

Error Message
MIVR-CLUSTER_MGR- 3 -NODE_SYNCHRONIZE_STATE_ERROR : Cluster Manager can not synchronize state for node. nodeId [Int]

Explanation Cluster Manager can not synchronize state for node, and will be restarted.

Recommended Action No actions needed

Error Message
MIVR-CLUSTER_MGR- 3 -ACCESS_CONFIG_DATA_ERROR : Cluster Manager can not access configuration data. Exception [String]

Explanation Cluster Manager can not access configuration data

Recommended Action Verify that Configuration data is available. If problem persist contact Cisco technical assistance center

Error Message
MIVR-CLUSTER_MGR- 4 -DYNAMIC_LICENSE_NOT_DEFINED : Dynamic license is not defined.

Explanation Dynamic license is not defined

Recommended Action No actions needed

Error Message
MIVR-CLUSTER_MGR- 2 -THROWS_KEEP_ALIVE_EXCEPTION : Cluster Manager throws KeepAlive Exception. Exception [String]

Explanation Cluster Manager detects some problem that prevents its functionality, and will be restarted

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CLUSTER_MGR- 3 -MANAGER_DISPATCH_ERROR : Can not process command. Cmd [String] Exception [String]

Explanation Cluster Manager can not process command from CVD

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CONTACT_MGR- 3 -CONTACT_ADD_CHANNEL_ERROR : Could not add a channel to a contact. Contact [String] Contact Class [String] Contact Type [String] Contact id [Int] Contact implementation id [String] Exception [String]

Explanation An error occured while attempting to associate a channel to a contact

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CONTACT_MGR- 1 -MGR_PARTIAL_SERVICE : Contact Manager in partial service.

Explanation The Contact Manager is in partial service; potential deadlocks were detected

Recommended Action Investigate as required

Error Message
MIVR-CONTACT_MGR- 2 -DEADLOCK_DETECTED : Potential deadlock detected. Contact id [Int] Contact implementation id [String] Contact Class [String] Contact Type [String] Deadlocked object [String]

Explanation Potential deadlock detected on the specified contact for the specified object

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CONTACT_MGR- 6 -MGR_IN_SERVICE : Contact Manager in service.

Explanation The Contact Manager is in service

Recommended Action No actions needed

Error Message
MIVR-CONTACT_MGR- 3 -RE_ENTRANT_ERROR : Re-entrancy error. Contact [String] Contact Class [String] Contact Type [String] Contact id [Int] Contact implementation id [String] Exception [String]

Explanation Unsupported re-entrancy detected for a Contact object

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CONTACT_MGR- 3 -INITIALIZATION_ERROR : Contact Manager initialization error. Exception [String]

Explanation Error occured during the initialization of the contact manager

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CONTACT_MGR- 5 -MGR_SHUTDOWN : Contact Manager in shutdown.

Explanation The Contact Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-CONTACT_MGR- 3 -CONTACT_CREATE_EVENT_ERROR : Error when create contact event. Contact [String] Contact Class [String] Contact Type [String] Contact id [Int] Contact implementation id [String] Exception [String]

Explanation There is an error when create contact event or subsystem specific event

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CONTACT_MGR- 1 -DEADLOCK_COUNT_EXCEEDED : Deadlock count exceeded. Deadlock info [String]

Explanation Deadlock count exceeded

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CONTACT_MGR- 3 -CONTACT_DUPLICATE_CHANNEL_ERROR : Duplicate channel for a contact. Contact [String] Contact Class [String] Contact Type [String] Contact id [Int] Contact implementation id [String] Exception [String]

Explanation More than one channel of a specific type associated with a contact

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CONTACT_MGR- 3 -CONTACT_REMOVE_CHANNEL_ERROR : Could not remove a channel from a contact. Contact [String] Contact Class [String] Contact Type [String] Contact id [Int] Contact implementation id [String] Exception [String]

Explanation An error occured while attempting to remove a channel from a contact

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CONTACT_MGR- 3 -CONTACT_CREATE_STATE_ERROR : Error when create contact state. Contact [String] Contact Class [String] Contact Type [String] Contact id [Int] Contact implementation id [String] Exception [String]

Explanation There is an error when create contact state

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CONTACT_MGR- 3 -CONTACT_RUN_INIT_ERROR : Error when run the contact initializer. Contact [String] Contact Class [String] Contact Type [String] Contact id [Int] Contact implementation id [String] Exception [String]

Explanation There is an error when running the contact initializer

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CONTACT_MGR- 3 -CONTACT_INVALID_STATE_ERROR : Some action is performed when contact is in invalid state. Contact [String] Contact Class [String] Contact Type [String] Contact id [Int] Contact implementation id [String] Exception [String]

Explanation Some action is performed when contact is in invalid state, such as marking the contact as handled when the contact is not in the Accepted state, etc.

Recommended Action Verify and update the application and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CONTACT_MGR- 6 -MGR_INITIALIZING : Contact Manager initializing.

Explanation The Contact Manager is initializing

Recommended Action No actions needed

Error Message
MIVR-CONTACT_MGR- 2 -MGR_OUT_OF_SERVICE : Contact Manager in out of service.

Explanation The Contact Manager is out of service; contact management will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CONTACT_MGR- 5 -MGR_SHUTTING_DOWN : Contact Manager shutting down.

Explanation The Contact Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-CONTACT_MGR- 4 -DETECTION_ERROR : Unexpected error in deadlock detection thread. Exception [String]

Explanation The deadlock detection thread detected and unexpected error

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-CONTACT_MGR- 3 -CONTACT_SETSTATE_ERROR : Could not change Contact state. Contact [String] Contact Class [String] Contact Type [String] Contact id [Int] Contact implementation id [String] Exception [String]

Explanation Could not change state for a Contact object

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CONTACT_MGR- 6 -DEADLOCK_AVOIDED : Potential deadlock avoided. Contact id [Int] Contact implementation id [String] Contact Class [String] Contact Type [String] Deadlocked object [String]

Explanation Potential deadlock avoided on the specified contact for the specified object

Recommended Action No actions needed

Error Message
MIVR-CONTACT_MGR- 3 -CONTACT_CREATION_ERROR : Contact creation error. Contact Type [String] Contact id [Int] Contact implementation id [String] Exception [String]

Explanation Error occured during an outbound contact creation

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CRA_CMM- 6 -CMM_START_ACTIVE : CRS active.

Explanation Starting as active CRS Server

Recommended Action No actions needed

Error Message
MIVR-CRA_CMM- 6 -CMM_INIT : CMM initialized.

Explanation The ClusterMsgMgr is initialized

Recommended Action No actions needed

Error Message
MIVR-CRA_CMM- 6 -CMM_START_STANDBY : CRS standby.

Explanation Starting as standby CRS Server

Recommended Action No actions needed

Error Message
MIVR-CRA_CMM- 6 -CMM_DESTROY : CMM stopped.

Explanation The ClusterMsgMgr is stopped

Recommended Action No actions needed

Error Message
MIVR-CRA_CMM- 6 -CMM_GOING_STANDBY : CRS going standby.

Explanation CRS Server goes from active to standby

Recommended Action No actions needed

Error Message
MIVR-CRA_CMM- 6 -CMM_GOING_ACTIVE : CRS going active.

Explanation CRS Server goes from standby to active

Recommended Action No actions needed

Error Message
MIVR-CRA_HRDM- 6 -STARTING_TO_REPAIR_DB : Going online, starting to repair DB.

Explanation Going online, starting to repair DB

Recommended Action No actions needed

Error Message
MIVR-CRA_HRDM- 6 -HRDM_INIT : HRDM initialized.

Explanation The Historical Reporting Data Manager is initialized

Recommended Action No actions needed

Error Message
MIVR-CRA_HRDM- 3 -DB_RECORD_INVALID_FIELD : Invalid field in record. Record Type [String] Invalid Field [String] A description of the error [String]

Explanation Invalid field in record

Recommended Action Invalid field in record

Error Message
MIVR-CRA_HRDM- 6 -HRDM_DBWRITER_STOP : HR Data Writer stopped.

Explanation The Historical Reporting Data Writer was stopped

Recommended Action No actions needed

Error Message
MIVR-CRA_HRDM- 3 -HRDM_DBWRITING_ERROR : Error on Database Writing. Record [String] A description of the error [String]

Explanation While writing Historical Reporting Data into Database, Exception occured

Recommended Action Contact the System Administrator to Check the Database

Error Message
MIVR-CRA_HRDM- 3 -HRDM_EXCEPTION : An exception has been caught by the HRDM. A description for the nature of the exception [String]

Explanation An exception has been caught by the HRDM

Recommended Action An exception has been caught by the HRDM

Error Message
MIVR-CRA_HRDM- 3 -HRDM_DBWRITING_FAILED : Database writing Faliure. Record [String] A description of the error [String]

Explanation Writing Historical Reporting Data into Database failed

Recommended Action Contact the System Administrator to Check the Database

Error Message
MIVR-CRA_HRDM- 4 -CRDR_TABLE_ERROR : Linkedlist should not be null. ContactID [Int] Sequence Number [Int]

Explanation Linkedlist should not be null

Recommended Action Linkedlist should not be null

Error Message
MIVR-CRA_HRDM- 6 -HRDM_STOP : HRDM stopped.

Explanation The Historical Reporting Data Manager is stopped

Recommended Action No actions needed

Error Message
MIVR-CRA_HRDM- 3 -HRDM_INVALID_RECORD : Invalid Record. Record Type [String]

Explanation Historical Reporting Data is not written into DB due to unrecognized record type

Recommended Action Contact the System Administrator

Error Message
MIVR-CRA_HRDM- 3 -HRDM_ERROR : An error occurred in the HRDM. A description of the error [String]

Explanation An error occurred in the HRDM

Recommended Action An error occurred in the HRDM

Error Message
MIVR-CRA_HRDM- 1 -DB_RECORD_WRITER_ERROR : Did not get handle to the Database Record Writer. A description of the error [String]

Explanation Please contact System Administrator and verify that the Database Schema is correct

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-CRA_HRDM- 6 -DONE_REPAIRING_DB : Done repairing DB.

Explanation Done repairing DB

Recommended Action No actions needed

Error Message
MIVR-DB_MGR- 1 -MGR_PARTIAL_SERVICE : Database Manager in partial service.

Explanation The Database Manager is in partial service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-DB_MGR- 6 -DATASOURCE_STATE : state change. change [String]

Explanation state change

Recommended Action No actions needed

Error Message
MIVR-DB_MGR- 6 -MGR_IN_SERVICE : Database Manager in service.

Explanation The Database Manager is in service

Recommended Action No actions needed

Error Message
MIVR-DB_MGR- 5 -MGR_SHUTDOWN : Database Manager in shutdown.

Explanation The Database Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-DB_MGR- 3 -DATASOURCE_INIT_ERROR : Failed to db server. Type [String] Exception [String]

Explanation Failed to initialize the db server

Recommended Action Please check db server

Error Message
MIVR-DB_MGR- 3 -UPDATE_CLUSTERDEPENDENTCONFIG_FAILED : Failed to update DBVersion in ClusterDependentConfig . Exception [String]

Explanation Failed to update DBVersion in ClusterDependentConfig

Recommended Action No actions needed

Error Message
MIVR-DB_MGR- 3 -DS_PRIMARY_READ_ERROR : Failed to read Datasource primary. Type [String] Exception [String]

Explanation Failed to read Datasource primary from cluster profile

Recommended Action Please check cluser profile info

Error Message
MIVR-DB_MGR- 3 -CREATE_SERVICE_CONVERGENCE_FAILED : Failed to create convergence service . Name [String]

Explanation Failed to create convergence service

Recommended Action Please check cluster manager

Error Message
MIVR-DB_MGR- 3 -SQL_PROPERTIES_READ_ERR : Error in reading SQL properties from cluster info. Exception [String]

Explanation Error in reading SQL properties such as SQL instance name , port

Recommended Action Check DB components are configured

Error Message
MIVR-DB_MGR- 6 -MGR_INITIALIZING : Database Manager initializing.

Explanation The Database Manager is initializing

Recommended Action No actions needed

Error Message
MIVR-DB_MGR- 2 -MGR_OUT_OF_SERVICE : Database Manager in out of service.

Explanation The Database Manager is out of service;

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-DB_MGR- 5 -MGR_SHUTTING_DOWN : Database Manager shutting down.

Explanation The Database Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-DB_MGR- 6 -NO_CLUSTER_MGR : No cluster Manager.

Explanation There is no cluster Manager running

Recommended Action No actions needed

Error Message
MIVR-DB_MGR- 3 -ERROR_JDBC_DRVER_LOAD : Error in loading jTDS Driver. Exception [String]

Explanation Error in loading jTDS Driver

Recommended Action Check whether driver is avaialble

Error Message
MIVR-DOC_MGR- 1 -UNAUTHORISED_ACCESS : Unauthorised access. Name [String] Exception [String]

Explanation The Document Manager found that requested resource is not a legitimate one

Recommended Action Investigate as required

Error Message
MIVR-DOC_MGR- 1 -MGR_PARTIAL_SERVICE : Document Manager in partial service.

Explanation The Document Manager is in partial service; synchronization of files with document repository is in progress

Recommended Action No actions needed

Error Message
MIVR-DOC_MGR- 3 -UNABLE_LOAD_USER_DOC : Unable to load the user document file. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to load the specified user document file

Recommended Action Verify and update the configuration

Error Message
MIVR-DOC_MGR- 6 -MGR_IN_SERVICE : Document Manager in service.

Explanation The Document Manager is in service

Recommended Action No actions needed

Error Message
MIVR-DOC_MGR- 2 -INVALID_USER_DIR : Invalid user document directory configured. Directory [String] Exception [String]

Explanation The configured user document directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-DOC_MGR- 2 -WEBAPP_INIT_FAILURE : Unable to initialize the specified web application. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to initialize the specified web applicaton; it will not be available to HTTP-triggered applications

Recommended Action Verify and update the configuration and restart server

Error Message
MIVR-DOC_MGR- 6 -NO_WEBAPPS_APPS : Webapps directory is empty.

Explanation No apps in the webapps directory of the repository to process

Recommended Action No actions needed

Error Message
MIVR-DOC_MGR- 6 -NO_WEBAPPS : Webapps directory not found.

Explanation No webapps directory in the repository to process

Recommended Action No actions needed

Error Message
MIVR-DOC_MGR- 3 -UNDEFINED_USER_DOC : Undefined user document. Name [String] Language [String] Exception [String]

Explanation A user document cannot be located

Recommended Action Verify and update the configuration

Error Message
MIVR-DOC_MGR- 5 -MGR_SHUTDOWN : Document Manager in shutdown.

Explanation The Document Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-DOC_MGR- 1 -WEBAPPS_MONITOR_FAILURE : Webapps directory monitoring failure. Exception [String]

Explanation The Document Manager can no longer monitor dynamic updates to the webapps directory of the repository; updates to war files will require restarting the local Unified CCX Engine Service

Recommended Action Investigate as required

Error Message
MIVR-DOC_MGR- 3 -DOC_FILE_SUPPORT_FAILURE : Document file support failure. Exception [String]

Explanation The Document Manager can not register file support for user document files; user documents will not be synchronized on local server

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-DOC_MGR- 3 -UNDEFINED_SYSTEM_DOC : Undefined system document. Name [String] Language [String] Exception [String]

Explanation A system document cannot be located

Recommended Action Verify and update the configuration

Error Message
MIVR-DOC_MGR- 3 -UNABLE_LOAD_SYSTEM_DOC : Unable to load the system document file. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to load the specified system document file

Recommended Action Verify and update the configuration

Error Message
MIVR-DOC_MGR- 2 -WAR_EXPAND_FAILURE : Unable to expand the specified war file. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to expand the specified war file; the corresponding web application will not be available to HTTP-triggered applications

Recommended Action Verify and update the configuration and restart server

Error Message
MIVR-DOC_MGR- 3 -WEBAPP_REMOVE_FAILURE : Unable to remove the specified web application. Name [String] Language [String] Exception [String]

Explanation The Document Manager is unable to remove the specified web applicaton

Recommended Action Verify and update the configuration and restart server

Error Message
MIVR-DOC_MGR- 6 -MGR_INITIALIZING : Document Manager initializing.

Explanation The Document Manager is initializing

Recommended Action No actions needed

Error Message
MIVR-DOC_MGR- 2 -MGR_OUT_OF_SERVICE : Document Manager in out of service.

Explanation The Document Manager is out of service; documents won't be accessible

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-DOC_MGR- 5 -MGR_SHUTTING_DOWN : Document Manager shutting down.

Explanation The Document Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-DOC_MGR- 3 -WEBSERVICES_ERROR : Exception thrown while processing web services for Document. Exception [String]

Explanation The Document Manager is unable to initialize the web services; external access to the document repository will not be possible andsupport for forwarding HTTP requests will also not be supported

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-DOC_MGR- 2 -INVALID_SYSTEM_DIR : Invalid system document directory configured. Directory [String] Exception [String]

Explanation The configured system document directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-DOCUMENT_STEPS- 3 -PARAMETER_CONTAINS_NULL_VALUE : Step parameter contains null value. Task ID [String] Local Variable [String] Step Name [String]

Explanation Step parameter contains NULL value

Recommended Action Validate the workflow script from the editor. If problem persist contact Cisco technical assistance center

Error Message
MIVR-DOCUMENT_STEPS- 3 -TEXT_SUBSTITUTION_STEP_UNDEFINED_ENCODING : Undefined Encoding of variable in Text Substitution Step. Task ID [String] Local Variable [String] Step Name [String] Encoding Type [String]

Explanation Text substitution step uses a template with unsupported encoding type

Recommended Action Check and validate the workflow script in the editor. Also verify the template.

Error Message
MIVR-DOCUMENT_STEPS- 3 -TEMPLATEDOCUMENT_CONTAINS_NULL_VALUE : Template document contains null value. Task ID [String] Template Document [String] Step Name [String]

Explanation Cannot access the Template document

Recommended Action Check the accessibility of the template document from the server

Error Message
MIVR-DOCUMENT_STEPS- 3 -TEMPLATEDOCUMENT_NOT_OF_CORRECT_TYPE : Template document not of type com.cisco.doc.Document. Task ID [String] Template Document [String] Step Name [String]

Explanation Template document is not Document Type

Recommended Action Check and validate the workflow script in the editor

Error Message
MIVR-ENG- 5 -ModuleStart : Module has successfully started. Module Name [String]

Explanation This notification signifies a module has started successfully and transitioned into the in-service state

Recommended Action No actions needed

Error Message
MIVR-ENG- 1 -ModuleStop : Module has stopped. Module Name [String] Module Failure Cause [Enum]

Explanation This notification signifies a module has stopped

Recommended Action Investigate as required

Module Failure Cause-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Other or Unspecified Failure
2 Graceful Shutdown
3 Heartbeat Failure
4 Initialization Failure
5 Out of Resource
6 Partial Failure
Error Message
MIVR-ENG- 3 -ModuleRunTimeFailure : Run-time Failure. Module Name [String] Module Run-time Failure Cause [Enum] Module Failure Name [String] Module Failure Message [String]

Explanation This notification signifies a run-time failure has occured

Recommended Action Investigate as required

Module Run-time Failure Cause-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Other or Unspecified Failure
2 Read Access Failure
3 Write Access Failure
4 Create Failure
5 Delete Failure
6 Update Failure
7 Init Failure
8 Load Failure
9 Out of Resource
10 Call Process Failure
11 Registration Failure
12 De-registration Failure
13 Connection Failure
14 Disconnection Failure
15 Unknown Target
16 Un-reacheable Target
Error Message
MIVR-ENG- 6 -SERVICE_STARTING : Service Starting. Module Name [String]

Explanation Module is up and running

Recommended Action No actions needed

Error Message
MIVR-ENG- 6 -SYSTEM_READY : System ready.

Explanation System is up and running

Recommended Action No actions needed

Error Message
MIVR-ENG- 6 -SERVICE_STOPPING : Service Stopping. Module Name [String]

Explanation Module is stopping

Recommended Action No actions needed

Error Message
MIVR-ENG- 4 -FAILURE_TO_READ_ENGINE_PROPERTIES_FILE : Failure to read Engine Properties file. Engine Properties File Name [String]

Explanation An error has occurred when reading the engine properties file

Recommended Action Check with the wfengine.properties file in the installed directory. If it is not here, please re-install the Application again or call your technical support

Error Message
MIVR-ENG- 4 -PROBLEM_IN_READING_LDAP_DIRECTORY : Problem in reading the LDAP Directory. Step Name [String]

Explanation An error has occurred when retrieving information from the directory service

Recommended Action Check with the directory service. Make sure that it is up and running. If not, please reset the directory service. Also, when resetting the directory service, please reset the Application Service. If problem still un-resolves, call your technical support

Error Message
MIVR-ENG- 3 -THREAD_CAUGHT_EXCEPTION : Unhandled exception caught in the given thread. Thread Name [String]

Explanation An exception has been caught

Recommended Action If problem persists, contact Cisco technical assistance center

Error Message
MIVR-ENG- 6 -ENGINE_SHUTDOWN_CALLED : Engine Shutdown called.

Explanation Engine has been shutted down

Recommended Action No actions needed

Error Message
MIVR-ENG- 6 -WORKFLOW_MANAGER_DESTROYED : Workflow Manager detroyed.

Explanation Workflow manager has been stopped

Recommended Action No actions needed

Error Message
MIVR-ENG- 6 -RMI_MANAGER_DESTROYED : RMI Manager detroyed.

Explanation RMI Manager has been stopped

Recommended Action No actions needed

Error Message
MIVR-ENG- 6 -TASK_MANAGER_DESTROYED : Task Manager detroyed.

Explanation Task Manager has been stopped

Recommended Action No actions needed

Error Message
MIVR-ENG- 6 -REALTIME_DATA_MANAGER_DESTROYED : Real Time Data Manager detroyed.

Explanation Real Time Data Manager has been stopped

Recommended Action No actions needed

Error Message
MIVR-ENG- 6 -HISTORICAL_REPORTING_MANAGER_DESTROYED : Historical Reporting Manager detroyed.

Explanation Historical Data Manager has been stopped

Recommended Action No actions needed

Error Message
MIVR-ENG- 6 -SUBSYSTEMS_STOPPED : SubSystems Stopped.

Explanation The subsystems have been stopped

Recommended Action No actions needed

Error Message
MIVR-ENG- 6 -WORKFLOW_RT_CONTAINER_SET : Workflow RT container set.

Explanation The workflow runtime container has been setup

Recommended Action No actions needed

Error Message
MIVR-ENG- 6 -WORKFLOW_MANAGER_INITIALIZED : Workflow Manager initialiazed.

Explanation The Workflow Manager has been initialized

Recommended Action No actions needed

Error Message
MIVR-ENG- 6 -RMI_MANAGER_INITIALIZED : RMI Manager initialiazed.

Explanation The RMI Manager has been initialized

Recommended Action No actions needed

Error Message
MIVR-ENG- 6 -TASK_MANAGER_INITIALIZED : Task Manager initialiazed.

Explanation The Task Manager has been initialized

Recommended Action No actions needed

Error Message
MIVR-ENG- 6 -REALTIME_DATA_MANAGER_INITIALIZED : Real Time Data Manager initialiazed.

Explanation The Realtime Data Manager has been initialized

Recommended Action No actions needed

Error Message
MIVR-ENG- 6 -HISTORICAL_REPORTING_MANAGER_INITIALIZED : Historical Reporting Manager initialiazed.

Explanation The Historical Reporting Manager has been initialized

Recommended Action No actions needed

Error Message
MIVR-ENG- 6 -SUBSYSTEMS_STARTED : SubSystems Started.

Explanation All subsystems have been started

Recommended Action No actions needed

Error Message
MIVR-ENG- 6 -SYSTEM_AND_DOMAIN : Current System and Domain. Module Name [String] Domain Name [String]

Explanation The system is running with a specific domain

Recommended Action No actions needed

Error Message
MIVR-ENG- 4 -PROBLEM_IN_PURGING_HISTORICAL_REPORT_FILES : Problem in purging Historical Reporting file(s).

Explanation Unable to purging Historical Reporting files

Recommended Action Check the configuration of the Historical Reporting. If problem persist contact Cisco technical assistance center

Error Message
MIVR-ENG- 4 -PROBLEM_IN_OPENING_HISTORICAL_REPORT_FILE : Problem in opening Historical Report file. Historical Report File Name [String]

Explanation Unable to open Historical Reporting files

Recommended Action Check the configuration of the Historical Reporting. If problem persist contact Cisco technical assistance center

Error Message
MIVR-ENG- 3 -RMI_UNKNOWN_HOST : Unknown host (RMI). Host address (RMI) [String]

Explanation Unable to locate the RMI host

Recommended Action Check the configuration of the engine host name in the AppAdmin page. If problem persist contact Cisco technical assistance center

Error Message
MIVR-ENG- 3 -RMI_PORT_IN_USE : RMI port in use. RMI Port number [String]

Explanation RMI port is being used by other applications

Recommended Action Change the port number of the engine to avoid conflict or check with the network configuration for other applications. If problem persist contact Cisco technical assistance center

Error Message
MIVR-ENG- 3 -SUBSYSTEM_START_ERROR : Error in starting the subsystem. Subsystem Name [String]

Explanation Error in starting the subsystem

Recommended Action Restart the server. If problem persist contact Cisco technical assistance center

Error Message
MIVR-ENG- 4 -SUBSYSTEMS_START_HALTED_IN_RECOVERY : Halt the starting of the subsystems, because system is being recovered or repaired.

Explanation Halt the starting of the subsystems, because system is being recovered or repaired

Recommended Action No actions needed

Error Message
MIVR-ENG- 6 -SUBSYSTEMS_START_CONTINUED : Continue the starting of the subsystems, because system has completed its recovery or repair.

Explanation Continue the starting of the subsystems, because system has completed its recovery or repair

Recommended Action No actions needed

Error Message
MIVR-ENG- 3 -HISTORICAL_MANAGER_INIT_ERROR : Error in starting the Historical Manager. Exception Message [String]

Explanation Error in starting the Historical Manager

Recommended Action Check the associated exception message and get more detail from the trace log if neccessary

Error Message
MIVR-ENG- 4 -HISTORICAL_MANAGER_QUEUE_CLOSE_TO_CAPACITY : Historical Manager database queue is close to capacity. Percentage of queue in use [String]

Explanation The Historical Manager queues is close to capacity. Once it becomes full, historical records may be lost. This can occur when database is under load of not running properly. If queue size goes below the threshold, an alarm HISTORICAL_MANAGER_QUEUE_NO_LONGER_AT_CAPACITY will be sent to cancel this alarm

Recommended Action Should monitor database and system load closely. Possible solutions include reducing system load, database activity such as generating reports. If problem persist contact Cisco technical assistance center

Error Message
MIVR-ENG- 6 -HISTORICAL_MANAGER_QUEUE_NO_LONGER_AT_CAPACITY : Historical Manager database queue is no longer close to capacity. Percentage of queue in use [String]

Explanation This message cancels the condition indicated by the alarm "HISTORICAL_MANAGER_QUEUE_CLOSE_TO_CAPACITY"

Recommended Action No action is needed.

Error Message
MIVR-ENG- 6 -HISTORICAL_MANAGER_QUEUE_CAPACITY_CHECK : Historical Manager database queue capacity report. Percentage of queue in use [String]

Explanation This message is informational. It appears when the queue capacity exceeds 50%"

Recommended Action No action is needed.

Error Message
MIVR-ENG- 3 -HISTORICAL_DATABASE_WRITE_FAILED : Failure occurred when writing historical record to the database. Table Name [String]

Explanation Failure occurred while inserting a record, please see the trace log for details of the failure, and a copy of the record

Recommended Action Historical records could be important. The failure should be corrected. Records can be added back manually based on details in the trace log.

Error Message
MIVR-ENG- 3 -HISTORICAL_DATABASE_WRITE_TIMEOUT : Timeout occurred when writing historical record to the database.. Table Name [String] Timeout value in seconds [String]

Explanation Timeout occurred while inserting a record, please see the trace log for more details. This can be caused by a busy database.

Recommended Action The insertion will be retried. But this may indicate an unreponsive or slow database. Should monitor database and system closely. Try to bring down activities such as heavy reporting.

Error Message
MIVR-ENG- 3 -CUSTOM_SUBSYSTEM_ERROR : Custom subsystem is not found. Exception [String]

Explanation There was a problem initializing the custom subsystem

Recommended Action Investigate as required

Error Message
MIVR-ENG- 3 -ERROR_IN_CUSTOMCONFIG : Error while retrieving custom config info. config file name [String] Exception [String]

Explanation An error occurred while reading a custom config file

Recommended Action Investigate as required

Error Message
MIVR-ENG- 2 -ERROR_IN_CONFIG : Error while retrieving critical configuration information. config file name [String] Exception [String]

Explanation An error occurred while reading a custom config file

Recommended Action Investigate as required

Error Message
MIVR-ENG- 2 -CLASS_NOT_FOUND_EXCEPTION : ClassNotFoundException caught . Exception [String]

Explanation ClassNotFoundException caught while reading Engine Configuration

Recommended Action Possible cause due to mismatch in jar files version. Check the timestamp of jar file version in install directory. If it is not the same, please re-install the Application again or call your technical support

Error Message
MIVR-ENG- 3 -FAILURE_TO_READ_ENGINE_CONFIG : Failure to read Engine Configurations . Exception [String]

Explanation An error has occurred when reading the engine Configurations

Recommended Action Investigate as required

Error Message
MIVR-ENG- 4 -EXCEPTION_READING_ENGINE_PROPERTIES_FILE : Exception reading Engine Properties file. property name [String] Exception [String]

Explanation An error has occurred when reading a property in engine.properties file

Recommended Action Check the value of the property in wfengine.properties file in the installed directory. Otherwise, please re-install the Application again or call your technical support

Error Message
MIVR-EXECUTOR_MGR- 1 -MGR_PARTIAL_SERVICE : Executor Manager in partial service.

Explanation The Executor Manager is in partial service; thread priorities will not be properly set

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-EXECUTOR_MGR- 4 -INVALID_THREAD_PRIORITY_CHANGE : Invalid thread priority change. Facility [String] Sub-Facility [String] Executor id [String] Thread [String] Thread priority [Int] Original thread priority [Int]

Explanation The specified thread had an unsupported priority changed; user's code should not attempt to manually change the priority of threads for whatever reasons

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-EXECUTOR_MGR- 6 -MGR_INITIALIZING : Executor Manager initializing.

Explanation The Executor Manager is initializing

Recommended Action No actions needed

Error Message
MIVR-EXECUTOR_MGR- 5 -MGR_SHUTTING_DOWN : Executor Manager shutting down.

Explanation The Executor Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-EXECUTOR_MGR- 2 -MGR_OUT_OF_SERVICE : Executor Manager in out of service.

Explanation The Executor Manager is out of service; executors won't be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-EXECUTOR_MGR- 4 -CMD_BLOCKED : Invoking blocked execution handler. Facility [String] Sub-Facility [String] Executor id [String] Mnemonic [String] Thread [String] Thread priority [Int] Time [Long] Handler [String]

Explanation The specified blocked execution handler is being invoked for the specified command as the executor queue could not accept it

Recommended Action No actions needed

Error Message
MIVR-EXECUTOR_MGR- 6 -MGR_IN_SERVICE : Executor Manager in service.

Explanation The Executor Manager is in service

Recommended Action No actions needed

Error Message
MIVR-EXECUTOR_MGR- 4 -MISSING_RESOURCE : Missing thread priority resource. Facility [String] Sub-Facility [String] Executor id [String] Exception [String]

Explanation The executor manager is unable to locate internal thread priority resources

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-EXECUTOR_MGR- 4 -CMD_EXCEPTION : Un-handled command exception. Facility [String] Sub-Facility [String] Executor id [String] Mnemonic [String] Thread [String] Thread priority [Int] Time [Long] Exception [String]

Explanation The specified command did not handled the specified exception

Recommended Action No actions needed

Error Message
MIVR-EXECUTOR_MGR- 4 -INVALID_THREAD_NAME_CHANGE : Invalid thread name change. Facility [String] Sub-Facility [String] Executor id [String] Thread [String] Original Thread [String]

Explanation The specified thread had an unsupported name changed; user's code should not attempt to manually change the name of threads for whatever reasons

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-EXECUTOR_MGR- 4 -ATTEMPT_FAILED : Attempt failed. Facility [String] Sub-Facility [String] Executor id [String] Mnemonic [String] Time [Long] Exception [String]

Explanation Attempt to execute the specified command failed

Recommended Action No actions needed

Error Message
MIVR-EXECUTOR_MGR- 5 -MGR_SHUTDOWN : Executor Manager in shutdown.

Explanation The Executor Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-EXECUTOR_MGR- 4 -EXECUTE_FAILED : Execute failed. Facility [String] Sub-Facility [String] Executor id [String] Mnemonic [String] Time [Long] Exception [String]

Explanation Request to execute the specified command failed

Recommended Action No actions needed

Error Message
MIVR-EXPR_MGR- 1 -MGR_PARTIAL_SERVICE : Expression Manager in partial service.

Explanation The Expression Manager is in partial service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-EXPR_MGR- 6 -MGR_IN_SERVICE : Expression Manager in service.

Explanation The Expression Manager is in service

Recommended Action No actions needed

Error Message
MIVR-EXPR_MGR- 3 -EXPR_NOT_LICENSED : Expression not licensed. Non terminal token id [String] Expression type [String] Token [String] Line [Int] Column [Int] Exception [String]

Explanation The specified expression is not licensed

Recommended Action Verify and update the script

Error Message
MIVR-EXPR_MGR- 6 -MGR_INITIALIZING : Expression Manager initializing.

Explanation The Expression Manager is initializing

Recommended Action No actions needed

Error Message
MIVR-EXPR_MGR- 5 -MGR_SHUTTING_DOWN : Expression Manager shutting down.

Explanation The Expression Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-EXPR_MGR- 2 -MGR_OUT_OF_SERVICE : Expression Manager in out of service.

Explanation The Expression Manager is out of service; expressions won't be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-EXPR_MGR- 5 -MGR_SHUTDOWN : Expression Manager in shutdown.

Explanation The Expression Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 3 -DATA_SOURCE_CANNOT_BE_INITIALIZED : Repository Datastore data source cannot be initialized. Exception [String]

Explanation The file manager could not get the datasource initialized for Repository Datastore.

Recommended Action If problem persists.Please contact Cisco Technical Assistance Center(TAC)

Error Message
MIVR-FILE_MGR- 3 -STATE_CHECKER_THREAD_CREATION_FAILED : Unable to start the File Manager's state monitor thread. Exception [String]

Explanation Unable to start the File Manager state monitor thread;FileManager functionality not available.

Recommended Action If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MIVR-FILE_MGR- 1 -MGR_PARTIAL_SERVICE : File Manager in partial service.

Explanation The File Manager is in partial service; file synchronization will notbe available

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-FILE_MGR- 3 -UNABLE_UPLOAD_FILE : Unable to upload the specified file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The file manager could not upload the specified file

Recommended Action Investigate as required

Error Message
MIVR-FILE_MGR- 6 -DELETE_FILE_FOLDER_REQ_BY_USER : A file or folder delete was initiated by user. Class [String] Domain [String] Directory [String] Name [String] User Id [String]

Explanation The file manager is requested to delete folder or file by user

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 3 -REFRESH_FAILED : File refresh operation failed. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation Unable to download and create the specified file

Recommended Action Investigate as required

Error Message
MIVR-FILE_MGR- 3 -RDS_SQL_EXCEPTION_INFO : SQL Exception. Exception details [String]

Explanation SQL Exception occurred in File Manager

Recommended Action Investigate as required

Error Message
MIVR-FILE_MGR- 4 -CLASSPATH_SYNC_FAILED : Custom classpath files synchronization failed. Exception [String]

Explanation The remote file manager was unable to synchronize the custom classpath files and <default><webapps> folder from the cluster's document repository

Recommended Action Investigate as required

Error Message
MIVR-FILE_MGR- 2 -CUSTOM_FILES_CLASSPATH_WEB_APPS_SYNC_FAILED : Unable to synchronize custom files/jars from Repository Datastore. Class [String] Exception [String]

Explanation Unable to do synchronization of <default><classpath> and<default><webapps> folders under <Documents><user>

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-FILE_MGR- 6 -SYNC_FOUND_LOCAL_FILE_NOT_IN_REPOSITORY : The local file found during synchronization is not present in Repository Datastore. Class [String] Extra local file [String]

Explanation The extra local file found during synchronization is being deleted.

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 5 -CUSTOM_FILES_CLASSPATH_WEB_APPS_SYNC_SUCCEEDED : Synchronization of custom files/jars from Repository Datastore done.

Explanation Synchronization of <default><classpath> and<default><webapps> folders under <Documents><user> completed.

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 6 -MGR_INITIALIZING : File Manager initializing.

Explanation The File Manager is initializing

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 2 -MGR_OUT_OF_SERVICE : File Manager in out of service.

Explanation The File Manager is out of service; files won't be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-FILE_MGR- 3 -UNABLE_DOWNLOAD_FILE : Unable to download the specified file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The file manager could not download the specified file

Recommended Action Investigate as required

Error Message
MIVR-FILE_MGR- 4 -SYNC_FAILED_TO_CREATE_FILE : Synchronization failed to create file. Class [String] Reason [String] Exception [String]

Explanation Creation of files failed during synchronization.

Recommended Action If problem persists contact.Please Cisco Technical Assistance Center(TAC).If files are missing you may have to restart the CVD Service.

Error Message
MIVR-FILE_MGR- 3 -SYNC_THREAD_CREATION_FAILED : Unable to start the File Manager's local disk synchronization thread for a file type.. Class [String] Exception [String]

Explanation Unable to start the File Manager sychronization thread;synchronization will not be available for the file type

Recommended Action If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MIVR-FILE_MGR- 6 -CLASSPATH_SYNC_START : Custom classpath and <default><webapps> files are being synchronized.

Explanation The remote file manager is synchronizing the custom classpath files and webapps folders files from the cluster's document repository

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 4 -ORIGINAL_FILE_NOT_FOUND : Original file not found while copying with new version. Original file: [String]

Explanation The file manager was unable to copy a new version file since the original file was not found.

Recommended Action Investigate as required

Error Message
MIVR-FILE_MGR- 3 -UNABLE_GET_REPOSITORY_STATISTICS : Unable to get the repository size information. Space information requested: [String] Exception [String]

Explanation The File Manager could not get the repository size information

Recommended Action Investigate as required

Error Message
MIVR-FILE_MGR- 6 -REMOTE_STANDALONE_MODE : Remote File Manager initialized in stand-alone mode.

Explanation The remote file manager is being initialized in stand-alone mode; it will attempt to synchronized custom classpaths with the cluster

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 6 -MGR_IN_SERVICE : File Manager in service.

Explanation The File Manager is in service

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 3 -UNABLE_RENAME_FILE : Unable to rename the specified file. Class [String] Domain [String] Directory [String] Name [String] Destination Domain [String] Destination Directory [String] Destination Name [String] Exception [String]

Explanation The file manager could not rename the specified file

Recommended Action Investigate as required

Error Message
MIVR-FILE_MGR- 3 -CLEANUP_THREAD_CREATION_FAILED : Unable to start the File Manager's cleanup thread. Exception [String]

Explanation Unable to start the cleanup background thread; will not be able to perform the disk cleanup operations

Recommended Action If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MIVR-FILE_MGR- 4 -GET_RDS_DB_CONNECTION_FAILED : Unable to get connection to the Repository Datastore. Failure Reason [String]

Explanation Unable to get connection to Repository Datastore access; will not be able to perform prompts,grammars, documents related operations

Recommended Action Check Repository Datastore is activated.If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MIVR-FILE_MGR- 6 -CLASSPATH_SYNC_DONE : Custom classpath files synchronized.

Explanation The remote file manager successfully synchronized the custom classpath files and webapps folder files from the cluster's document repository

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 3 -UNABLE_GET_FILE_MODIFIED_TIME : Unable to get the last modified time of the file or directory. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not get the file or directory's last modified time

Recommended Action Verify the path of the file or directory

Error Message
MIVR-FILE_MGR- 4 -EXCEPTION_IN_TEMP_FILES_HANDLING_METHOD : Method generated exception. Exception [String]

Explanation File Manager temporary files-cleanup handling, generated exception.

Recommended Action If problem persists please contact Cisco Technical Assistance Center(TAC).

Error Message
MIVR-FILE_MGR- 3 -UNABLE_GET_LAST_MODIFIED_USER : Unable to get the last modified user of the file or folder . Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not get the file or folder

Recommended Action Verify the file or folder exists in repository

Error Message
MIVR-FILE_MGR- 4 -LAST_SYNC_TIME_CHECK_FAILED : Error while checking the replication LastSynchedTime. Exception [String]

Explanation Could not get the replication sync time while updating repository statistics

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 6 -NO_FOLDER_FILE_TO_DELETE_BY_CLEANUP_TASK_RUN : Current run of daily cleanup found no files,folders to delete. Exception [String]

Explanation The File Manager daily cleanup task, to cleanup deleted (folder,files) on local disk,found not files,folders to delete .

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 3 -UNABLE_DELETE_FILE : Unable to delete the specified file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The file manager could not delete the specified file

Recommended Action Investigate as required

Error Message
MIVR-FILE_MGR- 6 -UPLOAD_ARCHIVE_FILE_SUCCESS : Success progress of upload archive file. Class [String] status [String]

Explanation Archive file each file type upload status

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 4 -COPY_FILES_TO_ORIG_LOCATION : Copying of files to original location errored. Exception [String]

Explanation The task to copy files from <temp> directory to original location failed

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 3 -CLUSTER_RMI_REBIND_FAILED : Unable to register remote interface in cluster space. Exception [String]

Explanation A remote interface could not be binded to the cluster space; automatic synchronization of files will not be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-FILE_MGR- 3 -UNABLE_MAKE_DIR : Unable to make directory. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not create the directory

Recommended Action Verify that path of the directory

Error Message
MIVR-FILE_MGR- 3 -SYNC_REMOTE_NOTIFICATION_FAILED : Notifying remote File Manager service objects failed. Class [String] Node Id [String] Exception [String]

Explanation Synchronization notifications using remote File Manager Service failed for one or more nodes.

Recommended Action If problem persists contact.Please Cisco Technical Assistance Center(TAC).

Error Message
MIVR-FILE_MGR- 6 -SYNC_OPERATION_STARTED : Synchronization started.. Class [String] Synchronization status [String]

Explanation Repository Datastore to local disk synchronization started.

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 3 -UNABLE_UPLOAD_ARCHIVE_FILE : Unable to upload the archive file. Archive File Name [String] Reason [String] Archive Length [String] Exception [String]

Explanation The File Manager could not upload the specified file

Recommended Action Investigate as required

Error Message
MIVR-FILE_MGR- 4 -DELETED_FOLDER_FILE_CLEANUP_TASK_RUN_FAILED : Current run of daily cleanup task failed. Exception [String]

Explanation The File Manager daily cleanup task, to clean deleted (folder,files) on local disk errored.The files,folders can get deleted in next daily run.

Recommended Action Investigate as required

Error Message
MIVR-FILE_MGR- 4 -SYNC_INVALID_STATE : Synchronization detected invalid state. Class [String] Reason [String]

Explanation Invalid state detected during synchronization

Recommended Action Investigate as required

Error Message
MIVR-FILE_MGR- 3 -UNABLE_LIST_FILES : Unable to list the files denoted by the specified file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The file manager could not list the files denoted by the specified file

Recommended Action Investigate as required

Error Message
MIVR-FILE_MGR- 6 -RECOVERY_COMPLETED_EVENT : File Manager recieved recovery completed event, full synchronization will be performed..

Explanation File Manager detected recovery completed event.Repository changes will be synched to local disk now.

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 1 -CLUSTER_COMM_FAILED : Cluster communication failure. Exception [String]

Explanation Unable to communicate with the cluster; will not be able to access the cluster repository files

Recommended Action Investigate as required

Error Message
MIVR-FILE_MGR- 3 -DUPLICATE_FILE_SUPPORT : Duplicate file support detected. Class [String] Exception [String]

Explanation An attempt is being made at registering a duplicate file support

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-FILE_MGR- 3 -UNABLE_GET_FILE_LENGTH : Unable to get the length of the file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not get the file length

Recommended Action Verify the path of the file

Error Message
MIVR-FILE_MGR- 3 -UNABLE_TO_CREATE_TEMP_DIR : Unable to make temp directory. Class [String] Name [String] Exception [String]

Explanation The File Manager could not create temp directory

Recommended Action Verify that Unified CCX prompts, documents, grammars and scripts folder are proper

Error Message
MIVR-FILE_MGR- 4 -ERROR_WHILE_SYNCH : An error occurred while synchronizing. Class [String] Method [String] Exception [String]

Explanation An error occurred while File Manager is synchronizing disk from RDS

Recommended Action If problem persists please contact Cisco Technical Assistance Center(TAC).

Error Message
MIVR-FILE_MGR- 3 -INVALID_FILE : Invalid file. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The specified file is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-FILE_MGR- 3 -FAIL_TO_CREATE_RDS_SERVICE_CONVERGENCE : Repository Datastore Service convergence object cannot be created.

Explanation The file manager cannot create Repository Datastore convergence object.Repository Datastore failover functionality will not be available.

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-FILE_MGR- 4 -SYNC_LOCAL_FILE_LATEST_THAN_IN_REPOSITORY : The local file is found to be newer than one in the Repository Datastore. Class [String] Local file [String] Repository Datastore file [String]

Explanation Local file is being replaced by the one in Repository Datastore

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 4 -SYNC_NOT_COMPLETE : Synchronization did not complete.. Class [String] Exception [String]

Explanation This indicates some of the synchronization operation failed.

Recommended Action If problem persists contact.Please Cisco Technical Assistance Center(TAC).

Error Message
MIVR-FILE_MGR- 6 -SYNC_OPERATION_COMPLETED : Synchronization completed.. Class [String] Synchronization status [String]

Explanation Repository Datastore to local disk synchronization completed.

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 6 -DELETED_TEMP_FILE_FOLDER : Temp file or folder was deleted. Temporary file or folder: [String]

Explanation The file manager deleted temporary file or folder

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 3 -UNABLE_SET_LAST_MODIFIED : Unable to set last modified time of the file or directory. Class [String] Domain [String] Directory [String] Name [String] Exception [String]

Explanation The File Manager could not set the last modified time of the file or directory.

Recommended Action Verify the path of the file or directory

Error Message
MIVR-FILE_MGR- 5 -MGR_SHUTTING_DOWN : File Manager shutting down.

Explanation The File Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 3 -UNABLE_FILE_EXISTS_CHECK : Check for file or directory existence failed. Class [String] Domain [String] Directory [String] Name [String] Error reason [String]

Explanation The File Manager could not find whether file or directory exists

Recommended Action Verify the path of the file or directory

Error Message
MIVR-FILE_MGR- 6 -RECOVERY_DETECTED : File Manager detected an archive request in the system;synchronization from Repository to local disk not performed..

Explanation File Manager detected an archive request in the system

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 3 -INVALID_FILE_CLASS : Invalid file class. Class [String] Exception [String]

Explanation The specified file class is not supported by the file manager

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-FILE_MGR- 4 -RMI_REBIND_FAILED : Unable to register remote interface. Exception [String]

Explanation A remote interface could not be binded to the RMI registry; remote access to files from the editor will not be available

Recommended Action Verify the RMI configuration and restart server

Error Message
MIVR-FILE_MGR- 3 -FILE_MANAGER_REGISTRATION_WITH_CLUSTER_FAILED : Unable to register the File Manager's Service remote object with the cluster.. Exception [String]

Explanation Unable to register the File Manager's remote service object.

Recommended Action If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MIVR-FILE_MGR- 4 -SYNC_FAILED_TO_MKDIR : Synchronization failed to make directory. Class [String] Reason [String]

Explanation Creation of directories failed during synchronization.

Recommended Action If files are missing you may have to restart the CVD Service.If problem persists contact.Please Cisco Technical Assistance Center(TAC)

Error Message
MIVR-FILE_MGR- 4 -RDS_DETERMINATION_FAILED : Repository Datastore cannot be initalized.. Exception [String]

Explanation The file manager could not initialize datastore to store prompts, grammars and documents within the cluster.This may happen if Repository Datastore component is not available in the cluster or configured properly.

Recommended Action Investigate as required

Error Message
MIVR-FILE_MGR- 6 -REMOTE_COLLOCATED_MODE : Remote File Manager initialized in collocated mode.

Explanation The remote file manager is being initialized in collocated mode; it will not attempt to synchronized custom classpaths with the cluster

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 5 -MGR_SHUTDOWN : File Manager in shutdown.

Explanation The File Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 4 -NEW_VERSION_FILE_NOT_FOUND : Newer version of file not found in <temp> directory. New version file(<temp>): [String]

Explanation The file manager was unable to find newer verion of file in <temp> while updating to original location

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 6 -SYNC_FOUND_LOCAL_FOLDER_NOT_IN_REPOSITORY : The local folder found during synchronization is not present in Repository Datastore. Class [String] Extra local folder [String]

Explanation The extra local folder found during synchronization is being deleted.

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 3 -SYNC_CANNOT_INITIALIZE_LOCAL_STORE : Unable to initialize local disk info when performing Repository Sync. Class [String] Exception [String]

Explanation Local store intialization failed during synchronization

Recommended Action If problem persists contactCisco Technical Assistance Center(TAC)

Error Message
MIVR-FILE_MGR- 3 -SYNC_CANNOT_INITIALIZE_DB_STORE : Unable to initialize Repository Datastore access when performing Synchronization. Class [String] Exception [String]

Explanation Accessing Repository Datastore failed.

Recommended Action Check if the RDS component is activated.If problem persists contact.Please Cisco Technical Assistance Center(TAC)

Error Message
MIVR-FILE_MGR- 6 -SYNCHRONIZATION_UPDATE : FileManager RDS to local disk synchronization. Class [String] Information [String]

Explanation progress message related to FileManager synchronization of local disk from RDS

Recommended Action No actions needed

Error Message
MIVR-FILE_MGR- 3 -REP_DATASTORE_INIT_FAILED : Unable to initialize the Repository Datastore access. Exception [String]

Explanation Unable to initialize Repository Datastore access; will not be able to perform prompts,grammars, documents related operations

Recommended Action Check Repository Datastore is enabled.If problem presists contactCisco Technical Assistance Center(TAC)

Error Message
MIVR-FILE_MGR- 6 -FILE_MARK_FOR_DELETION : Deleted file. Class [String] Domain [String] Directory [String] Name [String]

Explanation File Manager found the file marked for deletion

Recommended Action Operation cannot be preformed

Error Message
MIVR-FILE_MGR- 4 -MASTER_RDS_NOT_FOUND : Repository Datastore not found.. Reason [String]

Explanation The file manager could not find Repository Datastore to store prompts, grammars and documents within the cluster.This may happen if Repository Datastore component is not activated or Master RDS is not determined.

Recommended Action Investigate as required

Error Message
MIVR-GENERAL_STEPS- 3 -COULD_NOT_FIND_TIME_RANGE : Could not find Time range. Default branch executed. Task ID [String] Hour of Day [String] Minute [String]

Explanation Could not find Time range. Default branch executed

Recommended Action Check and validate your workflow script.

Error Message
MIVR-GENERAL_STEPS- 3 -COULD_NOT_FIND_RANGE_OF_DAYS : Could not find range of Days containing the current day. Task ID [String] Current day [String]

Explanation Could not find range of Days containing the current day

Recommended Action Check and validate your workflow script.

Error Message
MIVR-GENERIC- 5 -ProcessStart : Process Starting. Process Identifier [UInt] Module Name [String]

Explanation This notification signifies that a process has just started. This notification is intended to work in conjunction with the ProcessStop notification to notify the start and stop status of a particular process.

Recommended Action No actions needed

Error Message
MIVR-GENERIC- 5 -ModuleStart : Module has successfully started. Module Name [String]

Explanation This notification signifies a module has started successfully and transitioned into the in-service state

Recommended Action No actions needed

Error Message
MIVR-GENERIC- 3 -ModuleRunTimeFailure : Run-time Failure. Module Name [String] Module Run-time Failure Cause [Enum] Module Failure Name [String] Module Failure Message [String]

Explanation This notification signifies a run-time failure has occured

Recommended Action Investigate as required

Module Run-time Failure Cause-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Other or Unspecified Failure
2 Read Access Failure
3 Write Access Failure
4 Create Failure
5 Delete Failure
6 Update Failure
7 Init Failure
8 Load Failure
9 Out of Resource
10 Call Process Failure
11 Registration Failure
12 De-registration Failure
13 Connection Failure
14 Disconnection Failure
15 Unknown Target
16 Un-reacheable Target
Error Message
MIVR-GENERIC- 1 -ModuleStop : Module has stopped. Module Name [String] Module Failure Cause [Enum]

Explanation This notification signifies a module has stopped

Recommended Action Investigate as required

Module Failure Cause-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Other or Unspecified Failure
2 Graceful Shutdown
3 Heartbeat Failure
4 Initialization Failure
5 Out of Resource
6 Partial Failure
Error Message
MIVR-GENERIC- 1 -ProcessStop : Process Stopped. Process Identifier [UInt] Module Name [String]

Explanation This notification signifies that a process has just stopped. This notification is intended to work in conjunction with the ProcessStart notification to notify the start and stop status of a particular process.

Recommended Action Investigate as required

Error Message
MIVR-GRAMMAR_MGR- 3 -GRAMMAR_LEXICAL_ERROR : Template grammar lexical error. Name [String] Template [String] Language [String] Exception [String]

Explanation The specified lexical error occured while parsing a template grammar

Recommended Action Verify and update the application

Error Message
MIVR-GRAMMAR_MGR- 1 -MGR_PARTIAL_SERVICE : Grammar Manager in partial service.

Explanation The Grammar Manager is in partial service; synchronization of files with grammar repository is in progress

Recommended Action No actions needed

Error Message
MIVR-GRAMMAR_MGR- 6 -MGR_IN_SERVICE : Grammar Manager in service.

Explanation The Grammar Manager is in service

Recommended Action No actions needed

Error Message
MIVR-GRAMMAR_MGR- 2 -INVALID_USER_DIR : Invalid user grammar directory configured. Directory [String] Exception [String]

Explanation The configured user grammar directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-GRAMMAR_MGR- 3 -GRAMMAR_PARSING_ERROR : Template grammar parsing error. Name [String] Template [String] Language [String] Exception [String]

Explanation The specified error occured while parsing a template grammar

Recommended Action Verify and update the application

Error Message
MIVR-GRAMMAR_MGR- 3 -UNDEFINED_NAME_GRAMMAR : Undefined user or system grammar. Name [String] Type [String] Language [String] Exception [String]

Explanation A user or system grammar cannot be located

Recommended Action Verify and update the configuration

Error Message
MIVR-GRAMMAR_MGR- 3 -GRAMMAR_FILE_SUPPORT_FAILURE : Grammar file support failure. Exception [String]

Explanation The Grammar Manager can not register file support for user grammar files; user grammars will not be synchronized on local server

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-GRAMMAR_MGR- 5 -MGR_SHUTDOWN : Grammar Manager in shutdown.

Explanation The Grammar Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-GRAMMAR_MGR- 3 -UNABLE_PARSE_GRAMMAR : Unable to parse the grammar. Grammar [String] Type [String] Exception [String]

Explanation The Grammar Manager is unable to parse the specified grammar

Recommended Action Verify and update the configuration

Error Message
MIVR-GRAMMAR_MGR- 3 -UNSUPPORTED_GRAMMAR : Unsupported grammar type. Name [String] Type [String] Language [String] Exception [String]

Explanation The specified grammar type is not supported

Recommended Action Verify and update the application

Error Message
MIVR-GRAMMAR_MGR- 6 -MGR_INITIALIZING : Grammar Manager initializing.

Explanation The Grammar Manager is initializing

Recommended Action No actions needed

Error Message
MIVR-GRAMMAR_MGR- 5 -MGR_SHUTTING_DOWN : Grammar Manager shutting down.

Explanation The Grammar Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-GRAMMAR_MGR- 2 -MGR_OUT_OF_SERVICE : Grammar Manager in out of service.

Explanation The Grammar Manager is out of service; grammars won't be accessible

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-GRAMMAR_MGR- 3 -SYSGRAMMAR_FILE_SUPPORT_FAILURE : System grammar file support failure. Exception [String]

Explanation The Grammar Manager can not register file support for system grammar files; system grammars will not be synchronized on local server

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-GRAMMAR_MGR- 3 -WEBSERVICES_ERROR : Exception thrown while processing web services for Grammar. Exception [String]

Explanation Exception thrown while processing web services for Grammar

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-GRAMMAR_MGR- 2 -INVALID_SYSTEM_DIR : Invalid system grammar directory configured. Directory [String] Exception [String]

Explanation The configured system grammar directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-GRAMMAR_MGR- 3 -UNABLE_LOAD_GRAMMAR : Unable to load the grammar file. Name [String] Type [String] Language [String] Exception [String]

Explanation The Grammar Manager is unable to load the specified grammar file

Recommended Action Verify and update the configuration

Error Message
MIVR-GRAMMAR_MGR- 3 -UNSUPPORTED_CONVERSION : Unsupported grammar conversion. Type [String] Conversion Type [String] Exception [String]

Explanation The specified grammar conversion is not supported

Recommended Action Verify and update the application

Error Message
MIVR-HOLIDAY_MGR- 1 -MGR_PARTIAL_SERVICE : Holiday Manager in partial service.

Explanation The Holiday Manager is in partial service; synchronization of files with holiday repository is in progress

Recommended Action No actions needed

Error Message
MIVR-HOLIDAY_MGR- 3 -UNDEFINED_SYSTEM_CALENDAR : Undefined system calendar. Name [String] Locale [String] Exception [String]

Explanation A system calendar cannot be located

Recommended Action Verify and update the configuration

Error Message
MIVR-HOLIDAY_MGR- 6 -MGR_IN_SERVICE : Holiday Manager in service.

Explanation The Holiday Manager is in service

Recommended Action No actions needed

Error Message
MIVR-HOLIDAY_MGR- 2 -INVALID_USER_DIR : Invalid user holiday directory configured. Directory [String] Exception [String]

Explanation The configured user holiday directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-HOLIDAY_MGR- 3 -UNABLE_LOAD_USER_CALENDAR : Unable to load the user calendar file. Name [String] Locale [String] Exception [String]

Explanation The Holiday Manager is unable to load the specified user calendar file

Recommended Action Verify and update the configuration

Error Message
MIVR-HOLIDAY_MGR- 5 -MGR_SHUTDOWN : Holiday Manager in shutdown.

Explanation The Holiday Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-HOLIDAY_MGR- 3 -UNDEFINED_USER_CALENDAR : Undefined user calendar. Name [String] Locale [String] Exception [String]

Explanation A user calendar cannot be located

Recommended Action Verify and update the configuration

Error Message
MIVR-HOLIDAY_MGR- 3 -HOLIDAY_FILE_SUPPORT_FAILURE : Holiday file support failure. Exception [String]

Explanation The Holiday Manager can not register file support for user holidays files; user holidays will not be synchronized on local server

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-HOLIDAY_MGR- 2 -HOLIDAY_LDAP_CFG_ERROR : Holiday LDAP configuration failure. Exception [String]

Explanation The Holiday Manager is unable to load its LDAP configuration

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-HOLIDAY_MGR- 3 -UNABLE_LOAD_SYSTEM_CALENDAR : Unable to load the system calendar file. Name [String] Locale [String] Exception [String]

Explanation The Holiday Manager is unable to load the specified system calendar file

Recommended Action Verify and update the configuration

Error Message
MIVR-HOLIDAY_MGR- 6 -MGR_INITIALIZING : Holiday Manager initializing.

Explanation The Holiday Manager is initializing

Recommended Action No actions needed

Error Message
MIVR-HOLIDAY_MGR- 2 -MGR_OUT_OF_SERVICE : Holiday Manager in out of service.

Explanation The Holiday Manager is out of service; holiday calendars won't be accessible

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-HOLIDAY_MGR- 5 -MGR_SHUTTING_DOWN : Holiday Manager shutting down.

Explanation The Holiday Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-HOLIDAY_MGR- 4 -HOLIDAY_LDAP_CFG_MONITOR_FAIL : Holiday LDAP configuration monitoring failure. Exception [String]

Explanation The Holiday Manager can no longer monitor dynamic update to some of its configuration

Recommended Action No actions needed

Error Message
MIVR-HOLIDAY_MGR- 2 -INVALID_SYSTEM_DIR : Invalid system holiday directory configured. Directory [String] Exception [String]

Explanation The configured system holiday directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-HOLIDAY_MGR- 3 -UNABLE_LOAD_SYSTEM_HOLIDAYS : Unable to load the system holidays. Locale [String] Exception [String]

Explanation The Holiday Manager is unable to load the system holidays for the specified locale

Recommended Action Verify and update the configuration

Error Message
MIVR-HR_MGR- 6 -DB_INIT : Initializing DB. description [String]

Explanation Initializing DB

Recommended Action No actions needed

Error Message
MIVR-HR_MGR- 4 -DUPLICATE_HR_DB_ENTRY : A possible duplicate entry encountered during insertion into HR DB Tables. description [String]

Explanation The entry was ignored during insertion into HR DB Tables

Recommended Action No actions needed

Error Message
MIVR-HR_MGR- 6 -CLOSE_SQL_DATA : sql data files closed..

Explanation sql data files closed.

Recommended Action No actions needed

Error Message
MIVR-HR_MGR- 3 -SAVE_EXCEPTION : An exception caught . A description for the nature of the exception [String] Table [String] SQL statement [String] Exception [String]

Explanation An exception caught

Recommended Action An exception caught

Error Message
MIVR-HR_MGR- 3 -DB_LISTENER_INIT : Convergence for HDS from CVD is null.

Explanation Convergence for HDS from CVD is null

Recommended Action Check Control Center

Error Message
MIVR-HR_MGR- 6 -HRM_QUEUE_CAPACITY_CHECK : Queue capacity status. description [String]

Explanation Queue capacity checked.

Recommended Action No actions needed

Error Message
MIVR-HR_MGR- 2 -UCCX_HISTORICAL_DATA_WRITTEN_TO_FILES : Historical Data is being written to files please check the DB connectivity and availability. Module Name [String] Module Run-time Failure Cause [Int] Module Failure Name [String] Module Failure Message [String]

Explanation Historical Data is being written to files please check the DB connectivity and availability

Recommended Action No actions needed

Error Message
MIVR-HR_MGR- 3 -GET_INETADDRESS : Unable to get InetAddress. Exception [String]

Explanation Error in getting the InetAddress

Recommended Action Check the system, if problem persists contact the administrator

Error Message
MIVR-HR_MGR- 3 -HISTORICAL_DB_WRITE_FAILED : Error in writing into DB. Table [String] Exception [String]

Explanation Data will be saved in data files.

Recommended Action Check the DB server status in Control Center

Error Message
MIVR-HR_MGR- 6 -NO_FILES_TO_RESTORE : No files present to restore.

Explanation No files present to restore, SQLData folder might be empty

Recommended Action Check SQLdata folder if it is empty

Error Message
MIVR-HR_MGR- 6 -DBCONVEGENCE_INFO : DB convergence. description [String]

Explanation DB convergence

Recommended Action No actions needed

Error Message
MIVR-HR_MGR- 4 -HRM_QUEUE_CLOSE_TO_CAPACITY : Queue nearing capacity. description [String]

Explanation Historical Reporting Mgr queue reaching its capacity.

Recommended Action Check database performance/connectivity

Error Message
MIVR-HR_MGR- 6 -HRM_INIT : Initializing Historical Reporting Mgr. description [String]

Explanation Initializing Historical Reporting Mgr

Recommended Action No actions needed

Error Message
MIVR-HR_MGR- 3 -HISTORICAL_DB_WRITE_TIMEOUT : Timeout occurred while writing inot DB. Table [String] Exception [String]

Explanation Timeout occurred while writing inot DB, retried

Recommended Action No actions needed

Error Message
MIVR-HR_MGR- 3 -ERROR_GETTING_SQL_DATA_INDEX : sqldata.index was not deleted or wasn't present.

Explanation sqldata.index was not deleted or wasn't present

Recommended Action Check for permissions

Error Message
MIVR-HR_MGR- 6 -HRM_QUEUE_NO_LONGER_AT_CAPACITY : Queue is not full. description [String]

Explanation Queue is no longer at capacity.

Recommended Action No actions needed

Error Message
MIVR-HR_MGR- 3 -NO_DB_SCHEMA_VALIDATION : No database schema validation. reason [String]

Explanation No database schema validation

Recommended Action Please check the database server up running

Error Message
MIVR-HR_MGR- 4 -HDS_MASTER : Historical datastore master not found..

Explanation Historical datastore master not found.

Recommended Action Check whether HDS master exists for the cluster in Control Center

Error Message
MIVR-HR_MGR- 6 -SAVE_DATA : While shutting down, the historical data in queue is saved in files..

Explanation Saving historical data in files.

Recommended Action No actions needed

Error Message
MIVR-HR_MGR- 6 -UNREGISTER_DBLISTENER : DB listener for HDS removed from CVD.

Explanation DB listener for HDS removed from CVD successfully.

Recommended Action No actions needed

Error Message
MIVR-HR_MGR- 6 -DB_INSTANCENAME : Error in reading DB instance name.

Explanation Error in reading DB instance name

Recommended Action No actions needed

Error Message
MIVR-HR_MGR- 6 -SAVEDATA_INIT : Initializing SaveData. description [String]

Explanation Initializing SaveData

Recommended Action No actions needed

Error Message
MIVR-HR_MGR- 3 -SQL_DATA : Error while initialzing SaveData for saving sql data.. description [String]

Explanation Error while initialzing SaveData for saving sql data in the file.

Recommended Action Check the system

Error Message
MIVR-HR_MGR- 6 -HRM_EXIT : destroyed successfully.. Total number of records written [String] Total number of record overflow [String]

Explanation destroyed successfully.

Recommended Action No actions needed

Error Message
MIVR-HR_MGR- 6 -FILE_WRITER_THREAD : Historical data file writer thread. description [String]

Explanation Historical data file writer thread

Recommended Action No actions needed

Error Message
MIVR-HR_MGR- 6 -RECORDWRITER_REGISTERED : Initializing recordwriter. description [String]

Explanation Initializing recordwriter

Recommended Action No actions needed

Error Message
MIVR-HR_MGR- 6 -HRM_DESTROY : being destroyed..

Explanation Historical Reporting Mgr being destroyed.

Recommended Action No actions needed

Error Message
MIVR-HR_MGR- 3 -EXCEPTION_INFO : An exception has been caught.. A description for the nature of the exception [String] Exception [String]

Explanation An exception has been caught.

Recommended Action An exception has been caught.

Error Message
MIVR-HR_MGR- 4 -HISTORICAL_REPORTING_MANAGER_DISABLED : Historical Reporting Mgr disbaled..

Explanation Historical Reporting Mgr disbaled.

Recommended Action No actions needed

Error Message
MIVR-HR_MGR- 3 -DB_SCHEMA_CHECK : Error on database schema check. reason [String] Exception [String]

Explanation Error on database schema check

Recommended Action Check database running status from Control Center

Error Message
MIVR-ICD_CTI- 3 -CTI_SERVER_INIT_FAILED : CTI Server not initialized. A description for the nature of the exception [String] Exception [String]

Explanation The CTI Server is not initialized

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-ICD_CTI- 3 -SOCKET_IO_EXCEPTION : IO Exception occured on server socket. A description for the nature of the exception [String] Exception [String]

Explanation IO Exception occured on server socket

Recommended Action No actions needed

Error Message
MIVR-ICD_CTI- 3 -MSG_INVALID : An unexpected message. A specific description for a trace [String]

Explanation An unexpected message

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-ICD_CTI- 3 -CLIENT_SOCKET_CLOSED : Client connection closed. A specific description for a trace [String]

Explanation Client connection closed

Recommended Action No actions needed

Error Message
MIVR-ICD_CTI- 5 -CTI_SERVER_STOPPING_INTERRUPTED : CTI Server interrupting threads to stop. A description for the nature of the exception [String] Exception [String]

Explanation The CTI Server is interrupting threads to stop.

Recommended Action No actions needed

Error Message
MIVR-ICD_CTI- 4 -ECC_VARIABLE_TRUNCATION : Some of the ECC variable information did not fit into the message. One or more variable names may have been truncated, and one or more variables may have been omitted from the message. The list of truncated variable names [String] The list of variable names with truncated values [String] The list of variables omitted from the message [String]

Explanation Some of the ECC variable information did not fit into the message. One or more variable names may have been truncated, and one or more variables may have been omitted from the message

Recommended Action Verify and update the script

Error Message
MIVR-ICD_CTI- 6 -CLIENT_PING_INFO : Server pinging client for info.. A specific description for a trace [String]

Explanation Server pinging client for info.

Recommended Action No actions needed

Error Message
MIVR-ICD_CTI- 3 -MSG_PROCESSING_EXCEPTION : Exception occured while processing the message. A description for the nature of the exception [String] A specific description for a trace [String] Exception [String]

Explanation Exception occured while processing the message

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-ICD_CTI- 3 -ERROR_READING_MSGQ : Exception while reading MsgQ. A description for the nature of the exception [String] Exception [String]

Explanation Exception while reading MsgQ

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-ICD_CTI- 3 -MSGQ_READ_INTERRUPTION : MsgQ interrupted while reading. A specific description for a trace [String]

Explanation MsgQ interrupted while reading

Recommended Action No actions needed

Error Message
MIVR-ICD_CTI- 3 -SOCKET_ACCEPT_EXCEPTION : Exception while accepting a client connection.. A description for the nature of the exception [String] Exception [String]

Explanation An exception occured while accepting a client connection to the server socket.

Recommended Action No actions needed

Error Message
MIVR-ICD_CTI- 3 -SOCKET_WRITE_EXCEPTION : Exception while writing to a socket. A description for the nature of the exception [String] Exception [String]

Explanation Exception while writing to a socket

Recommended Action No actions needed

Error Message
MIVR-ICD_CTI- 3 -SOCKET_READ_EXCEPTION : Exception while reading from a socket input.. A description for the nature of the exception [String] Exception [String]

Explanation An exception occured while reading a message from the input stream on the client socket.

Recommended Action No actions needed

Error Message
MIVR-ICD_CTI- 6 -WATCHDOG_INFO : Watchdogthread:. A specific description for a trace [String]

Explanation Watchdogthread:

Recommended Action No actions needed

Error Message
MIVR-ICD_CTI- 3 -SOCKET_INTERRUPTED_EXCEPTION : Interrupted Exception occured on server socket. A description for the nature of the exception [String] Exception [String]

Explanation Interrupted Exception occured on server socket

Recommended Action No actions needed

Error Message
MIVR-ICD_CTI- 5 -CTI_SERVER_STOPPED : CTI Server is stopped.

Explanation The CTI Server is stopped.

Recommended Action No actions needed

Error Message
MIVR-ICD_CTI- 3 -CONTACT_INACTIVE_EXCEPTION : ContactInactiveException thrown.. Exception [String] An App FW CallContact [com.cisco.call.CallContact]

Explanation A ContactInactiveException has been thrown by the App FW and caught by the CTI Server.

Recommended Action No actions needed

Error Message
MIVR-ICD_CTI- 5 -CTI_SERVER_INITIALIZED : CTI Server is initialized.

Explanation The CTI Server is initialized.

Recommended Action No actions needed

Error Message
MIVR-ICD_RTDM- 3 -ERROR_UPDATING : Error in update walboard system. Exception [String]

Explanation Error

Recommended Action No actions needed

Error Message
MIVR-ICD_RTDM- 6 -RTS_RMI_BIND : Real-time snapshot remote object created successfully.

Explanation success

Recommended Action No actions needed

Error Message
MIVR-ICD_RTDM- 6 -WRITER_STOP : Real-time Snapshot stopped.

Explanation The Real-time Snapshot Data Writer is stopped

Recommended Action No actions needed

Error Message
MIVR-ICD_RTDM- 3 -STAT_CONDITION_FAILED : A reporting stat condition has failed. Module Name [String] Condition that should always be true [String] A reporting entity [String]

Explanation A reporting stat condition has failed

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-ICD_RTDM- 6 -INVALID_WRITING_INTERVAL : As the data writing interval is invalid, it will be set to the default, 30. value [String]

Explanation Invalid writing interval

Recommended Action No actions needed

Error Message
MIVR-ICD_RTDM- 6 -NO_WALLBOARD_SYSTEM_UPDATE : As there is no CDS master, wallboard is not updated.

Explanation no CDS DB master

Recommended Action No actions needed

Error Message
MIVR-ICD_RTDM- 6 -CFG_SETTINGS : Current Real-time Snapshot configurations. Real-time Snapshot Data writing status [String] Real-time Snapshot Data writing Interval [Long] CSQ Summary Info [String] Over all Summary Info [String]

Explanation Current Real-time Snapshot configurations

Recommended Action No actions needed

Error Message
MIVR-ICD_RTDM- 6 -CSQ_INFO_EMPTY : CSQ Data is empty.

Explanation CSQ Data is empty

Recommended Action No actions needed

Error Message
MIVR-ICD_RTDM- 6 -STATUS_CHANGE : Real-time snashot data writter status. Real-time Snapshot Data writing status [String]

Explanation Real-time snashot data writter status

Recommended Action No actions needed

Error Message
MIVR-ICD_RTDM- 6 -NO_WALLBOARD_SYSTEM_INFO : No wallboard system info configured.

Explanation no wallboard system info

Recommended Action No actions needed

Error Message
MIVR-ICD_RTDM- 3 -CFG_INIT_FAILURE : Error in initializing real-time snapshot config.

Explanation Setting to default values

Recommended Action Check wfengine.properties

Error Message
MIVR-ICD_RTDM- 4 -CFG_MONITOR_FAIL : Real-time Snapshot configuration monitoring failure. Exception [String]

Explanation Real-time Snapshot Data Writer can no longer monitor dynamic update to some of its configuration

Recommended Action No actions needed

Error Message
MIVR-ICD_RTDM- 3 -WRITER_EXCEPTION : An exception has been caught by Real-time Snapshot data writer. A description for the nature of the exception [String] Exception [String]

Explanation An exception has been caught by Real-time Snapshot data writer

Recommended Action An exception has been caught by Real-time Snapshot data writer

Error Message
MIVR-ICD_RTDM- 6 -DEFAULT_CONFIG : No config to read, setting default..

Explanation no config

Recommended Action No actions needed

Error Message
MIVR-ICD_RTDM- 6 -WRITER_INIT : Real-time Snapshot initialized.

Explanation The Real-time Snapshot Data Writer is initialized

Recommended Action No actions needed

Error Message
MIVR-ICD_RTDM- 6 -INTERRUPTED : real-time snapshot data Writing interrupted.

Explanation Interrupted

Recommended Action No actions needed

Error Message
MIVR-ICD_RTDM- 6 -NO CDS MASTER DB : No database CDS master to write. reason [String]

Explanation no DB

Recommended Action Please check control center

Error Message
MIVR-LIB_AXL- 3 -SLEEP_AXL_EXCEPTION : Exception while sleeping for AXL. Exception [String]

Explanation Exception while sleeping for AXL

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_AXL- 3 -DUPLICATE_VALUE_AXL_EXCEPTION : Entered Duplicate Value. Exception [String]

Explanation Entered Duplicate Value

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_AXL- 3 -IO_AXL_EXCEPTION : IO AXL Exception. Exception [String]

Explanation IO AXL Exception

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_AXL- 3 -AXL_CONFIF_EXCEPTION : AXL Configuration Exception. Exception [String]

Explanation AXL Configuration Exception

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_AXL- 3 -RESOURCE_UNAVAILABLE_AXL_EXCEPTION : CCM AXL Server is busy. Exception [String]

Explanation CCM AXL Server is busy

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_AXL- 3 -UNKNOWN_HOST_AXL_EXCEPTION : Invalid CCM Hostname. Exception [String]

Explanation Invalid CCM Hostname

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_AXL- 3 -INVALID_USER_AXL_EXCEPTION : IIS Authentication failed on CCM. Exception [String]

Explanation IIS Authentication failed on CCM

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_AXL- 4 -AXL_TIMEOUT_DETECTED : AXL Timeout Detected. Cmd [String]

Explanation AXL Timeout Detected

Recommended Action No actions needed

Error Message
MIVR-LIB_AXL- 3 -AXL_EXCEPTION : Unknown AXL Exception. Exception [String]

Explanation Unknown AXL Exception

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_AXL- 3 -AXL_SOCKET_POOL_EXCEPTION : AXL can not initializa socket pool. Exception [String]

Explanation AXL can not initializa socket pool

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_CFG- 3 -NOTIFY_FAIL : Fail Notifying Remote Object. Exception [String]

Explanation Fail Notifying Remote Object

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_CFG- 4 -CUIC_REPORT_PERMISSIONS_ERROR : Grant or Revoke permissions to CUIC Folders and Reports failed. Exception [String]

Explanation Grant or Revoke permissions to CUIC Folders and Reports failed

Recommended Action No actions needed

Error Message
MIVR-LIB_CFG- 3 -INVALID_USER : User is invalid. User [String] Exception [String]

Explanation User could not be retrieved

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_CFG- 3 -INVALID_DATA_TYPE : DB operation failed because data type is invalid. ICD Config Data Type [String]

Explanation DB operation failed because data type is invalid

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-LIB_CFG- 6 -UNABLE_TO_ACQUIRE_CLUSTER_MUTEX : Cluster mutex lock could not be acquired. Name of thread trying to acquire lock [String] Exception [String]

Explanation Cluster mutex lock could not be acquired

Recommended Action No actions needed

Error Message
MIVR-LIB_CFG- 3 -REPOS_CFG_FAIL : Fail to access repository profile configuration. Exception [String]

Explanation Fail to create/retrieve/update/remove repository profile configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MIVR-LIB_CFG- 3 -GED_CONFIG_FAIL : Fail to retrieve GED 125 configuration. Exception [String]

Explanation Fail to retrieve GED 125 configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MIVR-LIB_CFG- 1 -UCCX_TO_CUIC_SYNC_FAILED : Notification to CUIC failed. UCCX TO CUIC SYNC failed for these resources::: [String]

Explanation Notification to CUIC on resource change failed

Recommended Action EXECUTE Resource sync command from CLI

Error Message
MIVR-LIB_CFG- 3 -JTAPI_CFG_FAIL : Fail to access JTAPI configuration. Exception [String]

Explanation Fail to create/retrieve/update/remove JTAPI configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MIVR-LIB_CFG- 3 -TAPI_GRP_CONFIG_FAIL : Fail to retrieve TAPI Port Group configuration. Exception [String]

Explanation Fail to retrieve TAPI Port Group configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MIVR-LIB_CFG- 6 -MASTER_CDS_CHANGE : The master CDS has changed. Master CDS Name [String]

Explanation The master CDS has changed

Recommended Action No actions needed

Error Message
MIVR-LIB_CFG- 3 -TELE_CFG_FAIL : Fail to create telephony application configuration. Exception [String]

Explanation Fail to create telephony application configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MIVR-LIB_CFG- 3 -ENG_SAVE_FAIL : Fail to save LDAP engine configuration. Exception [String]

Explanation Fail to save LDAP engine configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MIVR-LIB_CFG- 3 -PROFILE_CFG_FAIL : Fail to access profile configuration. Exception [String]

Explanation Fail to create/retrieve/update/remove profile configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MIVR-LIB_CFG- 3 -CONFIG_FAIL : Fail to load ldap configuration file. Exception [String]

Explanation Fail to load ldap configuration file

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_CFG- 3 -GED_SCRIPT_CFG_FAIL : Fail to retrieve GED 125 Script configuration. Exception [String]

Explanation Fail to retrieve GED 125 Script configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MIVR-LIB_CFG- 3 -VOICE_CFG_FAIL : Fail to access Voice configuration. Exception [String]

Explanation Fail to create/retrieve/update/remove Voice configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MIVR-LIB_CFG- 3 -GED_ROUTE_CFG_FAIL : Fail to retrieve GED 125 Route configuration. Exception [String]

Explanation Fail to retrieve GED 125 Route configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MIVR-LIB_CFG- 3 -PROVIDER_UNAVAILABLE : LDAP provider is unavailable. ldap url base [String] Exception [String]

Explanation LDAP provider is unavailable

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_CFG- 3 -HTTP_CFG_FAIL : Fail to access HTTP configuration. Exception [String]

Explanation Fail to create/retrieve/update/remove HTTP configuration

Recommended Action Verify LDAP server availability and configuration

Error Message
MIVR-LIB_CFG- 4 -REMOTE_OBJ_FAIL : Remote object could not be retrieved. remote object name [String] Exception [String]

Explanation Remote object could not be retrieved

Recommended Action No actions needed

Error Message
MIVR-LIB_CFG- 3 -INI_SAVE_FAIL : Fail to save ini ldap configuration file. Exception [String]

Explanation Fail to save ini ldap configuration file

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-LIB_CFG- 3 -ENGINE_CONFIG_FAIL : LDAP Engine Configuration fail to initialize. Exception [String]

Explanation LDAP Engine Configuration fail to initialize

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_CLUSTER_CFG- 6 -MUTEX_SUCCESSFULLY_RENEWED : Mutex successfully renewed. owner [String] usage [String] userInfo [String] leaseDate [String]

Explanation Mutex successfully renewed

Recommended Action No actions needed

Error Message
MIVR-LIB_CLUSTER_CFG- 4 -INVALID_MUTEX_OWNER : Invalid Mutex owner. cmd [String] lockOwner [String] owner [String] usage [String] userInfo [String]

Explanation The specified cmd was requested by a different owner than the original owner who acquired the mutex, which is not permitted

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-LIB_CLUSTER_CFG- 3 -CONFIG_ERROR : Error while accessing LockConfig. owner [String] usage [String] userInfo [String] Exception [String]

Explanation Error while accessing LockConfig

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-LIB_CLUSTER_CFG- 4 -MUTEX_EXPIRED : Mutex expired. cmd [String] lockOwner [String] leaseDate [String] owner [String] usage [String] userInfo [String]

Explanation The mutex lease has expired when the specified cmd is received

Recommended Action No actions needed

Error Message
MIVR-LIB_CLUSTER_CFG- 6 -MUTEX_SUCCESSFULLY_ACQUIRED : Mutex successfully acquired. owner [String] usage [String] userInfo [String]

Explanation Mutex successfully acquired

Recommended Action No actions needed

Error Message
MIVR-LIB_CLUSTER_CFG- 6 -MUTEX_SUCCESSFULLY_RELEASED : Mutex successfully released. owner [String] usage [String] userInfo [String]

Explanation Mutex successfully released

Recommended Action No actions needed

Error Message
MIVR-LIB_CRTP- 3 -CRTP_INTERCEPT_ERROR : CRTP interceptor error operation. Error reason [String] Exception [String]

Explanation CRTP interceptor encountered an error while performing the following operation

Recommended Action No actions needed

Error Message
MIVR-LIB_CRTP- 3 -CRTP_SERVLET_ERROR : CRTP servlet error. Error reason [String] Exception [String]

Explanation CRTP servlet encountered an error while performing the following operation

Recommended Action No actions needed

Error Message
MIVR-LIB_DATABASE- 6 -RECOVERY_COMPLETED_EVENT : Received recovery completed event; DB alias will be synched now.

Explanation Database component detected recovery completed event; DB alias will be synched now.

Recommended Action No actions needed

Error Message
MIVR-LIB_DATABASE- 3 -SUBSCRIBER_DB_UNAVAILABLE : Subscriber database is not running or inaccessible.

Explanation An attempt to connect to the subscriber database has failed. Verify that the subscriber database is functioning and network connectivity is available to the subscriber node.

Recommended Action Investigate as required

Error Message
MIVR-LIB_DATABASE- 6 -UPLOAD_USER_FILE_FAILED : Database Archive Component fails to upload the corresponding file or directory to Repository Datastore. It will be copied to the specified temporary location. file or directory name [String] temporary directory name [String] Exception [String]

Explanation Database Archive Component fails to upload the corresponding file or directory to Repostiory Datastore during upgrade migration. The file or directory will be copied to the specified temporary directory.

Recommended Action Investigate as required

Error Message
MIVR-LIB_DATABASE- 3 -DATABASE_ERROR : A generic database error. Exception [String]

Explanation A generic database error occured, this could be related to SQL or none-SQL related.

Recommended Action Investigate as required

Error Message
MIVR-LIB_DATABASE- 3 -UPDATE_ERROR : update error. Exception [String]

Explanation Error in updating the cluster info

Recommended Action Investigate as required

Error Message
MIVR-LIB_DATABASE- 3 -COPYING_USER_FILES_FAILED : Database Archive Component fails to copy the corresponding file or directory to temporary location. file or directory name [String] temporary directory name [String] Exception [String]

Explanation Database Archive Component fails to copy the corresponding file or directory to temporary location, in an attempt to save the file after it fails to upload it to Repository datastore.

Recommended Action Investigate as required

Error Message
MIVR-LIB_DATABASE- 3 -DB_REPLICATION_ERROR : A generic database replication error. Exception [String]

Explanation A generic database replication error occured, this could be related to SQL or none-SQL related.

Recommended Action Investigate as required

Error Message
MIVR-LIB_DATABASE- 1 -DB_REPLICATION_STOPPED : Database replication stopped. Reason for Stopping Replication [String] Exception [String]

Explanation Database replication is stopped. Please Setup Replication from DataStore Control Center, after bringing the other node up.

Recommended Action Investigate as required

Error Message
MIVR-LIB_DATABASE- 6 -SCRIPT_NOT_FOUND : Database Archive Component could not find the corresponding file or directory to upload during restore. file or directory location [String]

Explanation Database Archive Component could not find the corresponding file or directory to upload during restore

Recommended Action Investigate as required

Error Message
MIVR-LIB_DATABASE- 1 -DB_NOT_IN_SYNC : Database is not in sync on both nodes.

Explanation One of more tables in Database are not in sync across nodes. Please Check whether replication is working fine. If replication is broken, reset replication else synchronize data on both nodes using forced data sync from CLI

Recommended Action Investigate as required

Error Message
MIVR-LIB_DATABASE- 6 -DB_REPLICATION_INITIALIZING : DB Replication is getting initialized.

Explanation DB Replication is getting initialized

Recommended Action No actions needed

Error Message
MIVR-LIB_DATABASE- 3 -INIT_ERROR : read error. Exception [String]

Explanation error in reading

Recommended Action Investigate as required

Error Message
MIVR-LIB_DATABASE- 4 -REPLICATION_OLD_PUBLISHER_CLEANUP_FAIL : DB Replication old publisher cleanup failed. Old Publisher [Int] Exception [String]

Explanation Failed to cleanup the old publisher role while performing a switch publisher

Recommended Action No actions needed

Error Message
MIVR-LIB_DATABASE- 6 -RECOVERY_DETECTED : Detected a recovery archive request in the system; DB alias sync is postponed until recovery is complete..

Explanation Database component detected a recovery archive request in the system; DB alias sync is postponed until recovery is complete.

Recommended Action No actions needed

Error Message
MIVR-LIB_EVENT- 3 -DISPATCH_FAILURE : A failure occured while dispatching an event. Event [String] Event source [String] Event listener [String] Exception [String]

Explanation An uncaught error occured while dispatching an event

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-LIB_EVENT- 5 -TOO_LONG_IN_QUEUE : Event queue time exceeded. Event [String] Queue Time [Long]

Explanation The specified event stayed in queue for too long

Recommended Action No actions needed

Error Message
MIVR-LIB_EVENT- 4 -EVENT_INIT_FAILURE : Unable to initialize the system event queue logger. Exception [String]

Explanation The logger could not be registered with the system event queue; the traces for the event queue will not be available

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 6 -ICM_SESSION_ESTABLISHED : ICM session established.

Explanation A session was established with the ICM

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 3 -INVALID_ECC_LENGTH : Invalid ICM ECC variable length. ECC Variable Name [String] ECC Variable Value [String] ECC Variable Length [Int] Call id [Int] Media id [String] Exception [String]

Explanation The specified ICM Expanded Call variable is of an invalid length

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 3 -INVALID_TRUNK_NUM : Invalid ICM Trunk number. Trunk number [Int] Exception [String]

Explanation The specified ICM Trunk number is invalid

Recommended Action Restart server

Error Message
MIVR-LIB_ICM- 3 -DECODING_ERROR : ICM Message decoding error. Exception [String]

Explanation The ICM provider encountered an error while decoding an ICM message

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 6 -VRU_CONN_ESTABLISHED : VRU connection established with ICM. ICM Address [String]

Explanation A VRU connection has been established with the ICM

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 3 -NO_IDLE_TRUNKS : No idle trunks left in trunk group. Trunk Group id [Int] Exception [String]

Explanation The specified ICM Trunk Group has no idle trunks left

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 4 -UNSUPPORTED_VERSION : Unsupported VRU protocol version. Version [Int]

Explanation An ICM session was rejected because the specified ICM VRU protocol version is not supported by this ICM provider

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 3 -INVALID_MSG_FIELD : Invalid ICM message field. Field Tag Name [String] Field Tag id [Int] Exception [String]

Explanation The ICM Provider is unable to decode an ICM message field

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 3 -UNEXPECTED_ECC_FIELD : Unexpected ECC field. ECC Field [String] ECC Field Class [String] Call id [Int] Media id [String]

Explanation The specified ICM Call is being aborted

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 3 -INVALID_CALL_ID : Invalid ICM Call id. Call id [Int] Exception [String]

Explanation The specified ICM Call identifier is invalid

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 6 -ICM_VRU_PROTOCOL_VERSION : The ICM VRU Protocol version received. Version [Int]

Explanation An ICM session request was received with the specified VRU protocol version

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 4 -UNEXPECTED_ICM_MSG : Unexpected ICM message received. ICM Message [String] Call id [Int] Media id [String]

Explanation An unexpected ICM message was received for the specified call

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 4 -DISABLING_EVENT_FEED : Disabling Event Feed for this ICM session. Version [Int]

Explanation The Event Feed protocol is being disabled because the specified VRU protocol version doesn't support both the Service Control and the Event Feed protocols

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_ICM- 6 -ABORTING_CALL : Aborting ICM Call. Call id [Int] Media id [String] Trunk number [Int] Trunk Group id [Int]

Explanation The specified ICM Call is beaing aborted

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 4 -SERVICE_CTRL_DISABLED : Rejecting initialization due to disabled Service Control protocol.

Explanation The initalization was rejected because the Service Control protocol is disabled

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_ICM- 3 -INVALID_TRUNK_GROUP_ID : Invalid ICM Trunk Group id. Trunk Group id [Int] Exception [String]

Explanation The specified ICM Trunk Group identifier is invalid

Recommended Action Restart server

Error Message
MIVR-LIB_ICM- 3 -ENCODING_ERROR : ICM Message encoding error. ICM Message [String] Call id [Int] Media id [String] Exception [String]

Explanation The ICM provider encountered an error while encoding the specified ICM message

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 3 -UNDEFINED_TRUNK : Undefined ICM Trunk. Trunk number [Int] Trunk Group id [Int] Exception [String]

Explanation The specified ICM Trunk is undefined in the ICM Provider

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 3 -INVALID_ECC_ID : Invalid ICM ECC variable index. ECC Variable Name [String] ECC Variable Index [Int] Call id [Int] Media id [String] Exception [String]

Explanation The specified ICM Expanded Call variable index is invalid

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 3 -UNDEFINED_SERVICE : Undefined ICM Service. Service id [Int] Exception [String]

Explanation The specified ICM Service is undefined in the ICM Provider

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 3 -CALLBACK_ALREADY_INIT : Callback already registered. Call id [Int] Media id [String] Exception [String]

Explanation A service control callback is already registered with the specified call

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 3 -INVALID_ECC_TYPE : Invalid ICM ECC variable type. ECC Variable Name [String] ECC Variable Type [String] Call id [Int] Media id [String] Exception [String]

Explanation The specified ICM Expanded Call variable type is invalid

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 1 -UNABLE_INIT_VRU_PORT : Unable to initialize VRU port. VRU Port [Int] Exception [String]

Explanation The ICM Provider was unable to initialize the configured VRU connection port

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 4 -ICM_SESSION_CLOSED : ICM session closed. Reason [String]

Explanation The session was closed by the ICM

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 3 -PROVIDER_DISABLED_ON_STANDBY : Rejecting ICM session because CRS is in standby mode.

Explanation The requested ICM session was rejected because the ICM Provider is in standby mode

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 3 -INVALID_MSG : Invalid ICM message type. ICM Message Type [String] Exception [String]

Explanation The ICM Provider is unable to decode an ICM message

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 3 -INVALID_PROVIDER_PARM : Invalid ICM Provider parameter. Parameter Name [String] Parameter Value [String] ICM Provider Name [String] Exception [String]

Explanation The ICM Provider is missing the specified mandatory parameter

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 2 -ICM_SESSION_LOST : ICM Session lost.

Explanation The session with the ICM was lost

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 4 -POLLED_FEED_UNSUPPORTED : Rejecting initialization due to unsupported Polled Feed protocol.

Explanation The initialization was rejected because the Polled Feed protocol is unsupported

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 3 -SERVICE_UNAVAILABLE : ICM Service is unavailable. Service id [Int] Contact id [Int] Exception [String]

Explanation The specified ICM Service is unavailable for the specified call

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 3 -UNREGISTERED_ECC_VAR : Unregistered ECC variable. ECC Variable id [Int] Call id [Int] Media id [String]

Explanation The specified ICM Expanded Call variable is not registered

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_ICM- 3 -INVALID_SERVICE_ID : Invalid ICM Service id. Service id [Int] Exception [String]

Explanation The specified ICM Service identifier is invalid

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_ICM- 3 -UNDEFINED_VRU_SCRIPT : Undefined VRU script referenced by the specified call. VRU Script [String] ICM Message [String] Call id [Int] Media id [String]

Explanation The VRU script referenced by the specified call is undefined

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 3 -INVALID_CED_LENGTH : Invalid caller-entered digits length. CED [String] CED Length [Int] Call id [Int] Media id [String] Exception [String]

Explanation The specified caller-entered digits are of an invalid length

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 3 -INVALID_ECC_ARRAY_LENGTH : Invalid ICM ECC array variable length. ECC Variable Name [String] ECC Variable Index [Int] ECC Variable Value [String] ECC Variable Length [Int] Call id [Int] Media id [String] Exception [String]

Explanation The specified ICM Expanded Call array variable is of an invalid length

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 6 -ACCEPTING_VRU_CONN : Accepting VRU connection. VRU Connection [String]

Explanation The ICM Provider is accepting the specified VRU connection

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 3 -INVALID_PERIPHERAL_ID : Invalid ICM Provider peripheral index. ICM Peripheral id [Int] ICM Provider Name [String] Exception [String]

Explanation The specified ICM Provider peripheral index is invalid

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 3 -NO_INITIAL_MICROAPP_PLAY : No initial microapp play request referenced by the specified call. ICM Message [String] Call id [Int] Media id [String]

Explanation A microapp play continue request was received without an initial play request referenced by the specified call

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 6 -OPERATIONAL_STATUS : ICM Provider operational status. ICM Provider Status [Int] ICM Provider Name [String]

Explanation The ICM Provider operational status is changing to the given value

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 3 -PROVIDER_DISABLED : Rejecting ICM session due to disabled ICM provider.

Explanation The requested ICM session was rejected because the ICM Provider is disabled

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_ICM- 6 -IGNORING_ICM_MSG : Ignoring ICM message received. ICM Message [String]

Explanation The specified ICM message was ignored

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 1 -UNABLE_INIT_VRU_IO : Unable to initialize VRU I/O streams. VRU Port [Int] Exception [String]

Explanation The ICM Provider was unable to initialize the VRU I/O streams for the configured VRU connection port

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 6 -TRUNCATING_ANI : Trancating ANI to 40 characters. ANI [String] Call id [Int] Media id [String]

Explanation The ANI received is longer then 40 characters and must be trancated

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 3 -INVALID_MEDIA_PROTOCOL : Invalid ICM message media protocol. Media Protocol [String] Exception [String]

Explanation The ICM Provider is unable to decode an ICM media protocol

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 3 -TRUNK_GROUP_EMPTY : ICM Trunk Group is empty. Trunk Group id [Int] Exception [String]

Explanation The specified ICM Trunk Group has no trunks configured

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_ICM- 3 -INVALID_TRUNK_STATUS : Invalid ICM Trunk status. ICM Trunk Status [String] Exception [String]

Explanation The specified ICM Trunk status status is invalid

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 3 -INVALID_OPERATIONAL_STATUS : Invalid ICM Provider operational status. ICM Provider Status [Int] ICM Provider Name [String] Exception [String]

Explanation The specified ICM Provider operational status is invalid

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 3 -INVALID_VAR_ID : Invalid ICM Call variable id. Variable id [Int] Call id [Int] Media id [String] Exception [String]

Explanation The specified ICM Call variable identifier is invalid

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_ICM- 4 -INVALID_SEQ_NUM : Invalid sequence number. ICM Message [String] Sequence Number [Int] Call id [Int] Media id [String] Exception [String]

Explanation The ICM provider received a request from the ICM which with an invalid sequence number

Recommended Action No actions needed

Error Message
MIVR-LIB_ICM- 3 -TRUNK_IN_USE : ICM Trunk is already in use. Trunk number [Int] Trunk Group id [Int] Contact id [Int] Exception [String]

Explanation The specified ICM Trunk is already in use for the specified call

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 3 -CALL_ALREADY_INIT : ICM Call is already initialized. Call id [Int] Media id [String] Exception [String]

Explanation The specified ICM Call is already initialized

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 3 -UNDEFINED_TRUNK_GROUP : Undefined ICM Trunk Group. Trunk Group id [Int] Exception [String]

Explanation The specified ICM Trunk Group is undefined in the ICM Provider

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 3 -DUPLICATE_CALL_ID : Duplicate ICM Call id. Call id [Int] Exception [String]

Explanation The specified ICM Call identifier is already in use by another call

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 4 -EVENT_FEED_DISABLED : Rejecting initialization due to disabled Event Feed protocol.

Explanation The initialization was rejected because the Event Feed protocol is disabled

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_ICM- 3 -INVALID_VAR_LENGTH : Invalid ICM Call variable length. Variable id [Int] Variable Value [String] Variable Length [Int] Call id [Int] Media id [String] Exception [String]

Explanation The specified ICM Call variable is of an invalid length

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_ICM- 3 -CALL_NOT_INIT : ICM Call is not initialized. Call id [Int] Media id [String] Exception [String]

Explanation The specified ICM Call is not initialized

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 3 -INVALID_CALLBACK : Invalid callback registered. Call id [Int] Media id [String] Exception [String]

Explanation An invalid service control callback was registered

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_ICM- 4 -TIME_SYNCH_DISABLED : Rejecting initialization due to disabled Time Synchronization protocol.

Explanation The initialization was rejected because the Time Synchronization protocol is disabled

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_ICM- 3 -INVALID_ECC_NAME : Invalid ICM ECC variable name. ECC Variable Name [String] ECC Variable Length [Int] Exception [String]

Explanation The specified ICM Expanded Call variable name is invalid

Recommended Action Verify and update the configuration

Error Message
MIVR-LIB_ICM- 3 -INVALID_CAUSE : Invalid clearing cause. Cause [Int] Call id [Int] Media id [String] Exception [String]

Explanation The specified cleraing cause is invalid

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_JASPER- 6 -MSG : . Message [String] Exception [String]

Explanation See log message for more info.

Recommended Action Investigate as required

Error Message
MIVR-LIB_JASPER- 6 -MMSG : . Module [String] Message [String] Exception [String]

Explanation See module's log message for more info.

Recommended Action Investigate as required

Error Message
MIVR-LIB_JMAIL- 5 -JMAIL_LOG_MONITOR_FAIL : Java Mail log configuration monitoring failure.

Explanation Java Mail layer can no longer monitor dynamic update to its log configuration; debug messages disabled

Recommended Action No actions needed

Error Message
MIVR-LIB_LDAP- 3 -LDAP_CON_ERROR : Error accessing LDAP. ldap url [String] Exception [String]

Explanation An error occurred while accessing LDAP

Recommended Action No actions needed

Error Message
MIVR-LIB_LDAP- 4 -LDAP_CON_WARNING : Problem accessing LDAP. ldap url [String] Exception [String]

Explanation An problem occurred while accessing LDAP

Recommended Action No actions needed

Error Message
MIVR-LIB_LICENSE- 3 -LICENSE_CONFIG_UNAVAILABLE_ERROR : LicenseConfig unavailable or retrieve error. Exception [String]

Explanation LicenseConfig was not accessible or the license object does not exist

Recommended Action Investigate as required

Error Message
MIVR-LIB_LICENSE- 3 -LICENSE_VM_CONFIG_ERROR : OVA Template Mismatched. VM configuration does not match the OVA Profile..

Explanation OVA Template Mismatched. VM configuration does not match the OVA Profile.

Recommended Action Please refer to the Unified CCX Virtualization DocWiki for the supported VM configurations.

Error Message
MIVR-LIB_LICENSE- 6 -NO_LICENSE : No Licenses were found. Error reason [String]

Explanation objFile returned from LDAP is null or it does not contain any valid licenses

Recommended Action No actions needed

Error Message
MIVR-LIB_LICENSE- 2 -LICENSE_PACKAGE_NONE : Upload a valid license through the Cisco Unified CCX Application Administration.. Error reason [String]

Explanation Cisco Unified CCX license package is None.Upload a valid license through Cisco Unified CCX Application Administration.

Recommended Action Verify and update the licences

Error Message
MIVR-LIB_LICENSE- 3 -RMI_LICENSE_ERROR : RMI Remote License error. Exception [String]

Explanation A problem occurred while trying to register RMI Remote License Implementation

Recommended Action Verify the RMI configuration and restart server

Error Message
MIVR-LIB_LICENSE- 3 -LICENSE_REPOSITORY_UNAVAILABLE_ERROR : Config repository inaccessible. Exception [String]

Explanation A problem occurred when trying to read licenses from the Config repository

Recommended Action Investigate as required

Error Message
MIVR-LIB_LICENSE- 3 -LICENSE_CONFIG_ERROR : Access license config error. Exception [String]

Explanation A problem occurred when trying to retrieve licenses from the license config object

Recommended Action Investigate as required

Error Message
MIVR-LIB_LICENSE- 3 -LICENSE_READ_ERROR : License read error. Exception [String]

Explanation A problem occurred when trying to read license files

Recommended Action Investigate as required

Error Message
MIVR-LIB_LICENSE- 3 -LICENSE_REPOSITORY_ERROR : License Repository error. Exception [String]

Explanation A problem occurred when trying to read licenses from the Config repository

Recommended Action Investigate as required

Error Message
MIVR-LIB_LICENSE- 6 -LICENSE_INFO : License Information. Licenses [String]

Explanation The cluster was configured with the specified licenses enabled.

Recommended Action No actions needed

Error Message
MIVR-LIB_LICENSE- 3 -LICENSE_TIME_EXPIRED : Upload a valid license through the Cisco Unified CCX Application Administration.. Error reason [String]

Explanation One or More Temporary License(s) have expired. The corresponding features would become unusable. Please upload valid license for the same through Cisco Unified CCX Application Administration.

Recommended Action Verify and update the licences

Error Message
MIVR-LIB_MEDIA- 3 -PROB_STOP_RECORDING : Exception in recording. Exception [String]

Explanation recording exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-LIB_MEDIA- 6 -PROMPT_STREAM_ERROR_IGNORED : Prompt Stream error ignored. Exception [String]

Explanation Prompt Stream error ignored, because of continueOnPromptError=true

Recommended Action Verify that prompt stream has right audio format

Error Message
MIVR-LIB_MEDIA- 4 -BACK_THREAD_STOPPED : Background thread stopped during prompt. Exception [String]

Explanation Background thread stopped during prompt due to the exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-LIB_MEDIA- 3 -PROB_READ_RTP_STREAM : Exception in read(). Exception [String]

Explanation read exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-LIB_MEDIA- 6 -RTP_PROPERTIES_REASSIGNED : RTP Properties Reassigned. Method Name [String] HOST NAME [String] PORT NUMBER [Int] PACKET SIZE [Int]

Explanation RTP Properties Has Been Reassigned

Recommended Action No actions needed

Error Message
MIVR-LIB_MEDIA- 3 -PROB_WRITE_DATA_TO_DISK : Exception in run(). Exception [String]

Explanation run exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-LIB_MEDIA- 3 -PROB_APPEND_STREAM_DATA : Exception in run(). Exception [String]

Explanation run exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-LIB_MEDIA- 3 -UNABLE_START_PROMPT : Could not start prompt. Exception [String]

Explanation Could not start prompt due to the exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-LIB_MEDIA- 3 -PROB_CLOSE_INP_STR : Problem closing input stream. Exception [String]

Explanation Problem closing input stream for prompt due to the exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-LIB_MEDIA- 3 -MEDIA_STRM_NOT_STARTED : Media stream not started. Exception [String]

Explanation The Media stream was not started

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_MEDIA- 4 -PROB_READ_PROMPT_STREAM : Problem while reading prompt input stream. Exception [String]

Explanation Problem while reading prompt input stream

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_MEDIA- 3 -PROB_START_RECORDING : Exception in recording. Exception [String]

Explanation recording exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-LIB_MEDIA- 3 -FAIL_SEND_SID_PCKT : Failed to send SID packet. All Call ids [String] Exception [String] Media Stream Info [String]

Explanation Failed to send SID packet due to the exception, Stream info is attached

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-LIB_MEDIA- 3 -FAILURE_SOCKET_ALLOC : Failure in socket allocation. Exception [String]

Explanation Failure in socket allocation for streaming due to the exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-LIB_MEDIA- 4 -PROB_RESET_PROMPT_STREAM : Problem while resetting prompt input stream. Exception [String]

Explanation Problem while resetting prompt input stream in DBIS.resetSources()

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LIB_MEDIA- 3 -PROMPT_ERROR_IGNORED : Prompt error ignored. Exception [String]

Explanation Prompt error ignored, because of continueOnPromptError=true

Recommended Action Verify that prompt exist and has right audio format

Error Message
MIVR-LIB_MEDIA- 3 -STREAM_ABORTED : Stream aborted due to problem while sending packets. All Call ids [String] Exception [String] Media Stream Info [String]

Explanation Stream aborted due to problem while sending packets due to the exception, Stream info is attached

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-LIB_MEDIA- 3 -PROBLEM_FILL_BUFFER : Problem filling buffer. Failure reason for the associated error [String] Exception [String]

Explanation Problem filling buffer

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-LIB_MEDIA- 3 -FAILURE_PREPARE_PROMPT : Failure preparing to play prompt. Exception [String]

Explanation Failure preparing to play prompt in PromptPlayer due to the exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-LIB_RMI- 5 -RMI_LOG_MONITOR_FAIL : RMI log configuration monitoring failure.

Explanation RMI layer can no longer monitor dynamic update to its log configuration; debug messages disabled

Recommended Action No actions needed

Error Message
MIVR-LIB_SERVLET- 6 -MSG : . Message [String] Exception [String]

Explanation See log message for more info.

Recommended Action Investigate as required

Error Message
MIVR-LIB_SERVLET- 6 -MMSG : . Module [String] Message [String] Exception [String]

Explanation See module's log message for more info.

Recommended Action Investigate as required

Error Message
MIVR-LIB_TC- 6 -MSG : . Message [String] Exception [String]

Explanation See log message for more info.

Recommended Action Investigate as required

Error Message
MIVR-LIB_TC- 6 -MMSG : . Module [String] Message [String] Exception [String]

Explanation See module's log message for more info.

Recommended Action Investigate as required

Error Message
MIVR-LIB_TPL- 6 -TPL_INFO : TPL_LOG4J Info log. A specific description for a trace [String]

Explanation TPL_LOG4J Info log

Recommended Action No actions needed

Error Message
MIVR-LIB_TPL- 3 -TPL_ERROR : Error in ThirdParty library. A specific description for a trace [String] A description for the nature of the exception [String] Exception [String]

Explanation Error in ThirdParty library

Recommended Action No actions needed

Error Message
MIVR-LIB_TPL- 5 -TPL_LOG4J_LOG_MONITOR_FAIL : TPL log configuration monitoring failure.

Explanation TPL logs layer can no longer monitor dynamic update to its log configuration; debug messages disabled

Recommended Action No actions needed

Error Message
MIVR-LIB_TPL- 6 -TPL_LOG4J_LOG_MONITOR : TPL log. message [String] error_desc [String]

Explanation Hibernate and Atomikos logs

Recommended Action No actions needed

Error Message
MIVR-LOG_MGR- 2 -MGR_PARTIAL_SERVICE : Log Manager in partial service.

Explanation The Log Manager is in partial service; logs won't be completely availablew

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LOG_MGR- 3 -XML_PARSING_ERROR : XML parsing error. Catalog [String] Public identifier [String] System identifier [String] Line number [Int] Column number [Int] Exception [String] Nested Exception [String]

Explanation The log manager could not parse the XML log catalog

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LOG_MGR- 6 -MGR_IN_SERVICE : Log Manager in service.

Explanation The Log Manager is in service

Recommended Action No actions needed

Error Message
MIVR-LOG_MGR- 4 -INTERRUPT : Log generation interrupted. Catalog [String] Mnemonic [String] Exception [String]

Explanation The generation of a log was interrupted

Recommended Action Restart server

Error Message
MIVR-LOG_MGR- 4 -LOG_CFG_MONITOR_FAIL : Log levels configuration monitoring failure. Exception [String]

Explanation The Log Manager can no longer monitor dynamic update to the log levels configuration; tracing can no longer be turned on or off

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LOG_MGR- 4 -TO_STRING_FAILURE : Log toString() conversion failure. Catalog [String] Mnemonic [String] Parameter index [Int] Exception [String]

Explanation The log writer is unable to convert the given parameter in the specified log to a string

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-LOG_MGR- 5 -MGR_SHUTDOWN : Log Manager in shutdown.

Explanation The Log Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-LOG_MGR- 6 -MGR_INITIALIZING : Log Manager initializing.

Explanation The Log Manager is initializing

Recommended Action No actions needed

Error Message
MIVR-LOG_MGR- 2 -MGR_OUT_OF_SERVICE : Log Manager in out of service.

Explanation The Log Manager is out of service; logs won't be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LOG_MGR- 5 -MGR_SHUTTING_DOWN : Log Manager shutting down.

Explanation The Log Manager is in the process of shutting down; pending logs are being flushed out

Recommended Action No actions needed

Error Message
MIVR-LOG_MGR- 3 -UNABLE_LOAD_CATALOG : Unable to load log catalog. Catalog [String] Exception [String] Nested Exception [String]

Explanation The log manager could not load the log catalog

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-LOG_MGR- 6 -CATALOG_LOADED : Log catalog loaded. Catalog [String]

Explanation The specified log catalog was loaded in memory

Recommended Action No actions needed

Error Message
MIVR-LOG_MGR- 3 -WRITER_FAILURE : Log writer failure. Catalog [String] Exception [String]

Explanation The log writer failed to properly initialize for the log catalog

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-MGR_MGR- 6 -MGR_ALREADY_INIT : Manager initialization failed. Exception [String]

Explanation A manager in the Manager Manager failed to initialize because it has already been loaded.

Recommended Action Investigate as required

Error Message
MIVR-MGR_MGR- 1 -MGR_PARTIAL_SERVICE : Manager Manager in partial service.

Explanation Some managers are currently out of service

Recommended Action Investigate as required

Error Message
MIVR-MGR_MGR- 2 -NETWORK_FAILURE_DETECTED : lookup on local host resolved to loopback address. Please check network connectivity.

Explanation lookup on local host resolved to loopback address. Please check network connectivity.

Recommended Action Investigate as required

Error Message
MIVR-MGR_MGR- 1 -MGR_CONFIG_ERROR : Error while reading configuration file for ManagerManager. Exception [String]

Explanation Error while reading configuration file for ManagerManager

Recommended Action Verify and update the configuration and restart server

Error Message
MIVR-MGR_MGR- 3 -MGR_XML_PARSE_ERROR : Could not create URL while parsing xml data. Exception [String]

Explanation Could not create URL while parsing xml data

Recommended Action Verify and update the configuration and restart server

Error Message
MIVR-MGR_MGR- 1 -RMI_FAILURE_RETRY : RMI could not be configured at the specified port. Will attempt to retry.. Exception [String]

Explanation RMI could not be configured at the specified port. Will attempt to retry.

Recommended Action Verify the RMI configuration and restart server

Error Message
MIVR-MGR_MGR- 3 -THREAD_DEATH_EXCEPTION : An uncaught exception has be thrown in a thread. Thread name [String] Exception [String]

Explanation An uncaught exception has be thrown in a thread

Recommended Action Investigate as required

Error Message
MIVR-MGR_MGR- 0 -MGRMGR_KEEPALIVE_EXCPT : A KeepAlive exception has been thrown in Manager Manager. Exception [String]

Explanation A KeepAlive exception has been thrown in Manager Manager

Recommended Action Investigate as required

Error Message
MIVR-MGR_MGR- 0 -MGRMGR_START_FAIL : Fail to start Application startable class. Exception [String]

Explanation Manager Manager fail to start the startable class

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-MGR_MGR- 4 -CLASSPATH_NOT_LOADED : A classpath was not loaded during initialization. Exception [String]

Explanation A classpath was not loaded during initialization

Recommended Action No actions needed

Error Message
MIVR-MGR_MGR- 6 -MGR_INITIALIZING : Manager Manager initializing.

Explanation The Manager Manager is initializing

Recommended Action No actions needed

Error Message
MIVR-MGR_MGR- 2 -MGR_OUT_OF_SERVICE : Manager Manager in out of service.

Explanation All primary managers are out of service

Recommended Action Investigate as required

Error Message
MIVR-MGR_MGR- 3 -MANAGER_INTERCEPT_ERROR : Manager interceptor error operation. Error reason [String] Exception [String]

Explanation Manager interceptor encountered an error while performing the following operation

Recommended Action No actions needed

Error Message
MIVR-MGR_MGR- 0 -MGRMGR_INIT_FAIL : Fail to initialize Manager Manager and start main thread. Exception [String]

Explanation Fail to initialize Manager Manager and start main thread

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-MGR_MGR- 6 -MGR_IN_SERVICE : Manager Manager in service.

Explanation The Manager Manager is in service

Recommended Action No actions needed

Error Message
MIVR-MGR_MGR- 0 -APP_SVC_INIT_ERROR : Application services initialization error. Exception [String]

Explanation The Application services could not be initialized because the RMI registry could not be accessed

Recommended Action Verify the RMI configuration and restart server

Error Message
MIVR-MGR_MGR- 6 -MGRMGR_PERFMON_INIT_SUCCESS : Application successfully initialized perfmon dll.

Explanation The Application services loaded the WFCCNPerfWin32 dll

Recommended Action No actions needed

Error Message
MIVR-MGR_MGR- 1 -BOOTSTRAP_INIT_ERROR : Error occurred while initializing bootstrap information. Exception [String]

Explanation Error occurred while initializing bootstrap information

Recommended Action Verify and update the configuration and restart server

Error Message
MIVR-MGR_MGR- 1 -CURRENCY_CFG_MONITOR_FAIL : Currency configuration monitoring failure. Exception [String]

Explanation The system default currency can no longer be updated dynamically

Recommended Action Investigate as required

Error Message
MIVR-MGR_MGR- 1 -WEB_SERVICE_ERROR : Web service initialization error. Error reason [String]

Explanation Web service initialization error

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-MGR_MGR- 4 -IP_HOSTNAME_UPDATE : Host Name of one of the UCCX Servers in cluster is changed. Old Host Name [String] New Host Name [String]

Explanation Host Name of one of the UCCX Servers in cluster is changed

Recommended Action No actions needed

Error Message
MIVR-MGR_MGR- 3 -CLASSPATH_NOT_FOUND : Configured classpath is not found. Exception [String]

Explanation Configured classpath is not found

Recommended Action Verify and update the configuration and restart server

Error Message
MIVR-MGR_MGR- 3 -HOSTFILE_ERROR : An error occurred while trying to access host file. Exception [String]

Explanation An error occurred while trying to access host file

Recommended Action Verify and update the configuration

Error Message
MIVR-MGR_MGR- 3 -MGRMGR_ROOTDIR_ERROR : No root directory path found in properties file.

Explanation No root directory path found in properties file

Recommended Action No actions needed

Error Message
MIVR-MGR_MGR- 1 -HIGH_MEM_USAGE : JVM heap memory usage is high. Facility [String] Current usage [String] Maximum available [String] percentage Old Gen Memory used [Int]

Explanation JVM heap memory usage is high

Recommended Action Investigate as required

Error Message
MIVR-MGR_MGR- 5 -MGRMGR_KEEPALIVE_EXCPT_CANCEL : Manager Manager is attempting to cancel KeepAlive exception. Exception [String]

Explanation KeepAlive exception is cancelled in ManagerManager because the manager in question return from a timeout. Note that this does not mean Node Manager did not detect the KeepAlive exception. It might be that Node Manager detected the exception while ManagerManager is cancelling it.

Recommended Action No actions needed

Error Message
MIVR-MGR_MGR- 1 -APP_CFG_SYNC_FAIL : Application configuration failure. Exception [String]

Explanation The Manager Manager could not retrieve configuration information from the Config Framework. Using local configuration.

Recommended Action Investigate as required

Error Message
MIVR-MGR_MGR- 1 -RMI_PORT_CONFIGURATION_FAILURE : Failed to configure new rmi port. Old Port [String] New Port [String]

Explanation Cannot modify rmi port to the configured value since port is in use by another application. Please change rmi port configuration using CRS Administrator.

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-MGR_MGR- 6 -DEFAULT_CURRENCY_UPDATE : System default currency updated. Currency [String]

Explanation The system default currency was updated

Recommended Action No actions needed

Error Message
MIVR-MGR_MGR- 5 -MGR_SHUTTING_DOWN : Manager Manager in shutting down.

Explanation The Manager Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-MGR_MGR- 1 -REGISTRY_INIT_ERROR : An error occurred during initialization of registry. Exception [String]

Explanation RMI Registry could not be initialized.

Recommended Action Verify the RMI configuration and restart server

Error Message
MIVR-MGR_MGR- 4 -CUSTOM_PROP_NOT_FOUND : CustomFileClasspath.properties file is not found.

Explanation CustomFileClasspath.properties file is not found

Recommended Action No actions needed

Error Message
MIVR-MGR_MGR- 1 -REGISTRY_RETRY_ERROR : Maximum retries reached trying to create registry. No registry created.. Registry retry value [String]

Explanation Maximum retries reached trying to create registry. No registry created.

Recommended Action Verify the RMI configuration and restart server

Error Message
MIVR-MGR_MGR- 6 -REGISTRY_RETRY_INFO : Could not create registry at specified port. Will retry at different port. Port [String]

Explanation ManagerManager could not create registry at specified port. Will retry at different port

Recommended Action No actions needed

Error Message
MIVR-MGR_MGR- 1 -BOOTSTRAP_SYNC_ERROR : ManagerManager bootstrap sync failure. Exception [String]

Explanation ManagerManager cannot synchronize the bootstrap information due to the following problem

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-MGR_MGR- 4 -MANAGER_INTERCEPT_WARNING : Manager interceptor warning. Reason for this warning [String]

Explanation Manager interceptor warning log info

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-MGR_MGR- 1 -APP_CFG_MONITOR_FAIL : Application configuration monitoring failure. Exception [String]

Explanation The Manager Manager can no longer monitor dynamic update to some of its configuration

Recommended Action Investigate as required

Error Message
MIVR-MGR_MGR- 1 -MGR_INIT_ERROR : Manager initialization error. Exception [String]

Explanation A manager in the Manager Manager cannot be instantiated and will not be available

Recommended Action Investigate as required

Error Message
MIVR-MGR_MGR- 0 -UNRECOVERABLE_ERROR : An unrecoverable error has occurred. Exception [String]

Explanation An unrecoverable error has occurred

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-MGR_MGR- 3 -MGRMGR_SHUTDOWN_FAIL : An exception occurred while shutting down Manager Manager. Exception [String]

Explanation An exception occurred while shutting down Manager Manager

Recommended Action Investigate as required

Error Message
MIVR-MGR_MGR- 5 -MGR_SHUTDOWN : Manager Manager in shutdown.

Explanation The Manager Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-MGR_MGR- 4 -IP_ADDRESS_UPDATE : IP Address of one of the UCCX Servers in cluster is changed. Old IP Address [String] New IP Address [String]

Explanation IP Address of one of the UCCX Servers in cluster is changed

Recommended Action No actions needed

Error Message
MIVR-MGR_MGR- 3 -MGRMGR_BEAN_ERROR : Error setting design time bean. Exception [String]

Explanation There was an error setting the design time bean

Recommended Action No actions needed

Error Message
MIVR-MGR_MGR- 0 -THREADS_DUMP : Java Virtual Machine Threads Dump. Message [String] Exception [String]

Explanation A dump of all running threads was just produced in JVM.log. Collect all existing logs and the JVM.log file and forward them to Cisco.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-MGR_MGR- 3 -GET_DEFAULT_USER_ERROR : Default User could not be retrieved. Exception [String]

Explanation Default User could not be retrieved due to the following error

Recommended Action No actions needed

Error Message
MIVR-MGR_MGR- 1 -MEMORY_USAGE_EXCEEDED_THRESHOLD : Memory usage exceeded the threshold set. Facility [String] Current usage [String] Maximum available [String] percentage Heap memory used [Int]

Explanation Memory usage exceeded the threshold set

Recommended Action Investigate as required

Error Message
MIVR-MGR_MGR- 1 -SYS_CFG_SYNC_FAIL : System configuration failure. Exception [String]

Explanation The Manager Manager could not retrieve system configuration from the Config Framework. Using local configuration.

Recommended Action Investigate as required

Error Message
MIVR-MGR_MGR- 1 -RMI_CREATE_ERROR : Cannot create rmi registry at specified port location. Port [String] Exception [String]

Explanation Cannot create rmi registry at specified port location since port is in use by another application. Please change rmi port configuration using CRS Administrator or shutdown the process using the specified port.

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-MGR_MGR- 1 -SYS_CFG_MONITOR_FAIL : System configuration monitoring failure. Exception [String]

Explanation The Manager Manager can no longer monitor dynamic update to the system configuration

Recommended Action Investigate as required

Error Message
MIVR-NODE_MGR- 3 -NODE_MGR_STOPNODE_ERROR : Can't stop and restart the node manager and its controlled processes. Exception [String]

Explanation Can't stop and restart the node manager and its controlled processes

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-NODE_MGR- 3 -NODE_MGR_SERVICE_START_ERROR : Can't start service. service name [String] Exception [String]

Explanation Can't start service

Recommended Action Retry the operation and if problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-NODE_MGR- 3 -NODE_MGR_REMOVE_LISTENER_ERROR : Could not remove Node listener. Exception [String]

Explanation Could not remove node listener from node manager

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-NODE_MGR- 0 -NODE_MGR_SERVICE_CRASH_DETECTED : Node manager detected service crash. service name [String]

Explanation Node manager detected service crash

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-NODE_MGR- 1 -NODE_MGR_DESTROY_ERROR : Destroy Node Manager failed. Exception [String]

Explanation Destroy the native node manager failed

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-NODE_MGR- 1 -MEDIASENSE_STATUS_DOWN : One or more configured Mediasense nodes are down or unreachable from this CCX..

Explanation One or more configured Mediasense nodes are down or unreachable from this CCX.

Recommended Action Bring Mediasense node(s) UP, then update Recording Server Configuration to re-subscribe CCX for Mediasense session events.

Error Message
MIVR-NODE_MGR- 3 -NODE_MGR_SERVICE_ACTIVATE_ERROR : Can't activate the service. service name [String] Exception [String]

Explanation Can't activate the service

Recommended Action Retry the operation and if problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-NODE_MGR- 3 -NODE_MGR_SERVICE_DEACTIVATE_ERROR : Can't deactivate the service. process name [String] Exception [String]

Explanation Can't deactivate the service

Recommended Action Retry the operation and if problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-NODE_MGR- 3 -NODE_MGR_SETFAILUREREASON_ERROR : Set service failure reason failed. Exception [String]

Explanation Set a service failure reason to display in Unified CCX Administration failed

Recommended Action No actions needed

Error Message
MIVR-NODE_MGR- 3 -NODE_MGR_STARTNODE_ERROR : Can't start the node manager and its controlled processes. opeartion failure source [String]

Explanation Can't start the node manager and its controlled processes

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-NODE_MGR- 1 -NODE_MGR_KEEP_ALIVE_ERROR : Node Manager keep alive ping failed. Exception [String]

Explanation Node manager keep alive ping failed

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-NODE_MGR- 3 -NODE_MGR_SERVICE_RESTART_ERROR : Can't restart service. service name [String] Exception [String]

Explanation Can't restart service

Recommended Action Retry the operation and if problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-NODE_MGR- 0 -NODE_MGR_SERVICE_MONITOR_THREAD_FAILED : Node manager service Monitor thread failed. Exception [String]

Explanation Node manager service Monitor thread failed

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-NODE_MGR- 3 -NODE_MGR_SERVICE_STOP_ERROR : Can't stop service. service name [String] Exception [String]

Explanation Can't stop service

Recommended Action Retry the operation and if problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-NODE_MGR- 0 -GENERAL_JVM_DEADLOCK_ERROR : A JVM deadlock has been detected. Exception [String]

Explanation A JVM deadlock has been detected. Copy out any JVM.log under log/MCVD MADM MIVR directory

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-NODE_MGR- 3 -NODE_MGR_ADD_LISTENER_ERROR : Could not add Node listener. Exception [String]

Explanation Could not add node listener to node manager

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-PROMPT_MGR- 1 -MGR_PARTIAL_SERVICE : Prompt Manager in partial service.

Explanation The Prompt Manager is in partial service; synchronization of files with prompt repository is in progress

Recommended Action Investigate as required

Error Message
MIVR-PROMPT_MGR- 3 -INVALID_TTS_PROVIDER : Invalid TTS prompt provider. Name [String] Exception [String]

Explanation The specified TTS prompt provider is invalid

Recommended Action Verify and update the configuration

Error Message
MIVR-PROMPT_MGR- 2 -INVALID_USER_DIR : Invalid user prompt directory configured. Directory [String] Exception [String]

Explanation The configured user prompt directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-PROMPT_MGR- 3 -UNDEFINED_GENERATED_PROMPT : Undefined generated prompt. Generated Prompt [String] Language [String] Exception [String]

Explanation Unable to resolve the generated prompt

Recommended Action Verify and update the application and if problem persist contact Cisco technical assistance center

Error Message
MIVR-PROMPT_MGR- 6 -GENERATOR_FALLBACK : Falling back to system prompt generators. Generated Prompt [String] Generator Constructor [String] Bundle [String] Language [String] Exception [String]

Explanation The Prompt Manager failed to use the prompt generator bundle specified by the generated prompt and is falling back to the systemprompt generators

Recommended Action Verify and update the application

Error Message
MIVR-PROMPT_MGR- 3 -UNSUPPORTED_PROMPT : Unsupported prompt type. Name [String] Type [String] Language [String] Exception [String]

Explanation The specified prompt type is not supported

Recommended Action Verify and update the application

Error Message
MIVR-PROMPT_MGR- 3 -PROMPT_LEXICAL_ERROR : Template prompt lexical error. Name [String] Template [String] Language [String] Exception [String]

Explanation The specified lexical error occured while parsing a template prompt

Recommended Action Verify and update the application

Error Message
MIVR-PROMPT_MGR- 3 -UNDEFINED_NAME_PROMPT : Undefined user or system prompt. Name [String] Type [String] Transcription [String] Language [String] Exception [String]

Explanation A user or system prompt cannot be located

Recommended Action Verify and update the configuration

Error Message
MIVR-PROMPT_MGR- 3 -UNDEFINED_TTS_PROMPT : Undefined TTS prompt. Name [String] Transcription [String] Language [String] Exception [String]

Explanation A TTS prompt cannot be generated

Recommended Action Verify and update the configuration and restart server

Error Message
MIVR-PROMPT_MGR- 3 -UNDEFINED_SILENCE_PROMPT : Undefined silence prompt. Silence Duration [Long] Exception [String]

Explanation A silence prompt cannot be located

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-PROMPT_MGR- 3 -PROMPT_FILE_SUPPORT_FAILURE : Prompt file support failure. Exception [String]

Explanation The Prompt Manager can not register file support for user prompt files; user prompts will not be synchronized on local server

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-PROMPT_MGR- 6 -MGR_INITIALIZING : Prompt Manager initializing.

Explanation The Prompt Manager is initializing

Recommended Action No actions needed

Error Message
MIVR-PROMPT_MGR- 2 -MGR_OUT_OF_SERVICE : Prompt Manager in out of service.

Explanation The Prompt Manager is out of service; prompts won't be accessible

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-PROMPT_MGR- 5 -MGR_SHUTTING_DOWN : Prompt Manager shutting down.

Explanation The Prompt Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-PROMPT_MGR- 6 -SYSTEM_TTS_PROVIDER : System TTS provider registered. Name [String]

Explanation A system TTS prompt provider has been registered

Recommended Action No actions needed

Error Message
MIVR-PROMPT_MGR- 6 -MGR_IN_SERVICE : Prompt Manager in service.

Explanation The Prompt Manager is in service

Recommended Action No actions needed

Error Message
MIVR-PROMPT_MGR- 5 -MGR_SHUTDOWN : Prompt Manager in shutdown.

Explanation The Prompt Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-PROMPT_MGR- 3 -UNABLE_CREATE_TTS : Unable to instantiate TTS prompt provider. Name [String] Classname [String] Exception [String]

Explanation The specified TTS prompt provider cannot be located or instantiated

Recommended Action Verify and update the configuration and restart server

Error Message
MIVR-PROMPT_MGR- 3 -PROMPT_PARSING_ERROR : Template prompt parsing error. Name [String] Template [String] Language [String] Exception [String]

Explanation The specified error occured while parsing a template prompt

Recommended Action Verify and update the application

Error Message
MIVR-PROMPT_MGR- 6 -NO_SYSTEM_TTS_PROVIDER : No system TTS provider registered.

Explanation There is no system TTS prompt provider currently registered

Recommended Action Verify and update the configuration

Error Message
MIVR-PROMPT_MGR- 6 -TTS_PROVIDER_FALLBACK : Falling back to system configured TTS provider. Transcription [String] Language [String] Name [String] Exception [String]

Explanation The Prompt Manager failed to use the TTS prompt provider specified by the TTS prompt and is falling back to the system TTS prompt provider

Recommended Action Verify and update the application

Error Message
MIVR-PROMPT_MGR- 3 -UNDEFINED_GENERATOR : Undefined prompt generator. Generated Prompt [String] Generator Constructor [String] Bundle [String] Language [String] Exception [String]

Explanation The Prompt Manager failed to locate a prompt generator as requested

Recommended Action Verify and update the application and if problem persist contact Cisco technical assistance center

Error Message
MIVR-PROMPT_MGR- 3 -INVALID_GENERATOR : Invalid prompt generator. Generated Prompt [String] Generator Name [String] Generator Constructor [String] Language [String] Exception [String]

Explanation The Prompt Manager failed to instantiate the rquested prompt generator

Recommended Action Verify and update the application and if problem persist contact Cisco technical assistance center

Error Message
MIVR-PROMPT_MGR- 3 -WEBSERVICES_ERROR : Exception thrown while processing web services for Prompt. Exception [String]

Explanation Exception thrown while processing web services for Prompt

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-PROMPT_MGR- 2 -INVALID_SYSTEM_DIR : Invalid system prompt directory configured. Directory [String] Exception [String]

Explanation The configured system prompt directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-REST_CLIENT- 1 -UCCX_TO_CUIC_SYNC_FAILED : Notification to CUIC failed. UCCX TO CUIC SYNC failed for these resources::: [String]

Explanation Notification to CUIC on resource change failed

Recommended Action EXECUTE Resource sync command from CLI

Error Message
MIVR-RTPPORT_MGR- 2 -INVALID_RTPPORT : Invalid initial RTP port configured. Number [Int] Exception [String]

Explanation The configured initial RTP port is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-RTPPORT_MGR- 1 -MGR_PARTIAL_SERVICE : RTP Port Manager in partial service.

Explanation The RTP Port Manager is in partial service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-RTPPORT_MGR- 6 -INSTALLED_PAYLOAD_TYPES : The payload of the prompt installed on this system. Payload [String]

Explanation The payload of the prompt installed on this system

Recommended Action No actions needed

Error Message
MIVR-RTPPORT_MGR- 6 -MGR_IN_SERVICE : RTP Port Manager in service.

Explanation The RTP Port Manager is in service

Recommended Action No actions needed

Error Message
MIVR-RTPPORT_MGR- 6 -MGR_INITIALIZING : RTP Port Manager initializing.

Explanation The RTP Port Manager is initializing

Recommended Action No actions needed

Error Message
MIVR-RTPPORT_MGR- 2 -RTPPORT_CFG_ERROR : RTP port configuration failure. Exception [String]

Explanation The RTP Port Manager is unable to load its configuration

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-RTPPORT_MGR- 2 -MGR_OUT_OF_SERVICE : RTP Port Manager in out of service.

Explanation The RTP Port Manager is out of service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-RTPPORT_MGR- 5 -MGR_SHUTTING_DOWN : RTP Port Manager shutting down.

Explanation The RTP Port Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-RTPPORT_MGR- 5 -MGR_SHUTDOWN : RTP Port Manager in shutdown.

Explanation The RTP Port Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-RTPPORT_MGR- 2 -PAYLOAD_CFG_ERROR : RTP codec configuration failure. Exception [String]

Explanation The RTP Port Manager is unable to load its codec configuration

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-RTPPORT_MGR- 3 -INVALID_PAYLOAD_TYPE : Payload type supported in the system is invalid. Payload [String]

Explanation The specified system supported payload type is invalid

Recommended Action Reinstall server

Error Message
MIVR-RTPPORT_MGR- 6 -RECOVERY_DETECTED : RTP Port Manager detected an archive request in the system.

Explanation RTP Port Manager detected an archive request in the system

Recommended Action No actions needed

Error Message
MIVR-SCRIPT_MGR- 1 -MGR_PARTIAL_SERVICE : Script Manager in partial service.

Explanation The Script Manager is in partial service; synchronization of files with script repository is in progress

Recommended Action No actions needed

Error Message
MIVR-SCRIPT_MGR- 3 -STEP_COPY_FAILURE : Unable to copy a step. Script [String] Step id [Long] Step Class [String] Step Description [String] Exception [String]

Explanation The specified step could not be copied

Recommended Action Verify and update the configuration

Error Message
MIVR-SCRIPT_MGR- 3 -UNSUPPORTED_SCRIPT : Unsupported script type. Script [String] Type [String] Domain [String] Exception [String]

Explanation The specified script type is not supported

Recommended Action Verify and update the script

Error Message
MIVR-SCRIPT_MGR- 2 -INVALID_USER_DIR : Invalid user script directory configured. Directory [String] Exception [String]

Explanation The configured user script directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SCRIPT_MGR- 3 -INVALID_FINAL_CFG_VAR : Variable defined as a final variable. Application [String] Script [String] Variable [String] Exception [String]

Explanation The script variable is defined as final which cannot be modified

Recommended Action Verify and update the configuration

Error Message
MIVR-SCRIPT_MGR- 4 -HIDDEN_STEP_FOUND : Script contains an hidden step. Script [String] Step id [Long] Step Class [String] Step Description [String]

Explanation The specified script contains the specified hidden step

Recommended Action Load the script in the Unified CCX Editor and save it back; this will removethe hidden step

Error Message
MIVR-SCRIPT_MGR- 3 -INVALID_SCRIPT : Invalid script. Script [String] Exception [String]

Explanation The script configured is invalid and cannot be loaded

Recommended Action Verify and update the script

Error Message
MIVR-SCRIPT_MGR- 4 -CFG_VAR_NOT_DEFINED : Variable not defined in script. Application [String] Script [String] Variable [String]

Explanation A configured variable is not defined in the script

Recommended Action Verify and update the configuration

Error Message
MIVR-SCRIPT_MGR- 3 -SCRIPT_NOT_DEFINED : Script not defined. Script [String] Exception [String]

Explanation The specified script is not configured in the repository

Recommended Action Verify and update the script

Error Message
MIVR-SCRIPT_MGR- 3 -NOT_A_CFG_VAR : Variable not defined as a configuration variable. Application [String] Script [String] Variable [String]

Explanation A configured variable is not defined as a configuration variable in the script

Recommended Action Verify and update the configuration

Error Message
MIVR-SCRIPT_MGR- 2 -NO_SCRIPT_CTX : No context defined in script. Application [String] Script [String]

Explanation The specified script doesn't have a context of variables defined

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SCRIPT_MGR- 6 -MGR_INITIALIZING : Script Manager initializing.

Explanation The Script Manager is initializing

Recommended Action No actions needed

Error Message
MIVR-SCRIPT_MGR- 2 -MGR_OUT_OF_SERVICE : Script Manager in out of service.

Explanation The Script Manager is out of service; Scripts won't be accessible

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SCRIPT_MGR- 5 -MGR_SHUTTING_DOWN : Script Manager shutting down.

Explanation The Script Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-SCRIPT_MGR- 3 -RMI_REBIND_FAILED : Unable to register remote interface. Exception [String]

Explanation A remote interface could not be bound to the RMI registry; remote access for dynamic update or other functions will not be available

Recommended Action Verify the RMI configuration and restart server

Error Message
MIVR-SCRIPT_MGR- 6 -MGR_IN_SERVICE : Script Manager in service.

Explanation The Script Manager is in service

Recommended Action No actions needed

Error Message
MIVR-SCRIPT_MGR- 3 -CUSTOMIZER_ERROR : Exception thrown while processing customizer of a step in Script. Application [String] Script [String]

Explanation Exception thrown while processing customizer of a step in Script

Recommended Action Verify and update the configuration

Error Message
MIVR-SCRIPT_MGR- 5 -MGR_SHUTDOWN : Script Manager in shutdown.

Explanation The Script Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-SCRIPT_MGR- 3 -UNABLE_LOAD_SCRIPT : Unable to load script. Script [String] Exception [String]

Explanation The script manager could not load the specified script

Recommended Action Verify and update the script

Error Message
MIVR-SCRIPT_MGR- 3 -INVALID_LICENSES : Invalid licenses. Script [String] Exception [String]

Explanation The script configured cannot be loaded because of missing licenses

Recommended Action Verify and update the licences

Error Message
MIVR-SCRIPT_MGR- 3 -INCOMPATIBLE_CFG_VAR_TYPES : Incompatible configuration variable types. Application [String] Script [String] Variable [String] Variable type defined [String] Variable type configured [String] Exception [String]

Explanation A configured variable type is incompatible with the variable defined script

Recommended Action Verify and update the configuration

Error Message
MIVR-SCRIPT_MGR- 3 -UNDEFINED_NAME_SCRIPT : Undefined user or system script. Script [String] Type [String] Domain [String] Exception [String]

Explanation A user or system script cannot be located

Recommended Action Verify and update the configuration

Error Message
MIVR-SCRIPT_MGR- 3 -CORRUPTED_SCRIPT : The script is corrupted. Script [String] Exception [String]

Explanation The specified script or the last script that the system attempted to load is corrupted and cannot be sucessfully loaded

Recommended Action Please Contact Cisco technical assistance center to recover the script

Error Message
MIVR-SCRIPT_MGR- 3 -WEBSERVICES_ERROR : Exception thrown while processing web services for Script. Exception [String]

Explanation Exception thrown while processing web services for Script

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SCRIPT_MGR- 2 -INVALID_SYSTEM_DIR : Invalid system script directory configured. Directory [String] Exception [String]

Explanation The configured system script directory is invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SCRIPT_MGR- 3 -SCRIPT_FILE_SUPPORT_FAILURE : Script file support failure. Exception [String]

Explanation The Script Manager can not register file support for script files; scripts will not be accesible from the script repository

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SECURITY_MGR- 2 -SECURITY_VIOLATION : Security violation. Permission Name [String] Permission Action [String] Application [String] Script [String] Step id [Long] Step Class [String] Step Description [String] Expression [String] Exception [String]

Explanation The Security Manager has detected the following security violation

Recommended Action Verify and update the script

Error Message
MIVR-SECURITY_MGR- 6 -MGR_IN_SERVICE : Security Manager in service.

Explanation The Security Manager is in service

Recommended Action No actions needed

Error Message
MIVR-SECURITY_MGR- 5 -INVALID_LOCATION : Invalid File Path. location [String]

Explanation Invalid File Path sent for read Permission

Recommended Action No actions needed

Error Message
MIVR-SECURITY_MGR- 3 -RUNTIME_ERROR : Runtime Error. Permission Name [String] Permission Action [String] Exception [String]

Explanation The Security Manager has detected runtime error

Recommended Action No actions needed

Error Message
MIVR-SESSION_MGR- 2 -DEADLOCK_DETECTED : Potential deadlock detected. Session id [Long] Contact id [Int] Contact implementation id [String] Contact Class [String] Contact Type [String] Thread [String]

Explanation Potential deadlock detected for the specified session/contact and thread

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SESSION_MGR- 4 -DETECTION_ERROR : Unexpected error in deadlock detection thread. Exception [String]

Explanation The deadlock detection thread detected and unexpected error

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SESSION_MGR- 6 -DEADLOCK_AVOIDED : Potential deadlock avoided. Session id [Long] Contact id [Int] Contact implementation id [String] Contact Class [String] Contact Type [String] Thread [String]

Explanation Potential deadlock avoided for the specified session/contact and thread

Recommended Action No actions needed

Error Message
MIVR-SESSION_MGR- 1 -DEADLOCK_COUNT_EXCEEDED : Deadlock count exceeded. Deadlock info [String]

Explanation Deadlock count exceeded

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SOCKET_MGR- 1 -MGR_PARTIAL_SERVICE : Socket Manager in partial service.

Explanation The Socket Manager is in partial service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SOCKET_MGR- 6 -MGR_IN_SERVICE : Socket Manager in service.

Explanation The Socket Manager is in service

Recommended Action No actions needed

Error Message
MIVR-SOCKET_MGR- 4 -MISSING_RESOURCE : Missing socket resources. Facility [String] Sub-Facility [String] Socket allocator id [String] Exception [String]

Explanation The socket manager is unable to locate internal socket resources

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SOCKET_MGR- 5 -MGR_SHUTDOWN : Socket Manager in shutdown.

Explanation The Socket Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-SOCKET_MGR- 4 -REQUEST_TIMEOUT : Requesting a socket timed out. Facility [String] Sub-Facility [String] Socket allocator id [String] Mnemonic [String] Thread [String] Time [Long]

Explanation Request to get a socket timed out

Recommended Action No actions needed

Error Message
MIVR-SOCKET_MGR- 4 -REQUEST_FAILED : Requesting a socket failed. Facility [String] Sub-Facility [String] Socket allocator id [String] Mnemonic [String] Thread [String] Time [Long] Exception [String]

Explanation Request to get a socket failed

Recommended Action No actions needed

Error Message
MIVR-SOCKET_MGR- 4 -REQUEST_BLOCKED : Invoking blocked allocation handler. Facility [String] Sub-Facility [String] Socket allocator id [String] Mnemonic [String] Thread [String] Time [Long] Handler [String]

Explanation The specified blocked allocation handler is being invoked for the specified socket request as the allocator queue could not accept it

Recommended Action No actions needed

Error Message
MIVR-SOCKET_MGR- 6 -MGR_INITIALIZING : Socket Manager initializing.

Explanation The Socket Manager is initializing

Recommended Action No actions needed

Error Message
MIVR-SOCKET_MGR- 2 -MGR_OUT_OF_SERVICE : Socket Manager in out of service.

Explanation The Socket Manager is out of service; allocators won't be available

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SOCKET_MGR- 5 -MGR_SHUTTING_DOWN : Socket Manager shutting down.

Explanation The Socket Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-SS_CHAT- 3 -CHAT_SS_GENERIC_EXCEPTION : Unknown CHAT Subsystem Exception. Exception [String]

Explanation Unknown CHAT Subsystem Exception

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_CHAT- 1 -CHAT_SS_NOT_CONFIGURED : CHAT Subsystem not configured. Exception [String]

Explanation Check Social Miner configuration

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_CHAT- 6 -SS_INITIALIZING : CHAT Subsystem initializing.

Explanation The CHAT Subsystem is initializing

Recommended Action No actions needed

Error Message
MIVR-SS_CHAT- 5 -SS_SHUTDOWN : CHAT Subsystem is shutdown.

Explanation The CHAT Subsystem has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-SS_CHAT- 1 -SS_PARTIAL_SERVICE : CHAT Subsystem in partial service.

Explanation Some information could not be properly loaded from the repository

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_CHAT- 2 -SS_OUT_OF_SERVICE : CHAT Subsystem in out of service.

Explanation CHAT Subsystem is either disabled or failed to be loaded

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_CHAT- 5 -SS_SHUTTING_DOWN : CHAT Subsystem is shutting down.

Explanation The CHAT Subsystem is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-SS_CHAT- 1 -CHAT_SS_SOCIALMINER_EXCEPTION : CHAT Subsystem in partial service. Exception [String]

Explanation Social Miner is not reachable

Recommended Action Investigate as required

Error Message
MIVR-SS_CHAT- 0 -CHAT_SS_INIT_ERROR : CHAT Subsystem initialization error. Exception [String]

Explanation The CHAT Subsystem could not be initialized because (more than likely) the config could not be accessed

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_CHAT- 6 -SS_IN_SERVICE : CHAT Subsystem in service.

Explanation The CHAT Subsystem is in service

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 3 -SUBSYSTEM_CMT_GRP_REPOSITORY_DATA_NULL : Configuration data received by Subsystem CMT is null. Method Name [String]

Explanation Data Received From Group Repository Is Null

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_CMT- 6 -SUBSYSTEM_CMT_GRP_ADDED_CALLED : A CMT group needs to be added at configuration request. Method Name [String] GROUP ID [Int] GROUP TYPE [String] NUMBER CHANNEL [Int]

Explanation GroupAdded Method Called

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 5 -SS_SHUTDOWN : CMT subsystem is SHUTDOWN.

Explanation The CMT subsystem has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 6 -SUBSYSTEM_CMT_LOG_OBJECT_NOT_NULL : The log object used by the CTM Subsystem is not null.

Explanation Log object of the CMT Subsystem is not null

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 3 -SS_OUT_OF_SERVICE : CMT subsystem is OUT_OF_SERVICE.

Explanation CMT subsystem is either disabled or failed to be loaded

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_CMT- 3 -SUBSYSTEM_CMT_DESTROY_FAILED : Subsystem CMT failed to destroy itself during subsystem shutdown. Exception [String]

Explanation CMT Can Not Destroy itself During Shutdown

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 4 -SUBSYSTEM_CMT_DISPOSE_CHANNEL_FAILED : Attempt to dispose a CMT channel failed. Method Name [String] Exception [String]

Explanation CMT Failed to Dispose a Channel

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 3 -SUBSYSTEM_CMT_CLASS_DIALOGCHANNEL_NOT_FOUND : Class of DialogChannel not found. Method Name [String] DIALOG CHANNEL CLASS [String] Exception [String]

Explanation Class of DialogChannel Not Found

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_CMT- 6 -SUBSYSTEM_CMT_GROUP_ALREADY_EXIST : Configuration requests Subsystem CMT to create a CMT group that already exists. Method Name [String] GROUP ID [Int]

Explanation Group Already Exists

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 3 -SUBSYSTEM_CMT_DESTROY_GRP_FAILED : Subsystem CMT failed to destroy a CMT group during subsystem shutdown. Method Name [String] Exception [String]

Explanation CMT Can Not Destroy Group(s) During Shutdown

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 3 -MEDIA_MANAGER_ERROR : Media Manager Error. Exception [String]

Explanation Media Manager Error

Recommended Action Stop Media Driver, restart system, if problem persist contact Cisco

Error Message
MIVR-SS_CMT- 3 -SUBSYSTEM_CMT_CREATE_GRP_FAILED : Subsystem CMT has failed to create a CMT group. Method Name [String] GROUP TYPE [String] GROUP ID [Int] Exception [String]

Explanation Create Group Failed

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_CMT- 6 -SUBSYSTEM_CMT_REGISTER_SS_CMT_AS_GRP_LISTENER : Subsystem CMT registers itself as a group event listener. Method Name [String] cisco media channel [String]

Explanation CMT Registered Self As a Group Event Listener

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 4 -SS_PARTIAL_SERVICE : CMT subsystem is in PART_SERVICE.

Explanation The CMT subsystem is in partial service

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_CMT- 3 -SUBSYSTEM_CMT_DISPOSE_GROUP_FAILED : CMT subsystem failed to dispose group. Exception [String]

Explanation CMT Subsystem Failed To Dispose Group

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 6 -SUBSYSTEM_CMT_MODIFICATION_NOT_NEED : CMT group already has exact parameters requested by configuration. Method Name [String] GROUP ID [Int] GROUP TYPE [String]

Explanation Currently Has Exact Nbr of Channels As Reqired By App Admin

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 6 -SUBSYSTEM_CMT_REMOVE_GRP_LISTENER : Subsystem CMT removes itself as a Group event listener. Method Name [String] CHANNEL TYPE [String]

Explanation CMT Removes Self As a Group Listener

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 6 -SUBSYSTEM_CMT_GRP_REMOVED_CALLED : Configuration requests subsystem CMT to remove a CMT group. Method Name [String] GROUP ID [Int] GROUP TYPE [String]

Explanation GroupRemoved Method Called

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 6 -SS_IN_SERVICE : CMT subsystem IN_SERVICE.

Explanation The CMT subsystem is in full service

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 3 -SUBSYSTEM_CMT_INIT_FAILED : Subsystem CMT failed to initialize itself during subsystem startup. Exception [String]

Explanation CMT Can Not Initilizing itself During Startup

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 3 -SUBSYSTEM_CMT_CHANNEL_TYPE_NULL : Configuration has supplied a Null channel type. Method Name [String]

Explanation Channel Type is Null

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_CMT- 6 -SUBSYSTEM_CMT_GROUP_CREATED : Subsystem CMT has successfully created a CMT group. Method Name [String] GROUP ID [Int] GROUP TYPE [String] NUMBER CHANNEL [Int]

Explanation Group Created

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 6 -SUBSYSTEM_CMT_NEED_ADD_CHANNEL_TO_GROUP : Channels need to be added to a CMT group at configuration request. Method Name [String] GROUP ID [Int] GROUP TYPE [String] CHANNEL ADD [Int]

Explanation Notified By App Admin To Add More Channels

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 3 -SUBSYSTEM_CMT_CREATE_CHANNEL_FAILED : Subsystem CMT has failed to create a CMT channel. Method Name [String] CHANNEL TYPE [String] Exception [String]

Explanation Create Channel Failed

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_CMT- 3 -SUBSYSTEM_CMT_GROUP_TYPE_NOT_SUPPORTED : Configuration has specified a group type not supported by Subsystem CMT. Method Name [String] GROUP ID [Int] GROUP TYPE [String]

Explanation Group Type Not Supported

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_CMT- 6 -SS_INITIALIZING : CMT subsystem initializing.

Explanation The CMT subsystem is initializing

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 3 -SUBSYSTEM_CMT_ADD_CHANNEL_TO_GRP_FAILED : Attempt by Subsystem CMT to add a channel to a CMT group failed. Method Name [String] GROUP TYPE [String] GROUP ID [Int] channel count [Int] Exception [String]

Explanation Add Channel to Group Failed

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_CMT- 6 -SUBSYSTEM_CMT_CHANNEL_CREATED : Subsystem CMT has successfully created a CMT channel. Method Name [String] CHANNEL TYPE [String] CHANNEL ID [Int]

Explanation Channel Created

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 6 -SUBSYSTEM_CMT_GRP_DOES_NOT_EXIST : Configuration requests subsystem CMT to modify a CMT group that does not exist. Method Name [String] GROUP ID [Int] GROUP TYPE [String] NUMBER CHANNEL [Int]

Explanation The Group As Specified By App Admin Does Not Currently Exist

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 3 -SUBSYSTEM_CMT_SETSTATE_FAILED : Subsystem CMT failed to set state. Exception [String]

Explanation CMT Returns Error When Calling SetState

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 3 -SUBSYSTEM_CMT_LOG_OBJECT_NULL : The log object used by the CTM Subsystem is null.

Explanation Log object of the CMT Subsystem is null

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_CMT- 6 -SUBSYSTEM_CMT_DISPOSE_GRP : Subsystem CMT disposes a CMT group during subsystem shutdown. Method Name [String] GROUP ID [Int]

Explanation CMT Disposed This Group During Shutdown

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 4 -GET_USER_ID_ERROR : Get User ID Cause an error. Exception [String] DTMF KeyPad Mapping [String]

Explanation get User Id Error

Recommended Action Verify User record in the DC Directory, Contact Cisco if problem persist

Error Message
MIVR-SS_CMT- 3 -SUBSYSTEM_CMT_GET_DIALOGGROUP_CONFIG_FAILED : Subsystem CMT failed to retrieve dialog group config object. Exception [String]

Explanation CMT Failed To Retrieve Dialog Group Config Object

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 5 -SS_SHUTTING_DOWN : CMT subsystem is SHUTTING_DOWN.

Explanation The CMT subsystem is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 3 -MEDIA_MANAGER_CANT_CLOSE_STREAM : Media Manager could not close media streams. Exception [String] Stream Name [String]

Explanation Media Manager encoutred error(s) while closing the media streams, this could be related to media driver

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_CMT- 3 -SUBSYSTEM_CMT_GROUP_TYPE_NULL : Configuration requests Subsystem CMT to add, remove or modify a group with group type null. Method Name [String] GROUP ID [Int]

Explanation Group Type is Null

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_CMT- 6 -SUBSYSTEM_CMT_GRP_MODIFIED_CALLED : A CMT group needs to be modified at configuration request. Method Name [String] GROUP ID [Int] GROUP TYPE [String] NUMBER CHANNEL [Int]

Explanation GroupModified Method Called

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 6 -SUBSYSTEM_CMT_DIALOG_CTRL_GRP_CREATED : Subsystem CMT has successfully created a CMT group. Method Name [String] GROUP TYPE [String] GROUP ID [Int]

Explanation Dialog Control Group Created

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 4 -MEDIA_MANAGER_CLOSE_STREAM_EXCEPTION : Media Manager has exception while queuing the request for close stream , will reattempt now. Exception [String]

Explanation Media Manager could not queue the close stream task

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 6 -SUBSYSTEM_CMT_GRP_REMOVED : A CMT group has been removed from the Subsystem CMT. Method Name [String] GROUP TYPE [String] GROUP ID [Int]

Explanation Group Removed

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 6 -SUBSYSTEM_CMT_CHANNEL_ADDED_TO_GRP : Attempt by Subsystem CMT to add a channel to a CMT group succeeded. Method Name [String] GROUP TYPE [String] GROUP ID [Int] channel count [Int]

Explanation Channel Added to Group

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 6 -SUBSYSTEM_CMT_NEED_REMOVE_CHANNEL_FROM_GROUP : Channels need to be removed from a CMT group at configuration request. Method Name [String] GROUP ID [Int] GROUP TYPE [String] CHANNEL REMOVE [Int]

Explanation Notified By App Admin To Remove some Channels

Recommended Action No actions needed

Error Message
MIVR-SS_CMT- 3 -SUBSYSTEM_CMT_REGISTER_GRP_LISTENER_FAILED : Subsystem CMT failed to register itself as a group event listener. Exception [String]

Explanation CMT Failed To Register Self As a Group Event Listener

Recommended Action No actions needed

Error Message
MIVR-SS_CM- 3 -CAUGHT_EXCEPTION : An exception has been caught by the Cm.. Module Name [String] Exception [String]

Explanation An exception has been caught by the Cm.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_CM- 5 -SS_SHUTDOWN : Cm is shutdown.

Explanation The Cm has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-SS_CM- 6 -CONTACT_CLEARED : Administrator cleared the contact from the system. Administrator who cleared the contact [String] ID of an RmCm Contact [String] The name of the method that invoked another method [String] Time at which the contact clear was issued [String]

Explanation Administrator cleared the contact from the system

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_CM- 3 -RESOURCE_EXTN_DOES_NOT_ALLOWED : This resource is not on the allowed list. Module Name [String] The resource extension [String] The supervisor login id [String]

Explanation This resource is not on the allowed list

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_CM- 3 -CSQ_NAME_DOES_NOT_ALLOWED : This CSQ name is not on the allowed list. Module Name [String] The CSQ Name [String] The supervisor login id [String]

Explanation This CSQ name is not on the allowed list

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_CM- 3 -CSQ_NAME_DOES_NOT_EXIST : This CSQ name does not exist. Module Name [String] The CSQ Name [String]

Explanation This CSQ name does not exist

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_CM- 3 -ILLEGAL_SESSION_STATE_EXCEPTION : IllegalSessionStateException thrown.. Module Name [String] Exception [String] An App FW Session [com.cisco.session.Session]

Explanation An IllegalSessionStateException has been thrown by the App FW and caught by the Cm.

Recommended Action No actions needed

Error Message
MIVR-SS_CM- 3 -ERROR_CONFIGURING_WF : Error configuring workflow. Module Name [String] A specific description for a trace [String] The ESD ID [Int] Exception [String]

Explanation Error configuring workflow

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_CM- 3 -INCOMPATIBLE_SESSION_EXCEPTION : IncompatibleSessionException thrown.. Module Name [String] Exception [String] An App FW Session [com.cisco.session.Session] An App FW CallContact [com.cisco.call.CallContact]

Explanation An IncompatibleSessionException has been thrown by the App FW and caught by the Cm.

Recommended Action No actions needed

Error Message
MIVR-SS_CM- 3 -FAIL_TO_SET_RMON_STATUS : Unable to set status and post events to HRDM. Module Name [String] A description for the nature of the exception [String]

Explanation Unable to set status and post events to HRDM

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_CM- 2 -UNABLE_LOAD_WF : Unable to load the script. Module Name [String] Exception [String]

Explanation Unable to load the script

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_CM- 3 -ENCOUNTERS_THROWABLE : This thread has encountered a Throwable exception. Module Name [String] The name of the class that this thread belongs to [String] Exception [String]

Explanation This thread has encountered a Throwable exception

Recommended Action No actions needed

Error Message
MIVR-SS_CM- 3 -CLEANUP_STUCK_CONTACT : Removed stuck contact. ID of an RmCm Contact [String] The name of the method that invoked another method [String]

Explanation The system detected an old contact and removed it

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_CM- 3 -ERROR_INVOKING_WF : Error invoking workflow. Module Name [String] Exception [String]

Explanation Error invoking workflow

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_CM- 6 -INTERRUPTED : This thread has been interrupted. Module Name [String] The name of the class that this thread belongs to [String]

Explanation This thread has been interrupted

Recommended Action No actions needed

Error Message
MIVR-SS_CM- 3 -CONTACT_INACTIVE_EXCEPTION : ContactInactiveException thrown.. Module Name [String] Exception [String] An App FW CallContact [com.cisco.call.CallContact]

Explanation A ContactInactiveException has been thrown by the App FW and caught by the Cm.

Recommended Action No actions needed

Error Message
MIVR-SS_CM- 3 -DUPLICATE_CHANNEL_EXCEPTION : DuplicateChannelException thrown.. Module Name [String] Exception [String] An App FW CallContact [com.cisco.call.CallContact]

Explanation A DuplicateChannelException has been thrown by the App FW and caught by the Cm.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_CM- 3 -RESOURCE_EXTN_DOES_NOT_EXIST : This resource does not exist. Module Name [String] The resource extension [String]

Explanation This resource does not exist

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_DB- 5 -ModuleStart : Module has successfully started. Module Name [String]

Explanation This notification signifies a module has started successfully and transitioned into the in-service state

Recommended Action No actions needed

Error Message
MIVR-SS_DB- 1 -ModuleStop : Module has stopped. Module Name [String] Module Failure Cause [Enum]

Explanation This notification signifies a module has stopped

Recommended Action Investigate as required

Module Failure Cause-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Other or Unspecified Failure
2 Graceful Shutdown
3 Heartbeat Failure
4 Initialization Failure
5 Out of Resource
6 Partial Failure
Error Message
MIVR-SS_DB- 3 -ModuleRunTimeFailure : Run-time Failure. Module Name [String] Module Run-time Failure Cause [Enum] Module Failure Name [String] Module Failure Message [String]

Explanation This notification signifies a run-time failure has occured

Recommended Action Investigate as required

Module Run-time Failure Cause-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Other or Unspecified Failure
2 Read Access Failure
3 Write Access Failure
4 Create Failure
5 Delete Failure
6 Update Failure
7 Init Failure
8 Load Failure
9 Out of Resource
10 Call Process Failure
11 Registration Failure
12 De-registration Failure
13 Connection Failure
14 Disconnection Failure
15 Unknown Target
16 Un-reacheable Target
Error Message
MIVR-SS_DB- 4 -EXCEPTION_DURING_CLEANUPCONNECTIONS : Exception occured during Cleaning up Database Connections. Task ID [String]

Explanation Error in cleaning up the database connection pool

Recommended Action If problem persists Copy the error message exactly as it appears on the console or in the system log, and contact your Database Administrator

Error Message
MIVR-SS_DB- 4 -ERROR_IN_GETTING_DBSTATS : Error in getting Database Statistics data list.

Explanation Error in getting Database Statictics from the DSN

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message
MIVR-SS_DB- 3 -ERROR_IN_CREATING_NEW_CONNECTION : Error in creating new connection for the given DSN. DSN Name [String]

Explanation Cannot add a new connection to Datasource connection pool

Recommended Action If the database connectivity is desired, then do the following. Verify that the database is online and that it is visible on the network.Verify that the userid and password in the ODBC administrator match those in the Database Configuration AppAdmin pages.

Error Message
MIVR-SS_DB- 4 -ERROR_IN_GETTING_DSN_LIST : Error in getting the list of configured DSNs.

Explanation Could not get the list of configured DSNs

Recommended Action Try connecting to the LDAP server. If able to connect to the LDAP server, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message
MIVR-SS_DB- 3 -ERROR_IN_CHECKOUT_FROM_DSN : Error in checkout from DSN. Task ID [String] DSN Name [String]

Explanation Error getting a connection for a datasource

Recommended Action If the database connectivity is desired, then do the following. Verify that the database is online and that it is visible on the network.Verify that the userid and password in the ODBC administrator match those in the Database Configuration AppAdmin pages.

Error Message
MIVR-SS_DB- 3 -DATASOURCE_FOR_DSN_NOT_FOUND : Datasource for given DSN not found. DSN Name [String]

Explanation Cannot create a connection for the datasource DSN.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message
MIVR-SS_DB- 3 -CANNOT_CREATE_DATASOURCE_FOR_DSN : Cannot create Datasource for given DSN. DSN Name [String]

Explanation Cannot create a connection to the database

Recommended Action If the database connectivity is desired, then do the following. Verify that the database is online and that it is visible on the network.Verify that the userid and password in the ODBC administrator match those in the Database Configuration AppAdmin pages.

Error Message
MIVR-SS_DB- 3 -ERROR_INITIALIZING_DATASOURCEPOOL : Error while initializing Datasource poll.

Explanation Cannot add a new connection to Datasource connection pool

Recommended Action If the database connectivity is desired, then do the following. Verify that the database is online and that it is visible on the network.Verify that the userid and password in the ODBC administrator match those in the Database Configuration AppAdmin pages.

Error Message
MIVR-SS_DB- 5 -NO_DSN_CONFIGURED : No DSNs Configured.

Explanation No EDBS has been configured.

Recommended Action Configure the ODBC datasource from control panel and then configure the EDBS from Application admin pages.

Error Message
MIVR-SS_DB- 3 -RMI_INIT_FAILED_IN_EDBS : RMI Intialization failed in Database SubSystem.

Explanation Could not connect to the remote engine.

Recommended Action Verify that only one instance of the database is running on this server.Reboot the server.

Error Message
MIVR-SS_DB- 5 -SUN_JDBC_DRIVER_OPEN_SUCCESSFUL : Sun JDBC open successful.

Explanation Successfully opened Sun JDBC Driver

Recommended Action No action is required

Error Message
MIVR-SS_DB- 5 -MICROSOFT_JDBC_DRIVER_OPEN_SUCCESSFUL : Microsoft JDBC open successful.

Explanation SSuccessfully opened Microsoft JDBC Driver

Recommended Action No actions needed

Error Message
MIVR-SS_DB- 5 -INITIALIZING_EDBS_SS : Initializing Database SubSystem.

Explanation Database subsystem of the application is being initialized.

Recommended Action No actions is required

Error Message
MIVR-SS_DB- 4 -EXCEPTION_ON_TESTSQLUPDATE : Exception occured while testing SQL Update.

Explanation Error occurred while executing an SQL update

Recommended Action Check your sql statement and verify database availability.

Error Message
MIVR-SS_DB- 4 -EXECUTE_SQL_UPDATE_EXCEPTION : Exception occured while executing SQL Update. SQL State [String] SQL Error code [String] Connection # [String]

Explanation Error occurred while executing an SQL update

Recommended Action Check your sql statement and verify database availability.

Error Message
MIVR-SS_DB- 4 -NO_DATASOURCES_FOUND : No Datasources found.

Explanation Cannot get the list of configured DSNs

Recommended Action Try connecting to the LDAP server. If able to connect to the LDAP server, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message
MIVR-SS_DB- 4 -EXCEPTION_ON_TESTSQL : Exception occured while testing SQL statement.

Explanation Error occurred while executing an SQL statement

Recommended Action Check your sql statement and verify database availability.

Error Message
MIVR-SS_DB- 4 -EXECUTE_SQL_EXCEPTION : Exception occured while executing SQL statement. SQL State [String] SQL Error code [String] Connection # [String]

Explanation Error occurred while executing an SQL statement

Recommended Action Check your sql statement and verify database availability.

Error Message
MIVR-SS_DB- 4 -RMI_SERVER_GETSTATS_FAILED : RMI server getStatistics failed.

Explanation Error occurred while getting the database real time statistics

Recommended Action Verify that only one instance of the database is running on this server.Reboot the server.

Error Message
MIVR-SS_DB- 4 -RMI_SERVER_GETCOLUMNS_FAILED : RMI Server getColumns failed. Connection # [String]

Explanation Error occurred while getting the columns from database

Recommended Action Verify that only one instance of the database is running on this server.Reboot the server.

Error Message
MIVR-SS_DB- 4 -RMI_SERVER_PROCESSING_RESULTSET_FAILED : RMI Server processing resultset failed.

Explanation Error occurred while processing the result set.

Recommended Action Verify that only one instance of the database is running on this server.Reboot the server.

Error Message
MIVR-SS_DB- 4 -RMI_SERVER_GET_METADATA_FAILED : RMI server get Metadata failed.

Explanation Error occurred while getting metadata from the database

Recommended Action Verify that only one instance of the database is running on this server.Reboot the server.

Error Message
MIVR-SS_DB- 4 -EXCEPTION_IN_REFRESH_DB_SCHEMA : Exception occured while refreshing Database schema.

Explanation Error in refreshing the database schema

Recommended Action No actions needed

Error Message
MIVR-SS_DB- 6 -REMOVING_DATABASE_CONNECTION : Removing Database connection. DSN Name [String]

Explanation Removing the database connection

Recommended Action No actions needed

Error Message
MIVR-SS_DB- 6 -REMOVING_DSN : Removing DSN. DSN Name [String]

Explanation Removing the DSN

Recommended Action No actions needed

Error Message
MIVR-SS_DB- 6 -MODIFYING_DATABASE_CONNECTION : Modifying Database connection. DSN Name [String] New Pool Size [String]

Explanation Modifying the database connection

Recommended Action No actions needed

Error Message
MIVR-SS_DB- 6 -ADDING_DATABASE_CONNECTION : Adding Database connection. DSN Name [String]

Explanation Adding database connection

Recommended Action No actions needed

Error Message
MIVR-SS_DB- 6 -CREATING_NEW_SET_OF_DB_CONNECTIONS : Creating new set of Database connections. DSN Name [String] Max number of Database connections [String]

Explanation Creating a new set of database connections

Recommended Action No actions needed

Error Message
MIVR-SS_DB- 6 -STARTING_DB_CONNECTION_RESETTER_THREAD : Starting thread for resetting Database connections for the given DSN. DSN Name [String]

Explanation Resetting connections to the datasource

Recommended Action No actions needed

Error Message
MIVR-SS_DB- 4 -COULD_NOT_ADD_CONNECTION_FOR_DSN : Failure to add connections for the given DSN. DSN Name [String]

Explanation Cannot create a connection for the datasource DSN.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message
MIVR-SS_DB- 6 -CONNECTION_RETRY : Retrying connection to given DSN. DSN Name [String]

Explanation Retrying connection to a given DSN

Recommended Action No actions needed

Error Message
MIVR-SS_DB- 6 -CONNECTION_POOL_SIZE_INFORMATION : Connection Pool Size information. DSN Name [String] Pool size [String] Max Pool size [String]

Explanation Connection pool size information

Recommended Action No actions needed

Error Message
MIVR-SS_DB- 3 -DB_CREATE_CONNECTION_FAILED : Database create connection failed. SQL State [String] SQL Error code [String]

Explanation Could not connect to the database

Recommended Action If the database connectivity is desired, then do the following. Verify that the database is online and that it is visible on the network.Verify that the userid and password in the ODBC administrator match those in the Database Configuration AppAdmin pages.

Error Message
MIVR-SS_DB- 3 -FAILURE_TO_CONNECT_TO_DATABASE_SERVER : Failure to connect to Database server. Will continue to try periodically..

Explanation Could not connect to the database

Recommended Action If the database connectivity is desired, then do the following. Verify that the database is online and that it is visible on the network.Verify that the userid and password in the ODBC administrator match those in the Database Configuration AppAdmin pages.

Error Message
MIVR-SS_DB- 4 -FAILURE_WHILE_RECONNECTING : Failure while trying to reconnect to given DSN in DBMonitorThread. Connection number or ID [String] DSN Name [String]

Explanation Could not connect to the database

Recommended Action If the database connectivity is desired, then do the following. Verify that the database is online and that it is visible on the network.Verify that the userid and password in the ODBC administrator match those in the Database Configuration AppAdmin pages.

Error Message
MIVR-SS_DB- 4 -EXCEPTION_IN_DB_CONNECTION_RESETTER_THREAD : Exception caught in DB connection monitor thread.

Explanation Exception caught in DB connection monitor thread

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message
MIVR-SS_DB- 4 -EXCEPTION_DURING_RESETTING_CONNECTION : Exception during Resetting DB connection.

Explanation Exception during Resetting DB connection

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message
MIVR-SS_DB- 5 -CON_RESETTER_THREAD_RECON_SUCCESS : Successful reconnection to. DSN Name [String] Number of attempt [String]

Explanation Successful reconnection to DSN

Recommended Action No actions needed

Error Message
MIVR-SS_DB- 4 -EXCEPTION_DURING_DESTROY_CONNECTION : Exception occured during destroying Database connections. SQL State [String] SQL Error code [String]

Explanation Error during destroying DB connection

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message
MIVR-SS_DB- 3 -BAD_CONNECTION : Bad connection for the given DSN. DSN Name [String]

Explanation Bad connection for the given DSN

Recommended Action If the database connectivity is desired, then do the following. Verify that the database is online and that it is visible on the network.Verify that the userid and password in the ODBC administrator match those in the Database Configuration AppAdmin pages.

Error Message
MIVR-SS_DB- 3 -d : du. Task ID [String] Step Name [String]

Explanation An error happens with given task id and step name

Recommended Action Validate the workflow script. If problem persists, contact your Cisco technical support representative and provide the representative with the gathered information

Error Message
MIVR-SS_DB- 3 -d : du. Task ID [String] Step Name [String]

Explanation An error happens with given task id and step name

Recommended Action Validate the workflow script. If problem persists, contact your Cisco technical support representative and provide the representative with the gathered information

Error Message
MIVR-SS_DB- 3 -d : du. Task ID [String] Step Name [String]

Explanation An error happens with given task id and step name

Recommended Action Validate the workflow script. If problem persists, contact your Cisco technical support representative and provide the representative with the gathered information

Error Message
MIVR-SS_DB- 3 -d : du. Task ID [String] Step Name [String]

Explanation An error happens with given task id and step name

Recommended Action Validate the workflow script. If problem persists, contact your Cisco technical support representative and provide the representative with the gathered information

Error Message
MIVR-SS_DB- 3 -d : du. Task ID [String] Step Name [String]

Explanation An error happens with given task id and step name

Recommended Action Validate the workflow script. If problem persists, contact your Cisco technical support representative and provide the representative with the gathered information

Error Message
MIVR-SS_DB- 5 -NO_JDBC_DRIVER_CONFIGURED : No JDBC Drivers Configured.

Explanation No JDBC Drivers are configured.

Recommended Action Upload JDBC Driver from Application admin pages.

Error Message
MIVR-SS_DB- 3 -CANNOT_UPLOAD_JDBC_DRIVER : Cannot upload the given JDBC Driver. DRIVER ID [String]

Explanation Cannot upload the JDBC driver

Recommended Action If the database connectivity is desired, then do the following. Verify that the database is online and that it is visible on the network.Verify that the JDBC driver jar provided is valid.

Error Message
MIVR-SS_DB- 6 -REMOVING_JDBC_DRIVER : Removing DSN. DRIVER ID [String]

Explanation Removing the JDBC Driver

Recommended Action No actions needed

Error Message
MIVR-SS_DB- 6 -ADDING_JDBC_DRIVER : Adding JDBC Driver. DRIVER ID [String]

Explanation Adding JDBC Driver

Recommended Action No actions needed

Error Message
MIVR-SS_DB- 4 -EXCEPTION_IN_REFRESH_JDBC_DRIVERS : Exception occured while refreshing JDBC Drivers.

Explanation Error in refreshing the JDBC Drivers

Recommended Action No actions needed

Error Message
MIVR-SS_EMAIL- 6 -SS_INITIALIZING : eMail subsystem initializing.

Explanation The eMail subsystem is initializing

Recommended Action No actions needed

Error Message
MIVR-SS_EMAIL- 5 -SS_SHUTDOWN : eMail subsystem is shutdown.

Explanation The eMail subsystem has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-SS_EMAIL- 3 -RMI_REBIND_FAILED : Unable to register remote interface. Exception [String]

Explanation A remote interface could not be binded to the RMI registry; remote access for dynamic update or other functions will not be available

Recommended Action Verify the RMI configuration and restart server

Error Message
MIVR-SS_EMAIL- 1 -SS_PARTIAL_SERVICE : eMail subsystem in partial service.

Explanation Some information could not be properly loaded from the repository

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_EMAIL- 2 -SS_OUT_OF_SERVICE : eMail subsystem in out of service.

Explanation eMail subsystem is either disabled or failed to be loaded

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_EMAIL- 5 -SS_SHUTTING_DOWN : eMail subsystem is shutting down.

Explanation The eMail subsystem is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-SS_EMAIL- 0 -EMAIL_SS_TRY_TO_USE_BUT_DOWN : Attempt to use eMail subsystem while it is not in service. Task id [Long]

Explanation A workflow was executed which uses eMail while subsystem is not in service

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_EMAIL- 0 -EMAIL_SS_INIT_ERROR : eMail Subsystem initialization error. Exception [String]

Explanation The eMail Subsystem could not be initialized because (more than likely) the LDAP Directory could not be accessed

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_EMAIL- 5 -EMAIL_SS_NO_SERVER_CONFIGURED : No Mail Server is configured in the Application Administration to setup eMail..

Explanation No Mail Server is configured in the Application Administration to setup eMail.

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_EMAIL- 0 -EMAIL_SS_JAVAMAIL_MESSAGING_EX : JavaMail reporting a messaging exception. Task id [Long] Exception [String]

Explanation JavaMail reporting a messaging exception. Could the Mail Server be down or not accessible on the network?

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_EMAIL- 0 -EMAIL_SS_GEN_SEND_PROCESSING_EX : General exception trying to send eMail. Exception [String]

Explanation General Exception trying to send eMail but likely before invoking JavaMail. Do all variables have valid values?

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_EMAIL- 6 -SS_IN_SERVICE : eMail subsystem in service.

Explanation The eMail subsystem is in service

Recommended Action No actions needed

Error Message
MIVR-SS_ENT_SRV- 3 -SUBSYSTEM_ERROR : Fail to start or stop Enterprise Server Subsystem. Exception [String]

Explanation Could not start or stop Enterprise Server Subsystem

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_ENT_SRV- 6 -SS_INITIALIZING : Enterprise Server Subsystem initializing.

Explanation The Enterprise Server Subsystem is initializing

Recommended Action No actions needed

Error Message
MIVR-SS_ENT_SRV- 5 -SS_SHUTDOWN : Enterprise Server Subsystem is shutdown.

Explanation The Enterprise Server Subsystem has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-SS_ENT_SRV- 1 -SS_OUT_OF_SERVICE : Enterprise Server Subsystem in out of service.

Explanation The Enterprise Server Subsystem is out of service

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_ENT_SRV- 3 -SOCKET_ERROR : Exception encountered with listener socket. Module Name [String] A specific description for a trace [String] A description for the nature of the exception [String]

Explanation Exception encountered with listener socket

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_ENT_SRV- 6 -ACTIVE_LRM : Enterprise Server Subsystem's Active LRM. A specific description for a trace [String]

Explanation Enterprise Server Subsystem's Active LRM

Recommended Action No actions needed

Error Message
MIVR-SS_ENT_SRV- 6 -START_RECOVERY : Enterprise Server Subsystem is initiating recovery.

Explanation Enterprise Server Subsystem is initiating recovery

Recommended Action No actions needed

Error Message
MIVR-SS_ENT_SRV- 3 -ERROR_LOAD_REGISTRY : Fail to read registry. Exception [String]

Explanation Could not read registry entry

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_ENT_SRV- 6 -SS_PARTIAL_SERVICE : Enterprise Server Subsystem in partial service.

Explanation The Enterprise Server Subsystem is in partial service

Recommended Action No actions needed

Error Message
MIVR-SS_ENT_SRV- 5 -SS_SHUTTING_DOWN : Enterprise Server Subsystem is shutting down.

Explanation The Enterprise Server Subsystem is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-SS_ENT_SRV- 3 -CORBA_INVOKE_ERROR : Fail to invoke corba call. Exception [String]

Explanation Could not invoke corba method

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_ENT_SRV- 3 -ERROR_LOAD_LDAP : Fail to read LDAP INFO. Exception [String]

Explanation Could not read LDAP content

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_ENT_SRV- 6 -SS_IN_SERVICE : Enterprise Server Subsystem in service.

Explanation The Enterprise Server Subsystem is in service

Recommended Action No actions needed

Error Message
MIVR-SS_HTTP- 5 -ModuleStart : Module has successfully started. Module Name [String]

Explanation This notification signifies a module has started successfully and transitioned into the in-service state

Recommended Action No actions needed

Error Message
MIVR-SS_HTTP- 1 -ModuleStop : Module has stopped. Module Name [String] Module Failure Cause [Enum]

Explanation This notification signifies a module has stopped

Recommended Action Investigate as required

Module Failure Cause-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Other or Unspecified Failure
2 Graceful Shutdown
3 Heartbeat Failure
4 Initialization Failure
5 Out of Resource
6 Partial Failure
Error Message
MIVR-SS_HTTP- 3 -ModuleRunTimeFailure : Run-time Failure. Module Name [String] Module Run-time Failure Cause [Enum] Module Failure Name [String] Module Failure Message [String]

Explanation This notification signifies a run-time failure has occured

Recommended Action Investigate as required

Module Run-time Failure Cause-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Other or Unspecified Failure
2 Read Access Failure
3 Write Access Failure
4 Create Failure
5 Delete Failure
6 Update Failure
7 Init Failure
8 Load Failure
9 Out of Resource
10 Call Process Failure
11 Registration Failure
12 De-registration Failure
13 Connection Failure
14 Disconnection Failure
15 Unknown Target
16 Un-reacheable Target
Error Message
MIVR-SS_HTTP- 4 -SERVLET_INITIALIZATION_ERROR : Error during Servlet initialization. Application NAME [String] Trigger status [String]

Explanation Error happens during servlet initialization

Recommended Action Restart the server. If problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_HTTP- 1 -HTTP_REQUEST_ERROR : Http Request Error. Cause of Http request error [String]

Explanation Http request error

Recommended Action Check the HTTP Trigger and Generic Application Setup in AppAdmin. If problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_HTTP- 1 -APPLICATION_ERROR : Application Error. Cause for Application error [String]

Explanation An error has happened when invoking an application

Recommended Action Check the HTTP Trigger and Generic Application Setup in AppAdmin. If problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 3 -ICM_CHANNEL_DUP_EX : Duplicated ICM Channel added. Contact id [Int] Media id [String] Task id [Long] Exception [String]

Explanation The ICM Channel was added to a contact which already has a channel added with the class or type

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 4 -TASK_INIT_ERROR : Error in ICM task initializer. Task id [Long] Exception [String]

Explanation The ICM task initializer failed to initialize the specified task

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_ICM- 3 -ICM_CFG_ERROR : ICM configuration error. Config Filename [String] Configuration Property Key [String] Info [String] Exception [String]

Explanation An error was detected in the ICM configuration

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 3 -INITIAL_SCRIPT_LOAD_ERROR : Failed to load the Initial Script loaded. Initial Script [String] Script [String] Exception [String]

Explanation There is an error in loading the Initial Script

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 6 -VRU_SCRIPT_UNLOADED : VRU Script unloaded. VRU Script [String]

Explanation The specified VRU Script was unloaded from memory

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 2 -SS_OUT_OF_SERVICE : ICM subsystem in out of service.

Explanation The VRU interface is disabled or there is no session active with the ICM

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_ICM- 3 -UNABLE_INIT_ICM_ROUTE : Unable to init ICM route. Route Address [String] Exception [String]

Explanation The specified ICM route failed to be initialized

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 0 -UNABLE_INIT_ICM_PROVIDER : Unable to initialize an ICM Provider. Exception [String]

Explanation The ICM subsystem was unable to initialize an ICM Provider which is required to establish communications with the ICM

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 4 -ICM_REQ_FAILED : ICM request failed. ICM Message [String] Contact id [Int] Media id [String] Task id [Long] Exception [String]

Explanation The specified ICM request failed

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 2 -SS_ALREADY_INIT : ICM subsystem is already initialized. Exception [String]

Explanation The ICM subsystem is being initialized for the second time

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_ICM- 3 -INVALID_SERVICE : Unable to create or access the corresponding ICM service for the specified call. Service id [Int] Contact id [Int] Media id [String] Task id [Long] Exception [String]

Explanation The ICM subsystem is unable to create or access the ICM service associated with the specified call

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 1 -DFLT_SCRIPT_LOAD_ERROR : Failed to load default script. Script [String] Exception [String]

Explanation The specified default script failed to be loaded in memory for the given ICM route

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 3 -SS_STATE_ERROR : Unable to process subsystem state. Subsystem Name [String] Subsystem State [String] Exception [String]

Explanation The ICM subsystem was unable to process a state changed for the specified subsystem

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 1 -SS_PARTIAL_SERVICE : ICM subsystem in partial service.

Explanation Some VRU scripts could not be properly loaded from the repository

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_ICM- 6 -DFLT_SCRIPT_LOADED : Default script loaded. Script [String] Route Address [String]

Explanation The specified default script was loaded in memory for the given ICM route

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 6 -INITIAL_SCRIPT_LOADED : Initial Script loaded successfully. Initial Script [String] Script [String]

Explanation The Initial Script has been loaded in memory successfully

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 3 -CFG_READ_ERROR : Unable to read an ICM CFG table. CFG Table [String] Exception [String]

Explanation The ICM subsystem was not able to read the specified ICM CFG table

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 6 -ICM_ROUTE_RELOADED : ICM route reloaded. Route Address [String]

Explanation The specified ICM route was reloaded in memory

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 3 -UNABLE_ADD_CFG_LISTENER : Unable to add config listener. Exception [String]

Explanation The ICM subsystem was unable to register listener to receive configuration changes event

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 6 -SCRIPT_LOADED : Script loaded. Script [String] Route Address [String]

Explanation The specified script was loaded in memory for the given ICM route

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 6 -VRU_SCRIPT_RELOADED : VRU Script reloaded. VRU Script [String]

Explanation The specified VRU Script was reloaded in memory

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 6 -ICM_ROUTE_LOADED : ICM route loaded. Route Address [String]

Explanation The specified ICM route was loaded in memory

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 3 -UNABLE_REG_ICM_ROUTE : Unable to register ICM route. Route Address [String] Exception [String]

Explanation The specified ICM route failed to be registered

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 3 -INVALID_TRIGGER_TYPE : Invalid application trigger. Application [String] Incorrect Application Trigger Class [String] Correct Application Trigger Class [String] Exception [String]

Explanation The application trigger received is invalid

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 3 -INVALID_TRUNK_GROUP : Unable to create or access the corresponding ICM trunk group for the specified call. Trunk Group id [Int] Contact id [Int] Media id [String] Task id [Long] Exception [String]

Explanation The ICM subsystem is unable to create or access the ICM trunk group associated with the specified call

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 3 -CHANNEL_MISSING : Channel is missing from contact. Channel Class [String] Contact id [Int] Media id [String] Contact Class [String] Contact Type [String] Exception [String]

Explanation The specified type of channel is not associated with the given contact

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 2 -CFG_ACCESS_ERROR : Unable to access an ICM configuration. Exception [String]

Explanation The ICM subsystem was not able to access the ICM configuration

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 6 -VRU_SCRIPT_LOADED : VRU Script loaded. VRU Script [String]

Explanation The specified VRU Script was loaded in memory

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 5 -SS_SHUTDOWN : ICM subsystem in shutdown.

Explanation The ICM subsystem has complete its shutdown

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 4 -ICM_CFG_MONITOR_FAIL : ICM configuration monitoring failure. Exception [String]

Explanation The ICM subsystem can no longer monitor dynamic update to some of its configuration

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 3 -UNDEFINED_VRU_SCRIPT : Undefined VRU script referenced by the specified call. VRU Script [String] Contact id [Int] Media id [String] Task id [Long]

Explanation The ICM subsystem is unable to access the VRU script referenced by the specified call

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_ICM- 3 -UNABLE_ACCESS_CHANNEL : The channel associated with a call cannot be determined. Contact id [Int] Media id [String] Task id [Long] Exception [String]

Explanation The ICM subsystem can not access the channel associated with the specified call

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_ICM- 1 -ICM_ROUTE_LOAD_ERROR : Failed to load ICM route. Route Address [String] Exception [String]

Explanation The specified ICM route failed to be loaded in memory

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 3 -ICM_CHANNEL_ADD_EX : Failure in adding ICM Channel to a contact. Contact id [Int] Media id [String] Task id [Long] Exception [String]

Explanation There is an error when trying to add the ICM Channel to a contact

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 3 -CFG_UNDEFINED_OBJECT : Undefined object in ICM CFG table. CFG Object [String] CFG Table [String]

Explanation The CFG object is not defined in the specified ICM CFG table

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 0 -UNABLE_GET_ICM_PEER : Unable to get an ICM Peer object.

Explanation The ICM subsystem was uanble to get an ICM Peer object which is required to establish communications with the ICM

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 4 -IGNORING_MICROAPP_GRAMMAR : Ignoring the following grammar for the microapp request. Grammar [String] ICM Message [String] Contact id [Int] Media id [String] Task id [Long]

Explanation The specified grammar will be ignored while processing the specified microapp request

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 6 -SS_IN_SERVICE : ICM subsystem in service.

Explanation The ICM subsystem is in service

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 5 -CFG_EMPTY_TABLE : Empty ICM CFG table. CFG Table [String]

Explanation The specified ICM CFG table is empty

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 4 -ICM_TIMEOUT : Timeout waiting for ICM instructions. Timeout [Long] Contact id [Int] Media id [String] Task id [Long]

Explanation The specified call timed out waiting for instructions from the ICM

Recommended Action Check the ICM or increase the configured timeout

Error Message
MIVR-SS_ICM- 6 -SS_INITIALIZING : ICM subsystem initializing.

Explanation The ICM subsystem is initializing

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 3 -RMI_REBIND_FAILED : Unable to register remote interface. Exception [String]

Explanation A remote interface could not be binded to the RMI registry; remote access for dynamic update or other functions will not be available

Recommended Action Verify the RMI configuration and restart server

Error Message
MIVR-SS_ICM- 1 -VRU_SCRIPT_LOAD_ERROR : Failed to load VRU Script. VRU Script [String] Script [String] Exception [String]

Explanation The specified VRU Script failed to be loaded in memory with the configured script

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 6 -ICM_ROUTE_UNLOADED : ICM route unloaded. Route Address [String]

Explanation The specified ICM route was unloaded from memory

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 1 -SCRIPT_LOAD_ERROR : Failed to load script. Script [String] Route Address [String] Exception [String]

Explanation The specified script failed to be loaded in memory for the given ICM route

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 3 -CFG_OBJECT_READ_ERROR : Unable to read an object from an ICM CFG table. CFG Object [String] CFG Table [String] Exception [String]

Explanation The ICM subsystem was not able to read an object from the specified ICM CFG table

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 1 -UNABLE_UPDATE_ICM_PROVIDER : Unable to update ICM Provider. Exception [String]

Explanation The ICM subsystem was unable to update the ICM Provider

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 5 -SS_SHUTTING_DOWN : ICM subsystem in shutting down.

Explanation The ICM subsystem is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 3 -INVALID_TRUNK : Unable to create or access the corresponding ICM trunk for the specified call. Trunk number [Int] Trunk Group id [Int] Contact id [Int] Media id [String] Task id [Long] Exception [String]

Explanation The ICM subsystem is unable to create or access the ICM trunk associated with the specified call

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 4 -IGNORING_TERMINATING_KEYS : Ignoring the following terminating keys for the microapp request. Terminating keys [String] ICM Message [String] Contact id [Int] Media id [String] Task id [Long]

Explanation The specified terminating keys will be ignored while processing the specified microapp request

Recommended Action No actions needed

Error Message
MIVR-SS_ICM- 3 -CFG_DUP_OBJECT : Duplicate object in ICM CFG table. CFG Object [String] CFG Table [String]

Explanation The CFG object is duplicated in the specified ICM CFG table

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 4 -INVALID_ECC_NAME : Unable to create or access the corresponding ICM ECC variable for the specified script. ECC Variable Name [String] Script [String] Exception [String]

Explanation The ICM subsystem is unable to create or access the ICM ECC variable associated with the specified script

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_ICM- 3 -ICM_TIMEOUT_INVALID : Timeout value is invalid. Exception [String]

Explanation The Timeout value is not in the right format

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_ICM- 3 -UNABLE_CREATE_CALL : Unable to create corresponding ICM call for the specified call. Contact id [Int] Media id [String] Task id [Long] Exception [String]

Explanation The ICM subsystem is unable to create an ICM call for the specified call

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_MRCP_ASR- 5 -SS_SHUTDOWN : Mrcp ASR subsystem is SHUTDOWN.

Explanation The Mrcp ASR subsystem has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_ASR- 3 -SUBSYSTEM_MRCP_MEDIA_MANAGER_ERROR : MRCP Media Manager Error. Exception [String]

Explanation MRCP Media Manager Error

Recommended Action Stop Media Driver, restart system, if problem persist contact Cisco

Error Message
MIVR-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_CHANNEL_ADDED_TO_GRP : Channel added to Group. Group Channel Type [String] Group id [Int] channel count [Int]

Explanation Channel added to Group

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_MODIFY_PRVD_FAILED : Unable to modify provider. Provider Name [String] Exception [String]

Explanation Unable to modify

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_ASR- 3 -SS_OUT_OF_SERVICE : Mrcp ASR subsystem is OUT_OF_SERVICE.

Explanation Mrcp ASR subsystem is either disabled or failed to be loaded

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_DESTROY_PRVD_FAILED : Specified provider could not be destroyed. Provider Name [String] Exception [String]

Explanation Specified provider could not be destroyed

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_CREATE_GRP_FAILED : Create Group failed. Group id [Int] Group Channel Type [String] Exception [String]

Explanation Create Group failed

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_SS_INIT_FAILED : Unable to initialize the Mrcp SS. Exception [String]

Explanation Unable to initialize the Mrcp SS

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_ASR- 6 -SS_ALREADY_INIT : Mrcp ASR Subsystem is already initialized.. Subsystem Name [String]

Explanation Mrcp ASR Subsystem is already initialized.

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_CREAT_CHANNEL_FAILED : Create Channel failed. Channel Type [String] Exception [String]

Explanation Create Channel failed

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_NO_SERVER_FOUND : No MRCP Speech Server found for group.. Group id [Int]

Explanation No MRCP Speech Server found for group.

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_MRCP_ASR- 1 -SS_PARTIAL_SERVICE : Mrcp ASR subsystem is in PART_SERVICE.

Explanation The Mrcp ASR subsystem is in partial service

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_REMOVE_GRP_LISTENER : Mrcp ASR removes self as a group listener. Channel Type [String]

Explanation Mrcp ASR removes self as a group listener

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_ADD_CHANNEL_TO_GRP_FAILED : Add Channel to group failed. Group Channel Type [String] Group id [Int] channel count [Int] Exception [String]

Explanation Add Channel to group failed

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_REFRESH_PRVD_FAILED : Could not refresh specified provider. Method Name [String] Provider Name [String] Exception [String]

Explanation Could not refresh specified provider

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_DISPOSE_GRP : Mrcp ASR disposed this Group during shutdown. Group id [Int]

Explanation Mrcp ASR disposed this Group during shutdown

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_GROUP_TYPE_NULL : Group Type is null. Method Name [String] Group id [Int]

Explanation Group Type is null

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_DISPOSE_GRP_FAILED : Mrcp ASR failed to dispose a group. Group id [Int] Exception [String]

Explanation Mrcp ASR failed to dispose a group

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_ASR- 6 -SS_IN_SERVICE : Mrcp ASR subsystem IN_SERVICE.

Explanation The Mrcp ASR subsystem is in full service

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_NEED_REMOVE_CHANNEL_FROM_GROUP : Notified By AppAdmin to remove some channels. Group id [Int] Group Channel Type [String] CHANNEL REMOVE [Int]

Explanation Notified By AppAdmin to remove some channels

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_CHANNEL_TYPE_NULL : Channel Type is null. Channel id [Int]

Explanation Channel Type is null

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_ASR- 6 -SS_INITIALIZING : Mrcp ASR subsystem initializing.

Explanation The Mrcp ASR subsystem is initializing

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_MODIFY_GRP_FAILED : Modify group failed, group could not be added.. Provider Name [String] Group id [Int] Exception [String]

Explanation Modify group failed, group could not be added.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_START_MONITOR_FAILED : Monitor for the specified provider could not be started. Provider Name [String] Exception [String]

Explanation Monitor for the specified provider could not be started

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_GET_GRP_FAILED : Could not get the group with the specified id. Group id [Int] Exception [String]

Explanation Could not get the group with the specified id

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_COULD_NOT_CHANGE_GRP_STATE : Unable to change state of Group. Channel id [Int] Provider Name [String]

Explanation Unable to change state of Group

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_CHANNEL_CREATED : Channel created. Channel Type [String] Channel id [Int]

Explanation Channel created

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_GRP_REPOSITORY_DATA_NULL : Data received from Group repository is null. Method Name [String]

Explanation Data received from Group repository is null

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_GROUP_TYPE_NOT_SUPPORTED : Group Type not supported. Method Name [String] Group id [Int] Group Channel Type [String]

Explanation Group Type not supported

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_CREATE_PRVD_FAILED : Could not create provider. Method Name [String] Provider Name [String] Exception [String]

Explanation Could not create provider

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_MODIFICATION_NOT_NEED : Currently has exact nbr of channels as req by AppAdmin. Group id [Int] Group Channel Type [String]

Explanation Currently has exact nbr of channels as req by AppAdmin

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_ASR- 5 -SS_SHUTTING_DOWN : Mrcp ASR subsystem is SHUTTING_DOWN.

Explanation The Mrcp ASR subsystem is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_DISPOSE_CHANNEL_FAILED : Mrcp ASR failed to dispose a Channel. Exception [String]

Explanation Mrcp ASR failed to dispose a Channel

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_GET_PRVD_FAILED : Error retrieving provider data. Method Name [String] Provider Name [String] Exception [String]

Explanation Error retrieving provider data

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_NEED_ADD_CHANNEL_TO_GROUP : Notified By AppAdmin to add more channels. Group id [Int] Group Channel Type [String] CHANNEL ADD [Int]

Explanation Notified By AppAdmin to add more channels

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_REGISTER_SS_MRCP_ASR_AS_GRP_LISTENER : Mrcp ASR registered self as a Group event listener. Method Name [String] Channel Type [String]

Explanation Mrcp ASR registered self as a Group event listener

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_ASR- 4 -SUBSYSTEM_MRCP_ASR_CREATE_GRP_MAP_FAILED : Error creating group-server mapping for the specified provider. Provider Name [String] Exception [String]

Explanation Error creating group-server mapping for the specified provider

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_ASR- 6 -SUBSYSTEM_MRCP_ASR_CLASS_DIALOGCHANNEL_NOT_FOUND : Class for the specified Dialog Channel was not found. Method Name [String] DIALOG CHANNEL CLASS [String] Exception [String]

Explanation Class for the specified Dialog Channel was not found

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_TTS- 4 -SUBSYSTEM_MRCP_TTS_DEREG_PRVD_FAILED : Could not deregister specified provider. Provider Name [String] Exception [String]

Explanation Could not deregister specified provider

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_TTS- 5 -SS_SHUTDOWN : MRCP TTS subsystem is SHUTDOWN.

Explanation The MRCP TTS subsystem has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_TTS- 6 -SS_INITIALIZING : MRCP TTS subsystem initializing.

Explanation The MRCP TTS subsystem is initializing

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_TTS- 3 -SS_OUT_OF_SERVICE : MRCP TTS subsystem is OUT_OF_SERVICE.

Explanation MRCP TTS subsystem is either disabled or failed to be loaded

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_MRCP_TTS- 3 -MRCP_TTS_CREATE_SESSION_SRVR_ERROR : MrcpClient.createSession() failed due to possible internal server error on the mrcp server. Please make sure the mrcp server processes are up and adequate licenses are provisioned.. Server IP [String] Create Session Return Code [String] MRCP Reason [String]

Explanation MrcpClient.createSession() failed due to possible internal server error on the mrcp server. Please make sure the mrcp server processes are up and adequate licenses are provisioned.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_TTS- 4 -SUBSYSTEM_MRCP_TTS_GET_PRVD_FAILED : Error retrieving provider data. Method Name [String] Provider Name [String] Exception [String]

Explanation Error retrieving provider data

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_TTS- 4 -SUBSYSTEM_MRCP_TTS_CREATE_PRVD_FAILED : Could not create specified provider. Provider Name [String] Exception [String]

Explanation Could not create specified provider

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_TTS- 5 -SS_ALREADY_INIT : MRCP TTS subsystem is already initialized. Subsystem Name [String]

Explanation MRCP TTS subsystem is already initialized

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_TTS- 3 -MRCP_TTS_CREATE_SESSION_SVC_NOTFOUND : MrcpClient.createSession() failed due to Service unavailable or no mrcp vendor licenses available. Please make sure the mrcp server processes are up and adequate licenses are provisioned.. Server IP [String] Create Session Return Code [String] MRCP Reason [String]

Explanation MrcpClient.createSession() failed due to Service unavailable or no mrcp vendor licenses available. Please make sure the mrcp server processes are up and adequate licenses are provisioned.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_TTS- 4 -SUBSYSTEM_MRCP_TTS_SS_INIT_FAILED : MRCP TTS subsystem initialization failed. Exception [String]

Explanation MRCP TTS subsystem initialization failed

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_TTS- 4 -SUBSYSTEM_MRCP_TTS_START_MONITOR_FAILED : Monitor for the specified provider could not be started. Provider Name [String] Exception [String]

Explanation Monitor for the specified provider could not be started

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_TTS- 1 -SS_PARTIAL_SERVICE : MRCP TTS subsystem is in PART_SERVICE.

Explanation The MRCP TTS subsystem is in partial service

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_MRCP_TTS- 5 -SS_SHUTTING_DOWN : MRCP TTS subsystem is SHUTTING_DOWN.

Explanation The MRCP TTS subsystem is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-SS_MRCP_TTS- 4 -SUBSYSTEM_MRCP_TTS_CLEAR_PRVDMGR_FAILED : Could not clear the provider managers during refresh. Provider Name [String] Exception [String]

Explanation Could not clear the provider managers during refresh

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_TTS- 4 -SUBSYSTEM_MRCP_TTS_CLEAR_PRVD_FAILED : Could not clear the specified provider. Provider Name [String] Exception [String]

Explanation Could not clear the specified provider

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_TTS- 4 -SUBSYSTEM_MRCP_TTS_CREATE_PRVDMGR_FAILED : Could not create specified provider manager. Provider Name [String] Exception [String]

Explanation Could not create specified provider manager

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_TTS- 4 -SUBSYSTEM_MRCP_TTS_RELOAD_PRVD_FAILED : Could not reload specified provider. Method Name [String] Provider Name [String] Exception [String]

Explanation Could not reload specified provider

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_MRCP_TTS- 6 -SS_IN_SERVICE : MRCP TTS subsystem IN_SERVICE.

Explanation The MRCP TTS subsystem is in full service

Recommended Action No actions needed

Error Message
MIVR-SS_OB- 3 -CAUGHT_EXCEPTION : An exception has been caught by the Outbound subsystem.. Module Name [String] Exception [String]

Explanation An exception has been caught by the Outbound subsystem.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_OB- 6 -SS_INITIALIZING : Outbound subsystem initializing.

Explanation The Outbound subsystem is initializing

Recommended Action No actions needed

Error Message
MIVR-SS_OB- 5 -SS_SHUTDOWN : Outbound subsystem is shutdown.

Explanation The Outbound subsystem has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-SS_OB- 2 -SS_OUT_OF_SERVICE : Outbound subsystem in out of service.

Explanation The Outbound subsystem is out of service

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_OB- 3 -STAT_CONDITION_FAILED : A reporting stat condition has failed. Module Name [String] Condition that should always be true [String] A reporting entity [String]

Explanation A reporting stat condition has failed

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_OB- 3 -SIP_ADAPTER_INIT_ERROR : Failed to initialize SIP Adapter. Exception [String]

Explanation Failed to initialize SIP Adapter

Recommended Action No actions needed

Error Message
MIVR-SS_OB- 6 -DESTROYED : Outbound subsystem has been destroyed. Module Name [String]

Explanation Outbound subsystem has been destroyed

Recommended Action No actions needed

Error Message
MIVR-SS_OB- 5 -SS_SHUTTING_DOWN : Outbound subsystem is shutting down.

Explanation The Outbound subsystem is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-SS_OB- 3 -DIALER_ERROR : An exception in Outbound Dialer is prevented.. Module Name [String] Error reason [String]

Explanation An exception in Outbound Dialer is prevented.

Recommended Action No actions needed

Error Message
MIVR-SS_OB- 3 -ENCOUNTERS_THROWABLE : Error while processing messages from Outbound Msessage Queue. Description [String] Exception [String]

Explanation Error while processing messages from Outbound Msessage Queue

Recommended Action No actions needed

Error Message
MIVR-SS_OB- 6 -INTERRUPTED : Outbound Subsystem Component - Message Queue wait is interrupted. Description [String]

Explanation Outbound Subsystem Component - Message Queue wait is interrupted

Recommended Action No actions needed

Error Message
MIVR-SS_OB- 6 -SS_IN_SERVICE : Outbound subsystem in service.

Explanation The Outbound subsystem is in service

Recommended Action No actions needed

Error Message
MIVR-SS_OB- 6 -GETTING_DESTROYED : Outbound subsystem getting destroyed. Module Name [String]

Explanation Outbound subsystem getting destroyed

Recommended Action No actions needed

Error Message
MIVR-SS_RMCM- 3 -CAUGHT_EXCEPTION : An exception has been caught by the RmCm Subsystem.. Module Name [String] Exception [String]

Explanation An exception has been caught by the RmCm Subsystem.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RMCM- 5 -SS_SHUTDOWN : RmCm subsystem is shutdown.

Explanation The RmCm subsystem has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-SS_RMCM- 6 -SS_INITIALIZING : RmCm subsystem initializing.

Explanation The RmCm subsystem is initializing

Recommended Action No actions needed

Error Message
MIVR-SS_RMCM- 2 -SS_OUT_OF_SERVICE : RmCm subsystem in out of service.

Explanation The RmCm subsystem is out of service

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_RMCM- 5 -SS_SHUTTING_DOWN : RmCm subsystem is shutting down.

Explanation The RmCm subsystem is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-SS_RMCM- 3 -RECORDING_TAGGING_FAILED : MEDIASENSE_CALLBACK: Failed to tag recording.. This is the ID of the particular recording in MediaSense [String] Tags for this recording [String]

Explanation MEDIASENSE_CALLBACK: Failed to tag recording.

Recommended Action This recording cannot be searched/filtered based on tags. Use other criteria.

Error Message
MIVR-SS_RMCM- 3 -RECORDING_TAGGING_EXCEPTION : MEDIASENSE_CALLBACK: Exception in tagging recording.. This is the ID of the particular recording in MediaSense [String] Exception [String]

Explanation MEDIASENSE_CALLBACK: Exception in tagging recording.

Recommended Action An exception occured while attempting to create and apply tags to this recording. Hence, use other criteria to search/filter.

Error Message
MIVR-SS_RMCM- 6 -SS_IN_SERVICE : RmCm subsystem in service.

Explanation The RmCm subsystem is in service

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 6 -UNAVAILABLE_RNA_FLAG_MODIFIED : The Unavailable RNA flag is modified to. unavailable RNA flag [String]

Explanation The Unavailable RNA flag is modified to

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 2 -UNABLE_LOAD_CME_CONFIG : Unable to load CME config info. Module Name [String] Exception [String]

Explanation Unable to load CME config info

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_RM- 2 -UNABLE_LOAD_JTAPI_CONFIG : Unable to load JTAPI config info. Module Name [String]

Explanation Unable to load JTAPI config info

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_RM- 6 -ACTION_ON_RMON_SUPERVISOR : An action has been taken on this supervisor. Module Name [String] An action taken on this resource [String] The resource ID [String]

Explanation An action has been taken on this supervisor

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 6 -ACTION_ON_RESOURCE : An action has been taken on this resource. Module Name [String] An action taken on this resource [String] The resource ID [String]

Explanation An action has been taken on this resource

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 3 -ILLEGAL_SESSION_STATE_EXCEPTION : IllegalSessionStateException thrown.. Module Name [String] Exception [String] An App FW Session [com.cisco.session.Session]

Explanation An IllegalSessionStateException has been thrown by the App FW and caught by the Rm.

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 3 -INCOMPATIBLE_SESSION_EXCEPTION : IncompatibleSessionException thrown.. Module Name [String] Exception [String] An App FW Session [com.cisco.session.Session] An App FW CallContact [com.cisco.call.CallContact]

Explanation An IncompatibleSessionException has been thrown by the App FW and caught by the Rm.

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 3 -ACTION_ON_RESOURCE_FAILED : An action that has been taken on this resource has failed. Module Name [String] An action taken on this resource [String] The resource ID [String] A specific description for a trace [String]

Explanation An action that has been taken on this resource has failed

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_RM- 6 -TRYING_GET_JTAPI_PROVIDER : Trying to get JTAPI provider. Module Name [String]

Explanation Trying to get JTAPI provider

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 3 -ACTION_ON_ESD_FAILED : An action that has been taken on this ESD has failed. Module Name [String] An action taken on this resource and this ESD [String] The ESD ID [Int] A specific description for a trace [String]

Explanation An action that has been taken on this ESD has failed

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_RM- 6 -INTERRUPT_APP_TASK_FAILED : An error condition has prevented interruption on the application task.. Module Name [String] Exception [String]

Explanation An error condition has prevented interruption on the application task.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RM- 6 -CLEANING_UP_PROVIDER : Cleaning up provider. Module Name [String] The name of a variable [String]

Explanation Cleaning up provider

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 3 -UNABLE_TO_STOP_MONITORING : VoIP Monitor server is unable to stop monitoring. Module Name [String] A description for the nature of the error [String]

Explanation VoIP Monitor server is unable to stop monitoring

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RM- 3 -LOGOFF_FAILED : Logoff of resource failed. Module Name [String] The description of a message sent from/to the RM [String] A specific description for a trace [String]

Explanation Logoff of resource failed

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RM- 3 -ERROR_INVOKING_WF : Error invoking workflow. Module Name [String] Exception [String]

Explanation Error invoking workflow

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_RM- 6 -ACTION_ON_ROUTEPOINT : An action has been taken on this route point. Module Name [String] An action taken on this route point [String] The route point name [String]

Explanation An action has been taken on this route point

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 3 -ACTION_ON_APPLICATION_FAILED : An action that has been taken on this application has failed. Module Name [String] An action taken on this application [String] The application name [String] A specific description for a trace [String]

Explanation An action that has been taken on this application has failed

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_RM- 3 -GET_CISCO_CALLS_AT_AGENT_FAILED : Unable to get Cisco Calls at agent.. Module Name [String] Exception [String]

Explanation Unable to get the Cisco Calls present at the IAQ extension of the agent.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RM- 3 -PROBLEM_INIT_JTAPI_PROVIDER : JTAPI Exception while trying to initialize JTAPI provider. Module Name [String] Exception [String]

Explanation JTAPI Exception while trying to initialize JTAPI provider

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 3 -DUPLICATE_CHANNEL_EXCEPTION : DuplicateChannelException thrown.. Module Name [String] Exception [String] An App FW CallContact [com.cisco.call.CallContact]

Explanation A DuplicateChannelException has been thrown by the App FW and caught by the Rm.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RM- 3 -ACTION_ON_RMON_SUPERVISOR_FAILED : An action that has been taken on this resource has failed. Module Name [String] An action taken on this resource [String] The resource ID [String] A specific description for a trace [String]

Explanation An action that has been taken on this resource has failed

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_RM- 6 -RESOURCE_CONFIG_INFO : Resource configuration info. Module Name [String] A resource object [String] The ESD order [String]

Explanation Resource configuration info

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 3 -LOGIN_FAILED : Login of resource failed. Module Name [String] The description of a message sent from/to the RM [String] A specific description for a trace [String]

Explanation Login of resource failed

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RM- 6 -GOT_NEW_JTAPI_PROVIDER : Got new JTAPI provider. Module Name [String]

Explanation Got new JTAPI provider

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 3 -UNABLE_TO_START_MONITORING : VoIP Monitor server is unable to start monitoring. Module Name [String] A description for the nature of the error [String]

Explanation VoIP Monitor server is unable to start monitoring

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RM- 3 -ERROR_ALLOCATING_RESOURCE : An error has occurred while allocating this resource. Module Name [String] A specific description for a trace [String]

Explanation An error has occurred while allocating this resource

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RM- 3 -ACTION_ON_CTIPORTGROUP_FAILED : An action that has been taken on this cti port group has failed. Module Name [String] An action taken on this cti port group [String] The cti port group id [Int] A specific description for a trace [String]

Explanation An action that has been taken on this cti port group has failed

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_RM- 4 -INVALID_PARAMETER : Invalid parameter. The name of the method that invoked another method [String] The name of a parameter [String] The value of a parameter [java.lang.Object]

Explanation An invalid parameter was passed to a method

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RM- 3 -INVALID_STATE_TRANSITION : Invalid state transtion. Module Name [String] The description of a message sent from/to the RM [String] A specific description for a trace [String]

Explanation Invalid state transtion

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RM- 3 -GET_IAQ_EXTN_FAILED : getIAQExtn() failed because it was interrupted. Module Name [String] Exception [String]

Explanation getIAQExtn() failed because it was interrupted

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 2 -CTI_SERVER_INIT_FAILED_AFTER_UPDATING_TCP_PORT : CTI Server not initialized. A description for the nature of the exception [String] Exception [String]

Explanation The CTI Server is not initialized

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RM- 6 -REORDERING_ARL : The ARL of this ESD has been reordered. Module Name [String] The ESD ID [Int]

Explanation The ARL of this ESD has been reordered

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 2 -UNABLE_LOAD_WF : Unable to load the workflow. Module Name [String] Exception [String]

Explanation Unable to load the workflow

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_RM- 6 -METHOD_INTERRUPTED_BY_EXCEPTION : A method has been interrupted by an exception. Module Name [String] The name of the method invoked [String] Exception [String]

Explanation A method has been interrupted by an exception

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 6 -ACTION_ON_ESD : An action has been taken on this ESD. Module Name [String] An action taken on this resource and this ESD [String] The ESD ID [Int]

Explanation An action has been taken on this ESD

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 3 -ILLEGAL_CONTACT_STATE_EXCEPTION : IllegalContactStateException thrown.. Module Name [String] Exception [String] An App FW Session [com.cisco.session.Session] An App FW CallContact [com.cisco.call.CallContact]

Explanation An IllegalContactStateException has been thrown by the App FW and caught by the Rm.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RM- 6 -INTERRUPTED : This thread has been interrupted. Module Name [String] The name of the class that this thread belongs to [String]

Explanation This thread has been interrupted

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 2 -UNABLE_LOAD_SIP_CONFIG : Unable to load SIP config info. Module Name [String] Exception [String]

Explanation Unable to load SIP config info

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_RM- 2 -UNABLE_GET_JTAPI_PROVIDER : Unable to get new JTAPI provider. Module Name [String]

Explanation Unable to get new JTAPI provider

Recommended Action Verify and update the configuration and restart server

Error Message
MIVR-SS_RM- 3 -ACTION_ON_ROUTEPOINT_FAILED : An action that has been taken on this route point has failed. Module Name [String] An action taken on this route point [String] The route point name [String] A specific description for a trace [String]

Explanation An action that has been taken on this route point has failed

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_RM- 5 -SS_SHUTDOWN : Rm is shutdown.

Explanation The Rm has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 6 -ACTION_ON_APPLICATION : An action has been taken on this application. Module Name [String] An action taken on this application [String] The application name [String]

Explanation An action has been taken on this application

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 6 -ESD_CONFIG_INFO : ESD configuration info. Module Name [String] An ESD object [String] The resource selection criterion [String] The contact queueing criterion [String] The auto-work option [String] The resource order [String]

Explanation ESD configuration info

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 3 -COULD_NOT_REINIT_RMCM_SS : Could not reinitialize RmCm subsystem. Module Name [String] A specific description for a trace [String]

Explanation Could not reinitialize RmCm subsystem

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_RM- 3 -ERROR_CONFIGURING_WF : Error configuring workflow. Module Name [String] A specific description for a trace [String] The ESD ID [Int] The resource ID [String] Exception [String]

Explanation Error configuring workflow

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_RM- 2 -UNABLE_GET_PROVIDER : Unable to get provider. Module Name [String] A specific description for a trace [String]

Explanation Unable to get provider

Recommended Action Verify and update the configuration and restart server

Error Message
MIVR-SS_RM- 6 -ACTION_ON_RESOURCE_IN_ESD : An action has been taken on this resource and this ESD. Module Name [String] An action taken on this resource and this ESD [String] The resource ID [String] The ESD ID [Int]

Explanation An action has been taken on this resource and this ESD

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 6 -TCP_PORT_MODIFIED : The TCP port of CTI server is modified to. TCP PORT of CTI SERVER [String]

Explanation The TCP port of CTI server is modified to

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 1 -UNABLE_GET_JTAPI_PEER : Unable to get JTAPI peer object. Module Name [String]

Explanation Unable to get JTAPI peer object

Recommended Action Verify and update the configuration and restart server

Error Message
MIVR-SS_RM- 3 -CLEANUP_STUCK_CONTACT : Removed stuck contact. ID of an RmCm Contact [LogParameter.STRING] Phone number of an endpoint [LogParameter.STRING] The name of the method that invoked another method [String]

Explanation The system detected an old contact and removed it

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RM- 3 -UNABLE_TO_GET_USER : Unable to get user object. Module Name [String] The description of a message sent from/to the RM [String] A specific description for a trace [String]

Explanation Unable to get user object

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RM- 3 -CAUGHT_EXCEPTION : An exception has been caught by the Rm.. Module Name [String] Exception [String]

Explanation An exception has been caught by the Rm.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RM- 3 -DROP_CALL_FAILED : Dropping a call failed. Module Name [String] A description for the nature of the exception [String] Exception [String]

Explanation Dropping a call failed

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 3 -RESOURCE_DOES_NOT_EXIST : This resource does not exist. Module Name [String] The description of a message sent from/to the RM [String]

Explanation This resource does not exist

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_RM- 2 -UNABLE_LOAD_JASMIN_CONFIG : Unable to load Jasmin config info. Module Name [String] Exception [String]

Explanation Unable to load Jasmin config info

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_RM- 6 -ACTION_ON_CTIPORTGROUP : An action has been taken on this cti port group. Module Name [String] An action taken on this application [String] The application name [String]

Explanation An action has been taken on this cti port group

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 3 -VOIP_MONITOR_SERVER_OBJ_UNAVAILABLE : Unable to access VoIP Monitor Subsystem's Corba object. Module Name [String] The name of the method that invoked another method [String]

Explanation Unable to access VoIP Monitor Subsystem's Corba object

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RM- 3 -RESOURCE_LINE_RESTRICTED : Resource's line is restricted. Module Name [String] The description of a message sent from/to the RM [String]

Explanation Resource's line is restricted

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 3 -RESOURCE_DEVICE_BUSY : Resource's device is busy. Module Name [String] The description of a message sent from/to the RM [String]

Explanation Resource's device is busy

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 3 -RESOURCE_STATE_CHANGE_FAILED : Resource state change failed. Module Name [String] The description of a message sent from/to the RM [String] A specific description for a trace [String]

Explanation Resource state change failed

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RM- 4 -UNEXPECTED_MSG : An unexpected message was received. Module Name [String] The description of a message sent from/to the RM [String] A specific description for a trace [String]

Explanation An unexpected message was received

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RM- 3 -RIMGR_METHOD_INVOC_ERROR : RIMgr has had a problem invoking a method. Module Name [String] The name of the method that invoked another method [String] The name of the method invoked [String] The error message resulting from a method invocation [String]

Explanation RIMgr has had a problem invoking a method

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RM- 3 -ENCOUNTERS_THROWABLE : This thread has encountered a Throwable exception. Module Name [String] The name of the class that this thread belongs to [String] Exception [String]

Explanation This thread has encountered a Throwable exception

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 3 -RESOURCE_DEVICE_RESTRICTED : Resource's device is restricted. Module Name [String] The description of a message sent from/to the RM [String]

Explanation Resource's device is restricted

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 3 -CONTACT_INACTIVE_EXCEPTION : ContactInactiveException thrown.. Module Name [String] Exception [String] An App FW CallContact [com.cisco.call.CallContact]

Explanation A ContactInactiveException has been thrown by the App FW and caught by the Rm.

Recommended Action No actions needed

Error Message
MIVR-SS_RM- 3 -ESD_DOES_NOT_EXIST : This ESD does not exist. Module Name [String] The description of a message sent from/to the RM [String]

Explanation This ESD does not exist

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_RM- 3 -RESOURCE_DEVICE_OFF : Resource's device is off. Module Name [String] The description of a message sent from/to the RM [String]

Explanation Resource's device is off

Recommended Action No actions needed

Error Message
MIVR-SS_RTR- 6 -SS_INITIALIZING : RTR subsystem initializing.

Explanation The RTR subsystem is initializing

Recommended Action No actions needed

Error Message
MIVR-SS_RTR- 5 -SS_SHUTDOWN : RTR subsystem is SHUTDOWN.

Explanation The RTR subsystem has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-SS_RTR- 6 -SUBSYSTEM_RTR_LOG_OBJECT_NULL : SUBSYSTEM_RTR_LOG_OBJECT_NULL.

Explanation Log object of the RTR Subsystem is null

Recommended Action No actions needed

Error Message
MIVR-SS_RTR- 1 -SS_PARTIAL_SERVICE : RTR subsystem is in PART_SERVICE.

Explanation The RTR subsystem is in partial service

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_RTR- 3 -SS_OUT_OF_SERVICE : RTR subsystem is OUT_OF_SERVICE.

Explanation RTR subsystem is either disabled or failed to be loaded

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_RTR- 5 -SS_SHUTTING_DOWN : RTR subsystem is SHUTTING_DOWN.

Explanation The RTR subsystem is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-SS_RTR- 6 -CONTACT_CLEARED : Administrator cleared the contact from the system. Administrator who cleared the contact [String] ID of an RmCm Contact [String] The name of the method that invoked another method [String] Time at which the contact clear was issued [String]

Explanation Administrator cleared the contact from the system

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_RTR- 6 -SUBSYSTEM_RTR_LOG_OBJECT_NOT_NULL : SUBSYSTEM_RTR_LOG_OBJECT__NOT_NULL.

Explanation Log object of the RTR Subsystem is not null

Recommended Action No actions needed

Error Message
MIVR-SS_RTR- 6 -SS_IN_SERVICE : RTR subsystem IN_SERVICE.

Explanation The RTR subsystem is in full service

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 3 -UNABLE_ADD_CALL_OBSERVER : Unable to add a call observer . All Call ids [String] Failure type for the CallControl error [String] Exception [String]

Explanation Unable to add a call observer during the specified operation

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -ADD_CONTACT_SESSION_FAIL : Add Contact fails. Contact id [Int] Contact implementation id [String] Session id [Long] Exception [String]

Explanation Unable to add the specified call contact to the given call session

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -CONSULT_FAILED : Consult failed . All Call ids [String] Extension [String] Exception [String] Failure reason [String]

Explanation Consult failed to the specified extension

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 1 -SS_OUT_OF_SERVICE : JTAPI subsystem in out of service. Failure reason [String]

Explanation The JTAPI subsystem could not establish a connection with the Call Manager or no CTI Ports could be initialized

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_TEL- 3 -CALL_CONTROL_INTERRUPT : Interrupted while doing a call control operation . All Call ids [String] Failure type for the CallControl error [String] Exception [String]

Explanation Call Control operation for the specified call was interrupted

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -RTP_CONTROLLER_FAIL : RTP Controller fails. Channel Class [String] Contact id [Int] Contact implementation id [String] Contact Class [String] Contact Type [String] Failure reason [String] Exception [String]

Explanation Failure in the RTP controller of the dialog channel in the given call contact

Recommended Action Verify and update the application and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 3 -REFRESH_CTI_PORT_GROUP_FAILED : Refresh of CTI Port group failed. Old Group id [Int] Group id [Int] Exception [String]

Explanation Refresh of CTI Port group failed because IDs are invalid

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 4 -CONFERENCE_END_FAILED : Conference End failed . All Call ids [String]

Explanation Conference End event indicates a failure

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -REMOVE_SESSION_MAP_FAIL : Remove session mapping fails. Contact implementation id [String] Session id [Long] Exception [String]

Explanation Unable to remove the specified mapping id from the given call session

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 2 -SS_PARTIAL_SERVICE : JTAPI subsystem in partial service. Failure reason [String]

Explanation Some CTI Ports, CTI Route points or JTAPI Triggers could not be properly initialized

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_TEL- 6 -GET_NEW_PROVIDER : Attempt to get JTAPI provider.

Explanation Attempting to get a new JTAPI provider

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 3 -PROVIDER_EVENT_PROCESS_INTERRUPT : Interrupted while processing a provider event . JTAPI provider name [String] Event [String] Exception [String]

Explanation Provider event processing for the specified provider was interrupted

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -CONFIG_REFRESH_FAILED : Config refresh failed. Exception [String]

Explanation Config refresh failed

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 3 -ABORT_CALL : Aborting a call for reason. All Call ids [String] Reason for aborting a call [String] Exception [String]

Explanation Aborting a specified call for the given reason

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -UNABLE_PROCESS_CALL : Unable to process a call. All Call ids [String] Route Address [String] The type of call process [String] Exception [String]

Explanation Unable to process a call at the specified CTI Route point

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -CTIPG_ROUTE_END_EVENT : CTI Port Group RouteEnd event. Route Session [String] Exception [String]

Explanation The CTI Port Group received a RouteEnd event and was interrupted while trying to recover the CTI Port

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -NO_TERMINAL_CONNECTION : Unable to get TerminalConnection object . All Call ids [String] List of Active Connections [String] The type of call event [String]

Explanation Unable to get terminal connection for the final call in a conference or transfer scenario

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -MULT_XFER_FAIL : Multiple transfer failures. All Call ids [String]

Explanation Experiencing multiple transfer failures..aborting call

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 6 -NO_TRIGGER_FOR_CTIPG : No Triggers uses CTI Port Group. Group id [Int]

Explanation There isn't any Triggers (CTI Route points) that uses the CTI Port Group

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 3 -CTI_PORT_GROUP_FAILURE : CTI Port Group operation failure. Group Channel Type [String] Group id [Int] Failure type for the CTI Port Group error [Int] Failure reason [String] Exception [String]

Explanation Failure occurred while trying to operate on a CTI Port group

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 3 -ROUTE_FAILED : Route failed . All Call ids [String] List of Active Connections [String] Extension [String] Exception [String] Failure reason [String]

Explanation Failed to redirect call from route point to cti port of the specified extension

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -NULL_LAST_REDIRECTED_ADDR : Got a Null Last Redirected Address. Call id [Int] Media id [String] CTI Port [String]

Explanation JTAPI returns a null last redirected address, probably because the call did not come from a route point

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -JTAPI_PEER_ERROR : Unable to get JTAPI Peer. Exception [String]

Explanation JTAPI Unable to get a JTAPI Peer object

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 3 -CONFIG_CREATED_FAILED : Config creation failed. Exception [String]

Explanation Config creation failed

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 4 -CTI_PORT_HAS_ACTIVE_CONN : Some lingering connections in CTI Port. CTI Port [String] List of Active Connections [String] All Call ids [String]

Explanation An idle CTI Port still show some active connections

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 6 -SS_REFRESH : JTAPI Subsystem Refresh invoked.

Explanation JTAPI Subsystem Refresh invoked

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 1 -UNABLE_REGISTER_CTIRP : Unable to register CTI Route point . Route Address [String] Failure reason [String] Exception [String]

Explanation Unable to register a CTI route point with the JTAPI Provider

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 5 -CTIPG_ROUTE_EVENT : CTI Port Group route event. Route Session [String] Route Address [String] Failure reason [String] Exception [String]

Explanation The CTI Port Group Route event is terminating the route session

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -ADD_SESSION_MAP_FAIL : Add session mapping fails. Contact implementation id [String] Session id [Long] Exception [String]

Explanation Unable to add the specified mapping id to the given call session

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -CALL_CONTROL_EXCEPTION : Received exception while doing a call control operation . All Call ids [String] Failure type for the CallControl error [String] Failure reason [String] Exception [String]

Explanation Call Control operation for the specified call failed due to the specified exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -WAIT_FOR_CONSULT_COMPLETION_FAILED : Wait for consult completion failed . All Call ids [String]

Explanation Did not receive the Transfer End or Conference End event

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 4 -TIMEOUT_WAITING_FOR_TRANSFER_END : Timeout waiting for the TransferEnd/ConferenceEnd. Contact id [Int] Contact implementation id [String] Task id [Long]

Explanation Call control operation failed due to timeout while waiting for the TransferEnd/ConferenceEnd

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -REFRESH_ALL_CTI_PORT_GROUPS_FAILED : CTI Port group refresh failed. Exception [String]

Explanation CTI Port group refresh failed

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 3 -REJECT_CALL : Rejecting a call for reason. Call id [Int] Media id [String] Failure reason [String]

Explanation Rejecting a specified call for the given reason

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -CONFIG_MODIFIED_FAILED : Config modify failed. Exception [String]

Explanation Config modify failed

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 3 -CONFIG_DELETED_FAILED : Config deletion failed. Exception [String]

Explanation Config deletion failed

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 3 -CLEAN_SESSION_MAP_FAIL : Clean session mappings fails. All Call ids [String] Starting session mapping id [String] Ending session mapping id [String] Exception [String]

Explanation Unable to clean the specified range of session mapping ids in the session of the given call. This may be due to an unsupported call scenario.

Recommended Action Verify and update the application and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 5 -NO_CTIPG_CONFIGREP : No CTI Port Group in config repository.

Explanation No CTI Port Group were found in the config repository

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 3 -HOLD_FAILED : Hold failed . All Call ids [String] Exception [String] Failure reason [String]

Explanation Failed to hold a call due to the specified exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -CALL_CONTROL_INVAL_STATE : Invalid state for Call Control operation. All Call ids [String] Failure type for the CallControl error [String] Connection State [Int] Failure reason [String] Exception [String]

Explanation Call Control operation for the specified call failed due to the specified invalid connection state

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -RECOVERY_INTERRUPTED : CTI Port Recovery fails due to interruption. CTI Port [String] Exception [String]

Explanation Recovery of the specified CTI Port fails due to interruption

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -REFRESH_TRIGGER_FAILED : Refresh of Trigger failed. Route Address [String] Exception [String]

Explanation Refresh of Trigger failed because of the exception

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 6 -DEADLOCK_AVOIDED : Potential deadlock avoided . CTI Port [String]

Explanation Potential deadlock avoided for the specified CTI Port

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 6 -APP_LOAD_SUCCESS : Successfully loaded application. Application [String] Route Address [String]

Explanation Successfully loaded application for the CTI Route point

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 3 -UNABLE_ACCESS_JTAPI_PROVIDER_ADDR : The JTAPI provider addresses cannot be determined. Exception [String]

Explanation The JTAPI subsystem can not access the JTAPI provider's addresses

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -DISCONNECT_FAILED : Disconnect failed . All Call ids [String] Failure reason [String] Exception [String]

Explanation Failed to disconnect a call due to the specified exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 6 -SS_IN_SERVICE : JTAPI subsystem in service.

Explanation The JTAPI subsystem is in service

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 3 -RMI_REBIND_FAILED : Unable to register remote interface. Exception [String]

Explanation A remote interface could not be binded to the RMI registry; remote access for dynamic update or other functions will not be available

Recommended Action Verify the RMI configuration and restart server

Error Message
MIVR-SS_TEL- 2 -DEADLOCK_DETECTED : Potential deadlock detected . CTI Port [String]

Explanation Potential deadlock detected for the specified CTI Port

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -CALL_EVENT_PROCESS_INTERRUPT : Interrupted while processing a call control event . All Call ids [String] Failure type for the CallControl error [String] Exception [String]

Explanation Call Control event processing for the specified call was interrupted

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -ANSWER_FAILED : Answer failed . All Call ids [String] Exception [String] Failure reason [String]

Explanation Failed to answer a call due to the specified exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -REDIRECT_FAILED : Redirect failed . All Call ids [String] Extension [String] Exception [String] Failure reason [String]

Explanation Redirect failed to the specified extension

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -UNABLE_CANCEL_CALLBACK : Unable to cancel Callback for CTI Route point. Route Address [String] Exception [String]

Explanation Unable to cancel the callback for the specified CTI Route Point

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 3 -TAKE_BACK_TRANSFER_FAILED : Take back and transfer failed . All Call ids [String] Extension [String] Exception [String]

Explanation Take back and transfer failed to the specified extension

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -SEND_DTMF_FAILED : SendDtmf failed . All Call ids [String] Exception [String] Failure reason [String]

Explanation Failed to send DTMFs due to the specified exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 4 -RECOVERY_THRD_EXCEPTION : CTI Port Recovery fails due to unhandled exception. Recovery Thread Name [String] Exception [String]

Explanation The specified Recovery Thread fails due to an unhandled exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 5 -AUDIO_TREATMENT_FAILED : Audio treatment failed . All Call ids [String] Audio treatment [String] Exception [String]

Explanation Audio treatment failed

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -UNABLE_FIND_LOCALE_CONFIG_REP : Config Repository does not contain valid Locale information. Route Address [String] Exception [String]

Explanation Config Repository does not contain valid locale information in the specified CTI Route point

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 4 -NO_CONSULT_XFER_HELD_EVENT : Held Event not received for failed consult Transfer . All Call ids [String] Extension [String]

Explanation Held Event was not received for a failed consult Transfer to the specified extension

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -UNABLE_LOAD_TRIGGER : Unable to load Trigger. Application Trigger [String] Failure reason [String] Exception [String]

Explanation Unable to load Trigger because of the specified failure

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 6 -SS_LOGIN : JTAPI Login String. Module Name [String] JTAPI login string [String]

Explanation JTAPI Login String

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 3 -NO_TERMINAL_OBJ : Unable to get Terminal Object for CTI Port . CTI Port [String]

Explanation Unable to get terminal object for the specified CTI Port

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 3 -TRANSFER_FAILED : Transfer failed . All Call ids [String] Extension [String] Failure reason [String] Exception [String]

Explanation Transfer failed to the specified extension

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 4 -UNABLE_READ_DROPPED : Unable to read DROPPED event in message queue . CTI Port [String] Exception [String]

Explanation Unable to read DROPPED event in message queue for ConsultCallObserver due to the specified exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -ADD_GROUP_LISTENER_FAIL : Unable to register as a group config listener. Module Name [String] Group Channel Type [String] Exception [String]

Explanation Failed to register self as a group config listener. Any changes in group configuration will not get updated until the system restarts

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 3 -UNABLE_REGISTER_CTIPORT : Unable to register CTI Port . CTI Port [String] Failure reason [String] Exception [String]

Explanation Unable to register a CTI Port with the JTAPI Provider

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 4 -CTIPORT_REMOVE_OBSERVER : Error while removing CTI Port observer. CTI Port [String] Exception [String]

Explanation Error occurred while removing observer for the CTI Port

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 3 -NO_SESSION_FOR_CONTACT : Session mapping for the given mapping id is not found. Contact implementation id [String] Failure reason [String]

Explanation Session mapping for the given mapping id is not found

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 4 -GROUP_FOR_TRIGGER_NOT_READY : Groups in JTAPI trigger is not ready. Route Session [String] Route Address [String]

Explanation Some groups in the JTAPI trigger is not ready to accept any call, either because the system initialization has not completed or there is an error in the group initialization.

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_TEL- 4 -TRANSFER_END_FAILED : Transfer End failed . All Call ids [String]

Explanation Transfer End event indicates a failure

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -MAKE_CALL_FAILED : Outbound call failed . All Call ids [String] CTI Port [String] Exception [String] Failure reason [String]

Explanation Failed to make an outbound call due to the specified exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 4 -UNABLE_DISPOSE_CTIPORT : Unable to dispose CTI Port . CTI Port [String] Exception [String]

Explanation Unable to dispose a CTI Port

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 6 -PROVIDER_CLEANUP : Cleaning up JTAPI provider. Module Name [String] JTAPI provider name [String]

Explanation Cleaning up JTAPI provider

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 3 -UNABLE_FIND_CTIRP_CONFIG_REP : Config Repository does not contain CTI Route point. Route Address [String]

Explanation Config Repository does not contain the specified CTI Route point

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 6 -CTI_ADDRESS_EVENT : Receives. Event [String] Addr [String]

Explanation CTI has sent an event for Port or Route Point

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 3 -ACTIVE_CALL_REJECTED : Active call rejected by timer or due to reRoute. Call id [Int] Media id [String] CTI Port [String]

Explanation Active call was rejected by timer on CTI Port or due to reRoute

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 6 -JTAPI_PROVIDER_EVENT : JTAPI Provider state is changed. JTAPI provider name [String] Event [String]

Explanation JTAPI Provider state is changed

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 6 -RECREATE_CTI_PORT : Recreating a deadlocked CTI Port. CTI Port [String]

Explanation Recreating a deadlocked CTI Port

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 5 -SS_SHUTDOWN : JTAPI subsystem is shutdown.

Explanation The JTAPI subsystem has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 4 -UNABLE_INTERRUPT_CTIPORT : Unable to interrupt the CTI Port. CTI Port [String] Exception [String]

Explanation Unable to interrupt the CTI Port

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 2 -UNABLE_REGISTER_CALLBACK : Unable to register Callback for CTI Route point. Route Address [String] Exception [String]

Explanation Unable to register a callback for the specified CTI Route Point

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 4 -NO_TRANSFER_HELD_EVENT : Held Event not received for failed Transfer . All Call ids [String] Extension [String]

Explanation Held Event was not received for a failed Transfer to the specified extension

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -CTIRP_REMOVE_OBSERVER : Error while removing a route address observer . Route Address [String] Exception [String]

Explanation Error occurred while removing observer for the route address

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 3 -NO_CONNECTION : Unable to get Connection object . All Call ids [String] List of Active Connections [String] The type of call event [String]

Explanation Unable to get connection for the final call in a conference or transfer scenario

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 1 -DEADLOCK_THRESH_EXCEEDED : Deadlock threshold exceeded . Deadlock info [String]

Explanation Deadlock threshold exceeded

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 5 -CTIPG_REROUTE_EVENT : CTI Port Group ReRoute event. Route Session [String] Route Address [String] CTI Port [String] Time Lapse [Long]

Explanation The CTI Port Group received a ReRoute event and is terminating the route session

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -UNABLE_LOAD_APP : Unable to load Application. Application [String] Failure reason [String] Route Address [String] Application Id [Int] Exception [String]

Explanation Unable to load application because of the specified failure

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 6 -CTIPORT_RECOV_THR_START : Starting CTI Port Recovery Thread. Recovery Thread Name [String]

Explanation Starting CTI Port Recovery Thread

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 3 -UNABLE_RECREATE_CTIRP : Unable to recreate a CTI Route Point. Route Address [String] Exception [String]

Explanation Unable to recreate a CTI Route Point due to the specified exception

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 6 -SS_INITIALIZING : JTAPI subsystem initializing. Version Info [String]

Explanation The JTAPI subsystem is initializing

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 3 -MISSING_CHANNEL : Missing channel. Channel Class [String] Contact id [Int] Contact implementation id [String] Contact Class [String] Contact Type [String] Exception [String]

Explanation A channel of the specified class is not available with the given call contact

Recommended Action Verify and update the application

Error Message
MIVR-SS_TEL- 3 -WAIT_FOR_CALL_AND_MEDIA_ACTIVE_FAILED : Waiting for call and media active failed. All Call ids [String] Time Lapse [Long]

Explanation Waiting for call and media active failed

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 3 -REJECT_FAILED : Reject failed . All Call ids [String] Exception [String]

Explanation Failed to reject a call due to the specified exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 5 -INTERRUPT_EXCEPTION_RECEIVED : InterruptedException received. Module Name [String] Exception [String]

Explanation Received an InterruptedException during operation

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 6 -RECOVER_CTI_RP : Recovering a CTI Port for the CTI Route Point. Route Address [String] CTI Port [String] All Call ids [String] Number of Sessions [Int]

Explanation Recovering a CTI Port for the CTI Route Point which has specified number of active sessions

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 3 -ADD_CHANNEL_FAIL : Add Channel fails. Channel Class [String] Contact id [Int] Contact implementation id [String] Contact Class [String] Contact Type [String] Exception [String]

Explanation Unable to add the specified channel to the given call contact

Recommended Action Verify and update the application and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 5 -CTIPG_ROUTE_ADDR_NOT_EXIST : CTI Port Group route address does not exist. Route Session [String] Route Address [String]

Explanation The CTI Route point does not exist in route table

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_TEL- 3 -UNHOLD_FAILED : Unhold failed . All Call ids [String] Exception [String] Failure reason [String]

Explanation Failed to unhold a call due to the specified exception

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_TEL- 4 -EVENT_NOT_RECEIVED : Event not received. All Call ids [String] Missing Event [String] Exception [String]

Explanation The specified event is not received

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 5 -SS_SHUTTING_DOWN : JTAPI subsystem is shutting down.

Explanation The JTAPI subsystem is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-SS_TEL- 3 -UNABLE_RECREATE_CTI_PORT : Unable to recreate a CTI Port. CTI Port [String] Exception [String]

Explanation Unable to recreate a CTI Port due to the specified exception

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-SS_VB- 3 -VOICEBROWSER_GENERIC_ERROR : VoiceBrowser generic error. Error description [String]

Explanation VoiceBrowser generic error

Recommended Action In such case you would like to turn on debug trace and get more information. Please contact Cisco support for this

Error Message
MIVR-SS_VB- 3 -ERROR_CONNECTING_TO_TTS_SERVER : Error connecting to Text-to-Speech server. TTS Server name or IP address [String]

Explanation Error in connecting to TTS server

Recommended Action Check the TTS setup and configuration.

Error Message
MIVR-SS_VB- 3 -NUANCE_FATAL_ERROR : Fatal error in Nuance. Error message from Nuance [String]

Explanation An error has occurred in Nuance service(s)

Recommended Action Check the Nunance setup and configuration. Lookout for any other Nuance errors.

Error Message
MIVR-SS_VB- 3 -NUANCE_NONFATAL_ERROR : Non Fatal error in Nuance. Error message from Nuance [String]

Explanation An error has occurred in Nuance service(s)

Recommended Action Check the Nunance setup and configuration.

Error Message
MIVR-SS_VB- 3 -ERROR_WITH_PARSER : Error encountered instantiating the XML Parser. Parser Name [String] Error detail [String]

Explanation An error has occurred in instantiating an XML Parser

Recommended Action Check the system setup depending on the specidfic error that has occured

Error Message
MIVR-SS_VB- 4 -MALFORMED_URI_EXCEPTION : Given URI is malformed. URI [String]

Explanation The given URI has some problem

Recommended Action Please check the VoiceXML Application that uses this URI and correct it as appropriate.

Error Message
MIVR-SS_VB- 4 -IO_EXCEPTION_IN_FETCHING_URI : Given URI throws I/O exception. URI [String]

Explanation The given URI has some I/O problem

Recommended Action Please check the VoiceXML Application that uses this URI and correct it as appropriate.

Error Message
MIVR-SS_VB- 4 -GRAMMAR_PARSE_EXCEPTION : Given URI throws I/O exception. URI [String] URI [String] URI [String]

Explanation The given URI has some I/O problem

Recommended Action Please check the VoiceXML Application that uses this URI and correct it as appropriate.

Error Message
MIVR-SS_VB- 4 -VXML_DOCUMENT_PARSE_EXCEPTION : Exception in parsing VoiceXML document. URI of VoiceXML Document [String]

Explanation Parsing the given vxml document encountered some problem

Recommended Action Please check the VoiceXML file as indicated by the URI and correct it as appropriate.

Error Message
MIVR-SS_VOIPMON_SRV- 6 -SS_INITIALIZING : VOIP subsystem initializing.

Explanation The VOIP subsystem is initializing

Recommended Action No actions needed

Error Message
MIVR-SS_VOIPMON_SRV- 5 -SS_SHUTDOWN : VOIP subsystem is shutdown.

Explanation The VOIP subsystem has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-SS_VOIPMON_SRV- 1 -SS_OUT_OF_SERVICE : VOIP subsystem in out of service.

Explanation The VOIP subsystem is out of service

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_VOIPMON_SRV- 3 -FAIL_FIND_NET_INFO : Fail to obtain network information. Module Name [String] A specific description for a trace [String] Exception [String]

Explanation Could not obtain network information

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_VOIPMON_SRV- 5 -SS_NOT_CONFIGURED : VOIP subsystem in not configured.

Explanation The VOIP subsystem is not configured

Recommended Action Verify and update the configuration

Error Message
MIVR-SS_VOIPMON_SRV- 3 -ERROR_LOAD_REGISTRY : Fail to read registry. Module Name [String] A specific description for a trace [String] Exception [String]

Explanation Could not read registry entry

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_VOIPMON_SRV- 6 -SS_PARTIAL_SERVICE : VOIP subsystem in partial service.

Explanation The VOIP subsystem is in partial service

Recommended Action No actions needed

Error Message
MIVR-SS_VOIPMON_SRV- 5 -SS_SHUTTING_DOWN : VOIP subsystem is shutting down.

Explanation The VOIP subsystem is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-SS_VOIPMON_SRV- 3 -CORBA_INVOKE_ERROR : Fail to invoke corba call. Module Name [String] A specific description for a trace [String] Exception [String]

Explanation Could not invoke corba method

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_VOIPMON_SRV- 3 -VOIP_OPERATION_ERROR : VOIP subsystem operation error. Module Name [String] A specific description for a trace [String] Exception [String]

Explanation VOIP subsystem operation error

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_VOIPMON_SRV- 3 -FAIL_START_KEEP_ALIVE_THREAD : Fail to start keep alive thread for each monitoring connection. Exception [String]

Explanation Could not start keep alive thread for the monitoring Corba call

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_VOIPMON_SRV- 3 -ERROR_LOAD_LDAP : Fail to read LDAP INFO. Module Name [String] A specific description for a trace [String] Exception [String]

Explanation Could not read LDAP content

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-SS_VOIPMON_SRV- 6 -SS_IN_SERVICE : VOIP subsystem in service.

Explanation The VOIP subsystem is in service

Recommended Action No actions needed

Error Message
MIVR-STEP_CALL_CONTROL- 4 -INVALID_DECODETYPE : Invalid decoding type. Task id [Long] Step Name [String] Decoding Type [Int]

Explanation The decoding type is NOT recognised

Recommended Action Verify and update the configuration

Error Message
MIVR-STEP_CALL_CONTROL- 4 -INVALID_ENCODETYPE : Invalid encoding type. Task id [Long] Step Name [String] Encoding Type [Int]

Explanation The encoding type is NOT recognised

Recommended Action Verify and update the configuration

Error Message
MIVR-STEP_CALL_CONTROL- 4 -REDIRECT_VAR_NULL : Redirect's variable is null or not a String. Task id [Long]

Explanation Redirect's variable for the specified taskId is null or not a String

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-STEP_CALL_CONTROL- 4 -INVALID_ENCODE_FORMAT : Invalid format for encoding type. Task id [Long] Step Name [String] Encoding Type [String] Decoded Value [String]

Explanation The decoded value has a invalid format for encoding

Recommended Action Verify and update the configuration

Error Message
MIVR-STEP_MEDIA_CONTROL- 4 -LDAP_REPOS_ERROR : Repository error, error connecting to LDAP server. Task id [Long] Exception [String]

Explanation Repository error, error connecting to LDAP server, due to exception:

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-STEP_MEDIA_CONTROL- 4 -WRONG_DATE_FORMAT : Date has wrong format. Task id [Long] Variable [String] Date/time Value [String]

Explanation The Date value for the given variable in the specified task has wrong format

Recommended Action Verify and update the application

Error Message
MIVR-STEP_MEDIA_CONTROL- 3 -RECORDING_GENERAL_EX : General Recording Exception. Exception [String]

Explanation There is exception occured during recording step execution.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-STEP_MEDIA_CONTROL- 4 -WRONG_TIME_FORMAT : Time has wrong format. Task id [Long] Variable [String] Date/time Value [String]

Explanation The Time value for the given variable in the specified task has wrong format

Recommended Action Verify and update the application

Error Message
MIVR-STEP_MEDIA_CONTROL- 3 -RECORDING_PREPROCESS_EX : Preprocess failed for Recording Step. Exception [String]

Explanation There is exception occured during recording step preprocess.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-STEP_MEDIA_CONTROL- 4 -SPOKEN_NAME_UPLOAD_ERROR : Unable to upload spoken name.

Explanation Unable to contact LDAP Directory or LDAP Directory has wrong schema

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-STEP_MEDIA_CONTROL- 3 -RECORDING_CUSTOMIZER_EX : Customizer failed for Recording Step. Exception [String]

Explanation There is exception occured during recording step customizer.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-STEP_MEDIA_CONTROL- 3 -RECORDING_EXECUTE_EX : Execute failed for Recording Step. Exception [String] Task id [Long]

Explanation There is exception occured during recording step execute.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-STEPS_CONTACT- 4 -STEPS_CONTACT : A contact step is running.. Task id [Long]

Explanation An Exception is thrown from a Contact Step.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-STEPS_DB- 3 -MISSING_DB_NAME : Database name missing. Task ID [String] Step Name [String]

Explanation Resource does not have a name

Recommended Action Specify a resource name using DBGetCustomizer

Error Message
MIVR-STEPS_DB- 3 -MISSING_DB_RESOURCE_NAME : Database resource name missing. Task ID [String] Step Name [String]

Explanation Does not have a resource by that name

Recommended Action Specify a resource name using DBGetStep Customizer

Error Message
MIVR-STEPS_DB- 3 -MISSING_SQL_STATEMENT : SQL statement missing. Task ID [String] Step Name [String]

Explanation SQL statement not given.

Recommended Action Provide a SQL statement.

Error Message
MIVR-STEPS_DB- 4 -DB_CONNECTION_NOT_AVAILABLE : Database connection not available for the given Database name. Task ID [String] Step Name [String] Database Name [String]

Explanation Could not connect to the database.

Recommended Action Verify that the database is available.

Error Message
MIVR-STEPS_DB- 3 -DB_NAME_UNCHANGEABLE : Invalid Usage : May not change database name in Query Reuse. Task ID [String] Step Name [String] Old Database name [String] New Database name [String]

Explanation Cannot resuse DB resources between different data sources/databases

Recommended Action Must use a different database resource for each database.

Error Message
MIVR-STEPS_DB- 3 -EXECUTE_SQL_UPDATE_EXCEPTION : Error during executing SQL Update. Task ID [String] Step Name [String] SQL State [String] SQL Error Code [String]

Explanation Exception occurred while executing the query

Recommended Action Check the SQl statement and databse availability. Copy the error message exactly as it appears on the console or in the system log, and contact your Database Administrator

Error Message
MIVR-STEPS_DB- 3 -EXCEPTION_OCCURED : Exception occured. Task ID [String] Step Name [String]

Explanation Exception occurred while executing the query

Recommended Action Check the SQl statement and databse availability. Copy the error message exactly as it appears on the console or in the system log, and contact your Database Administrator

Error Message
MIVR-STEPS_DB- 3 -MISSING_DB_RESOURCE : Missing Database resource. Task ID [String] Step Name [String]

Explanation Resource does not have a name

Recommended Action Specify a resource name using DBReleaseStep Customizer

Error Message
MIVR-STEPS_DB- 3 -NO_DB_RESOURCE_CONFIGURED : Database Resource not configured. Task ID [String] Step Name [String]

Explanation Does not have a resource by that name

Recommended Action Specify a resource name using DBGetStep Customizer

Error Message
MIVR-STEPS_DB- 3 -EXECUTE_SQL_EXCEPTION : Error during executing SQL Update. Task ID [String] Step Name [String] SQL State [String] SQL Error Code [String]

Explanation Exception occurred while executing the query

Recommended Action Check the SQl statement and databse availability. Copy the error message exactly as it appears on the console or in the system log, and contact your Database Administrator

Error Message
MIVR-STEPS_EMAIL- 3 -EMAIL_ATTACH_NO_DOC_EXISTS : Attached document for this local variable does not exist. Local Variable [String] Task id [Long]

Explanation The attached document for this local variable does not exist. It must exist in order to be sent.

Recommended Action Verify and update the configuration

Error Message
MIVR-STEPS_EMAIL- 3 -EMAIL_NOT_INITIATED : The step uses an eMail Variable Name that has not been initiated.. Local Variable [String] Task id [Long]

Explanation The step uses an eMail Variable Name that has not been initiated. The Create eMail step must initiate the email.

Recommended Action Verify and update the configuration

Error Message
MIVR-STEPS_EMAIL- 2 -EMAIL_STEP_GENERAL_EX : General exception from processing. Exception [String] Step [String] Task id [Long]

Explanation General exception in executing this step

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-STEPS_EMAIL- 3 -EMAIL_ATTACH_NOT_STR_OR_DOC : Attached document for this local variable is neither of type "java.lang.String" or "com.cisco.doc.Document.". Local Variable [String] Task id [Long]

Explanation The attached document for this local variable is not the proper type.

Recommended Action Verify and update the configuration

Error Message
MIVR-STEPS_EMAIL- 2 -EMAIL_PREPROCESS_EX : Exception from preprocessing expressions. Exception [String] Step [String]

Explanation Exception from preprocessing expressions on this step's customizer

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-STEPS_EMAIL- 3 -EMAIL_NOT_CONFIGURED : eMail Subsystem has not been configured. Step [String]

Explanation The eMail subsystem was not configured (needs Mail Server), therefore this workflow cannot be run

Recommended Action Verify and update the configuration

Error Message
MIVR-STEP_SESSION_MGMT- 6 -SESSION_HANDLED : The session was handled.

Explanation The session was handled

Recommended Action No actions needed

Error Message
MIVR-STEPS_GRAMMAR- 3 -EXPECT_RECOGNIZABLE_VARIABLE : Expect Playable variable. Exception [String] Step [String] Task id [Long]

Explanation Exception from preprocessing expressions on this step's customizer

Recommended Action No actions needed

Error Message
MIVR-STEPS_GRAMMAR- 3 -GRAMMAR_STEP_EXCEPTION : Exception. Exception [String] Step [String] Task id [Long]

Explanation Exception from a grammar step

Recommended Action No actions needed

Error Message
MIVR-STEPS_JAVA- 3 -EXECUTE_ANNOTATION_STEP : Expect comments. Exception [String] Step [String] Task id [Long]

Explanation Exception from preprocessing expressions on this step's customizer

Recommended Action No actions needed

Error Message
MIVR-STEPS_PROMPT- 3 -EXPECT_PLAYABLE_VARIABLE : Expect Playable variable. Exception [String] Step [String] Task id [Long]

Explanation Exception from preprocessing expressions on this step's customizer

Recommended Action No actions needed

Error Message
MIVR-STEPS_SESSION- 3 -SESSION_STEP_RUNNING : Session Step Running. Exception [String] Step [String] Task id [Long]

Explanation Exception from preprocessing expressions on this step's customizer

Recommended Action No actions needed

Error Message
MIVR-STEPS_USER- 2 -DATASTORE_IO_ACCESS_EX : General datastore search exception. Task id [Long] Step [String] Exception [String]

Explanation General datastore search exception in executing this step

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-STEPS_USER- 4 -SPOKEN_NAME_UPLOAD_ERROR : Unable to upload spoken name. Exception [String]

Explanation Unable to upload the spoken name to the Repository

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-STEPS_USER- 4 -USERS_NOT_UNIQUE : The Userbase has been incorrectly configured. Task id [Long] Step [String] User [String]

Explanation The directory lists several Users having the same Agent Extension, therefore the first User on the list is returned.

Recommended Action Verify and update the configuration

Error Message
MIVR-STEPS_USER- 3 -AUTHENTICATE_ERROR : Authenticating error. Exception [String]

Explanation A problem occur when authenticating password

Recommended Action No actions needed

Error Message
MIVR-USER_MGR- 4 -NAME_GRAMMAR_GENERATION_NOT_ALLOWED : Name Grammar Generation not allowed unless in MIVR or MADM.

Explanation Name Grammar Generation not allowed unless in MIVR or MADM

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-USER_MGR- 1 -MGR_PARTIAL_SERVICE : User Manager in partial service.

Explanation The User Manager is in partial service

Recommended Action Investigate as required

Error Message
MIVR-USER_MGR- 4 -DB_CORRUPTION_ILLEGAL_VALUE : Possible Call Manager database corruption due to an illegal value. Table name [String] Column name [String] Column value [String]

Explanation Possible Call Manager database corruption due to an illegal value

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-USER_MGR- 3 -NAME_GRAMMAR_SCHEDULE_UPDATE_FAILED : Name Grammar schedule update failed. Exception [String]

Explanation The User Manager failed to update automatic Name Grammar Generator schedule; Name To User may not function

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-USER_MGR- 3 -UNEXPECTED_EXCEPTION : Unexpected exception thrown. Exception [String]

Explanation Unexpected exception thrown

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-USER_MGR- 4 -FILE_IO_ERROR : Error occurred during file I/O. Exception [String]

Explanation Error occurred during file I/O

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-USER_MGR- 4 -DB_CORRUPTION_EMPTY_VALUE : Possible Call Manager database corruption due to empty required value. Table name [String] Column name [String] Row [Int]

Explanation Possible Call Manager database corruption due to empty required value

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-USER_MGR- 4 -NAME_GRAMMAR_UPDATE_STATUS_FAILED : Name Grammar Generation status update failed. Exception [String]

Explanation The User Manager failed to update Name Grammar Generation Status. The status information may be incorrect.

Recommended Action No actions needed

Error Message
MIVR-USER_MGR- 6 -MGR_INITIALIZING : User Manager initializing.

Explanation The User Manager is initializing

Recommended Action No actions needed

Error Message
MIVR-USER_MGR- 5 -MGR_SHUTTING_DOWN : User Manager shutting down.

Explanation The User Manager is in the process of shutting down

Recommended Action No actions needed

Error Message
MIVR-USER_MGR- 2 -MGR_OUT_OF_SERVICE : User Manager in out of service.

Explanation The User Manager is out of service

Recommended Action Restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-USER_MGR- 3 -INIT_FAILED : User Manager failed to initialize. Exception [String]

Explanation An exception has occurred during the initialization of the User Manager

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-USER_MGR- 3 -NAME_GRAMMAR_UPDATE_CONFIG_FAILED : Name Grammar configuration update failed. Exception [String]

Explanation The User Manager failed to update Name Grammar Generation Configuration; Name To User may not function

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-USER_MGR- 1 -CANNOT_CREATE_SYSTEM_USER : Caller cannot create a System User. Exception [String]

Explanation An unauthorized class has attempted to create an instance of a System User.

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-USER_MGR- 4 -AUDIO_FORMAT_ERROR : Wrong audio format in stream. Exception [String]

Explanation Wrong audio format in stream

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-USER_MGR- 3 -NAME_GRAMMAR_GENERATION_FAILED : Name Grammar generation failed. Exception [String]

Explanation The User Manager was unable to generate the Name Grammars; Name To User may not function

Recommended Action Verify and update the configuration, restart server and if problem persist contact Cisco technical assistance center

Error Message
MIVR-USER_MGR- 6 -MGR_IN_SERVICE : User Manager in service.

Explanation The User Manager is in service

Recommended Action No actions needed

Error Message
MIVR-USER_MGR- 4 -STREAM_IO_ERROR : Error occurred during stream I/O. Exception [String]

Explanation Error occurred during stream I/O

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-USER_MGR- 5 -MGR_SHUTDOWN : User Manager in shutdown.

Explanation The User Manager has completed its shutdown

Recommended Action No actions needed

Error Message
MIVR-USER_MGR- 4 -DB_CORRUPTION_BAD_VALUE_FORMAT : Possible Call Manager database corruption due to bad value format. Table name [String] Column name [String] Column value [String] Exception [String]

Explanation Possible Call Manager database corruption due to bad value format

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-USER_MGR- 4 -DB_CORRUPTION_MISSING_COLUMN : Possible Call Manager database corruption due to missing column. Table name [String] Column name [String] Exception [String]

Explanation Possible Call Manager database corruption due to missing column

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-USER_MGR- 3 -CONFIG_LISTENER_INIT_FAILED : Unable to register config listener. Exception [String]

Explanation Unable to register config listener for UserGrammarConfig; Name To User may not function

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-USER_MGR- 3 -NO_SYSTEM_PAYLOAD : System payload type could not be determined.

Explanation System payload type could not be determined

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
MIVR-USER_MGR- 5 -CLUSTER_ID_CHANGED : Cluster ID has changed.. Previous Cluster ID [String] Current Cluster ID [String]

Explanation Cluster ID has changed. This is a rare but normal condition. It can occur after a restore operation following a re-install. Users whose cluster specific data was modified after the re-install but before the restore will lose those modifications.

Recommended Action No actions needed

Error Message
MIVR-USER_MGR- 4 -DB_CORRUPTION_NON_UNIQUE_KEY : Possible Call Manager database corruption due to non unique key. Table name [String] Column name [String] Key value [String]

Explanation Possible Call Manager database corruption due to non unique key

Recommended Action If problem persist contact Cisco Technical Assistance Center

Error Message
Phone- 6 -DeviceImageDownloadStart : Device has begun downloading the firmware load. DeviceName [String] IPAddress [String] Active [String] RequestedLoadId [String]

Explanation Cisco IP Phone has started downloading its firware load (image)

Recommended Action Informational purposes only; no action is required

Error Message
Phone- 6 -DeviceImageDownloadSuccess : Device has successfully downloaded the firmware load. DeviceName [String] IPAddress [String] Method [Enum] Active [String] Inactive [String] Server from which the firmware was downloaded [String]

Explanation Cisco IP Phone has successfully downloaded its image.

Recommended Action No action is required.

Method-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 TFTP
2 HTTP
3 PPID
Error Message
Phone- 4 -DeviceImageDownloadFailure : Device firmware download has failed. DeviceName [String] IPAddress [String] Active [String] Inactive [String] FailedLoadId [String] Method [Enum] FailureReason [Enum] Server [String]

Explanation Cisco IP phone failed to download its firmware load (image) for the reason defined in this alarm

Recommended Action Verify that the IP address or hostname of the image download server (either the Load server or the TFTP server) is correct. If you're using a hostname, verify that the Domain Name Server (DNS) is accessible from the phone and can resolve the hostname. Verify that the TFTP service is activated and running on the Load server or TFTP server (the server you are using to serve firmware load files). Verify that the Load server or TFTP server is accessible from the phone. Also, refer to the reason code descriptions for recommended actions.

Method-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 TFTP
2 HTTP
3 PPID
FailureReason-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 A TFTP server error occurred - examine the TFTP log to determine whether other errors occurred at the same time the device was attempting to download its firmware and correct any TFTP errors that may have occurred. Also, investigate the load on the TFTP server to ensure that device download requests are being processed; check network connectivity to the TFTP server.
2 Specified firmware load ID is not found on the TFTP server. Check that file name is correct, or load (image) file exist on TFTP server.
3 An internal phone error occurred during the download attempt; reset the phone to correct the issue
4 The Load server or TFTP server could not process the phone's firmware load request. It's possible that congestion is causing a delay in TFTP response. To allow the phone to attempt the download again, wait a few minutes then reset the phone. The phone will attempt to download its firmware load again. If resetting the phone does not solve the issue, restart the Load server or TFTP server (whichever server provides firmware loads).
5 An encryption error occurred on the phone while trying to load the new firmware load (image); reset the phone to correct the issue
6 The downloaded firmware load (image) is not encrypted. Verify that correct load (image) name is provided to the phone and that the server that provides firmware loads has that encrypted load (image) file
7 The downloaded firmware load (image) cannot be decrypted using the decryption key on the phone (resulting in an encryption key mismatch). If you have provided the image encryption key, try re-encrypting the image with the key that matches the key already on the phone, then attempt the download again. Otherwise, collect the phone logs from the time of this alarm (review the steps in the Administration Guide for the appropriate phone model to learn how to access the phone logs) and contact the Cisco Technical Assistance Center (TAC).
8 There is a problem with the encryption of the downloaded firmware load (image). Collect pertinent details such as the device's MAC address, device type, the firmware load ID, and phone logs from the time of this alarm (review the steps in the Administration Guide for the appropriate phone model to learn how to access the phone logs), and contact the Cisco Technical Assistance Center (TAC).
9 The phone did not receive a load server name or IP address and as a result, does not have the server information needed to download a firmware load. Check the Device Configuration page in Cisco Unified CM Administration to ensure that the IP address of the Load server or TFTP server is accurately configured. If the information is inaccurate or not present, supply the correct information and restart the phone. If the information is accurate, restart the phone. If this alarm recurs, contact the Cisco Technical Assistance Center (TAC).
10 The phone attempted an action that is not allowed by the Load server or TFTP server; reset the phone to attempt to clear the condition
13 The device has exceeded the internally-configured time allowed for a response from the Load server or TFTP server when requesting the firmware load file. It's possible that congestion is causing a delay in TFTP response. To allow the phone to attempt the download again, wait a few minutes then reset the phone. The phone will attempt to download the file again. If resetting the phone does not solve the issue, restart the Load server or TFTP server (whichever server provides the firmware load files).
14 The data that the phone received from the Load server or TFTP server was not intact; not enough information was received. Restart the phone to begin the download process again.
15 The data that the phone received from the Load server or TFTP server was not intact; too much information was received. Restart the phone to begin the download process again.
16 The phone cannot connect to the network; check for network connectivity to the image firmware load server or the TFTP server and correct any broken connection. Restart the phone to attempt connection again unless the restart occurs automatically.
17 The DNS server name that the phone is attempting to connect to could not be resolved. Examine the DNS server name(s) in the phone settings to verify that the information is accurate and if not, update the name on the phone. Restart the phone unless the restart occurs automatically.
18 No DNS server - Configure a DNS server IP address on the phone settings. Restart the phone unless the restart occurs automatically.
19 Connection to the Load server or TFTP server has timed out - The phone attempted to connect to the Load server or TFTP server but could not connect successfully. If you are using the TFTP server to serve firmware loads, check the TFTP server IP address as configured in the settings on the phone; make sure the IP address is accurate. If it is not, correct the IP address and press Apply; the phone should restart automatically. If you are using a Load server to serve firmware loads, check the IP address or hostname on the Phone Configuration page in Cisco Unified CM Administration for the phone identified in this alarm, to ensure that the information is accurate. If it is not, update the IP address or hostname and restart the phone. Also, verify that network connectivity exists between the phone and the Load server or TFTP server. Restart the phone to attempt connection again unless the restart occurs automatically.
20 Download was cancelled - A previous download request was superceded by a new download request. The original download was cancelled so that the new download could continue. No action is required.
Error Message
Phone- 6 -DeviceApplyConfigResult : Indicates the result of an Apply Config action in Unified CM Administration. DeviceName [String] IPAddress [String] UnifiedCM_Result [Enum] Phone_Result [Enum] Reason [Enum]

Explanation Cisco IP Phone has applied its config

Recommended Action No action is required.

UnifiedCM_Result-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 no change - the new phone configuration changes do not impact Unified CM.
2 Configuration changes applied - The Unified CM Administration applied the configuration changes dynamically without requiring phone to re-register.
3 Re-registration - The Unified CM Administration applied the configuration changes and required the phone to re-register to make them effective.
Phone_Result-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Configuration changes applied - The phone applied the configuration changes dynamically without a reset or restart.
2 Reset delayed - Phone will set the inactive partition as active partition, then reset, and come up from the new active partition.
3 Restart now - The phone will restart immediately.
4 Restart delayed - The phone will restart, but restart is delayed for reason as specified in reason parameter.
5 Config pending- The phone will delay applying the configuration changes because phone is downloading a firmware image.
6 TFTP Error- While downloading the configuration file, phone encountered tftp error for reason as specified in reason parameter .
Reason-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Configuration file changed- Config file has changed since last download of configuration file.
2 Download in progress- Download of firmware image is going on.
3 Call is active- A call is active on the phone.
4 Re-registration delayed - Because call is active, re-registration of the phone is delayed. Registration will resume when phone is idle.
5 Reset delayed - Because call is active, reset of phone is delayed. Reset will continue when phone is idle.
6 A TFTP server error occurred - examine the TFTP log to determine whether other errors occurred at the same time the device was attempting to download its configuration file and correct any TFTP errors that may have occurred. Also, investigate the configuration file on the TFTP server to ensure that configuration file requests are being processed; check network connectivity to the TFTP server.
7 Specified configuration file is not found on the TFTP server. Check that file name is correct and file exist on TFTP server.
8 The phone attempted an action that is not allowed by the Load server or TFTP server; reset the phone to attempt to clear the condition
9 An internal phone error occurred during the download attempt of configuration file; reset the phone to correct the issue
10 Connection to the Load server or TFTP server has timed out - The phone attempted to connect to the Load server or TFTP server but could not connect successfully. If you are using the TFTP server to serve configuration file, check the TFTP server IP address as configured in the settings on the phone; make sure the IP address is accurate. If it is not, correct the IP address and press Apply; the phone should restart automatically. If you are using a Load server to serve configuration file, check the IP address or hostname on the Phone Configuration page in Cisco Unified CM Administration for the phone identified in this alarm, to ensure that the information is accurate. If it is not, update the IP address or hostname and restart the phone. Also, verify that network connectivity exists between the phone and the Load server or TFTP server. Restart the phone to attempt connection again unless the restart occurs automatically.
11 Specified CTL file is not found on the TFTP server. Check that file name is correct and file exist on TFTP server.
12 Authentication for CTL file failed; reset the phone to correct the issue
13 The Load server or TFTP server could not process the phone's configuration file download request. It's possible that congestion is causing a delay in TFTP response. To allow the phone to attempt the download again, wait a few minutes then reset the phone. The phone will attempt to download its configuration file again. If resetting the phone does not solve the issue, restart the Load server or TFTP server (whichever server provides configuration file).
14 An encryption error occurred on the phone while trying to load the new configuration file; reset the phone to correct the issue
15 The downloaded configuration file is not encrypted. Verify that security or authentication mode of phone is same as what is configured in Unified CM for that phone and that the server that provides configuration file has that encrypted file
16 The downloaded configuration file cannot be decrypted using the decryption key on the phone (resulting in an encryption key mismatch). If you have provided the configuration file encryption key, try re-encrypting the configuration file with the key that matches the key already on the phone, then attempt the download again. Otherwise, collect the phone logs from the time of this alarm (review the steps in the Administration Guide for the appropriate phone model to learn how to access the phone logs) and contact the Cisco Technical Assistance Center (TAC).
17 There is a problem with the encryption of the downloaded configuration file. Collect pertinent details such as the device's MAC address, device type, the configuration file, and phone logs from the time of this alarm (review the steps in the Administration Guide for the appropriate phone model to learn how to access the phone logs), and contact the Cisco Technical Assistance Center (TAC).
18 The phone did not receive a load server name or IP address and as a result, does not have the server information needed to download a configuration file. Check the Device Configuration page in Cisco Unified CM Administration to ensure that the IP address of the Load server or TFTP server is accurately configured. If the information is inaccurate or not present, supply the correct information and restart the phone. If the information is accurate, restart the phone. If this alarm recurs, contact the Cisco Technical Assistance Center (TAC).
19 The DNS server name that the phone is attempting to connect to could not be resolved. Examine the DNS server name(s) in the phone settings to verify that the information is accurate and if not, update the name on the phone. Restart the phone unless the restart occurs automatically.
20 An internal phone error occurred in processing the configuration file; restart the phone to correct the issue
21 Configuration file Re-TFTP - Phone need to download the configuration file again.
22 Certification mismatch for configuration file - Phone detected certification mismatch for downloaded configuration file.
23 Firmware load update required - Phone need to download new firmware image.
Error Message
Phone- 4 -DeviceConfigFailure : Device was unable to install the new configuration file. DeviceName [String] IPAddress [String] Current version stamp of the phone's configuration file [String] Version stamp of the new configuration file that has been requested [String] Failure reason [Enum]

Explanation Cisco IP Phone is unable to install the latest configuration file. After a configuration change has occurred in Cisco Unified CM Administration, the phone successfully downloads its new configuration file but due to some error, it cannot install it.

Recommended Action Refer to the reason code descriptions for recommended actions

Failure reason-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Version mismatch - The version of the configuration file that was downloaded does not match the version stamp of the file that was requested by Unified CM. The phone failed to load the file due to the version stamp mismatch. This sometimes occurs due to a misstep during a phone or Unified CM upgrade. Verify that database replication is functioning by going to the Cisco Unified Reporting web page, generating a Unified CM Database Status report, and verifying that "all servers have a good replication status". You can also go to Real-Time Reporting Tool (RTMT) and check the Replication Status in the Database Summary page. If status shows 2, then replication is working. If replication is not working, restart the TFTP and Cisco CallManager services.
2 TFTP server unavailable - Either the IP address of the TFTP server configured in the Administrator Settings is incorrect or the TFTP server is not running. Verify that phone settings have the correct TFTP IP address and that the TFTP server is running.
3 File not found - The phone configuration file requested by the phone does not exist in the TFTP server. Verify that IP address provided in the Administration Setting for TFTP server is correct. Verify that the phone is configured in Unified CM Administration and the MAC address shown in Unified CM Administration matches the actual MAC address of the phone. If the phone is not configured in Unified CM Administration, configure the phone in Unified CM Administration and manually restart the phone from the administrator settings on the device itself.
4 Read error - The phone is unable to read the configuration file successfully. Collect the phone logs from the time of this alarm (review the steps in the Administration Guide for the appropriate phone model to learn how to access the phone logs) and contact the Cisco Technical Assistance Center (TAC).
Error Message
Phone- 4 -PowerSavePlusFailure : The device could not enter Power Save Plus. DeviceName [String] DeviceIPv4Address [String] Reason [Enum]

Explanation The device indicated in this alarm could not enter Power Save Plus mode, even though the feature is enabled for this device. This can occur because of configuration errors such as a missing or incorrect EneergyWise domain or secret, a power supply to the device that is incompatible with the Power Save Plus feature, or because the switch is not EnergyWise enabled or has refused to allow the device to enter Power Save Plus mode

Recommended Action Actions to correct this condition vary according to the reason code specified in this alarm. Refer to the reason code definitions in this alarm for recommended actions

Reason-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 NoEnergyWiseDomain - The EnergyWise domain has not been configured on this device. An EnergyWise domain is always required for the Power Save Plus feature even when the Allow EnergyWise Overrides check box is not checked. Specify an EnergyWise domain on the Device Configuration window in Unified CM Administration, in the EnergyWise Domain field
2 NoEnergyWiseSecret - The EnergyWise secret (password) has not been configured on this device. An EnergyWise secret is always required for the Power Save Plus feature even when the Allow EnergyWise Overrides check box is not checked. Specify an EnergyWise secret on the Device Configuration window in Unified CM Administration, in the EnergyWise Secret field
3 NoPowerOverEthernet - The device is not powered by standard Power-over-Ethernet (PoE). This can occur if the device is receiving wall power through an AC adapter plugged in to the phone or when the device has been plugged into a non-PoE hub or router or into a mid-span device which is used to add PoE to switches that do not natively support PoE. If the device is intentionally connected to a power source other than PoE, the Power Save Plus feature should be disabled on this device. PoE is required for the Power Save Plus feature
4 NoEnergyWiseSwitch - The device is not attached to a switch that has EnergyWise enabled. This can occur if the device is attached to a Cisco switch but EnergyWise has not been enabled or if the EnergyWise-enabled switch is running a Cisco IOS version that is incompatible with the Power Save Plus feature. Verify that the device is attached to a Cisco switch that has EnergyWise enabled and that the version of the IOS software that the switch is running includes support for the EnergyWise/Power Save Plus feature
5 PSPRejected - The EnergyWise-enabled switch refused to allow the device to enter Power Save Plus. Verify that the version of the IOS software that the switch is running includes support for the EnergyWise/Power Save Plus feature. Examine the switch and the reject message (negative acknowledgement) for any information relating to the reason for the refusal
Error Message
Phone- 6 -LastOutOfServiceInformation : Information related to the last out-of-service event . Device Name [String] Device IPv4 Address [String] IPv4 default gateway [String] Device IPv6 Address [String] IPv6 default gateway [String] Model Number [String] Neighbor IPv4 Address [String] Neighbor IPv6 Address [String] Neighbor Device ID [String] Neighbor Port ID [String] DHCPv4 Status [Enum] DHCPv6 Status [Enum] TFTP Configuration Status [Enum] DNS Status on Unified CM 1 [Enum] DNS Status on Unified CM 2 [Enum] DNS Status on Unified CM 3 [Enum] Voice VLAN [String] CUCM IP Address [String] Local Port [String] Time Stamp [String] Reason For Out Of Service [Enum] Last Protocol Event Sent [String] Last Protocol Event Received [String]

Explanation The device has lost communication with Unified CM, due to a reason such as a network connectivity issue, Unified CM outage, configuration error, and in some cases, a normal unregistration event. A device can go out-of-service for many reasons, both intentional such as manually resetting the device after a configuration change, and unintentional such as loss of network connectivity. Other causes for this alarm could include a device being registered to a secondary node and then the primary node coming online, which causes the device to re-home to the primary Unified CM node. Other error conditions include lack of a KeepAlive being returned from the Unified CM node to which this device was registered, and so on.

Recommended Action Actions to take vary depending on the reason specified in this alarm for why the device went out of service. If the device being out of service is expected (normal occurrence), such as during a manual devie reset, no action is required. Reason codes 18-23 are all normal reason codes. Other reason codes should be investigated to determine why Unified CM is not running or whether a network problem or configuration error exists. In the case of a network connectivity problem or loss of KeepAlives, use network diagnostic tools, the Real-Time Monitoring Tool, and the Cisco Unified CM Reporting tool to evaluate and correct any reported network or Unified CM system errors. In the case of a device re-homing to the primary Unified CM node, watch for a successful registration of the device on the primary node. Also, refer to the reason code descriptions for recommended actions

DHCPv4 Status-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Successful - DHCPv4 configuration completed without error
2 RequestTimedOut - The DHCPv4 request timed out. Check for and correct errors on the DHCP server
3 DHCPdisabled - DHCPv4 was disabled at the time the device went out-of-service
DHCPv6 Status-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Successful - DHCPv6 configuration completed without error
2 RequestTimedOut - The DHCPv6 request timed out. Check for and correct errors on the DHCP server
3 DHCPdisabled - DHCPv6 was disabled at the time the device went out-of-service
TFTP Configuration Status-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 TFTPDownloadSuccess - TFTP download of the configuration file completed without error
2 TFTPtimedOut - Connection to the TFTP server has timed out - The device attempted to connect to the TFTP server but could not connect successfully. Check the TFTP server IP address as configured in the settings on the device; make sure the IP address is accurate. If it is not, correct the IP address and press Apply; the device should restart automatically. Also, verify that network connectivity exists between the device and the TFTP server. Restart the device to attempt connection again unless the restart occurs automatically
3 NoServerInfo - The device did not receive a TFTP IP address or the DNS name was not resolved and as a result, does not have the server information needed to download a configuration file. Check that DHCP option 150 has been configured properly. If the information is inaccurate or not present, supply the correct information and restart the device. If the information is accurate, restart the device. If this alarm recurs, contact the Cisco Technical Assistance Center (TAC)
DNS Status on Unified CM 1-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 DNSsuccessful - DNS resolution completed without error
2 DNSrequestTimedOut - The DNS request timed out. Check the DNS server and make sure that it is functioning properly
3 DNShostNameNotFound - The DNS server was unable to resolve the host name specified for the primary Cisco Unified CM
4 DNSresolutionNotNeeded - The primary Cisco Unified CM was specified by an IP address so no DNS resolution was needed
DNS Status on Unified CM 2-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 DNSsuccessful - DNS resolution completed without error
2 DNSrequestTimedOut - The DNS request timed out. Check the DNS server and make sure that it is functioning properly
3 DNShostNameNotFound - The DNS server was unable to resolve the host name specified for the secondary Cisco Unified CM
4 DNSresolutionNotNeeded - The secondary Cisco Unified CM was specified by an IP address so no DNS resolution was needed
DNS Status on Unified CM 3-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 DNSsuccessful - DNS resolution completed without error
2 DNSrequestTimedOut - The DNS request timed out. Check the DNS server and make sure that it is functioning properly
3 DNShostNameNotFound - The DNS server was unable to resolve the host name specified for the tertiary Cisco Unified CM
4 DNSresolutionNotNeeded - The tertiary Cisco Unified CM was specified by an IP address so no DNS resolution was needed
Reason For Out Of Service-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
10 TCPtimedOut - The TCP connection to the Cisco Unified Communication Manager experienced a timeout error
12 TCPucmResetConnection - The Cisco Unified Communication Manager reset the TCP connection
13 TCPucmAbortedConnection - The Cisco Unified Communication Manager aborted the TCP connection
14 TCPucmClosedConnection - The Cisco Unified Communication Manager closed the TCP connection
15 SCCPKeepAliveFailure - The device closed the connection due to a SCCP KeepAlive failure
16 TCPdeviceLostIPAddress - The connection closed due to the IP address being lost. This may be due to the DHCP Lease expiring or the detection of IP address duplication. Check that the DHCP Server is online and that no duplication has been reported by the DHCP Server
17 TCPDeviceRegsistrationTimedOut - The device closed the TCP connection due to a registration timeout
18 TCPclosedConnectHighPriorityUcm - The device closed the TCP connection in order to reconnect to a higher priority Cisco Unified CM
20 TCPclosedUserInitiatedReset - The device closed the TCP connection due to a user initiated reset
22 TCPclosedUcmInitiatedReset - The device closed the TCP connection due to a reset command from the Cisco Unified CM
23 TCPclosedUcmInitiatedRestart - The device closed the TCP connection due to a restart command from the Cisco Unified CM
24 TCPClosedRegistrationReject - The device closed the TCP connection due to receiving a registration rejection from the Cisco Unified CM
25 RegistrationSuccessful - The device has initialized and is unaware of any previous connection to the Cisco Unified CM
26 TCPclosedVlanChange - The device closed the TCP connection due to reconfiguration of IP on a new Voice VLAN
27 TCPclosedPowerSavePlus - The device closed the TCP connection in order to enter Power Save Plus mode
100 ConfigVersionMismatch - The device detected a version stamp mismatch during registration Cisco Unified CM
104 TCPclosedApplyConfig - The device closed the TCP connection to restart triggered internally by the device to apply the configuration changes
105 TCPclosedDeviceRestart - The device closed the TCP connection due to a restart triggered internally by the device because device failed to download the configuration or dial plan file
106 TCPsecureConnectionFailed - The device failed to setup a secure TCP connection with Cisco Unified CM
107 TCPclosedDeviceReset - The device closed the TCP connection to set the inactive partition as active partition, then reset, and come up from the new active partition
108 VpnConnectionLost - The device could not register to Unified CM because VPN connectivity was lost
200 ClientApplicationClosed - The device was unregistered because the client application was closed
201 OsInStandbyMode - The device was unregistered because the OS was put in standby mode
202 OsInHibernateMode - The device was unregistered because the OS was put in hibernate mode
203 OsInShutdownMode - The device was unregistered because the OS was shut down
204 ClientApplicationAbort - The device was unregistered because the client application crashed
205 DeviceUnregNoCleanupTime - The device was unregistered in the previous session because the system did not allow sufficient time for cleanup
206 DeviceUnregOnSwitchingToDeskphone - The device was unregistered because the client requested to switch from softphone to deskphone control
207 DeviceUnregOnSwitchingToSoftphone - The device is being registered because the client requested to switch from deskphone control to softphone
208 DeviceUnregOnNetworkChanged - The device is being unregistered because the client detected a change of network
209 DeviceUnregExceededRegCount - The device is being unregistered because the device has exceeded the maximum number of concurrent registrations
210 DeviceUnregExceededLoginCount - The device is being unregistered because the client has exceeded the maximum number of concurrent logons
Error Message
Phone- 6 -DeviceTLInfo : Trust List Files are updated or installed successfully. DeviceName [String] IPv4Address [String] IPv6Address [String] CTL_Signature [String] CTL_TFTP_Server [String] ITL_Signature [String] ITL_TFTP_Server [String]

Explanation Trust List Files(CTL/ITL) are updated or installed successfully

Recommended Action Informational purposes only; no action is required

Error Message
RecordingClient- 1 -RECORD1001 : The installation may have failed or registry become corrupted.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Reinstall CAD.

Error Message
RecordingClient- 1 -RECORD1002 : The installation may have failed or registry become corrupted.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Reinstall CAD.

Error Message
RecordingClient- 1 -RECORD1004 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (CPU and memory). Make sure the Record service properties are correct.

Error Message
RecordingClient- 1 -RECORD1005 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (CPU and memory). Make sure the Record service properties are correct.

Error Message
RecordingClient- 1 -RECORD1006 : The initialization of the Windows NT service was unsuccessful.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
RecordingClient- 1 -RECORD1007 : The initialization of the Windows NT service was unsuccessful.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
RecordingClient- 1 -RECORD1008 : The initialization of the Windows NT service was unsuccessful.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
RecordingClient- 1 -RECORD1009 : The initialization of the Windows NT service was unsuccessful.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check network settings.

Error Message
RecordingClient- 1 -RECORD1010 : The audio directory not found and could not be created. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the security settings.

Error Message
RecordingClient- 1 -RECORD1013 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action check network settings.

Error Message
RecordingClient- 1 -RECORD1014 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check network settings.

Error Message
RecordingClient- 1 -RECORD1015 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check network settings.

Error Message
RecordingClient- 1 -RECORD1016 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check network settings.

Error Message
RecordingClient- 1 -RECORD1017 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check network settings.

Error Message
RecordingClient- 1 -RECORD1018 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify server is properly installed.

Error Message
RecordingClient- 3 -RECORD2006 : An error occurred while synchronizing agents.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (CPU, memory and disk).

Error Message
RecordingClient- 3 -RECORD2007 : An error occurred while synchronizing agents.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (disk).

Error Message
RecordingClient- 3 -RECORD2008 : The maximum disk space that can be used by recordings has be reached.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resources.

Error Message
RecordingClient- 3 -RECORD2009 : The maximum disk space that can be used by recordings has be reached.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resources.

Error Message
RecordingClient- 3 -RECORD2010 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 3 -RECORD2011 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 3 -RECORD2012 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 3 -RECORD2013 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 3 -RECORD2014 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 3 -RECORD2015 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 3 -RECORD2016 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 3 -RECORD2017 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 3 -RECORD2018 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 3 -RECORD2019 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 3 -RECORD2020 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 3 -RECORD2021 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 3 -RECORD2022 : Playback stopped, most likely because the cache was empty. . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify that disk I/O is not overloaded.

Error Message
RecordingClient- 4 -RECORD3000 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4003 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4004 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4005 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4006 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4007 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4008 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4009 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4010 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4011 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4012 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4013 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4014 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4015 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4016 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4017 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4018 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4019 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4020 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4021 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4022 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RecordingClient- 4 -RECORD4023 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 1 -RECORD1001 : The installation may have failed or registry become corrupted.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Reinstall CAD.

Error Message
RPServer- 1 -RECORD1002 : The installation may have failed or registry become corrupted.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Reinstall CAD.

Error Message
RPServer- 1 -RECORD1004 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (CPU and memory). Make sure the Record service properties are correct.

Error Message
RPServer- 1 -RECORD1005 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (CPU and memory). Make sure the Record service properties are correct.

Error Message
RPServer- 1 -RECORD1006 : The initialization of the Windows NT service was unsuccessful.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
RPServer- 1 -RECORD1007 : The initialization of the Linux service was unsuccessful.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 1 -RECORD1008 : The initialization of the Windows NT service was unsuccessful.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
RPServer- 1 -RECORD1009 : The initialization of the Windows NT service was unsuccessful.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check network settings.

Error Message
RPServer- 1 -RECORD1010 : The audio directory not found and could not be created. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the security settings.

Error Message
RPServer- 1 -RECORD1013 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action check network settings.

Error Message
RPServer- 1 -RECORD1014 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check network settings.

Error Message
RPServer- 1 -RECORD1015 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check network settings.

Error Message
RPServer- 1 -RECORD1016 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check network settings.

Error Message
RPServer- 1 -RECORD1017 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check network settings.

Error Message
RPServer- 1 -RECORD1018 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify server is properly installed.

Error Message
RPServer- 3 -RECORD2006 : An error occurred while synchronizing agents.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (CPU, memory and disk).

Error Message
RPServer- 3 -RECORD2007 : An error occurred while synchronizing agents.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resource availability (disk).

Error Message
RPServer- 3 -RECORD2008 : The maximum disk space that can be used by recordings has be reached.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resources.

Error Message
RPServer- 3 -RECORD2009 : The maximum disk space that can be used by recordings has be reached.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check system resources.

Error Message
RPServer- 3 -RECORD2010 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 3 -RECORD2011 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 3 -RECORD2012 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 3 -RECORD2013 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 3 -RECORD2014 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 3 -RECORD2015 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 3 -RECORD2016 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 3 -RECORD2017 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 3 -RECORD2018 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 3 -RECORD2019 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 3 -RECORD2020 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 3 -RECORD2021 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 3 -RECORD2022 : Playback stopped, most likely because the cache was empty. . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify that disk I/O is not overloaded.

Error Message
RPServer- 4 -RECORD3000 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4003 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4004 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4005 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4006 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4007 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4008 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4009 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4010 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4011 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4012 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4013 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4014 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4015 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4016 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4017 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4018 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4019 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4020 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4021 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4022 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RPServer- 4 -RECORD4023 : . Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
RTMTAlarmCatalog- 3 -RTMT_ALERT : RTMT Alert. Name [String] Detail [String]

Explanation A Real-Time Monitoring Tool (RTMT) process in the AMC service uses the alarm mechanism to facilitate delivery of RTMT alerts in RTMT AlertCentral or via email.

Recommended Action Check AlertCentral in RTMT or any alerts that you have received via email to determine what issue has occurred and learn the recommended actions to resolve it. In AlertCentral, right-click the alert to open the alert information.

Error Message
RTMTAlarmCatalog- 3 -AlertEmailNotifyFailure : Alert Email Notification Failure.. Reason [String]

Explanation Alert notification mechanism using e-mails has failed.

Recommended Action Email notification of alerts failed due to a mis-configured SMTP Settings/SMTP server down. Check SMTP Server configuration and Examine the AMC service log files to determine the exact reason for failure.

Error Message
ServiceManagerAlarmCatalog- 5 -ServiceActivated : Service Activated.. Service Name [String]

Explanation This service is now activated.

Recommended Action No action is required.

Error Message
ServiceManagerAlarmCatalog- 5 -ServiceDeactivated : Service Deactivated.. Service Name [String]

Explanation This service is now deactivated.

Recommended Action No action is required.

Error Message
ServiceManagerAlarmCatalog- 1 -ServiceActivationFailed : Failed to activate a service.. Service Name [String] Reason [String] Error String [String]

Explanation Failed to activate this service.

Recommended Action Activate the service again

Error Message
ServiceManagerAlarmCatalog- 1 -ServiceDeactivationFailed : Failed to deactivate a service.. Service Name [String] Reason [String] Error String [String]

Explanation Failed to deactivate this service.

Recommended Action Deactivate the service again

Error Message
ServiceManagerAlarmCatalog- 2 -ServiceFailed : Service terminated.. Service Name [String] Process ID [Int] Reason [String]

Explanation The Service has terminated abruptly. Service Manager will try to restart it.

Recommended Action Monitor the state of the service.

Error Message
ServiceManagerAlarmCatalog- 2 -ServiceStartFailed : Failed to start service.. Service Name [String] Reason [String]

Explanation Failed to start this service. Service Manager will attempt to start the service again.

Recommended Action Monitor the state of the service.

Error Message
ServiceManagerAlarmCatalog- 2 -ServiceStopFailed : Failed to stop service.. Service Name [String] Reason [String]

Explanation Unable to stop the specified service after serveral retries. The service will be marked stopped.

Recommended Action Check the syslog for system error code.

Error Message
ServiceManagerAlarmCatalog- 2 -ServiceRestartFailed : Failed to Restart service.. Service Name [String] Reason [String]

Explanation Unable to restart the specified service.

Recommended Action No action is required.

Error Message
ServiceManagerAlarmCatalog- 1 -ServiceExceededMaxRestarts : Service failed to start and exceeded maximum allowed restarts.. Service Name [String] Reason [Int]

Explanation Service failed to start, even after the max restarts attempts.

Recommended Action Start the service manually.

Error Message
ServiceManagerAlarmCatalog- 0 -FailedToReadConfig : Service Manager failed to read configuration file.. File Name [String] Reason [String]

Explanation Failed to read configuration file. Configuration file might be corrupted.

Recommended Action Re-install CUCM

Error Message
ServiceManagerAlarmCatalog- 1 -MemAllocFailed : Memory allocation failed.. Memory Allocation Failure [String]

Explanation Failure to allocate memory.

Recommended Action (1) Check the syslog for the system error number. (2) If the Alert is seen repeatedly, restart Service Manager (3) If the problem still persist, reboot the CUCM node.

Error Message
ServiceManagerAlarmCatalog- 1 -SystemResourceError : A System call failed.. System Call [String] Service [String] Reason [String]

Explanation System call failed.

Recommended Action (1) Check the syslog for the system error number.(2) If the Alert is seen repeatedly, restart Service Manager (3) If the problem still persist, reboot the node.

Error Message
ServiceManagerAlarmCatalog- 3 -ServiceManagerUnexpectedShutdown : Service Manager restarted successfully after an unexpected termination.. Process ID [ULong] Service Name [String]

Explanation Service Manager unexpectedly terminated. Service Manager has recovered but other components may be adversely affected. The only known causes of unexpected termination are adverse conditions such as hard power down, kernel panic, and readonly filesystem caused due to hardware or software. These conditions can corrupt the filesystem and database in ways that are unrecoverable. Repeat occurrences inevitably lead to corruption. It is critical to identify and remedy the cause of this unexpected termination.

Recommended Action Always shutdown via CLI or platform UI. Do not yank the power-cord or press and hold the power button. Use the recovery disk to perform a filesystem check to identify and attempt to correct any errors that occurred. If errors are detected a rebuild and restore from backup is recommended. Use a redundant reliable power source such as UPS and leverage Uninterruptible Power Supply (UPS) Integration for Unified CM. Run hardware diagnostics to check for hardware failures. If unexpected terminations persist contact Cisco Technical Support for assistance.

Error Message
SplkAXL- 3 -SPLKAXL2000 : An unexpected exception occurred.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended 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 Message
SplkAXL- 3 -SPLKAXL2001 : An error was returned by the CallManager.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action See text in error message for more details. Check the log for other errors.

Error Message
SplkAXL- 3 -SPLKAXL2002 : An Error occured initializing the HTTP interface.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action See text in error message for more details. Check the log for other errors. Check system resource availability (CPU and memory).

Error Message
SplkAXL- 3 -SPLKAXL2003 : The port used is invalid.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the log for other errors. Contact technical support.

Error Message
SplkAXL- 3 -SPLKAXL2004 : An error occured when trying to set the specified HTTP option.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action See text in error message for more details. Check system resource availability (CPU and memory).

Error Message
SplkAXL- 3 -SPLKAXL2005 : An error occured when trying to connect to the specified CallManager AXL interface.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action 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 Message
SplkAXL- 3 -SPLKAXL2006 : An error occured when trying to create an HTTP request to the specified CallManager AXL interface.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action 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 Message
SplkAXL- 3 -SPLKAXL2007 : An error occured when passing login credentials to the specified CallManager AXL interface.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action 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 Message
SplkAXL- 3 -SPLKAXL2008 : An error occured when sending an HTTP request to the specified CallManager AXL interface.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action 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 Message
SplkAXL- 3 -SPLKAXL2009 : An error occured when receiving response from an HTTP request to the specified CallManager AXL interface.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action 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 Message
SplkAXL- 3 -SPLKAXL2010 : HTTP response code 401 received for the second time from the web server, Authentication failed.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify that the login and password specified for the CallManager AXL Interface are correct. Verify that the CallManager IP address or host is correct. Check system resource availability (CPU and memory).

Error Message
SplkAXL- 3 -SPLKAXL2011 : Bad HTTP response code received from the web server.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify that the login and password specified for the CallManager AXL Interface are correct. Verify that the CallManager IP address or host is correct. Check system resource availability (CPU and memory).

Error Message
SplkAXL- 3 -SPLKAXL2013 : An error occured when reading data response from an HTTP request to the specified CallManager AXL interface.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action See text in error message for more details. Check system resource availability (CPU and memory). Check for network connectivity issues.

Error Message
SplkAXL- 3 -SPLKAXL2014 : A required argument is missing.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the log for other errors. Contact technical support.

Error Message
SplkAXL- 3 -SPLKAXL2015 : SplkAXL was not able to connect to LDAP. It will attempt to connect periodically until it succeeds.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify that LDAP Server is running. Check for network connectivity issues.

Error Message
SplkAXL- 3 -SPLKAXL2016 : SplkAXL was not able to specified info from LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify that LDAP Server is running. Check for network connectivity issues.

Error Message
SplkAXL- 3 -SPLKAXL2017 : SplkAXL being used before being initialized.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the log for other errors. Contact technical support.

Error Message
SplkAXL- 3 -SPLKAXL2018 : An error occured querying the specified CallManager.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action See text in error for more details. Check system resource availability (CPU and memory). Check for network connectivity issues.

Error Message
SplkAXL- 3 -SPLKAXL2019 : SplkAXL was unable to set the specified info in LDAP.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify that LDAP Server is running. Check for network connectivity issues.

Error Message
SplkAXL- 3 -SPLKAXL2020 : The CallManager version found is not supported.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the log for other errors. Contact technical support.

Error Message
SplkAXL- 3 -SPLKAXL2021 : Caught a splk_std::SplkXmlException.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
SplkAXL- 3 -SPLKAXL2022 : Caught a xercesc::XMLException.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
SplkAXL- 3 -SPLKAXL2023 : Caught a xercesc::DOMException.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
SplkAXL- 3 -SPLKAXL2024 : There was a problem getting the AXL username and password from CRS.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the error message for a description. Check the log for other errors. Check for network communication errors.

Error Message
SplkAXL- 3 -SPLKAXL2025 : There was a problem getting the JTapi user ID from CRS.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the error message for a description. Check the log for other errors. Check for network communication errors.

Error Message
SplkAXL- 3 -SPLKAXL2026 : There was a problem preparing the CURL connection.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the error message for a description. Check the log for other errors. Check for network communication errors.

Error Message
SplkAXL- 3 -SPLKAXL2027 : There was a problem performing the CURL action.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the error message for a description. Check the log for other errors. Check for network communication errors.

Error Message
SplkAXL- 3 -SPLKAXL2028 : There was a problem performing the CURL action.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Read the error message for a description. Check the log for other errors. Verify that the CallManager hostname is correct. Verify that the AXL username and password used is correct. Verify that the AXL user has AXL API access.

Error Message
SplkAXL- 4 -SPLKAXL3000 : The specified HTTP call timed out. The program will retry request when this error occurs.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action See text in error for more details. Check system resource availability (CPU and memory). Check for network connectivity issues.

Error Message
SplkAXL- 4 -SPLKAXL3001 : The version used does not match supported versions.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action See text in error for more details. Check system resource availability (CPU and memory). Check for network connectivity issues.

Error Message
SplkAXL- 4 -SPLKAXL3002 : The query return a 401 status code that may indicate a user authentication error.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action See text in error for more details. Check the AXL username and password.

Error Message
SplkAXL- 4 -SPLKAXL3003 : The query return a 403 status code that may indicate that the user does not have AXL API access.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action See text in error for more details. Check the AXL username and password.

Error Message
SplkAXL- 4 -SPLKAXL3004 : The query returned an unexpected status code.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action See text in error for more details. Check the AXL username and password.

Error Message
SplkAXL- 6 -SPLKAXL4000 : SplkAXL is not initialized, attempting to initialize.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check logs and verify that the initialization attempt succeeded. Look for other errors. Contact technical support.

Error Message
SplkAXL- 6 -SPLKAXL4001 : The CallManager version from LDAP differs from the version returned by the CallManager.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Look for other errors. Contact technical support.

Error Message
SplkCRS- 6 -SPLKCRS0000 : .. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
SplkMisc- 6 -SPLKMISC0000 : .. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
SplkSecurity- 4 -SECURE3000 : Unable to allocate memory.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
SplkSecurity- 4 -SECURE3001 : Unable to create lock.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
SplkSocket- 3 -SOCKET2000 : This is an internal error. The client is not configured with the information that it needs to locate the specified service.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
SplkSocket- 3 -SOCKET2001 : The specified socket service could not be created on the specified port, bind address and backlog.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Find out whether a service is already running on the specified port. If another instance of the service is already running on the specified port, either stop the running instance or leave it as is without start a new instance. If another service is running on the specified port and that service is required, contact technical support. If no services are running on the specified port, verify that the service is not being blocked by security software or a firewall. If the bind address is not NULL, check whether it is a valid IP address on the computer.

Error Message
SplkSocket- 4 -SOCKET3000 : Socket client received an invalid event from the socket service. The socket connection to the socket service will be dropped and reconnected.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Look at the status of the connection between client and the socket service. If the connection was disrupted, the client has lost data and the application may needs to restart again. If you upgraded the socket service while clients were connected to it, the clients are now running a different version than the socket service. In this case, applications must exit and restart their clients. If this error persists, contact technical support.

Error Message
SplkSocket- 6 -SOCKET0000 : The socket service on the specified port has started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
SplkSocket- 6 -SOCKET0001 : The socket service on the specified port has shut down.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
SplkSocket- 6 -SOCKET0002 : The maximum CalabrioEvent body size has been changed to specified value.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action

Error Message
SplkStd4j- 3 -SSFJ2000 : The specified client failed to connect to a service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action The client application will automatically attempt to reconnect to the service. If the connection attempt succeeds, no action is needed. 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 Message
SplkStd4j- 3 -SSFJ2001 : 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.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Complete the following steps. Check the status of the server. If it is down, restart it. Check the status of the service. If it is down, restart it. Verify the network connection between the client and the server on which the service is running. To verify the connection, run ping or telnet from the client to the server.

Error Message
SplkStd4j- 3 -SSFJ2002 : This is an internal error. The specified client is not configured with the information that it needs to locate the service.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
SplkStd4j- 3 -SSFJ2003 : The specified socket service could not be created on the specified port.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Complete the following steps. Find out whether a service is already running on the specified port. If another instance of the service is already running on the specified port, either stop the running instance or leave it as is without start a new instance. If another service is running on the specified port and that service is required, contact technical support. If no services are running on the specified port, verify that the service is not being blocked by security software or a firewall.

Error Message
SplkStd4j- 3 -SSFJ2004 : There is insufficient memory to run the applet or application.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Complete the following steps. Ensure that the client PC has sufficient memory. If you are attempting to run an applet, ensure that JVM has sufficient memory. From the Windows Control Panel, start the Java Control Panel and go to the Java tab. In the Java Applet Runtime Settings section, click View. Ensure that the Java Runtime Parameters field includes the -Xmx argument with a value of at least 8 MB (-Xmx8m). If you are attempting to run an application, call the application with the -Xmx argument set to a value of at least 8 MB (-Xmx8m).

Error Message
SplkStd4j- 3 -SSFJ2005 : The application is unable to read the specified file.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Verify that the file exists. If the specified exception is a security exception, verify that the application user has access to the specified file.

Error Message
SplkStd4j- 3 -SSFJ2006 : Client cannot retrieve specified event information from the socket message.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended 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 Message
SplkStd4j- 3 -SSFJ2007 : This is an internal error. The client is not configured with the information that it needs to locate the specified service.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
SplkStd4j- 3 -SSFJ2008 : SplkStd library could not be loaded.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Ensure that SplkStd library exists, is of correct version and accessible by SplkStd4J.

Error Message
SplkStd4j- 4 -3000 : Cannot get the localized string or resource for the given key.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Make sure the locale used by application 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.

Error Message
SplkStd4j- 4 -3001 : Cannot get the resource bundle for the base name and locale.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Make sure the locale used by application is a supported language or country. If you verified the previous actions and the error persists, this is an internal error where the localized resource file does not exist. Contact technical support.

Error Message
SplkStd4j- 6 -SSFJ0000 : The specified client is connected to the service on the specified host.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is required.

Error Message
SplkStd4j- 6 -SSFJ0001 : The client has disconnected from the specified service on the specified host.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is required.

Error Message
SplkStd4j- 6 -SSFJ0002 : The socket service on the specified port has shut down.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is required.

Error Message
SplkStd4j- 6 -SSFJ0003 : The socket service on the specified port has started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is required.

Error Message
SplkStd4j- 6 -SSFJ0004 : The maximum CalabrioEvent body size has been changed to specified value.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is required.

Error Message
SplkStd4j- 6 -SSFJ0005 : The time to sleep in milliseconds between attempts to read from socket channel has been changed to specified value.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is required.

Error Message
SplkStd4j- 6 -SSFJ0006 : Indicates the Paths used.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is required.

Error Message
SplkStd4j- 6 -SSFJ0007 : Indicates the successful bootstrap of product.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is required.

Error Message
SplkStd4j- 6 -SSFJ0008 : Indicates JNI callback thread is being started.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is required.

Error Message
SplkStd4j- 6 -SSFJ0009 : Indicates JNI callback thread is being terminated.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is required.

Error Message
SplkStd4j- 6 -SSFJ0010 : Indicates JNI callback thread has stopped.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is required.

Error Message
SplkStd- 3 -STD2000 : The specified client failed to send a heart beat to the service on the specified host.. Service Name [String] error Id [String] Message [String]

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

Recommended Action Complete the following steps. Check the status of the server. If it is down, restart it. Check the status of the service. If it is down, restart it. Verify the network connection between the client and the server on which the service is running. To verify the connection, run ping or telnet from the client to the server.

Error Message
SplkStd- 3 -STD2001 : The specified client failed to connect to a service.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action The client application will automatically attempt to reconnect to the service. If the connection attempt succeeds, no action is needed. 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 Message
SplkStd- 3 -STD2002 : The service controller threw an exception.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the exception message for an explenation of the exception and appropriate actions for resolving the issue.

Error Message
SplkStd- 3 -STD2003 : The application failed to install the console control signal translator.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the error message for an explenation of the error and appropriate actions for resolving the issue.

Error Message
SplkStd- 3 -STD2004 : The application failed to remove the console control signal translator.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check the error message for an explenation of the error and appropriate actions for resolving the issue.

Error Message
SplkStd- 4 -STD3000 : Encountered specified Windows error when performing specified registry operation.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action No action is needed if the registry entry is optional. 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 Message
SplkStd- 4 -STD3001 : Specified registry key is not of REG_SZ or REG_DWORD type.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action If registry key is not of REG_SZ or REG_DWORD type, change it to REG_SZ or REG_DWORD.

Error Message
SplkStd- 4 -STD3002 : Specified registry key is not of REG_DWORD type.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action If registry key is not of REG_DWORD type, change it to REG_DWORD.

Error Message
SplkStd- 4 -STD3003 : Caught unknown exception in specified function.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Contact technical support.

Error Message
SplkStd- 4 -STD3004 : 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..

Explanation

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

Error Message
SplkStd- 4 -STD3005 : 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.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
SplkStd- 4 -STD3006 : Application could not initialize Xerces XML system.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Check if xerces-c_2_7.dll (on Windows) or libxerces-c.so/libxerces-c.so.27/libxerces-depdom.so/libxerces-depdom.so.27 (on Linux) is accessible by the application. Check Xerces error description for further information.

Error Message
SplkStd- 4 -STD3007 : Application could not shutdown Xerces XML system properly.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Xerces XML system is only shutdown 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. Check Xerces error description for further information.

Error Message
SplkStd- 4 -STD3008 : An exception was caught, causing an executing thread to terminate unexpectedly.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action Contact technical support.

Error Message
SplkStd- 4 -STD3009 : 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.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
SplkStd- 4 -STD3010 : The specified thread factory could not create a new thread for specified thread pool potentially causing specified task to be discarded.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
SplkStd- 4 -STD3011 : Failed to start the log file compression thread. Log files may not be compressed automatically.. Service Name [String] error Id [String] Message [String]

Explanation

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

Error Message
SplkStd- 6 -STD0000 : Starting preference change event dispatch thread.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
SplkStd- 6 -STD0001 : Stopping preference change event dispatch thread.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
SplkStd- 6 -STD0002 : Indicates the PreferencesFactory used.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
SplkStd- 6 -STD0003 : Indicates the Paths used.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
SplkStd- 6 -STD0004 : The specified client is connected to the service on the specified host.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
SplkStd- 6 -STD0005 : The specified client has disconnected from the service on the specified host.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
SplkStd- 6 -STD0006 : A shared library was dynamically loaded at runtime.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
SplkStd- 6 -STD0007 : A shared library that was dynamically loaded at runtime. has been unloaded.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
SplkStd- 6 -STD0008 : The logging threshold has been changed in the logging configuration file.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
SplkStd- 6 -STD0009 : The logging maximum file size has been changed in the logging configuration file.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
SplkStd- 6 -STD0010 : The logging maximum file count has been changed in the logging configuration file.. Service Name [String] error Id [String] Message [String]

Explanation

Recommended Action None.

Error Message
SyslogCatalog- 3 -SyslogStringMatchFound : The configured Syslog Alarm/message string had matched. StringMatch [String] MatchedEvent [String]

Explanation Cisco Syslog Agent had detected an alarm which matches the configured string

Recommended Action Take the necessary action based on the received string matched event

Error Message
SyslogCatalog- 3 -HardwareFailure : Hardware failure alarm is received. hwStringMatch [String]

Explanation Cisco Syslog Agent had detected a hardware failure alarm

Recommended Action Take the necessary action based on the received hardware failure event

Error Message
SyslogCatalog- 3 -SyslogSeverityMatchFound : The configured Syslog Alarm/message severity had matched. SeverityMatch [String] MatchedEvent [String]

Explanation Cisco Syslog Agent had detected an alarm which matches the configured severity

Recommended Action Take the necessary action based on the received severity matched event

Error Message
SystemAccessCatalog- 4 -TotalProcessesAndThreadsExceededThresholdStart : The current total number of processes and threads has exceeded the maximum number of tasks configured for Cisco RIS Data Collector service parameter. This situation could indicate some process is leaking or some process has thread leaking.. NumberOfProcesses [String] NumberOfThreads [String] Reason [String] ProcessWithMostInstances [String] ProcessWithMostThreads [String]

Explanation The current total number of processes and threads has exceeded the maximum number of tasks. This situation could indicate some process is leaking or some process has thread leaking.

Recommended Action Check the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads, to see if the parameter has been set to a low value. If it has been, set the value higher or use the default value. Another possible action is that when a new Cisco product is integrated into Cisco Unified Communications Manager (Unified CM), new processes or threads are added to the system. Even in the normal process load situation, it's possible that the total number of processes and threads has exceeded the configured or default value of the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads. Set that parameter to the maximum allowed value. You can also review the details of this alarm to check the ProcessWithMostThreads description and the ProcessWithMostInstances description to discover which processes have the most threads and the most instances. Determine whether these values are reasonable for this process; if not, contact the owner of the process for troubleshooting the reasons why the thread count or the number of process instances is so high. It is also possible that Cisco RIS Data Collector sent a false alarm, which would indicate a defect in the Cisco RIS Data Collector service. To determine if this is the cause of the alarm - after you have checked all the other recommended actions described here - use RTMT to check the System object for performance counters Total Threads and Total Processes to confirm that the values in those counters do not exceed the value configured in the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads. If the counters do not show a value that is higher than what is configured in the service parameter, restart Cisco RIS Data Collector service. If the alarm persists after restarting the service, go to Cisco Unified Serviceability and collect trace logs (Trace > Configuration) for Cisco Syslog, Cisco RIS Data Collector, Cisco AMC Service, and Cisco RIS Perfmon Logs and contact Cisco Technical Assistance Center (TAC) for detailed assistance.

Error Message
SystemAccessCatalog- 5 -TotalProcessesAndThreadsExceededThresholdEnd : The current total number of processes and threads is less than the maximum number of tasks configured in the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads.. NumberOfProcesses [String] NumberOfThreads [String] Reason [String]

Explanation The current total number of processes and threads is less than the maximum number of tasks that has been configured in the Cisco RIS Data Collector service parameter, Maximum Number of Processes and Threads. This can occur because a product which was integrated into Cisco Unified Communications Manager has been disabled or deactivated, which reduces the total number of processes and threads running on the system. Another cause for the number of processes or thread to decrease is that one or more processes has been stopped, which reduces the total number of processes and threads running on the system.

Recommended Action This alarm is for information purposes only; no action is required.

Error Message
TCDSRVAlarmCatalog- 0 -IPAddressResolveError : The IP Address for host was NOT RESOLVED. HostName [String]

Explanation The IP Address for host was NOT RESOLVED

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 0 -NoCMEntriesInDB : There are no CallManager entries in the database..

Explanation There are no CallManager entries in the database.

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 6 -LoadShareDeActivateTimeout : There was timeout during wait for DeActivateLoadShare acknowledgement.

Explanation There was timeout during wait for DeActivateLoadShare acknowledgement

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 0 -LineStateSrvEngCreationError : There was an error during the LineStateSrvEng Creation.

Explanation There was an error during the LineStateSrvEng Creation

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 0 -GlobalSPUtilsCreationError : There was an error during the GlobalSPUtils creation.

Explanation There was an error during the GlobalSPUtils creation

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 0 -TapiLinesTableCreationError : There was an error during the TapiLinesTable creation.

Explanation There was an error during the TapiLinesTable creation

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 0 -HuntGroupControllerCreationError : There was an error during the HuntGroupController creation.

Explanation There was an error during the HuntGroupController creation

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 0 -HuntGroupCreationError : There was an error during the Hunt Group creation.

Explanation There was an error during the Hunt Group creation

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 0 -CallDirectorCreationError : There was an error during the CallDirector creation.

Explanation There was an error during the CallDirector creation

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 0 -SysControllerCreationError : There was an error during the SysController creation.

Explanation There was an error during the SysController creation

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 0 -TimerServicesCreationError : There was an error during the TimerServices creation.

Explanation There was an error during the TimerServices creation

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 3 -DBLGetVersionInfoError : DBL GetVersionInfo function returned NULL.

Explanation DBL GetVersionInfo function returned NULL

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 0 -ExcceptionInInitSDIConfiguration : Exception occured in InitSDIConfiguration function.

Explanation Exception occured in InitSDIConfiguration function

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 0 -SyncDBCreationError : There was an error during the SyncDB creation in SysController.

Explanation There was an error during the SyncDB creation in SysController

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 0 -LostConnectionToCM : Connection to CallManager was lost.

Explanation Connection to CallManager was lost

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 6 -UserLoginSuccess : User successfully logged in.. UserID [String]

Explanation User successfully logged in.

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 3 -UserLoginFailed : User log in failed because of bad user id or password.. UserID [String]

Explanation User log in failed because of bad user id or password.

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 6 -UserAlreadyLoggedIn : User is already logged in. UserID [String]

Explanation User is already logged in

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 6 -UserLoggedOut : User logged out. UserID [String]

Explanation User logged out

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 6 -AgentOnline : Agent online.

Explanation Agent online

Recommended Action NONE

Error Message
TCDSRVAlarmCatalog- 6 -AgentOffline : Agent offline.

Explanation Agent offline

Recommended Action NONE

Error Message
TestAlarmCatalog- 6 -TestAlarmInformational : Testing INFORMATIONAL_ALARM .

Explanation Test Alarm

Recommended Action No action required.

Error Message
TestAlarmCatalog- 0 -TestAlarmEmergency : Testing EMERGENCY_ALARM .

Explanation Test Alarm

Recommended Action No action required.

Error Message
TestAlarmCatalog- 1 -TestAlarmAlert : Testing ALERT_ALARM .

Explanation Test Alarm

Recommended Action No action required.

Error Message
TestAlarmCatalog- 2 -TestAlarmCritical : Testing CRITICAL_ALARM .

Explanation Test Alarm

Recommended Action No action required.

Error Message
TestAlarmCatalog- -TestAlarmDebug : Testing DEBUG_ALARM .

Explanation Test Alarm

Recommended Action No action required.

Error Message
TestAlarmCatalog- 3 -TestAlarmError : Testing ERROR_ALARM .

Explanation Test Alarm

Recommended Action No action required.

Error Message
TestAlarmCatalog- 5 -TestAlarmNotice : Testing NOTICE_ALARM .

Explanation Test Alarm

Recommended Action No action required.

Error Message
TestAlarmCatalog- 4 -TestAlarmWarning : Testing WARNING_ALARM .

Explanation Test Alarm

Recommended Action No action required.

Error Message
TestAlarmCatalog- 6 -TestAlarmWindows : Testing INFORMATIONAL_ALARM .

Explanation Test Alarm for Windows OS based server Only.

Recommended Action No action required.

Error Message
TestAlarmCatalog- 6 -TestAlarmAppliance : Testing INFORMATIONAL_ALARM .

Explanation Test Alarm for Appliance OS based server Only.

Recommended Action No action required.

Error Message
TVSAlarmCatalog- 1 -SDIControlLayerFailed : Failed to update trace logging or alarm subsystem for new settings.. Error [Int] Reason [String]

Explanation This usually indicates a lack of system resources or a failure in database access by the trace logging or alarm subsystem.

Recommended Action In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TVS and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm. Ensure that the database server is running, and that the Cisco Database Layer Monitor service is running without problems. If this alarm persists, contact the Cisco Technical Assistance Center (TAC) with TVS service and database trace files.

Error Message
TVSAlarmCatalog- 3 -ConfigThreadReadConfigurationFailed : Failed to retrieve enterprise parameter values from database at TVS service startup..

Explanation This is usually caused by database access failure.

Recommended Action In Cisco Unified Serviceability, enable Detailed level traces in the Trace Configuration window for TVS and Cisco Database Layer Monitor services. Also, use RTMT to look for error messages that may have occurred around the time of the alarm.

Error Message
TVSAlarmCatalog- 1 -ConfigThreadChangeNotifyServerSingleFailed : Failed to allocate resources to handle configuration change notification from database..

Explanation This usually indicates a lack of memory when there is a system issue such as running out of resources.

Recommended Action Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message
TVSAlarmCatalog- 6 -ITLFileRegenerated : New ITL File has been generated..

Explanation This usually means that a new certificate related to ITLFile has been modified.

Recommended Action None.

Error Message
TVSAlarmCatalog- 6 -TVSCertificateRegenerated : TVS Server certificate has been regenerated..

Explanation This usually means that the TVS certificate has been regenerated. TVS server will automatically be restarted

Recommended Action None.

Error Message
TVSAlarmCatalog- 6 -RollBackToPre8.0Disabled : Roll Back to Pre 8.0 has been disabled in the Enterprise Parameter page..

Explanation This usually means that the RollBack to Pre 8.0 feature is modified in the Enterprise Parameter page

Recommended Action None.

Error Message
TVSAlarmCatalog- 6 -RollBackToPre8.0Enabled : Roll Back to Pre 8.0 has been enabled in the Enterprise Parameter page..

Explanation This usually means that the RollBack to Pre 8.0 feature is modified in the Enterprise Parameter page

Recommended Action None.

Error Message
TVSAlarmCatalog- 6 -DefaultDurationInCacheModified : Default value of a Certificate duration in cache is modified in the Service Parameter page..

Explanation This usually means that the Default Certificate duration in cache value is modified int the Service Parameter page

Recommended Action None.

Error Message
TVSAlarmCatalog- 6 -ClusterSecurityModeModified : Cluster Security Mode is modified..

Explanation This usually means that the Cluster Security mode has been modified

Recommended Action None.

Error Message
TVSAlarmCatalog- 1 -TVSServerListenSetSockOptFailed : Failed to increase the size of the network buffer for receiving file requests.. nError [Int] IPAddress [String] Port [Int]

Explanation This usually indicates a lack of memory when there is a system issue such as running out of resources.

Recommended Action Use RTMT to monitor the system memory resources and consumption and correct any system issues that might be contributing to a reduced amount of system resources.

Error Message
TVSAlarmCatalog- 1 -TVSServerListenBindFailed : Fail to connect to the network port through which file requests are received.. nError [Int] IPAddress [String] Port [Int]

Explanation This usually happens if the network port is being used by other applications on the system or if the port was not closed properly in the last execution of TVS server.

Recommended Action Verify that the port is not in use by other application. After stopping the TVS server, at the command line interface (CLI) on the TVS server, execute the following command: show network status listen. If the port number specified in this alarm is shown in this CLI command output, the port is being used. Restart the Cisco Unified Communications Manager system, which may help to release the port. If the problem persists, go to Cisco Unified Serviceability and enable Detailed level traces in the Trace Configuration window for the TVS service and contact the Cisco Technical Assistance Center (TAC).

Error Message
IMEAlarmCatalog- 2 -BootstrapFailed : Bootstrap servers unreachable.. Bootstrap peers [String]

Explanation This alarm indicates that the IME server was unable to reach any of the bootstrap peers for a particular IME distributed cache. This means that the IME distributed cache is not in service and no operations on the IME distributed cache can proceed. The IME server will periodically re-attempt to connect to the Bootstrap servers. If the condition is due to a temporary Internet connectivity issue, the problem will self-repair. However, if it is due to a persistent condition, action must be taken.

Recommended Action Make sure that your firewall configuration is allowing the IME server to access the Internet. Verify that your Internet connectivity is operational. If those are correct, try pinging the configured IP addresses and ports of the bootstrap servers, and diagnose any network issues from there. The IP addresses and ports of the bootstrap servers that were tried by the IME server are included as name/value pairs in the alarm.

Error Message
IMEAlarmCatalog- 4 -InvalidCertificateFromPeer : Invalid certificate received from peer. Reason Code [Enum] Peer IDs [String] IP address [String] Claimed Peer ID [String]

Explanation This alarm indicates that another IME server presented an invalid certificate. A certificate can be invalid because it expired or is signed by an unknown certificate authority (CA).

Recommended Action This alarm most likely means that one of the other IME servers in the network has an expired certificate or a misconfigured CA. There is little you can do to fix these cases, and the system will recover gracefully.

Reason Code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Expired
2 Unknown Certificate Authority
Error Message
IMEAlarmCatalog- 1 -InvalidCertificate : Invalid certificate configured.. Certificate [String]

Explanation This alarm is generated if the IME distributed cache is enabled on the IME server, but a certificate has not been has been configured or an invalid certificate has been configured.

Recommended Action If the certificate name is empty, it means that no certificate is configured. Obtain a certificate and configure it. If a certificate name is provided, it means that a certificate is configured, but isn't appropriate for this IME distributed cache. Check the following: 1. Check that the certificate is not expired 2. Check that the certificate is signed by a CA whose certificate has been configured into the trust list. The certificate for the public Cisco Intercompany Media Network will be automatically included in your configuration. 3. Check that the certificate contains a SubjectAltName field, and that this field has one or more URI parameters, each in the following format: IME:(peerID)@(IMEDistributedCache-name); Check that the IME distributed cache-name matches the name of the IME distributed cache this certificate is configured to be used with.

Error Message
IMEAlarmCatalog- 4 -StoreFailed : Store failure into IME distributed cache. DID number [String] Resource ID [String] Peer ID [String]

Explanation This alarm is generated when the IME service fails to store a E.164 into the IME distributed cache. This can be due to an unusual transient network condition. It is self-repairing; however, it may introduce a brief interval during which IME server in other enterprises will fail to discover that E.164 number, and thus you might miss an opportunity to receive VoIP calls towards that number. IME may take longer to switch to VoIP for calls to that number from other enterprises.

Recommended Action Typically, no action is required on your part. However, if you are trying to understand why you are not receiving calls to a specific number over VoIP, this alarm will help you diagnose the problem.

Error Message
IMEAlarmCatalog- 4 -QuotaExceeded : Store failure into IME distributed cache because the quota has been met. DID number [String] Resource ID [String] Peer ID [String]

Explanation This alarm is generated when IME fails to store a E.164 into the IME distributed cache due to an excess of quota according to the storing node. This is a highly unlikely error condition.

Recommended Action Unlike StoreFailed, this error condition is persistent. When it does occur, it is usually because you are just underneath your quota limit on the number of E.164 numbers which can be published. Obtaining a second IME server and splitting the numbers across them will fix the problem.

Error Message
IMEAlarmCatalog- 3 -InvalidCredentials : Invalid or mismatched credentials. User name [String] IP address [String]

Explanation This alarm is generated when a Unified CM attempts to connect to the IME server, but presents invalid credentials - either an ivalid user name or invalid password.

Recommended Action Check the configured username and password on both the IME server and Unified CM, and make sure they match. The alarm will contain the IP address of the offending Unified CM node; you can use this to determine which Unified CM node, and thus cluster, is the offending one.

Error Message
IMEAlarmCatalog- 3 -IMEDistributedCacheInactive : Inactive IME distributed cache. IME distributed cache name [String]

Explanation This alarm is generated when Unified CM attempts to connect to the IME server, however, the IME distributed cache is not currently active on the IME server.

Recommended Action Check to make sure that the certificate for the IME server is provisioned. Check to make sure that the IME distributed cache has been activated via the CLI.

Error Message
IMEAlarmCatalog- 3 -OriginatingVCRLost : VCR Overflow.. DID number [String]

Explanation This alarm is generated when IME has been forced to abandon an attempt at validating a called E.164 DID due to an overflow of its buffers. It is an indication of an overload on the IME server.

Recommended Action If you are consistently seeing this error, it means that your IME server is at capacity, and you are required to purchase another IME server. Infrequent instances of this alarm may occur due to extremely unlikely statistical anomalies which can cause a buffer overflow due to temporary spikes in utilization.

Error Message
IMEAlarmCatalog- 4 -OrigValidationFailure : Validation Failure.. DID number [String] Peer ID [String] IP address [String]

Explanation This alarm is generated when the IME server failed an attempt to validate authentic ownership of an E.164 DID by a target enterprise. This alarm can be caused for several reasons. One is that the target enterprise is misconfigured or malicious, and does not in fact own the number in question. There is nothing you can do about these cases; the system will automatically ignore those enterprises until they fix their configuration. However, the alarm can also occur because of a time synchronization problem between your Unified CM and the target enterprise. If you are seeing a regular occurrence of this alarm across a large number of DIDs and a large number of target peerIDs (both of which are included in the alarm), it is a strong indicator of a time synchronization problem.

Recommended Action For frequent occurrence of this alarm across a large number of different peerIDs, check the time settings on your Unified CM clusters and verify that the time is accurate. If the alarm is associated with a closed user group (the IME distributed cache name is included in the alarm), the alarm can be due to misconfiguration of the various timers. Consult the administrator of the closed user group (CUG) to obtain the appropriate values for these parameters. If the alarm is occurring for a specific peerID or a small number of peerIDs, it is a sign of potential attack or gross misconfiguration at another enterprise. The IME server will ignore these, but at the cost of CPU. If your IME server is running at high CPU utilization and you are seeing a large number of these alarms, you should configure your firewall to block outbound TCP connections to the IP address of the peerID which is causing the problems. That will cause the IME server to fail to even attempt validation to this peer, reducing the CPU costs. That might reduce your CPU utilization.

Error Message
IMEAlarmCatalog- 3 -BadNumber : Possible misconfigured DID.. DID number [String]

Explanation This alarm is generated when the IME server was asked to validate an E.164 DID, but had no matching call information for a call to this DID. This alarm can be caused by several conditions. The most common condition is where the IME server has been rebooted, and has lost call records. Over the next 24 hours, you will see this alarm repeatedly from the service once it recovers. The other, more important case, is when you have misconfigured the set of enrolled DID patterns to include an E.164 DID that you do not actually own. Persistent instances of this alarm to the same number, present as an attribute of this alarm, indicate this possibility.

Recommended Action After a reboot of a IME server, you should ignore this alarm for the next 24 hours. If you see this alarm outside of a reboot, check the E.164 number present in the alarm, and verify that this E.164 number corresponds to one that you actually own. If not, correct your configuration of enrolled DID patterns. If you do own the number, this alarm may still be thrown if you have misconfigured the translation patterns which convert called party numbers to E.164 numbers, or you have forgotten to mark a trunk device as 'PSTN access'. Check the call detail records on Unified CM for calls made to the line associated with that E.164 number over the last 24 hours. Once you have found those calls, check the originating device, and identify calls which were received over a PSTN device. If the device is in fact a device used for PSTN access, but is not currently configured as a PSTN access device, change the configuration so that it is a PSTN access device. If it was labeled as a PSTN access device, check the transformation patterns configured on that device, and make sure that they properly convert the called party number to an E.164 format. Remember, the transformation rule must generate an E.164 number including the + sign.

Error Message
IMEAlarmCatalog- 5 -TicketPasswordChanged : Ticket password changed.. User name [String]

Explanation This alarm is generated by the IME server when the administrator changes the password that is used to generate the validation tickets. The validation tickets are a critical piece of the security of IME.

Recommended Action You should check to make sure that you, or another authorized administrator, has actually changed the password. If the change is unauthorized, it is a sign of potential compromise of the administrative interfaces on the IME server. You should immediately change administrative passwords on the IME server to prevent further unauthorized access.

Error Message
IMEAlarmCatalog- 4 -BlockedValidation : Validation attempt blocked.. Domain name [String] DID number [String]

Explanation This alarm is generated by the IME server when another domain is IME-capable, and wished to learn a route to reach your domain, however, they were blocked because their domain appears on your Untrusted list.

Recommended Action This may not be an error condition at all. If you see this alarm repeatedly from the same domain, it means that communications between you and that domain are occurring with some regularity, and you may wish to consider adding that domain to your Trusted list.

Error Message
IMEAlarmCatalog- 4 -SWUpdateRequired : Software update required.. Upgrade message [String] Upgraded version [String] Criticality of the upgrade [Enum]

Explanation This alarm is generated by the IME server when a new version of IME software is required. The alarm severity will tell you how important it is to install this upgrade. Critical upgrades are essential for you to apply immediately! This alarm will repeat until you perform the upgrade.

Recommended Action Visit the Cisco website to obtain more information about the software update. For critical upgrades, you should attend to this within a matter of days. These upgrades cover cases of security vulnerabilities or key functional outages. In some cases, if you do not immediately apply a critical upgrade, IME may be rendered inoperable through an inability to connect to the network.

Criticality of the upgrade-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Critical
2 Recommended
3 Optional
Error Message
IMEAlarmCatalog- 5 -MessageOfTheDay : Message from network administrators.. Message text [String]

Explanation This alarm is generated by the IME server when the administrators of the Cisco Intercompany Media Network have a message for you.

Recommended Action Read the contents of the note and take appropriate action.

Error Message
IMEAlarmCatalog- 5 -ConfigUpdated : Updated network configuration received.. Configuration Version [String] Bootstrap peer ID [String]

Explanation The network administrators have pushed out new configuration parameters for the network. These parameters have automatically been accepted by the IME server.

Recommended Action None.

Error Message
IMEAlarmCatalog- 1 -BannedFromNetwork : IME has been banned from network.. Configuration Version [String] Peer ID [String]

Explanation The network administrators have pushed out new configuration parameters for the network, and those parameters included a directive to ban this IME server from the network. Your IME server is now either fully or partly inoperative. This should only happen in the most extreme of cases, typically if Cisco has detected that your service is being used maliciously to launch attacks into the IME network. If you believe you have received this in error, contact technical support immediately.

Recommended Action Contact technical support.

Error Message
IMEAlarmCatalog- 5 -SuccessfulEnrollment : IME has successfully obtained a certificate from the CA.. Message [String]

Explanation IME has, at a command from the CLI, or automatically, obtained a new or renewal certificate from the certificate authority (CA).

Recommended Action Notification purposes only; no action is required

Error Message
IMEAlarmCatalog- 3 -EnrollFailure : IME enroll failed.. Message [String] IP address [String] IME Server ID [String] Reason code [Enum]

Explanation The IME server has, at a command from the CLI, or automatically, attempted to enroll with the certificate authority (CA) and obtain a new certificate - a process that is required for continued operation. However, this attempt failed due to timeout or because you have not purchased an automated renewal.

Recommended Action If you have not actually purchased automated renewals for your IME certificates, then this alarm is expected at around three weeks prior to expiration of your certificate. Please visit Godaddy and purchase a renewal IME certificate. If you have purchased a renewal, and the error is a timeout, IME will retry the attempt, and so no action may yet be required. If this alarm repeats for several days with a timeout, it means that IME was unable to contact the CA. Check your Internet connections and contact Godaddy to see if they are having an outage.

Reason code-Enum Definitions
Enum Definitions - Failure cause:
Value Definition
1 Timeout
2 Unauthorized
Error Message
IMEAlarmCatalog- 2 -NoLicense : No IME license found.. IP address [String]

Explanation IME requires a license to function. Also, IME licenses are version-specific so be certain that the license is for the version you are trying to run. You can run a license unit report in CLI (utils ime license file report).

Recommended Action Request license generation for your version of IME and upload the license using the SFTP account. Thereafter, you can install the license in CLI (utils ime license file install).

Error Message
IMEAlarmCatalog- 5 -SDLLinkISVtoIME : SDL link between IME service and IME Config Manager service restored.. Remote Application IP Address [String] Unique Link ID [String] Local Node ID [Int] Local Application ID [Int] Remote Node ID [Int] Remote Application ID [Int]

Explanation This alarm indicates that IME has gained communication with the IME Config Manager service.

Recommended Action Notification purposes only; no action is required

Error Message
IMEAlarmCatalog- 1 -SDLLinkOOStoIME : SDL link between IME service and IME Config Manager service is out of service.. Remote Application IP Address [String] Unique Link ID [String] Local Node ID [Int] Local Application ID [Int] Remote Node ID [Int] Remote Application ID [Int]

Explanation This alarm indicates that IME server has lost communication with IME Config Manager service. This alarm usually indicates that one of these services has gone down (either intentionally for maintenance; or unintentionally due to a service failure or connectivity failure).

Recommended Action Check for any alarms that might have indicated an IME failure or an IME Config Manager failure and take appropriate action for the indicated failure. If the service was stopped intentionally, start the service.

Error Message
IMEAlarmCatalog- 5 -ServicePortOnline : A Cisco IME service port is online. Protocol [String] Port Number [UInt]

Explanation IME has successfully opened a socket port to provide service

Recommended Action Notification purposes only; no action is required

Error Message
IMEAlarmCatalog- 2 -ServicePortOffline : An IME service port is offline. Protocol [String] Port Number [UInt] Error Number [Int]

Explanation An IME socket port that is used to provide service has unexpectedly closed. Normally, this port should never be closed. An unexpected closing of this port generally indicates an operating system failure or an external attack on IME.

Recommended Action Restart the IME service and verify that IME opens this socket port and provide service. You can watch for an instance of the notice level alarm, ServicePortOnline, when service to the port has been restored. If this alarm occurs for an extended duration, collect the existing trace files and contact the Cisco Technical Assistance Center (TAC).

Error Message
IMEAlarmCatalog- 4 -SuspiciousIPAddress : IME has identified suspicious connection attempts from an IP address. Port Number [UInt] IP Address [String]

Explanation IME has identified suspicious connection attempts from an IP address and has temporarily blocked the address. This alarm is an indication that a Denial-of-Service attack may have been attempted from this IP address.

Recommended Action Examine network activity for repeated attempts to access the port number specified in this alarm. Using the IP address specified in this alarm, attempt to identify the device that has been sending connection attempts to the port. If the IP address belongs to a device that is configured in IME, evaluate the possible reason for such numerous connection attempts. Generally, no device that is functioning properly will trigger this alarm. Reset the device or remove the device from the network.

Error Message
IMEAlarmCatalog- 2 -ServicePortFailedToOpen : An IME service port fails to be opened. Protocol [String] Port Number [UInt] Error Number [Int]

Explanation An IME socket port that is used to provide service fails to open.

Recommended Action Please check the IME configuration to make sure that this port is not used by other applications. If this alarm occurs repeatly, collect the existing trace files and contact the Cisco Technical Assistance Center (TAC).