SDP-26500 to SDP-26236

29 SDP-26500 to SDP-26236

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

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

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

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

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

SDP-25002: Unable to create JNDI Context.
Category:: Process
Cause:: An exception has occurred.
Action:: Check the stack trace for more details. Check the JNDI Context initialization parameters.

SDP-25003: Unable to create an instance of Driver Locator.
Category:: Process
Cause:: An exception has occurred.
Action:: Check the stack trace for more details.

SDP-25004: Message could not be delivered to client due to rollback at the client application. Message ID {0}.
Category:: Process
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

SDP-25005: Failed to create Sending Core instance.
Category:: Process
Cause:: An exception has occurred.
Action:: Check the stack trace for more details.

SDP-25006: Failed to remove an EJB instance.
Category:: Process
Cause:: An exception has occurred.
Action:: Check the stack trace for more details.

SDP-25007: An error occurred while processing an outbound message.
Category:: Process
Cause:: The outbound JMS message does not contain a valid message or request information.
Action:: Check the stack trace for more details.

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

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

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

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

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

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

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

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

SDP-25016: Could not get TimerService or Timers.
Category:: Process
Cause:: Could not get TimerService or Timers.
Action:: Check application server status.

SDP-25017: Could not cancel timer.
Category:: Process
Cause:: Could not cancel timer
Action:: Check the stack trace for more details.

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

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

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

SDP-25030: Unable to schedule a timer to refresh the driver locator cache.
Category:: Process
Cause:: An exception has occurred while scheduling a timer to refresh the driver cache.
Action:: Check the stack trace for more details.

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

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

SDP-25034: There are total {0} registered User Messaging Drivers. Driver(s): {1}.
Category:: Process
Cause:: A Messaging Driver registered with the Messaging Server
Action:: None

SDP-25035: Messaging store not found.
Category:: Process
Cause:: An exception has occurred while attempting to find the messaging store.
Action:: Check the stack trace for more details.

SDP-25036: An error occurred while registering driver information at User preference subsystem {0}.
Category:: Process
Cause:: An exception has occurred while registering the driver information at User preference subsystem.
Action:: Check the stack trace for more details.

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

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

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

SDP-25043: An unknown command message was received, ignoring: {0}.
Category:: Process
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.

SDP-25055: Failed to create Receiving Core instance.
Category:: Process
Cause:: An exception has occurred.
Action:: Check the stack trace for more details.

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

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

SDP-25059: An unknown JMS message is received, ignoring: {0}.
Category:: Process
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.

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

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

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

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

SDP-25065: An error occurred while sending a message to failover address {0}.
Category:: Process
Cause:: An exception has occurred while sending out a failover message.
Action:: Check the stack trace for more details.

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

SDP-25070: Unable to retrieve messaging engine sending and/or receiving queues from configuration.
Category:: Process
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.

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

SDP-25082: No predicates and/or devices matched. Ignoring converter rule (MIME type: {0}, delivery type: {1}, predicate: {2}).
Category:: Process
Cause:: An invalid message converter rule was provided.
Action:: Check the log file for additional details.

SDP-25083: Message content is not an instance of MimeMultipart.
Category:: Process
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.

SDP-25085: Message {0} has a nonunique Message ID or recipient, and does not look like a redelivery attempt.
Category:: Process
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.

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

SDP-25088: Unable to refresh the driver locator cache, due to exception.
Category:: Process
Cause:: An error has occurred while refreshing the driver locator cache.
Action:: Check the reported error message and correct any configuration problems.

SDP-25089: Status could not be delivered to client due to rollback at the client application. Message ID {0} {1}.
Category:: Process
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

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

SDP-25106: Conflicting recipient IDs for Message {0}.
Category:: Process
Cause:: A conflict between recipient identifiers has been detected.
Action:: Ensure that applications are using unique Message IDs.

SDP-25107: Message ID {0} in Status object does not match previously recorded Message ID {1}.
Category:: Process
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.

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

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

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

SDP-25251: Messaging Exception while processing Parlay X request.
Category:: Process
Cause:: A Messaging Exception has occurred.
Action:: Check the stack trace for more details.

