|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Configuration Rename Error/ Adapter Configuration names must have only alphanumeric characters with no embedded spaces and can be up to 80 characters long. Type in a valid name.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Field:Instance Name/Palette error. Adapter Configuration names must have only alphanumeric characters with no embedded spaces and can be up to 80 characters long. Type in a valid name.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Connection Retry Mechanism Warning/This adapter version does not support connection retry mechanism. The values configured in the Run-time Connection tab will be ignored
|
|
|
You are probably using an older version of the adapter which does not support connection retry mechanism.
|
|
Connection Retry Mechanism Warning/This adapter version does not suspend services on connection failure. The configured value 'Number of Reconnect Attempts Before Suspending Impacted Service(s)' will be ignored
|
|
|
You are probably using an older version of the adapter which does not support suspending services on connection failure.
|
|
|
|
|
Do not use JMS service if you are using an older version of the adapter which does not support JMS services.
|
|
|
|
|
Do not use XML wire format if you are using an older version of the adapter which does not support XML wire format.
|
|
|
|
|
Do not configure more than one service in an instance if you are using an older version of the adapter.
|
|
|
|
|
|
|
Palette Error/Palette error. The value of ’Number of Reconnect Attempts Before Suspending Impacted Service(s)' should be less than the value of 'Maximum Number of Reconnect Attempts'/'
|
|
|
Check if the value of number of reconnect attempts is less than the maximum number of reconnect attempts.
|
|
|
|
|
|
|
Error During Delete : Read-Only File/The resource " %1 " could not be deleted. Delete requires that " %2 " must be checked out. Check out the resource and try deleting again. You can select the resource to be checked out by clicking the "Go To Resource" button.
|
|
|
|
|
Error During Rename : Read-Only File/The resource " %1 " could not be renamed. Rename requires that " %2 " must be checked out. Check out the resource and try renaming again. You can select the resource to be checked out by clicking the "Go To Resource" button.
|
|
|
|
|
|
|
|
|
|
Message: "%1" was created during schema generation. Ensure that this resource "%2" is added to RCS and checked in. Click the Go To Resource button to select the resource
|
|
|
|
|
Transformation Plugin Warning/Warning: This adapter version does not support transformation plugin. The transformation plugin configuration will be ignored.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Select a view name using the FetchSchema option and check whether a valid database name has been specified in the instance level.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Do not configure more than one service in an instance if you are using an older version of the adapter.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Schema Generation Successful/RPC Operation Schema generated with name %1 Special characters in View Names will be removed when generating schemas
|
|
|
|
|
Error During Move|Paste : Read-Only File /The resource " %1 " could not be moved|pasted. Move|Paste requires the " %2 " must be checked out. Check out the resource and try move|paste again. You can select the resource to be checked out by clicking the "Go To Resource" button.
|
|
|
|
|
Error During Delete : Read-Only File/The resource " %1 " could not be deleted. Delete requires that " %2 " must be checked out. Check out the resource and try deleting again. You can select the resource to be checked out by clicking the "Go To Resource" button.
|
|
|
|
|
Error During Move:Read-Only File/The resource " %1 " could not be moved. Move requires that " %2 " must be checked out. Check out the resource and try moving again. You can select the resource to be checked out by clicking the "Go To Resource" button.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Warning/You have selected Subscriber Type: With Dynamic Login. Selecting this option will not allow you to change the subscriber type anymore. Press OK to confirm, cancel to revert.
|
|
|
Selecting this option will not allow you to change the subscriber type anymore. Make sure that you require this option.
|
|
Warning/You have selected Subscriber Type: With Dynamic Login. Selecting this option will not allow you to make further changes to Configuration form. Press OK to confirm, cancel to revert.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
------------ Exception in Trigger ------------ Trigger Name: %1 Trigger Subject: %2 Event Name: %3 Error Code: %4 Original Error: %5 ----------------------------------------------
|
|
|
|
|
------------ Exception in trigger ------------Trigger Name: %1 Trigger Subject: %2 Event Name: %3 This exception is most probably due to the fact that data has been sent using the same subject that this trigger is listening to but the format of the incoming data is not of the required format.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Attribute: [%1] has been defined as a single value field in the meta data and is not expecting a vector. Only the first element in the vector is taken as the value of this attribute
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This could be related to the fact that the subscriber instance has not been configured correctly in the EventRegistry to receive the incoming message or that the incoming message is faulty.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
LotusClientRequest: Parameter: [%1] is not a valid parameter for operation: [%2] of class: [%3], Parameter: [%4] is not a valid parameter for operation: [%5] of class: [%6]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This could be related to the fact that the subscriber instance has not been configured correctly in the EventRegistry to receive the incoming message or that the incoming message is faulty.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
For attachments in field: [%1] to be published by value, a ’files’ property for the attribute must be defined in the configuration. This property must have its value set to the actual suffix for all the attachments.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
An Exception has occurred in request document processing errorClass: LotusAdapterException errorCode: %1 errorText: %2 OriginalError: %3 severity: %4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-----------------EXCEPTION-------------------Request : [server: [%1] and operation: [%2]] Error Code : LotusServerWithReply_665 Error Text : An Exception has occurred in the processing of a server request Original Error: class: %3 text: %4
|
|
|
|
|
EXCEPTION :: Request: [server: [%1] and operation: [%2]] Error Code: LotusServerWithReply_665 Error Code: An Exception has occurred in the processing of a server request Original Error: class: %3 text: %4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Startup Error. Unable to create a connection with the target application %1 using connection parameters [ServerName= %2, UserName= %3] and the target application error is %4
|
|
|
|
|
|
|
|
|
|
|
|
|
Specify a different port as the port specified is already in use. Change the port in nsf also accordingly.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Subscription error. Subscription service %1 failed to deserialize the event received on subject %2 and SDK exception thrown is %3. The Repository URL is %4 and the Configuration URL is %5.
|
|
|
|
|
|
|
|
|
|
Subscription error. Subscription service %1 listening on subject %2 could not deserialize the inbound event to MbusinessDocument %3. The Repository URL is %4 and the Configuration URL is %5.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Subscription error. Subscription service %1 listening on subject %2 received event with missing attributes in class %3. The Repository URL is %4 and the Configuration URL is %5.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Subscription error. Subscription service %1 listening on subject %2 could not process the inbound event due to connection error %3 against target application %4 with parameters are [ServerName= %5, UserName= %6].
|
|
|
|
|
Subscription error. Subscription service %1 listening on subject %2 failed due to target application invocation error %3. Target application is %4. The target application specific commands and parameters are %5.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Publication error. Publication service %1 publishing on subject %2 encountered error %3 while trying to connect to target application %4. Connection parameters are [ServerName= %5, UserName= %6], the connection timeout is %7 millisecs, and the number of retry efforts is %8. Polling timeout is %9 millisecs.
|
|
|
|
|
Publication error. Publication service %1 with publication subject %2 encountered error %3 while trying to create publish event with schema %4. The Target application details are %5.
|
|
|
|
|
Publication error. Publication service %1 with publishing subject as %2 received event from target application %3. It failed while converting event to "Minstance" as it could not get the class description for %4. Repository URL is %5 and the Configuration URL is %6.
|
|
|
|
|
Publication error. Publication service %1 with publishing subject %2 received the event from target application %3. It failed while converting event to "Minstance" attribute %4 of class %5 is missing. Repository URL is %6 and the Configuration URL is %7.
|
|
|
|
|
Publication error. Publication service %1 with publication subject %2 received event from target application but could not create the business document %3. The target application details are [ServerName= %4, UserName= %5], the Repository URL is %6 and the Configuration URL is %7.
|
|
|
|
|
Publication error. Publication service %1 with publication subject %2 received SDK Exception %3 while converting the event received from target application to BusinessDocument. The exception occurred while setting the attribute %4 with value of %5 for Business Document %6. The target application details are %7, the Repository URL is %7 and Configuration URL is %8.
|
|
|
|
|
|
|
|
|
|
Request-Response error. Request-Response service %1 received unexpected null data in incoming request. Expects event %2. The Repository URL is %3 and the Configuration URL is %4.
|
|
|
|
|
Request-Response error. Request-Response service %1 failed to deserialize the received MServerRequest to MInstance: Received event = %2, SDK exception = %3. The Repository URL is %4 and the Configuration URL is %5.
|
|
|
|
|
Request-Response error. Error in incoming data for RPC service: %1. Not able to map incoming data to the business object schema: %2 configured at design-time. Invalid data type: %3 for attribute: %4.
|
|
|
|
|
|
|
|
|
|
Request-Response error. Connection error in invocation of RPC service:%1. Connection parameters are [Server Name: %2, database name:%3, user name:%4.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Request-Response Invocation error. Request-Response Invocation service %1 received event from target application %2. It failed while converting event to Request, as it could not get the class description for %3. Repository URL is %4 and the Configuration URL is %5.
|
|
|
|
|
Request-Response Invocation error. Request-Response Invocation service %1 received event from target application %2. It failed while converting event to Request, as it could not get the Operation description %3 in the class %4. Repository URL is %5 and the Configuration URL is %6.
|
|
|
|
|
Request-Response Invocation error. Request-Response Invocation service %1 received event from target application %2. It failed while converting event to Request. Repository URL is %4 and the Configuration URL is %5.
|
|
|
|
|
Request-Response Invocation error. Request-Response Invocation service %1 received event from target application %2. It failed while converting event to Request, as it cannot set Operation Parameter %3. Repository URL is %4 and the Configuration URL is %5.
|
|
|
|
|
Request-Response Invocation error. Request-Response Invocation service %1 received error while sending event over the wire. The Request-Response Invocation endpoint details are %2.
|
|
|
|
|
Request-Response Invocation error. Request-Response Invocation service %1 received error while requesting event over the wire. The Request-Response invocation endpoint details are %2.
|
|
|
|
|
Request-Response Invocation error. Request-Response Invocation service %1 received error while requesting event over the wire. The Request-Response Invocation endpoint details are %2.
|
|
|
|
|
Request-Response Invocation error. Request-Response Invocation service %1 received null reply while requesting event over the wire. The Request-Response Invocation endpoint details are %2.
|
|
|
|
|
Request-Response Invocation error. Request-Response Invocation service %1 received timeout error while requesting event over the wire. The Request-Response Invocation endpoint details are %2.
|
|
|
|
|
Request-Response Invocation error. Request-Response Invocation service %1 received error while processing reply message. The Request-Response Invocation endpoint details are %2.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Enter a sessionID corresponding to the user as whom you would like to perform the operation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Enter a sessionID corresponding to the user as whom you would like to perform the operation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[%1] Records retrieved using the Server Query (FTSearch), the parameters are: [%2] .............
|
|
|
|
|
NO Records retrieved using the Server Query (FTSearch), the parameters are: [%1] .............
|
|
|
|
|
|
|
|
Please check the adapter configuration settings.
|
|
Failed to get parameters when doing Server Query (FTSearch), the given parameters are: [%1]. Error Message: %2
|
|
|
Please check the adapter configuration settings related to FTSearch Parameters.
|
|
The FTSearch parameter is empty or not defined when doing Server Query (FTSearch).
|
|
|
Please check the adapter configuration settings related to FTSearch Parameters.
|
|
The number of FTSearch parameters is incorrect when doing Server Query (FTSearch).
|
|
|
Please check the adapter configuration settings related to FTSearch Parameters.
|
|
Invalidated FTSearch parameters when doing Server Query (FTSearch), the given parameters are [%1]. Error Message: %2
|
|
|
Please check the adapter configuration settings related to FTSearch Parameters.
|
|
FTSearch parameter 'query' is empty when doing Server Query (FTSearch).
|
|
|
Please check the adapter configuration settings related to FTSearch Parameters.
|
|
<description>the number [%1] FTSearch parameter is empty when doing Server Query (FTSearch).
|
|
|
Please check the adapter configuration settings related to FTSearch Parameters.
|
|
|
|
|
|
|
Processing the query using the FTSearch ...........
|
|
|
Indicates normal adapter operation. No action required.
|
|
|
|
|
Indicates normal adapter operation. No action required.
|
|
Set Update Mode to [%1] for [%2].
|
|
|
|
|
Disable key fields on Insert for [%1].
|
|
|
Indicates normal adapter operation. No action required.
|
|
Publishing for Insert Operation has happenned on source document, setting opcode to [%1].
|
|
|
|
|
|
|
|
|
|
Schema [%1] NOT supported. No Service can be found with the specified schema name in the coming message.
|
|
|
|
|
Failed to process the request. The tracking ID is : %1.
|
|
|
Indicates normal adapter operation. No action required.
|
|
Failed to Update the related Document fields where applicable. The error message is: %1
|
|
|
Please check whether the related document is existed.
|
|
|
|
|
|
|
FTSearch parameter 'query' has invalid symbol when doing Server Query (FTSearch).
|
|
|
Please check the adapter configuration settings related to FTSearch Parameters.
|
|
|
|
|
Please configure key fields at designer or set key fields (using the formKey attribute in the incoming message at run time).
|
|
Form [%1] NOT exists in Domino.
|
|
|
Please check whether the form exists in Domino.
|
|
Field [%1] NOT exists for Form [%2] in Domino.
|
|
|
Please check the whether the field for exists for the form in Domino.
|
|
FTSearch parameter ’query’ is specified by ending with an invalid symbol with when doing Server Query (FTSearch).
|
|
|
Please check the adapter configuration settings related to FTSearch Parameters.
|
|
FTSearch parameter ’query’ is specified by ending with an invalid symbol with when doing Server Query (FTSearch).
|
|
|
Please check the adapter configuration settings related to FTSearch Parameters.
|
|
Schema NOT defined correctly for [%1].
|
|
|
Please check the adapter configuration settings related to FTSearch Parameters.
|
|
Received a New Request. The tracking ID is: %1.
|
|
|
|
|
Message/Design-Time Test Connection is successful.
|
|
|
|
|
Field:Max No of Retries/Palette error. The Maximum Number of Retries must be an integer greater than or equal to -1, and less than or equal to 65535.
|
|
|
|
|
Connection Not Established/Please verify whether the connection with the Database has been established.
|
|
|
Establish connection with the DataBase by clicking the button "Connect" in adapter instance Design-time Connection tab.
|
|
View Not Avaialble/The View '%1' doesn't exist.
|
|
|
|
|
View Not Given/Palette error. Please give a valid View Name or select a View name using 'Fetch Schemas'".
|
|
|
|
|
Form Not Given/Palette error. Please give a valid Form Name or select a Form name using 'Fetch Schemas'.
|
|
|
|
|
Form Not Avaialble/The Form '%1' doesn't exist.
|
|
|
|
|
Message/RPC Result Schema regenerated successfully by the form '%1'.\nPlease refer to the 'View Result Schema' tab for the details.
|
|
|
|
|
Message/The Request Name '%1' of the Target doesn't equals the service name '%2'.\nPlease click the "Read Target" button to read the Proper Target.
|
|
|
|
|
MValid Field Value Required/Please input a valid value for '%.
|
|
|
|
|
Fatal Error/Error in creating staticmetadata classes and sequences.
|
|
|
|
|
Cannot Get Value From the Field/Cannot not get the value of '%.
|
|
|
|
|
Field:No Retries Before Suspend/Palette error. The Number of Publication Service Threads must be greater than or equal to 0, and less than or equal to 65535.
|
|
|
|
|
Field: %1 /Palette error. The Input of the field must be integer greater than or equal to 0, and less than or equal to 65535.
|
|
|
|
|
Connection Failed/Design-Time Connection Failed, Please Check the Connection Parameters.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|