WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Messages_en_US

This pseudo class documents the set of messages that can be issued by the IBM Telecom Web Services Server components.

TAS5001E: An unexpected error occurred.
Explanation:
An unexpected error occurred. The exception is printed and a stack trace is generated.
User Response:
Use the exception to determine the type of error, and the stack trace to determine where the error occurred.
TAS5002E: Attempt to sign Service Agreement for {0} was not successful.
Explanation:
{0} is the name of the requested service manager. The ParlayConnector was not successful signing the service agreement for the requested service manager.
User Response:
  • Verify that the service agreement is correctly configured. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation
TAS5003E: Requested service {0} was not found.
Explanation:
{0} is the name of the requested service manager. The requested service was not found in the list of subscribed services for the caller's domain on the Gateway.
User Response:
  • Verify that you are using the appropriate service manager factory to obtain the requested service manager.
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation
TAS5004E: Not able to get IpAccess from ParlayConnector.
Explanation:
The ParlayConnector was unsuccessful getting access to the Gateway. See the preceding messages for more information about the failure.
User Response:
  • Examine the preceding messages for more details about the failure. Correct the problems described in those messages.
  • Retry the operation
TAS5005E: The specified encryption method {0} requires an encryption key.
Explanation:
{0} is the name of the encryption method. The encryption method is specified in the configuration, but no encryption key is specified for it.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5006W: The specified encryption method {0} is not supported in this method.
Explanation:
{0} is the name of the encryption method. The encryption method is specified in the configuration, but is not supported in the current release.
User Response:
Correct the configuration. For information about supported encryption methods, see the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5007W: Property {0} does not have the form serviceType,propertyName,valueList .
Explanation:
{0} is a configuration property. The name specifies a service property but the value does not have the required format.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5008E: A Gateway Exception was thrown during IpAccess.obtainInterface({0}).
Explanation:
{0} is the name of the Parlay interface which could not be obtained. An unexpected error occurred at the Gateway. The ParlayConnector will retry the operation.
User Response:
None.
TAS5009E: A Gateway Exception was thrown during retry IpAccess.obtainInterface({0}).
Explanation:
{0} is the name of the Parlay interface which could not be obtained. An unexpected error occurred at the Gateway.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation.
TAS5010I: Retrying IpAccess.obtainInterface().
Explanation:
The ParlayConnector is retrying the operation that was in progress when an unexpected error occurred at the Gateway.
User Response:
None.
TAS5011E: A Gateway Exception was thrown during IpServiceDiscovery.listSubscribedServices().
Explanation:
An unexpected error occurred at the Gateway. The ParlayConnector will retry the operation.
User Response:
None.
TAS5012E: A Gateway Exception was thrown during retry IpServiceDiscovery.listSubscribedServices().
Explanation:
An unexpected error occurred at the Gateway.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure.
  • Correct any existing problems.
  • Retry the operation.
TAS5013I: Retrying IpServiceDiscovery.listSubscribedServices().
Explanation:
The ParlayConnector is retrying the operation that was in progress when an unexpected error occurred at the Gateway.
User Response:
None.
TAS5014E: A Gateway Exception was thrown during IpServiceAgreementManagement.selectService().
Explanation:
An unexpected error occurred at the Gateway. The ParlayConnector will retry the operation.
User Response:
None.
TAS5015E: A Gateway Exception was thrown during retry IpServiceAgreementManagement.selectService().
Explanation:
An unexpected error occurred at the Gateway.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation.
TAS5016I: Retrying IpServiceAgreementManagement.selectService().
Explanation:
The ParlayConnector is retrying the operation that was in progress when an unexpected error occurred at the Gateway.
User Response:
None.
TAS5017E: A Gateway Exception was thrown during IpServiceDiscovery.listServiceTypes().
Explanation:
An unexpected error occurred at the Gateway. The ParlayConnector will retry the operation.
User Response:
None.
TAS5018E: A Gateway Exception was thrown during retry IpServiceDiscovery.listServiceTypes().
Explanation:
An unexpected error occurred at the Gateway.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation.
TAS5019I: Retrying IpServiceDiscovery.listServiceTypes().
Explanation:
The ParlayConnector is retrying the operation that was in progress when an unexpected error occurred at the Gateway.
User Response:
None.
TAS5020E: A Gateway Exception was thrown during IpServiceAgreementManagement.signServiceAgreement().
Explanation:
An unexpected error occurred at the Gateway. The ParlayConnector will retry the operation.
User Response:
None.
TAS5021E: A Gateway Exception was thrown during retry IpServiceAgreementManagement.signServiceAgreement().
Explanation:
An unexpected error occurred at the Gateway.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation.
TAS5022I: Retrying IpServiceAgreementManagement.signServiceAgreement().
Explanation:
The ParlayConnector is retrying the operation that was in progress when an unexpected error occurred at the Gateway.
User Response:
None.
TAS5023W: Not able to get Gateway IpServiceDiscovery object.
Explanation:
The Gateway returned a NULL Service Discovery object reference.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation
TAS5024W: No services are available from the Gateway.
Explanation:
The Gateway returned an empty Subscribed Services list.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation
TAS5025W: The requested service {0} was not found in the list of services available on the Gateway.
Explanation:
{0} is the type of service manager requested. The specified service was not found in the Subscribed Services list returned by the Gateway.
User Response:
  • Verify that you are using the appropriate service manager factory to obtain the requested service manager.
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation
TAS5026W: The requested service {0} was found in list of services available on the Gateway, but the corresponding service token is null.
Explanation:
{0} is the type of service manager requested. The specified service was found in the Subscribed Services list returned by the Gateway, but the service token returned by the Gateway is NULL.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation
TAS5027W: The number of service types is greater than {0}; only the first {1} will be listed.
Explanation:
{1} is the maximum number of service types that can be listed. {2} is the actual number of service types that will be listed. The Subscribed Services list returned by the Gateway contains more entries than expected. Not all service types in the Gateway Subscribed Services list will be reported.
User Response:
None.
TAS5028W: Not able to get Gateway signatureAndServiceManager object.
Explanation:
The ParlayConnector was not successful in signing the Service Agreement for the requested service. See the preceding messages for more information about the failure.
User Response:
  • Examine the preceding messages for more details about the failure. Correct the problems described in those messages.
  • Retry the operation
TAS5029W: Property {0} was not found in the configuration.
Explanation:
{0} is a configuration property. The named property is not defined in the configuration. If a default value is defined for the property, the default value will be used.
User Response:
If you intended to configure the named property, correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5030W: Property {0}, defined in the configuration, has an unrecognized value.
Explanation:
{0} is a configuration property. The named property is defined in the configuration, but the value assigned to it is not correct. If a default value is defined for the property, the default value will be used.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5031W: No service agreement text was found in the configuration.
Explanation:
The ParlayConnector configuration specifies that service agreements are defined by service type, but no service agreements are configured.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5032W: Property {0}, defined in the configuration, will not be used for service discovery.
Explanation:
{0} is a configuration property. The named property is defined in the configuration, but the value assigned to it is not correct. The ParlayConnector will ignore this property.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5033E: Property {0}, defined in the configuration, is incorrect. It must be greater than zero, but not greater than one.
Explanation:
{0} is a configuration property. The named property is defined in the configuration, but the value assigned to it is not correct. This value should be greater than 0.0, but not greater than 1.0.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5034E: A P_SERVICE_ACCESS_DENIED exception on selectService() for service type {0} may indicate that there are service agreements that are not terminated. If the problem persists, contact your Gateway provider.
Explanation:
{0} identifies a service type registered on the Parlay Gateway. A P_SERVICE_ACCESS_DENIED exception was thrown by the Parlay Gateway IpServiceAgreementManagement.selectService() for the specified service type. The most likely reasons are:
  • The client domain is not subscribed to the requested service.
  • A service agreement has already been signed for the requested service, but ParlayConnector is unable to terminate this agreement.
