Cisco TelePresence Manager 1.3 Administration and Installation Guide

Timestamp

Date and time the message was logged. You can sort the messages in ascending or descending order by the time stamp.

Type

Message type.

ID

Message identification number. You can sort the reports in ascending or descending order by ID.

Module

Component within CTS-Manager that generated the error.

Message

Explanation of problem detected. Move your mouse pointer over a message field to see a complete description.

Detailed view of Meetings reports that the Cisco TelePresence meeting is "Pending for more information from Exchange".

This message appears when one of the two following conditions occurs:

•When Cisco TelePresence Manager receives notice of an event, it waits 30 seconds to see if any further event details are forthcoming from Microsoft Exchange and then validates the meeting.

•If the room is in manual-accept mode and the room's delegate has accepted a meeting only tentatively or has not responded to meeting e-mail notification

•Wait a few moments and view Meetings status again to see if the meeting has been validated.

•Advise the room delegate to respond to meeting e-mail notification.

The meeting organizer receives no e-mail to confirm the meeting is scheduled.

This problem occurs when a room is not in auto-accept mode.

Make sure reserved rooms are in auto-accept mode.

If a room is in manual-accept mode, the meeting invitation must be accepted by the room's delegate using Microsoft Outlook or Lotus Notes.

Scheduled Meetings do not show the status "In Progress", or Rooms do not show "In Use" when a call is placed.

Connectivity between the Cisco TelePresence system and CTS-Manager is lost.

Check the Rooms window for status.

The SSH username and password should be configured for the Cisco TelePresence system. See the Unified CM Installation Guide for Cisco TelePresence for more help.

Verify that the Calendar service is running on the Cisco TelePresence system.

Room status indicates an error condition.

Place your mouse over the status to see the error described in a tooltip. This problem can occur when:

•The phone associated with the Cisco TelePresence meeting room is not included in Cisco TelePresence Manager application user profile.

•The phone associated with the Cisco TelePresence meeting room is not registered with the Unified CM.

•More than one Cisco TelePresence phone could be configured with the same room name.

Cisco TelePresence IP phone associated with participating rooms must be added to the CTS-Manager Application User Profile.

Update the CTS-Manager Application User Profile with correct room data.

Check the Rooms window for status.

Check the IP connectivity between the equipment and CTS-Manager.

Missing Secure Shell username and password for the Cisco TelePresence IP phone should be configured in the Unified CM configuration.

A recurring meeting is not listed in the Scheduled Meetings window

The first occurrence of the meeting is scheduled more than one year in the past.

Reschedule the meeting so that the start date for the recurring meeting is less than one year in the past.

Two instances of the same meeting (either a single meeting or an instance of a recurring meeting) are listed in the Scheduled Meetings window.

The date or time of the meeting was modified after the start time of the meeting, but before the meeting was initiated or the before the meeting end time has occurred.

This is expected behavior. The meeting instance with the new start date or start time is treated as a new meeting.

A recurring point-to-point meeting listed in the Scheduled Meetings window displays an Error status.

OR

A recurring multipoint meeting is listed in the Scheduled Meetings window as a point-to-point meeting (only two rooms are scheduled).

The rooms included in the meeting are in manual-accept mode (delegates must accept meeting invitations).

If the recurring meeting is a point-to-point meeting (R1 & R2) and a room delegate has declined one instance (R1), all meeting instances show only one room scheduled.

If the recurring meeting is a multi-point meeting (R1, R2, & R3) and a room delegate has declined one instance (R1), all meeting instances show only two rooms scheduled (R2 & R3).

•In Microsoft Exchange, select the checkbox for the room(s) missing from the scheduled meeting and Re-sync.

•In IBM Domino, click Re-sync to re-sync the database.

Room Status reports a Subscription or Synchronization error with Microsoft Exchange

A Discovery operation attempted to sync to a newly added Room calendar before even one meeting was added to the calendar.

A Room calendar must contain at least one scheduled meeting in order for Cisco TelePresence Manager to successfully subscribe and sync.

To remove the error status:

1. Schedule at least one meeting on the Room calendar.

2. From the System Configuration > Microsoft Exchange window, select the room showing the subscription error and click Re-sync.

3. From the Support > Rooms Summary tab, select the room showing the Exchange subscription or sync error (on the Status tab), and click Update Schedule.

Recurring or single meeting with only one room is displayed with an Error status after meeting start time has passed.

If a meeting organizer deletes a meeting that was

1. not launched,

2. after the meeting start time

all but one rooms are removed from the scheduled meeting and the meeting is set to an Error status.

If the meeting was a recurring meeting and the meeting series was deleted after the first instance of the meeting was

1. not launched,

2. after the 1st meeting instance start time

all but one rooms are removed from the scheduled meeting and the meeting is set to an Error status.

This is expected behavior. All room calendars are available for scheduled meetings.

Meeting Confirmation email refers to upcoming meeting instance, not to meeting instance whose details were updated.

The Send Email button in the Meeting Details window is available to any user (Concierge or Administrator) logging into Cisco TelePresence Manager. If you make changes to a future instance of a recurring meeting and click Send Email, the confirmation email sent to the Meeting Organizer refers to the upcoming meeting and not to the future instance that was changed.

The Meeting Organizer must click the link in the Confirmation email to open the Meeting Details window and select the future meeting instance to see the changes made.

Meeting instances in a recurring meeting are not listed in the Action Required emails.

Action Required emails list only the first 50 instances of a recurring meeting.

