86 SDP-25001 to SDP-26455

SDP-25001: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25002: Unable to create JNDI Context

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check the JNDI Context initialization parameters.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25003: Unable to create an instance of Driver Locator

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25005: Failed to create Sending Core instance

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25006: Failed to remove an EJB instance

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25007: An error occurred while processing an outbound message.

Cause: The outbound JMS message does not contain a valid message or request information.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25008: An unexpected error occurred while processing an outbound message.

Cause: An unexpected exception has occurred while processing the outbound message.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25009: An error occurred while storing a message.

Cause: An unexpected exception has occurred while processing the message.

Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25010: An error occurred while sending an outbound message.

Cause: An unexpected exception has occurred while processing the outbound message.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25011: An error occurred while transforming an outbound message.

Cause: An unexpected exception has occurred while processing the outbound message.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25012: An error occurred while processing error statuses.

Cause: An unexpected exception has occurred while processing error statuses.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25015: There are no transformed messages of message {0} for recipients {1}. Skipping message delivery to these recipients.

Cause: An unexpected exception has occurred while transforming an outbound message.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25020: Unable to schedule a timed failover event

Cause: An unexpected exception has occurred while scheduling a timed failover event.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25021: An error occurred while processing a timed failover event

Cause: An unexpected exception has occurred while processing a timed failover event.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25030: Unable to schedule a timer to refresh the driver locator cache.

Cause: An unexpected exception has occurred while scheduling a timer to refresh the driver cache.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Configuration

SDP-25031: Unable to refresh the driver locator cache.

Cause: An unexpected exception has occurred while refreshing the driver locator cache.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Configuration

SDP-25032: An error occurred while registering driver information {0}.

Cause: An unexpected exception has occurred while registering the driver information.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Configuration

SDP-25033: An error occurred while unregistering driver information {0}.

Cause: An unexpected exception has occurred while unregistering the driver information.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Configuration

SDP-25034: There are total {0} registered User Messaging Drivers. Driver(s): {1}

Cause: A Messaging Driver registered with the Messaging Server

Action: None

Level: 1

Type: NOTIFICATION

Impact: Configuration

SDP-25035: Messaging store not found.

Cause: An unexpected exception has occurred while attempting to find the messaging store.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25037: Error while retrieving configuration property: {0}.

Cause: Unable to read from the messaging server configuration file 'configuration/appconfig.xml' or the named property does not exist.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Configuration

SDP-25038: Error while loading the messaging server configuration properties. Falling back to default configuration.

Cause: Unable to read from the messaging server configuration file 'configuration/appconfig.xml'.

Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Configuration

SDP-25040: Unable to create an instance of CommandReceiverBean.

Cause: An unexpected exception has occurred while attempting to process a command.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25041: Received driver registration command message: {0}.

Cause: A driver sent its registration information to this engine.

Action: None

Level: 1

Type: TRACE

Impact: Configuration

SDP-25042: An error occurred while processing a command message.

Cause: An unexpected exception has occurred while attempting to process a command.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Configuration

SDP-25043: An unknown command message was received, ignoring: {0}.

Cause: The engine received an unknown command message and was unable to process the command.

Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.

Level: 1

Type: WARNING

Impact: Configuration

SDP-25044: Received driver unregistration command message: {0}.

Cause: A driver was undeployed and it sent an unregistration command to the engine.

Action: None

Level: 1

Type: TRACE

Impact: Configuration

SDP-25055: Failed to create Receiving Core instance.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25057: An error occurred while processing an inbound message.

Cause: The inbound JMS message does not contain a valid message.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25058: An unexpected error occurred while processing an inbound message.

Cause: An unexpected exception has occurred while processing the inbound message.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25059: An unknown JMS message is received, ignoring: {0}.

Cause: The engine received an unknown JMS message and was unable to process it.

Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25060: There is no application that has registered this address as an access point. Message will not be delivered.

Cause: There is no application that has registered this recipient address as an access point.

Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25061: An unexpected error occurred while processing inbound message statuses.

Cause: An unexpected exception has occurred while attempting to process inbound message statuses.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25062: Cannot correlate status with any message; storing for possible later processing.

Cause: An inbound status arrived in an unexpected order.

Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25063: There is no application client information for this status: {0}

Cause: There is no application client information associated with this access point holder.

Action: Check the current log file for additional details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25064: An unexpected error occurred while recording a status processing update.

Cause: An unexpected exception has occurred while attempting to record a status processing update.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25065: An unexpected error occurred while sending a message to failover address {0}.

Cause: An exception has occurred while sending out a failover message.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25066: An unexpected error occurred while processing an outbound message status.

Cause: An unexpected exception has occurred while attempting to process an outbound message status.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25070: Unable to retrieve messaging engine sending and/or receiving queues from configuration.

Cause: A severe configuration error has occurred and the system is not functional.

Action: Check the messaging engine configuration and the stack trace, if available, for more details.

Level: 1

Type: ERROR

Impact: Configuration

SDP-25080: An error occurred while converting a message.

Cause: An invalid message content or inappropriate converter was used to perform the message conversion.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25081: An error occurred while adding a message converter rule: {0}

Cause: An invalid message converter rule was provided.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25082: No predicates and/or devices matched. Ignoring converter rule (MIME type: {0}, delivery type: {1}, predicate: {2}).

Cause: An invalid message converter rule was provided.

Action: Check the current log file for additional details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25083: Message content is not an instance of MimeMultipart

Cause: An invalid message content was provided to this converter.

Action: Check the current log file for additional details. Check User Messaging Service Javadoc on OTN for more information on sending MimeMultipart messages.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25084: Could not lookup physical device {0} for recipient {1}

Cause: An invalid recipient was provided or there is no device mapping for this recipient.

Action: Check the current log file for additional details. Send the message with a valid recipient.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25085: Message {0} has a nonunique Message ID or recipient, and does not look like a redelivery attempt.

Cause: A message was sent or received that appears to be a duplicate of an already processed message; re-enqueuing message with delay specified.

Action: Ensure that messages are assigned unique Message IDs.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25086: Retrying delivery of message {0}

Cause: Previous attempt to deliver message failed. Retrying.

Action: None.

Level: 1

Type: TRACE

Impact: Requests/Responses

SDP-25087: Message {0} is marked for retry but has already been delivered.

Cause: A message was marked for retry by JMS but has already been delivered; dropping message.

Action: None.

Level: 1

Type: TRACE

Impact: Requests/Responses

SDP-25088: Unable to refresh the driver locator cache, due to the following error: {0}

Cause: An unexpected error has occurred while refreshing the driver locator cache.

Action: Check the reported error message and correct any configuration problems.

Level: 1

Type: ERROR

Impact: Configuration

SDP-25100: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25101: Caught an unexpected database exception.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Data

SDP-25102: TopLink database platform class {0} not found. Using default database platform.

Cause: No TopLink database platform class is available with the configured name.

Action: Add new or update existing <DatabasePlatform> with a valid TopLink database platform class in usermessagingserver/configuration/appconfig.xml.

Level: 1

Type: WARNING

Impact: Configuration

SDP-25103: Could not instantiate TopLink database platform class.

Cause: An exception has occurred while instantiating the TopLink database platform class.

Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Configuration

SDP-25104: Initializing Messaging Store in transient mode.

Cause: Initializing Messaging Store in transient mode. Message history will not persist across server restarts.