User Response:
  • Verify that the client domain is configured correctly. If it is not, correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
  • Verify that the client domain that is configured is subscribed to the requested service. If it is not, contact your Gateway provider or redesign your application to use a different service type.
  • If the problem persists, contact your Gateway provider. If there is a signed, unterminated service agreement for this service type, request that the service agreement be terminated.
TAS5035E: SERVICE{0}_IDENTIFIER {1} is configured, but SERVICE{2}_MAPPEDCLASS is not configured.
Explanation:
{0} identifies a Gateway extension service is configured in the environment. {2} is the Gateway identifier string configured for the Gateway extension service. {3} identifies the mapped class which must be configured for the Gateway extension service. The specified Gateway extension service is configured with a Gateway identifier string, but the required corresponding mapped class is not configured.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5036E: Extension Service {0} will not be enabled.
Explanation:
{0} is the Gateway identifier string configured for a Gateway extension service. The specified Gateway extension service, as currently configured, cannot be supported. See the preceding messages for more information about the problem.
User Response:
  • Examine the preceding messages for more information about the problem.
  • Correct the problems described in those messages.
  • Restart the Application.
  • Retry the operation
TAS5037E: SERVICE{0}_MAPPEDCLASS is configured as {1}, but a classname cannot end with the path delimiter character.
Explanation:
{1} identifies a Gateway extension service mapped class configured in the environment. {2} is the class name configured for the Gateway extension service mapped class. The specified Gateway extension service mapped class is not a properly formed class name because it ends with the path delimiter character.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5038E: SERVICE{0}_MAPPEDCLASS is configured as {1}; not able to load required associated class {2}.
Explanation:
{1} identifies a Gateway extension service mapped class configured in the environment. {2} is the class name configured for the Gateway extension service mapped class. {3} identifies a class which was not found. The specified associated class must exist for the specified mapped class to be a properly formed mapped class.
User Response:
Correct the configuration or the mapped class name. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5039E: Not able to map the SERVICE{0}_IDENTIFIER {1} service manager to the SERVICE{2}_MAPPEDCLASS {3}.
Explanation:
{1} identifies a Gateway extension service configured in the environment. {2} is the Gateway identifier string configured for the Gateway extension service. {3} identifies the mapped class configured for the Gateway extension service. {4} is the class name configured for the Gateway extension service mapped class. The specified Gateway extension service cannot be mapped to the mapped class configured for it. See the preceding messages for more information about the problem.
User Response:
  • Examine the preceding messages for more details about the problem. Correct the problems described in those messages.
  • Retry the operation
TAS5040W: Property {0} has the form serviceType,propertyName,and valueList, but valueList is null.
Explanation:
{0} is a configuration property. The named property specifies a service property in the correct format, but all entries in the valueList are NULL.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5041E: Not able to map the requested service manager {0}.
Explanation:
{0} is the type of service manager requested. The ParlayConnector was able to get the specified service manager from the Gateway, but was unable to create the associated mapped class object. See the preceding messages for more information about the problem.
User Response:
  • Examine the preceding messages for more details about the problem. Correct the problems described in those messages.
  • Retry the operation
TAS5042E: SERVICE{0}_MAPPEDCLASS ({1}) is not a properly formed class name.
Explanation:
{1} identifies a Gateway extension service mapped class configured in the environment. {2} is the class name configured for the Gateway extension service mapped class. The specified Gateway extension service mapped class is not a properly formed class name.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5043E: Class {0} for SERVICE{1}_MAPPEDCLASS {2} does not contain the required narrow() method.
Explanation:
{1} identifies a required class associated with the specified mapped class. {2} identifies the mapped class configured for the Gateway extension service. {3} is the class name configured for the Gateway extension service mapped class. The specified required class was found, but it is not properly formed because it does not contain a narrow() method.
User Response:
  • Correct the required class definition.
  • Rebuild the Application.
  • Restart the Application.
  • Retry the operation.
TAS5044E: SERVICE{0}_MAPPEDCLASS is configured as {1}. Not able to load required associated interface {2}.
Explanation:
{1} identifies a Gateway extension service mapped class configured in the environment. {2} is the class name configured for the Gateway extension service mapped class. {3} identifies the interface that was not found. The specified associated interface must exist for the specified mapped class to be a properly formed mapped class.
User Response:
Correct the configuration or the mapped class. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5045E: Class {0} for SERVICE{1}_MAPPEDCLASS {2} does not contain the required {3}({4}) method.
Explanation:
{1} identifies a required class associated with the specified mapped class. {2} identifies the mapped class configured for the Gateway extension service. {3} is the class name configured for the Gateway extension service mapped class. {4} is the name of the method that was not found in class {1}. {5} is the class of the single parameter required for method {4}. The specified required class was found, but it is not properly formed because it does not contain a method with the specified signature.
User Response:
  • Correct the required class definition.
  • Rebuild the Application.
  • Restart the Application.
  • Retry the operation.
TAS5046E: A PLATFORM_EXCEPTION on terminateServiceAgreement() service type {0} might cause an unterminated service agreement.
Explanation:
{0} identifies a service type registered on the Parlay Gateway. A PLATFORM_EXCEPTION was thrown when attempting to call IpServiceAgreementManagement.terminateServiceAgreement() for the specified service type. The most likely reasons are:
  • A null parameter was passed to IpServiceAgreementManagement.terminateServiceAgreement().
  • A hardware communication failure.
User Response:
Check the console for more specific information about the problem. If there was a communication failure, fix the problem.
  • Stop the IBM Telecom Web Services Server.
  • Restart the IBM Telecom Web Services Server. The ParlayConnector will retry the IpServiceAgreementManagement.terminateServiceAgreement() operation.
TAS5047W: Property {0} does not have the form serviceType,agreementText .
Explanation:
{0} is a configuration property. The named property specifies agreement text for a service agreement, but the value does not have the required format.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5048W: Not able to get Gateway IpServiceAgreementManagement object.
Explanation:
The ParlayConnector was not able to obtain the IpServiceAgreementManagement interface from the ParlayGateway.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure.
  • Correct any existing problems.
  • Retry the operation.
TAS5049I: Service manager for {0} is preloaded.
Explanation:
{0} is a service type supported by the Gateway. The ParlayConnector has obtained the specified service manager using the configured service agreement and has cached the service manager reference.
User Response:
None.
TAS5050I: The current state of {0} is {1}.
Explanation:
{1} identifies an application server. {2} is a component state. The specified component is reporting its current state.
User Response:
None.
TAS5051E: No IpService was specified to isWireless().
Explanation:
The parameter specified to the isWireless() method is not a service manager object.
User Response:
  • Correct the application to specify a service manager object to the isWireless() method.
  • Rebuild the Application.
  • Restart the Application.
  • Retry the operation.
TAS5052E: A Gateway Exception was thrown during IpAccess.obtainInterfaceWithCallback({0}).
Explanation:
{0} is the interface that the ParlayConnector was requesting from the Gateway. An unexpected error occurred at the Gateway. The ParlayConnector will retry the operation.
User Response:
None.
TAS5053E: A Gateway Exception was thrown during retry IpAccess.obtainInterfaceWithCallback({0}).
Explanation:
{0} is the interface that the ParlayConnector was requesting from the Gateway. An unexpected error occurred at the Gateway.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure.
  • Correct any existing problems.
  • Retry the operation.
TAS5054I: Retrying IpAccess.obtainInterfaceWithCallback().
Explanation:
The ParlayConnector is retrying the operation that was in progress when an unexpected error occurred at the Gateway.
User Response:
None.
TAS5055E: A Gateway Exception was thrown during IpServiceDiscovery.describeServiceType().
Explanation:
An unexpected error occurred at the Gateway. The ParlayConnector will retry the operation.
User Response:
None.
TAS5056E: A Gateway Exception was thrown during retry IpServiceDiscovery.describeServiceType().
Explanation:
An unexpected error occurred at the Gateway.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure.
  • Correct any existing problems.
  • Retry the operation.
