|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Check the connection parameters specified during configuration, Verify that the Work Station Listener is running.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Please check the repository. Please ignore this message if you are using a repository configured using the 4.1.1 adapter.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Please check the value of the CommunicationType'field,intheincomingmessage.'
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Startup Error. Unable to create a connection with the target application %1 using connection parameters User Name: %2, Client Name: %3,Group Name: %4 and the target application error is %5
|
|
|
|
|
|
|
|
|
|
|
|
|
If you are running the adapter against configurations created by 4.x palette or your adapter configuration was saved in AE Version 4.0 or AE Version 5.0 format, the warning message can be ignored and the password will be handled correctly by the adapter. If your adapter configuration was saved in AE Version 5.1 format, open the configuration in TIBCO Designer and change the password to use a global variable. If the warning still displays, contact TIBCO support.
|
|
Publication error. Publication Service, failed for Event Name : %1, encountered error %2 while trying to connect to target application Tuxedo. Connection parameters are User Name:%3, Client Name: %4, Group Name: %5, Flag: %6.
|
|
|
Please ensure that the target application is running. Verify your repository settings for validity of connection parameters
|
|
Publication error. Publication service received event. Failed while converting event to Minstance as it could not get the class description. Repository URL is %1 and the Configuration URL is %2.
|
|
|
Please verify the configuration of the publication service and check that the schema/class definitions are present in the repository.
|
|
|
|
|
|
|
|
|
|
Please check the configuration of the application that is requesting the event and make sure that it matches the inbound event definition for the above RequestResponse service.
|
|
Request Response error. Request Response service %1 failed to deserialize the received MOperationRequest to MInstance. The Repository URL is %2 and the Configuration URL is %3
|
|
|
Please check the configuration of the application that is requesting the event and make sure that it matches the inbound event definition for the above Request Response service.
|
|
|
|
|
|
|
Request Response error. Request Response service failed due to target application invocation error %1 for Tuxedo service: %2,Communication Type: %3 on application call %4.Tracking Id: %5
|
|
|
Please check the target application command and the parameters passed to it and ensure that they are valid.
|
|
|
|
|
Please check the target application command and the parameters passed to it and ensure that they are valid.
|
|
|
|
|
|
|
|
|
Request Response Invocation Service
|
Please check the repository settings for valid configuration of the Request Response Invocation service.
|
|
|
|
Request Response Invocation Service
|
Please check the repository settings for valid configuration of the Request Response Invocation service.
|
|
|
|
Request Response Invocation Service
|
Please ensure that the target application is running. Also check the configuration of the Request Response Invocation service.
|
|
|
|
Request Response Invocation Service
|
Please check repository settings for valid configuration of the Request Response Invocation endpoint for this service.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Subscription error. Subscription service failed due to target application invocation error %1 for Tuxedo service: %2, Communication Type: %3 on application call %4. Tracking Id: %5
|
|
|
Please check the target application command and the parameters passed to it and ensure that they are valid.
|
|
Subscription error. Subscription service failed due to target application invocation error %1 for RequestQueueName: %2, QueueSpaceName: %3,Communication Type: %4 on application call %5.Tracking Id: %6
|
|
|
Please check the target application command and the parameters passed to it and ensure that they are valid.
|
|
Subscription error. Subscription service failed due to target application invocation error %1 for ReplyQueueName: %2, QueueSpaceName: %3,Communication Type: %4 on application call %5.Tracking Id: %6
|
|
|
Please check the target application command and the parameters passed to it and ensure that they are valid.
|
|
|
|
|
Please check the target application command and the parameters passed to it and ensure that they are valid.
|
|
|
|
|
Please check the target application command and the parameters passed to it and ensure that they are valid.
|
|
|
|
|
Please check the target application command and the parameters passed to it and ensure that they are valid.
|
|
|
|
|
Please check the target application command and the parameters passed to it and ensure that they are valid.
|
|
|
|
|
Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service.
|
|
|
|
|
Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service
|
|
|
|
|
Check the configuration of the application that is publishing the event and make sure that it matches the inbound event definition for the above subscription service
|
|
Subscription error. Subscription service %1 could not process the inbound event for Communication Type : %2,due to connection error against target application Tuxedo using parameters Client Name: %3, Group Name: %4, User Name : %5.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Publication error. Publication service failed due to target application invocation error: %1 for QueueName: %2, QueueSpaceName: %3, Communication Type: %4 on application call %5. Tracking Id: %6
|
|
|
Please check the target application command and the parameters passed to it and ensure that they are valid.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Please type in a valid name. Adapter Configuration names can only have alphanumeric characters and can be up to 80 characters long.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Invalid Instance Name/Adapter Configuration names must have only alphanumeric characters and can be up to 80 characters long. Please type in a valid name.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Please checkout the resource and try renaming again. You can select the resource to be checked out by clicking the Go To Resource button.
|
|
|
|
|
Please checkout the resource and try deleting again. You can select the resource to be checked out by clicking the "Go To Resource" button.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Please do not use 'PollingIntervalforOutstandingInvocations''
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|