This section documents the set of messages that the SOA
Service Platform Common components can issue.
- SOAS1000E:{0}:{1} Invalid value for network resource {2} property: {3}
- Explanation:
- {0} is the transaction ID for the traffic shaping common component request.
{1} is the name of the component that issued the message.
{2} is the network resource name whose resource specification was being accessed.
{3} is the network resource property that was missing or invalid.
The network resource property was missing or contained an invalid specification property.
- User Response:
-
- Check the network resource specification for the specified network resource
and verify that the specification contains the property name and a valid value.
- SOAS1500E:{0}{1} Parameter object is null.
- SOAS1504E:{0}{1} One or more required parameter(s) is invalid.
- SOAS1505E:{0}{1} Failed to create the {2}. The specified {2} may exist: {3}.
- SOAS1506E:{0}{1} Failed to update the {2} description. The specified {2} may not exist: {3}.
- SOAS1507E:{0}{1} Failed to update the {2} status. The specified {2} may not exist: {3}.
- SOAS1508E:{0}{1} Failed to get the {2} status. The specified {2} may not exist: {3}.
- SOAS1509E:{0}{1} Failed to remove the {2}. The specified {2} may not exist: {3}.
- SOAS1510E:{0}{1} Failed to retrieve {2}. The {2} may not exist: {3}.
- SOAS1511E:{0}{1} Policy name-value pair are invalid, params: {2}.
- SOAS1512E:{0}{1} Failed to create a SQL Connection.
- SOAS1513E:{0}{1} SQL statement failed writing to the database.
- SOAS1514E:{0}{1} SQL Illegal Argument writing to the database.
- SOAS1515E:{0}{1} SQL Failed to close SQL connection.
- SOAS1516E:{0}{1} SQL statement error.
- SOAS1517E:{0}{1} Illegal SQL state exception.
- SOAS1518E:{0}{1} NotificationRecord not found in database.
- SOAS1519E:{0}{1} SQL error reading a row or colum from the DB query.
- SOAS1520E:{0}{1} Invalid input value {2} for message part {3}.
- SOAS1521I:{0}{1} An invalid message part was received: [service = {2},[requester = {3}],[correlator = {4}]
- Invalid input value %1 for message part %2.
- SOAS1523E:{0}{1} A service error occurred. Failure reason is {2}.
- SOAS1524I:{0}{1} Unable to remove notification records: [service = {2}],[requester = {3}],[correlator = {4}],[reason = {5}],[details = {6}]
- A service error occurred. Failure reason is %1.
- SOAS1526E:{0}{1} Notification records not found.
- SOAS1527I:{0}{1} Unable to find notification records: [service = {2}],[requester = {3}],[correlator = {4}]
- Notification records not found.
- SOAS1529E:{0}{1} Duplicate Record found.
- SOAS1530E:{0}{1} Unable to close database connections.
- SOAS1531E:{0}{1} GlobalID Notification records not found.
- SOAS1532E:{0}{1} Start and End Notification records not found.
- SOAS1533E:{0}{1} Target and Criteria Notification records not found.
- SOAS1534E:{0}{1} Terminate All Notification records not found.
- SOAS1535E:{0}{1} PortType and EndPoint Notification records not found.
- SOAS1536E:{0}{1} FindAll Notifications returned no records.
- SOAS1537E:{0}{1} ResetAll Notifications records not found.
- SOAS1538E:{0}{1} NotificationAdministrationSupport Interface not supported.
- SOAS1539E:{0}{1} Notification Manager Server error {2}.
- SOAS2000E:{0}:{1} Invalid Delivery Method Specified [{2}].
- Explanation:
- {0} is the transaction ID for the pxnotify common component request.
{1} is the name of the component that issued the message.
{2} is the delivery method specified.
An invalid delivery method was specified in the message.
- User Response:
-
- None: possibly a programming error.
- SOAS2001E:{0}:{1} Invalid message category received [{2}].
- Explanation:
- {0} is the transaction ID for the pxnotify common component request.
{1} is the name of the component that issued the message.
{2} is the message category that was received
An message with an invalid message category was received.
- User Response:
-
- None: possibly a programming error.
- SOAS2002E:{0}:{1} Invalid message operation received [{2}], for category {3}.
- Explanation:
- {0} is the transaction ID for the pxnotify common component request.
{1} is the name of the component that issued the message.
{2} is the name of the operation.
{3} is the operation category.
An invalid message operation was received.
- User Response:
-
- None: possibly a programming error.
- SOAS2003E:{0}:{1} Invalid JMS Message type received [{2}], expected javax.jms.ObjectMessage .
- Explanation:
- {0} is the transaction ID for the pxnotify common component request.
{1} is the name of the component that issued the message.
{2} is the class name of the invalid JMS message type.
An invalid JMS message type was received when an javax.jms.ObjectMessage type was expected.
- User Response:
-
- None: possibly a programming error.
- SOAS2004E:{0}:{1} Error extracting data from JMS message.
- Explanation:
- {0} is the transaction ID for the pxnotify common component request.
{1} is the name of the component that issued the message.
An exception occurred while trying to extracting data from a JMS message.
- User Response:
-
- None: possibly a programming error.
- SOAS2005E:{0}:{1} Invalid Callback endpoint value specified [{2}].
- Explanation:
- {0} is the transaction ID for the pxnotify common component request.
{1} is the name of the component that issued the message.
{2} is the callback endpoint value.
An invalid callback endpoint value was specified.
- User Response:
-
- Verify that the callback endpoint was correctly configured.
- SOAS2006E:{0}:{1} Empty or Null ESB endpoint URI specified.
- Explanation:
- {0} is the transaction ID for the pxnotify common component request.
{1} is the name of the component that issued the message.
An empty or null ESB endpoint URI was specified.
- User Response:
-
- SOAS2007E:{0}:{1} Invalid numeric timeout value specified [{2}].
- Explanation:
- {0} is the transaction ID for the pxnotify common component request.
{1} is the name of the component that issued the message.
{2} is the numeric timeout value that was specified.
An invalid numeric timeout value was specified for the endpoint component.
- User Response:
-
- Verify that the timeout value specified for the endpoint component has been
correctly configured.
- SOAS2008E:{0}:{1} Throwable exception caught, unable to issue callback, error: [{2}].
- Explanation:
- {0} is the transaction ID for the pxnotify common component request.
{1} is the name of the component that issued the message.
{2} is the message from the throwable exception.
Throwable exception caught, unable to issue a callback because the
SPNotificationExtension was not available.
- User Response:
-
- None: review exception message for possible causes.
- SOAS2009E:{0}:{1} Invalid ESB endpoint URI specified [{2}].
- Explanation:
- {0} is the transaction ID for the pxnotify common component request.
{1} is the name of the component that issued the message.
{2} is the the endpoint URI that was specified.
An invalid ESB endpoint URI was specified.
- User Response:
-
- Verify that the endpoint has been correctly configured.
- SOAS2010E:{0}:{1} Empty or Null Delivery Method specified.
- Explanation:
- {0} is the transaction ID for the pxnotify common component request.
{1} is the name of the component that issued the message.
An empty or null delivery method was specified.
- User Response:
-
- None: possibly a programming error.
- SOAS2011E:{0}:{1} Error attempting to delivery notification, error: [{2}].
- Explanation:
- {0} is the transaction ID for the pxnotify common component request.
{1} is the name of the component that issued the message.
{2} is the message from the exception that occurred.
An exception occurred while attempting to delivery notification
to an operation category.
- User Response:
-
- None: review exception message for possible causes.
- SOAS3000E:{0}:{1} Request object is null.
- Explanation:
- {0} is the transaction ID for the usage records common component request.
{1} is the name of the usage records common component.
The request object received is null.
- User Response:
-
- None: possibly a programming error.
- SOAS3001E:{0}:{1} Write usage record failed. Check trace for details.
- Explanation:
- {0} is the transaction ID for the usage records common component request.
{1} is the name of the usage records common component.
Unable to write a usage record.
- User Response:
-
- Check the trace log for possible causes.
- SOAS3002E:{0}:{1} Read usage record failed. Check trace for details.
- Explanation:
- {0} is the transaction ID for the usage records common component request.
{1} is the name of the usage records common component.
Unable to read a usage record.
- User Response:
-
- Check the trace log for possible causes.
- SOAS3003E:{0}:{1} Could not access datasource.
- Explanation:
- {0} is the transaction ID for the usage records common component request.
{1} is the name of the usage records common component.
Unable to access the datasource.
- User Response:
-
- Check the trace log for possible causes.
- SOAS3004E:{0}:{1} Could not get a database connection.
- Explanation:
- {0} is the transaction ID for the usage records common component request.
{1} is the name of the usage records common component.
Unable to get a database connection.
- User Response:
-
- Check the trace log for possible causes.
- SOAS3005E:{0}:{1} Unable to close database connection.
- Explanation:
- {0} is the transaction ID for the usage records common component request.
{1} is the name of the usage records common component.
Unable to close a database connection.
- User Response:
-
- Check the trace log for possible causes.
- SOAS3006E:{0}:{1} Invalid usage record field: {2}.
- SOAS3007E:{0}:{1} Error writing usage record to database: {2}
- SOAS4001E:{0}{1} Invalid input parameter, params: {2}
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter value in the input
Invalid input parameter.
- User Response:
-
- Verify the input parameters, and use valid parameter(s) to try again
- SOAS4002E:{0}{1} Operation failed, the parameter {2} is not valid, params: {3}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter(s) in the input
{3} is the invalid parameter value in the input
Operation failed, the parameter is not valid
- User Response:
-
- Verify the input parameters, and use valid parameter(s) to try again
- SOAS4003E:{0}{1} Operation failed, the specified {2} already exists, params: {3}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter(s) in the input
{3} is the invalid parameter value in the input
The specified parameter already exists.
- User Response:
-
- Verify the input parameters, and use valid parameter(s) to try again
- SOAS4004E:{0}{1} Operation failed, the specified {2} does not exist, params: {3}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter(s) in the input
{3} is the invalid parameter value in the input
Operation failed, the specified parameter does not exist
- User Response:
-
- Verify the input parameters, and use valid parameter(s) to try again
- SOAS4005E:{0}{1} Operation failed, the type of specified {2} is not valid for creating {3}, params: {4}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter(s) in the input
{3} is the invalid parameter type in the input
{4} is the invalid parameter value in the input
Operation failed, the specified parameter is not valid in the creation operation
- User Response:
-
- Verify the input parameters, and use valid parameter(s) to try again
- SOAS4006E:{0}{1} Operation failed, the specified {2} is the same with the existing one, params: {3}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter(s) in the input
{3} is the invalid parameter value in the input
Operation failed, the specified parameter is the same with the existing one
- User Response:
-
- Verify the input parameters, and use valid parameter(s) to try again
- SOAS4007E:{0}{1} Operation failed, the predefined {2} cannot be created or removed, params: {3}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter(s) in the input
{3} is the invalid parameter value in the input
Operation failed, the specified parameter is predefined value which can not be created or removed
- User Response:
-
- Verify the input parameters, and use valid parameter(s) to try again
- SOAS4008E:{0}{1} Operation failed, the specified {2} cannot be removed because it contains children, params: {3}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter(s) in the input
{3} is the invalid parameter value in the input
Operation failed, the specified parameter cannnot be removed becaue it contains children
- User Response:
-
- Verify the input parameters, and use valid parameter(s) to try again
- SOAS4009E:{0}{1} Operation failed, the specified {2} may not contain {3}, params: {4}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter(s) in the input
{3} is the invalid parameter type in the input
{4} is the invalid parameter value in the input
Operation failed, the specified parameter may not contain the specified type.
- User Response:
-
- Verify the input parameters, and use valid parameter(s) to try again
- SOAS4010E:{0}{1} Operation failed, the specified {2} is not an individual {2}, params: {3}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter(s) in the input
{3} is the invalid parameter value in the input
Operation failed, the specified parameter is not an individual type
- User Response:
-
- Verify the input parameters, and use valid parameter(s) to try again
- SOAS4011E:{0}{1} Operation failed, the specified {2} or one of its parents is disabled, params: {3}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter(s) in the input
{3} is the invalid parameter value in the input
Operation failed, the specified parameter or one of its parent is disabled
- User Response:
-
- Make sure the item and its parent are enabled, and then try again
- SOAS4012E:{0}{1} Operation failed, the specified Subscription cannot be created because a subscription to a different implementation of the same service already exists, params: {2}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter value in the input
Operation failed, the specified Subscription cannot be created because a subscription to a different implementation of the same service already exists.
- User Response:
-
- (1) Remove existing subscription, or (2)Verify the input parameters, and use valid parameter(s), then try again
- SOAS4013E:{0}{1} Operation failed, the type of specified {2} is not a group, params: {3}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter(s) in the input
{3} is the invalid parameter value in the input
Operation failed, the specified parameter is not a group.
- User Response:
-
- Verify the input parameters, and use valid parameter(s) to try again
- SOAS4014E:{0}{1} Operation failed, the specified {2} is not editable, params: {3}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter(s) in the input
{3} is the invalid parameter value in the input
Operation failed, the specified parameter is not editable.
- User Response:
-
- Verify the input parameters, and use valid parameter(s) to try again
- SOAS4015E:{0}{1} Operation failed, the specified {2} and {3} cannot be same, params: {4}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter(s) in the input
{3} is the invalid parameter in the input
{4} is the invalid parameter value in the input
Operation failed, the specified parameter may not contain the specified type.
- User Response:
-
- Verify the input parameters, and use valid parameter(s) to try again
- SOAS4016E:{0}{1} Operation failed, the specified policy value does not match the policy type, params: {2}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter value in the input
Operation failed, the specified policy value does not match the policy type.
- User Response:
-
- Make sure policy value and type are compatible,then try again
- SOAS4017E:{0}{1} Operation failed, the type of specified {2} is neither an individual service nor a service group, params: {3}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter(s) in the input
{3} is the invalid parameter value in the input
Operation failed, the type of specified parameter is neither an individual service nor a service group.
- User Response:
-
- Make sure the parameter is a individual service or service group, then try again
- SOAS4018E:{0}{1} Operation failed, the specified {2} can not be the child item or one of its descendants, params: {3}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter(s) in the input
{3} is the invalid parameter value in the input
Operation failed, the specified parameter can not be the child item or one of its descendants.
- User Response:
-
- Verify the input parameters, and use valid parameter(s) to try again
- SOAS4019E:{0}{1} Operation failed, the parent of predefined {2} ALL cannot be updated, params: {3}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter(s) in the input
{3} is the invalid parameter value in the input
Operation failed, the parent of predefined ALL cannot be updated.
- User Response:
-
- Verify the input parameters, and use valid parameter(s) to try again
- SOAS4020E:{0}{1} Operation failed, the value of the parameter {2} exceeds the maximum length allowed (250 characters), params: {3}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter(s) in the input
{3} is the invalid parameter value in the input
Operation failed, the value of the parameter exceeds the maximum length allowed (250 characters).
- User Response:
-
- Verify the input parameters, and use valid parameter(s) to try again
- SOAS4021E:{0}{1} Operation failed, the specified {2} contains an invalid occurrence of the escape character (the escape character can only appear in the pattern string if it is followed by itself, %, or _), params: {2}.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
{2} is the invalid parameter(s) in the input
{3} is the invalid parameter value in the input
Operation failed, the specified parameter contains an invalid occurrence of the escape character (the escape character can only appear in the pattern string if it is followed by itself, %, or _).
- User Response:
-
- Verify the input parameters, and use valid parameter(s) to try again
- SOAS4496E:{0}{1} Failed to get data source.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
Failed to get data source.
- User Response:
-
- Datasoure is not configure properly, please contact administrator
- SOAS4497E:{0}{1} Failed to get database connection.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
Failed to get database connection.
- User Response:
-
- Database is not running or connection parameter is not specified properly, please contact administrator
- SOAS4498E:{0}{1} Internal database error.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
Internal database error.
- User Response:
-
- Database is not in consistent state or a database error occurs, please contact administrator
- SOAS4499E:{0}{1} Internal service error.
- Explanation:
- {0} Empty, reserved for transaction ID.
{1} is the name of the component that issued the message, which is "ServicePolicyManager".
Internal service error.
- User Response:
-
- Please contact administrator
- SOAS4500E: An internal error occurred; the Service Policy Manager Console was unable to fulfill the request.
- Explanation:
- An internal problem prevented the application
from successfully processing your request.
- User Response:
-
- Please contact the administrator and/or examine the system logs.
- Diagnosing the problem will require enabling diagnostic trace.
- SOAS4501E: Unable to contact the Service Policy Manager Console.
- Explanation:
- The web browser either could not contact the application, or it did
not receive a timely response from the application.
- User Response:
-
- Please check connectivity with the application server.
-
- After checking connectivity,
please attempt to re-login to the application.
- Diagnosing the problem may require enabling the diagnostic trace.
- SOAS4502E: Unauthorized to access the Service Policy Manager Console.
- Explanation:
- The server reported that you are not authorized to access
this content or function.
- User Response:
-
- Please verify the your username and password.
- Please verify that you are authorized to access the application.
- Please contact the administrator and/or examine the system logs.
- SOAS4503E: A malformed request was reported; the Service Policy Manager Console was unable to fulfill the request.
- Explanation:
- The application reports that you've issued a malformed request
that it could not process.
- User Response:
-
- Please contact the administrator and/or examine the system logs.
- Diagnosing the problem will require enabling diagnostic trace.