TAS5057I: Retrying IpServiceDiscovery.describeServiceType().
Explanation:
The ParlayConnector is retrying the operation that was in progress when an unexpected error occurred at the Gateway.
User Response:
None.
TAS5058I: The ParlayConnector is using the default value {0} for Property {1}.
Explanation:
{1} is the default value for the named property. {2} is the name of the property. The ParlayConnector is using the default value for the named property.
User Response:
If the default value is correct for the application, no action is necessary. If the default value needs to be overridden, correct the configuration. For information about supported encryption methods, see the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5059W: Property {0}, defined in the configuration, has an incorrectly formed value.
Explanation:
{0} is a property. The named property is defined in the configuration, but the value assigned to it is not correct. If a default value is defined for the property, the default value will be used.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5060E: A Gateway Exception was thrown during IpServiceAgreementManagement.initiateSignServiceAgreement().
Explanation:
An unexpected error occurred at the Gateway. The ParlayConnector will retry the operation.
User Response:
None.
TAS5061E: A Gateway Exception was thrown during retry IpServiceAgreementManagement.initiateSignServiceAgreement().
Explanation:
An unexpected error occurred at the Gateway.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure.
  • Correct any existing problems.
  • Retry the operation.
TAS5062I: Retrying IpServiceAgreementManagement.initiateSignServiceAgreement().
Explanation:
The ParlayConnector is retrying the operation that was in progress when an unexpected error occurred at the Gateway.
User Response:
None.
TAS5063E: Attempt to initiate sign Service Agreement for {0} was not successful.
Explanation:
{0} is the service manager the ParlayConnector was preparing to request from the Gateway. An unexpected error occurred at the Gateway.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure.
  • Correct any existing problems.
  • Retry the operation.
TAS5064E: Not able to sign Service Agreement for {0} because the required property {1} was not found in the configuration.
Explanation:
{1} is the service manager the ParlayConnector was preparing to request from the Gateway. {2} is the name of a required environment property. The ParlayConnector is not able to sign a service agreement to obtain the named service manager from the Gateway. An unexpected error occurred at the Gateway.
User Response:
Correct the configuration. For information about supported encryption methods, see the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5065E: An unexpected error occurred in describeService({0}).
Explanation:
{0} is the name of the Gateway service specified to describeService(). An unexpected error occurred.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure.
  • Correct any existing problems.
  • Retry the operation.
TAS5066W: No properties were found during describeService({0}).
Explanation:
{0} is the name of the Gateway service specified to describeService(). No properties were found for the named service, either on the Parlay Gateway, or in the ParlayConnector's environment configuration.
User Response:
  • Verify the service name that was specified to describeService().
  • If necessary, correct the configuration. For information about supported encryption methods, see the configuration information in the IBM WebSphere Telecom Web Services Server information center.
  • Check the console to determine if there was a communication, Gateway, or other failure.
  • Correct any existing problems.
  • Retry the operation.
TAS5067W: Not able to verify the digital signature of the Parlay Gateway given with the {0} service manager. The service manager is accepted.
Explanation:
{0} is the name of the Gateway service the ParlayConnector has requested from the Parlay Gateway. The ParlayConnector has received the named service manager. However, the ParlayConnector is unable to verify the sender of this object because the ParlayConnector is not configured to verify the digital signature. The service manager is accepted by the ParlayConnector.
User Response:
If the communication link to the Gateway is secure, no action is necessary. If the communication link to the Gateway may be vulnerable,
  • Do not use the service manager object.
  • Configure the ParlayConnector so that the source of the service manager object can be verified. For information about configuring the ParlayConnector, see the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5068W: Property {0}, defined in the configuration has a value that is not recognized {1}. It is not being used.
Explanation:
{1} is a property. {2} is the incorrect value assigned to the specified property. The named property is defined in the configuration, but the value assigned to it is not correct.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5069E: The Parlay Gateway gave a digital signature that is not correct with the {0} service manager. The service manager is discarded.
Explanation:
{0} is the name of the Gateway service the ParlayConnector has requested from the Parlay Gateway. The ParlayConnector has received the named service manager. However, the ParlayConnector cannot verify that the service manager was received from the Parlay Gateway because the digital signature received with it is not correct. The ParlayConnector will not return the service manager to the application or use the service manager in any way.
User Response:
  • Verify that the ParlayConnector is correctly configured to verify the digital signature received from the Gateway. For information about configuring the ParlayConnector, see the configuration information in the IBM WebSphere Telecom Web Services Server information center.
  • Check the console to determine if there was a communication, Gateway, or other failure.
  • Correct any existing problems.
  • Retry the operation.
TAS5070W: Property {0}, defined in the configuration, will not be used for signing service agreements.
Explanation:
{0} is a configuration property. The named property is defined in the configuration, but the value assigned to it is not correct. The ParlayConnector will ignore this property.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5071W: Property {0}, defined in the configuration, has the form serviceType,agreementText, but serviceType is null, or agreementText is null.
Explanation:
{0} is a configuration property. The named property specifies agreement text for a service agreement in the correct format, but the agreement text is NULL.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5072W: Property {0}, defined in the configuration, does not have the form serviceType,terminationText.
Explanation:
{0} is a configuration property. The named property specifies termination text for a service agreement, but the value does not have the required format.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5073W: Property {0}, defined in the configuration, has the form serviceType,terminationText, but serviceType is null or terminationText is null.
Explanation:
{0} is a configuration property. The named property specifies termination text for a service agreement in the correct format, but the termination text is NULL.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5074W: Property {0}, defined in the configuration, will not be used for terminating service agreements.
Explanation:
{0} is a configuration property. The named property is defined in the configuration, but the value assigned to it is not correct. The ParlayConnector will ignore this variable.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5075E: An Exception occurred requesting cache status update on target node: {0}.
Explanation:
{0} identifies a node in the WebSphere cluster. The ParlayConnector was not able to synchronize the cache on the named node.
User Response:
  • Check the console for the specific nature of the problem. Correct any existing problems.
  • Stop the application server.
  • Restart the application server.
TAS5076E: Not able to update cache status on target node: {0}.
Explanation:
{0} identifies a node in the WebSphere cluster. The ParlayConnector was not able to synchronize the cache on the named node.
User Response:
  • Check the console for more specific information about the problem. Correct any existing problems.
  • Stop the application server.
  • Restart the application server.
TAS5077E: An Exception occurred getting a {0} service instance using the configured JNDI name {1}.
Explanation:
{1} is the service type name defined for a Parlay service implemented locally. {2} is JNDI name specified as the implementation of service type name. The active configuration includes the definition for the specified Parlay service implemented locally. An exception occurred getting an instance of the implementation using the specified JNDI name.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5078E: The {0} service instance obtained using configured JNDI name {1} does not implement the required interface {2}.
Explanation:
{1} is the service type name defined for a Parlay service implemented locally. {2} is JNDI name specified as the implementation of service type name. {3} is an interface that must be implemented by all local implementations of Parlay services defined in the active configuration. The active configuration includes the definition for the specified Parlay service implemented locally. The object obtained using the specified JNDI name does not implement the specified interface.
User Response:
Do one of the following:
  • Correct the configuration.
  • Change the local implementation so that it does implement the required interface.
See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5079E: The {0} service instance obtained using configured JNDI name {1} does not extend the required class {2}.
Explanation:
{1} is the service type name defined for a Parlay service implemented locally. {2} is JNDI name specified as the implementation of service type name. {3} is an Class that must be extended by all local implementations of Parlay services defined in the active configuration. The active configuration includes the definition for the specified Parlay service implemented locally. The object obtained using the specified JNDI name does not extend the specified Class.
User Response:
Do one of the following:
  • Correct the configuration.
  • Change the local implementation so that it does extend the required Class.