SDP-25252: Exception while initializing Parlay X Messaging servlet.
Category:: Process
Cause:: An exception occurred while initializing the Parlay X Messaging servlet.
Action:: Check the stack trace for more details.

SDP-25253: Exception while initializing Parlay X Messaging content servlet.
Category:: Process
Cause:: An exception occurred while initializing the Parlay X Messaging content servlet.
Action:: Check the stack trace for more details.

SDP-25254: Exception while processing SOAP attachment content.
Category:: Process
Cause:: An exception occurred while processing message content in a SOAP attachment.
Action:: Check the stack trace for more details.

SDP-25255: Message contains multiple attachments. All but first attachment will be ignored.
Category:: Process
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.

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

SDP-25257: Error initializing JAXP DatatypeFactory. Some data types may not be converted correctly.
Category:: Process
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.

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

SDP-25301: JNDI context is null.
Category:: Process
Cause:: JNDI context was null.
Action:: See the Javadoc on Oracle Technology Network (OTN) for more information about how to instantiate a JNDI context.

SDP-25302: EJB home for UserPrefsService is null.
Category:: Process
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.

SDP-25303: Unable to connect to User Messaging Service (UMS) server at {0}.
Category:: Process
Cause:: EJB Naming Exception was caught when creating a UserPrefsServices object.
Action:: Check the stack trace for more details.

SDP-25304: EJB Remote Exception was caught at server {0}.
Category:: Process
Cause:: EJB Remote Exception was caught.
Action:: Check the stack trace for more details.

SDP-25305: EJB Create Exception was caught at server {0}.
Category:: Process
Cause:: EJB Create Exception was caught.
Action:: Check the stack trace for more details.

SDP-25306: XML Document object is null.
Category:: Process
Cause:: XML Document object is null.
Action:: Specify a valid XML document object.

SDP-25307: No file to upload. File name is not set.
Category:: Process
Cause:: The file name to be uploaded was not set.
Action:: Invoke setFileName() to set the file name.

SDP-25308: The file, {0}, cannot be read.
Category:: Process
Cause:: The file cannot be read.
Action:: Check the file.

SDP-25309: File not found: {0}.
Category:: Process
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.

SDP-25311: The document cannot be uploaded. Parser and stack are out of sync. Tag name: {0} Local name: {1}.
Category:: Process
Cause:: The document cannot be uploaded because parser and stack were out of sync.
Action:: Fix mismatched tags.

SDP-25312: Provisioning Exception was caught.
Category:: Process
Cause:: Provisioning Exception was caught.
Action:: Check the stack trace for more details.

SDP-25314: Rule {0} is already defined.
Category:: Process
Cause:: Rule with the same name was already defined.
Action:: Choose a different rule name to avoid conflict.

SDP-25316: Input parameter, UserPrefsServices, is null.
Category:: Process
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.

SDP-25317: Required input parameter, UserID, is null.
Category:: Process
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.

SDP-25318: Invalid input parameter. DeviceAddress object is null.
Category:: Process
Cause:: Input parameter, DeviceAddress object, is null.
Action:: Pass a valid DeviceAddress object. Check User Messaging Service Javadoc on OTN for more information.

SDP-25319: UserRuleSet is not set. Call initProcessor() first.
Category:: Process
Cause:: UserRuleSet object is null.
Action:: Call initProcessor() first to complete initialization.

SDP-25320: Rule Set is null.
Category:: Process
Cause:: The Rule Set was not available or could not be created.
Action:: Use a valid Rule Set.

SDP-25321: XML String representing the Rule Set is null.
Category:: Process
Cause:: The XML document element representing the Rule Set was null or empty.
Action:: Use a valid Rule Set XML element.

SDP-25322: User Rule Set is null.
Category:: Process
Cause:: The User Rule Set was not available or could not be created.
Action:: Use a valid User Rule Set object.

SDP-25323: User Rule Set is inconsistent. See exception for more details.
Category:: Process
Cause:: User Rule Set is inconsistent.
Action:: Check User Rule Set for consistency.

SDP-25324: XML document is invalid. See exception for details.
Category:: Process
Cause:: XML document is invalid. See stacktrace for more details.
Action:: Validate the XML document.