To view additional instances of a recurring meeting, the Meeting Organizer must click the link in the Action Required email and display the Meeting Details window.

A scheduled meeting is not listed in the Scheduled Meetings window. (For IBM Domino deployment.)

The date of a scheduled meeting must fall between two days prior to the current date and two calendar years in the future ( -2 days — +12 months), in order for Cisco TelePresence Manager to sync the meeting between the Domino database and the Cisco TelePresence Manager database.

Note If a meeting is scheduled while Cisco TelePresence Manager is down, and more than two days pass before CTS-Manager is restarted, the meeting will not be sync'd and must be rescheduled.

Verify the rooms are registered properly in the System Configuration > IBM Domino window. The room name appearing in the Associated Rooms column must exactly match the room names added to the profile in Unified CM.

Note In Unified CM the Product Specific Configuration Layout window refers to "Room Name (from Exchange)". This is the room name that must match the room name in the Domino server database in order for CTS-Manager to successfully sync.

A deleted meeting still appears in CTS-Manager. (For IBM Domino deployment.)

The CTS-Manager database is set to delete scheduled meetings according to the (Polling Interval * 3). The Polling Interval is set in the IBM Domino window.

If the scheduled meeting does not fall within two days prior to the current date and two calendar years in the future ( -2 days — +12 months), the meeting is not deleted from the CTS-Manager database.

Please wait the prescribed amount of time to ensure the meeting is deleted.

Scheduled meetings show an error.

OR

New meetings are not appearing in the Scheduled Meetings window.

After the Microsoft Exchange server is down, CTS-Manager does not regain a connections.

Re-sync the rooms with scheduled meeting errors or missing meetings. After the room re-sync Exchange may still display an error status.

This can be fixed by either

•waiting for CTS-Manager to renew subscription to the affected rooms (occurs every 55 minutes) OR

•restarting the CTS-Manager server.

New meetings are not processed by CTS-Manager after a software upgrade.

The Domino or Exchange server was down during the upgrade and the initialization process did not complete properly.

•Initiate Discovery manually to initialize the processes.

OR

•Restart CTS-Manager

An Action Required email does not list the error for all instances of a recuring meeting (Domino Calendar Server issue)

If a recurring meeting is created with two endpoints, and is then modified by removing one endpoint for all meeting instances, the Action Required email does not list out all the meeting instances.

This is expected behavior. The meeting organizer should modify the meeting series using Lotus Notes and add a second Cisco TelePresence room.

A deleted meeting still appears in the Scheduled Meetings window.

The meeting was deleted from the Exchange room calendar, but the meeting is not deleted in CTS-Manager. This can happen is room reservations are managed using Outlook Auto Accept.

Delete the meeting from the room calendar.

Refer to Microsoft Knowledge Base article 280854 for more information.

The Cisco TelePresence IP phone displays the standard idle screen instead of the meeting list managed by CTS-Manager.

This problem can occur when:

•There is no connectivity between the Cisco TelePresence IP phone and Cisco TelePresence Manager.

•The scheduled meeting is outside the user-specified time window.

•The Secure Shell username and password for the Cisco TelePresence IP phone in the Unified CM configuration are missing.

•CTS-Manager has not sent required information to the Cisco TelePresence IP phone.

•The network is not properly configured or is down.

•Check the dashboard for phone status.

•Only meetings within the user-specified time window are displayed on the phone user interface. The administrator can configure the number of days displayed.

•Verify that the Calendar service is running in the Cisco TelePresence system.

A scheduled meeting does not appear on the Cisco TelePresence phone user interface.

•The room name configured in Unified CM does not match the actual room name (e-mail alias) configured in the Directory Server.

•Duplicate room names are configured.

•Cisco TelePresence IP phone associated with participating rooms has not been added to the CTS-Manager Application User Profile.

•The Exchange or Domino user account for CTS-Manager does not have permission to retrieve calendar data.

•The room name must exactly match the name (e-mail alias) provided in the Directory Server.

•Remove duplicate room names configured in Unified CM.

•Update the CTS-Manager Application User Profile with correct room data.

•Change the CTS-Manager user account for Exchange or Domino so it has permissions to retrieve (read) room and calendar data.

A proposed meeting was deleted from Microsoft Outlook, but it still appears on the Cisco TelePresence phone user interface.

This problem can occur when:

•Outlook Web Access (OWA) is used to schedule meetings because OWA does not receive delete updates.

•CTS-Manager is not synchronized with the Exchange database.

•Log into Microsoft Outlook and use that application to delete the meeting.

•Use the Re-Sync Operations under Microsoft Exchange to resynchronize the database and meeting schedule.

Room is not sync'd between Microsoft Exchange and Cisco TelePresence Manager.

•LDAP user container DN must be configured correctly for all domains.

•LDAP field mapping should be set to default settings.

Extra room has been added to a specific instance of a recurring meeting.

Note This issue occurs with Exchange 2007.

1. A meeting organizer schedules a recurring meeting with two or more rooms (R1, R2 and R3).

2. Meeting organizer deletes R1 from one instance of recurring meeting (M1).

3. Meeting organizer adds a fourth room to master series (R4).

4. R1 has been re-added to M1.

1. Open the R1 room calendar and delete the scheduled meeting instance.

2. In Cisco TelePresence Manager, go to the Configuration>Microsoft Exchange window, select the checkbox next to the room and click the Re-sync button.

Note Refer to Microsoft Knowledge Base article 949294 for more information.