See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5080E: Requested service {0} is not type {1}.
Explanation:
{1} is a Gateway service identifier. {2} is a Gateway service type. A compound name of the form service-type:service-identifier was specified for a Gateway service. The service identifier has been found in the Gateway's list of subscribed services, but the service type in the description does not match the service type in the compound name.
User Response:
Verify that the service type and service identifier are correctly specified. If the compound name is incorrect,
  • Correct the compound name in the request
  • Retry the operation
If the compound name is correct,
  • Check the console to determine if there was a communication, Gateway, or other failure.
  • Correct any existing problems.
  • Retry the operation.
TAS5081I: The {0} service is enabled.
Explanation:
{0} is a Gateway service type. The ParlayConnector has obtained the Gateway reference to the named service.
User Response:
None.
TAS5082E: The ParlayConnector timed out waiting for a Gateway callback in authentication.
Explanation:
The ParlayConnector is not able to complete authentication with the Parlay Gateway because the Gateway has not made the expected call back.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • ParlayConnector will retry authentication when it next receives a service manager request.
TAS5083E: The ParlayConnector timed out waiting for a Gateway callback to sign the service agreement for the {0} service.
Explanation:
{0} is a Gateway service type. The ParlayConnector is not able to sign a service agreement with the Parlay Gateway because the Gateway did not make the expected call back. The ParlayConnector is not able to obtain the requested service manager.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • ParlayConnector will retry signing the service agreement when it next receives a request for the service manager.
TAS5084E: Not able to get the initial Parlay Gateway reference from the primary remote host.
Explanation:
The ParlayConnector was not able to connect to the Gateway using the configured primary Gateway initial host.
User Response:
  • Verify that the ParlayConnector is correctly configured for the Gateway. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
  • Check the console to determine if there was a WebSphere or other failure. Correct any existing problems.
  • Restart the WebSphere Application Server.
TAS5085E: Not able to get the initial Parlay Gateway reference from the secondary remote host.
Explanation:
The ParlayConnector was not able to connect to the Gateway using the configured primary Gateway initial host. A secondary Gateway initial host is configured. The ParlayConnector is not able to connect to the Gateway using the configured secondary Gateway initial host.
User Response:
  • Verify that the ParlayConnector is correctly configured for the Gateway. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
  • Check the console to determine if there was a WebSphere or other failure. Correct any existing problems.
  • Restart the WebSphere Application Server.
TAS5086W: Configuration data {0} not found for secondary remote host.
Explanation:
{0} is a configuration property which is not configured. The ParlayConnector was not able to connect to the Gateway using the value configured for the primary Gateway initial host. A secondary Gateway initial host is not configured.
User Response:
If you configure a secondary Gateway initial host in the environment, the ParlayConnector will attempt to connect to this Gateway and use it when there is a failure to connect using the configured primary Gateway initial host. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5087I: The Gateway has issued IpClientAccess.terminateAccess with reason {0}.
Explanation:
{0} is the explanation text provided by the Gateway. The application server is shutting down because the Gateway has terminated access to it. The ParlayConnector must reauthenticate with the Gateway and sign service agreements. All applications must renew their notification requests.
User Response:
Restart the application server.
TAS5088I: The initial Parlay Gateway reference has been obtained.
Explanation:
The application server has obtained the IpInitial object for the Parlay Gateway.
User Response:
None.
TAS5089E: An unexpected error occurred in describeService({0},{1}).
Explanation:
{1} is the service type name defined for a Parlay service implemented locally. {2} is JNDI name specified as the implementation of service type name. The active configuration includes the definition for the specified Parlay service that is implemented locally. An exception occurred calling describeService() on the object bound to the JNDI name.
User Response:
Do one of the following:
  • Correct the configuration.
  • Correct the local implementation so that it does not throw an exception in describeService().
See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5090W: No properties were found during describeService({0},{1}).
Explanation:
{1} is the service type name defined for a Parlay service implemented locally. {2} is JNDI name specified as the implementation of service type name. The active configuration includes the definition for the specified Parlay service implemented locally. No service properties were returned by a call to describeService() on the object bound to the JNDI name.
User Response:
None.
TAS5091W: No gateway service instances were found meeting the requirements for type {0} (gateway ServiceTypeName {1}).
Explanation:
{1} is the service type specified on the getServiceManager() request. {2} is the ServiceTypeName defined on the Parlay gateway.
  • If {1} is not the same as {2}, then the active configuration includes the definition of service type alias {1} for gateway ServiceTypeName {2}.
  • If the active configuration includes service properties for type {1}, then they were specified in service discovery.
  • The gateway did not return any service instances during service discovery for gateway ServiceTypeName {2} (using any service properties specified in the active configuration for type {1}).
User Response:
  • Check the ServiceTypeName ({2}) to determine if it is a valid subscribed service name.
  • Check the active configuration to verify that any service properties specified for service type {1} are correct.
  • Check the gateway to determine if there is an active service manager instance of ServiceTypeName {2} and service properties as specified in the configuration for service type {1}.
  • Retry the operation.
TAS5401E: An unexpected error occurred.
Explanation:
An unexpected error occurred. The exception is printed and a stack trace is generated.
User Response:
Use the exception to determine the type of error, and the stack trace to determine where the error occurred.
TAS5402E: A Gateway Exception was thrown during IpAPILevelAuthentication.requestAccess().
Explanation:
An unexpected error occurred at the Gateway. The ParlayConnector will retry the operation.
User Response:
None.
TAS5403E: A Gateway Exception was thrown during retry IpAPILeveAuthentication.requestAccess().
Explanation:
An unexpected error occurred at the Gateway.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation.
TAS5404I: Retrying IpAPILevelAuthentication.requestAccess().
Explanation:
The ParlayConnector is retrying the operation that was in progress when an unexpected error occurred at the Gateway.
User Response:
None.
TAS5406I: The ParlayConnector is connected to the gateway.
Explanation:
The ParlayConnector successfully connected with the Gateway.
User Response:
None.
TAS5407W: The ParlayConnector is not connected to the gateway.
Explanation:
The ParlayConnector has not connected with the Gateway.
User Response:
  • Verify that the ParlayConnector is correctly configured for the Gateway. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
TAS5408E: A Gateway Exception was thrown during ipInitialRef.initiateAuthentication().
Explanation:
An unexpected error occurred at the Gateway. The ParlayConnector will retry the operation.
User Response:
None.
TAS5409E: A Gateway Exception was thrown during retry ipInitialRef.initiateAuthentication().
Explanation:
An unexpected error occurred at the Gateway.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation.
TAS5410I: Retrying ipInitialRef.initiateAuthentication().
Explanation:
The ParlayConnector is retrying the operation that was in progress when an unexpected error occurred at the Gateway.
User Response:
None.
TAS5411E: A Gateway Exception was thrown during IpAPILevelAuthentication.selectEncryptionMethod().
Explanation:
An unexpected error occurred at the Gateway. The ParlayConnector will retry the operation.
User Response:
None.
TAS5412E: A Gateway Exception was thrown during retry IpAPILevelAuthentication.selectEncryptionMethod().
Explanation:
An unexpected error occurred at the Gateway.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation.
TAS5413I: Retrying IpAPILevelAuthentication.selectEncryptionMethod().
Explanation:
The ParlayConnector is retrying the operation that was in progress when an unexpected error occurred at the Gateway.
User Response:
None.
TAS5414E: A Gateway Exception was thrown during IpAPILevelAuthentication.authenticate().
Explanation:
An unexpected error occurred at the Gateway. The ParlayConnector will retry the operation.
User Response:
None.
TAS5415E: A Gateway Exception was thrown during retry IpAPILevelAuthentication.authenticate().
Explanation:
An unexpected error occurred at the Gateway.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation.
TAS5416I: Retrying IpAPILevelAuthentication.authenticate().
Explanation:
The ParlayConnector is retrying the operation that was in progress when an unexpected error occurred at the Gateway.
User Response:
None.
TAS5420I: The ParlayConnector accepted the Parlay Gateway. Application-Gateway authentication was successful.
Explanation:
The Gateway has been authenticated to the application.
User Response:
None.
TAS5421E: The ParlayConnector rejects the Parlay Gateway. Application-Gateway authentication was not successful.
Explanation:
The Gateway could not be authenticated to the application. The application has halted its attempt to connect with the Gateway.
User Response:
  • Verify that the ParlayConnector is correctly configured for the Gateway. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