SDP-25325: Cannot serialize Rule Session.
Category:: Process
Cause:: Cannot serialize Rule Session, which is not critical.
Action:: No action needed.

SDP-25326: Filter XML is null.
Category:: Process
Cause:: The Preference Rules were missing or inconsistent.
Action:: Use a well-formed User Preference XML document.

SDP-25327: Cannot create Rule Session.
Category:: Process
Cause:: Cannot create Rule Session.
Action:: No action needed.

SDP-25328: UserPrefsException was caught.
Category:: Process
Cause:: UserPrefsException was caught.
Action:: Check the stack trace for more details.

SDP-25329: Rule {0} does not exist.
Category:: Process
Cause:: The expected rule was not found.
Action:: Check the rule by name on the User Preference page.

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

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

SDP-25334: Device name is null.
Category:: Process
Cause:: Device name is null.
Action:: Provide a valid Device name.

SDP-25336: Input parameter, UserPrefsObject, is null.
Category:: Process
Cause:: Required parameter, UserPrefsObject, is null.
Action:: Provide a valid UserPrefsObject.

SDP-25337: Failed to move a rule: origin rule number is out of the range of existing rules.
Category:: Process
Cause:: Origin rule number is not valid.
Action:: Specify a valid rule number.

SDP-25341: The order of calling methods is wrong.
Category:: Process
Cause:: The order of calling methods is wrong.
Action:: Check the order of the methods being called.

SDP-25343: No devices are defined.
Category:: Process
Cause:: Tried to call delivery preferences without defining devices.
Action:: Define devices for use with delivery preferences.

SDP-25344: Invalid action {0} is found and ignored.
Category:: Process
Cause:: An invalid action was detected.
Action:: Use one of the valid actions: BROADCAST, FAIL_OVER, and DO_NOT_SEND.

SDP-25345: Runtime exception was caught.
Category:: Process
Cause:: Runtime exception was caught.
Action:: Check the stack trace for more details.

SDP-25346: No configured Business Terms are available, only system terms will be used.
Category:: Process
Cause:: Business Term configuration could not be read.
Action:: Ensure that business term configuration is correct

SDP-25347: Device {0} cannot be added because it is present in the list.
Category:: Process
Cause:: A device was present in the list already.
Action:: Ensure that the device to be added is not in the device list.

SDP-25348: Failed to move a device: device ID index number is out of the range of device list.
Category:: Process
Cause:: Device ID index number is not valid.
Action:: Specify a valid device ID index number.

SDP-25349: Name of rule is not set.
Category:: Process
Cause:: Rule name was not set.
Action:: Set the name of the rule.

SDP-25350: FilterOperation of a rule is not set.
Category:: Process
Cause:: FilterOperation of a rule was not set.
Action:: Set the FilterOperation of the rule.

SDP-25351: ActionOperation of a rule is not set.
Category:: Process
Cause:: ActionOperation of a rule was not set.
Action:: Set the ActionOperation of the rule.

SDP-25352: Condition of a rule is not set.
Category:: Process
Cause:: Condition of a rule was not set.
Action:: Set the condition of the rule.

SDP-25353: unable to send a BROADCAST message because no address is set.
Category:: Process
Cause:: An address has not been set for the BROADCAST action.
Action:: Set at least one address for the BROADCAST action.

SDP-25354: A failover address is not set for the FAIL_OVER action.
Category:: Process
Cause:: An address has not been set for the FAIL_OVER action.
Action:: Set at least one address for the FAIL_OVER action.

SDP-25356: Cannot persist device address {0} for user GUID {1}, because one already exists.
Category:: Process
Cause:: An identical device address already exists.
Action:: Remove the conflicting device address, overwrite it, or specify a different address.

SDP-25361: The Java VM does not support the encoding {0}.
Category:: Process
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.

SDP-25387: Rule fact for term {0} has been ignored as it does not have the correct type, {1}.
Category:: Process
Cause:: The fact from user or application had an incorrect data type.
Action:: Provide the fact with the correct data type as indicated.

