36 SDP-25001 to SDP-26551

SDP-25001: An exception was caught.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

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: Process

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: Process

SDP-25004: Message could not be delivered to client due to rollback at the client application. Message ID {0}.: Cause: The client did rollback on the transaction, hence the message could not be re-delivered to the client.; Action: Check why the client did rollback
Level: 1

Type: WARNING

Impact: Process

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: Process

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: Process

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: WARNING

Impact: Process

SDP-25008: An error occurred while processing an outbound message.: Cause: An exception has occurred while processing the outbound message.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25009: An error occurred while storing a message.: Cause: An exception has occurred while processing the message.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25010: An error occurred while sending an outbound message.: Cause: An exception has occurred while processing the outbound message.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25011: An error occurred while transforming an outbound message.: Cause: An exception has occurred while processing the outbound message.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25012: An error occurred while processing error statuses.: Cause: An exception has occurred while processing error statuses.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25013: An error occurred while resending an outbound message.: Cause: An exception has occurred while processing the resent outbound message.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25014: A JMS exception occurred, trying to recover: Cause: A JMS exception occurred; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25015: There are no transformed messages of message {0} for recipients {1}. Skipping message delivery to these recipients.: Cause: An error has occurred while transforming an outbound message.; Action: Use the messageId to trace the message handling.
Level: 1

Type: WARNING

Impact: Process

SDP-25016: Could not get TimerService or Timers.: Cause: Could not get TimerService or Timers.; Action: Check application server status.
Level: 1

Type: ERROR

Impact: Process

SDP-25017: Could not cancel timer.: Cause: Could not cancel timer; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25020: Unable to schedule a timed failover event.: Cause: An exception has occurred while scheduling a timed failover event.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25021: An error occurred while processing a timed failover event.: Cause: An exception has occurred while processing a timed failover event.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25022: Unable to schedule a timed resend event.: Cause: An exception has occurred while scheduling a timed resend event.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25030: Unable to schedule a timer to refresh the driver locator cache.: Cause: An 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: Process

SDP-25032: An error occurred while registering driver information {0}.: Cause: An exception has occurred while registering the driver information.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25033: An error occurred while unregistering driver information {0}.: Cause: An exception has occurred while unregistering the driver information.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

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: Process

SDP-25035: Messaging store not found.: Cause: An 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-25036: An error occurred while registering driver information at User preference subsystem {0}.: Cause: An exception has occurred while registering the driver information at User preference subsystem.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25037: An error occurred while unregistering driver information at User preference subsystem {0}.: Cause: An exception has occurred while unregistering the driver information at User preference subsystem.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25040: Unable to create an instance of CommandReceiverBean.: Cause: An exception has occurred while attempting to process a command.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25042: An error occurred while processing a command message.: Cause: An exception has occurred while attempting to process a command.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

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: Process

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: Process

SDP-25057: An error occurred while processing an inbound JMS message.: Cause: The inbound JMS message does not contain a valid message.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25058: An error occurred while processing an inbound message.: Cause: An exception has occurred while processing the inbound message.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

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: Process

SDP-25060: There is no application that has registered this address as an access point. The message will be delivered when the access point is registered. Address={0}: Cause: There is no application that has registered this recipient address as an access point.; Action: Register the access point. The message is kept in a pending queue until an application registers a corresponding access point.
Level: 1

Type: WARNING

Impact: Process

SDP-25061: An error occurred while processing inbound message statuses.: Cause: An exception has occurred while attempting to process inbound message statuses.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25063: Status not delivered to client since no client information found for application {0}.: Cause: There is no application client information stored.; Action: Check the log file for additional information.
Level: 1

Type: WARNING

Impact: Process

SDP-25064: An error occurred while recording a status processing update.: Cause: An exception has occurred while attempting to record a status processing update.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25065: An 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: WARNING

Impact: Process

SDP-25066: An error occurred while processing an outbound message status.: Cause: An exception has occurred while attempting to process an outbound message status.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

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: Process

SDP-25081: An error occurred while adding a message converter rule: {0}.: Cause: An invalid message converter rule was provided.; Action: Check the log file for additional details.
Level: 1

Type: WARNING

