Explanation: An exception occurred when reading the WebSphere Presence Server configuration file.
User response: Ensure that the WebSphere Presence Server configuration file is formatted properly and contains valid data.
Explanation: One of the configuration parameters is not valid.
User response: Ensure that the WebSphere Presence Server configuration file contains valid data.
Explanation: An application failed with the java.lang.ClassNotFoundException exception. This means that the class is missing from the jar or classpath.
User response: Search the JAR files on your system for the missing class. When you find the missing class, make sure that its JAR is in the general classpath, the project classpath, the command line classpath, or the ext directories for WebSphere Application Server.
Explanation: An unexpected internal error occurred.
User response: An internal error occurred in The Presence Server application. Notify your system administrator.
Explanation: An application failed because an initial context could not be instantiated, or a lookup failed. A javax.naming.NamingException error occurred.
User response: Notify your system administrator.
Explanation: An exception occurred when creating a local EJB.
User response: Notify your system administrator.
Explanation: An exception occurred when looking up an object JNDI name.
User response: Notify your system administrator.
Explanation: An error occurred when creating an EJB. A null pointer was returned.
User response: Notify your system administrator.
Explanation: A remote exception occurred when invoking an external provider.
User response: Notify your system administrator.
Explanation: An error occurred when creating a Timer. A null pointer was returned.
User response: Notify your system administrator.
Explanation: An error occurred when accessing a database.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: Could not initialize access to a database. This problem usually occurs when the Storage Engine bean cannot be located.
User response: Notify your system administrator.
Explanation: An SQLException error was received when closing a database connection.
User response: Notify your system administrator.
Explanation: A database access error occurred while executing an SQL SELECT statement from the PUBLISH table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL SELECT statement from the FULLDOC table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL DELETE statement from the PUBLISH table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL DELETE statement from the FULLDOC table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL INSERT/UPDATE statement in the PUBLISH table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL INSERT/UPDATE statement in the FULLDOC table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL SELECT statement from the MANAGING_SERVERS table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL INSERT/UPDATE statement in the MANAGING_SERVERS table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL DELETE statement from the MANAGING_SERVERS table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL SELECT statement from the CONFIG table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL SELECT statement from the WATCHERS table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL INSERT/UPDATE statement in the WATCHERS table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL DELETE statement from the WATCHERS table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL SELECT statement from the PRESENCE_AUTH_RULES table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL INSERT/UPDATE statement in the PRESENCE_AUTH_RULES table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL DELETE statement from the PRESENCE_AUTH_RULES table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: The database could not be accessed. The database type (DB2 or Oracle) cannot be determined from the database connection details.
User response: Notify your system administrator.
Explanation: An SQLException error was received when trying to get a database connection.
User response: Notify your system administrator.
Explanation: There are too many watcher subscriptions for the user, and this information cannot be contained in the watchers table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received. The problem might be fixed by increasing the size of the SubscriptionIds column.
Explanation: A database access error occurred while executing an SQL SELECT statement from the CONTENT_INDIRECTION table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL INSERT/UPDATE statement in the CONTENT_INDIRECTION table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL DELETE statement from the CONTENT_INDIRECTION table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL SELECT statement from the SUBSCRIPTIONS table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL INSERT/UPDATE statement in the SUBSCRIPTIONS table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: A database access error occurred while executing an SQL DELETE statement from the SUBSCRIPTIONS table.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: An exception occurred when trying to get onMessage to receive the message type.
User response: Notify your system administrator.
Explanation: An exception occurred when trying to get onMessage to receive an object.
User response: Notify your system administrator.
Explanation: A problem was detected while analyzing the broadcast of a presence update operation.
User response: Notify your system administrator.
Explanation: The Presence Server application encountered a RemoteException while trying to subscribe to a shared list server provider.
User response: Notify your system administrator.
Explanation: The Presence Server application encountered a RemoteException while trying to unsubscribe from a shared list server provider.
User response: Notify your system administrator.
Explanation: The Presence Server application could not parse the white and black list document as configured in the shared list server.
User response: Notify your system administrator.
Explanation: The Presence Server application encountered an unpredictable error response from the XDMS shared list server.
User response: Notify your system administrator.
Explanation: The Presence Server application encountered an incorrect NOTIFY from the XDMS shared list server.
User response: Notify your system administrator.
Explanation: The Presence Server application could not register an external source.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: The Presence Server application could not unregister an external source.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: The Presence Server application received this error from an external provider.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: The Presence Server application received this error from an external source.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: An error occurred when composing external information to a presence document.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: The Presence Server application encountered a RemoteException while trying to subscribe to an XDMS service provider.
User response: Notify your system administrator.
Explanation: The Presence Server application encountered a RemoteException while trying to unsubscribe from an XDMS service provider.
User response: Notify your system administrator.
Explanation: The Presence Server application could not register the external authorization service.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: The Presence Server application could not unregister the external authorization service.
User response: For information about how to resolve the problem, look at the description in the alarm message you received.
Explanation: Authorization could not be performed because there is no registered external authorization service.
User response: Register an external authorization service to perform authorization for watchers.
Explanation: The unsubscribe operation is unnecessary because there is no registered external authorization service.
User response: No action is required.
Explanation: The Presence Server application could not initialize usage records.
User response: Notify your system administrator.
Explanation: The operation on the usage records database did not complete because a run-time exception was encountered.
User response: Notify your system administrator.
Explanation: The operation did not complete because the SIP application session has expired, or because the request could not be located.
User response: No action is required.
Explanation: The operation did not complete because the SIP session does not exist, because it has expired, or because a run-time exception was encountered.
User response: No action is required.
Explanation: The doPublish operation did not complete because a runtime exception was encountered.
User response: No action is required.
Explanation: The operation did not complete because a SIP application session has expired, or because the request could not be located.
User response: No action is required.
Explanation: The attempt to subscribe to a SIP provider was unsuccessful for the reason described in the message you received.
User response: For information about how to resolve the problem, look at the description of the message returned by the failure for more information on how to resolve the problem.
Explanation: An error occurred when accessing the data layer.
User response: Notify your system administrator.
Explanation: An error occurred while sending a publish request from the resource list server (RLS).
User response: Notify your system administrator.
Explanation: This is an informational message received during system configuration.
User response: No action is required.
Explanation: This is an informational message received during system configuration.
User response: No action is needed.
Explanation: This is an informational message received during system configuration.
User response: No action is required.
Explanation: Loading system configuration is completed, but there are values that will not be considered in this context.
User response: Recheck the configuration values you specified, resolve any incompatibilities, and retry the operation.
Explanation: This is an informational message received during system configuration.
User response: No action is required.
Explanation: This is an informational message received during system configuration.
User response: No action is required.
Explanation: This is an informational message received during system configuration.
User response: No action is required.