SDP-25388: Device named {0} of user {1} not found.
Category:: Process
Cause:: The user does not have a device with that name.
Action:: Check username and device name.

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

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

SDP-25403: Error in registering messaging Runtime MBeans.
Category:: Process
Cause:: Exception was thrown.
Action:: Check stack trace

SDP-25404: Error in unregistering messaging Runtime MBeans.
Category:: Process
Cause:: Exception was thrown.
Action:: Check stack trace.

SDP-25405: Naming exception thrown looking up Management Store: Unable to initialize SDP Messaging Runtime MBeans.
Category:: Process
Cause:: Naming exception thrown while looking up the Management Store EJB.
Action:: Check stack trace.

SDP-25406: Create exception thrown while creating Management Store: Unable to initialize SDP Messaging Runtime MBeans.
Category:: Process
Cause:: Create exception thrown while creating Management Store EJB.
Action:: Check stack trace.

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

SDP-25408: Invalid query parameter: query field: {0}, query condition: {1}, query value: {2}.
Category:: Process
Cause:: Invalid combination of query parameters or invalid query value.
Action:: Check stack trace.

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

SDP-25410: Unable to convert to composite type and return composite data for the MBean. Name: {0}.
Category:: Process
Cause:: OpenDataException was caught.
Action:: Check stack trace.

SDP-25416: Error occurred while attempting to get the parent server MBean for {0}.
Category:: Process
Cause:: An exception was thrown while attempting to get the parent server MBean.
Action:: Check stack trace.

SDP-25500: Failed to schedule Timer.
Category:: Process
Cause:: Timer could not be scheduled in the TimerManager
Action:: Check stack trace, diagnostic dump

SDP-25501: Exception when delivering pending messages.
Category:: Process
Cause:: Exception when delivering pending messages
Action:: Check the stack trace for more details.

SDP-25502: Unable to create JNDI Context.
Category:: Process
Cause:: An exception has occurred.
Action:: Check the stack trace for more details. Check the JNDI Context initialization parameters.

SDP-25503: Unable to connect to the messaging server.
Category:: Process
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.

SDP-25504: Unable to register application information with the messaging server.
Category:: Process
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.

SDP-25505: Unable to enqueue outbound message.
Category:: Process
Cause:: Engine Sending Queue may not be available.
Action:: Check the stack trace for more details.

SDP-25506: Unable to get receiving queues from application information.
Category:: Process
Cause:: An exception has occurred.
Action:: Check the stack trace for more details. Check the Application information properties.

SDP-25507: Unable to enqueue inbound message status because no engine queues were found.
Category:: Process
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.

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

SDP-25510: An error occurred while attempting to retrieve the actual password from the credential store.
Category:: Process
Cause:: An exception has occurred.
Action:: Check the stack trace for more details.

SDP-25511: An error occurred while dequeuing a message from the application receiving queue.
Category:: Process
Cause:: An invalid JMS message was dequeued by the Dispatcher MDB.
Action:: Check the stack trace for more details.

SDP-25512: An invalid message was dequeued from the application receiving queue: {0}.
Category:: Process
Cause:: An invalid JMS message was dequeued by the Dispatcher MDB.
Action:: Check the stack trace for more details.

SDP-25513: JNDI lookup of application callback listener failed.
Category:: Process
Cause:: An invalid callback listener was previously registered and could not be invoked.
Action:: Check the stack trace for more details.

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

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

SDP-25516: Message/Status listener not configured. Suspending messaging client MDB to disable asynchronous message/status callbacks.
Category:: Process
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.

SDP-25517: Messaging client MDB suspend failed: {0}.
Category:: Process
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.

SDP-25519: QueueWorker rejected.
Category:: Process
Cause:: QueueWorker rejected
Action:: Check WorkManager configuration.

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

SDP-25532: An error occurred while retrieving the Application Information from the application JNDI context.
Category:: Process
Cause:: An exception has occurred.
Action:: Check the stack trace for more details.

SDP-25541: An error occurred while generating received message statuses.
Category:: Process
Cause:: An exception has occurred.
Action:: Check the stack trace for more details.

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