Impact: Process

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 log file for additional details.
Level: 1

Type: WARNING

Impact: Process

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: WARNING

Impact: Process

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: Process

SDP-25087: No matching driver found for {0} = {1}.: Cause: No matching driver found for the given property.; Action: Check that there is a correctly deployed and configured driver matching the given property.
Level: 1

Type: WARNING

Impact: Process

SDP-25088: Unable to refresh the driver locator cache, due to exception.: Cause: An 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: Process

SDP-25089: Status could not be delivered to client due to rollback at the client application. Message ID {0} {1}.: Cause: The client did rollback on the transaction, hence the status could not be re-delivered to the client.; Action: Check why the client did rollback
Level: 1

Type: WARNING

Impact: Process

SDP-25101: Caught a database exception.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

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: Process

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: Process

SDP-25109: Failed to initialize persistence context.: Cause: An exception has occurred while initializing the persistence context.; Action: Check the stack trace for more details.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25202: Parameter {0} is missing in SOAPMessageContext sent from client. Generating default value.: Cause: The client application sent a message without required attribute.; Action: Make sure the client application add ApplicationName, ApplicationInstanceName, and ClientType to the SOAPMessageContext.
Level: 1

Type: WARNING

Impact: Process

SDP-25250: An exception was caught.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

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: Process

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: Process

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: Process

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: Process

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: Process

SDP-25256: Parameter {0} is missing in SOAPMessageContext sent from client. Generating default value.: Cause: The client application sent a message without required attribute.; Action: Make sure the client application add ApplicationName, ApplicationInstanceName, and ClientType to the SOAPMessageContext.
Level: 1

Type: WARNING

Impact: Process

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: Process

SDP-25300: An exception was caught.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

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: Process

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: Process

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: Process

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: Process

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: Process

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: Process

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: Process

SDP-25308: The file, {0}, cannot be read.: Cause: The file cannot be read.; Action: Check the file.
Level: 1

Type: ERROR

Impact: Process

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: Process

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: Process

SDP-25312: Provisioning Exception was caught.: Cause: Provisioning Exception was caught.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

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: Process

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: Process

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: Process

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: Process

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: Process

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: Process

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: Process

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: Process

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: Process

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: Process

SDP-25325: Cannot serialize Rule Session.: Cause: Cannot serialize Rule Session, which is not critical.; Action: No action needed.
Level: 1

Type: WARNING

Impact: Process

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: Process

SDP-25327: Cannot create Rule Session.: Cause: Cannot create Rule Session.; Action: No action needed.
Level: 1

Type: WARNING

Impact: Process

SDP-25328: UserPrefsException was caught.: Cause: UserPrefsException was caught.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

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: Process

SDP-25330: Business Term Type has changed. Term = {0}.: Cause: Business Term Type has changed.; Action: Recheck the Preference Rules.
Level: 1

Type: WARNING

Impact: Process

SDP-25331: Cannot instantiate User Preferences Services.: Cause: Cannot instantiate User Preferences Services due to an initialization error.; Action: Check User Prefs Services configuration.
Level: 1

Type: WARNING

Impact: Process

SDP-25334: Device name is null.: Cause: Device name is null.; Action: Provide a valid Device name.
Level: 1

Type: ERROR

Impact: Process

SDP-25336: Input parameter, UserPrefsObject, is null.: Cause: Required parameter, UserPrefsObject, is null.; Action: Provide a valid UserPrefsObject.
Level: 1

Type: ERROR

Impact: Process

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: Process

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: Process

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: Process

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: Process

SDP-25345: Runtime exception was caught.: Cause: Runtime exception was caught.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

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: Process

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: Process

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: Process

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: Process

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: Process

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: Process

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: Process

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: Process

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: Process

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: WARNING

Impact: Process

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: Process

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: Process

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: Process

SDP-25390: Failed to set default address of MESSAGING of user {0}.: Cause: Failed to set default address; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25400: An exception was caught.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25403: Error in registering messaging Runtime MBeans.: Cause: Exception was thrown.; Action: Check stack trace
Level: 1

Type: ERROR

Impact: Process