Unless you need to restart the application or server to correct some other problem, it is not necessary to restart it. The ParlayConnector will retry this operation automatically on the next request for a service manager.
TAS5422E: Configuration data was not found for required property {0}.
Explanation:
{0} is a configuration property. The named property is not defined in the configuration. There is no default value for this property, therefore, it must be configured.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5423E: The Parlay Gateway has returned a NULL object for IpAPILevelAuthentication.
Explanation:
The ParlayConnector has established contact with the Gateway, but the Gateway has not returned the object needed for authentication to begin.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation.
TAS5424E: Application encryption capabilities list is empty.
Explanation:
The ParlayConnector makes a list of encryption methods to pass to the Gateway for authentication method negotiation. When the list of encryption methods supported by the ParlayConnector is reduced using configuration data, the list becomes empty. The ParlayConnector cannot continue the authentication process.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5425E: Authentication Method negotiation was not successful.
Explanation:
The ParlayConnector makes a list of encryption methods to pass to the Gateway for authentication method negotiation. This list contains the list of encryption methods supported by the ParlayConnector, reduced using configuration data. The Gateway does not accept any encryption method in the list passed to it by the ParlayConnector, therefore, the authentication process cannot continue.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5426I: Property {0} was not found in the configuration.
Explanation:
{0} is a configuration property. The named property is not defined in the configuration. If a default value is defined for the property, the default value will be used.
User Response:
If you intended to configure the named property, correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5427W: Property {1}, defined in the configuration, has an unrecognized value {0}.
Explanation:
{1} is the incorrect value assigned to the specified property. {2} is a configuration property. The named property is defined in the configuration, but the value assigned to it is not correct. If a default value is defined for the property, the default value will be used.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5428E: The Parlay Gateway returned a response but did not use the prescribed authentication method.
Explanation:
The Gateway participated in the authentication process, but did not use the encryption method that it chose during authentication method negotiation.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation.
TAS5429E: The Parlay Gateway specified an authentication method is not in the capability list.
Explanation:
The ParlayConnector makes a list of encryption methods to pass to the Gateway for authentication method negotiation. This list contains the list of encryption methods supported by the ParlayConnector, reduced using configuration data. The Gateway participated in the authentication method negotiation, but chose an authentication method not in the list passed to it by the ParlayConnector.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation.
TAS5430W: Encryption method {0}, defined in the configuration, cannot be used because no value is defined for {1}.
Explanation:
{1} is an encryption method configured in the environment. {2} is a configuration property required for use with the named encryption method, but is not found in the environment. The named encryption method is defined in the configuration, but it cannot be used because the named property is not defined in the configuration.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5431W: Encryption method {0}, defined in the configuration, cannot be used because no values are defined for {1} and {2}.
Explanation:
{1} is an encryption method configured in the environment. {2} is a configuration property required for use with the named encryption method, but is not found in the environment. {3} is a configuration property required for use with the named encryption method, but is not found in the environment. The named encryption method is defined in the configuration, but it cannot be used because the named properties are not defined in the configuration.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5432E: Not able to stop the application server after IpAppAccess.terminateAccess. An application server Force Stop, then Start is required.
Explanation:
The Gateway has terminated the current access session with the application server. The application server must shut down, then reauthenticate with the Gateway and sign service agreements. All applications must renew their notification requests. The application server was not able to shut down automatically.
User Response:
Stop the application server. Restart the application server.
TAS5433E: No callback object provided. IpAppAccess callback object is required.
Explanation:
The caller passed a NULL parameter instead of the required IpAppAccess callback object.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Rebuild and redeploy the application.
  • Restart the WebSphere Application Server.
  • Retry the operation.
TAS5434E: Not able to get IpAPILevelAuthentication object from ParlayGateway.
Explanation:
The ParlayConnector established contact with the Gateway, but the Gateway did not return the object needed for authentication to begin.
User Response:
  • Verify that the ParlayConnector is correctly configured for the Gateway. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation.
TAS5435E: Not able to get IpAccess object from ParlayGateway.
Explanation:
The ParlayConnector established contact with the Gateway, but the initial request for access was not successful.
User Response:
  • Verify that the ParlayConnector is correctly configured for the Gateway. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation.
TAS5436E: Required property {1}, defined in the configuration, has an unrecognized value {0}.
Explanation:
{1} is not the correct value assigned to the specified property. {2} is a configuration property. The named property is defined in the configuration, but the value assigned to it is not correct. There is no default value for this property, so it must be configured correctly.
User Response:
Correct the configuration. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5437E: Not able to locate the Parlay Gateway in the ORB Name Service.
Explanation:
The ParlayConnector is not able to locate the Gateway using the Name Service in the configured ORB.
User Response:
  • Verify that the ParlayConnector is correctly configured for the Gateway. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation.
TAS5438I: IBM WebSphere Telecom Web Services Server @PRODUCT.VERSION.DETAIL@, build level: {0}.
Explanation:
{0} identifies the product build level. The ParlayConnector is reporting its product level.
User Response:
None.
TAS5439E: Not able to locate the local ORB Name Service.
Explanation:
The ParlayConnector is not able to locate the Name Service in the local ORB.
User Response:
  • Check the console to determine if there was a WebSphere or other failure. Correct any existing problems.
  • Restart the WebSphere Application Server.
  • Retry the operation.
TAS5440E: Not able to get the naming context from the local ORB Name Service.
Explanation:
The ParlayConnector is not able to obtain the Naming Context from the local ORB Name Service.
User Response:
  • Check the console to determine if there was a WebSphere or other failure. Correct any existing problems.
  • Restart the WebSphere Application Server.
  • Retry the operation.
TAS5441E: Not able to get the naming context from the primary remote ORB Name Service.
Explanation:
The ParlayConnector is not able to obtain the Naming Context from the Name Service of the ORB configured as the Gateway Primary Name Service.
User Response:
  • Verify that the ParlayConnector is correctly configured for the Gateway. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
  • Check the console to determine if there was a WebSphere or other failure. Correct any existing problems.
  • Restart the WebSphere Application Server.
  • Retry the operation.
TAS5442E: Not able to get the naming context from the secondary remote ORB Name Service.
Explanation:
The ParlayConnector was not able to connect to the Gateway using the ORB configured as the Gateway Primary Name Service. A Gateway Secondary Name Service ORB is also configured. The ParlayConnector is not able to obtain the Naming Context from the Name Service of the ORB configured as the Gateway Secondary Name Service.
User Response:
  • Verify that the ParlayConnector is correctly configured for the Gateway. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
  • Check the console to determine if there was a WebSphere or other failure. Correct any existing problems.
  • Restart the WebSphere Application Server.
  • Retry the operation.