SDP-25543: The current authenticated user "{0}" does not match the configured security principal "{1}".
Category:: Process
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.

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

SDP-25701: Unable to instantiate class {0}.
Category:: Process
Cause:: Unable to instantiate a class.
Action:: Check to see if that class is in classpath or not.

SDP-25702: Unable to set content of Message object.
Category:: Process
Cause:: Unable to set content of a message.
Action:: Check the stack trace for more details.

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

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

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

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

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

SDP-25708: Unable to perform JNDI lookup of JMS QCF: {0}.
Category:: Process
Cause:: An exception has occurred.
Action:: Check the stack trace for more details.

SDP-25709: Unable to perform JNDI lookup.
Category:: Process
Cause:: An exception has occurred.
Action:: Check the stack trace for more details.

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

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

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

SDP-25713: Unable to perform JNDI lookup of JMS Queue: {0}.
Category:: Process
Cause:: An exception has occurred.
Action:: Check the stack trace for more details.

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

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

SDP-25716: Error occurred in looking up QueueConnectionFactory in JNDI, skipping: {0}
Category:: Process
Cause:: Error occurred in looking up QueueConnectionFactory in JNDI.
Action:: Check the stack trace for more details.

SDP-25717: Error occurred in looking up Queue in JNDI, skipping: {0}.
Category:: Process
Cause:: Error occurred in looking up queue in JNDI.
Action:: Check the stack trace for more details.

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

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.
Category:: Process
Cause:: The JMS receiver could not connect to the JMS destination.
Action:: Check the JMS system resource and the JMS server for additional information.

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

SDP-25728: Could not determine server platform type. Generic values will be used for platform-specific data.
Category:: Process
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.

SDP-25729: An exception occurred while enabling the WS-Security configuration: {0}.
Category:: Process
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.

SDP-25730: QueueWorker got exception.
Category:: Process
Cause:: QueueWorker got exception.
Action:: Check the log for related information.

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

SDP-25733: Failed to add/create new QWorker thread {0}
Category:: Process
Cause:: Failed to add/create new QWorker thread {0}.
Action:: Check the stack trace for more details.

SDP-25734: Failed to remove/un-schedule a QWorker thread {0}
Category:: Process
Cause:: Failed to remove/un-schedule a QWorker thread {0}.
Action:: Check the stack trace for more details.

SDP-25900: Exception occurred in config refresh scheduler. Message: {0}
Category:: Process
Cause:: An exception was caught.
Action:: Check the stack trace for more details.

SDP-25901: UMS Config changes found that requires UMS restart. Configs: {0}
Category:: Process
Cause:: Found config changes that requires restart
Action:: Restart Managed server

SDP-25902: Driver reload Failed for driver {0}. Cause {1}
Category:: Process
Cause:: An exception was caught
Action:: Check the stack trace for more details.

SDP-25903: Engine configuration failed to refresh for property {0}. Cause {1}
Category:: Process
Cause:: An exception was caught
Action:: Check the stack trace for more details.

SDP-25904: Timer is requested to stop for Config Refresh scheduler.
Category:: Process
Cause:: Timer is requested to stop
Action:: No Action required.

SDP-25905: Config Refresh scheduler has refreshed the configuration for Properties: {0}
Category:: Process
Cause:: Config Refresh scheduler found difference in configs
Action:: No Action required.

SDP-25906: Unable to initialize config store. Scheduler will not be able to refresh configs. Cause {0}
Category:: Process
Cause:: An exception was caught
Action:: Check the stack trace for more details.

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

SDP-26001: Cannot create JNDI Context.
Category:: Process
Cause:: Cannot create JNDI Context.
Action:: Check the stack trace for more details.

SDP-26002: The driver {0} is operational
Category:: Process
Cause:: The driver is operational
Action:: None

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

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

SDP-26005: Dispatcher failed to find a driver.
Category:: Process
Cause:: Dispatcher failed to find a driver.
Action:: Compare delivery type and content type between message and available drivers.

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

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

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

SDP-26009: Could not get JNDI InitialContext.
Category:: Process
Cause:: None
Action:: None

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

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

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

SDP-26013: Failed to stop driver: {0}.
Category:: Process
Cause:: Unable to stop driver.
Action:: Check stack trace for more details.