SDP-25404: Error in unregistering messaging Runtime MBeans.: Cause: Exception was thrown.; Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

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: Process

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: Process

SDP-25407: Exception initializing Runtime MBean.: Cause: An exception was thrown during runtime MBean initialization.; Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

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: Process

SDP-25409: Unable to initialize the composite type for the MBean.: Cause: OpenDataException was caught.; Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

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: 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: Failed to schedule Timer.: Cause: Timer could not be scheduled in the TimerManager; Action: Check stack trace, diagnostic dump
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25501: Exception when delivering pending messages.: Cause: Exception when delivering pending messages; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

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: Process

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: Process

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: Process

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: Process

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: Process

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: Process

SDP-25508: Unable to enqueue inbound message status.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

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: Process

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: Process

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: WARNING

Impact: Process

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: Process

SDP-25514: An error occurred while dispatching an inbound message to the application {0}.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25515: An error occurred while dispatching an inbound status to the application {0}.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

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: Process

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: Process

SDP-25519: QueueWorker rejected.: Cause: QueueWorker rejected; Action: Check WorkManager configuration.
Level: 1

Type: ERROR

Impact: Process

SDP-25524: Client called the deprecated method acknowledge().: Cause: The method acknowledge is deprecated.; Action: Use global transactions instead to achieve reliable message reception.
Level: 1

Type: WARNING

Impact: Process

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: Process

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: Process

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: Process

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: Process

SDP-25700: An exception was caught.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

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: Process

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: WARNING

Impact: Process

SDP-25703: Exception when getting cluster name for server {0}.: Cause: Could not get cluster name from RuntimeServiceMBean; Action: Check the stack trace for more details
Level: 1

Type: ERROR

Impact: Process

SDP-25704: Error in setMultiplePayload.: Cause: An error occurred in setMultiplePayLoad().; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25705: Exception printing message content.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25706: Failed to clone message content.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25707: Failed to clone headers. Message = {0}.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

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: Process

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: Process

SDP-25710: Exception caught when calling onMessage(), will rollback transaction.: Cause: Exception caught when calling onMessage(), will rollback transaction.; Action: Check log to get more information.
Level: 1

Type: WARNING

Impact: Process

SDP-25711: Received unknown object: {0} on queue {1}.: Cause: Received unknown object in JMS queue; Action: Check log to get more information.
Level: 1

Type: WARNING

Impact: Process

SDP-25712: Message received with invalid format: {0} on queue {1}.: Cause: Invalid message received on JMS queue; Action: Check log to get more information.
Level: 1

Type: ERROR

Impact: Process

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: Process

SDP-25714: Failed to obtaining destination availability for queue with JNDI name: {0}.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25715: Invalid format, skipping: {0}.: Cause: Invalid queue information.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

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: Process

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: Process

SDP-25718: Error occurred in getQueueInfoList.: Cause: Error occurred in getQueueInfoList().; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25719: The JMS receiver could not connect to the JMS destination. The error was: {1}. Please ensure the destination is available at the JNDI name {0}. The JMS receiver will periodically attempt to resolve this destination and additional warnings may be issued.: Cause: The JMS receiver could not connect to the JMS destination.; Action: Check the JMS system resource and the JMS server for additional information.
Level: 1

Type: WARNING

Impact: Process

SDP-25725: Message serialization failed.: Cause: Failed to serialize message due to I/O Error.; Action: Ensure that content is being created according to recommendations for Message class.
Level: 1

Type: ERROR

Impact: Process

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: Process

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: Process

SDP-25730: QueueWorker got exception.: Cause: QueueWorker got exception.; Action: Check the log for related information.
Level: 1

Type: WARNING

Impact: Process