Room Status reports a Subscription status error with Microsoft Exchange

A Discovery operation attempted to sync to a newly added Room calendar before even one meeting was added to the calendar.

A Room calendar must contain at least one scheduled meeting in order for Cisco TelePresence Manager to successfully subscribe and sync.

To remove the error status:

1. Schedule at least one meeting on the Room calendar.

2. From the System Configuration > Microsoft Exchange window, select the room showing the subscription error and click Re-sync.

3. From the Support > Rooms Summary tab, select the room showing the Exchange subscription or sync error (on the Status tab), and click Update Schedule.

Room is not sync'd between Microsoft Exchange and Cisco TelePresence Manager.

•Cisco TelePresence Manager must have Full Access or Read Permission to the Room's mailbox.

•The Room mailbox must be created with English as the default language.

•The Room user must log into the Room mailbox at least once.

•The Room email ID must be uniquely assigned to only one user (Room user).

•Room's email ID must be configured correctly in Unified CM and Exchange.

•The Cisco TelePresence System MAC address must be added to the User Profile in Unified CM.

•Each Cisco TelePresence System may have only one corresponding IP Phone, that shares the same DN with the Cisco TelePresence System and whose MAC address has been defined in the Unified CM User Profile.

•The Cisco TelePresence Manager's clock must be in sync with the Exchange system clock.

•UDP port 3621 cannot be blocked by a firewall between Exchange Cisco TelePresence Manager.

•Forms Based Authentication must not be enabled for the Exchange website in the Exchange server that is registered with Cisco TelePresence Manager.

•Verify the room is configured for Auto-accept, or the Room Delegate has accepted the meeting invitation.

•At least one meeting must be scheduled on a room calendar before syncing with CTS-Manager, or CTS-Manager will return a sync error condition for the room

In the Microsoft Exchange window, clicking Test Connection returns an error.

•Verify Exchange 2007 has a Client Access role.

•For IIS Manager on the Exchange server, make sure SSL is required is not checked for the default website when you are not using secure mode.

•In Exchange Management Console, make sure Exchange (Default Website) is not configured with FBA.

Note FBA must be disabled for Cisco TelePresence manager to sync meeting information with Exchange. If a new Room mailbox is added to a new Exchange server that has FBA enabled, you can either disable FBA on the second Exchange server, or use the initial Exchange server as the front-end server and point Cisco TelePresence Manager to that server.

In the Scheduled Meetings window the Meeting Subject is deleted.

Note This issue occurs with Exchange 2007.

By default, the Exchange mailbox calendar attributes AllBookInPolicy, DeleteSubject, and AddOrganizerToSubject are set to true. These attribute flags set to true delete the meeting subject and replace it with the organizer's username.

In order to display the original subject of the meeting, set DeleteSubject and AddOrganizerToSubject in the room calendar maibox setting to false.

Failed to authenticate. Check authentication parameters. Username: short form of email address. Password: Internet password

This problem can occur when the incorrect password is specified for the Domino server, or the LDAP server configured with Domino.

Make sure the Internet password is used in the Password fields in the System Configuration> IBM Domino window and the LDAP Server window.

Room is not sync'd between Domino server and Cisco TelePresence Manager.

•The Room user must log into the Room mailbox at least once.

•The Room email ID must be uniquely assigned to only one user (Room user).

•Room's email ID must be configured correctly in Unified CM and Domino.

•The Cisco TelePresence System MAC address must be added to the User Profile in Unified CM.

•Each Cisco TelePresence System may have only one corresponding IP Phone, that shares the same DN with the Cisco TelePresence System and whose MAC address has been defined in the Unified CM User Profile.

•The Cisco TelePresence Manager's clock must be in sync with the Domino system clock.

Clicking Test Connection returns an error.

The following services should be added to the list of server tasks to load automatically when the IBM Domino servers is started:

•RNRMGR

•DIIOP

•HTTP

•LDAP

•Router

•Calconn

In addition to the above services:

•the Resource Reservations Database must be local to the Domino server

•The Resource Reservation Database must be using the Resrc7.ntf or Resrc8.ntf template.

•The appropriate Security Settings should be applied to the Domino server.

•Verify the Host, Port, Organization Name, Username, and Password are correct.

•Verify the server is reachable from the Cisco TelePresence Manager host by performing a telnet to the Domino port.

Meeting Organizer unable to log into Cisco TelePresence Manager using the link in the Action Required email.

•Meeting Organizer is not using the internet password.

•Meeting Organizer is not entering their login name correctly.

•Verify the Meeting Organizer's password is set as the Domino internet password.

•On the Cisco TelePresence Manager login page, the Meeting Organizer must enter their Username in the standard Lotus Notes format <username>/<organization name>
(The organization name must match the value in the Organization Name field on the System Configuration > IBM Domino window).

Code

Message

Explanation

Recommended Actions

1000

Internal server error: $1.

A bucket for all untyped errors. The detail message would contain the actual error.

Contact support.

1001

Failed to parse config file '$1'. Error: $2.

The server fails to parse the config/ctis.xml configuration file. The webapp would fail to start up.

Check syntax of ctis.xml. This file should be changed by qualified technicians only. If possible, revert to its original content and restart Tomcat server. Contact support for further assistance.

1004

Version $1 is not supported for component: $2.

CTM does not support the version extracted from the given component.

Deploy CTM with supported versions of Exchange and LDAP only.

1005

The operation is unsupported on OS '$1'.

The current operation is not supported on the given platform.