SDP-26014: Unable to process inbound message/status.
Category:: Process
Cause:: Exception occurred while processing inbound message/status.
Action:: Check stack trace for more details.

SDP-26015: Unable to process command message.
Category:: Process
Cause:: Exception occurred while processing command message.
Action:: Check stack trace for more details.

SDP-26016: Error occurred while attempting to get the parent server MBean for {0}
Category:: Process
Cause:: Error occurred while attempting to get the parent server MBean
Action:: Check stack trace for more details

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

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

SDP-26019: Error occurred while registering driver {0}
Category:: Process
Cause:: Error occurred while registering driver.
Action:: Check stack trace for more details.

SDP-26020: Registration of driver {0} succeeded.
Category:: Process
Cause:: None
Action:: None

SDP-26021: Timed out while waiting for reply from Messaging engine.
Category:: Process
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.

SDP-26022: Illegal DeliveryType specified, ignoring type {0}.
Category:: Process
Cause:: Illegal DeliveryType specified.
Action:: Check message delivery type.

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

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

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

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

SDP-26027: Ignoring property {0} with unsupported Java type {1} during driver initialization.
Category:: Process
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

SDP-26028: Ignoring property {0} with invalid value {1} and/or Java type {2} during driver initialization.
Category:: Process
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

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

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

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

SDP-26032: JNDI lookup of driver connection factory {0} failed with the following error message: {1}. Will retry until successful.
Category:: Process
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.

SDP-26033: Started messaging driver: {0}
Category:: Process
Cause:: Driver was started.
Action:: None.

SDP-26034: Stopped messaging driver: {0}
Category:: Process
Cause:: Driver was stopped.
Action:: None.

SDP-26035: JNDI lookup of server command endpoint {0} failed. Will retry until successful.
Category:: Process
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.

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

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

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

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

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

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

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

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

SDP-26044: Driver {0} reconnected to the external gateway.
Category:: Process
Cause:
Action:

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

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

SDP-26102: Error while writing e-mail message content.
Category:: Process
Cause:: An exception has occurred while writing e-mail content and headers to an e-mail message.
Action:: Check stack trace or error log.

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

SDP-26104: Recipient address error.
Category:: Process
Cause:: Recipient e-mail address has an error.
Action:: Check and see if the recipient e-mail address is correct.

SDP-26105: Unable to deliver to following address(es): {0} Reason: {1}
Category:: Process
Cause:: One or more recipient e-mail addresses had an error.
Action:: Ensure that the e-mail address is correct.

SDP-26106: Failed to send the e-mail message
Category:: Process
Cause:: Unable to login to SMTP server.
Action:: Check SMTP server host name, port, user name, and password.

SDP-26107: Failed to add header - name: {0} value: {1}
Category:: Process
Cause:: Unable to add an e-mail header to a multipart message
Action:: Check the stack trace or error log.

SDP-26108: Content type parsing error {0}.
Category:: Process
Cause:: Error occurred while trying to parse the content type.
Action:: Check and see if the content type is specified correctly.

SDP-26109: Caught exception while closing connection to e-mail server.
Category:: Process
Cause:: An exception was caught while closing connection.
Action:: Check stack trace or error log.

SDP-26110: Failed to start Email Driver
Category:: Process
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.

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

SDP-26112: Authentication failed: user={0}, host={1}:{2}, sslEnabled={3}
Category:: Process
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.

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

SDP-26119: Max retry limit reached for trying to connect to user {0}
Category:: Process
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.

SDP-26122: An exception has been thrown when connecting to user {0}
Category:: Process
Cause:: Email driver could not connect to user.
Action:: Check username and password. Make sure the user exists and is accessible.

SDP-26123: Could not initialize Email Store for: user {0}, server {1}, folder {2}, sslEnabled {3}
Category:: Process
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.

SDP-26126: Unrecoverable message - {0}
Category:: Process
Cause:: failed to recover an e-mail message
Action:: Check stack trace or error log.

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

SDP-26131: Lookup of encoded credential value {0} in the credential store for property {1} failed during driver initialization.
Category:: Process
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.

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

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