SDP-25731: Failed to find database entry to update. Id: {0}: Cause: Failed to find database entry to update.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25800: Oracle User Messaging Service configuration is successfully upgraded.: Cause:; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25801: Shall upgrade driver {0} using configuration file at {1}.: Cause:; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25802: Driver {0} upgraded using {1}.: Cause:; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25803: Driver {0} already upgraded. Ignoring configuration in {1}.: Cause:; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25804: Shall upgrade server {0} using configuration file at {1}.: Cause:; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25805: Server {0} upgraded using {1}.: Cause:; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25806: Server {0} already upgraded. Ignoring configuration in {1}.: Cause:; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25807: Shall upgrade user preference configuration for {0} using file at {1}.: Cause:; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25808: User preference configuration for {0} upgraded using {1}.: Cause:; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25809: Invalid managed server entered. Continue upgrade to see if we still can do a remote copy of the 11g configuration files.: Cause:; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25810: Custom deployed UMS application {0} will be deleted from the domain.: Cause: Custom deployed UMS applications are not supported any longer.; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25811: Failed to read configuration for driver {0}, {1}. Probably due to targeted driver without configuration.: Cause:; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25812: Ignoring configuration for application {0}.: Cause:; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25820: Error in upgrading Oracle User Messaging Service configuration. Reason: {0}: Cause: An unexpected error occurred during Oracle User Messaging Service configuration upgrade.; Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25821: Failed to read the configuration file {0}.: Cause: The configuration file is missing or in wrong format.; Action: Check if the configuration file exists with correct format. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25822: Failed to save the configuration at {0}.: Cause: Error occured while saving the configuration to the configuration file.; Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25823: Failed to delete the old configuration file at {0}.: Cause: Error occurred while deleting the old configuration file.; Action: Check the file system. Correct the problem before running the Upgrade Assistant again.
Level: 1

Type: ERROR

Impact: Process

SDP-25824: Failed to parse the configuration file at {0}.: Cause: Error occured while parsing the configuration file.; Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again.
Level: 1

Type: ERROR

Impact: Process

SDP-25825: Error during copy of configuration files from remote managed server {0}.: Cause: Old 11g configuration files where due to some problem not copied correct to the AdminServer. It could be that the plugin is missing information needed to connect to and copy the configuration from one of the managed servers. Or it could be that the sshd is not running on all the managed servers.; Action: Check the error messages in the log file to see what the problem is. Correct the problem before running the Upgrade Assistant again or perform a manual copy of the old configuration from the remote managed servers to the AdminServer.
Level: 1

Type: ERROR

Impact: Process

SDP-25826: Error connecting to remote managed server {0}.: Cause: It could be that the plugin is missing information needed to connect to one of the managed servers. Or it could be that the sshd is not running on all the managed servers.; Action: Check the error messages in the log file to see what the problem is. Correct the problem before running the Upgrade Assistant again or perform a manual copy of the old configuration from the remote managed servers to the AdminServer.
Level: 1

Type: ERROR

Impact: Process

SDP-25827: Neither the configuration nor the data entered by the user provides all information needed to copy the UMS 11g configuration files.: Cause: Upgrade Assistant does not have all information about the remote managed servers to be able to connect and copy the UMS 11g configuration files.; Action: Make sure to fill in name and address for all remote managed Servers that does not have this information configured.
Level: 1

Type: ERROR

Impact: Process

SDP-25850: Oracle User Messaging Service schema upgraded.: Cause:; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25851: Oracle User Messaging Service schema upgrade is valid.: Cause:; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25852: Oracle User Messaging Service schema version {0} is the latest one. Upgrade is not required.: Cause: Specified Oracle User Messaging Service database schema version is the latest one. Upgrade is not required.; Action: No user action is required.
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25853: Oracle User Messaging Service schema upgrade is invalid.: Cause: Specified User Messaging Service schema was updated but is invalid.; Action: Restore the User Messaging Service schema from a backup and retry. Check the error messages in Oracle User Messaging Service component log files. Correct the problem before running the Upgrade Assistant again.
Level: 1

Type: ERROR

Impact: Process

SDP-25854: The upgrade is not supported from Oracle User Messaging Service schema version of {0}.: Cause: An unsupported base schema version was being upgraded.; Action: Refer to the Oracle User Messaging Service Upgrade Guide for supported versions to upgrade.
Level: 1

Type: ERROR

Impact: Process

SDP-25855: Error in upgrading Oracle User Messaging Service schema. {0}: Cause: An unexpected error occurred during Oracle User Messaging Service schema upgrade.; Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25856: Oracle User Messaging Service schema status is invalid.: Cause: Specified Oracle User Messaging Service database schema was invalid.; Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25857: Error in Oracle User Messaging Service schema readiness check.: Cause: An unexpected error occurred during Oracle User Messaging Service schema readiness check.; Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: ERROR