TAS5443W: Configuration data {0} was not found for secondary remote ORB Name Service.
Explanation:
{0} identifies the property which is not configured. The ParlayConnector was not able to connect to the Gateway using the ORB configured as the Gateway Primary Name Service. A Gateway Secondary Name Service ORB is not configured.
User Response:
If you configure a Gateway Secondary Name Service ORB in the environment, the ParlayConnector will attempt to connect to the Gateway using it when there is a failure to connect using the configured Gateway Primary Name Service ORB. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
TAS5444E: Not able to find the GatewayAuthenticator class {0}.
Explanation:
{0} identifies a Gateway authenticator class name. The ParlayConnector is configured to use the named class for authenticating with the ParlayGateway, but the named class is not found in the classpath.
User Response:
  • Verify that the class name is correctly specified in the configuration.
  • Verify that the class can be found in the classpath.
  • Rebuild and redeploy the application.
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Restart the WebSphere Application Server.
TAS5445E: Not able to find the GatewayLocator class {0}.
Explanation:
{0} identifies a Gateway locator class name. The ParlayConnector is configured to use the named class for locating the ParlayGateway, but it is not found in the classpath.
User Response:
  • Verify that the class name is correctly specified in the configuration.
  • Verify that the class can be found in the classpath.
  • Rebuild and redeploy the application.
  • Check the console to determine if there was a WebSphere or other failure. Correct any existing problems.
  • Restart the WebSphere Application Server.
  • Retry the operation.
TAS5446E: Not able to create an instance of class {0} using constructor {0}().
Explanation:
{1} identifies a class name. {2} identifies a class constructor. The named class is required to have a default constructor, but an error occurred when the ParlayConnector attempted to use it.
User Response:
  • Verify that the class has a default constructor.
  • Verify that the correct class is found in the classpath.
  • Rebuild and redeploy the application.
  • Check the console to determine if there was a WebSphere or other failure. Correct any existing problems.
  • Restart the WebSphere Application Server.
  • Retry the operation.
TAS5447I: The Parlay Gateway accepts the ParlayConnector. Gateway-Application authentication was successful.
Explanation:
The Parlay Gateway has notified the ParlayConnector that the ParlayConnector has successfully completed authenticating itself to the Gateway.
User Response:
None.
TAS5448E: The Parlay Gateway rejects the ParlayConnector. Gateway-Application authentication was not successful.
Explanation:
The Parlay Gateway has notified the ParlayConnector that the ParlayConnector has failed to authenticate itself to the Gateway.
User Response:
  • Verify that the ParlayConnector is correctly configured for the Gateway. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
  • Check the console to determine if there was a WebSphere or other failure. Correct any existing problems.
  • Restart the WebSphere Application Server.
  • Retry the operation.
TAS5449E: A Gateway Exception was thrown during IpAPILevelAuthentication.authenticationSucceeded().
Explanation:
An unexpected error occurred at the Gateway. The ParlayConnector will retry the operation.
User Response:
None.
TAS5450E: A Gateway Exception was thrown during retry IpAPILevelAuthentication.authenticationSucceeded().
Explanation:
An unexpected error occurred at the Gateway.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure.
  • Correct any existing problems.
  • Retry the operation.
TAS5451I: Retrying IpAPILevelAuthentication.authenticationSucceeded().
Explanation:
The ParlayConnector is retrying the operation that was in progress when an unexpected error occurred at the Gateway.
User Response:
None.
TAS5452E: A Gateway Exception was thrown during IpAPILevelAuthentication.abortAuthentication().
Explanation:
An unexpected error occurred at the Gateway. The ParlayConnector will retry the operation.
User Response:
None.
TAS5453E: A Gateway Exception was thrown during retry IpAPILevelAuthentication.abortAuthentication().
Explanation:
An unexpected error occurred at the Gateway.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure.
  • Correct any existing problems.
  • Retry the operation.
TAS5454I: Retrying IpAPILevelAuthentication.abortAuthentication().
Explanation:
The ParlayConnector is retrying the operation that was in progress when an unexpected error occurred at the Gateway.
User Response:
None.
TAS5455E: Not able to get the naming context using the value configured for property {0}.
Explanation:
{0} is a configuration property. The ParlayConnector was unable to connect to the Gateway using the value configured for the named property.
User Response:
  • Verify that the ParlayConnector is correctly configured for the Gateway. See the configuration information in the IBM WebSphere Telecom Web Services Server information center.
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Restart the WebSphere Application Server.
TAS5456I: Connecting to NameService on host {0}, port {1}.
Explanation:
The ParlayConnector is connecting to the specified hostname and port.
User Response:
None.
TAS5457I: Attempting to resolve the NamingContext for the Gateway.
Explanation:
The ParlayConnector is attempting to resolve the NamingContext for the Gateway. The Parlay Connector tries until the NamingContext is resolved.
User Response:
If this message occurs several times, ensure that the gateway location configuration is property bound to the Gateway.
TAS5458I: Attempt #{0} to resolve the NamingContext for the Gateway.
Explanation:
The ParlayConnector is attempting to resolve the NamingContext for the Gateway. The Parlay Connector tries until the configured retry count is reached or the NamingContext is resolved.
User Response:
None
TAS5459W: The ParlayConnector state is stopped or stopping. The {0} request is not being processed.
Explanation:
{0} is a request received by the ParlayConnector. The current ParlayConnector state prevents it from processing the request.
User Response:
Retry the operation when the ParlayConnector is in the 'started' state.
TAS5460W: The ParlayConnector state is restarting or recovering. The {0} request is not being processed.
Explanation:
{0} is a request received by the ParlayConnector. The current ParlayConnector state prevents it from processing the request.
User Response:
Retry the operation when the ParlayConnector is in the 'started' state.
TAS5461E: More than one serviceToken has been obtained from the Gateway for service type {0}.
Explanation:
{0} identifies a Parlay Gateway service type. The ParlayConnector has detected what appears to be a Parlay Gateway error.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Restart the application server.
  • Retry the operation.
TAS5462E: Not able to get IpAccess from ParlayConnector. Requested {0} service manager cannot be obtained.
Explanation:
{0} is the name of the requested service manager. The ParlayConnector was not successful getting access to the Gateway, therefore it is not able to obtain the requested service manager. See the preceding messages for more information about the failure.
User Response:
  • Examine the preceding messages for more details about the failure. Correct the problems described in those messages.
  • Check the console to determine if there was a communication, Gateway, or other failure.
  • Retry the operation
TAS5463E: Not able to get Gateway IpServiceAgreementManagement object. Requested {0} service manager cannot be obtained.
Explanation:
{0} is the name of the requested service manager. The ParlayConnector was not able to obtain the IpServiceAgreementManagement interface from the ParlayGateway, therefore it is not able to obtain the requested service manager. See the preceding messages for more information about the failure.
User Response:
  • Examine the preceding messages for more details about the failure. Correct the problems described in those messages.
  • Check the console to determine if there was a communication, Gateway, or other failure.
  • Retry the operation
TAS5464W: The ParlayConnector state is faulty. The {0} request is not being processed.
Explanation:
{0} identifies a request received by the ParlayConnector. The current ParlayConnector state prevents it from processing the request.
User Response:
See Troubleshooting in the IBM WebSphere Telecom Web Services Server information center.
TAS5465E: A Gateway Exception was thrown during ipInitialRef.initiateAuthenticationWithVersion().
Explanation:
An unexpected error occurred at the Gateway. The ParlayConnector will retry the operation.
User Response:
None.
TAS5466E: A Gateway Exception was thrown during retry ipInitialRef.initiateAuthenticationWithVersion().
Explanation:
An unexpected error occurred at the Gateway.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation.
TAS5467I: Retrying ipInitialRef.initiateAuthenticationWithVersion().
Explanation:
The ParlayConnector is retrying the operation that was in progress when an unexpected error occurred at the Gateway.
User Response:
None.
TAS5468E: A Gateway Exception was thrown during IpAPILevelAuthentication.selectAuthenticationMethod().
Explanation:
An unexpected error occurred at the Gateway. The ParlayConnector will retry the operation.
User Response:
None.
TAS5469E: A Gateway Exception was thrown during retry IpAPILevelAuthentication.selectAuthenticationMethod().
Explanation:
An unexpected error occurred at the Gateway.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation.
TAS5470I: Retrying IpAPILevelAuthentication.selectAuthenticationMethod().
Explanation:
The ParlayConnector is retrying the operation that was in progress when an unexpected error occurred at the Gateway.
User Response:
None.
TAS5501E: The connection to a Parlay Gateway framework failed.
Explanation:
An unexpected error occurred at the Gateway.
User Response:
  • Check the console to determine if there was a communication, Gateway, or other failure. Correct any existing problems.
  • Retry the operation.