SDP-26136: Driver property OutgoingDefaultFromAddr is deprecated. Use DefaultSenderAddress instead.
Category:: Process
Cause:: Driver property OutgoingDefaultFromAddr in 'usermessagingconfig.xml' is deprecated.
Action:: Use DefaultSenderAddress instead.

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

SDP-26138: Message was not delivered. No valid sender(From) address available.
Category:: Process
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'.

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

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

SDP-26452: No extension endpoint could be found for the specified recipient address.
Category:: Process
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.

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

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.
Category:: Process
Cause:: Extension Driver is not configured with at least one extension point with a valid endpoint URL and protocol.
Action:: Configure this driver.

SDP-26455: Error while processing Extension Driver configuration with Endpoint URL: {0}. The configuration must contains a valid endpoint URL and protocol.
Category:: Process
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.

SDP-26456: An exception occurred while enabling the WS-Security configuration: {0}
Category:: Process
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.

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

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

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

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

SDP-26151: Failed to process a received message in SMPP driver, because driver context is null
Category:: Process
Cause:: Driver context is null
Action:: Check the stack trace for more details.

SDP-26152: WorkManager object is null in SMPP driver.
Category:: Process
Cause:: The caller of setWorkManager() passed in a null WorkManager object as an argument
Action:: Make sure WorkManager object is not null.

SDP-26153: Failed to connect to server, host: {0}, port: {1} (local address: {2}, local port: {3})
Category:: Process
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.

SDP-26155: unable to initialize SMPP driver, because a driver attribute, sms.account.id, is not set.
Category:: Process
Cause:: The account ID was not set.
Action:: Set the correct account information.

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.
Category:: Process
Cause:: SMSC server or account information is not correct or missing.
Action:: Check those parameters.

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

SDP-26159: Illegal data length value from SMSC received and ignored: {0}
Category:: Process
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.

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

SDP-26161: Starting SMPP Driver: {0}
Category:: Process
Cause:: SMPP Driver resource adapter initialization.
Action:: None

SDP-26163: Data stream ended unexpectedly while reading packet from SMSC
Category:: Process
Cause:: The data stream ended unexpectedly while reading a packet from the SMSC. Message or command will be dropped.
Action:: None.

SDP-26164: Failed to bind receiver connection; will retry until bind operation is successful.
Category:: Process
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.

SDP-26165: Lookup of encoded credential value for account {0} in the credential failed during driver initialization.
Category:: Process
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.

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

SDP-27001: An exception was caught.
Category:: Process
Cause:: An exception has occurred.
Action:: Check the stack trace for more details.

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

SDP-27003: Invalid Credentials provided. {0}
Category:: Process
Cause:: Invalid Credentials provided
Action:: Check the credentials

SDP-27004: Not Found returned from API call please check message. {0}
Category:: Process
Cause:: Not Found returned from API.
Action:: Check the logs for details

SDP-27005: Message Payload contains Invalid data, cause: {0}
Category:: Process
Cause:: Message Payload contains Invalid data.
Action:: Check the message for details.

CLONE-92100: In method doCopyConfigValidation.
Category:: Process
Cause:
Action:

CLONE-92101: In method doCopyConfig.
Category:: Process
Cause:
Action:

CLONE-92102: In method doPostCopyConfig..
Category:: Process
Cause:
Action:

CLONE-92103: In method doPasteConfigValidation.
Category:: Process
Cause:
Action:

CLONE-92104: In method doPrePasteConfig.
Category:: Process
Cause:
Action:

CLONE-92105: In method doPasteConfig.
Category:: Process
Cause:
Action:

CLONE-92106: In method doPostPasteConfig.
Category:: Process
Cause:
Action:

CLONE-92107: Download data for User Preferences.
Category:: Process
Cause:
Action:

CLONE-92109: Extract driver configuration.
Category:: Process
Cause:
Action:

CLONE-92110: Extract configuration from {0}.
Category:: Process
Cause:
Action:

CLONE-92111: Value was null for property {0}. Skip.
Category:: Process
Cause:
Action:

CLONE-92112: No UMS config found. Skip driver configuration.
Category:: Process
Cause:
Action:

CLONE-92113: Update configuration on {0}.
Category:: Process
Cause:
Action:

CLONE-92114: Upload data for User Preferences.
Category:: Process
Cause:
Action:

CLONE-92115: UMS application not present in domain. Skip doCopyConfig (no-op).
Category:: Process
Cause:
Action:

CLONE-92116: UMS application not present in domain. Skip doPasteConfig (no-op).
Category:: Process
Cause:
Action:

CLONE-92117: Starting server {0}.
Category:: Process
Cause:
Action:

CLONE-92118: Stopping server {0}.
Category:: Process
Cause:
Action:

CLONE-92119: Handle User Preferences.
Category:: Process
Cause:
Action:

CLONE-92120: Found User Preferences on {0}.
Category:: Process
Cause:
Action:

CLONE-92130: No DriverConfigExtractor found for driver type {0}. Skip.
Category:: Process
Cause:
Action:

CLONE-92300: doCopyConfig failed. msg={0} stackTrace={1}
Category:: Process
Cause:: Failure during copyConfig.
Action:: See log for details.

CLONE-92301: doPasteConfig failed. msg={0} stackTrace={1}
Category:: Process
Cause:: Failure during pasteConfig.
Action:: See log for details.

CLONE-92302: Skipped corrupted ConfigGroup for {0}
Category:: Process
Cause:: Expected one ConfigProperty within ConfigGroup.
Action:: Edit moveplan.xml or configure manually in the production system.

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

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

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

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

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

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

SDP-26306: Required OAuth login information is missing or incomplete. Consumer key, consumer secret, access token, and/or access token secret is not set.
Category:: Process
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).

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

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

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

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

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

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

SDP-26313: Ignoring geo location string ({0}) in meta data that could not be converted to (double,double).
Category:: Process
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.

SDP-26314: Failed to verify the credentials.
Category:: Process
Cause:: Failed to verify the credentials.
Action:: Check the Twitter Driver configuration.

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

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

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

SDP-25800: Oracle User Messaging Service configuration is successfully upgraded.
Category:: Process
Cause:
Action:

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

SDP-25802: Driver {0} upgraded using {1}.
Category:: Process
Cause:
Action:

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

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

SDP-25805: Server {0} upgraded using {1}.
Category:: Process
Cause:
Action:

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

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

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

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

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

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

SDP-25812: Ignoring configuration for application {0}.
Category:: Process
Cause:
Action:

SDP-25820: Error in upgrading Oracle User Messaging Service configuration. Reason: {0}
Category:: Process
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.

SDP-25821: Failed to read the configuration file {0}.
Category:: Process
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.

SDP-25822: Failed to save the configuration at {0}.
Category:: Process
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.

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

SDP-25824: Failed to parse the configuration file at {0}.
Category:: Process
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.

SDP-25825: Error during copy of configuration files from remote managed server {0}.
Category:: Process
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.

SDP-25826: Error connecting to remote managed server {0}.
Category:: Process
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.

SDP-25827: Neither the configuration nor the data entered by the user provides all information needed to copy the UMS 11g configuration files.
Category:: Process
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.

SDP-25850: Oracle User Messaging Service schema upgraded.
Category:: Process
Cause:
Action:

SDP-25851: Oracle User Messaging Service schema upgrade is valid.
Category:: Process
Cause:
Action:

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

SDP-25853: Oracle User Messaging Service schema upgrade is invalid.
Category:: Process
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.

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

SDP-25855: Error in upgrading Oracle User Messaging Service schema. {0}
Category:: Process
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.

SDP-25856: Oracle User Messaging Service schema status is invalid.
Category:: Process
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.

SDP-25857: Error in Oracle User Messaging Service schema readiness check.
Category:: Process
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.

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

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

SDP-26213: Exception while sending message - from: {0} to: {1}.
Category:: Process
Cause:: Exception while sending message.
Action:: Check stack trace and recipient address

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

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

SDP-26236: Got an exception when receiving a message.
Category:: Process
Cause:: Got an exception when receiving a message.
Action:: Check to see if the message is well-formed.