Impact: Process

SDP-26000: An exception was caught.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26001: Cannot create JNDI Context.: Cause: Cannot create JNDI Context.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26002: The driver {0} is operational: Cause: The driver is operational; Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26003: Driver {0} is not configured with required properties. Driver disabled until configured.: Cause: Driver was not configured with all required properties.; Action: Configure this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26004: No Messaging Engine Queue information to enqueue status.: Cause: No Engine Queue information to enqueue status.; Action: Check that the Engine is deployed. Check Engine Queue information.
Level: 1

Type: ERROR

Impact: Process

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: WARNING

Impact: Process

SDP-26006: An error occurred while processing an outbound message.: Cause: An error occurred while processing an outbound message.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26007: No configuration was found for this Driver deployment: {0}. Driver disabled until a configuration is created.: Cause: No configuration was found for this Driver deployment.; Action: Create a configuration this SMPP Driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26008: Invalid configuration for driver {0}. Driver disabled until configured.: Cause: Invalid configuration for driver; Action: Correct the driver configuration.
Level: 1

Type: WARNING

Impact: Process

SDP-26009: Could not get JNDI InitialContext.: Cause: None; Action: None
Level: 1

Type: ERROR

Impact: Process

SDP-26010: Failed to start driver: {0}.: Cause: Failed to start driver.; Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26011: Failed to register driver in UMS engine: {0}.: Cause: Failed to register driver in UMS engine.; Action: Check stack trace and diagnostic dump for more details.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-26012: Timed out while waiting for SubDrivers to start: {0}.: Cause: Timed out while waiting for SubDrivers to start.; Action: Check stack trace and diagnostic dump for more details.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-26013: Failed to stop driver: {0}.: Cause: Unable to 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-26016: Error occurred while attempting to get the parent server MBean for {0}: Cause: Error occurred while attempting to get the parent server MBean; Action: Check stack trace for more details
Level: 1

Type: ERROR

Impact: Process

SDP-26017: Failed to invoke registerDriverInfo() for driver: {0}: Cause: Exception thrown while invoking registerDriverInfo().; Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26018: Invalid {0} value: {1}: Cause: The driver has been configured with an invalid property value.; Action: Review the driver configuration and ensure that the property is valid.
Level: 1

Type: WARNING

Impact: Process

SDP-26019: Error occurred while registering driver {0}: 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: Process

SDP-26022: Illegal DeliveryType specified, ignoring type {0}.: Cause: Illegal DeliveryType specified.; Action: Check message delivery type.
Level: 1

Type: ERROR

Impact: Process

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: Process

SDP-26024: Registration of driver {0} did not complete. Current state is {1}. Will retry periodically until messaging server responds.: Cause: None; Action: None
Level: 1

Type: WARNING

Impact: Process

SDP-26025: Error when registering messaging driver Runtime MBeans for {0}.: Cause: Exception was thrown.; Action: Check stack trace
Level: 1

Type: ERROR

Impact: Process

SDP-26026: Error in unregistering messaging driver Runtime MBeans.: Cause: Exception was thrown.; Action: Check stack trace
Level: 1

Type: ERROR

Impact: Process

SDP-26027: Ignoring property {0} with unsupported Java type {1} during driver initialization.: Cause: A property with an unsupported Java type was found in 'usermessagingconfig.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: Process

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 'usermessagingconfig.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: Process

SDP-26029: Exception occurred during driver configuration initialization for {0}.: Cause: An exception occurred during driver configuration initialization.; Action: Check the stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-26030: Failed to schedule work {0}: Cause: An exception occurred while scheduling a work.; Action: Check stack trace for more details.
Level: 1

Type: ERROR

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 'usermessagingconfig.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: Process

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: Process

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. 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: Process

SDP-26036: Unable to perform JNDI lookup.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26037: Unable to create JMSMessageReceiver: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26038: Failed to retrieve credential from credential store for user {0}: Cause: Failed to retrieve credential from credential store for the specified user.; Action: Check stack trace or error log.
Level: 1