Contact support. Users should not see this error at all as we only deploy on Linux.

1007

Failed to restart host. Error: '$1'.

CTM fails to restart the machine as requested. The detail message is given.

Contact support.

1008

The functionality '$1' is not yet implemented.

The given functionality has not been implemented yet.

Upgrade CTM.

1009

Error in initialization: '$1'.

Database maintenance manager fails to initialize due to missing scripts for either backup, purge or cron job.

Contact support. The installation process has failed.

1010

One or more arguments are null.

Exchange component is failing to test connection because one of the required parameters (host, super user account name/password, bind method) is null.

Check information provided on the Exchange configuration screen.

1011

Unable to dispatch API call.

CTM component is unable to communicate with the CTM Engine.

Check for any errors in the logfile. Contact support.

1012

Failed to shutdown host. Error: '$1'.

The server can not be shut down due to the specified reason.

Verify that user has the right permission to shutdown the server, check for any errors in the logfile. Contact support.

1013

Failed to determine IP address of host $1

Hostname may be incorrect

Verify hostname

1014

System service '$1' is shutting down.

Not an error. An info message is logged indicating a system service is being shut down.

Nothing to do.

1015

Service '$1' is started and ready to process requests.

Not an error. An info message is logged indicating a system service was started.

Nothing to do.

1200

Invalid meeting. Error: Field '$1' ($2) is invalid.

A field in the given meeting has invalid value.

Contact support.

1201

Invalid single meeting. Error: '$1' ($2) is invalid.

The given meeting is not a single meeting as expected.

Contact support.

1202

Invalid master meeting. Error: '$1' ($2) is invalid.

The given meeting is not a master meeting as expected.

Contact support.

1203

Invalid exception meeting. Error: '$1' ($2) is invalid.

The given meeting is not a exception meeting as expected.

Contact support.

1204

Too many TelePresence rooms.

Used by Exchange component in its email notification to inform meeting organizers that a meeting has more than two TelePresence rooms scheduled.

Remove extra TelePresence rooms from the meeting.

1205

Missing required number of TelePresence rooms.

Used by Exchange component in its email notification to inform meeting organizers that a meeting has less than two TelePresence rooms scheduled.

Add another TelePresence room to the meeting, or provide a dial number using the URL in the confirmation email.

1208

Recurring meeting instance: '$1'.

An error occurred while calculating the instances for a recurring meeting.

Contact support.

1209

Missing Conference ID and Bridge Number for the Multipoint meeting.

Used by Exchange component in its email notification to inform meeting organizers that a multipoint meeting is missing a conference id or bridge phone number. This is an unlikely case to happen.

Verify that MCU is configured properly, and at least one is available for multipoint meeting allocation.

1210

Missing required number of TelePresence rooms for the Multipoint meeting.

Used by Exchange component in its email notification to inform schedulers that a meeting has less number of rooms than what is required for a multipoint meeting. This is an unlikely case to happen.

Contact support.

1211

Selected TelePresence rooms are incompatible for multiroom conference. Contact help desk.

Used by Exchange component in its email notification to inform schedulers that a meeting is scheduled with room(s) that can not support multipoint conference.

Check the version of TelePresence equipment of each room and verify that it is a version which can support multipoint meeting. Upgrade if necessary.

1212

Insufficient resources to setup multiroom conference. Contact help desk.

Used by Exchange component in its email notification to inform schedulers that there is no available MCU for a multipoint meeting.

Verify that MCU is configured properly, and at least one is available for multipoint meeting allocation. Add a new MCU if necessary, or reschedule the meeting to a different time.

1213

Resources not setup to support multiroom conference. Contact help desk.

Used by Exchange component in its email notification to inform schedulers that there is no MCU configured for a multipoint meeting.

Verify that MCU is configured properly, and at least one is available for multipoint meeting allocation. Add a new MCU if necessary.

1214

Scheduler does not have enough privileges to setup this TelePresence meeting. Contact help desk.

Used by Exchange component in its email notification to inform schedulers that they don't have enough privilege for scheduling a multipoint meeting.

Verify that the scheduler has been assigned with the required user privilege. Add the scheduler to the user group that has the required privilege if necessary.

1215

Resource allocation error. $1

There is not enough resource available to migrate all meetings from one MCU to another MCU.

Verify that the target MCU has the proper configuration and that it is available.

1216

Meeting migration error. $1

An error occurred when attempting to migrate meetings from one MCU to another MCU

Check the error message in the logfile. Contact support.

1222

Failed to load/parse time zone map file '$1'. Error: $2.

The time zone map file maps a user calendaring time zone (from either Exchange or Domino) to a system time zone. The time zone map file is timezonemap.xml under /usr/local/ctis/config. The error would indicate the actual message in the Error portion of the message.

An internal error. Something has occurred during system installation or upgrade. Contact support.

1223

Unknown time zone target '$1'.

The time zone map file maps a user calendaring time zone (from either Exchange or Domino) to a system time zone. The time zone map file is timezonemap.xml under /usr/local/ctis/config. The error is indicating that a system time zone in the mapping is wrong.

An internal error. Something has occurred during system installation or upgrade. Contact support.

1400

Fail to $1 concierge. Error: $2.

CTM fails to perform the given operation for a concierge. The detail error message is given.

Most likely real cause would be DB operation error. DB might be down. Contact support.

1401

This device has $1 future meetings scheduled. Please migrate the meetings to another device first and try again.

Selected MCU has some future meetings scheduled and therefore it can't be deleted.