Action: n/a

Level: 1

Type: NOTIFICATION

Impact: Configuration

SDP-25105: Initializing Messaging Store in {0} mode.

Cause: Initializing Messaging Store in persistent mode. Message history will persist across server restarts.

Action: n/a

Level: 1

Type: NOTIFICATION

Impact: Configuration

SDP-25106: Conflicting recipient IDs for Message {0}.

Cause: A conflict between recipient identifiers has been detected.

Action: Ensure that applications are using unique Message IDs.

Level: 1

Type: WARNING

Impact: Programmatic

SDP-25107: Message ID {0} in Status object does not match previously recorded Message ID {1}.

Cause: A status object returned from a driver contained a different Message ID than expected.

Action: Ensure that drivers are mapping Gateway IDs to Message IDs correctly.

Level: 1

Type: WARNING

Impact: Data

SDP-25108: One or more addresses from Access Point {0} is already registered by another application.

Cause: An access point address can only be registered by one application at a time.

Action: Resolve the conflict among applications.

Level: 1

Type: TRACE

Impact: Requests/Responses

SDP-25109: Could not initialize persistence context.

Cause: An exception has occurred while initializing the persistence context.

Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Configuration

SDP-25110: An error occurred while initializing persistence session, with the following error message: {0}

Cause: An error occurred while attempting to initialize and log in to the TopLink persistence session.

Action: Check the reported error message and correct any configuration or database availability problems.

Level: 1

Type: WARNING

Impact: Session

SDP-25111: An error occurred while initializing persistence session, with the following exception stack trace:

Cause: An exception occurred while attempting to initialize and log in to the TopLink persistence session.

Action: Check the reported exception message and correct any configuration or database availability problems.

Level: 1

Type: TRACE

Impact: Session

SDP-25200: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25201: No endpoint URL is available for the web service callback operation.

Cause: No endpoint URL is available for the web service listener callback.

Action: Ensure a valid callback URL is specified when registering a message or status listener.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25250: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25251: Messaging Exception while processing Parlay X request.

Cause: A Messaging Exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25252: Exception while initializing Parlay X Messaging servlet.

Cause: An exception occurred while initializing the Parlay X Messaging servlet.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Deployment

SDP-25253: Exception while initializing Parlay X Messaging content servlet.

Cause: An exception occurred while initializing the Parlay X Messaging content servlet.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Deployment

SDP-25254: Exception while processing SOAP attachment content.

Cause: An exception occurred while processing message content in a SOAP attachment.

Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25255: Message contains multiple attachments. All but first attachment will be ignored.

Cause: The client application sent a message with multiple attachment parts.

Action: Client applications should send one attachment part per message. Complex content should be sent as a MIME Multipart object.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25256: Permission denied.

Cause: The client application did not have permission to invoke the attempted operation.

Action: Check the stack trace for more details.

Level: 1

Type: TRACE

Impact: Security

SDP-25257: Error initializing JAXP DatatypeFactory. Some data types may not be converted correctly.

Cause: Could not acquire instance of class javax.xml.datatype.DatatypeFactory. Marshalling/unmarshalling of some XML elements may not happen correctly.

Action: Ensure that the server's JAXP framework is configured correctly.

Level: 1

Type: WARNING

Impact: Configuration

SDP-25258: Error initializing the Servlet Endpoint Context. Parlay X module will not be able to service requests correctly.

Cause: Could not initialize the Servlet Endpoint Context.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25259: Error initializing access to Messaging Server. Parlay X module will not be able to service requests correctly.

Cause: Could not initialize internal Messaging Client endpoint.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25300: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25301: JNDI context is null.

Cause: JNDI context was null.

Action: See the Javadoc on Oracle Technology Network (OTN) for more information about how to instantiate a JNDI context.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25302: EJB home for UserPrefsService is null.

Cause: EJB home for UserPrefsService is null.

Action: See the Javadoc on Oracle Technology Network (OTN) for more information about how to specify an EJB home.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25303: Unable to connect to User Messaging Service (UMS) server at {0}.

Cause: EJB Naming Exception was caught when creating a UserPrefsServices object.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25304: EJB Remote Exception was caught at server {0}

Cause: EJB Remote Exception was caught.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25305: EJB Create Exception was caught at server {0}

Cause: EJB Create Exception was caught.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25306: XML Document object is null.

Cause: XML Document object is null.

Action: Specify a valid XML document object.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25307: No file to upload. File name is not set.

Cause: The file name to be uploaded was not set.

Action: Invoke setFileName() to set the file name.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25308: The file, {0}, cannot be read.

Cause: The file cannot be read.

Action: Check the file.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25309: File not found: {0}

Cause: The file with the given file name does not exist.

Action: Check to see if the path and file name are correct. File name must be in /path/filename or file://path/filename format.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25310: The URL is malformed: {0}

Cause: The URL is malformed.

Action: The URL must be in file://path/filename format.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25311: The document cannot be uploaded. Parser and stack are out of sync. Tag name: {0} Local name: {1}

Cause: The document cannot be uploaded because parser and stack were out of sync.

Action: Fix mismatched tags.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25312: Provisioning Exception was caught.

Cause: Provisioning Exception was caught.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25313: Null Pointer Exception was caught.

Cause: Null Pointer Exception was caught.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25314: Rule {0} is already defined.

Cause: Rule with the same name was already defined.

Action: Choose a different rule name to avoid conflict.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25316: Input parameter, UserPrefsServices, is null.

Cause: The UserPrefsServices object was null.

Action: Pass a valid UserPrefsServices object as a parameter. Check User Messaging Service Javadoc on OTN for more information.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25317: Required input parameter, UserID, is null.

Cause: Failed to invoke method, because required input parameter, UserID, is null.

Action: Pass a valid UserID. Check User Messaging Service Javadoc on OTN for more information.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25318: Invalid input parameter. DeviceAddress object is null.

Cause: Input parameter, DeviceAddress object, is null.

Action: Pass a valid DeviceAddress object. Check User Messaging Service Javadoc on OTN for more information.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25319: UserRuleSet is not set. Call initProcessor() first.

Cause: UserRuleSet object is null.

Action: Call initProcessor() first to complete initialization.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25320: Rule Set is null.

Cause: The Rule Set was not available or could not be created.

Action: Use a valid Rule Set.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25321: XML String representing the Rule Set is null.

Cause: The XML document element representing the Rule Set was null or empty.

Action: Use a valid Rule Set XML element.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25322: User Rule Set is null.

Cause: The User Rule Set was not available or could not be created.

Action: Use a valid User Rule Set object.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25323: User Rule Set is inconsistent. See exception for more details.

Cause: User Rule Set is inconsistent.

Action: Check User Rule Set for consistency.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25324: XML document is invalid. See exception for details.

Cause: XML document is invalid. See stacktrace for more details.

Action: Validate the XML document.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25325: Cannot serialize Rule Session.

Cause: Cannot serialize Rule Session, which is not critical.

Action: No action needed.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25326: Filter XML is null.

Cause: The Preference Rules were missing or inconsistent.

Action: Use a well-formed User Preference XML document.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25327: Cannot create Rule Session.

Cause: Cannot create Rule Session.

Action: No action needed.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25328: UserPrefsException was caught.

Cause: UserPrefsException was caught.

Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25329: Rule {0} does not exist.