Type: ERROR

Impact: Process

SDP-26039: Driver {0} does not have inbound configuration. No messages (including information about bounced emails) are received.: Cause:; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26040: Driver {0} does not have outbound configuration. Messages cannot be sent through this driver.: Cause:; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26041: An attempt to configure inbound for driver {0} was detected. All required properties was not configured so the whole configuration (inbound and outbound) will be invalidated. Driver disabled until configured.: Cause: An attempt to configure inbound for the driver was detected. All required properties was not configured so the whole configuration (inbound and outbound) will be invalidated. Driver disabled until configured.; Action: Remove inbound configuration or configure all required properties for this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26042: An attempt to configure outbound for driver {0} was detected. All required properties was not configured so the whole configuration (inbound and outbound) will be invalidated. Driver disabled until configured.: Cause: An attempt to configure outbound for the driver was detected. All required properties was not configured so the whole configuration (inbound and outbound) will be invalidated. Driver disabled until configured.; Action: Remove outbound configuration or configure all required properties for this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26043: Driver {0} lost connection to the external gateway. Will try to reconnect.: Cause:; Action:
Level: 1

Type: WARNING

Impact: Process

SDP-26044: Driver {0} reconnected to the external gateway.: Cause:; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26100: An exception was caught.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26101: An exception was caught.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

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: WARNING

Impact: Process

SDP-26103: Error while writing e-mail subject.: Cause: Cannot write the subject.; Action: Check stack trace or error log.
Level: 1

Type: WARNING

Impact: Process

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: WARNING

Impact: Process

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: WARNING

Impact: Process

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: WARNING

Impact: Process

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: WARNING

Impact: Process

SDP-26108: 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: WARNING

Impact: Process

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: Process

SDP-26110: Failed to start Email Driver: Cause: Failed to start Email Driver.; Action: Check stack trace or error log. Check e-mail driver parameters and make sure all email servers are running.
Level: 1

Type: ERROR

Impact: Process

SDP-26111: Failed to retrieve credential from credential store for user {0}: Cause: Failed to retrieve credential from credential store for the specified user.; Action: Check stack trace or error log.
Level: 1

Type: ERROR

Impact: Process

SDP-26112: Authentication failed: user={0}, host={1}:{2}, sslEnabled={3}: Cause: Authentication failed for the specified user, server, port, and sslEnabled parameters.; Action: Check stack trace or error log. Check the username, password, server, port, and sslEnabled parameters.
Level: 1

Type: ERROR

Impact: Process

SDP-26118: Failed to open folder {0} for user {1}: Cause: Folder name is not correct or does not exist.; Action: Check folder name spelling.
Level: 1

Type: ERROR

Impact: Process

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: WARNING

Impact: Process

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: Process

SDP-26123: Could not initialize Email Store for: user {0}, server {1}, folder {2}, sslEnabled {3}: Cause: Could not initialize Email Store for the specified user, server, folder, and sslEnabled parameters.; Action: Check stack trace or error log. Check the username, password, server, folder and sslEnabled parameters.
Level: 1

Type: ERROR

Impact: Process

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: Process

SDP-26130: Ignoring property {0} with invalid value {1} during driver initialization.: Cause: A property with an invalid value was found in 'usermessagingconfig.xml' during driver initialization.; Action: Ensure the value configured value is valid.
Level: 1

Type: WARNING

Impact: Process

SDP-26131: Lookup of encoded credential value {0} in the credential store for property {1} failed during driver initialization.: Cause: A property with an invalid encoded credential value was found in 'usermessagingconfig.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: Process

SDP-26134: Email Driver {0} is not configured with incoming mail properties. No emails (including information about bounced emails) are received.: Cause:; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26135: Email Driver {0} is not configured with outgoing mail properties. Emails cannot be sent through this driver.: Cause:; Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26136: Driver property OutgoingDefaultFromAddr is deprecated. Use DefaultSenderAddress instead.: Cause: Driver property OutgoingDefaultFromAddr in 'usermessagingconfig.xml' is deprecated.; Action: Use DefaultSenderAddress instead.
Level: 1

Type: WARNING