TAS5502I: Framework reconnect is not being done, current state of Connector is {0}.
Explanation:
The Parlay Connector is currently being stopped and the framework failover process will not be done.
User Response:
  • None
TAS5503I: An invalid Framework Heart Beat timer has expired, and is being removed.
Explanation:
An invalid Heartbeat timer was found from a previous session and will be removed.
User Response:
  • None
TAS5504I: Check found a received pulse from Gateway Framework.
Explanation:
A Heartbeat pulse was received from the Parlay Gateway. This is a health check from the Parlay Gateway to the Parlay Connector.
User Response:
  • None
TAS5505E: Check did not find a received pulse from Gateway Framework.
Explanation:
A Heartbeat pulse was not received from the Parlay Gateway. The health check from the Parlay Gateway to the Parlay Connector has failed. The framework failover process will be initiated.
User Response:
  • None
TAS5506E: Framework recovery will be started.
Explanation:
The framework failover process has been initiated.
User Response:
  • None
TAS5507E: Problem with the reference to the Application Manager.
Explanation:
An exception occurred when the Heartbeat Monitor tried to get an identifier for the ApplicationManager EJB for starting the failover process. This identifier is unique for each deployed ApplicationManager EJB.
User Response:
Enable trace log and restart the Parlay Connector to get trace information.
TAS5508I: HeartBeat Check timer started: Pulse time {0}, Missed Count {1}.
Explanation:
A Heartbeat timer has been started with the following values. {1} Is the amount of time between each pulse from the Gateway. {2} Is the number of pulse opportunities the Gateway is allowed to miss before framework failover processing will be initiated. The timer will check for received pulses from the Gateway using a time value based on the Pulse time multiplied by the number of Missed count.
User Response:
  • None
TAS5509E: Framework recovery will attempt recovery without resetting Service information
Explanation:
The framework failover process has been initiated.
User Response:
  • None
TAS5510E: Framework recovery has completed
Explanation:
The framework failover process has completed.
User Response:
  • Check the console to determine the state of the Parlay Connector. Correct any existing problems.
TAS5511E: Incorrect Framework version parameter
TAS5599E: {0}.
Explanation:
Used internally.
User Response:
None
TAS6001E: Unexpected error.
Explanation:
An unexpected error has occurred. An unexpected error is an error that is not normally expected to occur in the system. The error is caught, the user is notified, the exception, if any, is printed, and the system tries to recover. However, normal operation may not resume.
User Response:
Please note any information, such as exception information, that is provided with this error. You may need to restart the system.
TAS6003W: Property {0} in configuration has an unrecognized value.
Explanation:
The value for a Property key in the environment has an unexpected value in it. Where possible defaults are used.
User Response:
Correct the value for the given key.
TAS6004E: Error, could not find {0} in the JNDI environment.
Explanation:
The component is looking for a value key in the JNDI environment. That value is not present. Where possible a default is used.
User Response:
Add the key value to the environment configuration information.
TAS6005E: An Exception occurred while checking the environment.
Explanation:
The component is experienced an error interacting with the JNDI environment. Further information in the form of an Exception should be provided.
User Response:
Review the Exception for possible action.
TAS6006E: An Exception occurred getting state of ManagedObject {0}.
Explanation:
An error occurred while trying to get the provided object's state. Further information in the form of an Exception should be provided.
User Response:
Review the Exception for possible action.
TAS6007E: Incorrect parameters were passed. {0} has a value of {1}.
Explanation:
The method that generated this message was passed an incorrect parameter.
User Response:
Review the logs.
TAS6008E: An unknown ManagementEvent Type {0} was received and ignored.
Explanation:
An unknown ManagementEvent has been received. This Event is logged, and then ignored. The ManagementEvent in question is provided.
User Response:
Possible causes for this error are:
  • The code base has mixed versions of code in it.
  • An incorrect ManagementEvent was generated and passed. System generated ManagementEvents log their origin.
TAS6009E: AssignmentID is no longer valid. An application server Force Stop, then Start is required.
Explanation:
An error has been found while processing call notifications. The ParlayCallbackManager cannot restore the incorrect call notification.
User Response:
  1. Use the ParlayWebConsole to force the application server to stop.
  2. Use the ParlayWebConsole to start the application server.
TAS6010E: Notification request cannot be recovered. An application server Force Stop, then Start is required.
Explanation:
An error has been found while processing call notifications. The ParlayCallbackManager cannot restore the incorrect call notification.
User Response:
  1. Use the ParlayWebConsole to force the application server to stop.
  2. Use the ParlayWebConsole to start the application server.
TAS6011E: Requested {0} property cannot be created.
Explanation:
{0} is the name of a property. An unexpected error occurred while creating or retrieving the named property from the database.
User Response:
  1. Use the ParlayWebConsole to force the application server to stop.
  2. Use the ParlayWebConsole to start the application server.
TAS6012E: An error occurred. One or more of the properties files to merge was null, target is {0}, overlay is {1}.
Explanation:
The component was trying to merge two Properties Objects. One or more of the Properties Objects was null.
User Response:
Review the logs.
TAS6013E: An Exception occurred setting state on ManagedObject {0}.
Explanation:
An Exception occurred trying to set the State on a ManagedObject.
User Response:
Review the Exception for possible action.
TAS6014W: Object {0} is not a ManagedObject EJB. Ending operation.
Explanation:
The operation does not proceed, because the object being acted on is not a ManagedObject.
User Response:
Review the ManagedObject list for inclusion of non-ManagedObjects.
TAS6015W: No ManagedObjects were found.
Explanation:
The component was not able to find any ManagedObjects in the ManagedObject list.
User Response:
Review the ManagedObject list, and add any ManagedObjects needing management to that list.
TAS6017E: Properties resource {0} could not be found.
Explanation:
A properties file could not be found. Defaults are used where possible.
User Response:
Ensure that the properties file listed is available and readable by the system.
TAS6018E: No ApplicationManagers Objects were found.
Explanation:
No JNDI entries for any ApplicationManagers were found, so no ApplicationManagers will be started.
User Response:
Review the JNDI entries in the properties files for the ApplicationManager to ensure they are present.
TAS6019E: The time-out {0} value for the ApplicationManager to become ready has been exceeded.
Explanation:
The allotted startup time {0} for the system and the ApplicationManager to become ready has been exceeded.
User Response:
Review the logs for errors and possible corrective action.
TAS6020I: Current State of the {0} is {1}.
Explanation:
The current State of the ManagedObject is listed.
User Response:
No action is needed.
TAS6021I: The Queue status is {0}.
Explanation:
The status table of the System Queue.
User Response:
No action is required.
TAS6022I: The Connection table status is as follows: [{0}].
Explanation:
The status table for connections.
User Response:
No action is required.
TAS6023I: An Exception occured releasing the cluster wide lock. The Exception is {0}.
Explanation:
An Exception occurred trying to release the cluster wide lock. This lock is used during startup and shutdown.
User Response:
Review the Exception for possible action.
TAS6400I: Scheduler thread One started.
Explanation:
The main Scheduler thread started successfully.
User Response:
None required.
TAS6401I: Scheduler thread Two started.
Explanation:
The Scheduler dispatcher thread started successfully.
User Response:
None required.
TAS6402I: Scheduler thread One ended.
Explanation:
The Scheduler main thread was stopped successfully.
User Response:
None required.
TAS6403I: Scheduler thread Two ended.
Explanation:
The Scheduler dispatcher thread was stopped successfully.
User Response:
None required.
TAS6407E: Schedule event exception.
Explanation:
An attempt to schedule an event resulted in an exception.
User Response:
  • Check to make sure that the Scheduler persistent data storage location is available, accessible, and configured correctly.
  • Enable trace log and reschedule event to get trace information.