Cause: The expected rule was not found.

Action: Check the rule by name on the User Preference page.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25330: Business Term Type has changed.

Cause: Business Term Type has changed.

Action: Recheck the Preference Rules.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25331: Cannot instantiate User Prefs Services.

Cause: Cannot instantiate User Prefs Services due to an initialization error.

Action: Check User Prefs Services configuration such as DataSource and TopLink DB Platform.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25332: Directory for User Prefs Services File Persistence does not exist.

Cause: Directory for User Prefs Services File Persistence does not exist.

Action: System will try to create the directory.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25333: invalid directory: {0}

Cause: The given path was not a valid directory.

Action: Specify a valid directory, not a file.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25334: Device name is null.

Cause: Device name is null.

Action: Provide a valid Device name.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25335: invalid user ID: {0}

Cause: An invalid user ID was specified.

Action: Specify a valid user ID.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25336: Input parameter, UserPrefsObject, is null.

Cause: Required parameter, UserPrefsObject, is null.

Action: Provide a valid UserPrefsObject.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25337: Failed to move a rule: origin rule number is out of the range of existing rules.

Cause: Origin rule number is not valid.

Action: Specify a valid rule number.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25338: Cannot find object to update: {0}

Cause: Cannot find object to update.

Action: Could be a problem in implementing persistence.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25339: Object already exists.

Cause: Tried to persist an object that already exists.

Action: To overwrite existing value, use '-overwrite' flag.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25340: Object not found.

Cause: Tried to remove an object that does not exist.

Action: (None)

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25341: The order of calling methods is wrong.

Cause: The order of calling methods is wrong.

Action: Check the order of the methods being called.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25342: Cannot find default address for user {0}.

Cause: The default address of that user was not set.

Action: Check that default address is set from UserPreference Administrator page.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25343: No devices are defined.

Cause: Tried to call delivery preferences without defining devices.

Action: Define devices for use with delivery preferences.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25344: Invalid action {0} is found and ignored.

Cause: An invalid action was detected.

Action: Use one of the valid actions: BROADCAST, FAIL_OVER, and DO_NOT_SEND.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25345: Runtime exception was caught.

Cause: Runtime exception was caught.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25346: No configured Business Terms are available, only system terms will be used.

Cause: Business Term configuration could not be read.

Action: Ensure that business term configuration is correct

Level: 1

Type: WARNING

Impact: Configuration

SDP-25347: Device {0} cannot be added because it is present in the list.

Cause: A device was present in the list already.

Action: Ensure that the device to be added is not in the device list.

Level: 1

Type: WARNING

Impact: Configuration

SDP-25348: Failed to move a device: device ID index number is out of the range of device list.

Cause: Device ID index number is not valid.

Action: Specify a valid device ID index number.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25349: Name of rule is not set.

Cause: Rule name was not set.

Action: Set the name of the rule.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25350: FilterOperation of a rule is not set.

Cause: FilterOperation of a rule was not set.

Action: Set the FilterOperation of the rule.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25351: ActionOperation of a rule is not set.

Cause: ActionOperation of a rule was not set.

Action: Set the ActionOperation of the rule.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25352: Condition of a rule is not set.

Cause: Condition of a rule was not set.

Action: Set the condition of the rule.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25353: unable to send a BROADCAST message because no address is set

Cause: An address has not been set for the BROADCAST action.

Action: Set at least one address for the BROADCAST action.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25354: A failover address is not set for the FAIL_OVER action.

Cause: An address has not been set for the FAIL_OVER action.

Action: Set at least one address for the FAIL_OVER action.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25355: error while loading the business rule terms configuration

Cause: The business rule terms configuration file configuration/businessterms.xml could not be read.

Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Configuration

SDP-25356: Cannot persist device address {0} for user GUID {1}, because one already exists.

Cause: An identical device address already exists.

Action: Remove the conflicting device address, overwrite it, or specify a different address.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25357: Cannot persist rule set for user GUID {0}, because one already exists.

Cause: A rule set already exists for this user.

Action: Remove the conflicting rule set, or overwrite it.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25358: Cannot upload rule set for user GUID {0}, because one already exists.

Cause: A rule set already exists for this user.

Action: Try uploading the user messaging preferences using merge option 'overwrite' or 'append' (refer to command help for details).

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25359: Cannot upload user device for user GUID {0}, because one already exists.

Cause: A user device already exists for this user.

Action: Try uploading the user messaging preferences using merge option 'overwrite' or 'append' (refer to command help for details).

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25360: Initializing User Messaging Preferences services.

Cause: User Messaging Preferences services were initialized as part of application startup or deployment.

Action: None.

Level: 1

Type: NOTIFICATION

Impact: Other

SDP-25361: The Java VM does not support the encoding {0}.

Cause: The Java VM does not support the encoding used for XML string representing the RuleSet.

Action: Check your server Java VM and make sure it supports the encoding.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25362: This User Preference object cannot be deleted because it is backed by the user profile in the identity store: {0}.

Cause: An attempt was made to delete a read-only object backed by the user profile in the identity store.

Action: None.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25363: No UserRuleSet exists for userID {0}.

Cause: The user does not have a UserRuleSet.

Action: Check spelling of user ID.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25364: setFilterOperation has not been called.

Cause: Incorrect calling sequence.

Action: Invoke method setFilterOperation() first.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25365: Condition does not exist: {0}

Cause: Condition cannot be found.

Action: Check spelling of condition name or ID.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25366: Source parameter is greater than the number of conditions.

Cause: Source parameter is out of range.

Action: Provide correct source parameter.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25367: Error creating FilterCondition, type {0} is not valid.

Cause: Incorrect type has been found.

Action: Use correct type.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25368: Term {0} is not valid.

Cause: Term is not valid.

Action: Use a valid term.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25369: Term of type {0} does not accept operation {1}.

Cause: Unmatched type and operation.

Action: Use matching type and operation.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25370: Method setFilterTerm() has not been called.

Cause: setFilterTerm() method has not been called prior to current method invocation.

Action: Invoke setFilterTerm() first.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25371: FilterTerm should be initialized.

Cause: FilterTerm has not been initialized.

Action: Initialize FilterTerm first.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25372: Inconsistent FilterTerm.getName() : {0}, {1}

Cause: Name of filter term does not match the name of filter condition.

Action: Fix the inconsistency of filter term name and filter condition name.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25373: Inconsistent FilterTerm.getTypeName() : {0}, {1}

Cause: Type name of filter term does not match the name of filter condition.

Action: Fix the inconsistency of filter term type name and filter condition type name.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25374: Term operation should be defined.

Cause: Undefined term operation.

Action: Define operation of the term.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25375: Term of type {0} does not accept operation {1}.

Cause: Operation was not accepted by the term.

Action: Specify an operation that can be accepted by the term.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25376: TermOperation must be set.

Cause: TermOperation was not set.

Action: Set TermOperation properly.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25377: Operand {0} just allows {1} arguments, but is given {2}.

Cause: Number of arguments does not meet the requirement of the operand.

Action: Set correct number of arguments.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25378: Object {0} should be of type {1}.

Cause: Object has an incorrect Java type.

Action: Correct the type of object.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25379: Type {0} is not supported.

Cause: Object's type is not supported by User Preferences.

Action: Change the type of object to one of following supported Java types: String, Integer, Double and Date

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25380: User {0} does not exist in the system.