Migrate the meetings from the MCU (to be deleted) to another MCU and try the deletion again.

1402

A device with hostname $1 already exists. Please use a different hostname and try again.

A device with the same hostname and/or IP address already exists, therefore it doesn't allow the addition of the new device.

Check the hostname configuration for any conflict. Correct it and try the addition again.

1403

Duplicate entry. $1 already exists.Please use a different name and try again.

A configuration entry with the same value already exists, therefore it doesn't allow the addition of the new entry.

Check the entry value uniqueness to make sure it does not have any conflict with any existing configuration. Correct it and try the addition again.

1601

Failed to authenticate. Check authentication parameters.

Self-explanatory.

Check user name and password and try again.

1602

Unsupported authentication type '$1'.

The authentication specified during configuration (eg: for LDAP against Directory Server) is not supported.

Contact support.

1603

Error during encryption: '$1'.

An error occurred while encrypting a string. The detail error message is given.

Contact support.

1604

Error during decryption: '$1'.

An error occurred while decrypting a string. The detail error message is given.

Contact support.

1605

Insufficient credential '$1'. Requires credential '$2'.

User does not have sufficient privilege to access an URL.

Obtain correct credential and try again.

1606

Access permitted to email ID '$1' only.

Only scheduler is permitted to access the URL given in the email notification. Any other user trying to log in will be rejected with this error.

Use scheduler's credential to log in.

1607

New password is too simple. New password should contain both mixed-case alphabetic and non-alphabetic characters. It should not base on common words found in dictionary.

Self-explanatory. Happened when user changes super user password.

Use better formed password and try again.

1608

Password was change successfully, but could not be saved for future upgrade.

Could not save new password to platformConfig.xml due to some internal error.

Contact support.

1609

Could not change password: current password does not match.

Users must enter the old password correctly before they are allowed to change to new password.

Enter the correct old password.

1611

Unable to find username '$1' in the directory

Incorrect username specified in login screen

Enter correct username

1612

Failed to authenticate.Check authentication parameters.Username:LHS of email address.Password:AD password

CTM superuser account credentials inside MS-Exchange are invalid

Enter correct username/password

1613

Failed to authenticate.Check authentication parameters.Username:short form of email address.Password:Internet password.

CTM superuser account credentials inside IBM-Domino are invalid

Enter correct username/password

1700

Unknown configuration component '$1'.

Configuration for the specified component does not exist.

Ensure that the first time configuration setup is done and all the values are properly specified.

1701

No parameter '$1' found under configuration component '$2'.

Specific configuration parameter for a component does not exist in stored configuration.

Ensure that the first time configuration setup is done and all the values are properly specified.

1702

Failed to set parameter '$1' to value '$2'. Error: '$3'.

CTM is unable to save the given parameter due to the given detail error message. This is likely to be caused by DB error.

Check DB component status using CLI command. Restart it if necessary. Restart Tomcat after DB is running.

1703

Failed to update schedule to rooms '$1'. Error: '$2'.

CTM fails to submit a schedule update request to the given rooms.

Check room equipment and try again.

1704

Failed to validate DN '$1'.

CTM fails to validate specified DB in LDAP directory

Check DN configuration.

1705

Failed to validate email '$1'. The specified email does not exist

Extra email address specified under custom settings is not valid

Correct email address in specified field

1901

Failed to authenticate the TB device:

Username/password does not match for Telepresence Equipment

1. Configure username/password in Unified CM for specified telepresence equipment.

2. Run Unified CM Discovery for SR to sync configured username/password.

1902

Failed to send message to the TB device:

Could not deliver updated calendar to Telepresence Equipment due to loss of connectivity

1. Verify if Telepresence equipment is registered with Unified CM.

2. If Telepresence Equipment is not registered inside, contact Cisco TAC

1903

No Communication link on TB:

Web Service on TelepresenceEquipment is not running

1. Use Telepresence Equipment Troubleshooting guide to ensure the webservice is running

1904

Failed to update the SSH username/password from DB into cache.

Failed to retrieve SSH username password from DB

1. Use trouble shooting section to verify database connectivity

2000

Data Access Error: $1.

General error in data access operations

Look into the specific error message. Based on the message, verify if database is running, verify using 'Test Connection' if Directory Server is running, troubleshoot the specific message.

2001

Metaschema Parsing Error: $1.

An error occurred while parsing metaschema file.

Ensure that the installation and first time configuration has completed successfully.

2002

Error loading Metaschema file: $1.

The metaschema file is not loaded.

Ensure that the installation and first time configuration has completed successfully. Ensure that the disk is not corrupted.

2003

Datastore '$1' not found in Metaschema file.

Datastore values are not proper in metaschema file.

Ensure that the installation and first time configuration has completed successfully.

2004

Error updating override metaschema file.

Unable to write the values specified in the FieldMapping tab to the metaschema file.

Ensure that the installation and first time configuration has completed successfully. Ensure that the values specified in the FieldMappings tab are valid.

2005

Data Access Initialization Error: $1.

An error occurred during data access plugins initialization.

Evaluate specific message and troubleshoot database, LDAP connectivity and first time setup.

2006

Error in object creation: $1.

An error occurred during object creation in the database.

Evaluate object to be created and troubleshoot based on specific message.

2007

Error during object write: $1.

An error occurred during object update in the database.

Evaluate object to be updated and troubleshoot based on specific message.

2008

Error during object delete: $1.

An error occurred during object deletion in the database.