TAS6408E: Scheduler thread Two start exception.
Explanation:
Exception occurred when the Scheduler tried to start the event dispatcher thread
User Response:
Check trace log for stack dump if trace is enabled or try to start the thread again with trace enabled.
TAS6409E: Update scheduled event exception.
Explanation:
An exception occurred when the Scheduler tried to update scheduled event with a valid key.
User Response:
  • Check to make sure that the Scheduler persistent data storage location is available, accessible, and configured correctly.
  • Enable trace log and re-execute event update to get trace information.
TAS6410E: Delete scheduled event exception. Incorrect event key.
Explanation:
An exception occurred when the Scheduler tried to delete scheduled event with a key that does not match any of the available scheduled event keys in the persistent data storage location.
User Response:
Supply the correct key.
TAS6411E: Delete scheduled event exception.
Explanation:
Exception occurred when the Scheduler tried to delete scheduled event with a valid key.
User Response:
  • Check to make sure that the Scheduler persistent data storage location is available, accessible, and configured correctly.
  • Enable trace log and re-execute delete event to get trace information.
TAS6412I: Scheduler already started.
Explanation:
An attempt to start the Scheduler, when it is already started.
User Response:
None required.
TAS6413E: Scheduler start exception.
Explanation:
An exception occurred when the Scheduler thread One start method was invoked.
User Response:
Check trace log for stack dump if trace is enabled or try to start the thread again with trace enabled.
TAS6416W: Event action type {0} is not supported.
Explanation:
{1} is the event action (create=1,delete=2,update=3) for the Scheduler. When trace is enabled, information is logged for debug.
User Response:
None required.
TAS6417W: The Scheduler is currently not started.
Explanation:
The Scheduler thread One is currently in a stopped state or not started. The Scheduler thread One must be running for any scheduled event being delivered.
User Response:
Contact the administrator responsible for starting the Scheduler thread One.
TAS6418E: Database table access exception.
Explanation:
Exception occurred when the Scheduler thread One tries to access a table in a persistent data storage location.
User Response:
  • Check to make sure that the Scheduler persistent data storage location is available, accessible, and configured correctly.
  • Enable trace log and restart thread One to get trace information.
TAS6422E: Error parsing a collection of scheduled event entity.
Explanation:
an exception occurred when the Scheduler thread One tries to parse a collection of scheduled event entity that was retrieved from a persistent data storage location.
User Response:
Enable the trace log to get stack information about the exception.
TAS6430E: Object type not supported exception. Type must be a Stateless Session EJB.
Explanation:
An exception occurred when the Enterprise Java Bean (EJB) handle to the application that will receive the callback notification from the Scheduler is not a supported EJB type. The Scheduler only supports Stateless session EJB for application callbacks.
User Response:
Use the supported EJB for applications that will be receiving notification from the Scheduler.
TAS6431E: The EJB handle field of this ScheduledEventInfo instance is NULL.
Explanation:
An exception occurred when the EJB handle to the client application that will be receiving a callback notification for the event being scheduled is not supplied. This is a required field.
User Response:
Supply an EJB handle of the application that will be receiving notification from the Scheduler.
TAS6432E: The date field of this ScheduledEventInfo instance is NULL.
Explanation:
An exception occurred when the time and date to deliver the event being scheduled is not supplied. This is a required field.
User Response:
Supply the time and date that the event will be delivered.
TAS6433E: The key field of this ScheduledEventInfo instance is NULL.
Explanation:
An exception occurred when the key associated with a Scheduled event being updated is not supplied. This field is only required for scheduled event update.
User Response:
Supply the associated key to the scheduled event that needs update.
TAS6434E: ScheduledEventInfo is NULL.
Explanation:
An exception occurred when the ScheduledEventInfo object, which should contain the Scheduler required information for the event being scheduled is not supplied.
User Response:
Supply an instance of ScheduledEventInfo with the required Scheduler information for the event being scheduled.
TAS6435E: Repetition value is {0}. Repetition value must be equal to or greater than {1}.
Explanation:
{1} is the number of times to repeat delivery for a scheduled event. {2} is the minimum required times an event should be scheduled for repetition. When trace is enabled, information is logged for debug.
User Response:
None required.
TAS6436E: Interval value is {0}. Interval value must be equal to or greater than {1}.
Explanation:
{1} is the time delay between the delivery of repeating scheduled event. {2} is the minimum required time delay between repeating events. When trace is enabled, information is logged for debug.
User Response:
Not required.
TAS6437W: Repetition value must be greater than zero for Interval value {0} to be meaningful.
Explanation:
{1} is the time delay between the delivery of repeating scheduled event. When trace is enabled, information is logged for debug.
User Response:
Not required.
TAS6438E: ScheduledEventSettings is NULL.
Explanation:
An exception occurred when the ScheduledEventSettings object, which should contain the required Scheduler information for the event being scheduled, is not supplied.
User Response:
Supply an instance of ScheduledEventSettings with the required Scheduler information for the event being scheduled.
TAS6440E: Failure setting Scheduler state.
Explanation:
An exception occurred when the Scheduler tried to update its state information in a persistent data storage location.
User Response:
  • Check to make sure that the database is available, accessible, and configured correctly.
  • Enable trace log and restart the Scheduler to get trace information.
TAS6441E: Failure getting Scheduler location within a cluster.
Explanation:
An exception occurred when the Scheduler tried to determine the instance of the WAS machine location that is currently active within a cluster. The location information is stored in a persistent data storage location.
User Response:
  • Check to make sure that the database is available, accessible, and configured correctly.
  • Enable trace log and restart the Scheduler to get trace information.
TAS6442E: Failure getting Scheduler application ID.
Explanation:
An exception occurred when the Scheduler tried to get an identifier for the EventScheduler EJB for trace logging. This identifier is unique for each deployed EventScheduler EJB.
User Response:
Enable trace log and restart the Scheduler to get trace information.
TAS6444E: Failure sending management event ({0}) to Scheduler:{1}.
Explanation:
{1} is a ManagedObjectEvent Type used to manage the Scheduler state. {2} is the WAS node location where Scheduler is currently active within a cluster. An exception occurred when the Scheduler tries to forward a management event to the active Scheduler within a cluster.
User Response:
  • Check to make sure that the database is available, accessible, and configured correctly.
  • Enable trace log and restart the Scheduler to get trace information.
TAS6445I: The current state of {0} is {1}.
Explanation:
{1} is the unique identifier for the Scheduler. {2} is the current state of the Scheduler. When trace is enabled, information is logged for debug.
User Response:
None required.
TAS6446E: Error starting secondary Scheduler method.
Explanation:
An exception occurred when starting a secondary Scheduler thread one within a cluster.
User Response:
Enable trace log and restart the Scheduler to get trace information.
TAS6447E: Error getting class parameter type.
Explanation:
An exception occurred when trying to get the object type of a given parameter within a cluster.
User Response:
Enable trace log and restart the Scheduler to get trace information.
TAS6448E: Error setting Scheduler state properties.
Explanation:
An exception occurred when trying to set the current state of the Scheduler within a cluster.
User Response:
Enable trace log and restart the Scheduler to get trace information.



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