Cause: User name not found.

Action: Provide the correct user name.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25381: Device not found for user {0}.

Cause: Device does not exist.

Action: Provide a valid Device name or username.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25382: DeliveryType is missing in the address {0}.

Cause: Address does not have required DeliveryType.

Action: Provide a valid DeliveryType in the address in <DeliveryType>:<Address> format.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25383: Cannot persist device address {0}.

Cause: An exception occurred when storing device address.

Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25384: Cannot create RuleSet for the user {0}.

Cause: An exception occurred while creating RuleSet for this user.

Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25385: Saving UserRuleSet failed. Cannot get XMLString for user {0}.

Cause: An exception occurred while savinging RuleSet for this user.

Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25386: Could not find entity to update.

Cause: Unable to find the entity in storage.

Action: None.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25387: Rule fact for term {0} has been ignored as it does not have the correct type, {1}.

Cause: The fact from user or application had an incorrect data type.

Action: Provide the fact with the correct data type as indicated.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25388: Device named {0} of user {1} not found.

Cause: The user does not have a device with that name.

Action: Check username and device name.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25400: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25401: Unable to set the parameter {0} in the configuration because of exception {1}.

Cause: An exception has occurred while attempting to set the specified parameter in the configuration object.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25402: Could not find the value for the configuration parameter {0}, using default value.

Cause: There is no such entry for the parameter {0} in the configuration file.

Action: Check configuration parameter.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25403: Error in registering messaging Runtime MBeans.

Cause: Exception was thrown.

Action: Check stack trace

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25404: Error in unregistering messaging Runtime MBeans.

Cause: Exception was thrown.

Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25405: Naming exception thrown looking up Management Store: Unable to initialize SDP Messaging Runtime MBeans

Cause: Naming exception thrown while looking up the Management Store EJB.

Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25406: Create exception thrown while creating Management Store: Unable to initialize SDP Messaging Runtime MBeans.

Cause: Create exception thrown while creating Management Store EJB.

Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25407: Exception initializing Runtime MBean.

Cause: An exception was thrown during runtime MBean initialization.

Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25408: Invalid query parameter: query field: {0}, query condition: {1}, query value: {2}

Cause: Invalid combination of query parameters or invalid query value.

Action: Check stack trace.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25409: Unable to initialize the composite type for the MBean.

Cause: OpenDataException was caught.

Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25410: Unable to convert to composite type and return composite data for the MBean. Name: {0}

Cause: OpenDataException was caught.

Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25411: Unable to load Driver properties.

Cause: An exception has occurred while attempting to load the driver configuration properties.

Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25413: Could not find the value for the configuration parameter {0}, using default value.

Cause: There is no such entry for the parameter {0} in the configuration file.

Action: Check configuration parameter.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25414: Could not find the application deployment MBean for {0}

Cause: The application may not have started correctly.

Action: Check the application deployment status.

Level: 1

Type: WARNING

Impact: Process

SDP-25415: Found multiple application deployment MBeans for {0}

Cause: The application may not have started correctly.

Action: Check the application deployment status.

Level: 1

Type: WARNING

Impact: Process

SDP-25416: Error occurred while attempting to get the parent server MBean for {0}

Cause: An exception was thrown while attempting to get the parent server MBean.

Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-25500: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25502: Unable to create JNDI Context

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check the JNDI Context initialization parameters.

Level: 1

Type: ERROR

Impact: Configuration

SDP-25503: Unable to connect to the messaging server.

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check that the messaging server is up. Check the JNDI Context initialization parameters.

Level: 1

Type: ERROR

Impact: Configuration

SDP-25504: Unable to register application information with the messaging server.

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check that the messaging server is up. Check the JNDI Context initialization parameters.

Level: 1

Type: ERROR

Impact: Configuration

SDP-25505: Unable to enqueue outbound message.

Cause: Engine Sending Queue may not be available.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25506: Unable to get receiving queues from application information.

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check the Application information properties.

Level: 1

Type: ERROR

Impact: Configuration

SDP-25507: Unable to enqueue inbound message status because no engine queues were found.

Cause: The client is not aware of any engine queues to enqueue the status.

Action: Check that the application is registered successfully with the messaging server.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25508: Unable to enqueue inbound message status.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25509: An error occurred while notifying the MessageDispatcherBean about engine queues.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Configuration

SDP-25510: An error occurred while attempting to retrieve the actual password from the credential store.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Configuration

SDP-25511: An error occurred while dequeuing a message from the application receiving queue.

Cause: An invalid JMS message was dequeued by the Dispatcher MDB.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25512: An invalid message was dequeued from the application receiving queue: {0}

Cause: An invalid JMS message was dequeued by the Dispatcher MDB.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25513: JNDI lookup of application callback listener failed.

Cause: An invalid callback listener was previously registered and could not be invoked.

Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25514: An error occurred while dispatching an inbound message to the application.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25515: An error occurred while dispatching an inbound status to the application.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25516: Message/Status listener not configured. Suspending messaging client MDB to disable asynchronous message/status callbacks.

Cause: Message/Status listener was not configured by the application.

Action: If the application requires asynchronous message/status callbacks, configure the listener information. Otherwise, ignore this warning.

Level: 1

Type: WARNING

Impact: Configuration

SDP-25517: Messaging client MDB suspend failed: {0}

Cause: 1) The Messaging client was unable to access the MDB MBean because the container may not be in RUNNING state. 2) The server administrator username 'weblogic' does not exist.

Action: 1) Check the state of the container. Check the stack trace for more details. 2) Specify a valid server administrator username using the system property -Doracle.ums.admin.user and restart the server.

Level: 1

Type: WARNING

Impact: Configuration

SDP-25520: MessagingWebServiceClientImpl.send() operation failed.

Cause: An exception has occurred when invoking webservice send().

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25521: MessagingWebServiceClientImpl.receive() operation failed.

Cause: An exception has occurred while receiving messages from webservice.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25522: The application onMessage() callback operation failed.

Cause: An exception has occurred while attempting to call the application onMessage callback method.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25523: The application onStatus() callback operation failed.

Cause: An exception has occurred while attempting to call the application onStatus callback method.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25530: Creating Messaging EJB Client instance using Application information: {0}.

Cause: An application attempted to create a Messaging EJB Client instance.

Action: None

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-25531: Registering updated application information: {0}.

Cause: The application information changed.

Action: None

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-25532: An error occurred while retrieving the Application Information from the application JNDI context.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Configuration

SDP-25540: Unable to build a valid WSClient Application Name. Inbound messaging for this client may not work.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-25541: An error occurred while generating received message statuses.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25542: Security principal in client EJB Context "{0}" does not match security principal in ApplicationInfo "{1}". This may cause permission errors during future Messaging Client operations.

Cause: The security principal in the current EJBContext is different from the ApplicationInfo security principal field specified when creating the Messaging Client instance (or the default value, if no principal was provided).

Action: Ensure that the security principals used by this application for all Messaging Client operations match one another.

Level: 1

Type: WARNING

Impact: Security

SDP-25543: The current authenticated user "{0}" does not match the configured security principal "{1}".

Cause: The security principal in effect for the current thread is different from the security principal field specified when creating the Messaging Client instance.

Action: Ensure that the security principals used by this application for all Messaging Client operations match one another, or avoid configuring a specific security principal.

Level: 1