Evaluate object to be deleted and troubleshoot based on specific message.

2009

Error during object get: $1.

An error occurred during object retrieval from the database.

Evaluate object to be retrieved and troubleshoot based on specific message.

2010

Specified object '$1' not found in '$2' datastore.

The specified object does not exist in the data store

Evaluate object to be retrieved and troubleshoot based on specific message.

2011

Invalid Parameter Specified: '$1'.

The specified parameter is not valid.

Contact support.

2012

Error in Data Purge.

Error in Data Purge.

Evaluate message and contact support.

2013

Error in Data Backup.

Error in Data Backup.

Evaluate message and contact support.

2014

Error in Data Restore.

Error in Data Restore.

Evaluate message and contact support.

2015

Error in DB Maintenance Operations.

Error during database maintenance operation (Backup/Restore/Purge)

This is an error which is not handled by the categories mentioned above. Evaluate specific message and contact support.

2016

Error returned by spawned process: $1.

Error returned by script spawned by the server Java process

Evaluate the specific message. Contact support if required.

2017

Error acquiring connection: $1.

Error in getting a connection from connection pool

Check connection type (DB/LDAP) and verify connectivity. If problem persists, may require server restart. Contact support.

2018

Error closing connection: $1.

Error in closing a connection from connection pool

This may not be severe, but needs to be monitored. Check connection type (DB/LDAP) and verify connectivity. If problem persists, may require server restart. Contact support.

2019

Error closing statement: $1.

Error in closing a JDBC SQL statement object.

This may not be severe, but needs to be monitored. Check if database is running.

2020

Error instantiating class: $1.

Error in using pluggable methods during data access operations

Ensure the installation and first time setup is properly completed. This may be resolved by server restart. Contact support before doing this.

2021

Error instantiating method '$1' for class: '$2'.

Error in using pluggable methods during data access operations

Ensure the installation and first time setup is properly completed. This may be resolved by server restart. Contact support before doing this.

2022

Error retrieving field '$1' for class: '$2'.

Error in using pluggable methods during data access operations

Ensure the installation and first time setup is properly completed. This may be resolved by server restart. Contact support before doing this.

2023

Error setting value for field '$1' for class: '$2'.

Error in using pluggable methods during data access operations

Ensure the installation and first time setup is properly completed. This may be resolved by server restart. Contact support before doing this.

2024

Specified object '$1' is already deleted.

An object specified to be deleted is already deleted.

This is a warning to be monitored. Contact support.

2025

Object handler not found for specified object: '$1'.

The object handler for data access operations is not found.

This is a fatal error. Contact support.

2027

Attribute '$1' was not retrieved.

The requested attribute is not found in the object, either because application does not retrieve all the attributes for the object or it does not use the correct attribute name.

This is a severe error, but need not be fatal. Contact support.

2301

Unknown object interface '$1'.

An object specified is not accessible anymore.

This is a severe error, but need not be fatal. Contact support.

2302

The parameter '$1' with value '$2' is not valid.

Specified value for a parameter is not valid.

Evaluate the parameter. If it is a configurable parameter, ensure proper value is specified.

2400

Failed to connect to call manager:

Failure in retrieving information from Unified CM.

1. Cisco AXL WebService should be in running state.

2401

Failed to authenticate into Unified CM:

No Digital certificate found in truststore

1. Upload updated Digital cert for Unified CM

2402

Failed to locate attached phone to TelePresence device:

No Phone configured on shared line with telepresence equipment

1. Configured shared line with IP Phone

2403

Failed to locate room information attached to TelePresence equipment:

Missing Room information for Telepresence Equipment

1. Configure Room information using steps specified in CTM Configuration guide

2404

Failed to send AXL Message to Unified CM:

Failure in sending information request to Unified CM.

1. Incorrect digital certificate is uploaded.

2. Incorrect credentials specified in Unified CM Application user

1. Fix the certificate.

2. Correct Unified CM AppUser credentials

2405

Failed to retrieve publisher and/or subscriber nodes:

Failure in discovering Unified CM Node information from DB.

1. Incompatible Unified CM version

2. Specified Node is not a Unified CM publisher

1. Use compatible Unified CM version.

2. Publisher node hostname should be used

2406

Failed to authenticate and register with CTI Manager:

Invalid credentials and/or hostname.

1. Incorrect Unified CM App User credentials

2. Incorrect publisher node hostname is specified

1. Correct App User credentials and publisher node configuration

2407

Failed to create CTI Adapter to Unified CM

Failure in authenticating and connecting with CTIManager

1. Verify Unified CM App User credentials

2. Verify CTIManager service is activated on the publisher node

2409

Failed to create or update TelePresence equipment information:

Failure in creating Telepresence Equipment in DB

1. Ensure DN is configured.

2411

CTI Manager on Unified CM is down.

Failure in creating provider instance

1. CTIManager is not running

2415

Failed to connect to RIS Manager.

Failure in retrieving ipaddress from Unified CM

1. SOAP Webservice for RIS should be running.

2. Check Unified CM AppUser has correct privileges

2418

Failed to get list of addresses from CTI Provider.

Unified CM CTI Provider in error state

Contact Cisco TAC for Unified CM issues

2419

Failed to retrieve IP Address for requested device.

Unified CM RIS webservice is not running

Active SOAP webservice

2420

Failed to discovery TelePresence equipment.

One of the Unified CM interface is down

Contact Cisco TAC for Unified CM issues

2422

Directory number is not configured.

Directory number is not configured.

Configure Directory number

