Release 9.0.2
Part Number A95454-01
 Home |
 Solution Area |
 Contents |
 Index |
| Oracle9iAS Unified Messaging Administrator's Guide Release 9.0.2 Part Number A95454-01 |
|
This chapter includes component-specific errors, listed in numerical order. The error codes are divided into the following groups:
Error messages may appear in any part of Oracle9iAS Unified Messaging. Users may see them in the end-user interface, and administrators may see them in the administrative tools and process logs.
Sometimes, more than one error is displayed. A list of error messages is called an error stack. The bottommost error in the stack is typically the cause of the error.
The following is a list of IMAP4 and POP3 error messages:
Cause: Invalid user name or password used for LOGIN command.
Action: Check the user name, password and try again.
Cause: Used all your allowed login attempts
Action: Check the user name and password, then retry in a new session.
Cause: IMAP/POP session ended either by LOGOUT/QUIT command or because of some other fatal server error like unable to read or write to client connection anymore.
Action: Session end by LOGOUT/QUIT command is normal. If you suspect an abnormal connection termination, check for other errors in this error chain in server log file.
Cause: Successful login via authenticate command
Action: None
Cause: Unsuccessful login attempt via authenticate command
Action: Check the user credentials and try again.
Cause: Possibly a non-existent folder name was used.
Action: Correct the folder name and try again. If folder name is correct, check and resolve any other database errors in this error chain.
Cause: This could be due to an OCI error.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_FOLDER_API is loaded. Check and resolve any other database errors in this error chain.
Cause: This could be due to an OCI error.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_FOLDER_API is loaded. Check and resolve any other database errors in this error chain.
Cause: Server unable to create OCI connection pool.
Action: Make sure database is up and configured correctly in Oracle Internet Directory.
Cause: Successful connections to the database
Action: None
Cause: Database related error
Action: Check for OCI error in this error chain
Cause: Your session was idle for too long
Action: Send noop or any other command before timeout.
Cause: No more free memory is available to server.
Action: Reduce the load on server by reducing any of following: threads, max. clients, OCI sessions or Oracle Internet Directory connections. Make sure enough free memory is available for server on your system.
Cause: Internal error
Action: Contact customer support
Cause: This could be due to an OCI error.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_FOLDER_API is loaded. Check and resolve any other database errors in this error chain.
Cause: There are no more free sessions available in OCI connection pool.
Action: This may be a temporary error due to a spike in load. You may need to reevaluate your system to reduce the number of clients connecting to this database, increase the number of sessions in pool or tune the system in general to get faster response.
Cause: Database error.
Action: Check the OCI errors in this error chain
Cause: Trying to rename a non-existent folder, or the new name is already in use or not allowed.
Action: Make sure folder with old name exists and new name is not already in use or contains restricted characters. Check for any other database errors in this error chain.
Cause: This could be due to an OCI error.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_FOLDER_API is loaded. Check and resolve any other database errors in this error chain.
Cause: This could be due to an OCI error.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_FOLDER_API is loaded. Check and resolve any other database errors in this error chain.
Cause:
Action: Check the folder name you are trying to create. Also check for any OCI errors in this error chain.
Cause: This could be due to an OCI error.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_FOLDER_API is loaded. Check and resolve any other database errors in this error chain.
Cause: Syntax error in flag list for Store command.
Action: Correct the syntax for flag list.
Cause: Possible causes are:
Action: Make sure you are looking for the right folder and is spelled correctly. If it is a shared folder, check its configuration and permissions in Oracle Internet Directory. Check and resolve any other database errors in this error chain.
Cause: Database error.
Action: Check and resolve database errors in this chain.
Cause: Possible causes are:
Action: Check the name of the folder and make sure you are the owner of the shared folder you are trying to delete. Check for database errors in this error chain.
Cause: Possible causes are:
Action: Make sure you are the owner of shared folder or retry with a different name.
Cause: Database error.
Action: Check the database and Oracle Internet Directory error logs.
Cause: This could be due to an OCI error.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_FOLDER_API is loaded. Check and resolve any other database errors in this error chain.
Cause: This could be due to an OCI error.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_FOLDER_API is loaded. Check and resolve any other database errors in this error chain.
Cause: One of the required message attributes is missing in database.
Action: Make sure all required packages are loaded in the database correctly.
The following is a list of SMTP server error messages:
Cause: The process is consuming too much memory.
Action: Reduce the number of threads running and restart the process.
Cause: The process is consuming too much memory.
Action: Reduce the number of threads running and restart the process.
Cause: There are too many threads in the process.
Action: Reduce the number of threads and restart the server. If the problem persists, contact technical support.
Cause: The Oracle Internet Directory server may be down.
Action: Restart the Oracle Internet Directory server. If the problem still exists contact technical support.
Cause: The Oracle Internet Directory server may be down.
Action: Restart the Oracle Internet Directory server. If the problem still exists contact technical support.
Cause: The Oracle Internet Directory server may be down.
Action: Restart the Oracle Internet Directory server. If the problem still exists contact technical support.
Cause: The address resolution for the recipient resulted in a loop.
Action: Make sure the data present in the Oracle Internet Directory server does not introduce any loops for the recipient. Check if auto forward attribute for the recipient introduces a chain ending with original recipient.
Cause: Mandatory attribute orclobjectid is missing in Oracle Internet Directory.
Action: Populate correct value for the user in Oracle Internet Directory.
Action: Make sure all required packages are loaded in the database correctly. Check if ES_MESSAGE_API is loaded.
Action: Make sure all required packages are loaded in the database correctly. Check if ES_OT_API is loaded.
Cause: The user rule resulted in rejection of the message.
Action: None.
Cause: Auto reject is set in Oracle Internet Directory entry for the recipient.
Cause: There may be OCI errors.
Action: Make sure all required packages are loaded in the database correctly. Check if ES_MESSAGE_API is loaded.
Action: Check the log for exact reason for failure prior to this message, and see any correction for the user's setup is needed.
Cause: Error in recovery processing.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_QUEUE_API is loaded.
Cause: Error in recovery processing.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_QUEUE_API is loaded.
Action: Populate orclmailsmtpexternalfilterprocess with path for virus scanner executable if virus scanning is enabled.
Cause: Unable to authenticate user in Oracle Internet Directory.
Action: Check user name and password to see if they are correct.
Cause: Unable to get next message ID from database.
Action: Check if the schema is installed and if the package is valid.
Cause: Unable to insert envelope information into database.
Action: Check if the schema is installed and if the package is valid.
Cause: Unable to insert recipient information into database.
Action: Check if the schema is installed and if the package is valid.
Cause: Unable to insert the message into a queue.
Action: Check if the schema is installed and if the package is valid.
Cause: Unable to insert message into database.
Action: Check the OCI error and ORACLE error.
Cause: Message may be in a loop by checking the Received: headers.
Possible causes: Loop in address rewriting rules; Auto-forward between addresses;.forward set up by UNIX mail senders.
Action: Check the rewriting rules and auto-forward setup and notify the sender.
Cause: Unable to read from client.
Action: Check network connections.
Cause: DNS server failed to verify that the IP address of the SMTP client is correct.
Cause: DNS server failed to verify that the host is a valid internet host.
Cause: The sender is either in the list of rejected senders or rejected domains.
Cause: This could be due to either relay is not allowed for the non-local recipient's domain OR the non-local recipient is in the list of rejected recipients.
Cause: This could be due to OCI errors.
Cause: This could be due to OCI errors.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_MESSAGE_API is loaded.
Cause: This could be due to OCI errors.
Action: Make sure all required packages are loaded in the database correctly. In particular, check if ES_MESSAGE_API is loaded.
The following is a list of housekeeping error messages:
Cause: An RDBMS error prevented house keeper from successfully performing expiration.
Action: Correct the generic RDBMS error and try running house keeper again.
Cause: An RDBMS error prevented house keeper from successfully performing pruning.
Action: Correct the generic RDBMS error and try running house keeper again.
Cause: An RDBMS error prevented house keeper from successfully performing pruning.
Action: Correct the generic RDBMS error and try running house keeper again.
Cause: An RDBMS error prevented house keeper from successfully performing collection.
Action: Correct the generic RDBMS error and try running house keeper again.
Cause: Calendar component is not installed, attempt to perform Calendar garbage collection failed.
Action: If Calendar component is not used, ignore this error. Otherwise re-install Calendar component.
Cause: An RDBMS error prevented house keeper from successfully performing Calendar cleanup.
Action: Correct the generic RDBMS error and try running house keeper again.
Cause: An RDBMS error prevented house keeper from successfully performing tertiary storage.
Action: Correct the generic RDBMS error and try running house keeper again.
The following is a list of list server error messages:
Cause: The cause for this error is available in the error message itself.
Action: Look at the oerr error for the error specified in the error message.
Cause: The Oracle Internet Directory server is down or has stopped responding or is listening on a different port.
Action: Restart the Oracle Internet Directory server if it is not running. Otherwise, restart the list server and specify the correct host name and port number of the Oracle Internet Directory server.
Cause: Either the database or the Oracle Internet Directory server is not running or has stopped responding.
Action: Restart the database and Oracle Internet Directory server. If they are running, then restart the list server.
Cause: An Oracle Internet Directory error occurred while trying to process a command for the user.
Action: Check if the user entry on the Oracle Internet Directory server is still valid.
The following is a list of Thin Client error messages:
Cause: WebMail was unable to add the attachments.
Action: Try again.
Cause: The user did not specific a folder name.
Action: Enter a folder name.
Cause: WebMail was unable to create the folder.
Action: Try again.
Cause: The user specified a folder name that is being used by another folder.
Action: Name the folder with a new name or put the folder in a different location.
Cause: WebMail could not create a new message object.
Action: Try creating a message again.
Cause: User did not specify a valid e-mail address in the To field.
Action: Try again and specify a valid e-mail address.
Cause: WebMail could not create a new message object.
Action: Try creating a message again.
Cause: WebMail experienced a problem when removing the attachment.
Action: Contact your system administrator.
Cause: WebMail attachment indices are misaligned.
Action: Recreate the message.
Cause: The user did not select messages for deletion.
Action: Select the message for deletion.
Cause: The message does not exist.
Action: Contact your system administrator.
Cause: This is a problem with the voice mail messages in the folder.
Action: Contact your system administrator.
Cause: The user did not select a message before selecting Forward.
Action: Select a message before selecting Forward.
Cause: Multiple messages were selected for forwarding.
Action: Select one message at a time for forwarding.
Cause: The message selected could not be forwarded.
Action: Try selecting another message, if that does not work, contact your system administrator.
Cause: The selected message could not be processed for forwarding.
Action: Try again or contact your system administrator.
Cause: The destination folder selected does not exist.
Action: Select another destination folder.
Cause: The user did not select a message before selecting Move.
Action: Select a message before selecting Move.
Cause: WebMail could not process the move request.
Action: Try again or contact your system administrator.
Cause: No messages exist before of after the current message.
Action: Try another folder.
Cause: WebMail could not open the next message.
Action: Try again or contact your system administrator.
Cause: No messages exist before of after the current message.
Action: Try another folder.
Cause: WebMail could not open the previous message.
Action: Try again or contact your system administrator.
Cause: The folder is not accessible.
Action: Check the shared permission or contact your system administrator.
Cause: There is no such folder in the account.
Action: Contact your system administrator.
Cause: WebMail experienced problems opening the folder.
Action: Contact your system administrator.
Cause: Possibly a network problem.
Action: Contact your system administrator.
Cause: Internal error.
Action: Contact your system administrator.
Cause: The message may have been deleted, but the browser is looking a cached or old pages.
Action: Refresh the message list and try again.
Cause: The user did not check any messages before selecting Reply.
Action: Select a message before selecting Reply.
Cause: The user selected multiple messages for reply.
Action: Select only one message at a time.
Cause: WebMail could not process the message for reply.
Action: Try again or contact your system administrator.
Cause: Internal error
Action: Contact your system administrator
Cause: Internal error
Action: Contact your system administrator.
Cause: The user did not select a folder in the folder list before selecting Edit.
Action: Select a folder from the folder list.
Cause: The folder selected is not available.
Action: Verify that the folder exists, or contact you system administrator.
Cause: Internal Error
Action: Contact your system administrator.
Cause: The user tried to rename the inbox.
Action: None, the inbox cannot be renamed.
Cause: The user did not specify a name for the folder.
Action: Specify a name for the folder.
Cause: Internal error
Action: Contact your stem administrator.
Cause: Internal error
Action: Contact your stem administrator.
Cause: Internal error
Action: Contact your stem administrator.
Cause: Internal error
Action: Contact your stem administrator.
Cause: The session has timed out.
Action: Contact your stem administrator.
The following is a list of telephony error messages:
Cause: The Oracle Internet Directory server is not accessible.
Action: Make sure the Oracle Internet Directory server is accessible.
Cause: The Oracle Internet Directory server is not accessible.
Action: Make sure the Oracle Internet Directory server is accessible.
Cause: Unknown error.
Action: If the problem persists, reboot the system and report the problem.
Cause: Attempting to reinitialize the application after an unknown error failed.
Action: Reboot the system and report the problem.
Cause: The application thread is shutting down due to failed reinitialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: The application has attempted thread-specific cleanup and will shutdown due to failed initialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: Oracle Internet Directory is down or inaccessible.
Action: None. Application will automatically retry connection
Cause: Oracle9iAS Unified Messaging is answering calls for users who do not have Oracle Internet Directory entries or who have incorrect Oracle Internet Directory entries.
Action: If the user should be on the system, make sure that the user's VPIM user object has a correct VPIM mail address. If the user should not be on the system, then configure the PBX not to forward that user's calls to Oracle9iAS Unified Messaging.
Cause: The application is attempting to queue a message and the message queue location is undefined in Oracle Internet Directory.
Action: Set the message queue location in the appropriate process or instance objects in Oracle Internet Directory.
Cause: Error outputting a message to the recovery queue.
Action: Check disk space and permissions on the queue directory.
Cause: Application error condition.
Action: Restart the machine, check disk space, and report the problem if it persists.
Cause: The mail store database is down or inaccessible or there is another problem with message sending.
Action: Make sure the recovery application is running. It will send the message when the database is accessible again. Check database.
Cause: Oracle Internet Directory process or instance settings which are required for process startup are missing.
Action: Make sure that all Oracle Internet Directory properties required for the application are set in the appropriate process or instance objects.
Cause: The code type stored in a user or greeting Oracle Internet Directory object is incorrectly formatted. It may have been altered.
Action: Correct the formatting of the coder type, and make sure that the default coder types are valid ones.
Cause: The installation default message localization description string (XML) is poorly formed.
Action: Correct the message localization description string.
Cause: The installation default menu item bindings description string (XML) is poorly formed.
Action: Correct the menu item bindings description string.
Cause: Oracle Internet Directory error while looking up the installation default message localization description string or the installation default menu item bindings description string.
Action: Make sure that a default menu object and a default prompts object exist in Oracle Internet Directory as immediate children of the installation container in Oracle Internet Directory. The default attributes of both objects should be set to true.
Cause: An unexpected error condition with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: The CT Server may be down.
Action: Make sure that the CT Server is starting up. Once the server starts up, the application will recover.
Cause: The current configuration of the process instance being refreshed is invalid. A setting made since the process instance's last startup is wrong.
Action: Correct the process instances in the Oracle Internet Directory settings.
Cause: IT Media or CT Media API error. This message should never occur.
Action: Check disk space, reboot the system, and report the problem if it persists.
Cause: Internal application coding error. This message should never occur.
Action: Edit the menu item bindings configuration string to disable the menu item whose handler is missing.
Cause: The ASI for the attendant application is not defined in the attendant Oracle Internet Directory object to which this process instance's Oracle Internet Directory configuration points.
Action: Define the attendant ASI in the appropriate Oracle Internet Directory object.
Cause: There was a problem releasing the call to the attendant application. The attendant application is not running or not enough threads are running.
Action: Make sure the attendant application is running.
+ requestor.getAttendantAsi()
Cause: There was a problem reconfiguring the group for forwarding to the attendant application. The UMMediaServicesProfile could be configured incorrectly.
Action: Check UMMediaServicesProfile.
Cause: A fax tone was detected for a call for which call details were unavailable.
Action: Make sure call details are available. Also make sure that fax tone settings in CT Media are reasonable.
Cause: There was an unexpected problem performing a resource operation such as playing a message or detecting signals.
Action: Consult CT Media documentation for the meaning of the error code, if one is logged. Make sure that all sound files are installed. Make sure that disk space is available. Restart machine if all else fails.
Cause: There was a problem releasing the call to the recording or retrieval application. The recording or retrieval application is not running or not enough threads are running.
Action: Make sure the recording or retrieval application is running.
Cause: There was a problem reconfiguring the group for forwarding to the recording or retrieval application. The UMMediaServicesProfile may be configured incorrectly.
Action: Check the UMMediaServicesProfile.
Cause: The PBX connection type is missing or unrecognized, or, for SMDI connections, the SMDI monitor host, port, or timeout properties are missing.
Action: Correct all required PBX connection related properties in the appropriate Oracle Internet Directory process or instance object.
Cause: An unexpected error condition with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: The CT Server may be down.
Action: Make sure that the CT Server is starting up. Once the server starts up, the application will recover.
Cause: A well-formed XML string has an integer parameter value which cannot be parsed as an integer.
Action: From the log files, determine which XML string is causing the problem and correct it.
Cause: A localized message description string is not correctly formed.
Action: From the log files determine which string is not correctly formed and correct it.
Cause: Unexpected error.
Action: Determine from the logs which XML string is being parsed, and make sure the XML string is formed correctly.
Cause: Message should never occur.
Action: Report the problem.
Cause: The Oracle Internet Directory server is inaccessible.
Action: Make sure the Oracle Internet Directory server is accessible.
Cause: The Oracle Internet Directory server is inaccessible.
Action: Make sure the Oracle Internet Directory server is accessible.
Cause: Unknown error.
Action: If the problem persists, reboot the system and report the problem.
Cause: Attempting to reinitialize the application after an unknown error failed.
Action: Reboot the system and report the problem.
Cause: The application thread is shutting down due to failed reinitialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: The application has attempted thread-specific cleanup and will shutdown due to failed initialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: Oracle Internet Directory is down or inaccessible.
Action: None. Application will automatically retry connection.
Cause: Oracle9iAS Unified Messaging is answering calls for users who do not have Oracle Internet Directory entries or who have incorrect Oracle Internet Directory entries.
Action: If the user should be on the system, make sure that the user's VPIM user object has a correct VPIM mail address. If the user should not be on the system, then configure the PBX not to forward that user's calls to Oracle9iAS Unified Messaging.
Cause: The application is attempting to queue a message and the message queue location is undefined in Oracle Internet Directory.
Action: Set the message queue location in the appropriate process or instance objects in Oracle Internet Directory.
Cause: Error outputting a message to the recovery queue.
Action: Check disk space and permissions on the queue directory.
Cause: Application error condition.
Action: Restart the machine, check disk space, and report the problem if it persists.
Cause: The mail store database is down or inaccessible or there is another problem with message sending.
Action: Make sure the recovery application is running. It will send the message when the database is accessible again. Check database.
Cause: Oracle Internet Directory process or instance settings which are required for process startup are missing.
Action: Make sure that all Oracle Internet Directory properties required for the application are set in the appropriate process or instance objects.
Cause: The code type stored in a user or greeting object in Oracle Internet Directory is incorrectly formatted. It may have been altered.
Action: Correct the formatting of the coder type, and make sure that the default coder types are valid ones.
Cause: The installation default message localization description string (XML) is poorly formed.
Action: Correct the message localization description string.
Cause: The installation default menu item bindings description string (XML) is poorly formed.
Action: Correct the menu item bindings description string.
Cause: There was an Oracle Internet Directory error while looking up the installation default message localization description string or the installation default menu item bindings description string.
Action: Make sure that a default menu object and a default prompts object exist in Oracle Internet Directory. The immediate children of the installation container in Oracle Internet Directory. The default attributes of both objects should be set to true.
Cause: An unexpected error condition with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: The CT Server may be down.
Action: Make sure that the CT Server is starting up. Once the server starts up, the application will recover.
Cause: The current configuration of the process instance being refreshed is invalid. A setting made since the process instance's last startup is wrong.
Action: Correct the Oracle Internet Directory process instance settings.
Cause: IT Media or CT Media API error. This message should never occur.
Action: Check disk space, reboot the system, and report the problem if it persists.
Cause: Internal application coding error. This message should never occur.
Action: Edit the menu item bindings configuration string to disable the menu item whose handler is missing.
Cause: The ASI for the attendant application is not defined in the attendant Oracle Internet Directory object to which this process instance's Oracle Internet Directory configuration points.
Action: Define the attendant ASI in the appropriate Oracle Internet Directory object.
Cause: There was a problem releasing the call to the attendant application. The attendant application is not running or not enough threads are running.
Action: Make sure the attendant application is running.
Cause: There was a problem reconfiguring the group for hand off to the attendant application. The UMMediaServicesProfile profile is not configured correctly.
Action: Check UMMediaServicesProfile.
Cause: An unexpected error condition with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: The CT Server may be down.
Action: Make sure that the CT Server is starting up. Once the server starts up, the application will recover.
Cause: A well-formed XML string has an integer parameter value which cannot be parsed as an integer.
Action: Determine from the logs which XML string is causing the problem, and correct it.
Cause: A localized message description string is not formed correctly.
Action: Determine from the logs which string is not formed correctly, and correct it.
Cause: Unexpected error.
Action: Determine from the logs which XML string is being parsed, and make sure the XML string is well formed.
Cause: Message should never occur.
Action: Report the problem.
Cause: Oracle Internet Directory is down and no default domain is set in the environment.
Action: If the installation encompasses multiple domains, do nothing. If it is a single domain installation, set the default domain parameter in Oracle Internet Directory to be the name of the single domain.
Cause: The user who called in does not have voice mail access.
Action: If the user should have voice mail access, enable the user's voice mail access in Oracle Internet Directory.
Cause: A fax call was received.
Action: None.
Cause: There was a problem reconfiguring the group for hand off to the fax application. There may not be enough fax resources installed.
Action: If this problem is persistent, install more fax cards.
Cause: There was a problem delegating the call to the fax application. The fax application is not running or not enough threads are running.
Action: Make sure the fax application is running.
Cause: An unknown error condition.
Action: Report the problem if it persists.
Cause: CT Server corruption. This message should never occur.
Action: Check disk space and reboot the CT Server.
Cause: The user did not specify any message recipients.
Action: None.
Cause: Unexpected error condition or CT Server corruption.
Action: Check disk space and reboot the CT Server.
Cause: The message which is being replied to or forwarded has a sender whose text name is numeric, but not a phone number of a user in the system. The sender could have been removed from the system or could have an entirely numeric text name defined in Oracle Internet Directory.
Action: None
Cause: An error communicating with the database, or simultaneous deletion of the message being forwarded or replied to.
Action: Check database connection.
Cause: The ASI is not set in the fax process instance's Oracle Internet Directory object referenced in this process instance's object.
Action: Make sure the ASI is set in the appropriate fax process or instance object.
Cause: CT Media or IT Media API error.
Action: Check disk space and report the problem if it persists.
Cause: CT Media or IT Media API error.
Action: Check disk space and report the problem if it persists.
Cause: CT Media or IT Media API error, or an additional RTC has been defined in the CT Media application profile.
Action: Check disk space, correct the application if necessary, and report the problem if it persists.
Cause: The user's attendant extension cannot be found in Oracle Internet Directory.
Action: Make sure that the attendant extension is set in Oracle Internet Directory under one of the user's parent group profiles.
Cause: The telephone number field for a VPIM user is not set.
Action: Set the telephone number to the local telephone number of the VPIM user.
Cause: The user's telephone number is too long to be played.
Action: Shorten the user's telephone number. The length should be large enough to accommodate any phone number.
Cause: The Oracle Internet Directory server is inaccessible.
Action: Make sure the Oracle Internet Directory server is accessible.
Cause: The Oracle Internet Directory server is inaccessible.
Action: Make sure the Oracle Internet Directory server is accessible.
Cause: Unknown error.
Action: If the problem persists, reboot the system and report the problem.
Cause: Attempting to reinitialize the application after an unknown error failed.
Action: Reboot the system and report the problem.
Cause: The application thread is shutting down due to failed reinitialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: The application has attempted thread-specific cleanup and will shut down due to failed initialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: Oracle Internet Directory is down or inaccessible.
Action: None. Application will automatically retry connection.
Cause: Oracle9iAS Unified Messaging is answering calls for users who do not have Oracle Internet Directory entries or who have incorrect Oracle Internet Directory entries.
Action: If the user should be on the system, make sure that the user's VPIM user object has a correct VPIM mail address. If the user should not be on the system, then configure the PBX not to forward that user's calls to Oracle9iAS Unified Messaging.
Cause: The application is attempting to queue a message and the message queue location is undefined in Oracle Internet Directory.
Action: Set the message queue location in the appropriate process or instance objects in Oracle Internet Directory.
Cause: Error outputting a message to the recovery queue.
Action: Check disk space and permissions on the queue directory.
Cause: Application error condition.
Action: Restart the machine, check disk space, and report the problem if it persists.
Cause: The mail store database is down or inaccessible or there is another problem with message sending.
Action: Make sure the recovery application is running. It will send the message when the database is accessible again. Check database.
Cause: Oracle Internet Directory process or instance settings which are required for process startup are missing.
Action: Make sure that all Oracle Internet Directory properties required for the application are set in the appropriate process or instance objects.
Cause: The code type stored in a Oracle Internet Directory user or greeting object is incorrectly formatted. It may have been altered.
Action: Correct the formatting of the coder type, and make sure that the default coder types are valid ones.
Cause: The installation default message localization description string (XML) is poorly formed.
Action: Correct the message localization description string.
Cause: The installation default menu item bindings description string (XML) is poorly formed.
Action: Correct the menu item bindings description string.
Cause: Oracle Internet Directory error while looking up the installation default message localization description string or the installation default menu item bindings description string exist in Oracle Internet Directory as immediate children of the installation container in Oracle Internet Directory. The default attributes of both objects should be set to true.
Cause: An unexpected error condition with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: The CT Server may be down.
Action: Make sure that the CT Server is starting up. Once the server starts up, the application will recover.
Cause: The current configuration of the process instance being refreshed is invalid. A setting made since the process instance's last startup is wrong.
Action: Correct the process instance's Oracle Internet Directory settings.
Cause: IT Media or CT Media API error. This message should never occur.
Action: Check disk space, reboot the system, and report the problem if it persists.
Cause: Internal application coding error. This message should never occur.
Action: Edit the menu item bindings configuration string to disable the menu item whose handler is missing.
Cause: The ASI for the attendant application is not defined in the Oracle Internet Directory attendant object to which this process instance's Oracle Internet Directory configuration points.
Action: Define the attendant ASI in the appropriate Oracle Internet Directory object.
Cause: There was a problem releasing the call to the attendant application. The attendant application is not running or not enough threads are running.
Action: Make sure the attendant application is running.
Cause: There was a problem reconfiguring the group for hand off to the attendant application. The UMMediaServicesProfile profile could be configured incorrectly.
Action: Check the UMMediaServicesProfile.
Cause: An unexpected error condition with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: The CT Server may be down.
Action: Make sure that the CT Server is starting up. Once the server starts up, the application will recover.
Cause: A well-formed XML string has an integer parameter value which cannot be parsed as an integer.
Action: Determine from the logs which XML string is causing the problem, and correct it.
Cause: A localized message description string is not formed correctly.
Action: Determine from the logs which string is not formed correctly, and correct it.
Cause: Unexpected error.
Action: Determine from the logs which XML string is being parsed, and make sure the XML string is well formed.
Cause: Message should never occur.
Action: Report the problem.
Cause: An unexpected application condition.
Action: Check disk space, network connectivity, and access privileges.
Cause: An error communicating with Oracle Internet Directory. This error is non-fatal, but may reveal more serious Oracle Internet Directory communication problems.
Action: Try the operation again and see whether the condition recurs. Check if the Oracle Internet Directory server is down.
Cause: An error communicating with Oracle Internet Directory. This error is non-fatal, but may reveal more serious Oracle Internet Directory communication problems.
Action: Try the operation again and see whether the condition recurs. Check if the Oracle Internet Directory server is down.
Cause: Database down, disk space, or other error after a call has disconnected.
Action: Check disk space and see if database is reachable.
Cause: Database down or other error.
Action: Check if database is reachable.
Cause: Connection lost with Oracle Internet Directory.
Action: None. The application will automatically retry Oracle Internet Directory connection at the beginning of every call.
Cause: The user pressed only the pound key when asked to enter a mailbox number.
Action: None.
Cause: Third party bug was triggered and workaround is being attempted.
Action: None
Cause: Third party bug was triggered and workaround is being attempted.
Action: None
Cause: Loss of Oracle Internet Directory connection.
Action: None. The application will automatically retry Oracle Internet Directory connection at the beginning of every call.
Cause: Loss of Oracle Internet Directory connection.
Action: None. The application will automatically retry Oracle Internet Directory connection at the beginning of every call.
Cause: The user pressed only the pound key when prompted for a password.
Action: None.
Cause: Oracle Internet Directory error occurred while looking up a user.
Action: Check the user's Oracle Internet Directory settings.
Cause: The owner field of the Oracle9iAS Unified Messaging user object is not set.
Action: Set the owner field of the Oracle9iAS Unified Messaging user object to point to a mail user.
Cause: The owner field of the Oracle9iAS Unified Messaging user object is a DN which does not exist in the Oracle Internet Directory server.
Action: Correct the owner field of the Oracle9iAS Unified Messaging user object.
Cause: The mail user's orclMailStore attribute is not set.
Action: Set the mail user's orclMailStore attribute.
Cause: The mail user's targetdn attribute is not set or set incorrectly.
Action: Correct the targetdn to point to the mail user's corresponding public user.
Cause: The mail user's orclMailStore attribute is a DN which does not exist on the Oracle Internet Directory server.
Action: Correct the mail user's orclMailStore attribute.
Cause: The mail store orcldbdistinguishedname attribute is not set.
Action: Set the mail store orcldbdistinguishedname attribute.
Cause: The mail store orcldbdistinguishedname attribute is set to a DN which does not exist in the Oracle Internet Directory server.
Action: Correct the mail store object's orcldbdistinguishedname attribute.
Cause: The DBService orcldbglobalname attribute is not set in Oracle Internet Directory.
Action: Set the DBService orcldbglobalname attribute.
Cause: Loss of Oracle Internet Directory connection.
Action: None. The application will automatically retry Oracle Internet Directory connection at the beginning of every call.
Cause: Loss of Oracle Internet Directory connection.
Action: None. The application will automatically retry Oracle Internet Directory connection at the beginning of every call.
Cause: The VPIM mail user's object does not have the vpimmail ID set. As this attribute is required by the schema, a severe Oracle Internet Directory corruption has occurred.
Action: Contact Oracle Internet Directory server support.
Cause: The VPIM mail user's vpimmail ID was altered during the course of the telephone call. Most likely an Oracle Internet Directory corruption.
Action: Contact Oracle Internet Directory server support.
Cause: Unknown error authenticating user. Database could be down.
Action: Check database status.
Cause: E-mail server is missing the user's account.
Action: Make sure that user's account is properly set up in the e-mail server and Oracle Internet Directory.
Cause: The message for which a reply or forward is being composed has no message ID.
Action: None.
Cause: A failure to find items in the message header of a message to be forwarded or replied.
Action: None.
Cause: An error delegating to recording for a reply, forward, or new message composed within retrieval.
Action: Make sure that the recording application is running.
Cause: Unknown error while changing password.
Action: None.
Cause: The user's attendant extension cannot be found in Oracle Internet Directory.
Action: Make sure that the attendant extension is set in Oracle Internet Directory under one of the Oracle9iAS Unified Messaging user's parent Group Profiles.
Cause: The user's VPIM user object could not be found. There may have been an Oracle Internet Directory communication error or the owner attribute of the user object may have been incorrectly set.
Action: Make sure that the user's owner object is set to the dn of the mail user / VPIM user. Check that Oracle Internet Directory is available.
Cause: Database communication problem or disk space problem while setting the unread flag on a message.
Action: Make sure that the database is accessible and that there is sufficient disk space.
Cause: Database communication problem or disk space problem while deleting a message.
Action: Make sure that the database is accessible and that there is sufficient disk space.
Cause: Database communication problem or disk space problem while obtaining message header information.
Action: Make sure that the database is accessible and that there is sufficient disk space.
Cause: A data object in CT Media's container subsystem was externally deleted or there is an internal CT Media error.
Action: Check disk space. Reinstall CT Media if the problem persists.
Cause: The user's VPIM user object could not be found. There may have been an Oracle Internet Directory communication error or the owner attribute of the user object may have been incorrectly set.
Action: Make sure that the user's owner object is set to the dn of the mail user or VPIM user. Check that Oracle Internet Directory is available.
Cause: Disk space or internal CT Media error.
Action: Check disk space. Reinstall CT Media if the problem persists.
Cause: There was a database communication problem or disk space problem while obtaining message header information.
Action: Make sure that the database is accessible and that there is sufficient disk space.
Cause: There was an error accessing a just-recorded greeting or name. The greeting or name was removed, there is a disk space problem, or there was another CT Media error.
Action: Check disk space. Reboot the server if the problem persists.
Cause: There was an error storing a just recorded greeting or name in Oracle Internet Directory.
Action: Make sure that the Oracle Internet Directory server is accessible.
Cause: There was an error accessing Oracle Internet Directory to store a new password. Oracle Internet Directory maybe down or access control may be may not be configured correctly.
Action: Make sure that the Oracle Internet Directory server is accessible and that permissions are set correctly.
Cause: There was an error with the message playback due to a database connection problem.
Action: Check the database connection.
Cause: The Oracle Internet Directory server is inaccessible.
Action: Make sure the Oracle Internet Directory server is accessible.
Cause: The Oracle Internet Directory server is inaccessible.
Action: Make sure the Oracle Internet Directory server is accessible.
Cause: Unknown error.
Action: If the problem persists, reboot the system and report the problem.
Cause: Attempting to reinitialize the application after an unknown error failed.
Action: Reboot the system and report the problem.
Cause: The application thread is shutting down due to failed reinitialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: The application has attempted thread-specific cleanup and will shutdown due to failed initialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: Oracle Internet Directory is down or inaccessible.
Action: None. Application will automatically retry connection.
Cause: Oracle9iAS Unified Messaging is answering calls for users who do not have Oracle Internet Directory entries or who have incorrect Oracle Internet Directory entries.
Action: If the user should be on the system, make sure that the user's VPIM user object has a correct VPIM mail address. If the user should not be on the system, then configure the PBX not to forward that user's calls to Oracle9iAS Unified Messaging.
Cause: The application is attempting to queue a message and the message queue location is undefined in Oracle Internet Directory.
Action: Set the message queue location in the appropriate process or instance objects in Oracle Internet Directory.
Cause: Error outputting a message to the recovery queue.
Action: Check disk space and permissions on the queue directory.
Cause: Application error condition.
Action: Restart the machine, check disk space, and report the problem if it persists.
Cause: The mail store database is down or inaccessible or there is another problem with message sending.
Action: Make sure the recovery application is running. It will send the message when the database is accessible again. Check the database.
Cause: Oracle Internet Directory process or instance settings which are required for process startup are missing.
Action: Make sure that all Oracle Internet Directory properties required for the application are set in the appropriate process or instance objects.
Cause: The code type stored in a user or greeting Oracle Internet Directory object is incorrectly formatted. It may have been altered.
Action: Correct the formatting of the coder type, and make sure that the default coder types are valid ones.
Cause: The installation default message localization description string (XML) is poorly formed.
Action: Correct the message localization description string.
Cause: The installation default menu item bindings description string (XML) is poorly formed.
Action: Correct the menu item bindings description string
Cause: Oracle Internet Directory error while looking up the installation default message localization description string or the installation default menu item bindings description string.
Action: Make sure that a default menu object and a default prompts object exist in Oracle Internet Directory. The immediate children of the installation container in Oracle Internet Directory. The default attributes of both objects should be set to true.
Cause: An unexpected error condition with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: The CT Server may be down.
Action: Make sure that the CT Server is starting up. Once the server starts up, the application will recover.
Cause: The current configuration of the process instance being refreshed is invalid. A setting made since the process instance's last startup is wrong.
Action: Correct the process instance's Oracle Internet Directory settings.
Cause: An unexpected error condition with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: The CT Server may be down.
Action: Make sure that the CT Server is starting up. Once the server starts up, the application will recover.
Cause: A well-formed XML string has an integer parameter value which cannot be parsed as an integer.
Action: Determine from the logs which XML string is causing the problem, and correct it.
Cause: A localized message description string is not formed correctly.
Action: Determine from the logs which string is not formed correctly, and correct it.
Cause: Unexpected error.
Action: Determine from the logs which XML string is being parsed, and make sure the XML string is well formed.
Cause: Message should never occur.
Action: Report the problem.
Cause: The Oracle Internet Directory server is inaccessible.
Action: Make sure the Oracle Internet Directory server is accessible.
Cause: The Oracle Internet Directory server is inaccessible.
Action: Make sure the Oracle Internet Directory server is accessible.
Cause: Unknown error.
Action: If the problem persists, reboot the system and report the problem.
Cause: Attempting to reinitialize the application after an unknown error failed.
Action: Reboot the system and report the problem.
Cause: The application thread is shutting down due to failed reinitialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: The application has attempted thread-specific cleanup and will shut down due to failed initialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: Oracle Internet Directory is down or inaccessible.
Action: None. Application will automatically retry connection.
Cause: Unified Messaging is answering calls for users who do not have Oracle Internet Directory entries or who have incorrect Oracle Internet Directory entries.
Action: If the user should be on the system, make sure that the user's VPIM user object has a correct VPIM mail address. If the user should not be on the system, then configure the PBX not to forward that user calls to Oracle9iAS Unified Messaging.
Cause: The application is attempting to queue a message and the message queue location is undefined in Oracle Internet Directory.
Action: Set the message queue location in the appropriate process.
Cause: Error outputting a message to the recovery queue.
Action: Check disk space and permissions on the queue directory.
Cause: Application error condition.
Action: Restart the machine, check disk space, and report the problem if it persists.
Cause: The mail store database is down or inaccessible or there is another problem with message sending.
Action: Make sure the recovery application is running. It will send the message when the database is accessible again. Check the database.
Cause: Oracle Internet Directory process or instance settings which are required for process startup are missing.
Action: Make sure that all Oracle Internet Directory properties required for the application are set in the appropriate process or instance objects.
Cause: The code type stored in a user or greeting Oracle Internet Directory. The object is incorrectly formatted. It may have been altered.
Action: Correct the formatting of the coder type, and make sure that the default coder types are valid ones.
Cause: The installation default message localization description string (XML) is poorly formed.
Action: Correct the message localization description string.
Cause: The installation default menu item bindings description string (XML) is not formed correctly.
Action: Correct the menu item bindings description string.
Cause: Oracle Internet Directory error while looking up the installation default message localization description string or the installation default menu item bindings description string.
Action: Make sure that a default menu object and a default prompts object exist in Oracle Internet Directory as immediate children of the installation container in Oracle Internet Directory. The default attributes of both objects should be set to true.
Cause: An unexpected error condition with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: The CT Server may be down.
Action: Make sure that the CT Server is starting up. Once the server starts up, the application will recover.
Cause: The current configuration of the process instance being refreshed is invalid. A setting made since the process instance's last startup is wrong.
Action: Correct the Oracle Internet Directory process instance settings.
Cause: IT Media or CT Media API error. This message should never occur.
Action: Check disk space, reboot the system, and report the problem if it persists.
Cause: Internal application coding error. This message should never occur.
Action: Edit the menu item bindings configuration string to disable the menu item whose handler is missing.
Cause: The ASI for the attendant application is not defined in the attendant Oracle Internet Directory objects.
Action: Define the attendant ASI in the appropriate Oracle Internet Directory object.
Cause: There was a problem releasing the call to the attendant application. The attendant application is not running or not enough threads are running.
Action: Make sure the attendant application is running.
Cause: There was a problem reconfiguring the group for hand off to the attendant application. The UMMediaServicesProfile could be configured incorrectly.
Action: Check UMMediaServicesProfile.
Cause: An unexpected error condition with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: The CT Server may be down.
Action: Make sure that the CT Server is starting up. Once the server starts up, the application will recover.
Cause: A well-formed XML string has an integer parameter value which cannot be parsed as an integer.
Action: Determine from the logs which XML string is causing the problem, and correct it.
Cause: A localized message description string is formed incorrectly.
Action: Determine from the logs which string is formed incorrectly, and correct it.
Cause: Unexpected error.
Action: Determine from the logs which XML string is being parsed, and make sure the XML string is well formed.
Cause: Message should never occur.
Action: Report the problem.
Cause: Call detail information is unavailable.
Action: Make sure that the SMDI Monitor, if one exists, is running, and that the PBX integration settings in Oracle Internet Directory are correct.
Cause: Oracle Internet Directory is down and no default domain is set in the environment.
Action: If the installation encompasses multiple domains, do nothing. If it is a single domain installation, set the default domain parameter in Oracle Internet Directory to be the name of the single domain.
Cause: The user to whom a fax is being sent has fax-in access disabled.
Action: If the user should have fax-in access enabled, then enable it.
Cause: An error during fax reception.
Action: Check disk space, and reinstall CT Media if problems persist.
Cause: The user did not specify any message recipients.
Action: None.
Cause: CT Media or IT Media API error.
Action: Check disk space and report the problem if it persists.
Cause: An unexpected error condition with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: The CT Server may be down.
Action: Make sure that the CT Server is starting up. Once the server starts up, the application will recover.
Cause: The class location URL is not set in Oracle Internet Directory.
Action: Set the class location in Oracle Internet Directory.
Cause: Insufficient disk space or file system privileges.
Action: Check disk space and privileges.
Cause: The SMDI Monitor or CT Media MWI session service is unavailable.
Action: Verify that Oracle Internet Directory settings of PBX properties are correct. Verify that the SMDI Monitor, if any, is running. The MWIService will automatically reestablish connection.
Cause: The PBX connection type is missing or unrecognized, or the SMDI Monitor host, port, or timeout properties are missing.
Action: Correct all required PBX connection related properties in the appropriate process or instance Oracle Internet Directory object.
Cause: The Oracle JDBC classes are not correctly installed.
Action: Reinstall the Oracle JDBC classes.
Cause: The advanced queue for MWI does not exist, or is unavailable.
Action: Make sure the queue is installed and available.
Cause: The database is unavailable or inaccessible.
Action: Make sure the database is running and is accessible.
Cause: An Oracle Internet Directory server connection or authentication error occurred
Action: Make sure that the Oracle Internet Directory server is running. Reset authentication credentials if necessary.
Cause: An unknown error.
Action: None. Reconnection will be attempted.
Cause: An error establishing a connection after an unknown error.
Action: None. Reconnection will be attempted every 60 seconds.
Cause: The class oracle.AQ.AQOracleDriver cannot be found.
Action: Make sure that Oracle AQ classes are installed.
Cause: A RMI registry could not be located at the host and port number of the RMI URL set in Oracle Internet Directory.
Action: Make sure that an rmiregistry is running at the host and port number of the RMI URL set in Oracle Internet Directory.
Cause: The URL of the MWIService set in Oracle Internet Directory under the MWI service process or instance object is not formed correctly.
Action: Correct the MWIService URL.
Cause: The MWIService is not registered at the expected URL.
Action: Make sure that an MWIService is running at the location set in Oracle Internet Directory under the MWIService process or instance object.
Cause: Cannot create QueueTable. During installation, queue table creation did not go through
correctly. Or these queue connection parameters were changed in Oracle Internet Directory.
Action: Check for the Queuetable name listed in Oracle Internet Directory against the database.
Cause: The queue connection did not happen during installation.
Action: Check if the user entry and queues were created in the wireless process entry.
Cause: Session created was closed without saving the changes.
Action: Check if the wireless process died suddenly. If the connection to database was lost for some reason. Look at the v$session table to check if the wireless process has any session open.
Cause: Session was already closed. The wireless process went down and closed the session before running the final closeConnections code.
Action: Re-start the Wireless process if it was stopped suddenly.
Cause: Queue connection was closed. The wireless process is cleaning up connections. In that process, it may encounter a already closed queue connection.
Action: If this happens when a process is shutdown through the administration screens, please verify v$session table to remove any dangling session for wireless process. In most cases, the queue connection is already closed.
Cause: Wrong queue name in wireless process entry.
Action: Check user_queues table to verify the queue names.
Cause: User does not have permissions to create queues or queue senders.
Action: Check the user entry in Oracle Internet Directory against the user in database.
Cause: User does not have permissions to create queues or queue browsers.
Action: Check the user entry in Oracle Internet Directory against the user in database.
Cause: User does not have permissions to create queues or queuereceiver.
Action: Check the user entry in Oracle Internet Directory against the user in database.
Cause: Cannot queue or dequeue a message from queue.
Action: Check if the database is up and running. If the user has permissions to queue or dequeue messages
Cause: Trying to send this message to a null address. Cannot resolve to a null address.
Action: Sender will get a notification from wireless system saying the same.
Cause: The device specified for the destination user does not exist.
Action: Will try to send to a default device. If no such device, notification sent back to the sender of the wireless message.
Cause: Cannot send broadcast messages to null device.
Action: Notification sent back to the administrator.
Cause: Sender is not administrator.
Action: Check the credentials.
Cause: Oracle Internet Directory went down. Cannot connect to Oracle Internet Directory for resolving addresses.
Action: Check Oracle Internet Directory connections. Re-send the message.
Cause: Sender is not a administrator.
Action: Check the credentials and re-send the message.
Cause: Cannot find devices for a given destination user.
Action: If default device is found, wireless system will send the message to that device. Else, will send a notification to the sender about the same. Check the user entry to find if he has any devices associated.
Cause: Cannot find devices for a given destination user.
Action: If default device is found, wireless system will send the message to that device. Else, will send a notification to the sender about the same. Check the user entry to find if he has any devices associated.
Cause: Cannot find devices for a given destination user.
Action: If default device is found, wireless system will send the message to that device. Else, will send a notification to the sender about the same. Check the user entry to find if he has any devices associated.
Cause: Oracle Internet Directory went down during the address resolution for a message.
Action: Bring up Oracle Internet Directory. The message will be resolved again by wireless system.
Cause: Not a Oracle9iAS Unified Messaging user.
Action: Ignore. Will try to resolve it to user device or send a notification back to the user.
Cause: No system devices in Oracle Internet Directory.
Action: Check for system devices under installation under UMContainer in Oracle Internet Directory.
Cause: Oracle Internet Directory is down.
Action: Will re-establish connection three times. If cannot establish a connection, it will enqueue the message into exqueue, which will be later processed by WirelessExceptionProcess. Bring up the Oracle Internet Directory.
Cause: No system devices found under installation container.
Action: Need to have devices supported by the wireless system in order to send out messages.
Cause: Message sent from an outside caller.
Action: Will send the message if destination is Oracle9iAS Unified Messaging user. If not, will send back notification to the sender.
Cause: Cannot resolve a given destination to the user device.
Action: Will send out a notification to the sender in case of error.
Cause: Address does not belong to sender's address book.
Action: Wireless server will resolve from user devices instead.
Cause: Given device name not available for the destination.
Action: Will send to the default device. Else send notification to the sender about the same.
Cause: Cannot send wireless message to null device. Null device specified in Message
Action: Will send a notification back to the sender about the same. Re-send a wireless message with non-null wireless message.
Cause: Exception in resolution.
Action: Check if Oracle Internet Directory is down. Or user entry is removed from the time the wireless message was sent.
Cause: Cannot find the DN for the wireless process to get queue connection parameters.
Action: Check for the command line parameters for using the class.
Cause: Oracle Internet Directory parameters for queue connection are null.
Action: Input the correct parameters in the wireless process entry in Oracle Internet Directory and re-run the command.
Cause: During installation, the queue creation failed. Trying to re-create and that fails too.
Action: Check for permission set for this user in the database for queue creations.
Cause: Empty queue object. Either the queue connection lost due to the database down or the queue object was removed.
Action: Check if the database is down.
Cause: Cannot get the queue object. Either connection lost or queue name is wrong.
Action: Check for the name match. Check if the database is down.
Cause: Oracle Internet Directory is down.
Action: Check if the Oracle Internet Directory server is up and running. Re-start the application.
Cause: The classpath was not set right. The wireless application stopped.
Action: If the application is down, restart the application. Look if the database or Oracle Internet Directory server went down suddenly.
Cause: The wrong parameters were set in Oracle Internet DirectoryOracle Internet Directory for queue connections or the database is down.
Action: Check if the database is up and running. Check the following parameters:
orclumwirelessinqueue
orclpasswordattribute
orcluminquid in Oracle Internet Directory against user or password in the database and check user_queues in the database for the inqueue name.
Cause: Cannot create a session or the queue name specified in Oracle Internet Directory does not match with the queue name in the database.
Action: Check for the name match and the database connections.
Notification: Creating the queue for the first time
Cause: During installation, the queue objects specified in Oracle Internet Directory were not created correctly.
Action: Check if the name matches are not right for the queue names.
Cause: Either the database is down or the queue connection parameters are specified wrong in Oracle Internet Directory.
Action: Same as for error in creating InQueueSession.
Cause: An error occurred when receiving a message from the queue.
Action: See message inside the JMSException and linked SQLException for more information.
Cause: One of the expected non-null variables for queue processing is null.
Action: Check the required parameters for queue connections.
Cause: Message inserted into the queue has parameters missing or wrong.
Action: Look for the prepareMessage exceptions for more information.
Cause: Exception caused in the RunProcess
Action: Check for any SQLExceptions and WirelessServerProcessExceptions for more information.
Cause: Queue connections or Oracle Internet Directory connection are not established correctly.
Action: Check to see if the database is up and running. Oracle Internet Directory is up and running. Check the queue parameters in the Oracle Internet Directory against the database.
Cause: The database is down or the connection parameters wrong.
Action: DB should be up and running. Check the connection parameters for wireless exception process.
Cause: Received null values from Oracle Internet Directory.
Action: Check for the values of UMInstallContext, UMRootContext, and ESRootContext for the wireless exception process.
Cause: Not null value expected for processing a message. Null value encountered.
Action: check the messages enqueued into exception queue. In most of the cases, this error should not occur.
Error: cannot process a given message
Cause: Unable to process the message from exception queue.
Action: Look for prepareMessageExceptions and other SQL exceptions for more information.
Cause: Exception during run. An unexpected process shutdown occurred or the database connection was lost.
Action: Look out for the other exceptions thrown for more information.
Cause: The prepare statement for WirelessMessageTable is failing.
Action: Check for permissions for this user on WirelessMessageTable in the database.
Cause: Cannot prepare statement for update operations.
Action: Check permission for this user.
Cause: Cannot prepare statement for sequence number.
Action: Check permissions for this user.
Cause: The database is down or the sequence created in the database is not accessible.
Action: check for um_sequence for this user.
Cause: Cannot perform the database operation. Database is down or permission problems for the user.
Action: Check the database and permissions in the database for this user.
Cause: Corrupted connections in the database. Unable to undo the operation.
Action: Check the database uptime.
Cause: Unable to access WirelessMessageTable.
Action: The database should be up. Check for rows in WirelessMessageTable through SQL.
Cause: Same as above.
Cause: The database is down or the user's permission does not permit them to perform database operations.
Action: Check the database and permissions.
Cause: The database connection already closed. The database went down suddenly.
Action: restart the database and restart the application.
Cause: Cannot establish ESDS Oracle Internet Directory connection to process user address book. Oracle Internet Directory
Action: Bring up Oracle Internet Directory.
Cause: SMTP process not running.
Action: SMTP in process should be running to send notifications out.
Cause: Error during initialization.
Action: Check for other errors for more information.
Cause: Error during resolution of address.
Action: Check for other errors.
Cause: Queue connection was lost or the database is down or queue name is wrong.
Action: Check for the database state. Check the queue names against the database.
Cause: Exception error in inserting prepared message into queue.
Action: Same as above.
Cause: Entire message is sent. User asking for more message parts.
Action: Ignore. The message has already been sent.
Cause: The device in message does not match with any system devices.
Action: Send Messages to devices already supported by system.
Cause: Cannot parse the message sent from device.
Action: Look for additional error messages for more information. Format may be wrong.
Cause: Cannot resolve addresses for a message sent from a device.
Action: Check the format, to and from addresses.
Cause: Cannot get rows or data from WirelessMessageTable. The database may be down.
Action: Check for Database uptime.
Cause: Exception in preparing the message.
Action: Look for other errors for more information.
Cause: The system does not support such a device to send back the message or notification.
Cause: Error while notifying the sender with error information.
Cause: Cannot create QueueTable. During installation, the QueueTable creation did not go through correctly. Or these queue connection parameters were changed in Oracle Internet Directory.
Action: Check for the QueueTable name listed in Oracle Internet Directory against the database.
Cause: A queue creation did not occur during installation.
Action: Check if the queues were created and the user entry in the wireless process entry.
Cause: Session created was closed without saving the changes.
Action: Check if the wireless process died suddenly. If the connection to database was lost for some reason. Look at the v$session table to check if the Wireless process has any session open.
Cause: Session was already closed. The wireless process died for some reason and closed the session before running the final closeConnections code.
Action: Re-start the wireless process if it was stopped suddenly.
Cause: The queue connection was closed. The wireless process is cleaning up connections. In that process, it may encounter a already closed queue connection.
Action: If this happens when a process is shutdown through the administration screens, please verify v$session table to remove any dangling session for wireless process. In most cases, the queue connection is already closed.
Cause: Wrong queue name in wireless process entry.
Action: Check user_queues table to verify the queue names.
Cause: User does not have permissions to create queues or queue senders.
Action: Check the user entry in Oracle Internet Directory against the user in database.
Cause: User does not have permissions to create queues or queue browsers.
Action: Check the user entry in Oracle Internet Directory against the user in database.
Cause: User does not have permissions to create queues or queue receiver.
Action: Check the user entry in Oracle Internet Directory against the user in database.
Cause: Cannot queue or dequeue a message from queue.
Action: Check if the database is up and running. If the user has permissions to queue or dequeue messages
Cause: Trying to send this message to a null address. Cannot resolve to a null address.
Action: Sender will get a notification from wireless system saying the same.
Cause: The device specified for the destination user does not exist.
Action: Try to send to a default device. If no such device, notification sent back to the sender of the wireless message.
Cause: Cannot send broadcast messages to null device.
Action: Notification sent back to the administrator.
Cause: The sender is not an administrator.
Action: Check the credentials.
Cause: Oracle Internet Directory went down. Cannot connect to Oracle Internet Directory for resolving addresses.
Action: Check Oracle Internet Directory connections. Re-send the message.
Cause: Sender is not an administrator.
Action: Check the credentials and re-send the message.
Cause: Cannot find devices for a given destination user.
Action: If default device is found, wireless system will send the message to that device. A notification will be sent to the sender. Check the user entry to find if he has any devices associated.
Cause: Cannot find devices for a given destination user.
Action: If default device is found, wireless system will send the message to that device. A notification will be sent to the sender. Check the user entry to find if he has any devices associated.
Cause: Cannot find devices for a given destination user.
Action: If default device is found, wireless system will send the message to that device. A notification will be sent to the sender. Check the user entry to find if he has any devices associated.
Cause: Oracle Internet Directory went down during the address resolution for a message.
Action: Bring up Oracle Internet Directory. The message will be resolved again by the wireless system.
Cause: Not a Oracle9iAS Unified Messaging user.
Action: Ignore. Try to resolve it to user device or send a notification back to the user.
Cause: No system devices in Oracle Internet Directory.
Action: Check for System devices under installation under UMContainer in Oracle Internet Directory.
Cause: Oracle Internet Directory is down.
Action: Will re-establish connection three times. If cannot establish a connection, it will enqueue the message into exqueue, which will be later processed by WirelessExceptionProcess. Bring up the Oracle Internet Directory.
Cause: No system devices found under installation container.
Action: Need to have devices supported by the wireless system in order to send out messages.
Cause: Message sent from an outside caller.
Action: Will send the message if destination is Oracle9iAS Unified Messaging user. If not, will send back notification to the sender.
Cause: Cannot resolve a given destination to user device.
Action: Will send out a notification to the sender in case of error.
Cause: Address does not belong to sender's address book.
Action: Wireless server will resolve from user devices instead.
Cause: Given device name not available for the destination.
Action: Will send to the default device. Else send notification to the sender about the same.
Cause: Cannot send wireless message to null device. Null device specified in Message
Action: Will send a notification back to the sender about the same. Re-send a wireless message with non-null wireless message.
Cause: Exception in resolution.
Action: Check if Oracle Internet Directory is down. The user entry was removed from the time the wireless message was sent.
Cause: Cannot find the DN for the wireless process to get queue connection parameters.
Action: Check for the command line parameters for using the class.
Cause: Oracle Internet Directory parameters for queue connection are null.
Action: Input the correct parameters in the wireless process entry in Oracle Internet Directory and re-run the command.
Cause: During installation, the queue creation failed. Trying to re-create and that fails too.
Action: Check for permission set for this user in the database for queue creations.
Cause: Empty queue object. Either the queue connection was lost due to the database being down or the queue object was removed.
Action: Check if the database is down.
Cause: Cannot get the Queue Object. Either connection lost or queue name is wrong.
Action: Check for the name match. Check if the database is down.
Cause: Oracle Internet Directory is down.
Action: Check if the Oracle Internet Directory server is up and running. Re-start the application.
Cause: The classpath is not set right. The wireless application suddenly died for some reason.
Action: If the application is down, restart the application. Look if the database or Oracle Internet Directory server went down suddenly.
Cause: Wrong parameters set in Oracle Internet Directory for queue connections or the database is down.
Action: Check if the database is up and running. Check the following parameters:
orclumwirelessinqueue
orclpasswordattribute
orcluminquid in Oracle Internet Directory against user or password in the database and check user_queues in the database for the inqueue name.
Cause: Cannot create a session from above or queue name specified in Oracle Internet Directory does not match with queue name in the database.
Action: Check for the name match and the database connections.
Cause: During installation, queue objects specified in Oracle Internet Directory were not created correctly. Trying creating them before establishing connections.
Action: Check if the name matches are not right for the queue names.
Cause: Either the database is down or the queue connection parameters are specified wrong in Oracle Internet Directory.
Action: Check the database status and verify that the queue connection parameters are correct.
Cause: An error occurred when receiving a message from queue.
Action: See message inside the JMSException and linked SQLException for more information.
Cause: One of the expected non-null variables for queue processing is null.
Action: Check the required parameters for queue connections.
Cause: Message inserted into the queue has parameters missing or wrong.
Action: Look for the prepareMessage exceptions for more information.
Cause: Exception caused in run process
Action: Check for any SQLExceptions, WirelessServerProcessExceptions for more information.
Cause: The queue connections or Oracle Internet Directory connection are not established correctly.
Action: Check if the database is up and running. Oracle Internet Directory is up and running. Check the queue parameters in the Oracle Internet Directory against the database.
Cause: The database is down or the connection parameters are wrong.
Action: Verify that the database is running. Check the connection parameters for the wireless exception process.
Cause: Received null values from Oracle Internet Directory.
Action: Check for the values of UMInstallContext, UMRootContext, and ESRootContext for the wireless exception process.
Cause: There can be no null values for processing a message. Null value encountered.
Action: Check the messages enqueued into exception queue. In most of the cases, this error should not occur.
Cause: The system is unable to process the message from the exception queue.
Action: Check for prepareMessage exceptions and other SQL exceptions for more information.
Cause: Exception during run. Unexpected shutdown of process or database connection lost.
Action: Look out for the other exceptions thrown for more information.
Cause: prepare Statement for WirelessMessageTable failing.
Action: Check for permissions for this user on the WirelessMessageTable in the database.
Cause: cannot prepare statement for update operations.
Action: Check permission for this user.
Cause: Cannot prepare statement for sequence number.
Action: Check permissions for this user.
Cause: The database is down or the sequence created in the database is not accessible.
Action: check for um_sequence for this user.
Warning: Cannot insert a row into WMT table
Cause: Cannot perform the database operation. The database is down or permission problems for the user.
Action: Check the database and permissions in the database for this user.
Cause: Corrupted connections in the database. Unable to undo the operation.
Action: Check the database uptime.
Cause: Unable to access the WirelessMessageTable.
Action: the database should be up. Check for rows in WirelessMessageTable through SQL.
Cause: Unable to access the WirelessMessageTable.
Cause: The database is down or user's permission does not permit them to perform database operations.
Action: Check the database and permissions.
Cause: The database connection already closed. The database went down suddenly.
Action: restart the database and restart the application.
Cause: Cannot establish ESDS Oracle Internet Directory connection to process user address book.
Action: Oracle Internet Directory must be down. Bring up Oracle Internet Directory.
Cause: SMTP process not running.
Action: SMTP in process should be running to send notifications out.
Cause: There was an error during initialization.
Action: Check for other errors for more information.
Cause: There was an error during resolution of address.
Action: Check for other errors.
Cause: The queue connection was lost, or the database is down, or queue name is wrong.
Action: Check the database. Check the queue names against database.
Cause: There was an exception error in inserting prepared message into queue.
Action: Check the database. Check the queue names against database.
Cause: The entire message was sent and the user asking for more message parts.
Action: Ignore. The message has already been sent.
Cause: The device in message does not match with any system devices.
Action: Send messages to devices that are already supported by system.
Cause: The message sent from the device cannot be parsed.
Action: Look for additional error messages for more information. Format may be wrong.
Cause: Cannot resolve addresses for a message sent from a device.
Action: Check the format of the to and from addresses.
Cause: Cannot get the rows or data from the WirelessMessageTable. The database may be down.
Action: Check the database uptime.
Cause: There was an exception in preparing the message.
Action: Look for other errors for more information.
Cause: The system does not seem to support such a device to send back the message or notification.
Cause: An error occurred while notifying the sender with error information.
|
 Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|