Type: WARNING

Impact: Security

SDP-25600: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25700: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25701: Unable to instantiate class {0}.

Cause: Unable to instantiate a class.

Action: Check to see if that class is in classpath or not.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25702: Unable to set content of Message object.

Cause: Unable to set content of a message.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25704: Error in setMultiplePayload.

Cause: An error occurred in setMultiplePayLoad().

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25705: Exception printing message content.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25706: Failed to clone message content.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25707: Failed to clone headers. Message = {0} .

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25708: Unable to perform JNDI lookup of JMS QCF: {0}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25709: Unable to perform JNDI lookup.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25710: Could not close JMS queue connection.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25711: Received unknown object: {0}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25712: Message received with invalid format: {0}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25713: Unable to perform JNDI lookup of JMS Queue: {0}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25714: Access control exception was caught. Name: {0} Action:{1}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25715: Invalid format, skipping: {0}

Cause: Invalid queue information.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25716: Error occurred in looking up QueueConnectionFactory in JNDI, skipping: {0}

Cause: Error occurred in looking up QueueConnectionFactory in JNDI.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25717: Error occurred in looking up Queue in JNDI, skipping: {0}.

Cause: Error occurred in looking up queue in JNDI.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25718: Error occurred in getQueueInfoList.

Cause: Error occurred in getQueueInfoList().

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25719: Failed to authenticate user {0}.

Cause: Failed to authenticate a user.

Action: Check username and password and try again.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25720: Sender Address is null or empty.

Cause: Sender Address has an error.

Action: Enter a valid non-null value for sender.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25721: Recipient Address is null or empty.

Cause: Recipient Address has an error.

Action: Enter a valid non-null value for Recipient.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25722: Message content is empty.

Cause: Message content was not set properly.

Action: Enter a valid non-null value for the content.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25723: Message object is null.

Cause: Message is null.

Action: Set a valid non-null value of Message object.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25724: Message subject and content are null.

Cause: Message subject and content.

Action: Enter a valid non-null value for subject and/or content.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25725: Message serialization failed.

Cause: Failed to serialize message due to unexpected I/O Error.

Action: Ensure that content is being created according to recommendations for Message class.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25726: Connection failed to remote host {0} using HTTP Proxy {1}. Error: {2}.

Cause: There was a problem with either the remote host or the HTTP Proxy. Check the associated connection error for the exact cause.

Action: Check the value of the remote host and the HTTP Proxy settings.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25727: Unable to create JMS QueueSender, {0}. Cause: There was a problem in the connection to the JMS provider.

Cause: There was a problem in the connection to the JMS provider.

Action: Check the container log for additional errors from the JMS adapter.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-25728: Could not determine server platform type. Generic values will be used for platform-specific data.

Cause: The Java EE server platform could not be determined. Either this application is executing in a Java SE environment, or the Java EE server is configured incorrectly.

Action: If executing in a Java SE environment, no action is necessary. Otherwise ensure that Java Required Files module is deployed to this environment.

Level: 1

Type: NOTIFICATION

Impact: Configuration

SDP-25729: An exception occurred while enabling the WS-Security configuration: {0}

Cause: An exception occurred while attaching a WS-Security policy to a web service client or endpoint.

Action: Ensure that any WS-Security policies are specified in the correct format.

Level: 1

Type: WARNING

Impact: Security

SDP-26000: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26001: Cannot create JNDI Context.

Cause: Cannot create JNDI Context.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26002: Dispatcher got a message: id ({0}) from ({1}) to ({2}), subject ({3}) content ({4}).

Cause: None

Action: None

Level: 1

Type: TRACE

Impact: Requests/Responses

SDP-26003: Dispatcher sent message with id: {0}.

Cause: None

Action: None

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26004: No Messaging Engine Queue information to enqueue status.

Cause: No Engine Queue information to enqueue status.

Action: Check the stack trace for more details. Check Engine Queue information.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26005: Dispatcher failed to find a driver.

Cause: Dispatcher failed to find a driver.

Action: Compare delivery type and content type between message and available drivers.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26006: Exception while dispatching message to driver resource adapter.

Cause: Exception while dispatching message to driver resource adapter.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26007: Received inbound queue information from messaging engine: {0}

Cause: None

Action: None

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26008: An exception occurred while attempting to parse a Message: {0}.

Cause: None

Action: None

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26009: Could not get JNDI InitialContext.

Cause: None

Action: None

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26010: Unable to start driver: {0}.

Cause: Unable to start driver.

Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26011: Failed to invoke registerDriverInfo().

Cause: Exception thrown while invoking registerDriverInfo().

Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26012: unable to remove scheduled workers

Cause: An exception has occurred while removing a driver thread.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26013: Unable to cleanly stop driver: {0}.

Cause: Unable to cleanly stop driver.

Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26014: Unable to process inbound message/status.

Cause: Exception occurred while processing inbound message/status.

Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26015: Unable to process command message.

Cause: Exception occurred while processing command message.

Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26017: Attempting to register driver {0}.

Cause: None

Action: None

Level: 16

Type: TRACE

Impact: Process

SDP-26018: Located {0} DriverConnectionFactory successfully.

Cause: None

Action: None

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26019: Error occurred while registering driver.

Cause: Error occurred while registering driver.

Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26020: Registration of driver {0} succeeded.

Cause: None

Action: None

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26021: Timed out while waiting for reply from Messaging engine.

Cause: The registration command timed out in the JMS queue because the Messaging engine is down or the system is under heavy load.

Action: Check if the Messaging engine is up and ensure the system is not under extremely heavy load.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26022: Illegal DeliveryType specified, ignoring type {0}. Exception: {1}

Cause: Illegal DeliveryType specified.

Action: Check message delivery type.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26023: Benchmark logging is enabled for all inbound messages, which may slow down system performance. To disable it, unset environment variable sdpm_inbound_benchmark_logging and restart.

Cause: Benchmark logging is enabled when environment variable sdpm_inbound_benchmark_logging=true.

Action: To disable benchmark logging, unset environment variable sdpm_inbound_benchmark_logging and restart.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26024: Registration of driver {0} did not complete; will retry periodically until messaging server responds.

Cause: None

Action: None

Level: 1

Type: WARNING

Impact: Process

SDP-26025: Error in registering messaging driver Runtime MBeans.

Cause: Exception was thrown.

Action: Check stack trace

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26026: Error in unregistering messaging driver Runtime MBeans.

Cause: Exception was thrown.

Action: Check stack trace

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26027: Ignoring property {0} with unsupported Java type {1} during driver initialization.

Cause: A property with an unsupported Java type was found in 'configuration/driverconfig.xml' during driver initialization.

Action: Use one of the following valid Java types: java.lang.Boolean, java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, java.lang.Float, java.lang.Character

Level: 1

Type: WARNING

Impact: Configuration

SDP-26028: Ignoring property {0} with invalid value {1} and/or Java type {2} during driver initialization.

Cause: A property with an invalid value and/or unsupported Java type was found in 'configuration/driverconfig.xml' during driver initialization.

Action: Use a valid value and/or one of the following valid Java types: java.lang.Boolean, java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, java.lang.Float, java.lang.Character

Level: 1

Type: WARNING

Impact: Configuration

SDP-26029: Unable to load driver configuration properties from 'configuration/driverconfig.xml'.