2423

Incompatible Unified CM Configured. Please verify the supported Unified CM version inside Supported versions table.

Incompatible Unified CM version

Correct Unified CM version

2424

Failure inside scheduled maintenance operation

Execution of scheduled maintenance for Database or TelepresenceEquipment Discovery or Exchange sync or Calendar schedule push failed

Contact Cisco TAC for detailed investigation

2425

Failed to discover timezone information from Unified CM.

TimeZone information not configured or available in Unified CM

Contact Cisco TAC for Unified CM issues

2426

Failed to discover telepresence capability information from endpoints.

Failure in discovering capability information from Telepresence equipment endpoints. It is most likely due to an older version of the Telepresence equipment not having the support for capability information.

Check the version of Telepresence equipment, and upgrade to a later version if necessary.

2427

More than one IP Phone configured on shared DN with telepresence equipment.

There is more than one IP phones that share the same DN as the specified Telepresence equipment endpoint.

Remove extra IP Phones or assign them with new DN, such that the Telepresence equipment endpoint only has one IP phone sharing its DN.

2428

CTI Control is disabled for the IP Phone.

The specified Cisco IP Phone that is configured for the Telepresence equipment endpoint is not set with CTI control enabled.

Verify the IP phone configuration in Unified CM Admin, and configure it to allow CTI control.

2429

Failed to update time zone '$1'. Error: $2.

An internal server error.

Contact support.

2500

Failed to send message/event

ActiveMQ message system is failing

Contact Cisco TAC for detailed investigation

2601

Error getting detail for meeting ID '$1'.

CTM fails to extract meeting detail because either the scheduler ID or the meeting serial ID is null.

Check the URL that is provided in the email notification. The URL cannot be altered in anyway.

2602

Error getting certificate configuration file '$1'.

The cert-conf.xml does not exist under catalina.home. Something occurred during installation.

Contact support.

2603

Error loading certificate named: '$1'.

CTM fails to load the given certificate into the system.

Take corrective action according to the detail message and try again.

2604

Error deleting certificate unit '$1' of category '$2'. Error: '$3'.

CTM fails to delete the given cert.

Take corrective action according to the detail message and try again.

2605

Error $1 DHCP setting. CLI error code: $2.

CTM fails to enable/disable DHCP setting. Detail error message is given.

Take corrective action according to the detail message and try again.

2606

Error setting IP address and/or subnet mask. CLI error code: $1.

CTM fails to set new IP settings.

Take corrective action according to the detail message and try again.

2607

Error setting default gateway. CLI error code: $1.

CTM fails to change default gateway setting.

Take corrective action according to the detail message and try again.

2608

Error setting SNMP data. Command executed: '$1'. Error: '$2'.

CTM fails to execute SNMP setting script to set new SNMP setting.

Take corrective action according to the detail message and try again.

2609

Failed to '$1' SNMP service. Error: '$2'.

CTM fails to use ControlCenter to perform the given action on SNMP daemon.

Try to use CLI to activate/deactivate SNMP service. Contact support.

2610

Software upgrade already in progress.

Users attempt to start another software upgrade while there is an upgrade going on. There can be only one upgrade at any time.

Wait until the current upgrade completes and try again.

2611

Failed to upgrade software. Error: '$1'.

CTM fails to upgrade software due to the given error message.

Take corrective action according to the detail message and try again.

2612

System is restarting. Try again later.

The system is being restarted. Users are disallowed to log in while the system is being restarted.

Wait a few minutes and try to log in again.

2613

Webapp home directory '$1' does not exist.

The webapp directory does not exist. Something has occurred during installation.

Users should not see this error. Contact support.

2614

System is being maintained. Try again later.

Either a database restore or system restart is in progress. Users are prevented from logging in, and this error is shown on the log-in page.

Wait a few minutes and try to log in again.

2615

Cannot delete own role mapping: '$1'.

Users whose role is Administrator is trying to delete his own role mapping on the Access Management screen.

Users cannot delete his own role mapping. Super User can delete anything.

2616

FQDN '$1' is not a group FQDN.

Users enter an invalid user FQDN in the Role to LDAP mapping dialog box (during Access Management configuration).

Check the entered FQDN and try again.

2617

Failed to create remote account '$1'. Error: '$2'. Account name must contain only lower case alphabetic characters. Upper case, digit, and special characters are not allowed.

CTM fails to create the requested remote account. Detail error message is given.

Take corrective action according to the detail message and try again.

2618

Cannot view more than one meeting in the same session. Log out of session on meeting '$1' first.

Viewing more than one meeting in the same UI session is not allowed.

Log out of the session on the other meeting first and try again.

2619

Server is being restarted. Try again later.

An attempt to view the UI while server is being restarted.

Wait a few minutes and try to log in again.

2620

Email ID '$1' specified in URL is different than ID '$2' found in database.

The URL that is used to view a meeting contains a different user ID than the meeting scheduler. This request will be blocked with this error shown in the UI.

Make sure the user uses the exact same URL that is provided in the CTS-MAN generated email. After verifying the URL, if it still fails, contact support. In CTS-MAN 1.1, this could occur when switching between versions.

2621

Missing required URL parameter '$1'. Contact Administrator.

The URL that is used to view a meeting is missing a required parameter to retrieve the meeting information.

Make sure the user uses the exact same URL that is provided in the CTS-MAN generated email. After verifying the URL, if it still fails, contact support.

2622

Error setting primary DNS. CLI error code: $1