Impact: Process

SDP-26137: Both DefaultSenderAddress and the deprecated OutgoingDefaultFromAddr is configured in 'usermessagingconfig.xml'. DefaultSenderAddress will be used.: Cause: Both OutgoingDefaultFromAddr and DefaultSenderAddress is configured in 'usermessagingconfig.xml'. DefaultSenderAddress will be used.; Action: Remove configuration for OutgoingDefaultFromAddr.
Level: 1

Type: WARNING

Impact: Process

SDP-26138: Message was not delivered. No valid sender(From) address available.: Cause: No sender address set in message and DefaultSenderAddress is not configured in 'usermessagingconfig.xml'.; Action: Set sender(From) address in message or set DefaultSenderAddress in 'usermessagingconfig.xml'.
Level: 1

Type: WARNING

Impact: Process

SDP-26150: An exception was caught.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

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: Process

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: Process

SDP-26153: Failed to connect to server, host: {0}, port: {1} (local address: {2}, local port: {3}): Cause: Failed to connect to server with the specified parameters.; Action: Check the stack trace and the specified parameters. Ensure that the network is operational.
Level: 1

Type: ERROR

Impact: Process

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: Process

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: Process

SDP-26158: Caught exception while closing connection: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

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: WARNING

Impact: Process

SDP-26160: No configuration was found for this SMPP Driver deployment: {0}. Driver disabled until a configuration is created.: Cause: No configuration was found for this SMPP Driver deployment.; Action: Create a configuration this SMPP Driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26161: Starting SMPP Driver: {0}: Cause: SMPP Driver resource adapter initialization.; Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

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: Process

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: Process

SDP-26165: Lookup of encoded credential value for account {0} in the credential failed during driver initialization.: Cause: Lookup of encoded credential value in the credential failed during driver initialization.; Action: Check the stack trace for more details. Ensure that the encoded indirect password and the credential store are properly configured.
Level: 1

Type: WARNING

Impact: Process

SDP-26166: SMPP Driver {0} is not configured with all required properties. Driver disabled until configured.: Cause: SMPP Driver was not configured with all required properties.; Action: Configure this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26200: An exception was caught.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26205: Exception while getting content from message with id={0}: Cause: Exception while getting content from message.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

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: WARNING

Impact: Process

SDP-26214: Caught an exception in XMPP driver while sending out a message.: Cause: An exception was caught.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26225: Received Error Message. Code: {0} Text: {1}.: Cause: Received Error Message.; Action: Check error code and error message.
Level: 1

Type: WARNING

Impact: Process

SDP-26236: Got an 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: WARNING

Impact: Process

SDP-26300: A Twitter exception was caught.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26301: Got an exception when receiving tweets.: Cause: An exception has occurred when receiving tweets.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26302: Got an exception when receiving direct messages.: Cause: An exception has occurred when receiving direct message.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26303: Exception caught during attributes transferring of an inbound direct message.: Cause: An exception has occurred when transferring attributes of a direct message.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26304: Exception caught during attributes transferring of an inbound tweet.: Cause: An exception has occurred when transferring attributes of a tweet.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26305: Got an exception when building an inbound UMS message from a received tweet or direct message.: Cause: An exception has occurred when rebuilding an inbound UMS message.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26306: Required OAuth login information is missing or incomplete. Consumer key, consumer secret, access token, and/or access token secret is not set.: Cause: At least one of Twitter consumer key, consumer secret, access token, and access token secret is missing or not set.; Action: Check the log file for the missing field(s).
Level: 1

Type: ERROR

Impact: Process

SDP-26307: Required xAuth login information for user {0} is missing or incomplete. Both username and password are required.: Cause: Username or password is missing or not set.; Action: Check the log file for the missing field(s).
Level: 1

Type: ERROR

Impact: Process

SDP-26308: No configuration was found for this Twitter Driver deployment: {0}. Driver disabled until a configuration is created.: Cause: No configuration was found for this Twitter Driver deployment.; Action: Create a configuration this Twitter Driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26309: Twitter Driver {0} is not configured with all required properties. Driver disabled until configured.: Cause: Twitter Driver was not configured with all required properties.; Action: Configure this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26310: Twitter Driver not properly configured. AuthenticationMode {0} is unknown and not supported.: Cause: Twitter Driver not properly configured. AuthenticationMode given is unknown and not supported.; Action: Configure and restart this driver.
Level: 1