Cause: An exception occurred while attempting to load the driver configuration properties from 'configuration/driverconfig.xml'.

Action: Check the stack trace.

Level: 1

Type: ERROR

Impact: Configuration

SDP-26030: Unable to schedule worker used to attempt driver registration.

Cause: An exception occurred while scheduling a worker to attempt driver registration.

Action: Check the stack trace.

Level: 1

Type: WARNING

Impact: Process

SDP-26031: Lookup of encoded credential value {0} in the credential store for property {1} failed during driver initialization. Passing through the value as-is.

Cause: A property with an invalid encoded credential value was found in 'configuration/driverconfig.xml' during driver initialization.

Action: Use a valid encoded credential value and ensure the application has permission grants to access the credential store.

Level: 1

Type: WARNING

Impact: Configuration

SDP-26032: JNDI lookup of driver connection factory {0} failed with the following error message: {1}. Will retry until successful.

Cause: Driver connection factory could not be located in JNDI. Driver registration will not occur until this lookup succeeds.

Action: Wait for server startup to proceed. If driver registration does not occur, ensure that the driver connection factory JNDI name is configured correctly.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26033: Started messaging driver: {0}

Cause: Driver was started.

Action: None.

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26034: Stopped messaging driver: {0}

Cause: Driver was stopped.

Action: None.

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26035: JNDI lookup of server command endpoint {0} failed with the following error message: {1}. Will retry until successful.

Cause: Messaging Server command module could not be located in JNDI. Driver registration will not occur until this lookup succeeds.

Action: Wait for server startup to proceed. If driver registration does not occur, ensure that the messaging server is deployed and started.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26036: Receiver received message with id: {0}.

Cause: None

Action: None

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26100: An unexpected exception was caught.

Cause: An unexpected exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26101: Content type parsing error {0}.

Cause: Error occurred while trying to parse the content type.

Action: Check and see if the content type is specified correctly.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26102: Error while writing e-mail message content.

Cause: An exception has occurred while writing e-mail content and headers to an e-mail message.

Action: Check stack trace or error log.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26103: Error while writing e-mail subject.

Cause: Cannot write the subject.

Action: Check stack trace or error log.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26104: Recipient address error.

Cause: Recipient e-mail address has an error.

Action: Check and see if the recipient e-mail address is correct.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26105: unable to deliver to following address(es): {0} Reason: {1}

Cause: One or more recipient e-mail addresses had an error.

Action: Ensure that the e-mail address is correct.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26106: failed to send the e-mail message

Cause: Unable to login to SMTP server.

Action: Check SMTP server host name, port, user name, and password.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26107: failed to add header - name: {0} value: {1}

Cause: Unable to add an e-mail header to a multipart message

Action: Check the stack trace or error log.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26108: failed to initialize e-mail driver

Cause: Could not initialize Email Driver.

Action: Check stack trace or error log. Check e-mail driver parameters and make sure all e-mail servers are up.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26109: Caught exception while closing connection to e-mail server.

Cause: An exception was caught while closing connection.

Action: Check stack trace or error log.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26110: Starting Email Driver failed.

Cause: Could not start Email Driver.

Action: Check stack trace or error log. Check e-mail driver parameters and make sure all servers are up.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26111: Could not remove listener from Email Driver

Cause: Could not remove listener from Email Driver

Action: Check stack trace or error log

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26112: Null protocol error

Cause: Protocol was null.

Action: Specify an appropriate protocol for this driver.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26113: No incoming e-mail server.

Cause: Incoming server was not set.

Action: Set incoming server parameters.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26114: Username is missing.

Cause: Username was not set.

Action: Set the username in e-mail driver parameters.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26115: failed to receive an inbound e-mail message

Cause: An exception has occurred while receiving an inbound e-mail message.

Action: Check stack trace or error log.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26116: Protocol {0} is not supported.

Cause: An unsupported protocol was provided.

Action: Check the e-mail protocol name in e-mail driver parameters.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26117: Connection information of the inbound e-mail server is missing. Check the server host name, user name, and password.

Cause: Connect information was missing or incomplete.

Action: Provide the required connection information.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26118: failed to open folder: {0}

Cause: Folder name is not correct or does not exist.

Action: Check folder name spelling.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26119: Max retry limit reached for trying to connect to user {0}

Cause: Email driver has reached Max retry limit to connect to user.

Action: Check stack trace or error log. Check e-mail driver parameters and make sure all servers are up.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26120: IMAP server failed to expunge e-mail messages. mail box: {0}

Cause: An exception was caught when doing expunge.

Action: Check stack trace or error log. Check e-mail driver parameters and make sure all servers are up.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26121: Attempt to reconnect {0}. Error Count: {1} Retry Count: {2}.

Cause: Attempt to reconnect to the incoming e-mail server

Action: Check e-mail driver parameters and make sure all servers are up.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26122: An exception has been thrown when connecting to user {0}

Cause: Email driver could not connect to user.

Action: Check username and password. Make sure the user exists and is accessible.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26123: Could not initialize Email Store for user {0}

Cause: Could not initialize Email Store for user.

Action: Check stack trace or error log. Check username and password.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26124: invalid folder: {0}

Cause: An invalid folder name was specified.

Action: Check and see if the specified folder is valid and accessable.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26125: An exception has occurred while sending out a message.

Cause: An exception occurred while sending out a message.

Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26126: unrecoverable message - {0}

Cause: failed to recover an e-mail message

Action: Check stack trace or error log.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26127: Collision on e-mail message polling. Pausing for {0} seconds.

Cause: Multiple e-mail drivers polling the same e-mail account at the same time.

Action: (None)

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26128: A duplicate inbound e-mail message has been discarded: gateway message ID: {0}, recipient addresses: {1}, subject: {2}.

Cause: A duplicate message was detected and discarded by the e-mail receiver.

Action: (None)

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26129: unable to deliver to following addresses: {0} Reason: {1}

Cause: Recipient e-mail address was valid but sending failed for reason indicated in error message.

Action: Ensure that e-mail driver and SMTP server are operational and configured correctly, baed on information provided in error message.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26150: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26151: Failed to process a received message in SMPP driver, because driver context is null

Cause: Driver context is null

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26152: WorkManager object is null in SMPP driver.

Cause: The caller of setWorkManager() passed in a null WorkManager object as an argument

Action: Make sure WorkManager object is not null.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26153: Received status message with incorrect format.

Cause: The status received from SMSC does not have message ID or state.

Action: Correct the SMSC.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26154: Failed to process received status in SMPP driver, because driver context is null.

Cause: Driver Context is null

Action: Check driver context.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26155: unable to initialize SMPP driver, because a driver attribute, sms.account.id, is not set.

Cause: The account ID was not set.

Action: Set the correct account information.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26156: Failed to initialize SMPP Driver because driver attributes sms.server.host, sms.server.transmitter.port or sms.server.receiver.port is not set.

Cause: SMSC server or account information is not correct or missing.

Action: Check those parameters.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26157: SMPP driver failed to send out a message, because Message object is null.

Cause: Null message object.

Action: Check the caller of this method.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26158: Caught exception while closing connection

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26159: Illegal data length value from SMSC received and ignored: {0}

Cause: SMPP Driver has detected a corrupted data field from SMSC and it is trying to recover.