Failed to set requested primary DNS on the platform, CLI returned an error

Verify DNS name again

2623

Error setting secondary DNS. CLI error code: $1

Failed to set requested secondary DNS on the platform, CLI returned an error

Verify DNS name again

2624

Duplicate entry. Role '$1' for this Group FQDN already exists

Duplicate name specified for a rile.

Verify the role name again

2626

Error setting Domain. CLI error code: $1.

Failed to set the domain name

Refer to Domino installation and verify domain name

2627

Error deleting the primary DNS. CLI error code: $1

Failed to delete the DNS name, CLI returned an error

Contact Cisco TAC for detailed investigation.

2628

Error deleting the secondary DNS. CLI error code: $1

Failed to delete the DNS name, CLI returned an error

Contact Cisco TAC for detailed investigation.

2629

Invalid certificate type named: '$1'.Valid Certificate file extensions .cer and .der.

Incorrect cert file is used

Self explanatory

2803

Error during configuration policy delete: $1.

Failed to delete configuration policy

Contact Cisco TAC for detailed investigation.

2808

A configuration policy with this policy name $1 already exists.

Duplicate name specified for a policy

Self explanatory

3001

Unable to start adapter '$1'. Error: '$2'.

CTM fails to start one of its client adapters. The adapter name and detail message is given.

This is a fatal error. Contact support.

3002

Failed to sync '$1'.

CTM fails to perform synchronization for the given Exchange room or database.

Using the Exchange or Domino configuration UI, try to manually start the sync for the given room or database. If unsuccessful then contact support.

3003

Failed to process meeting '$1'.

CTM fails to process a meeting with given subject or system ID.

Update the meeting using the calendaring tool (Outlook or Lotus Notes) to see if the meeting can be processed again. Contact support.

3004

Failed to update room '$1'.

CTM fails to update some information on the given room.

Contact support.

3005

Failed to process '$1' event for room '$2'.

CTM fails to process a specific room event.

Contact support.

3100

Unexpected Error: $1.

CTM Exchange Adapter has encountered internal error.

Contact Cisco TAC for detailed investigation.

3101

Missing Config Param Error: $1.

Required configuration parameter is missing.

Specify the required parameter and retry operation.

3102

Exchange Connection Error: $1.

Connection to Exchange could not be established.

Make sure specified connection are correct, Exchange host is reachable.

3103

Param Format Error: $1. Given value:($2).

Specified Exchange Adapter parameter format is incorrect.

Correct the parameter based on message and retry operation.

3105

Room Subscription Error: Room:($1). Message:($2)

Room account does not exist in AD/Exchange, CTM account does not have proper permission to read room calendar, connection to Exchange might be down, room account on Exchange modified.

Setup room account in AD/Exchange, give CTM account read access to room's calendar, wait for CTM to regain connection to Exchange else restart CTM.

3106

Room Unsubscription Error: Room:($1). Message:($2)

Connection to Exchange might be down, room account on Exchange modified.

Wait for CTM to regain connection to Exchange else restart CTM.

3109

Room Renewal Error: Room:($1). Message:($2)

Connection to Exchange might be down, room account on Exchange modified.

Wait for CTM to regain connection to Exchange else restart CTM.

3111

Lock Error: Cannot acquire lock on element:($1).

Error in resolving deadlocks in server application threads.

This is a severe error, but need not be fatal. Contact support.

3112

Mailbox Error: Error during mailbox size computation:($1).

CTM is unable to read mailbox quota.

Specify specific mailbox quota for CTM account in Directory Server.

3113

Mailbox Quota Error: Cleanup account on Exchange. Quota:($1) Current size:($2).

Super user mailbox has filled up to the quota.

Cleanup super user account on Exchange.

3114

Invalid Domain Name

The specified domain name is invalid. Users would see this error during Test Connection of Exchange settings.

Correct the domain name and try Test Connection again.

3115

Invalid User Name. User name cannot contain space(s).

Invalid User Name. Exchange user name cannot contain space(s).

Correct the user name.

3116

Exchange connection succeeded

Not an error condition.

3501

Email cannot be sent for meeting in validation state '$1'.

Internal error.

Contact support.

3601

Room display segments information is missing.

Room does not have any display segment information.

This is a severe error, but it should never happen. Contact support.

3800

MCU is not reachable:

CTM is unable to communicate with the MCU

Check for any connectivity issue and check the MCU status.

3801

Failed to authenticate with MCU:

MCU is unable to find CTM hostname/IP address or unable to authenticate the CTM, therefore it will not process any request from this CTM.

Verify that the MCU is configured properly with the correct CTM settings.

3802

An error occurred at MCU:

MCU has reported an error. The error detail is given in the message.

Take corrective action according to the detail message and try again.

3803

MCU failed to authenticate:

CTM is unable to authenticate the MCU, therefore it will not process any request from this MCU

Verify that the authentication information that are entered in CTM and MCU match.

3804

HostName or IP Address not found for MCU:

MCU is unknown to CTM, therefore it will not process any request from this MCU

Verify that this MCU is configured properly in CTM.

4000

Domino Connection Error: $1.

Failed to connect to Domino server

Verify IP connectivity to Domino server, DIIOP task should be running

4001

Domino connection was established, but couldn't open the specified Domino resource database

Domino resource may be inaccessible for various reasons.

Contact Cisco TAC for detailed investigation.

4002

Domino Domain value '$1' specified is not correct.

Domino domain value is incorrect

Verify if Domino domain name is correct or has changed