23 SDP-25001 to SDP-26457
- SDP-25038: Error while loading the messaging server configuration properties. Falling back to default configuration.
-
Cause: Unable to read from the messaging server configuration file 'configuration/appconfig.xml'.
-
Action: Check the stack trace for more details.
Level: 1
Type: WARNING
Impact: Process
- SDP-25038: Error while loading the messaging server configuration properties. Falling back to default configuration.
-
Cause: Unable to read from the messaging server configuration file 'configuration/appconfig.xml'.
-
Action: Check the stack trace for more details.
Level: 1
Type: WARNING
Impact: 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-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-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-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-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-25062: Cannot correlate status with any message; storing for possible later processing.
-
Cause: An inbound status arrived in an unexpected order.
-
Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.
Level: 1
Type: WARNING
Impact: Process
- SDP-25062: Cannot correlate status with any message; storing for possible later processing.
-
Cause: An inbound status arrived in an unexpected order.
-
Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.
Level: 1
Type: WARNING
Impact: 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-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-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-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-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-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-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-25110: An error occurred while initializing persistence session, with the following error message: {0}
-
Cause: An error occurred while attempting to initialize and log in to the TopLink persistence session.
-
Action: Check the reported error message and correct any configuration or database availability problems.
Level: 1
Type: WARNING
Impact: Process
- SDP-25110: An error occurred while initializing persistence session, with the following error message: {0}
-
Cause: An error occurred while attempting to initialize and log in to the TopLink persistence session.
-
Action: Check the reported error message and correct any configuration or database availability problems.
Level: 1
Type: WARNING
Impact: 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-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-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-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-25359: Cannot upload user device for user GUID {0}, because one already exists.
-
Cause: A user device already exists for this user.
-
Action: Try uploading the user messaging preferences using merge option 'overwrite' or 'append' (refer to command help for details).
Level: 1
Type: ERROR
Impact: Process
- SDP-25359: Cannot upload user device for user GUID {0}, because one already exists.
-
Cause: A user device already exists for this user.
-
Action: Try uploading the user messaging preferences using merge option 'overwrite' or 'append' (refer to command help for details).
Level: 1
Type: ERROR
Impact: 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-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-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-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-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-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-25726: Connection failed to remote host {0} using HTTP Proxy {1}. Error: {2}.
-
Cause: There was a problem with either the remote host or the HTTP Proxy. Check the associated connection error for the exact cause.
-
Action: Check the value of the remote host and the HTTP Proxy settings.
Level: 1
Type: ERROR
Impact: Process
- SDP-25726: Connection failed to remote host {0} using HTTP Proxy {1}. Error: {2}.
-
Cause: There was a problem with either the remote host or the HTTP Proxy. Check the associated connection error for the exact cause.
-
Action: Check the value of the remote host and the HTTP Proxy settings.
Level: 1
Type: ERROR
Impact: 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-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-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-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-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-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-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-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-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-25855: Error in upgrading Oracle User Messaging Service schema.
-
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-25855: Error in upgrading Oracle User Messaging Service schema.
-
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-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-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-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-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-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-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-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-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-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-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-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-26035: JNDI lookup of server command endpoint {0} failed with the following error message: {1}. Will retry until successful.
-
Cause: Messaging Server command module could not be located in JNDI. Driver registration will not occur until this lookup succeeds.
-
Action: Wait for server startup to proceed. If driver registration does not occur, ensure that the messaging server is deployed and started.
Level: 1
Type: WARNING
Impact: Process
- SDP-26035: JNDI lookup of server command endpoint {0} failed with the following error message: {1}. Will retry until successful.
-
Cause: Messaging Server command module could not be located in JNDI. Driver registration will not occur until this lookup succeeds.
-
Action: Wait for server startup to proceed. If driver registration does not occur, ensure that the messaging server is deployed and started.
Level: 1
Type: WARNING
Impact: Process
- SDP-26129: Unable to deliver to following addresses: {0} Reason: {1}
-
Cause: Recipient e-mail address was valid but sending failed for reason indicated in error message.
-
Action: Ensure that e-mail driver and SMTP server are operational and configured correctly, baed on information provided in error message.
Level: 1
Type: WARNING
Impact: Process
- SDP-26129: Unable to deliver to following addresses: {0} Reason: {1}
-
Cause: Recipient e-mail address was valid but sending failed for reason indicated in error message.
-
Action: Ensure that e-mail driver and SMTP server are operational and configured correctly, baed on information provided in error message.
Level: 1
Type: WARNING
Impact: Process
- SDP-26130: 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-26130: 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-26131: 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-26131: 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-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-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-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: SMPP Driver not configured. Configure and restart this driver. Required Properties: SmsAccountId, SmsServerHost, TransmitterSystemId, ReceiverSystemId, TransmitterSystemType, ReceiverSystemType, TransmitterSystemPassword, ReceiverSystemPassword, ServerTransmitterPort, ServerReceiverPort.
-
Cause: SMPP Driver was not configured.
-
Action: Configure and restart this driver. Required Properties: SmsAccountId, SmsServerHost, TransmitterSystemId, ReceiverSystemId, TransmitterSystemType, ReceiverSystemType, TransmitterSystemPassword, ReceiverSystemPassword, ServerTransmitterPort, ServerReceiverPort.
Level: 1
Type: ERROR
Impact: Process
- SDP-26160: SMPP Driver not configured. Configure and restart this driver. Required Properties: SmsAccountId, SmsServerHost, TransmitterSystemId, ReceiverSystemId, TransmitterSystemType, ReceiverSystemType, TransmitterSystemPassword, ReceiverSystemPassword, ServerTransmitterPort, ServerReceiverPort.
-
Cause: SMPP Driver was not configured.
-
Action: Configure and restart this driver. Required Properties: SmsAccountId, SmsServerHost, TransmitterSystemId, ReceiverSystemId, TransmitterSystemType, ReceiverSystemType, TransmitterSystemPassword, ReceiverSystemPassword, ServerTransmitterPort, ServerReceiverPort.
Level: 1
Type: ERROR
Impact: 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-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-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-26203: XMPP Driver not configured. Configure and restart this driver. Required properties: IMServerHost, IMServerUsername, IMServerPassword.
-
Cause: XMPP Driver was not configured.
-
Action: Configure and restart this driver. Required properties: IMServerHost, IMServerUsername, IMServerPassword.
Level: 1
Type: ERROR
Impact: Process
- SDP-26203: XMPP Driver not configured. Configure and restart this driver. Required properties: IMServerHost, IMServerUsername, IMServerPassword.
-
Cause: XMPP Driver was not configured.
-
Action: Configure and restart this driver. Required properties: IMServerHost, IMServerUsername, IMServerPassword.
Level: 1
Type: ERROR
Impact: Process
- SDP-26206: Lookup of encoded credential value for username {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: ERROR
Impact: Process
- SDP-26206: Lookup of encoded credential value for username {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: ERROR
Impact: Process
- SDP-26217: Could not locate an account to deliver this message from sender {0}. Using the first account ( {1} ) to deliver this message.
-
Cause: Could not locate an account to deliver this message.
-
Action: To retain the original message sender, add sender of the message to 'user' configuration property of the driver.
Level: 1
Type: WARNING
Impact: Process
- SDP-26217: Could not locate an account to deliver this message from sender {0}. Using the first account ( {1} ) to deliver this message.
-
Cause: Could not locate an account to deliver this message.
-
Action: To retain the original message sender, add sender of the message to 'user' configuration property of the driver.
Level: 1
Type: WARNING
Impact: Process
- SDP-26221: Third-party transport connectivity is no longer supported. Ignoring all applicable configuration properties.
-
Cause: This is an upgraded XMPP Driver instance making use of third-party transport connectivity that is no longer supported in this version.
-
Action: None
Level: 1
Type: WARNING
Impact: Process
- SDP-26221: Third-party transport connectivity is no longer supported. Ignoring all applicable configuration properties.
-
Cause: This is an upgraded XMPP Driver instance making use of third-party transport connectivity that is no longer supported in this version.
-
Action: None
Level: 1
Type: WARNING
Impact: Process
- SDP-26227: New account registration failed. It appears that the Jabber/XMPP server does not allow automatic registration. Contact the server administrator for a new account. Now disconnecting from server: {0}
-
Cause: New account registration failed. It appears that the Jabber/XMPP server does not allow automatic registration.
-
Action: Contact the server administrator for a new account.
Level: 1
Type: WARNING
Impact: Process
- SDP-26227: New account registration failed. It appears that the Jabber/XMPP server does not allow automatic registration. Contact the server administrator for a new account. Now disconnecting from server: {0}
-
Cause: New account registration failed. It appears that the Jabber/XMPP server does not allow automatic registration.
-
Action: Contact the server administrator for a new account.
Level: 1
Type: WARNING
Impact: Process
- SDP-26228: New account registration failed. Either this account already exists and you have entered an incorrect password or there is a problem with the Jabber/XMPP server. Now disconnecting from server: {0}
-
Cause: New account registration failed. Either this account already exists and you have entered an incorrect password or there is a problem with the Jabber/XMPP server.
-
Action: Check that the specified account does not exist. Check that your password is valid
Level: 1
Type: WARNING
Impact: Process
- SDP-26228: New account registration failed. Either this account already exists and you have entered an incorrect password or there is a problem with the Jabber/XMPP server. Now disconnecting from server: {0}
-
Cause: New account registration failed. Either this account already exists and you have entered an incorrect password or there is a problem with the Jabber/XMPP server.
-
Action: Check that the specified account does not exist. Check that your password is valid
Level: 1
Type: WARNING
Impact: Process
- SDP-26234: Disconnecting from Jabber/XMPP server: {0}.
-
Cause: 1) The account was disconnected by the XMPP server due to another conflicting login. 2) The XMPP server went offline.
-
Action: 1) Identify and shut down the conflicting XMPP driver that is using the same account. 2) Check the status of the XMPP server.
Level: 1
Type: NOTIFICATION
Impact: Process
- SDP-26234: Disconnecting from Jabber/XMPP server: {0}.
-
Cause: 1) The account was disconnected by the XMPP server due to another conflicting login. 2) The XMPP server went offline.
-
Action: 1) Identify and shut down the conflicting XMPP driver that is using the same account. 2) Check the status of the XMPP server.
Level: 1
Type: NOTIFICATION
Impact: Process
- SDP-26238: Cannot deliver to this {0} user, because {0} transport is not enabled in the driver. Set the value for driver parameter: {1}.
-
Cause: Because transport was not enabled in the driver, delivery could not be made to the Yahoo, MSN, AOL, or ICQ user.
-
Action: Enable the transport in the driver.
Level: 1
Type: WARNING
Impact: Process
- SDP-26238: Cannot deliver to this {0} user, because {0} transport is not enabled in the driver. Set the value for driver parameter: {1}.
-
Cause: Because transport was not enabled in the driver, delivery could not be made to the Yahoo, MSN, AOL, or ICQ user.
-
Action: Enable the transport in the driver.
Level: 1
Type: WARNING
Impact: Process
- SDP-26248: Account disconnected: {0}. Cause: Unknown. Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.
-
Cause: The account was disconnected from the server due to an unknown error.
-
Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.
Level: 1
Type: WARNING
Impact: Process
- SDP-26248: Account disconnected: {0}. Cause: Unknown. Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.
-
Cause: The account was disconnected from the server due to an unknown error.
-
Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.
Level: 1
Type: WARNING
Impact: Process
- SDP-26252: Error occurred while initializing Proxy Driver: DriverConnection returned by DriverConnectionFactory is null.
-
Cause: DriverConnection returned by DriverConnectionFactory was null
-
Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.
Level: 1
Type: ERROR
Impact: Process
- SDP-26252: Error occurred while initializing Proxy Driver: DriverConnection returned by DriverConnectionFactory is null.
-
Cause: DriverConnection returned by DriverConnectionFactory was null
-
Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.
Level: 1
Type: ERROR
Impact: Process
- SDP-26254: Failed to initialize Proxy Driver with GatewayURL={0} and Username={1}. Check driver configuration properties and remote gateway, and restart the driver.
-
Cause: Failed to initialize Proxy Driver with the specified GatewayURL, Username and Password.
-
Action: Check stack trace or error log. Check Proxy Driver properties: GatewayURL, Username and Password. Also check the status of the remote gateway.
Level: 1
Type: ERROR
Impact: Process
- SDP-26254: Failed to initialize Proxy Driver with GatewayURL={0} and Username={1}. Check driver configuration properties and remote gateway, and restart the driver.
-
Cause: Failed to initialize Proxy Driver with the specified GatewayURL, Username and Password.
-
Action: Check stack trace or error log. Check Proxy Driver properties: GatewayURL, Username and Password. Also check the status of the remote gateway.
Level: 1
Type: ERROR
Impact: Process
- SDP-26258: 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-26258: 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-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-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-26308: No configuration element was found for this Twitter Driver deployment. Create a configuration and restart this Twitter Driver.
-
Cause: No configuration element was found for this Twitter Driver deployment.
-
Action: Create a configuration and restart this Twitter Driver.
Level: 1
Type: ERROR
Impact: Process
- SDP-26308: No configuration element was found for this Twitter Driver deployment. Create a configuration and restart this Twitter Driver.
-
Cause: No configuration element was found for this Twitter Driver deployment.
-
Action: Create a configuration and restart this Twitter Driver.
Level: 1
Type: ERROR
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-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-26351: Driver property VoiceXMLReceiveURL is empty.
-
Cause: VoiceXMLReceiveURL was not set and could not be dynamically generated.
-
Action: Check the validity of the VoiceXMLReceiveURL property. Ensure the host and port are that of the server where this driver is deployed.
Level: 1
Type: ERROR
Impact: Process
- SDP-26351: Driver property VoiceXMLReceiveURL is empty.
-
Cause: VoiceXMLReceiveURL was not set and could not be dynamically generated.
-
Action: Check the validity of the VoiceXMLReceiveURL property. Ensure the host and port are that of the server where this driver is deployed.
Level: 1
Type: ERROR
Impact: Process
- SDP-26361: Lookup of encoded credential value for username {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: ERROR
Impact: Process
- SDP-26361: Lookup of encoded credential value for username {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: ERROR
Impact: Process
- SDP-26451: One or more sets of extension endpoints were configured using identical protocols and mapped domains: {0}. The first endpoint listed in the configuration file will be used.
-
Cause: Each of the listed protocol/domain pairs is used to configure multiple extension endpoints.
-
Action: Remove the conflicting endpoint configuration, or ensure that each endpoint has unique protocol and mapped domain parameters.
Level: 1
Type: WARNING
Impact: Process
- SDP-26451: One or more sets of extension endpoints were configured using identical protocols and mapped domains: {0}. The first endpoint listed in the configuration file will be used.
-
Cause: Each of the listed protocol/domain pairs is used to configure multiple extension endpoints.
-
Action: Remove the conflicting endpoint configuration, or ensure that each endpoint has unique protocol and mapped domain parameters.
Level: 1
Type: WARNING
Impact: 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-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 element was found for this Extension Driver deployment. Create a configuration and restart this Extension Driver.
-
Cause: No configuration element was found for this Extension Driver deployment.
-
Action: Create a configuration and restart this Extension Driver.
Level: 1
Type: ERROR
Impact: Process
- SDP-26453: No configuration element was found for this Extension Driver deployment. Create a configuration and restart this Extension Driver.
-
Cause: No configuration element was found for this Extension Driver deployment.
-
Action: Create a configuration and restart this Extension Driver.
Level: 1
Type: ERROR
Impact: Process
- SDP-26454: Extension Driver not configured. Configure and restart this driver. The configuration must contain at least one Extension endpoint with a valid endpoint URL and protocol.
-
Cause: Extension Driver was not configured.
-
Action: Configure and restart this driver. The configuration must contain at least one Extension endpoint with a valid endpoint URL and protocol.
Level: 1
Type: ERROR
Impact: Process
- SDP-26454: Extension Driver not configured. Configure and restart this driver. The configuration must contain at least one Extension endpoint with a valid endpoint URL and protocol.
-
Cause: Extension Driver was not configured.
-
Action: Configure and restart this driver. The configuration must contain at least one Extension endpoint with a valid endpoint URL and protocol.
Level: 1
Type: ERROR
Impact: Process
- SDP-26455: Error while processing Extension Driver configuration for property group with Endpoint URL: {0}. Check the corresponding property group configuration, then restart this driver. The configuration must contain an Extension endpoint with a valid endpoint URL and protocol.
-
Cause: An error occurred while processing the Extension Driver configuration.
-
Action: Check the corresponding property group configuration, then restart this driver. The configuration must contain an Extension endpoint with a valid endpoint URL and protocol.
Level: 1
Type: ERROR
Impact: Process
- SDP-26455: Error while processing Extension Driver configuration for property group with Endpoint URL: {0}. Check the corresponding property group configuration, then restart this driver. The configuration must contain an Extension endpoint with a valid endpoint URL and protocol.
-
Cause: An error occurred while processing the Extension Driver configuration.
-
Action: Check the corresponding property group configuration, then restart this driver. The configuration must contain an Extension endpoint with a valid endpoint URL and protocol.
Level: 1
Type: 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-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