WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Messages_SOAX_en_US

This section documents the set of messages that the SOA Service Implementation components can issue.

SOAX0001E:{0}{1} {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the component that issued the message. A Parlay X Web Service fault condition occurred.
User Response:
  • Review the Parlay X Web Service fault documentation for more information.
SOAX0002I:{0}{1} Operation {2} must be invoked within an existing session: {3}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the name of the Web Service operation invoked by the client. {3} contains details about the specific session object and value (example: "HttpSession == null") behind receipt of this message. An incoming Web Service request needed to within a preexisting session, but was not. Because of the lack of a preexisting session, the request was rejected.
User Response:
  • Ensure the Web services client is maintaining sessions across multiple Web Service requests.
  • Ensure the Web services client is following the expected use case/method invocation order. Example: invoking StartNotification before EndNotification.
SOAX0004I:{0}{1} Policy {2} with value {3} is malformed; it must follow the syntax and semantics of the configuration setting {4}
Explanation:
{0} is the transaction ID for the Web Service request. {1} is the name of the service implementation that issued the message. {2} is the name of the policy provided by the client. {3} is the value of the policy provided by the client. {4} is the name of the configuration setting corresponding to the policy. An incoming Web Service request specified a policy value that was invalid according to the syntax and semantics of the corresponding configuration setting. Because it could not service the request's malformed policy value, the service implementation rejected the request.
User Response:
  • Ensure the Web Services client is providing the intended policy
  • Ensure the Web Services client is providing a value that is valid for the setting according to the administrative console. Refer to the administrative console's help for details on each of the settings.
SOAX0005I:{0}{1} Policy {2} with value {3} is invalid; its value must be more restrictive than the configuration setting {4} which has value {5}
Explanation:
{0} is the transaction ID for the Web Service request. {1} is the name of the service implementation that issued the message. {2} is the name of the policy provided by the client. {3} is the value of the policy provided by the client. {4} is the name of the configuration setting corresponding to the policy. {5} is the current value the configuration setting. An incoming Web Service request specified a policy value that was less restrictive than the corresponding configuration setting's value. Incoming policy values must be more restrictive than the settings they override. This is to ensure that policy does not violate installation-specific settings. Because it could not service the request's invalid policy value, the service implementation rejected the request.
User Response:
  • Ensure the Web Services client is providing the intended policy
  • Ensure the Web Services client is providing a value that is valid for the setting according to the administrative console. Refer to the administrative console's help for details on each of the settings.
  • Ensure the Web Services client is providing a value that is more restrictive than the current administrative console setting. The notion of "more restrictive" varies on a per-setting basis.
SOAX0006I:{0}{1} Policy {2} with value {3} is invalid; it attempts to overwrite the read-only configuration setting {4}.
Explanation:
{0} is the transaction ID for the Web Service request. {1} is the name of the service implementation that issued the message. {2} is the name of the policy provided by the client. {3} is the value of the policy provided by the client. {4} is the name of the configuration setting corresponding to the policy. An incoming Web Service request specified a policy value that attempts to override a read-only configuration setting. Because it could not service the request's invalid policy value, the service implementation rejected the request.
User Response:
  • Ensure the Web Services client is providing the intended policy.
  • Some configuration settings cannot be overridden. See the administrative console help for more details on the given configuration setting.
SOAX0100E:{0}{1} Admission control rejected request; it would exceed per service limit
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. The Admission Control component rejected a request because accepting it would exceed the currently defined per service limits.
User Response:
  • If you know the per service limits are correct, no action is required
  • Otherwise, correct Admission Control's per service limits
SOAX0101W:{0}{1} Admission control rejected request; it would exceed per service limit
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. The Admission Control component rejected a request because accepting it would exceed the currently defined per service limits.
User Response:
  • If you know the per service limits are correct, no action is required
  • Otherwise, correct Admission Control's per service limits
SOAX0102I:{0}{1} Admission control rejected request; it would exceed per service limit
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. The Admission Control component rejected a request because accepting it would exceed the currently defined per service limits.
User Response:
  • If you know the per service limits are correct, no action is required
  • Otherwise, correct Admission Control's per service limits
SOAX0103E:{0}{1} Admission control rejected request; it would exceed per operation limit
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. The Admission Control component rejected a request because accepting it would exceed the currently defined per operation limits.
User Response:
  • If you know the per service limits are correct, no action is required
  • Otherwise, correct Admission Control's per service, per operation limits
SOAX0104W:{0}{1} Admission control rejected request; it would exceed per operation limit
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. The Admission Control component rejected a request because accepting it would exceed the currently defined per operation limits.
User Response:
  • If you know the per service limits are correct, no action is required
  • Otherwise, correct Admission Control's per service, per operation limits
SOAX0105I:{0}{1} Admission control rejected request; it would exceed per operation limit
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. The Admission Control component rejected a request because accepting it would exceed the currently defined per operation limits.
User Response:
  • If you know the per service limits are correct, no action is required
  • Otherwise, correct Admission Control's per service, per operation limits
SOAX0106E:{0}{1} Traffic shaping rejected request; it would exceed limits for resource {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the name of the resource whose limits would be exceeded. The Traffic Shaping component rejected a request because accepting it would exceed limits for the specified resource.
User Response:
  • If you know the per service limits are correct, no action is required
  • Otherwise, correct Traffic Shaping's per resource, per operation limits
SOAX0107W:{0}{1} Traffic shaping rejected request; it would exceed limits for resource {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the name of the resource whose limits would be exceeded. The Traffic Shaping component rejected a request because accepting it would exceed limits for the specified resource.
User Response:
  • If you know the per service limits are correct, no action is required
  • Otherwise, correct Traffic Shaping's per resource, per operation limits
SOAX0108I:{0}{1} Traffic shaping rejected request; it would exceed limits for resource {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the name of the resource whose limits would be exceeded. The Traffic Shaping component rejected a request because accepting it would exceed limits for the specified resource.
User Response:
  • If you know the per service limits are correct, no action is required
  • Otherwise, correct Traffic Shaping's per resource, per operation limits
SOAX0109E:{0}{1} Unable to register notification; Notification management reported fault: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the fault reported by the notification management component. The Notification Management component reported an error while trying to register a new notification.
User Response:
  • Examine the reported fault and detail message. Consult the Notification Management component documentation for more information.
SOAX0110W:{0}{1} Unable to register notification; Notification management reported fault: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the fault reported by the notification management component. The Notification Management component reported an error while trying to register a new notification.
User Response:
  • Examine the reported fault and detail message. Consult the Notification Management component documentation for more information.
SOAX0111I:{0}{1} Unable to register notification; Notification management reported fault: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the fault reported by the notification management component. The Notification Management component reported an error while trying to register a new notification.
User Response:
  • Examine the reported fault and detail message. Consult the Notification Management component documentation for more information.
SOAX0112E:{0}{1} Unable to remove notification; Notification management reported fault: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the fault reported by the notification management component. The Notification Management component reported an error while trying to remove an existing notification.
User Response:
  • Examine the reported fault and detail message. Consult the Notification Management component documentation for more information.
SOAX0113W:{0}{1} Unable to remove notification; Notification management reported fault: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the fault reported by the notification management component. The Notification Management component reported an error while trying to remove an existing notification.
User Response:
  • Examine the reported fault and detail message. Consult the Notification Management component documentation for more information.
SOAX0114I:{0}{1} Unable to remove notification; Notification management reported fault: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the fault reported by the notification management component. The Notification Management component reported an error while trying to remove an existing notification.
User Response:
  • Examine the reported fault and detail message. Consult the Notification Management component documentation for more information.
SOAX0115E:{0}{1} Usage record component reported fault while writing record: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the fault reported by the usage record component. The Usage Record component reported an error while trying to write a record.
User Response:
  • Examine the reported fault and detail message. Consult the Usage Record component documentation for more information.
SOAX0116W:{0}{1} Usage record component reported fault while writing record: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the fault reported by the usage record component. The Usage Record component reported an error while trying to write a record.
User Response:
  • Examine the reported fault and detail message. Consult the Usage Record component documentation for more information.
SOAX0117I:{0}{1} Usage record component reported fault while writing record: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the fault reported by the usage record component. The Usage Record component reported an error while trying to write a record.
User Response:
  • Examine the reported fault and detail message. Consult the Usage Record component documentation for more information.
SOAX0118E:{0}{1} Usage record component reported fault while reading recordID {2}: {3}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the existing record that the service implementation is trying to read. {3} is the fault reported by the usage record component. The Usage Record component reported an error while trying to read an existing record.
User Response:
  • Examine the reported fault and detail message. Consult the Usage Record component documentation for more information.
SOAX0119W:{0}{1} Usage record component reported fault while reading recordID {2}: {3}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the existing record that the service implementation is trying to read. {3} is the fault reported by the usage record component. The Usage Record component reported an error while trying to read an existing record.
User Response:
  • Examine the reported fault and detail message. Consult the Usage Record component documentation for more information.
SOAX0120I:{0}{1} Usage record component reported fault while reading recordID {2}: {3}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the existing record that the service implementation is trying to read. {3} is the fault reported by the usage record component. The Usage Record component reported an error while trying to read an existing record.
User Response:
  • Examine the reported fault and detail message. Consult the Usage Record component documentation for more information.
SOAX0121E:{0}{1} Privacy component reported fault while retrieving information: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the fault reported by the privacy component. The Privacy component reported an error while trying to process a privacy information request.
User Response:
  • Examine the reported fault and detail message. Consult the Privacy component documentation for more information.
SOAX0122W:{0}{1} Privacy component reported fault while retrieving information: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the fault reported by the privacy component. The Privacy component reported an error while trying to process a privacy information request.
User Response:
  • Examine the reported fault and detail message. Consult the Privacy component documentation for more information.
SOAX0123I:{0}{1} Privacy component reported fault while retrieving information: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the fault reported by the privacy component. The Privacy component reported an error while trying to process a privacy information request.
User Response:
  • Examine the reported fault and detail message. Consult the Privacy component documentation for more information.
SOAX0124E:{0}{1} No admission control limits configured for service {2} operation {3}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the name of the service that no admission control limits are defined for. {3} is the name of the operation that no admission control limits are defined for. The admission control component is rejecting incoming requests because it has not been configured for this given service and operation.
User Response:
  • Configure the admission control component within appropriate limits for this service and operation.
SOAX0125W:{0}{1} No admission control limits configured for service {2} operation {3}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the name of the service that no admission control limits are defined for. {3} is the name of the operation that no admission control limits are defined for. The admission control component is rejecting incoming requests because it has not been configured for this given service and operation.
User Response:
  • Configure the admission control component within appropriate limits for this service and operation.
SOAX0126I:{0}{1} No admission control limits configured for service {2} operation {3}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the name of the service that no admission control limits are defined for. {3} is the name of the operation that no admission control limits are defined for. The admission control component is rejecting incoming requests because it has not been configured for this given service and operation.
User Response:
  • Configure the admission control component within appropriate limits for this service and operation.
SOAX0127E:{0}{1} Traffic shaping not configured for resource {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the name of the resource without a traffic shaping configuration. The traffic shaping component is rejecting incoming requests because the given resource has not been configured.
User Response:
  • Configure the traffic shaping component within appropriate limits for this resource.
SOAX0128W:{0}{1} Traffic shaping not configured for resource {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the name of the resource without a traffic shaping configuration. The traffic shaping component is rejecting incoming requests because the given resource has not been configured.
User Response:
  • Configure the traffic shaping component within appropriate limits for this resource.
SOAX0129I:{0}{1} Traffic shaping not configured for resource {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the name of the resource without a traffic shaping configuration. The traffic shaping component is rejecting incoming requests because the given resource has not been configured.
User Response:
  • Configure the traffic shaping component within appropriate limits for this resource.
SOAX0130E:{0}{1} Traffic shaping reports an invalid resource specification: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the name of the resource with an invalid traffic shaping configuration. The traffic shaping component is rejecting incoming requests because the given resource has been configured incorrectly.
User Response:
  • Repair the traffic shaping configuration for this resource.
SOAX0131W:{0}{1} Traffic shaping reports an invalid resource specification: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the name of the resource with an invalid traffic shaping configuration. The traffic shaping component is rejecting incoming requests because the given resource has been configured incorrectly.
User Response:
  • Repair the traffic shaping configuration for this resource.
SOAX0132I:{0}{1} Traffic shaping reports an invalid resource specification: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the name of the resource with an invalid traffic shaping configuration. The traffic shaping component is rejecting incoming requests because the given resource has been configured incorrectly.
User Response:
  • Repair the traffic shaping configuration for this resource.
SOAX0133E:{0}{1} Parlay X notification delivery unable to deliver notification: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the error detail from the Parlay X notification delivery component. The Parlay X notification delivery component could not deliver the requested notification.
User Response:
  • Examine the error detail and consult the Parlay X notification delivery component documentation to resolve.
SOAX0134W:{0}{1} Parlay X notification delivery unable to deliver notification: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the error detail from the Parlay X notification delivery component. The Parlay X notification delivery component could not deliver the requested notification.
User Response:
  • Examine the error detail and consult the Parlay X notification delivery component documentation to resolve.
SOAX0135I:{0}{1} Parlay X notification delivery unable to deliver notification: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the error detail from the Parlay X notification delivery component. The Parlay X notification delivery component could not deliver the requested notification.
User Response:
  • Examine the error detail and consult the Parlay X notification delivery component documentation to resolve.
SOAX0150E:{0}{1} Error invoking the admission control component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the admission control common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the admission control component endpoint
  • Ensure that the admission control component is accepting requests
SOAX0151W:{0}{1} Error invoking the admission control component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the admission control common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the admission control component endpoint
  • Ensure that the admission control component is accepting requests
SOAX0152I:{0}{1} Error invoking the admission control component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the admission control common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the admission control component endpoint
  • Ensure that the admission control component is accepting requests
SOAX0153E:{0}{1} Error invoking the traffic shaping component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the traffic shaping common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the traffic shaping component endpoint
  • Ensure that the traffic shaping component is accepting requests
SOAX0154W:{0}{1} Error invoking the traffic shaping component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the traffic shaping common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the traffic shaping component endpoint
  • Ensure that the traffic shaping component is accepting requests
SOAX0155I:{0}{1} Error invoking the traffic shaping component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the traffic shaping common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the traffic shaping component endpoint
  • Ensure that the traffic shaping component is accepting requests
SOAX0156E:{0}{1} Error invoking the notification management component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the notification management common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the notification management component endpoint.
  • Ensure that the notification management component is accepting requests.
SOAX0157W:{0}{1} Error invoking the notification management component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the notification management common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the notification management component endpoint.
  • Ensure that the notification management component is accepting requests.
SOAX0158I:{0}{1} Error invoking the notification management component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the notification management common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the notification management component endpoint.
  • Ensure that the notification management component is accepting requests.
SOAX0159E:{0}{1} Error invoking the Parlay X notification delivery component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the Parlay X Notification Delivery common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the notification delivery component endpoint.
  • Ensure that the notification delivery component is accepting requests.
SOAX0160W:{0}{1} Error invoking the Parlay X notification delivery component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the Parlay X Notification Delivery common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the notification delivery component endpoint.
  • Ensure that the notification delivery component is accepting requests.
SOAX0161I:{0}{1} Error invoking the Parlay X notification delivery component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the Parlay X Notification Delivery common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the notification delivery component endpoint.
  • Ensure that the notification delivery component is accepting requests.
SOAX0162E:{0}{1} Error invoking the usage record component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the usage record common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the usage record component endpoint.
  • Ensure that the usage record component is accepting requests.
SOAX0163W:{0}{1} Error invoking the usage record component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the usage record common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the usage record component endpoint.
  • Ensure that the usage record component is accepting requests.
SOAX0164I:{0}{1} Error invoking the usage record component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the usage record common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the usage record component endpoint.
  • Ensure that the usage record component is accepting requests.
SOAX0165E:{0}{1} Error invoking the privacy component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the privacy common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the privacy component endpoint.
  • Ensure that the privacy component is accepting requests.
SOAX0166W:{0}{1} Error invoking the privacy component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the privacy common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the privacy component endpoint.
  • Ensure that the privacy component is accepting requests.
SOAX0167I:{0}{1} Error invoking the privacy component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the privacy common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the privacy component endpoint.
  • Ensure that the privacy component is accepting requests.
SOAX0168E:{0}{1} Error invoking the faults and alarms component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the faults and alarms common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the faults and alarms component endpoint.
  • Ensure that the faults and alarms component is accepting requests.
SOAX0169W:{0}{1} Error invoking the faults and alarms component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the faults and alarms common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the faults and alarms component endpoint.
  • Ensure that the faults and alarms component is accepting requests.
SOAX0170I:{0}{1} Error invoking the faults and alarms component: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the exception that was returned while invoking the common component. The service implementation encountered an unexpected exception while invoking the faults and alarms common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the faults and alarms component endpoint.
  • Ensure that the faults and alarms component is accepting requests.
SOAX0200I:{0}{1} Check that endpoint is properly configured. Ensure configured endpoint is accepting requests.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. The service implementation encountered an unexpected exception while invoking a common component. This may be due to invalid endpoint information, network connectivity problems, remote server errors, etc.
User Response:
  • Verify the configuration for the relevant component endpoint.
  • Ensure that the component is accepting requests.
SOAX0201I:{0}{1} Configure admission control limits for this service and operation.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. The admission control component reported that this service or operation has no currently configured admission limits.
User Response:
  • Create the admission configuration for this service or operation, or both.
SOAX0202I:{0}{1} Check that traffic shaping component has been properly configured for this resource.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. The traffic shaping component reported that this resource has no currently configured traffic limits.
User Response:
  • Create the traffic shaping configuration for this resource.
SOAX0203I:{0}{1} Correct this resource's specification in the traffic shaping component.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. The traffic shaping component reported that this resource has an error in its configuration.
User Response:
  • Verify the traffic shaping configuration for this resource.
SOAX0204I:{0}{1} If performance is impacted, reconfigure admission control limits for this service and operation.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. The admission control component rejected a request because accepting the request would have violated the configured service and operation limits.
User Response:
  • Verify the admission control configuration for this resource.
  • If the configuration is correct, this message indicates normal operation for a rejected request.
  • If the configuration is not correct, adjust the service and operation admission limits as appropriate. See the admission control documentation for more information.
SOAX0205I:{0}{1} Additional detail provided for fault/alarm {2}: {3}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the fault or alarm code for which more information is being provided. {3} is the additional detail related to the fault or alarm. The service implementation is providing detail relevant to a recently generated fault or alarm.
User Response:
  • More information about the condition can be found by looking for the fault or alarm code provided.
SOAX0221I:{0}{1} Policy [{2}] not found.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the name of the policy. The service implementation could not find the named policy in the SOAP headers of the Web Service request. The ESB component adds policies to the SOAP headers before they are passed to the Service Platform component.
User Response:
  • Actions are dependent on the operator's implementation of the policy.
SOAX0222W:{0}{1} Invalid value [{2}] for policy [{3}].
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the value of the policy. {3} is the name of the policy. The value for the named policy is not valid.
User Response:
  • Correct the policy's value in the appropriate policy database table.
  • If the policy's value is correct in the policy database tables, then this is an internal processing error.
SOAX0223W:{0}{1} Attribute [{2}] not found.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the value of the attribute in the CONFIGPROPERTIES database table. The service implementation could not find the named attribute in the CONFIGPROPERTIES database table.
User Response:
  • Verify that you created the CONFIGPROPERTIES table. If not, run the appropriate DDL files.
  • If the CONFIGPROPERTIES table exists, try to open the configuration pages for the service implementation in the Administrative console and configure the attribute.
  • If the service implementation cannot be configured through the Administrative console, the table may be corrupted and you may need to recreate it using the appropriate DDL files.
SOAX0224W:{0}{1} Invalid value [{2}] for attribute [{3}].
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the value of the attribute. {3} is the name of the attribute. The value for the named attribute is not valid.
User Response:
  • Open the configuration pages for the service implementation in the Administrative console and configure the attribute.
SOAX0225I:{0}{1} Programming error. [{2}].
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is an internal processing message containing internal processing values. The service implementation detected an unexpected internal processing error.
User Response:
  • None: an internal processing error occurred.
SOAX0226I:{0}{1} Requester name null or zero-length.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. The service implementation received a request with a null or empty requester. Functionality relying upon a valid requester name, such as privacy, may be incorrect. This may be caused by a Web Service client that is not authenticating itself with the service platform.
User Response:
  • Ensure that the Web Service client is authenticating itself with the service platform
SOAX0227I:{0}{1} Unable to retrieve current server name.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. The service implementation could not determine the current Application server name. Faults and alarms may have a NullServerName in their source field.
User Response:
  • None: the condition is due to an internal error.
SOAX0228I:{0}{1} Unable to retrieve current host name.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. The service implementation could not determine the current host name. Faults and alarms may have a NullHostName in their source field.
User Response:
  • Ensure that the service platform has hostnames configured
SOAX0229I:{0}{1} Unable to retrieve current EAR name.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. The service implementation could not determine the current Enterprise Application Resource (EAR) name. Faults and alarms may have a NullEarName in their source field.
User Response:
  • None: the condition is due to an internal error.
SOAX0250E:{0}{1} Invalid structure or content in {2} request: {3}
SOAX0251W:{0}{1} Invalid structure or content in {2} request: {3}
SOAX0252I:{0}{1} Invalid structure or content in {2} request: {3}
SOAX0253E:{0}{1} Duplicate notification management entry: {2}
SOAX0254W:{0}{1} Duplicate notification management entry: {2}
SOAX0255I:{0}{1} Duplicate notification management entry: {2}
SOAX0256E:{0}{1} Service error occurred while processing the notification management request: {2}
SOAX0257W:{0}{1} Service error occurred while processing the notification management request: {2}
SOAX0258I:{0}{1} Service error occurred while processing the notification management request: {2}
SOAX0259E:{0}{1} Notification management entry not found: {2}
SOAX0260W:{0}{1} Notification management entry not found: {2}
SOAX0261I:{0}{1} Notification management entry not found: {2}
SOAX0270E:{0}{1} Invalid input value {2} for message part {3}.
SOAX0271I:{0}{1} An invalid message part was received: {2}
Invalid input value %1 for message part %2.
SOAX0273E:{0}{1} A service error occurred. Failure reason is {2}.
SOAX0274I:{0}{1} Unable to remove notification records: {2}
A service error occurred. Failure reason is %1.
SOAX0276E:{0}{1} Notification records not found.
SOAX0277I:{0}{1} Unable to find notification records: {2}
Notification records not found.
SOAX0500E:{0}{1} An unexpected exception occurred.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. An unexpected exception occurred in the service implementation that will halt processing of the Web Service request.
User Response:
  • Verify that the service implementation modules started without errors.
  • Verify that you have correctly configured the service implementation application.
  • If the service implementation has started without errors and has been correctly configured, it may be due to an internal error processing the data in the Web Service request.
SOAX0501W:{0}{1} An unexpected exception occurred. Processing will continue.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. An unexpected exception occurred in the service implementation, but processing of the Web Service request will continue if possible.
User Response:
  • Verify that the service implmentation modules started without errors.
  • Verify that you have correctly configured the service implementation application.
  • If the service implementation has started without errors and has been correctly configured, it may be due to an internal error processing the data in the Web Service request.
SOAX0502E:{0}{1} Unable to create a SIP application session.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. The service implementation could not create a SIP application session while processing a makeCall operation. It is likely that one of the service implementation SIP servlets did not start successfully.
User Response:
  • Verify that the service implementation modules started without errors.
  • Verify that you have correctly configured the service implementation application.
SOAX0503E:{0}{1} Unable to obtain a call identifier from the SIP application session.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. The service implementation created a SIP application session while processing a makeCall operation, but could not get a call identifier from the session. It is likely one of the service implementation SIP servlets did not start successfully.
User Response:
  • Verify that the service implementation modules started without errors.
  • Verify that you have correctly configured the service implementation application.
SOAX0551I:{0}{1} Check SIP servlet is started, check S-CSCF routing header is configured correctly.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. This message contains the suggested action to take when there is an error sending a SIP message. It is associated with messages SOAX0552, SOAX0553, and SOAX0554.
User Response:
  • Take the suggested action in this message.
SOAX0552E:{0}{1} Error sending SIP messages: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. One of the service implementation's SIP servlets received a 6XX error.
User Response:
  • Take the suggested action in message SOAX0551.
SOAX0553W:{0}{1} Error sending SIP messages: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. One of the service implementation's SIP servlets received a 6XX error.
User Response:
  • Take the suggested action in message SOAX0551.
SOAX0554I:{0}{1} Error sending SIP messages: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. One of the service implementation's SIP servlets received a 6XX error.
User Response:
  • Take the suggested action in message SOAX0551.
SOAX0555W:{0}{1} Policy or attribute configuration error: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} contains a policy or attribute and its current value. A policy or its corresponding attribute contains an invalid value for the expected type. For example, the value contains an alphanumeric value instead of an expected numeric value.
User Response:
  • Take the suggested action in message SOAX0556.
SOAX0556I:{0}{1} Verify that the policy or attribute is correctly configured.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. This message contains the suggested action to take when there is an error validating a policy or attribute value. It is associated with message SOAX0555.
User Response:
  • Take the suggested action in message SOAX0556.
SOAX0557W:{0}{1} Unable to add P-Asserted-Identity header to outbound request. Requester ID [ {2} ] could not be used to create a valid P-Asserted-Identity value.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the requester ID. A valid p-asserted-identity value could not be created from the requester ID that the ESB component passed in a SOAP header.
User Response:
  • None. Programming error.
SOAX1001I:{0}{1} Data source access error. Verify that the data source is running or tables exist.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message.
User Response:
  • Ensure the data source is up and running.
SOAX1003I:{0}{1} Duplicate Key Exception from Database, check input value.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message.
User Response:
  • Verify that the correlator is duplicate.
SOAX1005E:{0}{1} VerifyPrivacyPermits results false:{2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message.
User Response:
  • Verify if the privacy for this request is correct.
SOAX1015I:{0}{1} Notification delivery status: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} Notification delivery status.
User Response:
  • None.
SOAX1017E:{0}{1} Exception while {2}.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the operation name while the exception occurs.
User Response:
  • Review the log file and correct the cause for the exception.
SOAX1018W:{0}{1} Use default values for {2}.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the default value.
User Response:
  • None.
SOAX1020E:{0}{1} URI has IllegalArgument: {2}.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} URI argument.
User Response:
  • Check the URI for correct syntax.
SOAX1033W:{0}{1} Can not retrieve host name or requesterLocale. Check the requester configuration.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message.
User Response:
  • None.
SOAX2500E:{0}{1} Unsupported operation detected: [{2}].
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the name of an unsupported operation. The service implementation does not support the Web Service operation that was received. Release 1 only supports chargeAmount, refundAmount, chargeVolume, and refundVolume operation requests.
User Response:
  • Actions are Web Service client specific. If possible, disable the Web Service client's ability to send the unsupported operation requests.
SOAX2501I:{0}{1} WriteUsageRecordRequest = {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the contents of a WriteUsageRecordRequest. This message contains the contents of the WriteUsageRecordRequest that will be used to write a payment usage record to the USAGERECORD and USAGEPROPERTIES tables.
User Response:
  • None.
SOAX2502E:{0}{1} Events client reported fault while writing a change record: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is a general summary of the problem. A payment charge record could not be written to the CEI repository because of network or database problems. The CEI emitter will throw one of the following exceptions:
  • com.ibm.events.DataStoreConnectionFailureException
  • com.ibm.events.datastore.BadConnectionException
  • com.ibm.events.datastore.ConnectionTimeoutException
  • com.ibm.events.datastore.DataStoreNamingException
  • com.ibm.events.datastore.DataStoreIoException
  • com.ibm.events.datastore.DataStoreSqlException
  • javax.ejb.TransactionRolledbackLocalException
If possible, an alarm will be sent to an administrator. This may not be possible if the CEI server is completely down. Message SOAX2601 contains the suggested action that will be sent with the alarm.
User Response:
  • Verify that the CEI server is correctly configured and deployed.
  • Verify that the CEI database is full or is having connectivity problems.
SOAX2503W:{0}{1} Events client reported fault while writing a change record: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is a general summary of the problem. A payment charge record could not be written to the CEI repository due to problems that are not related to the network or database. If possible, an alarm will be sent to an administrator. This may not be possible if the CEI server is completely down. Message SOAX2601 contains the suggested action that will be sent with the alarm.
User Response:
  • Verify that the CEI server is correctly configured and deployed.
  • Verify that the service implementation modules started without errors.
  • Verify that you have correctly configured the service implementation application.
  • If you have correctly configured and deployed the CEI server and service implementation, then there may be an internal processing error in the service implementation.
SOAX2504E:{0}{1} An unexpected exception occurred.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. An unexpected exception occurred in the service implementation that will halt processing of the Web Service request.
User Response:
  • Verify that the service implementation modules started without errors.
  • Verify that you have correctly configured the service implementation application.
  • If the service implementation has started without errors and you have correctly configured it, it may be due to an internal error processing the data in the Web Service request.
SOAX2505W:{0}{1} An unexpected exception occurred. Processing will continue.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. An unexpected exception occurred in the service implementation, but processing of the Web Service request will continue if possible.
User Response:
  • Verify that the service implmentation modules started without errors.
  • Verify that you have correctly configured the service implementation application.
  • If the service implementation has started without errors and you have correctly configured it, it may be due to an internal error processing the data in the Web Service request.
SOAX2506E:{0}{1} Payment records were not created due to policy or configuration settings.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. A payment charge record cannot be written to either the USAGERECORDS and USAGEPROPERTIES tables or to the CEI repository because of current configuration settings.
User Response:
  • Configure one of the following policies to enable writing of a payment charge record: service.config.Payment_PostPaid_IMS.PaymentUsageRecordEnabled, service.config.Payment_PostPaid_IMS.CEIEnabled
  • Or configure one of the following payment properties in the Administrative console to enable writing of a payment charge record: PaymentUsageRecordEnabledDefault, CEIEnabledDefault.
SOAX2507E:{0}{1} Unable to create a CEI event because the Common Events Infrastructure service is not started.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. A payment charge record cannot be written to the CEI repository because the Common Event Infrastructure service is not started.
User Response:
  • Either set the service.config.Payment_PostPaid_IMS.CEIEnabled policy or the Administrative console payment CEIEnabled property to false.
  • Or start the Common Event Infrastructure service.
SOAX2601I:{0}{1} Access to the Common Events Infrastructure datastore is not available. Operator intervention may be required. Verify that the datastore is available.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. This is the suggested action when a payment charge record cannot be written to the CEI repository. It is associated with message SOAX2502.
User Response:
  • Take the action that is suggested in this message.
SOAX2602I:{0}{1} Start the Common Events Infrastructure (CEI) service or disable writing payment records to the CEI repository.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. This is the suggested action when a payment charge record cannot be written to the CEI repository. It is associated with message SOAX2507.
User Response:
  • Take the action that is suggested in this message.
SOAX3500I:{0}{1} Unable to parse presence document {2} with Content-Type {3}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the presence document the implementation could not parse {3} is the Content-Type reported for the presence document The service implementation could not parse the given presence document. This can occur because the document is empty, malformed, or otherwise incomprehensible to the implementation.
User Response:
  • Verify that the presence server is returning information in a format known to the service implementation
SOAX3501W:{0}{1} Error contacting the presence server: {2}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the SIP error message returned from attempting to contact the presence server The service implementation could not contact the configured presence server because no endpoint was configured, because of a request timeout, or because of a general SIP error that prevented communication.
User Response:
  • Verify that the presence server is answering incoming SIP requests.
  • Verify that no firewalls are blocking traffic between the service implementation and the presence server.
SOAX3502W:{0}{1} Error "{2}" substituting variables into message "{3}": [{4}{5}{6}{7}{8}{9}{10}{11}{12}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the Java error message received while trying to perform text substitution The service implementation could not substitute message variables into a Parlay X-style message string. This could be because the format string is invalid, there are insufficient or too many variables, or the variables could not be processed.
User Response:
  • If the message format string and variables are from an external system, verify that the external system is providing valid Parlay X-style messages/variables per 3GPP TS 29.199 v6.3.0 Part 1 Section 10.1.
SOAX3503I:{0}{1} The PresenceSupplier publish operation is not implemented in this release.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. A client attempted to invoke the Parlay X PresenceSubscriber publish operation, which is not implemented in this release.
User Response:
  • Verify that the client can recover from the resulting ServiceException.
SOAX3504I:{0}{1} The PresenceSupplier getOpenSubscriptions operation is not implemented in this release.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. A client attempted to invoke the Parlay X PresenceSubscriber getOpenSubscriptions operation, which is not implemented in this release.
User Response:
  • Verify that the client can recover from the resulting ServiceException.
SOAX3505I:{0}{1} The PresenceSupplier updateSubscriptionAuthorization operation is not implemented in this release.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. A client attempted to invoke the Parlay X PresenceSubscriber updateSubscriptionAuthorization operation, which is not implemented in this release.
User Response:
  • Verify that the client can recover from the resulting ServiceException.
SOAX3506I:{0}{1} The PresenceSupplier getMyWatchers operation is not implemented in this release.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. A client attempted to invoke the Parlay X PresenceSubscriber getMyWatchers operation, which is not implemented in this release.
User Response:
  • Verify that the client can recover from the resulting ServiceException.
SOAX3507I:{0}{1} The PresenceSupplier getSubscribedAttributes operation is not implemented in this release.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. A client attempted to invoke the Parlay X PresenceSubscriber getSubscribedAttributes operation, which is not implemented in this release.
User Response:
  • Verify that the client can recover from the resulting ServiceException.
SOAX3508I:{0}{1} The PresenceSupplier blockSubscription operation is not implemented in this release.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. A client attempted to invoke the Parlay X PresenceSubscriber blockSubscription operation, which is not implemented in this release.
User Response:
  • Verify that the client can recover from the resulting ServiceException.
SOAX3509I:{0}{1} Unable to retrieve presence information for presentity {2}. Service received SIP response {3} to an outbound SUBSCRIBE request with Call-ID {4}.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the presentity whose presence could not be retrieved. {3} is the SIP response code received for the outbound SUBSCRIBE request. {4} is the Call-ID used in the outbound SUBSCRIBE request. The service implementation could not retrieve presence information for the given presentity. The implementation received the SIP response code for an outbound SUBSCRIBE request on the given Call-ID.
User Response:
  • If the response code is a 3xx redirect response, verify that the presence server URI is correctly configured and does not point to a SIP redirect server. The service implementation will not follow 3xx redirect responses.
  • If the response code is a 408 Request Timeout, verify that the configured presence server URI is correct and that the presence server is executing.
  • Resolve other response codes based upon their meanings in RFCs 3265 and 3261. The Call-ID may be useful for locating specific messages within both the product and the presence server logs.
SOAX3510I:{0}{1} Unable to retrieve presence information for presentity {2} within {3} millisecond(s).
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the presentity whose presence could not be retrieved. {3} is the SIP fetch timeout in milliseconds used to retrieve the information. The service implementation could not retrieve presence information for the given presentity within the given timeout period.
User Response:
  • Ensure that the presence server is able to respond to an incoming SUBSCRIBE request and generate an outbound NOTIFY within the given timeout.
  • Ensure that the network between the service and the presence server allows for three SIP messages (example: SUBSCRIBE/200 then NOTIFY) within the given time period.
  • Ensure that the presence server and the network can meet the above two conditions while under load. If necessary, adjust the traffic shaping settings for the presence server to enforce a maximum load.
SOAX3511I:{0}{1} Unable to retrieve presence information for target {2}. The URI scheme was not present within the AdditionalGroupURISchemes setting, and the service was unable to parse target as a SIP, SIPS, or TEL URI: {3}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the target whose presence could not be retrieved. {3} is exception message received when attempting to parse the given target. The service implementation could not retrieve presence information for the given target because the target could not be converted into a SIP, SIPS, or TEL URI. The URI scheme was not present within the AdditionalGroupURISchemes setting.
User Response:
  • Ensure that the target follows from the supplied request address. This may require verifying group URI mappings within the group list resolution service in use.
  • Ensure that the AdditionalGroupURISchemes setting is correct, and that it contains the groupScheme setting in use at the Group List Manager.
  • Ensure that the target is a valid SIP, SIPS, or TEL URI.
SOAX3512I:{0}{1} Requested notification duration, {2} milliseconds, is longer than maximum allowable duration, {3} milliseconds.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the requested notification duration in milliseconds. {3} is the maximum allowable notification duration in milliseconds. The client's request was rejected because it specified too long a notification duration.
User Response:
  • Ensure that the service's MaximumNotificationDuration setting is appropriate. Increase the setting if desired.
  • Ensure that incoming policy headers that modify the MaximumNotificationDuration are appropriate. Increase the policy value if desired.
  • Have the Parlay X client request a shorter duration.
SOAX3517I:{0}{1} Unable to augment existing subscription for presentity {2} with endpoint {3} and correlator "{4}". The newly requested correlator "{5}" differs from the previous correlator.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the presentity to which the subscription applies. {3} is the PresenceNotification endpoint the client specified when originally creating the subscription. {4} is the correlator the client specified when originally creating the subscription. {5} is the correlator the client specified in the rejected request. The client's subscribePresence request was rejected because it the client already has a valid subscription for the given presentity with a different correlator. Clients must reuse any previously specified correlator and endpoint when issuing a second subscribePresence request for a given presentity.
User Response:
  • Ensure that the client re-uses any previously specified correlator and endpoint. Once you make the appropriate changes to the correlator and endpoint, the client should retry the request, otherwise the subscription permissions may be in a consistent state.
  • If you cannot use the previous correlator, use a new session when making this request. Using a new session avoids this request colliding with any state from earlier requests.
SOAX3518I:{0}{1} Unable to augment existing subscription for presentity {2} with endpoint {3} and correlator "{4}". The newly requested endpoint {5} differs from the previous endpoint.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the presentity to which the subscription applies. {3} is the PresenceNotification endpoint the client specified when originally creating the subscription. {4} is the correlator the client specified when originally creating the subscription. {5} is the correlator the client specified in the rejected request. The client's subscribePresence request was rejected because it the client already has a valid subscription for the given presentity with a different endpoint. Clients must re-use any previously specified correlator and endpoint when issuing a second subscribePresence request for a given presentity.
User Response:
  • Ensure that the client reuses any previously specified correlator and endpoint. Once the appropriate changes are made to the correlator and endpoint, the client should retry the same request. Otherwise the subscription permissions may be in an consistent state.
  • If the previous correlator cannot be reused, use a new session when making this request. Using a new session avoids this request colliding with any state from earlier requests.
SOAX3519I:{0}{1} Unable to retrieve presence information for presentity {2}. Service generated SIP response {3} to an inbound NOTIFY request with Call-ID {4}.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the presentity whose presence could not be retrieved. {3} is the SIP response sent for the inbound NOTIFY request. {4} is the Call-ID of the inbound NOTIFY request. The service implementation could not retrieve presence information for the given presentity. The service implementation received a malformed or otherwise invalid NOTIFY request on the given Call-ID. The service sent a SIP response with the given error code to the presence server because of the inbound NOTIFY.
User Response:
  • If the response has a status of 400, verify that the incoming NOTIFY is well-formed according to RFC 3265. Among other things, a well-formed NOTIFY request contains both an Event and a Subscription-State header.
  • If the response has a status of 415, verify that the incoming NOTIFY has a Content-Type compatible with the Accept headers in the outbound SUBSCRIBE.
  • If the response has a status of 489, verify that the incoming NOTIFY has an Event header containing the same SIP event package as the one specified in the corresponding outbound SUBSCRIBE.
  • Resolve other response codes based upon their meanings in RFCs 3265 and 3261. The Call-ID may be useful for locating specific messages within both the product and the presence server logs.
SOAX3520I:{0}{1} Unable to retrieve presence information for presentity {2}. Service received an unrecoverable Subscription-State of {3} in an inbound NOTIFY request with Call-ID {4}.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the presentity whose presence could not be retrieved. {3} is the Subscription-State header from the inbound NOTIFY request. {4} is the Call-ID of the inbound NOTIFY request. The service implementation could not either retrieve or re-subscribe to presence information for the given presentity. The service implementation received a Subscription-State header on an inbound NOTIFY request indicating that further subscription attempts were disallowed according to the semantics of RFC 3265.
User Response:
  • If the Subscription-State header has a 'reason=rejected' parameter, the subscription has been terminated due to a change in authorization policy. The service implementation's behavior follows from RFC 3265 section 3.2.4. If the behavior is unacceptable, determine why the presence server reported a change in authorization policy.
  • If the Subscription-State header has a 'reason=noresource' parameter, the subscription has been terminated because the presentity which was being monitored no longer exists. The service implementation's behavior follows from RFC 3265 section 3.2.4. If the behavior is unacceptable, determine why the presence server reported that the presentity ceased to exist.
  • Resolve other reason parameters based upon their meanings in RFC 3265 The Call-ID may be useful for locating specific messages within both the product and the presence server logs.
SOAX3521I:{0}{1} Unable to retrieve presence information for presentity {2}. Service cannot process a presentity with a TEL URI when the PresenceServerSIPURI setting is empty.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the presentity whose presence could not be retrieved. The service implementation cannot retrieve information for the given presentity because it has a TEL URI. When the PresenceServerSIPURI setting is empty, the service implementation relies on the presentity URI to direct an outbound SUBSCRIBE request to the appropriate destination. The SIP Container cannot determine where to send a TEL URI without additional routing information in the form of a non-empty PresenceServerSIPURI.
User Response:
  • Ensure that the given presentity should be a TEL URI.
  • Configure a SIP- or SIPS-based PresenceServerSIPURI that understands how to either respond to or direct TEL URIs.
SOAX3522E:{0}{1} The configured PresenceServerSIPURI {2} is not a valid SIP or SIPS URI: {3}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the configured PresenceServerSIPURI. {3} is the exception thrown while attempting to parse the URI. At runtime, the service cannot parse the supplied PresenceServerSIPURI into a valid SIP or SIPS URI. It cannot service any requests associated with this setting.
User Response:
  • Modify the PresenceServerSIPURI setting to contain a valid, well-formed SIP or SIPS URI.
SOAX3531I:{0}{1} Unable to retrieve members for group URI {2}. Incoming SOAP headers lacked relevant twssHeaders/resolvedGroups/groupList content.
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the service implementation that issued the message. {2} is the incoming group URI from the Parlay X Web Service request. The service could not obtain information about the given group URI from the SOAP headers associated with the Parlay X request. The service expects that the SOAP headers contain an entry every incoming group URI, and without the header information the service cannot process the request.
User Response:
  • Ensure that the group URI is as intended.
  • Ensure that the group URI is defined with the Group List Manager.
  • Ensure that the ESB is installed and processing incoming requests using a flow containing the Group Resolution Mediation primitive.
  • Ensure that the Group Resolution Mediation primitive is successfully contacting the Group List Manager



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.