Action: This error suggests communication errors between SMPP driver and SMSC. Check to see if this driver supports that SMSC.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26160: SMPP Driver not configured. Configure and restart this driver. Required Properties: SmsAccountId, SmsServerHost, TransmitterSystemId, ReceiverSystemId, TransmitterSystemType, ReceiverSystemType, TransmitterSystemPassword, ReceiverSystemPassword, ServerTransmitterPort, ServerReceiverPort.

Cause: SMPP Driver was not configured.

Action: Configure and restart this driver. Required Properties: SmsAccountId, SmsServerHost, TransmitterSystemId, ReceiverSystemId, TransmitterSystemType, ReceiverSystemType, TransmitterSystemPassword, ReceiverSystemPassword, ServerTransmitterPort, ServerReceiverPort.

Level: 1

Type: ERROR

Impact: Configuration

SDP-26161: Starting SMPP Driver: {0}

Cause: SMPP Driver resource adapter initialization.

Action: None

Level: 1

Type: NOTIFICATION

Impact: Configuration

SDP-26162: Message content could not be decoded using character set {0}

Cause: The message content retrieved from the SMSC could not be decoded using the specified character set.

Action: Ensure that the Default Encoding configuration parameter is correct.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26163: Data stream ended unexpectedly while reading packet from SMSC

Cause: The data stream ended unexpectedly while reading a packet from the SMSC. Message or command will be dropped.

Action: None.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26164: Failed to bind receiver connection; will retry until bind operation is successful.

Cause: Could not bind to the SMSC as a receiver. Bind operation will be retried periodically until it is successful.

Action: None required. Change value of configuration parameter "BindRetryDelay" to adjust retry interval.

Level: 1

Type: WARNING

Impact: Requests/Responses

SDP-26200: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26201: Unable to remove listener from XMPPDriver.

Cause: Unable to remove listener from XMPPDriver .

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26202: Unable to shut down XMPPDriver.

Cause: Unable to shut down XMPPDriver.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26203: XMPP Driver not configured. Configure and restart this driver. Required properties: IMServerHost, IMServerUsername, IMServerPassword.

Cause: XMPP Driver was not configured.

Action: Configure and restart this driver. Required properties: IMServerHost, IMServerUsername, IMServerPassword.

Level: 1

Type: ERROR

Impact: Configuration

SDP-26204: Error occurred while initializing {0}

Cause: Error occurred while initializing driver instance.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26205: Driver, {0}, initialization succeeds.

Cause: Driver initialization succeeds.

Action: Check the stack trace for more details.

Level: 16

Type: TRACE

Impact: Process

SDP-26206: Driver, {0}, initialization fails.

Cause: Driver initialization fails.

Action: Check the stack trace for more details.

Level: 16

Type: TRACE

Impact: Process

SDP-26207: Invalid value for im.retry.limit. Value reset to default - {0}

Cause: Invalid value for im.retry.limit. Value reset to default

Action: Specify a valid value for im.retry.limit

Level: 1

Type: NOTIFICATION

Impact: Configuration

SDP-26208: Invalid value for im.retry.interval. Value reset to default - {0} seconds

Cause: Invalid value for im.retry.interval. Value reset to default.

Action: Specify a valid value for im.retry.interval

Level: 1

Type: NOTIFICATION

Impact: Configuration

SDP-26209: Unable to initialize accounts

Cause: Unable to initialize accounts.

Action: Check username, password and IM server.

Level: 1

Type: ERROR

Impact: Configuration

SDP-26210: Unable to connect to XMPP server: {0}

Cause: Check the associated stack trace for the cause of the connection failure.

Action: Check the XMPP server hostname and port parameters and make sure the server is up.

Level: 1

Type: ERROR

Impact: Configuration

SDP-26212: Shut down complete

Cause: Shut down complete.

Action: None

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26213: Exception while sending message - from: {0} to: {1}.

Cause: Exception while sending message.

Action: Check stack trace and recipient address

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26214: Caught an exception in XMPP driver while sending out a message.

Cause: An unexpected exception was caught.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26215: The XMPP driver has no previous account to replace.

Cause: No previous XMPP (IM) account was found. Unable to replace previous account.

Action: None

Level: 1

Type: WARNING

Impact: Configuration

SDP-26216: No accounts defined in XMPP driver.

Cause: No XMPP accounts defined.

Action: Define a valid XMPP (IM) account.

Level: 1

Type: ERROR

Impact: Configuration

SDP-26217: Could not locate an account to deliver this message from sender {0}. Using the first account ( {1} ) to deliver this message.

Cause: Could not locate an account to deliver this message.

Action: To retain the original message sender, add sender of the message to 'user' configuration property of the driver.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26218: I/O problem using HTTP Proxy {0} for account: {1}

Cause: The connection with the HTTP Proxy was broken.

Action: Check stack trace for more information. Check HTTP Proxy settings to see if proxy is correct and reachable.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26219: Server DNS problem with account: {0}

Cause: The hostname could not be resolved by DNS.

Action: Check the stack trace, account parameters, and DNS server.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26220: Server I/O problem with account: {0}

Cause: The connection with the XMPP server was broken.

Action: Check the account parameters and the network connection.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26221: Third-party transport connectivity is no longer supported. Ignoring all applicable configuration properties.

Cause: This is an upgraded XMPP Driver instance making use of third-party transport connectivity that is no longer supported in this version.

Action: None

Level: 1

Type: WARNING

Impact: Configuration

SDP-26222: Agent registration failed for {0}. Error Code: {1}

Cause: Agent registration failed.

Action: Check error code and from address.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26223: Fatal Error on Presence object build.

Cause: Fatal Error on Presence object build.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26224: Exception managing presence

Cause: Exception managing presence.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26225: Received Error Message. Code: {0} Text: {1}.

Cause: Received Error Message.

Action: Check error code and error message.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26226: Unauthorized login to Jabber/XMPP server: {0}

Cause: Invalid username and/or password was supplied.

Action: Check username and password.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26227: New account registration failed. It appears that the Jabber/XMPP server does not allow automatic registration. Contact the server administrator for a new account. Now disconnecting from server: {0}

Cause: New account registration failed. It appears that the Jabber/XMPP server does not allow automatic registration.

Action: Contact the server administrator for a new account.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26228: New account registration failed. Either this account already exists and you have entered an incorrect password or there is a problem with the Jabber/XMPP server. Now disconnecting from server: {0}

Cause: New account registration failed. Either this account already exists and you have entered an incorrect password or there is a problem with the Jabber/XMPP server.

Action: Check that the specified account does not exist. Check that your password is valid

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26229: Plaintext authentication failed; disconnecting from server: {0}

Cause: Plaintext authentication failed.

Action: Check username and password and check with the Jabber/XMPP server administrator.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26230: Digest authentication failed. Attempting plain-text authentication: {0}

Cause: Digest authentication failed.

Action: Digest authentication failed. Check with the Jabber/XMPP server administrator.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26231: InfoQuery packet:

Cause: None

Action: None

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26232: Presence packet:

Cause: None

Action: None

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26233: Message packet:

Cause: None

Action: None

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26234: Disconnecting from Jabber/XMPP server: {0}. Cause: 1) The account was disconnected by the XMPP server due to another conflicting login. 2) The XMPP server went offline. Action: 1) Identify and shut down the conflicting XMPP driver that is using the same account. 2) Check the status of the XMPP server.