Type: ERROR

Impact: Process

SDP-26311: Retweet id string {0} in meta data could not be converted to long. No tweet for messageId {1}: Cause: Retweet id string in meta data could not be converted to long.; Action: Check how the application generates the meta data.
Level: 1

Type: WARNING

Impact: Process

SDP-26312: Ignoring reply id string {0} in meta data that could not be converted to long.: Cause: Ignoring reply id string in meta data that could not be converted to long.; Action: Check how the application generates the meta data.
Level: 1

Type: WARNING

Impact: Process

SDP-26313: Ignoring geo location string ({0}) in meta data that could not be converted to (double,double).: Cause: Ignoring geo location string in meta data that could not be converted to (double,double).; Action: Check how the application generates the meta data.
Level: 1

Type: WARNING

Impact: Process

SDP-26314: Failed to verify the credentials.: Cause: Failed to verify the credentials.; Action: Check the Twitter Driver configuration.
Level: 1

Type: WARNING

Impact: Process

SDP-26315: Failed to send tweet due to rate limitation.: Cause: Failed to send tweet due to rate limitation.; Action: Adjust the send rate or modify the Twitter Account settings.
Level: 1

Type: WARNING

Impact: Process

SDP-26316: Failed to receive tweet due to rate limitation.: Cause: Failed to receive tweet due to rate limitation.; Action: Wait or modify the Twitter Account settings.
Level: 1

Type: WARNING

Impact: Process

SDP-26317: Twitter exception when sending tweet. Msg={0}: Cause: Twitter exception when sending tweet.; Action: Check the Twitter Exception message.
Level: 1

Type: WARNING

Impact: Process

SDP-26450: An exception was caught.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26451: One or more sets of extension endpoints were configured using identical protocols and mapped domains: {0}.: 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: Process

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: Process

SDP-26453: No configuration was found for this Extension Driver deployment: {0}. Driver disabled until a configuration is created.: Cause: No configuration was found for this Email Driver deployment.; Action: Create a configuration this Email Driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26454: Extension Driver {0} is not configured with at least one extension point with a valid endpoint URL and protocol. Driver disabled until configured.: Cause: Extension Driver is not configured with at least one extension point with a valid endpoint URL and protocol.; Action: Configure this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26455: Error while processing Extension Driver configuration with Endpoint URL: {0}. The configuration must contains a valid endpoint URL and protocol.: Cause: An error occurred while processing the Extension Driver configuration.; Action: Check the corresponding configuration. The configuration must contains a valid endpoint URL and protocol.
Level: 1

Type: ERROR

Impact: Process

SDP-26456: 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: ERROR

Impact: Process

SDP-26457: An exception occurred while constructing the SOAP message: {0}: Cause: An exception occurred while constructing the SOAP message; Action: Check the configuration of the server.
Level: 1

Type: ERROR

Impact: Process

SDP-26500: An exception was caught.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26501: Failed to deliver a message to the gateway at {0}. No Status could be generated for the failed message.: Cause: A message failed to be delivered to the gateway.; Action: Check the connectivity to the gateway
Level: 1

Type: ERROR

Impact: Process

SDP-26502: Unable to connect to the Feedback service at {0}. Will retry to connect.: Cause: Unable to poll the Feedback service, due to a network problem.; Action: Check the connectivity to the Feedback service.
Level: 1

Type: ERROR

Impact: Process

SDP-26503: Unable to poll the Feedback service at {0}.: Cause: Unable to poll the Feedback service, probably due to a network problem.; Action: Check the connectivity to the Feedback service.
Level: 1

Type: ERROR

Impact: Process

SDP-26550: An exception was caught.: Cause: An exception has occurred.; Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26551: Failed to deliver a message to the gateway at {0}. No Status could be generated for the failed message.: Cause: A message failed to be delivered to the gateway.; Action: Check the connectivity to the gateway
Level: 1

Type: ERROR

Impact: Process