Cause: 1) The account was disconnected by the XMPP server due to another conflicting login. 2) The XMPP server went offline.

Action: 1) Identify and shut down the conflicting XMPP driver that is using the same account. 2) Check the status of the XMPP server.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26235: Account disconnected: {0}. Cause: I/O or authentication error. Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.

Cause: The account was disconnected from the server either due to I/O or authentication error.

Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26236: Got an unexpected exception when receiving a message.

Cause: Got an exception when receiving a message.

Action: Check to see if the message is well-formed.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26237: The call for conversion does not supply account information. The first account is being used for conversion.

Cause: The call for conversion did not supply the necessary account information.

Action: Provide the correct account information.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26238: cannot deliver to this {0} user, because {0} transport is not enabled in the driver. Set the value for driver parameter: {1}.

Cause: Because transport was not enabled in the driver, delivery could not be made to the Yahoo, MSN, AOL, or ICQ user.

Action: Enable the transport in the driver.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26239: Invalid network name in address: {0}

Cause: Invalid network name in address

Action: Specify a valid network name in address.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26240: Max Retry Limit ( {0} ) is reached. Restart the driver to try reconnecting for account {1}.

Cause: The Max Retry Limit was reached while attempting to reconnect.

Action: Restart the XMPP driver to try again.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26241: Reconnecting now... attempt #{0} for account {1}.

Cause: None

Action: None

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26242: Reconnecting in {0} seconds for account {1}.

Cause: None

Action: None

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26243: Account {0} is disconnected from the server at the request of the driver.

Cause: None.

Action: None.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26244: Missing value for parameters {0} and/or {1}.

Cause: None

Action: None

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26245: Could not initialize XMPPDriver.

Cause: XMPPDriver was misconfigured.

Action: Check driver parameters, account information and Jabber/XMPP server.

Level: 1

Type: ERROR

Impact: Process

SDP-26246: Caught exception while closing connection of XMPP server.

Cause: Caught exception in XMPP driver while closing server connection.

Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-26247: Caught exception while closing connection.

Cause: Caught exception while closing connection.

Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26248: Account disconnected: {0}. Cause: Unknown. Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.

Cause: The account was disconnected from the server due to an unknown error.

Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26249: Account connected: {0}

Cause: The driver successfully connected to the server for this account.

Action: None.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26250: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26251: Could not initialize Proxy Driver

Cause: Could not initialize Proxy Driver.

Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26252: Error occurred while initializing Proxy Driver: DriverConnection returned by DriverConnectionFactory is null.

Cause: DriverConnection returned by DriverConnectionFactory was null

Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26254: Failed to initialize Proxy Driver with GatewayURL={0} and Username={1}. Check driver configuration properties and remote gateway, and restart the driver.

Cause: Failed to initialize Proxy Driver with the specified GatewayURL, Username and Password.

Action: Check stack trace or error log. Check Proxy Driver properties: GatewayURL, Username and Password. Also check the status of the remote gateway.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26255: Exception occurred while initializing Proxy Driver

Cause: Exception occurred while initializing Proxy Driver

Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26256: Proxy Driver has not been configured. Configure and restart this driver. Required Property: GatewayURL.

Cause: Proxy Driver was not configured.

Action: Configure and restart this driver. Required Property: GatewayURL.

Level: 1

Type: ERROR

Impact: Configuration

SDP-26257: Exception occurred while invoking Proxy Driver remote request

Cause: Exception occurred while invoking Proxy Driver remote request

Action: Check stack trace or error log. Check Proxy Driver configuration and remote gateway.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26350: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26351: VoiceXML Driver property VoiceXMLReceiveURL is empty.

Cause: VoiceXMLReceiveURL was not set and could not be dynamically generated.

Action: Check the validity of the VoiceXMLReceiveURL property. Ensure the host and port are that of the server where this driver is deployed.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26352: VoiceXMLDriver: VoiceXMLOutboundServletURI cannot be null

Cause: VoiceXMLOutboundServletURI is null

Action: Assign proper value for Outbound Servlet URL.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26353: VoiceXMLDriver::Deliver: Message URL = {0}

Cause: None

Action: None

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26354: VoiceXMLDriver::Deliver: URL sent to Voice Gateway = {0}

Cause: None

Action: None

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26355: VoiceXMLDriver::Deliver: Reply message = {0}

Cause: None

Action: None

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

SDP-26356: VoiceXMLDriver: Socket error from VoiceXML Gateway.

Cause: Socket Error from the Gateway

Action: Check VoiceXML server URL and the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26357: VoiceXMLDriver could not initialize.

Cause: Initialization failed.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26358: VoiceXMLDriver: Exception while processing the HTTP request.

Cause: Exception while processing the HTTP request

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26359: VoiceXMLDriver: Caught exception while closing connection

Cause: Caught exception while closing connection

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26360: VoiceXML Driver not configured. Configure and restart this driver. Required Properties: VoiceXMLOutboundServletURI.

Cause: VoiceXML Driver was not configured.

Action: Configure and restart this driver. Required Properties: VoiceXMLOutboundServletURI.

Level: 1

Type: ERROR

Impact: Configuration

SDP-26400: An unexpected exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26401: Messaging Worklist Driver not configured. Configure and restart this driver. Required Properties: BPELConnectionURL.

Cause: Messaging Worklist Driver was not configured.

Action: Configure and restart this driver. Required Properties: BPELConnectionURL.

Level: 1

Type: ERROR

Impact: Configuration

SDP-26450: An unexpected exception was caught.

Cause: An unexpected exception has occurred.

Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Requests/Responses

SDP-26451: One or more sets of extension endpoints were configured using identical protocols and mapped domains: {0}. The first endpoint listed in the configuration file will be used.

Cause: Each of the listed protocol/domain pairs is used to configure multiple extension endpoints.

Action: Remove the conflicting endpoint configuration, or ensure that each endpoint has unique protocol and mapped domain parameters.

Level: 1

Type: WARNING

Impact: Configuration

SDP-26452: No extension endpoint could be found for the specified recipient address.

Cause: None of the configured extension endpoints matched the protocol and domain of the message recipient.

Action: Ensure that an endpoint is configured for the desired protocol and domain, or configure a default (empty) domain.

Level: 1

Type: NOTIFICATION

Impact: Configuration

SDP-26453: No configuration element was found for this Extension Driver deployment. Create a configuration and restart this Extension Driver.

Cause: No configuration element was found for this Extension Driver deployment.

Action: Create a configuration and restart this Extension Driver.

Level: 1

Type: ERROR

Impact: Configuration

SDP-26454: Extension Driver not configured. Configure and restart this driver. The configuration must contain at least one Extension endpoint with a valid endpoint URL and protocol.

Cause: Extension Driver was not configured.

Action: Configure and restart this driver. The configuration must contain at least one Extension endpoint with a valid endpoint URL and protocol.

Level: 1

Type: ERROR

Impact: Configuration

SDP-26455: Error while processing Extension Driver configuration for property group with Endpoint URL: {0}. Check the corresponding property group configuration, then restart this driver. The configuration must contain an Extension endpoint with a valid endpoint URL and protocol.

Cause: An error occurred while processing the Extension Driver configuration.

Action: Check the corresponding property group configuration, then restart this driver. The configuration must contain an Extension endpoint with a valid endpoint URL and protocol.

Level: 1

Type: WARNING

Impact: Configuration