1003 | System property {0} is invalid: {1}. To correct the property, go to the TN Properties page of the WmTN package in the Integration Server Administrator, or edit the ''packagesWmTNconfigproperties.cnf'' file. |
Explanation |
The system property provided for Trading Networks is invalid. |
Action |
Correct the property in the Configure Properties page in My webMethods, or edit the ‘IntegrationServer_directory\packages\WmTN\config\properties.cnf'' file. |
1008 | "{0}" is required. |
Explanation |
Required input value is missing. |
Action |
Provide value for required input fields and try again. |
1027 | You have attempted to use a feature that is restricted by your license. To be able to use all product features, please contact webMethods or your webMethods OEM solution provider to upgrade to an unrestricted version of Trading Networks. |
Explanation |
User not allowed to create doctypes, attempt failed. |
Action |
To be able to use all product features, please contact Software AG Global Support to upgrade to an unrestricted version of Trading Networks. |
1035 | User Status value(s) {0} already exist. |
1046 | Error registering TN''s XML content handler. |
Explanation |
Error while registering content handler for "text/xml". |
Action |
Contact Software AG Global Support. |
1119 | Encountered error while creating TN document |
1157 | New verify certificate set not added. |
Explanation |
In webMethods Trading Networks, if a verify certificate set is not added to a partner, this error shows up. |
Action |
Add the very certificate set to the partner and try again. |
1158 | New verify certificate set not updated. |
Explanation |
In webMethods Trading Networks, if the new verify certificate set for a partner is not updated, this error shows up. |
Action |
Ensure that the new verify certifcicate set for a partner is updated and try again. |
1160 | Asset already exists in Trading Networks |
Class | W |
Explanation |
The asset selected for import already exists in Trading Networks. |
Action |
To overwrite the existing asset with the one in the imported file, select the "force" option during the import process. |
1161 | An error occurred while retrieving package names. |
Class | E |
Explanation |
My webMethods encountered an error while displaying the names of Integration Server packages. |
Action |
Take appropriate action to resolve the problem described in the exception and try to perform the action again. |
1162 | All processing rules were imported successfully. Processing rules that existed before the import were removed. |
Class | W |
Explanation |
All the processing rules present in the import file were added to the Trading Networks database. All processing rules that existed before the import process were removed from the database. This happens when the Replace Rule List option is selected during the import of Trading Networks data. |
1166 | Unable to delete doc type. There are some activity logs associated with this doc type. Either delete the associated activity logs or run this service again with "deleteLogs=true" to have them deleted automatically. |
Explanation |
Unable to delete doc type because there are some activity logs associated with this doc type. |
Action |
Either delete the associated activity logs or run this service again with "deleteLogs=true" to have them deleted automatically. |
1170 | Unable to import processing rule {0}. Document type(s) used in the processing rule is not defined. |
1171 | inserted |
1172 | updated |
1173 | deleted |
1174 | Inserted. |
1175 | Updated. |
1176 | Deleted. |
1177 | Invalid status provided. Provide the proper status. |
1178 | Manage Export Import |
1179 | The {0} you are trying to save has been modified by another user. To ensure that you are using the latest version, cancel your changes and reopen the {1}. Modify the latest version and save your changes |
1180 | Invalid "{0}". It should not start with "=". |
1181 | No Validator found for "{0}" Service: "{0}". |
1203 | Error retrieving certificates for keystore alias {0} and key alias {1}. Check the keystore configuration in Integration Server. |
Class | E |
Explanation |
The keystore was modified or deleted in Integration Server, which caused the keystore mapping in Trading Networks to break. |
Action |
Check the keystore configuration in Integration Server. If the keystore does not exist in Integration Server, create the keystore. If the keystore mapping in Trading Networks is incorrect, select the correct keystore alias and key name for the certificate. |
1204 | Error retrieving keystore aliases. |
Class | E |
Explanation |
Trading Networks could not retrieve the keystore from Integration Server. |
Action |
Check the keystore configuration in Integration Server. If the keystore does not exist in Integration Server, ask the Integration Server administrator to create the keystore. |
1205 | Error retrieving key aliases for the keystore alias {0}. |
Class | E |
Explanation |
Trading Networks could not retrieve the keystore from Integration Server. |
Action |
Check the keystore configuration in Integration Server. If the keystore does not exist in Integration Server, ask the Integration Server administrator to create the keystore. |
19000 | Invalid facet provided to API - {0}. |
19001 | Error occurred while initializing Trading Networks charts during initialization of Trading Networks. |
Class | E |
Explanation |
Trading Networks charts could not be initialized due to an error faced during startup. |
Action |
Restart Trading Networks. |
19002 | Error occurred while initializing Trading Networks dashboarding store during initialization of Trading Networks. |
Class | E |
Explanation |
Trading Networks dashboarding store could not be initialized due to an error faced during startup. |
Action |
Restart Trading Networks. |
19003 | Hour value {0} is not in range. |
19004 | Dashboarding API inputs not valid. |
19005 | Error occurred during Analytics API call. |
Class | E |
Explanation |
An error occurred during Analytics API call. |
Action |
Check the Trading Networks logs for the cause of the failure and if required, contact your system administrator. |
19006 | afterDays parameter cannot be null. |
Class | E |
Explanation |
afterDays parameter cannot be null. |
Action |
Supply a value for afterDays parameter. |
19007 | afterDays parameter should be a positive integer. |
Class | E |
Explanation |
afterDays parameter provided is not a positive integer. |
Action |
Supply a valid value for afterDays parameter. The value must be a positive integer. |
19008 | batchSize parameter should be a positive integer. |
19010 | API error |
19011 | Transaction data {0} written to dashboarding table |
2017 | Could not delete field definition |
2020 | Error occurred while publishing event messages to ERF. |
Class | E |
Explanation |
An error occurred while publishing event messages to NERV. |
Action |
Check the Trading Networks logs for the cause of the failure and if required, contact your system administrator. |
2021 | Successfully published event message of type {0} to ERF. |
2023 | Error redefining type {0} ({1}) |
Explanation |
Error while updating the document type. |
Action |
The exception is in the full message. Take appropriate action to resolve the problem described in the exception. |
2061 | Error initializing type cache. |
Explanation |
There may have been an SQLException that prevented the initialization of the document type cache. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
2069 | Error while defining type {0} ({1}). |
Explanation |
The error encountered while defining the document type may be due to an SQLException or to a missing mandatory field. |
Action |
Look at the associated error message or stack trace in the logs and take appropriate action. |
2103 | MODIFY AND RESUBMIT |
2105 | Invalid input. Provide a value from the configured list of User Status values. |
2120 | Error initializing attribute cache. |
Explanation |
An SQLException may have prevented the attribute cache from being initialized. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
2174 | Unable to import init.xml due to exception message: {0}. Manually import init.xml as described in the Installation Guide. |
Explanation |
An exception occurred while importing init.xml, as described in the message. |
Action |
Manually import init.xml as described in the Installation Guide. |
2200...0 | Error encountered while reading USER status from the database. Exception message: {0}. |
Explanation |
Encountered SQLException while reading user status from database. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
2262 | Processing of invitation failed. {0} |
2263 | User not created for the partner. |
2264 | Updating the partner status to Invited has failed. |
2265 | Error occurred while changing the status of the invitations. |
2266 | Error occurred while changing the status of the following invitation: {0}. |
2267 | Error occurred while changing the status of the following archival service: {0}. |
2268 | Error occurred while changing the status of the archival services. |
2269 | Error occurred while changing the status of the invitations.The status should be either {0} or {1}. |
2270 | Error occurred while changing the status of the archival services.The status should be either {0} or {1}. |
2271 | Error occurred while changing the status of the queues.The status should be either {0}, {1}, {2}, or {3}. |
2272 | Error occurred while changing the status of the following invitation: {0}.Check the invite and provide all the necessary details. |
2303 | Exception encountered while getting TN assets dependency. |
Explanation |
In the webMethods Trading Networks Export Import feature using MWS, when webMethods Trading Networks fails to get the dependency of the asset type during export, this exception is thrown. |
Action |
You need to select the dependent asset and perform the export again. |
2304 | Exception encountered while exporting TN assets.The exception message is : {0}. |
Explanation |
In the webMethods Trading Networks Export Import feature using MWS, when webMethods Trading Networks fails to get the asset data during export, this exception is thrown. |
Action |
Contact your system administrator. |
2305 | Exception encountered while importing TN assets.The exception message is : {0}. |
Explanation |
In the webMethods Trading Networks Import feature using MWS, when webMethods Trading Networks fails to import data, this exception is thrown. |
Action |
Contact your system administrator. |
2306 | The import data file name is null or empty. |
Explanation |
In webMethods Trading Networks, when you try to import data and the import data file name is null or empty, this error is thrown. |
Action |
Import the data again after adding the import data file. |
2307 | The import data file {0} does not exist. |
Explanation |
In webMethods Trading Networks, when you try to import a data file but the file does not exist, this error is thrown. |
Action |
Ensure that the file is available and try again. |
2308 | The import file does not contain valid data. |
Explanation |
In webMethods Trading Networks, when you try to import a file and it does not contain valid data according to the type format, this error is thrown. |
Action |
Add a file that contains valid data according to the type format and try to import it again. |
24001 | Error occurred for the following Document ID while writing to TRANSACTIONSUMMARYDATA table:{0}. |
Class | E |
Explanation |
Writing to TransactionSummaryData table might fail due to many reasons. One reason is when the Trading Networks database is down. |
Action |
Check the Integration Server logs for the cause of the failure and if required, contact your system administrator. |
24002 | Volume value summary data for the following Document ID was successfully written to CUSTOMATTRIBUTEVOLUMEVALUE table: {0}. |
24003 | Error occurred for the following Document ID while writing to CUSTOMATTRIBUTEVOLUMEVALUE table:{0}. |
24004 | Success and failed transactions summary data for the following Document ID was successfully written to TRANSACTIONSUCCESSFAILEDDATA and SUCCESSFAILEDCHARTDOCIDMAP tables: {0}. |
24005 | Error occurred for the following Document ID while writing to TRANSACTIONSUCCESSFAILEDDATA and SUCCESSFAILEDCHARTDOCIDMAP tables:{0}. |
24006 | Success and failed transactions summary data for the following Document ID was successfully updated in TRANSACTIONSUCCESSFAILEDDATA and SUCCESSFAILEDCHARTDOCIDMAP tables: {0}. |
24007 | Error occurred for the following Document ID while updating TRANSACTIONSUCCESSFAILEDDATA and SUCCESSFAILEDCHARTDOCIDMAP tables:{0}. |
24008 | Late FA summary data for the following Document ID was successfully written to TRANSACTIONLATEFADATA table: {0}. |
24009 | Error occurred for the following Document ID while writing to TRANSACTIONLATEFADATA table:{0}. |
24010 | The following custom class required to filter run-time events of type Document Attribute Added based on event's attribute name was not found in classpath: {0} |
24011 | The following error occurred while trying to filter run-time events of type Document Attribute Added: {0} |
24500 | Exception {0} occured during execution of event processor {1} |
25002 | Error occurred while subscribing to {0} run-time event. The dashboards may not display any data. |
Class | W |
Explanation |
Event processor did not subscribe to the run-time event type due to one of the following reasons:- Trading Networks NERV custom bundle was not copied to the NERV config bundles location.- Universal Messaging server was not up and running. |
Action |
Ensure the following:- If you are using Trading Networks NERV custom bundle, ensure to copy the bundle to the NERV config bundles location. Refer to 9.7 webMethods Trading Networks Administrators guide for details.- If you are using Universal Messaging, ensure the server is up and running. |
25003 | Error occurred while unsubscribing from {0} run-time event. |
Class | W |
Explanation |
Event processor did not unsubscribe from the run-time event type due to one of the following reasons:- Event processor did not subscribe to the run-time event type successfully.- Universal Messaging server was down after the processor subscribed to the run-time event type. |
Action |
Ensure the following:- If the event processor subscribed to the run-time event type successfully.- If you are using Universal Messaging, ensure the server is up and running at all times. |
25500 | The following error occurred while suspending or unsuspending document delivery for a partner: {2}. The PartnerId is {0}, and the Id of the schedule is {1}. |
25501 | Error occurred while adding a delivery suspension schedule. |
25502 | Error occurred while updating a delivery suspension schedule. |
25503 | Error occurred while viewing a delivery suspension schedule. |
25504 | Error occurred while deleting a delivery suspension schedule. |
25505 | Error occurred while activating a delivery suspension schedule. |
25506 | Error occurred while deactivating a delivery suspension schedule. |
25507 | Error occurred while changing the Suspension Status of a delivery suspension schedule. |
25508 | Error occurred while checking the validity of a delivery suspension schedule. |
25509 | Error occurred while checking or unchecking the Suspend Delivery checkbox. |
25510 | An exception occurred while switching a deliverySuspendData validity to {0}. |
25511 | An exception occurred while selecting invalid status deliverySuspendData. |
25512 | An exception occurred while selecting invalid status deliverySuspendData. |
26000 | Error occurred while adding a delivery suspension schedule to Integration Server. |
26001 | Error occurred while updating a delivery suspension schedule on Integration Server. |
26002 | Error occurred while viewing a delivery suspension schedule on Integration Server. |
26003 | Error occurred while cancelling a delivery suspension schedule on Integration Server. |
26004 | Error occurred on Integration Server while changing the status of a delivery suspension schedule to inactive. |
26005 | Error occurred on Integration Server while changing the status of a delivery suspension schedule to active. |
26006 | Successfully added the following delivery suspension schedule to Integration Server: {0} |
26007 | Successfully updated the following delivery suspension schedule on Integration Server: {0} |
26008 | Successfully fetched the following delivery suspension schedule from Integration Server: {0} |
26009 | Successfully cancelled the following delivery suspension schedule on Integration Server: {0} |
26010 | Successfully suspended the following delivery suspension schedule on Integration Server: {0} |
26011 | Successfully resumed the following delivery suspension schedule on Integration Server: {0} |
26012 | Error occurred on Integration Server while checking for the existence of a delivery suspension schedule. |
26013 | Error occurred while parsing the date and time of a delivery suspension schedule. |
26014 | Error invoking remote service - {0} for alias - {1}. |
26015 | Error invoking local service - {0}. |
26016 | Error occured retriving VFS list from ActiveTransfer aliases |
26017 | ActiveTransfer service is not executable, please check alias - {0} is accessible or not. |
26018 | Large Document Delivery to remote ActiveTransfer not supported |
26019 | View Transaction Settings |
26020 | Edit Transaction Settings |
26021 | Unable to connect to ActiveTransfer. Contact your System Administrator |
3011 | (username={0})already exists.No new account created.Mapping done. |
Explanation |
While creating a partner account, Trading Networks found an existing user with the same name. No new account was created. Mapping was completed.. |
Action |
Provide a unique name and try again. |
3012 | Encountered error while enabling the {0} package. |
Explanation |
This error shows up when trying to enable the WmTN package. |
Action |
Contact your system administrator. |
3013 | Encountered error while disabling the {0} package. |
Explanation |
This error shows up while trying to disable the WmTN package. |
Action |
Contact your system administrator. |
3017 | An error occurred while trying to insert document (doc id = {0}, sender id = {1}) into the database. |
Explanation |
Exception occurred during inserting the documentinto the database, possibly due to a database or usage error. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
3023 | No such documents: {0}. |
3024 | Could not instantiate documents {0}. |
3025 | Error occurred while reinitializing Trading Networks JDBC connection pool in Integration Server. |
Class | E |
Explanation |
Trading Networks reinitializes the JDBC connection pool when a connection error occurs. This reinitialization disconnects all connections to the Trading Networks database. An error occurred during the reinitialization. |
Action |
Use the Integration Server Administrator JDBC Pools page to reinitialize the Trading Networks JDBC connection pool. |
3027 | Exception in finding database specific Class: {0} |
3028 | TPA with id {0} is locked |
3068 | Error while persisting queue. For details check the full stack trace. |
Explanation |
In webMethods Trading Networks, while registering a queue, if there is anyu error in scheduling the queue, this error is thrown. |
Action |
Check the full stack trace or contact your system administrator. |
3069 | Error occurred while changing the status of the following queue: {0}. |
3070 | Error occurred while changing the status of the queues. |
3100 | Exception occured while clearing TNASSET_READTIMEKEEPER table. |
3243 | Cannot process message that is not javax.mail.internet.MimeMessage or javax.mail.internet.MimeBodyPart. Current message is: {0} |
Explanation |
Cannot parse the message as it is not a javax.mail.internet.MimeMessage or javax.mail.internet.MimeBodyPart. |
Action |
Check the error message and take action as appropriate. |
4000 | Successfully saved the {1} delivery suspension schedule to Trading Networks database. The Id of the schedule is {0}. |
4001 | Successfully updated the {1} delivery suspension schedule on Trading Networks database. The Id of the schedule is {0}. |
4002 | Successfully fetched the following delivery suspension schedule from Trading Networks database: {0} |
4003 | Successfully deleted the following delivery suspension schedule from Trading Networks database: {0} |
4004 | Successfully changed the status of the following delivery suspension schedule to {1} on Trading Networks database: {0} |
4005 | Successfully changed the suspension status of the following delivery suspension schedule to {1} on Trading Networks database: {0} |
4006 | Successfully fetched the delivery suspension schedule with PartnerId {0} from Trading Networks database. |
4007 | A delivery suspension schedule with the following name already exists in Trading Networks database: {0} |
4008 | Error occured while executing Stored Procedures |
4009 | Error occurred while creating jdbc pool for tenantId: {0} and stageId: {1}. The exception message is : {2}. |
4010 | No jobs queued on queue {0} |
4024 | Invalid Receiver ID |
Explanation |
In webMethods Trading Networks, while setting the BizDoc envelope attribute, if the receiver ID is not a valid partner ID, this error is thrown. |
Action |
Enter a valid partner ID (for a receiver ID) and try again. |
4168 | Exception encountered while listing all the processing rules. |
Explanation |
Encountered an exception while getting the list of rules from the cache. Either the cache is not updated with data, or there is some exception in the database. |
Action |
The details of the exception is in the full message. Take appropriate action to resolve the problem described in the exception message. |
4169 | Access denied, as the User "{0}" does not have the privilege to {1} {2}. |
Explanation |
You do not have the required permission to take this action on the processing rule. |
Action |
Request that the Integration Server administrator assign the required permission. |
4170 | Error while recognizing the document. |
Explanation |
Error encountered while recognizing the document. The document may be corrupted. |
Action |
Check if the document is a valid XML document and not a corrupt document. |
4177 | {0} contacts deleted with ContactID {1}. |
Explanation |
Encountered data inconsistency issue while contact deletion. Expected exactly one matching contact. |
Action |
Contact Software AG Global Support. |
4178 | {0} addresses deleted with AddressID {1}. |
Explanation |
Encountered data inconsistency issue while address deletion. Expected exactly one matching address. |
Action |
Contact Software AG Global Support. |
4179 | {0} connections deleted with ID {1}. |
Explanation |
Encountered data inconsistency issue while destination deletion. Expected exactly one matching destination. |
Action |
Contact Software AG Global Support. |
4209 | Error encountered while getting the host ID |
Explanation |
The Trading Networks profile cache might be corrupted. |
Action |
The details of the exception are in the full message. Take appropriate action to resolve the problem described in the exception message. |
4210 | Error encountered while getting all the Processing Rule matches for the document. |
Explanation |
Encountered exception while retrieving rules from cache. The cache might not be updated. |
Action |
The details of the exception are in the full message. Take appropriate action to resolve the problem described in the exception message. Reload the WmTNWeb package. |
4211 | Error encountered while getting all the Delivery Services. |
Explanation |
Encountered exception while retrieving delivery services from the database. |
Action |
The details of the exception are in the full message. Take appropriate action to resolve the problem described in the exception message. |
4212 | Error encountered while getting RuleName with the name - {0}. |
Explanation |
The rule may have been deleted by someone in a different session. |
Action |
Refresh the rule cache by executing the search again. |
4213 | Error encountered while getting Last Change ID. |
Explanation |
This may be due to an exception while fetching the Last Change ID from the database. |
Action |
The details of the exception are in the full message. Take appropriate action to resolve the problem described in the exception message. |
4214 | Error encountered while getting Processing Rule with ID - {0}. |
Explanation |
The rule may have been deleted by someone in a different session. |
Action |
Refresh the rule cache by running the search again. |
4215 | Error encountered while changing the ordinality of the Processing Rule. |
Explanation |
Changing the ordering of the processing rules in another session might have caused an error while validating or updating the ordinal numbering in the database. |
Action |
Refresh the rule cache by executing the search again. |
4216 | Error encountered while deleting the processing rules. |
Explanation |
The rule might have been deleted by someone in a different session. |
Action |
Refresh the rule cache by executing the search again. |
4217 | Error encountered while updating the processing rule with Rule Name - {0}. |
Explanation |
The rule might have been deleted by someone in a different session. |
Action |
Refresh the rule cache by executing the search again. |
4218 | Error encountered while creating the processing rule with Rule Name - {0}. |
Explanation |
Error encountered while inserting the rule into the database. |
Action |
The details of the exception are in the full message. Take appropriate action to resolve the problem described in the exception message. |
4219 | Error encountered while querying the processing rules. |
Explanation |
The query would have failed while picking the rules. Check the database actions. |
Action |
The details of the exception are in the full message. Take appropriate action to resolve the problem described in the exception message. |
4220 | Access denied, as the User "{0}" does not have the permission to {1} processing rule. |
Explanation |
You do not have the permission to do the necessary action on the processing rule. |
Action |
Request that the Integration Server administrator assign the required permission. |
4221 | Access denied, as the User "{0}" does not have the permission to {1} processing rule - "{2}". |
Explanation |
You do not have the permission to do the necessary action on the processing rule. |
Action |
Request that the Integration Server administrator assign the required permission. |
4228 | Exception while changing the processing rule status. |
Explanation |
The rule might have been deleted by someone in a different session. |
Action |
Refresh the rule cache by executing the search again. |
4237 | Error encountered while getting the profiles associated with Profile Group. |
Explanation |
There might be a database error while retrieving the profile groups. |
Action |
The details of the exception are in the full message. Take appropriate action to resolve the problem described in the exception message. |
4238 | Access denied, as the User "{0}" does not have the permission to {1} processing rule - "{2}". |
Explanation |
You do not have the permission to do the necessary action on the processing rule. |
Action |
Request that the Integration Server administrator assign the required permission. |
4241 | Processing rule "{0}" change status failed. Processing rule update collision detected. This rule has been modified by another user. Refresh your rule list and retry this operation. |
Class | E |
Explanation |
In webMethods Trading Networks, while changing the status of a processing rule, if it is modified by another user, this error is thrown. |
Action |
Refresh your rule list and try again. |
4247 | Exception encountered while moving the processing rule. Invalid Ordinal given in Select Location. |
Class | E |
Explanation |
In webMethods Trading Networks, while moving the processing rule, if an invalid ordinal location is specified, this error is thrown. |
Action |
Specify a valid ordinal location and try again. |
4258 | Error encountered while creating the processing rule with Rule Name - "{0}". Rule name already exists. Change the name and save again. |
Class | E |
Explanation |
In webMethods Trading Networks, while creating a processing rule, if the rule name already exists, this error is thrown. |
Action |
Ensure to give a unique processing rule name and try again. |
4274 | Error encountered while querying for the delivery queues. |
Class | E |
Explanation |
In webMethods Trading Networks, if any error occurs while retrieving registered queues, this error is thrown. |
Action |
Contact your system administrator. |
4305 | The following sender(s) and receiver(s) configured in the processing rule do not exist in the system. Sender(s):"{0}" Receiver(s):"{1}" |
Class | E |
Explanation |
An error occurred while trying to create or update a processing rule with senders and receivers that do not exist in Trading Networks. |
Action |
Ensure the senders and receivers are valid. |
4306 | The following sender(s) configured in the processing rule do not exist in the system: "{0}" |
Class | E |
Explanation |
An error occurred while trying to create or update a processing rule with senders that do not exist in Trading Networks. |
Action |
Ensure the senders are valid. |
4307 | The following receiver(s) configured in the processing rule do not exist in the system: "{0}" |
Class | E |
Explanation |
An error occurred while trying to create or update a processing rule with receivers that do not exist in Trading Networks. |
Action |
Ensure the receivers are valid. |
4415 | IS DocType signature (ISDocType ={0}) is invalid. Provide a valid IS DocType signature. |
Explanation |
Exception encountered while loading the corresponding IS docType. |
Action |
Check whether the namespace of the corresponding IS docType is correct. |
4416 | Cannot add extended field definition. Extended field with name "{0}" already exists. |
Explanation |
Extended field with same name already exists. |
Action |
Supply different name for extended field. |
4417 | Cannot update extended field definition. Extended field with name "{0}" already exists. |
Explanation |
Extended field with same name already exists. |
Action |
Supply a different name for the extended field. |
4422 | A problem was encountered deleting the field defintion. |
4423 | Created New Permission "{0}" for role "{1}". |
4424 | Deleted Permission "{0}" for role "{1}". |
4429 | Importing a profile for {0} (id={1}), which is marked as "My Enterprise", but it has different ID than the existing My Enterprise profile for this Trading Network. Cannot change the identity of the My Enterprise profile. |
Class | E |
Explanation |
You are attempting to import a partner profile marked as "My Enterprise." However, the target Trading Networks server already contains a My Enterprise profile, with a different ID. The existing My Enterprise cannot be overwritten because the IDs are different. |
Action |
Import the partner data without selecting the "My Enterprise" profile. |
4430 | Importing a profile for {0} (id={1}), which is marked as "My Enterprise". A "My Enterprise" profile already exists for this Trading Network. If you want to update it, use the Force option. |
Class | E |
Explanation |
You are attempting to import a partner profile marked as "My Enterprise" without using the "Force import" option; however, the target Trading Networks server already contains a My Enterprise profile. |
Action |
Import the partner data using the "Force import" option. |
4431 | Error encountered while adding DLS artifacts with name {0}. The permissions for role {1} is null or empty. |
Class | E |
Explanation |
You are attempting to import or add a DLS dataset, but the dataset does not contain any permissions. |
Action |
If you are adding a DLS dataset, specify the required permissions for the dataset. If you are importing a DLS dataset, make sure that the data is correct. |
4432 | Error encountered while adding DLS artifacts with name {0}. The role name is null or empty. |
Explanation |
You are attempting to import or add a DLS dataset, but the dataset does not contain any roles. |
Action |
If you are adding a DLS dataset, specify the required roles for the dataset. If you are importing a DLS dataset, make sure that the data is correct. |
4433 | Error encountered while adding DLS artifacts with name {0}. The partner with name {1} is referenced in DLS data, but this partner does not exist on your Trading Networks system. |
Class | E |
Explanation |
You are attempting to import or add a DLS dataset, but the partner specified in the dataset is not present in the Trading Networks database. |
Action |
If this happens while importing a DLS dataset, make sure that the dependent partner profile is also imported along with the DLS dataset. |
4434 | Error encountered while adding DLS artifacts with name {0}. The document type with name {1} is referenced in DLS data, but this document type does not exist on your Trading Networks system. |
Class | E |
Explanation |
You are attempting to import or add a DLS dataset, but the document type specified in the dataset is not present in the Trading Networks database. |
Action |
If this happens while importing a DLS dataset, make sure that the dependent document type is also imported along with the DLS dataset. |
4435 | Error encountered while adding DLS artifacts with name {0}. The processing rule with name {1} is referenced in DLS data, but this processing rule does not exist on your Trading Networks system. |
Class | E |
Explanation |
You are attempting to import or add a DLS dataset, but the processing rule specified in the dataset is not present in the Trading Networks database. |
Action |
If this happens while importing a DLS dataset, make sure that the dependent processing rule is also imported along with the DLS dataset. |
4436 | A deleted profile with the same internal id already exists. Unable to recreate a deleted profile. |
Class | W |
Explanation |
You are attempting to import a partner. However, the target Trading Networks server already contains a deleted partner with the same ID. |
Action |
Import the partner using the "Force import" option. |
4461 | Profile has errors. |
Explanation |
In webMethods Trading Networks, while adding a profile information, if the profile has any error, this error message is displayed. |
Action |
Contact your system administrator. |
4464 | Attempt to import extended field "{0}" associated with the fieldgroup "{1}" failed. The extended field "{0}" associated with the fieldgroup "{1}" is not defined on your Trading Networks system. |
Explanation |
This error occured because the extended field associated with the fieldgroup is not defined on your Trading Networks system. |
Action |
Define the extended field associated with the fieldgroup on your Trading Networks system and try again. |
4467 | Administering Partner Onboarding |
4468 | The invitation with id "{0}" does not exist. |
4469 | Error occurred while changing the status of the partners. |
4470 | Error occurred while changing the status of the following partner: {0}. |
4471 | Partner Delivery Suspended |
4472 | Partner Delivery Unsuspended |
4473 | Error encountered deleting contact (contactID={0}). |
4474 | Error encountered deleting address (addressID={0}). |
4500 | A database error occurred while deleting a Binary Type. |
Explanation |
In webMethods Trading Networks, at the time of deleting a binary type, if there is a database error, then this error shows up. |
Action |
Contact your system administrator. |
5030 | Exception encountered while adding a new TPA. |
Explanation |
Encountered an exception while writing the TPA to the database. There might be an SQL Exception while writing to the database or some of the constraints were missed out. |
Action |
The details of the exception are in the full message. Take appropriate action to resolve the problem described in the exception message. |
5031 | Exception encountered while updating the TPA. |
Explanation |
Encountered an exception while writing the TPA to the database. There might be an SQL Exception while writing to the database or some of the constraints were missed out. |
Action |
The details of the exception are in the full message. Take appropriate action to resolve the problem described in the exception message. |
5032 | Exception encountered while fetching the TPA. |
Explanation |
Encountered an exception while fetching the TPA from the database. There might be an SQL Exception while retrieving the TPA from the database or there are TPA caching errors. |
Action |
The details of the exception are in the full message. Take appropriate action to resolve the problem described in the exception message. |
5033 | Exception encountered while deleting the TPA. |
Explanation |
Encountered an exception while deleting the TPA from the database. This may be bacause of SQL Exception during writing to database or may be due to removing the TPA from Cache. |
Action |
The details of the exception are in the full message. Take appropriate action to resolve the problem described in the exception message. |
5034 | No initial value created for tpaData. |
Explanation |
The tpaData parameter was not created. A wrong service output might have caused the issue. |
Action |
Check if the initService defined in the TPA is correct and generates the correct output. The output of the TPA initService must generate an IData for the "tpaData" parameter. |
5036 | An exception occurred while retrieving TPA names. |
Class | E |
Explanation |
My webMethods encountered an error while displaying the TPA names. |
Action |
Take appropriate action to resolve the problem described in the exception and try to perform the action again. |
5037 | An exception occurred while executing the validation service. |
Class | E |
Explanation |
My webMethods encountered an error while validating TPA data on the Trading Partner Agreement Details page. |
Action |
Take appropriate action to resolve the problem described in the exception and try to perform the action again. |
5038 | No output data was returned by the validation service. |
Explanation |
The validation service does not conform to the format of the TPA validation service output record "wm.tn.rec:TPAValidateServiceOutput." |
Action |
Correct the service to pass the output in the format described by the output record "wm.tn.rec:TPAValidateServiceOutput." |
5042 | Queue |
5043 | TPA updated on {0} at {1} |
5096 | Document delivered via ActiveTransfer. VFS Path: {0} ActiveTransfer Transaction ID: {1} |
6006 | Export file location not specified |
Explanation |
Trading Networks is not able to find the export directory location. |
Action |
Specify the export directory location in the tn.deployer.export.dir TN property |
6011 | Asset deletion failed - roll back to previous state failed. |
Explanation |
Trading Networks is not able to delete the asset, because of which rollback to the previous state has failed. |
Action |
Contact your system administrator. |
6013 | The binary file is either corrupt or not as expected. |
Explanation |
The binary file provided for deployment is not valid. |
Action |
Provide a valid binary file. |
6014 | The artifact ID is not available in the corresponding artifact properties file. |
Explanation |
Trading Networks needs the artifact ID for installing the artifacts for deployment. This is missing from the artifact properties file. |
Action |
Provide the artifact ID in the artifact properties file or recreate the artifact ID. |
6015 | checkpointId is required. |
Explanation |
Trading Networks needs the checkpoint ID as input for the execution of the checkpoint service. This is missing. |
Action |
Add the checkpointId in the checkpoint service. |
6016 | Delete Archive Schedule failed during rollback. |
Explanation |
Trading Networks may need to delete the archive schedule during deployment roll back. This deletion of archive schedule has failed during rollback. |
Action |
Contact your system administrator. |
6017 | Delete Private Queue for Partner failed during rollback. |
Explanation |
Trading Networks may need to delete the private queue for Partner during deployment roll back. This deletion of private queue has failed during rollback. |
Action |
Contact your system administrator. |
6018 | Delete Public Queue failed during rollback. |
Explanation |
Trading Networks may need to delete the public queue during deployment roll back. The deletion of public has failed during rollback. |
Action |
Contact your system administrator. |
6024 | The ProductNamespace "{0}" is not specific to Trading Networks.The expected ProductNamespace is "TN". |
Explanation |
During deployment, a ProductNamespace, which needs to be passed to the service, is required. The expected ProductNamespace specific to Trading Networks that needs to be passed to the service is "TN". |
Action |
Specify the ProductNamespace as TN. |
6025 | The runtime type is not specific to Trading Networks. |
Explanation |
The Ping service requires type as input. The value of "type" for Trading Networks is TN. |
Action |
Specify type as TN. |
6026 | deploymentId is required. |
Explanation |
The deleteDeliveredArtifacts and activateArtifacts services need the deploymentId. This is not specified. |
Action |
Specify the deploymentId as the service input. |
6030 | assetIdentifier(s) is required. |
Explanation |
The Trading Networks assets that are to be deleted has not been provided. |
Action |
Provide the Trading Networks assets. |
6032 | Asset deletion has failed. |
Explanation |
If the deletion of a Trading Networks asset has failed, this message is displayed. |
Action |
Based on the additional details in the message, you need to fix the issue and try to delete the Trading Networks asset again. |
6034 | Trading Networks is not able to retrieve the asset references for the asset: "{0}" of asset type: "{1}". "{2}" |
Explanation |
Trading Networks is not able to retrieve the asset references for the specified asset due to an unexpected error. |
Action |
Try to delete the asset again. If it still does not go through, contact your system administrator. |
6056 | Access denied. User "{0}" does not have the permission to {1} {2}, for Sender "{3}" and Receiver "{4}". |
Explanation |
User does not have the permission required to perform the necessary action on the TPA. |
Action |
Ask the B2B Administrator to assign the user the required permission. |
6057 | Access denied. User "{0}" does not have the permission to view {1}. |
Explanation |
User does not have the permission required to view the TPA. |
Action |
Request the B2B Administrator to assign user the required permission. |
6065 | Invalid "{0}". It should not start with "=". |
7010 | {0} is not a valid Trading Networks version. Rerun this program by specifying the supported version of your old Trading Networks. |
Explanation |
The Trading Networks version selected for migration is not valid. |
Action |
Rerun this program by specifying the correct version number. |
7011 | Source Server version is not provided. Rerun this program by specifying the source server version of Trading Networks. |
Explanation |
The Trading Networks version selected for migration is not provided. |
Action |
Rerun the migration utility by specifying the version number. |
7019 | The property file {0} does not exist. |
Explanation |
The properties.cnf file does not exist. |
Action |
Add the properties.cnf file to the "IntegrationServer > packages > WmTN > config" location. |
7020 | Document Type with name "{0}" already exists. Change the name and save again. |
Class | E |
Explanation |
Document type with the same name already exists. |
Action |
Change the document type name and save again. |
7021 | Error while changing the status of the doctype. |
Class | E |
Explanation |
Document type status update operation failed. |
Action |
See the stack trace and take appropriate action. |
7022 | Error while changing the status of the doctype {0}. |
Class | E |
Explanation |
Document type status update operation failed. |
Action |
See the stack trace and take appropriate action. |
7023 | List of doctypes for changing status can not be empty. |
Explanation |
List of doctypes is a mandatory field. |
Action |
Configure a list of doctypes while changing the status. |
7031 | The Trading Networks configuration file was successfully migrated. |
7033 | The Trading Networks data was successfully migrated. |
7034 | Started migrating onboarding templates data. |
7035 | Successfully completed migrating onboarding templates data. |
7036 | Migrating onboarding templates data failed. |
7037 | Started migrating onboarding idtype. |
7038 | Successfully completed migrating onboarding idtype. |
7039 | Migrating onboarding idtype failed. |
7040 | Migrating Trading Networks dashboard data. |
7041 | Trading Networks dashboard data |
7042 | Trading Networks dashboard data was successfully migrated. |
7043 | Migrating summary data from runtime tables. |
7044 | Successfully migrated Trading Networks dashboard data. |
7045 | Failed to migrate Trading Networks dashboard data. |
7046 | Migrate Trading Networks dashboard data? (Note: This will take longer if runtime data size is big. This operation involves purging of existing data in the dashboard tables, followed by populating data in the dashboard tables from runtime tables.) |
7047 | Migration selected for Trading Networks dashboard data. |
7048 | Migration not selected for Trading Networks dashboard data. |
7059 | Exception while fetching codes list for document type "{0}" and UUID "{1}" . |
7060 | Invalid document type passed while fetching codes list for document type "{0}" and UUID "{1}" . |
8001 | new String[]{"Cannot process message that is not javax.mail.internet.MimeMessage or javax.mail.internet.MimeBodyPart. Current message is: {0} ","","0"} |
Class | E |
Explanation |
Message cannot be parsed because it is neither a MimeMessage, nor a MimeBodyPart. |
Action |
Check the message type before invoking the service. |
8013 | Error encountered while downloading sample csv file. Please see error log for more details, contact your Administrator. |
Class | E |
Explanation |
In webMethods Trading Networks, in Parner Onboarding, while downloading a sample csv file for uploading a partner, if any error is encountered, this message appears. |
Action |
Contact your system administrator. |
8050 | A template field with this name already exists: {0}. |
Explanation |
In webMethods Trading Networks, while creating a new template field, if the name is not unique, this error shows up. |
Action |
Ensure to have a unique template field name and try again. |
8052 | An exception occurred while inserting template field (ID = "{0}", Name = "{1}"). |
Explanation |
In webMethods Trading Networks, while adding a template field, if an exception occurs while adding a new template field, this error is thrown. |
Action |
See the exception stack trace to find out the reason for this error. |
8053 | An exception occurred while updating template field (ID = "{0}", Name = "{1}"). |
Explanation |
In webMethods Trading Networks, while updating a template field, if an exception occurs while updating the template field, this error occurs. |
Action |
Check the exception stack trace to find out the reason for the error. |
8054 | An exception occurred while inserting template group (ID = "{0}", Name = "{1}"). |
Explanation |
In webMethods Trading Networks, while inserting a template field group, if an exception occurs while updating the template field, this error occurs. |
Action |
Check the exception stack trace to find out the reason for the error. |
8055 | A group with this name already exists: {0}. |
Explanation |
In webMethods Trading Networks, while adding a group to a questionnaire template, if the name already exists, this error shows up. |
Action |
Ensure to use a unique group name and try again. |
8056 | An exception occurred while fetching template fields for group(ID = "{0}", Name = "{1}"). |
Explanation |
In webMethods Trading Networks, while fetching template fields for a group, if an exception occurs, this error shows up. |
Action |
Check the exception stack trace to find out the reason for the error. |
8057 | A template with this name already exists: {0}. |
Explanation |
In webMethods Trading Networks, while adding a questionnaire template, if the name already exists, this error shows up. |
Action |
Ensure to use a unique questionnaire template name and try again. |
8059 | The invitation has expired. Contact your administrator. |
8060 | The invitation is disabled now. Contact your administrator. |
8061 | An exception occurred while querying templates. |
8062 | changed as following: |
8146 | VFS Path |
8146...0 | Sending the new email invitation failed. |
9000 | Invalid facet provided to API - {0} |
9001 | Access denied, as the User "{0}" doesnot have the permission to {1} {2}. |
Explanation |
The corresponding user does not have permissions to perform the associated actions. |
Action |
Contact a B2B Administrator for granting the corresponding permissions. |
9001...0 | Please supply the required value. |
9002 | Error encountered while fetching search results, page {0} requested is not found for queryId={1}. Contact your administrator to optimize the configuration of the TNQueryResults cache. |
Explanation |
In webMethods Trading Networks, while getting the query results, if the page request for a query ID is null, this error is thrown. |
Action |
Contact your administrator to optimize the configuration of the TNQueryResults cache. |
9002...0 | Please restore the original version of this service. |
9003 | Access denied, as the User "{0}" doesnot have the privilege to {1} {2}. |
Explanation |
The corresponding user does not have permissions to perform the associated action. |
Action |
Contact a B2B Administrator for granting the corresponding permissions. |
9003...0 | Could not configure Ehcache. Either the SoftwareAG-IS-TN.xml file is missing from the config folder or it is an invalid XML file. |
9004 | Access denied, as the User "{0}" doesnot have the privilege to view {1}. |
Explanation |
The corresponding user does not have permissions to view the corresponding Trading Networks asset. |
Action |
Contact a B2B Administrator for granting the corresponding permissions. |
9004...0 | Trading Networks Server startup failed. Error initializing Ehcache manager {0}. Contact your administrator to restore the SoftwareAG-IS-TN.xml file. |
9005 | Recipient info is not available for the recipientCert |
9006 | Primary and secondary certificates already exist for this owner, partner, and usage combination. |
Class | E |
Explanation |
A maximum of two certificates can be uploaded per unique combination of owner, partner, and usage. |
Action |
Delete the primary or secondary certificate before uploading an additional certificate. |
9007 | Error occurred while initializing Ehcache cache manager and accessing cache from it. Error message : {0}. |
Explanation |
An error occurred while initializing the Ehcache cache manager and accessing cache from it. |
Action |
Contact your system administrator. |
9008 | Failed to initialize cache manager for Ehcache. The SoftwareAG_IS_TN.xml file is missing, replaced, or invalid. |
Explanation |
webMethods Trading Networks failed to initialize the cache manager for Ehcache. The SoftwareAG_IS_TN.xml file is missing, replaced, or invalid. |
Action |
Add a valid SoftwareAG_IS_TN.xml file in the configurations folder. |
9009 | Error occurred while initializing Trading Networks because the following caches are not configured: {0} |
Class | E |
Explanation |
An error occurred while initializing Trading Networks because one or more caches are not configured. |
Action |
Check the cache manager SoftwareAG.IS.TN, configure the missing caches, and restart Integration Server. |
9010 | Error occurred while adding Ehcache Manager for tenantId: {0} and stageId: {1}. The exception message is: {2} |
9012 | Certificate with certificate ID {0} is already the primary certificate. |
Class | E |
Explanation |
The wm.tn.security:setPrimaryCertificate service was called incorrectly using the certificate ID of a primary certificate. |
Action |
Specify the certificate ID of the secondary certificate as input to wm.tn.security:setPrimaryCertificate service. |
9015 | Database error in getting prepared statement or Set proper dequeue strategy map entry |
9016 | Error encountered in wm.tn.security:setPrimaryCertificate. |
1010 | Error while running archive operation: {0}. |
Class | E |
Explanation |
Trading Networks encountered an exception while archiving documents. |
Action |
See the exception in the full message. Take appropriate action to resolve the problem described in the exception. |
1013 | {0} could not be completed because another {1} operation was under way or Archive_WorkTable has contents that were not cleaned up. If there is no archive/deletion service running, cleanup the table to complete the operation. |
Class | |
Explanation |
Trading Networks cannot complete the archive or delete operation either because another archive or delete operation is in progress or because the Archive_WorkTable has contents that need to be cleaned up. |
Action |
If no other archive or delete operation is in progress, clean up the Archive_WorkTable contents and restart the incomplete archive or delete operation. |
2004 | Cannot save a {0} without a {1}. |
Class | E |
Explanation |
Trading Networks cannot save the specified profile component because a required field is missing. |
Action |
Enter the value for the required field. |
2005 | Error logging database event. |
Class | E |
Explanation |
Trading Networks encountered an exception while writing an activity log entry to the database. |
Action |
See the exception written to the server log. Take appropriate action to resolve the problem described in the exception. |
2006 | Error encountered while deleting {0}. {1} rows changed in the database. |
Class | E |
Explanation |
Instead of deleting exactly one row from a table in the database, Trading Networks deleted the specified number of rows. |
Action |
See the exception written to the server log. Take appropriate action to resolve the problem described in the exception. |
2008 | Table not recognized: {0}. |
Class | E |
Explanation |
Trading Networks found a profile field in the database that refers to a nonexistent table. |
Action |
Ensure that your query is for an existing profile field. |
2009 | Error while inserting document {0}. |
Class | E |
Explanation |
Trading Networks encountered an exception while writing a document to the database. |
Action |
See the exception in the full message. Take appropriate action to resolve the problem described in the exception. |
2011 | Error while querying documents: {0}. Original SQL: {1}. |
Class | E |
Explanation |
Encountered an SQLException while performing a document query. |
Action |
Take appropriate action to resolve the problem described in the exception. |
2012 | Inserting field definition failed. |
Class | E |
Explanation |
Attempted to add a profile field definition, but the database was unchanged. |
Action |
Contact webMethods Customer Care. |
2016 | An attempt was made to access the SQL statement {0}, which was not defined in the configuration file. |
Class | E |
Explanation |
Attempted to execute an SQL statement that is not available in the file of externalized SQL statements (dbops.sql). |
Action |
If you have modified the dbops.sql file, restore the file to its prior state. |
2026 | An attempt was made to save an extended field with an unsupported data type. Name={0}, Data type={1}. |
Class | E |
Explanation |
Attempted to save an extended field for a partner, but the field's value is not a supported data type. |
Action |
Supply a value that is one of the supported data types for an extended field. |
2027 | Could not update type {0} for attribute {1}. |
Class | D |
Explanation |
Attempted to save a document attribute, but the attribute did not reference a valid document type. |
Action |
If you are explicitly calling services to save an attribute, ensure that the attribute refers to a valid document type. |
2029 | The database has no version information. Either it has not been initialized, or it has been changed to an invalid state by an external process. |
Class | E |
Explanation |
The TNModelVersion table is missing. Data from this table was accidentally deleted, the table was dropped, or the database is corrupt. |
Action |
Restore this table from the most recent backup. If the database is corrupt, work with your DBA to determine the cause. In this case, you will need to restore the entire database to the most recent backup. |
2031 | No model version information was available from the database. |
Class | S |
Explanation |
The TNModelVersion table is missing. Data from this table was accidentally deleted, the table was dropped, or the database is corrupt. |
Action |
Restore this table from the most recent backup. If the database is corrupt, work with your DBA to determine the cause. In this case, you will need to restore the entire database to the most recent backup. |
2036 | Unsupported encoding {0} declared in the TN config file (tn.store.encoding). |
Class | E |
Explanation |
The tn.store.encoding property was set to an invalid value. |
Action |
Set the tn.store.encoding property to a valid value. |
2037 | The model version specified (tnmv:) seems to be missing from the dbops.sql file in your WmTN package. Check the file and try again. |
Class | S |
Explanation |
The dbops.sql file must begin with "-- tnmv: x.x", where "x.x" is the current TNModelVersion number. This line has been removed or altered. |
Action |
Restore the dbops.sql file to the correct state. |
2039 | There was an error while reading the dbops.sql file in your WmTN package. The original error message was: {0}. |
Class | S |
Explanation |
Encountered an exception while reading the dbops.sql file. See the exception message for details. |
Action |
Take appropriate action to resolve the problem described in the exception. |
2040 | Error encountered while updating {0}. {1} rows changed in the database. |
Class | E |
Explanation |
Instead of updating exactly one row in a table in the database, Trading Networks updated the specified number of rows. |
Action |
Contact webMethods Customer Care. |
2041 | Error while redefining attribute {0} ({1}). |
Class | W |
Explanation |
Encountered an SQLException while updating a document attribute. |
Action |
Take appropriate action to resolve the problem described in the exception. |
2042 | Error encountered while updating {0}. {1} rows changed in the database for {2}. |
Class | E |
Explanation |
Instead of updating exactly one row in a table in the database, Trading Networks updated the specified number of rows. |
Action |
Contact webMethods Customer Care. |
2047 | No extended fields were deleted for group {0} (partnerID={1}). |
Class | E |
Explanation |
Expected to delete exactly one row in the PartnerProfileField table in the database. Instead, Trading Networks did not delete any rows. |
Action |
There seems to be an error while deleting. Find out why the row did not get deleted. |
2051 | Unable to insert binary object (partnerID={0}). |
Class | E |
Explanation |
An INSERT statement was unsuccessful in adding a row to the database. |
Action |
The exception is in the full message. Take appropriate action to resolve the problem described in the exception. |
2064 | There was an error interpreting the model version specifier (tnmv:) in the dbops.sql file in your WmTN package. The original error message was: {0}. |
Class | S |
Explanation |
The dbops.sql table must begin with "-- tnmv: x.x", where "x.x" is the current TN Model Version number. This line has been altered. |
Action |
Restore this line to its correct state. |
2066 | The main connection to the data store has not been initialized. Check the Trading Networks JDBC connection pool. |
Class | E |
Explanation |
There is no connection to the Trading Networks database. |
Action |
Use the Integration Server Administrator JDBC Pools page to test the connection to the Trading Networks database. You may need to adjust the connection pool settings or verify that the database is functioning normally. |
2067 | Extended field (fieldID={0}) not deleted (partnerID={1}). |
Class | E |
Explanation |
A DELETE statement was unsuccessful in removing a row from the database. |
Action |
Check the database connection or see the logs for more detailed stack trace information and take appropriate action. |
2079 | More than one extended field (fieldID={0}) removed in a single delete operation (partnerID={1}). |
Class | E |
Explanation |
Instead of deleting exactly one extended field in the database, Trading Networks deleted the specified number of fields. |
Action |
Check which other extended fields could have been deleted along with the intended one, then recreate the appropriate extended fields and redo the mapping. |
2085 | Cannot change a {0} without a {1}. |
Class | E |
Explanation |
Attempting to update a profile component, but a required field is missing. |
Action |
Supply a value for the missing field. |
2089 | Trading Networks could not retrieve data from your database. Go to the JDBC Pools page in the Integration Server Administrator and make sure your database URL, user name, and password are set correctly. Also make sure you created the Trading Networks database tables as described in the webMethods Installation Guide. |
Class | E |
Explanation |
The TNModelVersion table is missing from the Trading Networks database. The reason can be one of the following: 1) The Trading Networks database tables have not yet been created. 2) Data from TNModelVersion table was accidentally deleted. 3) The TNModelVersion table was dropped. 4) Your database is corrupt. |
Action |
Check your database. If the Trading Networks tables have not been created, create them. If the TNModelVersion table is missing or not valid, recreate it. If your database is corrupt, work with your database administrator to determine the cause. You might need to restore your entire database from the most recent backup. |
2096 | Document {0} from this sender was not successfully stored in the data store. The original exception message was: {1}. |
Class | E |
Explanation |
Encountered an exception while writing a document to the database. |
Action |
Take appropriate action to resolve the problem described in the exception. |
2104 | An attempt was made to access the SQL statement {0} before SQL statements were read from the disk. |
Class | E |
Explanation |
An SQL statement was used before the SQL statement cache was initialized. |
Action |
If your package uses Trading Networks facilities, be sure to declare a dependency on the WmTN package in your package's manifest.v3 file. |
2110 | Error decoding type {0}. |
Class | E |
Explanation |
Encountered an IOException while decoding binary data from the database into a BizDocType object. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
2112 | Document type not saved. A document type with the name [{0}] already exists. Cannot have two document types with the same name but different IDs. |
Class | E |
Explanation |
You cannot have two document types with the same name. |
Action |
Change the name of the document type and save it again. |
2114 | The system could not load the JDBC driver {0} for connection to the data store. Check the CLASSPATH setting and try again. |
Class | E |
Explanation |
The driver specified for the Trading Networks functional alias on the JDBC Pools Configuration page of the Integration Server could not be found. |
Action |
Make sure the driver is in your classpath. |
2119 | Unknown or deleted attribute {0}. |
Class | E |
Explanation |
The wm.tn.doc:setAttribute service was supplied an invalid attribute ID or name. |
Action |
Supply a valid attribute ID or name. |
2127 | Error encountered while updating Contact. {0} rows changed in database for {1} {2}. |
Class | E |
Explanation |
Instead of updating exactly one row in the Contact table in the database, Trading Networks updated the specified number of rows. |
Action |
Check the affected details and verify whether the data can be recreated. |
2131 | Could not find doc {0}; no document type {1}. |
Class | E |
Explanation |
Could not create a bizdoc from binary data in the database. The TN document type it references does not exist. |
Action |
The document type corresponding to the bizdoc may have been deleted, or the associated data may be corrupted. Contact Customer Care. |
2132 | Could not archive documents. |
Class | E |
Explanation |
Encountered an SQLException while archiving documents. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2133 | Could not delete archived documents. |
Class | E |
Explanation |
Encountered an SQLException while deleting archived documents. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2134 | Could not delete documents. |
Class | E |
Explanation |
Encountered an SQLException while deleting documents. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2135 | Could not queue documents. |
Class | E |
Explanation |
Encountered an SQLException while queuing a document for polling. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2136 | Could not poll documents. |
Class | E |
Explanation |
Encountered an SQLException while polling for documents. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2137 | Could not accept document. |
Class | E |
Explanation |
Encountered an SQLException while accepting a polled document. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2138 | Could not query the event table. |
Class | E |
Explanation |
Encountered an SQLException while querying activity log entries. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2139 | Could not delete the events. |
Class | E |
Explanation |
Encountered an SQLException while deleting activity log entries. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2140 | Could not instantiate document {0}. |
Class | E |
Explanation |
Encountered an SQLException while retrieving a document. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2141 | Could not check uniqueness {0}. |
Class | E |
Explanation |
Encountered an SQLException while querying the database to determine if a document is unique. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2142 | Could not get the user status. |
Class | E |
Explanation |
Encountered an SQLException while retrieving the user status of a document. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2143 | Could not insert the new document. |
Class | E |
Explanation |
Encountered an SQLException while saving a new document. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2144 | Could not change status for {0}. |
Class | E |
Explanation |
Encountered an SQLException while changing the status of a document. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2145 | One of (fromdoc,todoc) must be persisted. |
Class | E |
Explanation |
Attempted to relate two documents, but neither of them has been saved to the database. |
Action |
Save one or both of the documents to be related. |
2146 | Could not relate {0} and {1}. |
Class | E |
Explanation |
Encountered an SQLException while relating two documents. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2147 | Could not get rels: doc={0}, gr={1}. |
Class | E |
Explanation |
Encountered an SQLException while retrieving related documents. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2148 | The following exceptions occurred: |
Class | E |
Explanation |
The following exceptions were encountered while retrieving the full set of TN document types. |
Action |
See each of the following exceptions for details. Take appropriate action to resolve the problem described in each exception. |
2149 | Database error while fetching all types: {0}. |
Class | E |
Explanation |
Encountered an SQLException while retrieving the full set of TN document types. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2150 | Database error while adding type {0}: {1}. |
Class | E |
Explanation |
Encountered an SQLException while saving a new TN document type. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2151 | Encoding error while putting type {0}: {1}. |
Class | E |
Explanation |
Encountered an IOException while saving a new TN document type. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2152 | Database error while updating type {0}: {1}. |
Class | E |
Explanation |
Encountered an SQLException while updating a TN document type. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2153 | Encoding error while updating type {0}: {1}. |
Class | E |
Explanation |
Encountered an IOException while saving a new TN document type. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2154 | Cannot aggregate STRING attributes. |
Class | E |
Explanation |
Attempted to execute an aggregation operation (SUM, AVG, MIN, MAX) on a String attribute. |
Action |
Do not specify the aggregation operation. |
2160 | Could not queue document for delivery (id={0}). |
Class | E |
Explanation |
Encountered an SQLException while changing the status of a document to "QUEUED". |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2162 | Trading Networks database pool is not configured. Please configure a database pool for functional alias "TN" and restart the WmTN package. |
Class | E |
Explanation |
Data required to configure a connection to the database is missing or invalid. |
Action |
Use the Integration Server Administrator JDBC Pools page to recreate this data. |
2164 | Error while logging an activity entry to the audit sub system. The exception message is : {0}. |
Class | E |
Explanation |
Encountered an exception while publishing an activity log entry. |
Action |
Take appropriate action to resolve the problem described in the exception. |
2165 | Error while reading the database configuration. The exception message is : {0}. |
Class | E |
Explanation |
Trading Networks encountered an exception while reading the database configuration data. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. You might need to use the JDBC Pools page in the Integration Server Administrator to recreate this data. |
2168 | Trading Networks database pool is not configured properly. Make sure that a valid database pool is assigned for functional alias "TN" and restart the WmTN package. |
Class | E |
Explanation |
Data required to configure a connection to the database is missing or invalid. |
Action |
Use the Integration Server Administrator JDBC Pools page to recreate this data. |
2169 | Unable to locate the database configuration information. File {0} does not exist. |
Class | E |
Explanation |
A file required to configure a connection to the database is missing. |
Action |
Use the Integration Server Administrator JDBC Pools page to recreate this data. |
2170 | Trading Networks database pool is not configured properly. Make sure that a valid database pool is assigned to functional alias "TN" and try again. |
Class | E |
Explanation |
Data required to configure a connection to the database is missing or invalid. |
Action |
Use the Integration Server Administrator JDBC Pools page to recreate this data. |
2175 | The database connection pool associated with TN should allow at least 2 connections. Your TN pool is currently configured with a maximum of {0} connections. Aborting TN startup. Please increase your TN database pool maximum and restart the server. |
Class | E |
Explanation |
Trading Networks requires at least two connections for its pool. Trading Networks will not initialize with fewer than two connections. |
Action |
Use the Integration Server Administrator JDBC Pools page to increase the number of connections allowed for the Trading Networks database pool. Then restart your server. |
2180 | Database error while deleting document type {0}: {1}. |
Class | U |
Explanation |
Encountered an SQLException while deleting a document type. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
2181 | A BizDocType with this name already exists: {0}. |
Class | E |
Explanation |
You cannot have two document types with the same name. |
Action |
Save the document type with a different name. |
2184 | The profile field definition "{0}" already exists with a different ID. The field definition was not imported. |
Class | E |
Explanation |
This error can occur when importing extended profile fields. The most likely cause is that the field was already manually created on the target server. |
Action |
If you do not intend to import extended field values, this error can be ignored. If you do intend to import extended field values, and no partner yet has a value for this field on your target server, you can change the ID of the field definition to match the one on the source server. Carefully update the ProfileFieldID key in the ProfileField table of the database into which you are importing. |
2185 | An IDType with a key of "{0}" already exists with a different ID description. The IDType "{1}" was not imported. You will need to directly edit the IDType table in your database to correct this problem. |
Class | E |
Explanation |
The error can occur when importing extended ID types. The most likely cause is that the IDType was already manually created on the target server. |
Action |
Change the Type column of the IDType table on the target database to match that of the source database. |
2186 | Could not update comments for document {0}. |
Class | |
Explanation |
Encountered SQLException while updating comments for document. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
2199 | Error encountered while reading routing status from the database. Exception message: {0}. |
Class | |
Explanation |
Encountered SQLException while reading routing status from database. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
2212 | A scheduled archival service with this name already exists. |
Class | |
Explanation |
A scheduled archival service with the same name already exists. |
Action |
Change the name of the scheduled archival service and save again. |
2215 | Unable to save scheduled archive service "{0}". |
Class | |
Explanation |
Error encountered while updating the archive service. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
2221 | Interval is not a valid integer. |
Class | |
Explanation |
Interval set in the schedule is wrong; it must be a valid integer. |
Action |
Correct the interval field in the schedule and save the schedule again. |
2222 | Interval must be greater than zero. |
Class | |
Explanation |
Interval set in the schedule is wrong; it must be greater than zero. |
Action |
Correct the interval field in the schedule and save the schedule again. |
2223 | The scheduled {0} is invalid. Format must be YYYY/MM/DD. |
Class | |
Explanation |
Schedule date must be of format YYYY/MM/DD. |
Action |
Change the schedule according to the format and save it again. |
2224 | The scheduled {0} is invalid. Format must be hh:mm:ss. |
Class | |
Explanation |
Schedule time must be of format hh:mm:ss. |
Action |
Change the schedule according to the format and save it again. |
2231 | The scheduled delivery date/time is in the past. |
Class | |
Explanation |
Schedule delivery date/time set must not be in the past. |
Action |
Change the delivery schedule with the date/time in the future. |
2232 | If an end time is supplied, an end date must also be supplied. |
Class | |
Explanation |
End date has to be supplied along with end time. |
Action |
Set the end date along with the end time, and save the schedule. |
2233 | End date/time is in the past. |
Class | |
Explanation |
End date/time must not be set in the past. |
Action |
End date/time should always be later than the start date/time. Correct the end date/time and save the schedule again. |
2234 | End date/time is before start date/time. |
Class | |
Explanation |
End date/time must not be before the start date/time. |
Action |
End date/time should always be later than the start date/time. Correct the end date/time and save the schedule again. |
2235 | Could not construct a valid timestamp from this schedule. Dates must be in YYYY/MM/DD format and times must be in hh:mm:ss format. |
Class | |
Explanation |
Delivery schedule created with an incorrectly formatted date. |
Action |
Correct the date format and save the delivery schedule. |
2236 | Delivery schedule dates must be in the format "YYYY/MM/DD" and times must be in the format "hh:mm:ss". |
Class | |
Explanation |
Delivery schedule created with an incorrectly formatted date. |
Action |
Correct the date format and save the delivery schedule. |
2244 | Unable to remove scheduled archival service "{0}". |
Class | |
Explanation |
Encountered exception while deleting archival service from database. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
2246 | Unable to update scheduled archival service "{0}". |
Class | |
Explanation |
Encountered exception while updating archival service to database. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
2301 | An exception occurred while listing the document attributes. |
Class | |
Explanation |
Encountered exception while getting document attributes from cache or database. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
3001 | Persistence Service Failed. |
Class | E |
Explanation |
Encountered an exception while saving the document to the database. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
3002 | An error occurred while trying to insert this document into the database. The original error message was: {0}. |
Class | E |
Explanation |
Encountered an exception while saving the document to the database. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
3007 | Non-unique ID(s) detected. |
Class | E |
Explanation |
This incoming document already exists in the database. This is a duplicate document, based on the unique document criteria. |
Action |
Notify the document sender that the document sent is a duplicate. |
3008 | This document is not unique. It matched {0} existing documents in the database. |
Class | W |
Explanation |
This incoming document already exists in the database. This is a duplicate document, based on the unique document criteria. |
Action |
Notify the document sender that the document sent is a duplicate. |
3015 | Could not get the document bytes. |
Class | E |
Explanation |
An exception was thrown while adding the document content to the BizDocEnvelope. The document might be corrupt. |
Action |
Trading Networks wrote the exception to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
3016 | No such document: {0}. |
Class | E |
Explanation |
The wm.tn.doc:view service was passed an invalid internal document ID. |
Action |
Supply a valid internal document ID to the wm.tn.doc:view service. |
3018 | Invalid duplicate checking service. |
Class | E |
Explanation |
Custom duplicate check was selected, but either a duplicate check service was not specified or the specified duplicate check service was invalid. |
Action |
Using My webMethods Server, update the TN document type and/or the processing rule and specify a valid duplicate checking service. |
3019 | The BizDocType refers to a non-existent duplicate checking service: {0}. It may have been renamed, disabled, or deleted. |
Class | E |
Explanation |
Custom duplicate check was selected, but no duplicate check service was specified or the specified duplicate check service was invalid. This error could also occur when the specified duplicate check service has been renamed, disabled, or deleted. |
Action |
Using My webMethods Server, update the TN document type and/or the processing rule and specify a valid duplicate checking service. |
3020 | Duplicate document detected. |
Class | E |
Explanation |
You received a document that failed a custom duplicate document check. The custom duplicate checking service flagged the document as a duplicate. |
Action |
You can ignore this message, or you can notify the sender of the document that you have received a duplicate. |
1001 | Content Part {0} does not exist in document {1}. |
Class | E |
Explanation |
The document does not contain the requested content part. |
Action |
Request a different content part, or request this content part from a different document. |
1002 | Content for Part {0} of document {1} does not exist in TSpace. |
Class | E |
Explanation |
This is a large document and the requested content part was not found in the temporary storage. |
Action |
Request a different content part, or request this content part from a different document. |
1003 | Error retrieving content of content part {0} of document {1}. The exception message is : {2}. The stack trace is : {3} |
Class | E |
Explanation |
An exception was thrown while retrieving the document content. |
Action |
Take appropriate action to resolve the problem described in the exception message. |
1004 | Unable to find a document type for the given document type name, {0}. |
Class | E |
Explanation |
Could not find the document type specified for deleting. |
Action |
Provide a valid TN document type name to the wm.tn.doc:deleteDocuments service. |
1006 | Attempted to update system attributes for the document, but no rows were changed in the database. |
Class | E |
Explanation |
Trading Networks encountered an error while attempting to update the system attributes of the document. |
Action |
Retrieve this document from the database and examine it to determine why the error occurred. |
1017 | System Attribute update failed. |
Class | |
Explanation |
Encountered an exception while updating the system attribute. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
1018 | Error when adding large content part named {0} to this document |
Class | E |
Explanation |
Encountered an exception while adding a large content part to the document. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
1019 | The actual exception is {0}. |
Class | E |
Explanation |
Encountered an exception while adding a large content part to a document. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
1020 | User{0} is not an administrator and attempted to retrieve a document (docID={1}) that does not belong to him. |
Class | E |
Explanation |
Users without administrative rights can only retrieve documents that they have either sent or received. |
Action |
None. |
1021 | You do not have the authority to retrieve this document. Only administrators may access documents that they did not send or receive. |
Class | E |
Explanation |
Users without administrative rights can only retrieve documents that they have either sent or received. |
Action |
Request a user with administrative rights to access the document. |
2035 | Recognize: unable to get XML DTD for comparison: {0} {1} {2} {3} |
Class | E |
Explanation |
The DTD statement in the document may be incorrect. |
Action |
Check the document that is being processed to ensure that it is structured correctly. If it is not, notify the responsible party about this document. |
2036 | BizDocTypeReg: ERROR invoking recognize for {0} |
Class | E |
Explanation |
See the exception message for details. |
Action |
Take appropriate action to resolve the problem described in the exception. |
2040 | {0}: No envelope queries specified |
Class | E |
Explanation |
The TN document type has no envelope queries defined. |
Action |
Use My webMethods to edit the TN document type and define envelope queries. |
2041 | Error filling BizDocTypeStore cache |
Class | E |
Explanation |
Encountered an error while reading the TN document types from the database and caching them in memory. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. |
2042 | Doctype info not initialized |
Class | E |
Explanation |
The BizDocType Registry was not initialized. |
Action |
Try reloading the WmTN package. |
2043 | Unknown type name: {0} |
Class | E |
Explanation |
The wm.tn.doctype:view service was passed an invalid TN document type name. |
Action |
Pass a valid TN document type name to the service. |
2044 | Unknown type id: {0} |
Class | E |
Explanation |
The wm.tn.doctype:view service was passed an invalid TN document type ID. |
Action |
Pass a valid TN document type ID to this service. |
2045 | Operation not supported for RecordDocType |
Class | E |
Explanation |
You cannot create an instance of the RecordDocType. |
Action |
Creating an instance of the RecordDocType is not allowed. |
2054 | IOException encoding pipeline |
Class | E |
Explanation |
Encountered an exception while binary-encoding the data for an unknown document type. See the nested exception for details. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
2056 | Query or Transform Failed |
Class | E |
Explanation |
Encountered an exception while extracting a document attribute and converting its value. |
Action |
Verify that the attribute extraction query in the TN document type is valid. |
2057 | Transform Failed |
Class | E |
Explanation |
An error occurred while converting the attribute value. |
Action |
Use My webMethods to verify that the attribute details about the TN document type are correct. If they are, gather details about the error and contact Software AG Global Support. |
2058 | Error generating query expression |
Class | E |
Explanation |
Encountered an exception while generating an XML query to extract a document attribute. |
Action |
Correct the attribute extraction query on the TN document type. |
2059 | No such BizDocType: {0} |
Class | E |
Explanation |
The wm.tn.doc:createReply service was passed an invalid replyTypeId. |
Action |
Pass a valid replyTypeId to the service. |
2060 | Doctype info not initialized. BizDocType registry has not been created. |
Class | E |
Explanation |
The BizDocType Registry was not initialized. |
Action |
Try reloading the WmTN package. |
2061 | An error occurred when constructing the XML Document object |
Class | E |
Explanation |
A document object could not be constructed from the XML. See the nested exception for details. |
Action |
Take appropriate action to resolve the problem described in the nested exception. |
2062 | Recognition failed. |
Class | E |
Explanation |
Unable to recognize document. See the next message for details. |
Action |
Take appropriate action to resolve the problem described in the next message. |
2063 | There is not enough space on TSpace storage system to store the content of this large document |
Class | E |
Explanation |
The HDD partition used for temporary storage of large documents is full. |
Action |
Either change the value of the tn.tspace.location property, or increase the size of the partition. |
2065 | Unknown datatype encountered transforming attribute for FFDocType {0} |
Class | E |
Explanation |
The attribute value supplied in the pipeline for the flat file document is not a String. |
Action |
Correct the document gateway service that puts this value in the pipeline. The attribute value must be a String. |
2066 | FFDocType {0} encountered an unknown datatype while applying the {1} transformation to the "{2}" attribute. |
Class | E |
Explanation |
The attribute value supplied in the pipeline for the flat file document is not a String. |
Action |
Correct the document gateway service that puts this value in the pipeline. The attribute value must be a String. |
2067 | The {0} attribute is required by the {1} doctype. It is missing. |
Class | E |
Explanation |
The attribute that is required for the flat file TN document type is missing in the pipeline. |
Action |
Correct the document gateway service that supplies the value for this attribute. |
2068 | FFDocType {0} encountered an error transforming an attribute. |
Class | E |
Explanation |
The specified flat file document type extracts an attribute. Trading Networks encountered an error while transforming the attribute value. |
Action |
Use My webMethods to verify that the attribute details for the TN document type are correct. If they are, gather details about the error and contact Software AG Global Support. |
2069 | FFDocType {0} encountered an error while applying the {1} transformation to the "{2}" attribute: {3} : {4} |
Class | E |
Explanation |
An error occurred while transforming the attribute value. |
Action |
Use My webMethods to verify that the attribute details for the TN document type are correct. If they are, gather details about the error and contact Software AG Global Support. |
2070 | FFDocType {0} encountered an error reading the document bytes. |
Class | E |
Explanation |
Encountered a problem while processing the "ffdata" InputStream. |
Action |
See the entire message for details. |
2071 | FFDocType {0} encountered an error reading the document bytes. {1} : {2} |
Class | E |
Explanation |
Encountered an exception while reading the "ffdata" InputStream. See the exception message and stack trace for details. |
Action |
Verify that your document gateway service is not corrupting the "ffdata" InputStream. Resend the document. |
2072 | Cannot unregister a built-in DocType Category: {0} |
Class | E |
Explanation |
The wm.tn.doctype:unregisterCategory service was passed the name of a built-in TN document type category, such as "XML", or "Flat file". |
Action |
Do not unregister a built-in category. |
2079 | Could not determine document sender. |
Class | E |
Explanation |
The TN document type is configured to determine the document sender from the connected user but it could not. |
Action |
See the entire message for details. |
2080 | Could not determine document sender for doctype "{0}"because there is no connected user. |
Class | E |
Explanation |
The TN document type is configured to determine the document sender from the connected user but it could not. A possible reason for the error is the lack of a connected user. |
Action |
Determine why there is not a connected user. Perhaps the document has been submitted by a background thread. |
2081 | Could not get ProfileSummary for sender from connected user "{0}". |
Class | E |
Explanation |
The TN document type is configured to determine the document sender from the connected user but it could not. There is a connected user, but it does not have a partner profile. |
Action |
Create a partner profile for the user, or instruct the user to log on the system using a valid partner account. |
2083 | FFDocType {0} encountered an error reading the document bytes. Key "ffdata" is not found in the pipeline |
Class | E |
Explanation |
The "ffdata" InputStream is missing in the pipeline. |
Action |
Verify that your document gateway service is not dropping "ffdata" from the pipeline. Resend the document. |
2084 | FFDocType {0} encountered an error reading the content of document {1}. |
Class | E |
Explanation |
This is a large document and Trading Networks encountered an error while reading the document's InputStream from Tspace (hard disk drive space). See the nested exception for details. |
Action |
Take appropriate action to resolve the problem described in the nested exception. |
2085 | Error turning stream into bytes (docid={0}) |
Class | E |
Explanation |
The document has an unsupported encoding. See the server log or open this document in Transaction Analysis to see details about the error. |
Action |
Request the document to be resend using supported encoding. |
2086 | Attribute transformation ''{0}'' has no data |
Class | E |
Explanation |
The attribute referenced by this transformation is null. |
Action |
Gather details about this error, and contact Software AG Global Support. |
2088 | A corrupted document was encountered in recognition: {0} |
Class | E |
Explanation |
Trading Networks received an XML document that was not structured well. |
Action |
Correct the original document and resend it. |
2090 | Unable to load the following TN document types because their classes are not found in the classpath: {0}. Either correct the classpath to include the required classes and restart the Server or, if you no longer use these document types, delete them using the wm.tn.doctype:delete service and then restart the Server. |
Class | E |
Explanation |
There are TN document types in the database that are not available on the classpath. |
Action |
Correct the classpath to include the required classes and restart the server; or, if you no longer use these TN document types, delete them using the wm.tn.doctype:delete service, and then restart the server. |
2091 | Encountered an unsupported encoding |
Class | |
Explanation |
Encoding passed in the document is not supported by Integration Server. |
Action |
Change the document to a supported encoding. |
2092 | Error turning stream into bytes: {0} |
Class | |
Explanation |
Error encountered while converting the stream to bytes. This could happen if the stream was closed while still being read. |
Action |
Examine why the connection dropped while reading the stream. |
2093 | This operation is not supported for MissingDocType. |
Class | E |
Explanation |
The operation attempted to create a BizDocEnvelope from the MissingDocType class. |
Action |
If you developed code that creates instances of (No Suggestions) ensure that it does not attempt to create a BizDocEnvelope from the MissingDocType class. |
2094 | ERROR: The Java class for this document type was not found. |
Class | E |
Explanation |
The JAR file that holds the TN document type editor was not found. |
Action |
If you are viewing a Trading Networks XML or flat file document type, make sure that the tnclient.jar file is in the webMethods6\IntegrationServer\packages\WmTN\code\jars directory on the Integration Server file system. If you are viewing another category of TN document type, make sure that the JAR file with that TN document type editor is in the IntegrationServer\packages\WmTN\code\jars directory. |
2097 | Encountered an error while creating MAPI event to Optimize for EventMap {0} and for Sender with PartnerID {1}. |
Class | |
Explanation |
The error may be caused due to Broker being stopped. |
Action |
Start the associated Broker if it is stopped. |
3000 | Unable to construct mime message |
Class | E |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3001 | Unable to read mime message data source |
Class | |
Explanation |
The MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3002 | Unable to read mime message data source |
Class | E |
Explanation |
Problem while reading from input data source. |
Action |
Check input data source for errors. |
3003 | Unable to construct mime message |
Class | E |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3004 | Unable to handle data of type: {0} |
Class | E |
Explanation |
Attempted to add a message of type <msgType> to a multi-part MIME message. This type cannot be part of a multi-part MIME message. |
Action |
Check the message type that is being added to the multi-part MIME message. It must be either a multi-part MIME or a MIME message. |
3005 | Unable to handle null data source |
Class | E |
Explanation |
Cannot construct a MIME message from null data source. |
Action |
Pass valid, non-null data source to the service. |
3006 | Unable to read mime message data source |
Class | |
Explanation |
Problem while reading from input data source. |
Action |
Check input data source for errors. |
3007 | Unable to construct mime message |
Class | |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3008 | Can not replace existing body part |
Class | E |
Explanation |
Attempted to add a MIME body part to a MIME message that already contains a body part. |
Action |
Set the input flag 'replace' on the wm.tn.mime:addBodyPart service to 'yes'. This will replace the existing body part with the new one. Another solution is to set the flag 'multipart' to 'yes'. This will append the new body part to the existing one, making the message a multi-part MIME message. |
3009 | Unable to construct mime message |
Class | |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3010 | Unable to read mime message data source |
Class | |
Explanation |
Problem while reading the input data source. |
Action |
Check input data source for errors. |
3011 | getBodyPart not supported on non multipart message |
Class | E |
Explanation |
Attempted to get a MIME body part other than zero from a non-multipart MIME message. |
Action |
The number '0' (zero) is the only valid value for the input parameter 'index' of the wm.tn.mime:getBodyPartHeader and wm.tn.mime:getBodyPartContent services when the input MIME message is not a multi-part MIME message. |
3012 | Unable to construct mime message |
Class | |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3013 | Unable to read mime message data source |
Class | |
Explanation |
Problem while reading the input data source. |
Action |
Check input data source for errors. |
3014 | Unable to construct mime message |
Class | |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3015 | Unable to read mime message data source |
Class | |
Explanation |
Problem while reading the input data source. |
Action |
Check input data source for errors. |
3016 | Unable to construct mime message |
Class | |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3017 | Unable to construct mime message |
Class | |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3018 | Unable to construct mime message |
Class | |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3019 | Unable to construct mime message |
Class | |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3020 | Unable to construct mime message |
Class | |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3021 | Unable to construct mime message |
Class | |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3022 | Unable to construct mime message |
Class | |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3023 | Unable to construct mime message |
Class | |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3024 | Unable to determine Content type |
Class | E |
Explanation |
MIME message does not contain content-type information. Message is improperly structured. |
Action |
Inform the message sender about the error. |
3025 | Unable to get boundary for multipart mime message |
Class | E |
Explanation |
MIME message does not contain message boundary information. Message is improperly structured. |
Action |
Inform the message sender about the error. |
3026 | Unable to determine content-type |
Class | |
Explanation |
MIME message does not contain content-type information. Message is improperly structured. |
Action |
Inform the message sender about the error. |
3027 | Unable to construct mime message |
Class | |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3028 | Unable to read mime message data source |
Class | |
Explanation |
The MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3029 | Unable to construct mime message |
Class | |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3030 | Unable to determine content-type |
Class | |
Explanation |
MIME message does not contain content-type information. Message is improperly structured. |
Action |
Inform the message sender about the error. |
3031 | Unable to determine content-type |
Class | E |
Explanation |
MIME message does not contain content-type information. Message is improperly structured. |
Action |
Inform the message sender about the error. |
3032 | Unable to read mime message data source |
Class | E |
Explanation |
The MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3033 | Unable to construct mime message |
Class | E |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3034 | Unable to parse Content-Type string |
Class | E |
Explanation |
MIME message does not contain content-type information. Message is improperly structured. |
Action |
Inform the message sender about the error. |
3035 | Cannot write message to outputStream, content is null |
Class | E |
Explanation |
Message does not contain any data. |
Action |
Construct a MIME message with valid input data. |
3036 | Operation can only be performed on parsed message. |
Class | E |
Explanation |
The size of a MIME body part can only be determined for MIME messages that are parsed from a complete message. The size of each part cannot be determined when composing a MIME message. |
Action |
Do not attempt to obtain the size of a MIME body part that is part of a message that is being composed. |
3037 | Unable to parse ''Content-Disposition'' |
Class | E |
Explanation |
MIME message does not contain content-disposition information. Message is improperly structured. |
Action |
Inform the message sender about the error. |
3039 | Unable to get content. |
Class | E |
Explanation |
Error occurred while reading the message content. |
Action |
Check input data source for errors. |
3040 | Message Digest Algorithm ''{0}'' not supported. |
Class | E |
Explanation |
User has specified an invalid value for the 'digestAlgorithm' input parameter of the wm.tn.mime:setDigestAlgorithm service. |
Action |
Specify a valid value of either "MD5" or "SHA-1" for the 'digestAlgorithm' input parameter. |
3041 | Cannot set header for message that is not multipart. Either specify subType or set header using addBodyPart |
Class | E |
Explanation |
When calling the wm.tn.mime:createMimeData service, header for a non-multipart message cannot be set . |
Action |
Specify a value for subType, which will create a multi-part MIME message. Alternatively, for a MIME message that is not multi-part, headers can be specified when calling the wm.tn.mime:addBodyPart service. |
3101 | Parameter input must be an InputStream |
Class | E |
Explanation |
Input parameter 'input' must be an InputStream object. |
Action |
Pass in an InputStream object. |
3102 | Parameter mimeData cannot be null |
Class | |
Explanation |
Input parameter 'mimeData' must be sent. |
Action |
Pass in an mimeData object. |
3103 | content cannot be null when adding a mime body part |
Class | E |
Explanation |
Content cannot be null when adding a MIME body part |
Action |
Specify valid content. |
3104 | Unable to handle content of type {0} |
Class | E |
Explanation |
Input parameter 'content' must be one of the following types: InputStream, byte, array, or MIME message. |
Action |
Specify the value of the 'content' input parameter using one of the three allowed types. |
3105 | Parameter index must be of type int |
Class | E |
Explanation |
Specified a non-integer value for the 'index' input parameter when attempting to obtain a MIME body part. |
Action |
Check the value of the input parameter 'index' to ensure it is a non-negative integer. |
3106 | outputStream required |
Class | E |
Explanation |
Calls to the wm.tn.mime:writeToStream service require an OutputStream object to be specified for the 'outputStream' parameter. |
Action |
Pass an OutputStream object to the wm.tn.mime:writeToStream service. |
3107 | Unknown digest algorithm {0} |
Class | E |
Explanation |
User has specified an invalid value for the 'digestAlgorithm' input parameter. |
Action |
Specify a valid value of either "MD5" or "SHA-1" for the 'digestAlgorithm' input parameter. |
3108 | Parameter mimeData cannot be null |
Class | E |
Explanation |
The 'mimeData' input parameter has a null value. |
Action |
Specify a valid value for the 'mimeData' parameter. |
3109 | Parameter headerName cannot be null |
Class | E |
Explanation |
The headerName parameter cannot be null. |
Action |
Specify a valid value for the 'headerName' parameter. |
3112 | A digest algorithm must be specified when creating a message digest. |
Class | E |
Explanation |
The user has specified an invalid value for the 'digestAlgorithm' input parameter. |
Action |
Specify a valid value of either "MD5" or "SHA-1" for the 'digestAlgorithm' input parameter. |
3200 | Cannot recognize certificates |
Class | E |
Explanation |
Cannot recognize certificates. |
Action |
Certificates must be passed in as byte array objects. |
3201 | Cannot recognize certificate |
Class | E |
Explanation |
Cannot recognize certificates. |
Action |
Check the certificate format. The certificates must be a DER encoded ASN.1 format. |
3202 | Cannot recognize certificate at index {0} |
Class | E |
Explanation |
Cannot recognize certificate in chain at index: <index>. |
Action |
Check the certificate format. The certificate must be a DER encoded ASN.1 format. |
3203 | Certificate at index {0} is not valid |
Class | E |
Explanation |
Cannot recognize certificate at index: <index> |
Action |
Certificate must be passed in as byte array object. |
3204 | Error attempting to parse message contents |
Class | E |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3205 | Error attempting to read from message source |
Class | E |
Explanation |
An error occurred while reading message content. |
Action |
Check input data source for errors. |
3206 | Recipient certificate is not valid |
Class | E |
Explanation |
Cannot recognize certificates. |
Action |
Check the certificate format. The certificate must be a DER encoded ASN.1 format. |
3207 | Cannot recognize recipient certificate at index {0} |
Class | |
Explanation |
Cannot recognize certificate in chain at index: <index> |
Action |
Check certificate format. The certificate must be a DER encoded ASN.1 format. |
3208 | Cannot recognize recipient certificate at index {0} |
Class | |
Explanation |
Cannot recognize certificate in chain at index: <index> |
Action |
Check certificate format. The certificate must be a DER encoded ASN.1 format. |
3209 | Cannot recognize recipient certificate at index {0} |
Class | E |
Explanation |
Cannot recognize certificate at index: <index>. |
Action |
Check the certificate format. The certificate must be a DER encoded ASN.1 format. |
3210 | Certificate format is invalid for recipient certificate at index {0} |
Class | E |
Explanation |
Cannot recognize certificate in chain at index: <index>. |
Action |
Check the certificate format. The certificate must be a DER encoded ASN.1 format. |
3211 | Specified keylength {0}, is not allowed |
Class | E |
Explanation |
Invalid value specified for key length of RC2 encryption algorithm. |
Action |
Specify one of the allowed key length values: "40", "64", or "128". |
3212 | Specified algorithm `{0}`, is not supported |
Class | E |
Explanation |
Invalid encryption algorithm is specified. |
Action |
Specify one of the supported encryption algorithms: "TripleDES", "RC2", or "DES". |
3213 | In getEncryptedMimeObject: Cannot handle datasource of type: {0} |
Class | E |
Explanation |
When trying to create an encrypted message, the 'mimeSrc' object must be a MimeData object. |
Action |
Pass in a MimeData object. MimeData objects are created using the wm.tn.mime:createMimeData service. |
3214 | In getEncryptedMimeObject: Cannot handle null datasource |
Class | E |
Explanation |
The 'mimeSrc' input parameter cannot be null. |
Action |
Specify a valid MimeData object in the 'mimeSrc' parameter. |
3215 | Unable to get signer''s private key |
Class | |
Explanation |
Private key for sender may be missing. |
Action |
Ensure in My webMethods that the sender's private key is associated. |
3216 | Unable to get signer''s private key |
Class | E |
Explanation |
Cannot recognize the private key. |
Action |
Check the supplied private key. It should be a DER encoded ASN.1 representation of an RSA private key. |
3217 | Unable to get recipient certificate(s). |
Class | E |
Explanation |
Cannot recognize the certificates. |
Action |
Check the certificate format. The certificate must be a DER encoded ASN.1 format. |
3218 | Signer''s certificate is not a valid data format |
Class | E |
Explanation |
Cannot recognize certificates. |
Action |
Check the certificate format. The certificate must be a DER encoded ASN.1 format. |
3219 | Signer''s certificate is not recognized |
Class | E |
Explanation |
Cannot recognize certificates. |
Action |
Check the certificate format. The certificate must be a DER encoded ASN.1 format. |
3220 | Input parameter mimeSrc to service createSignedData cannot be of type {0}. It should be of type MimeData. |
Class | E |
Explanation |
When trying to create a signed message, the 'mimeSrc' object must be a MimeData object. |
Action |
Pass in a MimeData object. MimeData objects are created using the wm.tn.mime:createMimeData service. |
3221 | Input parameter mimeSrc to service createSignedData cannot be null. It should be of type MimeData. |
Class | E |
Explanation |
When trying to create a signed message, the 'mimeSrc' object must be a MimeData object. |
Action |
Pass in a MimeData object. MimeData objects are created using the wm.tn.mime:createMimeData service. |
3222 | Unable to parse message |
Class | E |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3223 | Input parameter mimeSrc should be of type MimeData |
Class | E |
Explanation |
The 'mimeSrc' object must be a MimeData object or an InputStream object. |
Action |
Pass in a MimeData or InputStream object. MimeData objects are created using the wm.tn.mime:createMimeData service. |
3224 | Could not obtain message content |
Class | E |
Explanation |
Error occurred while reading the message content. |
Action |
Check input data source for errors. |
3225 | Content is not of a recognized encryption type |
Class | E |
Explanation |
Cannot process the encrypted message. |
Action |
Contact the sender to re-send the message using the correct format. |
3226 | Given certificate does not decrypt message |
Class | E |
Explanation |
The message was not encrypted for the certificate that was passed to the service. |
Action |
First, validate that the correct certificate is used to decrypt the message. Then, if the certificate is the correct one, contact the message sender to determine which certificate was actually used to create the encrypted message. |
3229 | Cannot Process this object. Write this MimeData to stream, then process that stream. |
Class | E |
Explanation |
Cannot process the object. |
Action |
Write the MimeData to a stream and then process the stream again. |
3230 | Input parameter mimeData must be a MimeData object |
Class | E |
Explanation |
The 'mimeData' input parameter is not a MimeData object. |
Action |
Pass in a MimeData object. MimeData objects are created using the wm.tn.mime:createMimeData service. |
3231 | Message content is not certificates only data. Message could not be processed. |
Class | E |
Explanation |
The message cannot be handled by the wm.tn.mime:processCertsOnlyData service. |
Action |
Use the wm.tn.mime:createMimeMessage service to determine if the message is signed or encrypted. Then use either wm.tn.mime:processSignedData or wm.tn.mime:processEncryptedData as appropriate. |
3232 | Input parameter mimeSrc must be a MimeData object |
Class | E |
Explanation |
The 'mimeSrc' object must be a MimeData object. |
Action |
Pass a MimeData object. MimeData objects are created using the wm.tn.mime:createMimeData service. |
3233 | Message content is not signed data. Message could not be processed |
Class | E |
Explanation |
The message cannot be handled by the wm.tn.mime:processSignedData service. |
Action |
Use the wm.tn.mime:createMimeMessage service to determine if the message is signed or encrypted. Then use either wm.tn.mime:processSignedData or wm.tn.mime:processEncryptedData as appropriate. |
3234 | Signing key is not valid |
Class | E |
Explanation |
The key used to sign the message is invalid. |
Action |
Check certificate format. The certificate must be a DER encoded ASN.1 format. |
3235 | Unable to sign document |
Class | E |
Explanation |
The key used to sign the message is invalid. |
Action |
Check certificate format. The certificate must be a DER encoded ASN.1 format. |
3236 | Invalid signer certificate file information |
Class | E |
Explanation |
The signer certificate chain is invalid. |
Action |
The signer certificate chain must be an array of certificates. |
3237 | Certificate at index {0} not in recognizable format |
Class | E |
Explanation |
Cannot recognize certificate in chain at index: <index>. |
Action |
Check certificate format. The certificate must be a DER encoded ASN.1 format. |
3238 | Invalid certificate input at index {0} |
Class | E |
Explanation |
Cannot recognize certificate in chain at index: <index>. |
Action |
Check certificate format. The certificate must be a DER encoded ASN.1 format. |
3239 | Signature could not be verified |
Class | E |
Explanation |
The signature is invalid. The signature cannot be validated. |
Action |
Contact the message creator to determine what message was originally sent. |
3240 | Expired certificate chain |
Class | E |
Explanation |
A certificate used to sign the message has expired. |
Action |
Notify the message creator that the certificates used to sign the message are invalid. |
3241 | Error in certificate chain |
Class | E |
Explanation |
The certificate chain is invalid. |
Action |
Check certificate format. The certificates must be a DER encoded ASN.1 format. Ensure that the certificates form a chain. If the chain consists of Cert A and Cert B, the issuer of Cert A should be the same as the subject of Cert B. |
3242 | Untrusted certificate |
Class | E |
Explanation |
The certificate used to sign the message is not signed by a trusted certificate authority. On the other hand, the signature is structured correctly. |
Action |
The message should not be trusted because the certificate authority is not trusted. Add the certificate authority to the trusted certificate authorities, or the message creator must use a certificate issued by a trusted certificate authority to sign the message. |
3244 | Error using temporary storage space |
Class | E |
Explanation |
An error occurred when using the temporary storage system. |
Action |
See the webMethods Integration Server User Guide for more details. Additional details are available in the exception message. |
3245 | Unable to parse Encrypted Content. Invalid encrypted data. |
Class | E |
Explanation |
The message cannot be decrypted. |
Action |
Check the server log for additional error information. The stack trace of this error should contain additional information why this message cannot be decrypted. |
3246 | Unable to decrypt data. |
Class | E |
Explanation |
The message could not be decrypted. |
Action |
Check the server log for additional error information. The stack trace of this error should contain additional information why this message cannot be decrypted. |
3247 | Unable to parse Encrypted Content. Private key does not decrypt data. |
Class | E |
Explanation |
The private key used to decrypt the message cannot decrypt the message. |
Action |
First, validate that the correct private key is used to decrypt the message. Then, if the private key is correct, contact the message sender to determine which certificate was used to create the encrypted message. |
3248 | Unable to determine hash algorithm. Parameter micalg was null |
Class | E |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3249 | Unable to determine hash algorithm. Unknown micalg: {0} |
Class | E |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3250 | Improperly formed multipart/signed message |
Class | E |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3251 | Cannot process body part of type {0} |
Class | E |
Explanation |
Error occurred while processing the message. |
Action |
Check the error message and take action as appropriate. |
3252 | Cannot process signed data with content type {0} |
Class | E |
Explanation |
Message does not seem to be a signed message and thus cannot be processed by the wm.tn.mime:processSignedData service. |
Action |
Use the wm.tn.mime:createMimeMessage service to determine if the message is signed or encrypted. Then, use either wm.tn.mime:processSignedData or wm.tn.mime:processEncryptedData as appropriate. Otherwise, obtain the message content by using the wm.tn.mime:getBodyPartContent service. |
3253 | Unable to parse Content Type |
Class | E |
Explanation |
Source data used to construct the MIME message is not a properly structured MIME message. |
Action |
Check the input data. Fix the message to conform to the MIME standard. |
3254 | Unable to compute message digest using algorithm: {0} |
Class | E |
Explanation |
The digest algorithm is either invalid or is not a supported algorithm. |
Action |
Specify a supported algorithm. Valid values for the digest algorithm are: "SHA-1" or "MD5". |
3255 | Either ''profileAlias'' or (''privKey'',''signerCert'') are required |
Class | E |
Explanation |
To execute properly, the service requires either a valid value for 'profileAlias' or a valid value for the 'privKey' and 'signerCert' input parameters. |
Action |
Specify a value for either 'profileAlias', or 'privKey' and 'signerCert'. See the webMethods Trading Networks Built-In Services Reference for more details about this service. |
3256 | Either ''profileAlias'' or (''privKey'',''recipientCert'') are required |
Class | E |
Explanation |
To execute properly, the service requires either a valid value for 'profileAlias', or a valid value for the 'privKey' and 'recipientCert' input parameters. |
Action |
Specify a value for either 'profileAlias', or 'privKey' and 'recipientCert'. See the webMethods Trading Networks Built-In Services Reference for more details about this service. |
3257 | Algorithm {0} not supported |
Class | E |
Explanation |
The message was encrypted using the <algorithmName> algorithm. Cannot decrypt messages encrypted with this algorithm. |
Action |
Can decrypt messages that are encrypted with RC2, TripleDes, or DES algorithms only. |
3258 | Invalid RC2 parameter version: {0} |
Class | E |
Explanation |
This version of the RC2 algorithm is unsupported or invalid. The RC2 algorithm is supported with 40, 64, or 128 bit keys. |
Action |
Contact the message sender to ensure that a supported RC2 key length is being used. |
3259 | Supplied certificate cannot decrypt content |
Class | |
Explanation |
Decryption failed as the available certificates failed to decrypt content. |
Action |
Check if the certificates are correctly mapped to the user. |
3300 | No algorithm specified |
Class | E |
Explanation |
Mandatory 'algorithm' input parameter contained no value. |
Action |
Specify a valid value for the 'algorithm' input parameter. Valid values are either "SHA-1" or "MD5". |
3301 | Specified algorithm {0}, not supported |
Class | E |
Explanation |
The 'algorithm' Input parameter contained an invalid value. |
Action |
Specify a valid value for the 'algorithm' input parameter. Valid values are either "SHA-1" or "MD5". |
3302 | Security provider not found |
Class | E |
Explanation |
An internal error occurred. |
Action |
Contact Software AG Global Support. |
3303 | Input to createMessageDigest must be byte[] or InputStream |
Class | E |
Explanation |
The 'input' parameter must be a byte array or InputStream object. |
Action |
Specify a byte array or InputStream for the 'input' parameter. |
3304 | Parameter ''data'' must be a byte[] or InputStream |
Class | E |
Explanation |
The 'data' input parameter must be a byte array or InputStream object. |
Action |
Specify a byte array or InputStream for the 'data' parameter. |
3305 | Parameter ''signerInfo'' cannot be null |
Class | E |
Explanation |
Mandatory 'signerInfo' input parameter must contain a value. |
Action |
Specify valid information for the 'signerInfo' input parameter. |
3306 | Unable to process ''signerInfo'' at index {0} |
Class | E |
Explanation |
An error occurred attempting to process the signerInfo at index <index>. |
Action |
The server error log contains a stack trace with additional information about the error. |
3307 | Invalid certificate chain |
Class | E |
Explanation |
Cannot recognize certificates. |
Action |
Check certificate format. The certificate must be a DER encoded ASN.1 format. |
3308 | Invalid certificate at index {0} |
Class | E |
Explanation |
Cannot recognize certificate in chain at index: <index>. |
Action |
Check certificate format. The certificate must be a DER encoded ASN.1 format. |
3309 | Required parameter ''signatureStream'' cannot be null. |
Class | E |
Explanation |
Required 'signatureStream' parameter cannot be null. |
Action |
Pass an OutputStream object to the wm.tn.mime:sign service, in the 'signatureStream' parameter. |
3310 | Error occured reading input stream, cannot construct signature. |
Class | E |
Explanation |
Error occurred while reading the message content. |
Action |
Check input data source for errors. |
3311 | Hash Algorithm {0} not supported for signer at index {1} |
Class | E |
Explanation |
Hash Algorithm <algorithmName> not supported for signer at index <index>. |
Action |
Change the <algorithmName> at <index> to be one of the allowed algorithm names: "MD5" or "SHA-1". |
3312 | Bad certificate. Unable to set signer certificates. |
Class | E |
Explanation |
Cannot recognize certificate in chain at index: <index>. |
Action |
Check certificate format. The certificate must be a DER encoded ASN.1 format. |
3313 | Input parameter ''signature'' cannot be null. |
Class | E |
Explanation |
The 'signature' input parameter cannot be null. |
Action |
Pass the signature to verify into the service in the 'signature' input parameter. The 'signature' object should be either a byte array or an InputStream object. |
3314 | Input parameter ''signature'' must be a byte[] or InputStream |
Class | E |
Explanation |
The 'signature' input parameter must be a byte[] or InputStream. |
Action |
The 'signature' input parameter must be a byte[] or InputStream. |
3315 | Input parameter ''data'' required for verifying detached signature |
Class | E |
Explanation |
The 'data' input parameter cannot be null. |
Action |
Pass in the 'data' input parameter of the service, the data that is to be verified. The 'data' object should be either a byte array or an InputStream object. |
3316 | Input parameter ''data'' must be a byte[] or InputStream |
Class | E |
Explanation |
The 'data' input parameter must be a byte[] or InputStream. |
Action |
The 'data' input parameter must be a byte[] or InputStream. |
3317 | An error occured while attempting to verify the signature. |
Class | E |
Explanation |
Problem while reading from input data source. |
Action |
Check input data source for errors. |
3318 | Signature provided is not PKCS#7 SignedData |
Class | E |
Explanation |
Signature provided is not PKCS#7 SignedData. |
Action |
The wm.tn.mime:verify service can verify PKCS#7 SignedData signature only. |
3319 | Input parameter ''outputStream'' must be an OutputStream |
Class | E |
Explanation |
The 'outputStream' input parameter must be an OutputStream. |
Action |
The 'outputStream' input parameter must be an OutputStream. |
3320 | Input contained no signer information when processed as {0} type signature |
Class | E |
Explanation |
The message is not properly signed. |
Action |
This message cannot be verified. Contact the message creator to verify the proper message structure. |
3321 | Parameter ''data'' must be null when parameter detachedSignature equals false. |
Class | E |
Explanation |
The 'data' parameter must be null when 'detachedSignature' parameter equals to false. |
Action |
If the signature is detached, then set the 'detachedSignature' parameter to "true". Otherwise, do not pass in a value for 'data'. The signed message should be passed in via the 'signature' input parameter. |
3322 | Parameter ''data'' must not be null |
Class | |
Explanation |
The 'data' input parameter cannot be null. |
Action |
Pass the data into the service in the 'data' input parameter. The 'data' object should be either a byte array or an InputStream object. |
3323 | Certificate chain cannont be null |
Class | E |
Explanation |
Certificate chain cannot be null. |
Action |
Specify a certificate chain to use to sign this message. |
3324 | Private key or keyAlias required |
Class | E |
Explanation |
Private key or keyAlias required. |
Action |
To sign this message, specify either a private key, or use a keyAlias. |
3325 | Unable to decode signed message. Verify that signature type specified (detached or implicit) matches actual type. |
Class | E |
Explanation |
Unable to decode the signed message. |
Action |
Verify that the specified signature type (detached or implicit) matches the actual type. |
3326 | Unable to create digest. Input parameter ''data'' must be of type com.wm.app.tn.mime.DigestableInputStream or byte[]. |
Class | |
Explanation |
Error while creating message digest. |
Action |
Check that the input parameter is passed correctly. Input parameter 'data' must be of type com.wm.app.tn.mime.DigestableInputStream, or byte[]. |
3327 | Unable to write message to outputStream. |
Class | E |
Explanation |
Error occurred while writing the signed message. |
Action |
The server error log contains a stack trace with additional information about the error. |
3328 | Only one ''{0}'' can be specified in ''signerInfo'' |
Class | E |
Explanation |
When signing a message using a profile alias, you can only use one alias. |
Action |
Sign the message with only one profile alias. |
3400 | Values are required for both input parameters type and id |
Class | E |
Explanation |
Values are required for both 'type' and 'id' input parameters. |
Action |
Set the 'type' input parameter to "file" and the 'id' parameter to the name of the file that the InputStream will read from. |
3401 | Input parameter type cannot be null |
Class | E |
Explanation |
Values are required for both 'type' and 'id' input parameters. |
Action |
Set the 'type' input parameter to "file" and the 'id' parameter to the name of the file that the InputStream will read from. |
3402 | Input parameter id cannot be null |
Class | E |
Explanation |
Values are required for both 'type' and 'id' input parameters. |
Action |
Set the 'type' input parameter to "file" and the 'id' parameter to the name of the file that the InputStream will read from. |
3403 | Unable to open SharedInputStream |
Class | E |
Explanation |
An error occurred while reading from the specified data source. |
Action |
Check that the specified data source exists. The Integration Server error log should contain additional error information. |
3404 | Value ''{0}'' for parameter type is not supported. Please select from allowed values. |
Class | E |
Explanation |
The 'type' input parameter must be set to "file". |
Action |
Provide an allowed value. The 'type' input parameter must be set to "file". |
3501 | Parameter ''{0}'' must not be null |
Class | E |
Explanation |
The parameter called <parameterName> must be available but it does not exist in the pipeline . |
Action |
Specify a valid value for the <parameterName> parameter. |
4001 | No profile store to validate partner ID |
Class | E |
Explanation |
Unable to retrieve the profile store, probably due to a database error or a validation error. |
Action |
Check that the data is not corrupted or the database connection is active. |
4002 | Error transforming attribute {0}: {1} |
Class | E |
Explanation |
An exception was thrown while transforming a document attribute value. |
Action |
The exception was written to the server log. See the log for details. Take appropriate action to resolve the problem described in the exception. |
4003 | BizDocAttribute: can''t connect to profile store |
Class | E |
Explanation |
Encountered an exception during initialization. |
Action |
Contact Software AG Global Support. Prepare the following information: server and error logs, a copy of the Support Information page from the Trading Networks Console, and the WmTN/config/properties.cnf file. |
4006 | No profile store to transform attribute {0} |
Class | E |
Explanation |
Trading Networks was unable to retrieve the profile store. |
Action |
The exception was written to the server log. See the log for details. Take appropriate action to resolve the problem described in the exception. |
4007 | Unable to transform attribute {0}: attribute type {1} doesn''t match function type {2} |
Class | E |
Explanation |
Trading Networks could not transform the value of the attribute because the selected transformation is inappropriate for the data type of the attribute. |
Action |
Using My webMethods, update the TN document type that specifies the invalid transformation for the specified attribute. Select a transformation that is appropriate for the data type of the attribute. |
4008 | Error fetching all attributes: {0} |
Class | E |
Explanation |
An exception was thrown while reading all attributes from the database. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4009 | Error defining attribute {0}: {1} |
Class | E |
Explanation |
An exception was thrown while saving an attribute to the database. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4010 | Error listing types for {0}: {1} |
Class | E |
Explanation |
An exception was thrown while retrieving all TN document types that use an attribute. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4011 | Error redefining attribute {0}: {1} |
Class | E |
Explanation |
An exception was thrown while updating an attribute in the database. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4012 | Supplied value must be a number |
Class | E |
Explanation |
A processing rule contains extended criteria that uses a custom attribute with a NUMBER data type. However, the value you specified in the condition for this attribute is not a numeric value. |
Action |
Using My webmethods, update the extended criteria in the processing rule to provide a numeric value for attributes that have a NUMBER data type. |
4013 | Supplied value can not be transformed to a date |
Class | E |
Explanation |
A processing rule contains extended criteria that uses a custom attribute with a DATETIME data type. However, the value you specified in the condition for this attribute is not a date. |
Action |
Using My webmethods, update the extended criteria in the processing rule to supply a date value for attributes that have a DATETIME data type. |
4014 | {0} attribute value is a date but there is no transform. |
Class | E |
Explanation |
A TN document type indicates that a custom attribute with a DATETIME data type should be extracted from a document. However, the TN document type does not specify a date transformation for the custom attribute. |
Action |
Using My webmethods, update the TN document type to specify an appropriate date transformation for the custom attribute. |
4015 | {0} attribute is configured for custom transformation, but no transformation service is specified. |
Class | E |
Explanation |
A TN document type indicates that a custom attribute should perform custom attribute transformation. However, the TN document type does not specify a transformation service. |
Action |
Using My webMethods, update the TN document type to specify a transformation service. |
4016 | Error performing custom transformation on the {0} attribute. |
Class | E |
Explanation |
Encountered an exception while updating an attribute in the database. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4017 | Custom transformation {0} for the {1} attribute returned the wrong type. Should be {2} |
Class | E |
Explanation |
Custom attribute transformation did not return the data type that matches the data type of the associated attribute. |
Action |
Modify the custom attribute transformation service to return the correct data type specified in the error message. |
4018 | Custom transformation service {0} for the {1} attribute did not return "newValues" in the pipeline. |
Class | E |
Explanation |
Custom attribute transformation service did not return the required output parameter 'newValues'. |
Action |
Modify the custom attribute transformation service to return the 'newValues' output parameter. |
4019 | {0} attribute value is a date list but there is no transform. |
Class | E |
Explanation |
The TN document type does not specify a transformation for a date list type attribute. |
Action |
Using My webMethods, update the TN document type to specify a transformation service. |
4020 | Unable to parse the given value. Value {0} could not be converted to date format |
Class | E |
Explanation |
Unable to convert the value extracted from the document to a date format. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4021 | Attribute transformation for {0} of doctype {1} generated an exception. The original exception message is: {2}. |
Class | E |
Explanation |
Encountered an exception while updating an attribute in the database. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4022 | Attribute transformation function code {0} is invalid. |
Class | E |
Explanation |
A TN document type indicates an invalid attribute transformation function. |
Action |
Using My webMethods, update the TN document type to specify a valid transformation function. |
5006 | Converting the signed body of this document into a string failed. Verification cannot continue. The original signed body was {0}. |
Class | E |
Explanation |
Conversion failed for a document. |
Action |
If the signed body of the document is invalid, notify the document sender. |
5008 | This doctype ({0}) has no verification service defined. Verification cannot continue. |
Class | E |
Explanation |
This TN document type (<doctypeName>) has no verification service defined. |
Action |
If you are using a built-in TN document type, contact Software AG Global Support. If you are using your own TN document type, specify a verification service for it. |
5009 | No Verification Service |
Class | E |
Explanation |
The TN document type has no verification service defined. Verification cannot continue. |
Action |
If you are using a built-in TN document type, contact Software AG Global Support. If you are using your own TN document type, specify a verification service for it. |
5011 | The signature query for doctype {0} ({1}) generated an error. The error was {2}. |
Class | E |
Explanation |
The signature query (<query>) for the TN document type (<doctypeName>) generated an error. The error was <exceptionMessage>. |
Action |
If the signed body of the document is invalid, notify the document sender. |
5015 | Query Failed |
Class | E |
Explanation |
A signature query was defined for the TN document type but it failed to produce a result for this document. |
Action |
Either adjust the signature query that is defined in the TN document type, or notify the document sender that the structure of the document is incorrect. |
5017 | This document type ({0}) is missing one or both of its signature queries (Signature and SignedBody). Verification cannot proceed. |
Class | E |
Explanation |
One or both of this document type signature queries (Signature and SignedBody) may be missing. |
Action |
Using My webMethods, update the TN document type to specify both, a signature query and a signed body query. |
5018 | Missing Signature Query(s) |
Class | E |
Explanation |
This TN document type is missing one or both of its signature queries (Signature and SignedBody). Trading Networks cannot proceed with the verification of the signature. |
Action |
Using My webMethods, update the TN document type to specify both, a signature query and a signed body query. |
5019 | The signed body query for doctype {0} ({1}) generated an error. The error was {2}. |
Class | E |
Explanation |
The signed body query (<query>) for the TN document type (<doctypeName>) generated an error. The error was <exceptionMessage>. |
Action |
Take appropriate action to resolve the problem described in the exception. If the structure of the document is incorrect, notify the document sender. |
5020 | The signature of this document was invalid; no information was available about the party or parties that signed it. |
Class | E |
Explanation |
The signature of this document might be invalid. |
Action |
Notify the document sender. |
5021 | No Signer Info Available |
Class | E |
Explanation |
The signature of this document was not valid. No information was available about the party or parties that signed it. |
Action |
Notify the document sender. |
5022 | The PKCS verification service, pub.security.pkcs7:verify, produced an error trying to verify this document. The error was {0}. |
Class | E |
Explanation |
Encountered an exception while verifying a document signature. |
Action |
Take appropriate action to resolve the problem described in the exception. If the signature is invalid, notify the document sender. |
5023 | PKCS Service Error |
Class | E |
Explanation |
The PKCS verification service pub.security.pkcs7:verify, produced an error while trying to verify this document. |
Action |
Take appropriate action to resolve the problem described in the exception. If the signature is invalid, notify the document sender. |
5024 | The verification service for this document ({0}) generated an error. The original error was {1}. |
Class | E |
Explanation |
An exception was thrown while verifying a document signature. |
Action |
Take appropriate action to resolve the problem described in the exception. If the signature is invalid, notify the document sender. |
5025 | Verification Failed |
Class | E |
Explanation |
An exception was thrown while verifying a document signature. |
Action |
Take appropriate action to resolve the problem described in the exception. If the signature is invalid, notify the document sender. |
5026 | The signature query for doctype {0} ({1}) failed to produce a value. Without a signature, verification cannot proceed. |
Class | E |
Explanation |
A signature query was defined for the TN document type but it failed to produce a result for this document. |
Action |
Either update the TN document type to adjust the signature query, or notify the document sender that the structure of the document is incorrect. |
5028 | The signed body query for doctype {0} ({1}) failed to produce a value. Without a signed body, verification cannot proceed. |
Class | E |
Explanation |
A signed body query was defined for the TN document type but it failed to produce a result for this document. |
Action |
Either update the TN document type to adjust the signed body query, or notify the document sender that the structure of the document is incorrect. |
5030 | Base-64 decoding the signature for this document failed to produce a value. The signature (before decoding) was {0,number} bytes. |
Class | E |
Explanation |
An error occurred while decoding the signature. The signature might be invalid. |
Action |
Notify the document sender. |
5031 | Decoding Error |
Class | E |
Explanation |
Trading Networks could not decode the signature. The signature might be invalid. |
Action |
Notify the document sender. |
5032 | XML {0} failed: does not apply to non-XML documents |
Class | E |
Explanation |
Trading Networks attempted to perform an operation on a non-XML document. However, the operation can be performed only on XML documents. |
Action |
Check whether the input document is a valid XML document. |
5033 | XML {0} failed: no document content available |
Class | E |
Explanation |
Trading Networks attempted to perform an operation that failed because the document has no content. |
Action |
Notify the document sender. |
5034 | Bad XML content |
Class | E |
Explanation |
An exception was thrown while retrieving the document. |
Action |
The document may not be a valid XML document. |
5035 | An error prevented fetching the content of this XML document for {0}. The original error was {2}. |
Class | E |
Explanation |
An exception was thrown while retrieving the document. |
Action |
Check the database and make sure that the data is not corrupted. |
5036 | Signature Verification failed : The verification service, {0} aborted processing of this document. The message was {1}. |
Class | E |
Explanation |
A RoutingAbortedException was thrown by the verification service that caused the document processing to abort. |
Action |
Take appropriate action to resolve the problem described in the exception. If the document is invalid, notify the sender. |
5037 | The signing service, {0} aborted processing of this document. The message was {1}. |
Class | E |
Explanation |
A RoutingAbortedException was thrown by the verification service, which caused the document processing to abort. |
Action |
Take appropriate action to resolve the problem described in the exception. If the document is invalid, notify the sender. |
6001 | Attribute transform for {0} of doctype {1} failed to produce a value. The transform function was {3}, the first original value was {2}. |
Class | E |
Explanation |
The data type of the attribute might not match the type of the data extracted from the document. |
Action |
Make sure that the data type of the attribute matches the type of the data extracted from the document. If this is an XML TN document type, make sure that the XQL query that extracts the attribute is correct. |
6002 | Attribute query for {0} of doctype {1} failed to produce a result. The document may not be complete. The query was: {2} |
Class | E |
Explanation |
The XQL query for the attribute did not return a value. |
Action |
Change the XQL query accordingly to return correct result. |
6003 | Attribute query for {0} of doctype {1} generated an exception. The original exception message is: {2}. |
Class | E |
Explanation |
There is either a problem with the document, or with the query. |
Action |
Examine the document to see if it is well-structured XML. Correct and resubmit if needed. Examine the query to ensure that it is valid. Change the query if needed. |
6004 | Unable to get XML content for corrupted doc {0}. The original exception message is: {1}. |
Class | E |
Explanation |
The document may be corrupted. |
Action |
Fix the document and submit it again. |
6005 | Transform for {0} of doctype {1} generated an exception. The transform function was {2}. The original exception message is: {3}. |
Class | E |
Explanation |
There is either a problem with the document, or with the query. |
Action |
Examine the document to ensure that it is well-structured XML. Correct and resubmit if needed. Examine the query to ensure that it is valid. Adjust the query if needed. |
6006 | Transform for {0} of doctype {1} failed to produce a value. The transform function was {3}, the first original value was {2}. |
Class | E |
Explanation |
Perhaps the data type of the attribute does not match the type of the data extracted from the document. |
Action |
Make sure that the data extracted from the document is the same type as the attribute. If this is an XML TN document type, make sure that the XQL query that extracts the attribute is correct. |
6007 | Envelope query for {0} of doctype {1} failed to produce a result. The document may not be complete. The query was: {2} |
Class | E |
Explanation |
The XQL query for the attribute did not return a value. |
Action |
Fix the XQL query, if needed. |
6008 | Envelope query for {0} of doctype {1} generated an exception. The original exception message is: {2}. |
Class | E |
Explanation |
The document may be corrupted. |
Action |
Correct the document and submit it again. |
6009 | There was an error in trying to get XML header information (DOCTYPE and DTD). The document ({0}) is probably not valid XML. |
Class | E |
Explanation |
Probably, the document is not a well-structured XML. |
Action |
Correct the document and submit it again. |
6010 | There was an error in trying to get XML header information (DOCTYPE and DTD). The document ({0}) is probably not valid XML. The original exception message is: {1} |
Class | E |
Explanation |
Probably, the document is not a well-structured XML. |
Action |
Correct the document and submit it again. |
6011 | XQL query {1} failed recognizing document {0}. The document is probably not valid XML. The original exception message is: {2}. |
Class | E |
Explanation |
Probably, the document is not a well-structured XML. See the exception message for details. |
Action |
Correct the document and submit it again. |
6013 | No bizdoc supplied to lookup validation schema |
Class | E |
Explanation |
The wm.tn.doc.xml:getRecordBlueprint service was invoked with no BizDocEnvelope in the pipeline. |
Action |
Supply a BizDocEnvelope when invoking the wm.tn.doc.xml:getRecordBlueprint service. |
6014 | Non-XML bizdoc supplied to lookup validation schema |
Class | E |
Explanation |
The BizDocEnvelope passed to the wm.tn.doc.xml:getRecordBlueprint service is not an XML document type. |
Action |
Supply a BizDocEnvelope that matches an XML TN document type when invoking the wm.tn.doc.xml:getRecordBlueprint service. |
6015 | No bizdoc ID supplied for testing validation |
Class | E |
Explanation |
The wm.tn.doc.xml:testValidate service was invoked with no internal document ID in the pipeline. |
Action |
Supply an internal document ID (docID) when invoking the wm.tn.doc.xml:testValidate service. |
6016 | No such bizdoc: {0} |
Class | E |
Explanation |
The wm.tn.doc.xml:testValidate service was invoked with an invalid internal document ID in the pipeline. |
Action |
Provide a valid internal document ID when invoking the wm.tn.doc.xml:testValidate service. |
6017 | Required attribute is missing |
Class | E |
Explanation |
An attribute is defined as required by the document type but the document that matched the document type did not contain this attribute. |
Action |
Either change the document type so that this attribute is no longer required, or instruct the document sender to supply a value for the attribute. |
6018 | The {0} attribute is required by the {1} doctype. The query {2} did not return any results |
Class | E |
Explanation |
An attribute is defined as required by the document type but the document that matched the document type did not contain this attribute. |
Action |
Either change the document type so that this attribute is no longer required, or instruct the document sender to supply a value for the attribute. |
6019 | Attribute transformation for {0} of doctype {1} generated an exception. The query is {2}. The original exception message is: {3}. |
Class | E |
Explanation |
Encountered an exception. |
Action |
If the document is corrupted, notify the document sender. |
7003 | Error while getting {0}. Find if the EDI package is enabled and running in Integration Server. |
Class | |
Explanation |
WmEDI Package may be disabled. |
Action |
Check if the WmEDI package is enabled and running in Integration Server. |
7004 | Error while getting EDI Standards. Input for standard field cannot be null, its is a mandatory field. |
Class | |
Explanation |
Input for standard field cannot be null, it is a mandatory field. |
Action |
Configure the standard field in the input and run the service. |
7005 | Error while getting EDI Transactions. Input for standard field cannot be null, its is a mandatory field. |
Class | |
Explanation |
Input for standard field cannot be null, it is a mandatory field. |
Action |
Configure the standard field and run the query again. |
7006 | Error while getting EDI Transactions. Input for version field cannot be null, its is a mandatory field. |
Class | |
Explanation |
Input for version field cannot be null, it is a mandatory field. |
Action |
Configure the version field and run the query again. |
7007 | Error while getting {0}. Input for {1} field cannot be null, its is a mandatory field. |
Class | |
Explanation |
Input field suggested in error message is a mandatory field. |
Action |
Configure the input field and run the query again. |
7008 | Error while querying for document attributes. |
Class | |
Explanation |
Encountered an exception while querying document attributes. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
7009 | Error while getting the related doctypes for doctype attribute {0}. |
Class | |
Explanation |
An error occurred while getting related doctypes for the associated doctype attribute. The error may be because of an SQLException. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
7010 | Error while changing the status of the doctype attributes. |
Class | |
Explanation |
An error occurred while changing the status of the doctype attributes. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
7011 | Error while getting doctype attribute for doctype attribute ID {0}. |
Class | |
Explanation |
An error occurred while getting doctype attribute for the associated attribute ID. This may be because of an SQLException while querying the attribute. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
7012 | Error while updating doctype attribute for doctype attribute ID {0}. |
Class | |
Explanation |
An error occurred while updating the doctype attribute. This may be because of an SQLException while updating the attribute. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
7013 | Error while changing the status of the doctype attribute ID {0}. |
Class | |
Explanation |
An error occurred while updating the doctype attribute. This may be because of an SQLException while updating the attribute. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
7014 | Error while viewing doctype attribute. Input for docAttrID field cannot be null, its is a mandatory field. |
Class | |
Explanation |
An error occurred while viewing the doctype attribute. This may be because of an SQLException while querying for the attribute. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
7015 | Error while updating doctype attribute. Input for docAttrID field cannot be null, its is a mandatory field. |
Class | |
Explanation |
Input for docAttrID field cannot be null, it is a mandatory field. |
Action |
Configure the docAttrID field while updating the doctype attribute. |
7016 | Error while adding doctype attribute. Check whether all input variables have been passed properly. |
Class | |
Explanation |
Some mandatory fields may not have been passed before calling the service. |
Action |
Configure all input variables before calling the service. |
7017 | Attribute name "{0}" already exists. Change the name and save again. |
Class | E |
Explanation |
Attribute with the same name already exists. |
Action |
Change the attribute name and save. |
7018 | Error while updating doctype attribute. Attribute name with "{0}" already exists. Change the name and save again. |
Class | |
Explanation |
Attribute with same name already exists. |
Action |
Change the name and save. |
7019 | Error while querying for document attributes {0}. |
Class | |
Explanation |
An error occurred while querying doctype attributes. This may be because of an SQLException while querying the attribute. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
1001 | "{0}" is empty. At least one {1} must be supplied. Please supply the required value. |
Class | E |
Explanation |
You did not supply a value for the specified variable. At least one value is required. |
Action |
Supply at least one value for the specified field and try again. |
1002 | "{0}" and "{1}" are required ({0}={2}, {1}={3}). Please supply the required values. |
Class | E |
Explanation |
Both values are required. |
Action |
Supply both values. |
1009 | The value originally supplied as sender ID for this document was not a valid partner ID. The value was {0}. |
Class | E |
Explanation |
Partner ID supplied as sender ID is not being recognized as valid partner. |
Action |
Either create a partner profile for the document sender, add this ID to an existing partner's profile, or tell the document sender to resend the document using a different sender ID value. |
1010 | Error formatting error message {0}: {1} |
Class | E |
Explanation |
Unable to format the error message. |
Action |
Contact Software AG Global Support. |
1011 | The value originally supplied as receiver ID for this document was not a valid partner ID. The value was {0}. |
Class | E |
Explanation |
Partner ID supplied as receiver ID is not being recognized as valid partner. |
Action |
Either create a partner profile for the document receiver, add this ID to an existing partner's profile, or tell the document sender to resend the document using a different receiver ID value. |
1012 | {0} is null. |
Class | E |
Explanation |
An internal variable is unexpectedly null. |
Action |
Contact Software AG Global Support. |
1013 | At least one of "{0}" and "{1}" is required. |
Class | E |
Explanation |
At least one of the input fields is required, either its null or empty. |
Action |
Provide non-null value for at least one input parameter and try again. |
1016 | "sourceVersion" is required. Please supply the required value. |
Class | E |
Explanation |
A required value is missing. |
Action |
Supply the required value. |
1017 | "feature" is required. Please supply the required value. |
Class | E |
Explanation |
A required value is missing. |
Action |
Supply the required value. |
1018 | At least one input is required. |
Class | E |
Explanation |
All input fields are found to be null, at least one input should not be null. |
Action |
Provide at least one non-null value for input and try again. |
1019 | Enumeration contains elements that are not Strings. |
Class | E |
Explanation |
An unexpected value was passed to an internal method. |
Action |
Contact Software AG Global Support. |
1021 | schema cannot be null. |
Class | E |
Explanation |
Attempted to create a Trading Networks IData object with an empty set of name/value pairs. |
Action |
Contact Software AG Global Support. |
1022 | schema rows must be 2 wide |
Class | E |
Explanation |
Attempted to create a Trading Networks IData object without set of name/value pairs. |
Action |
Contact Software AG Global Support. |
1023 | keys cannot be null |
Class | E |
Explanation |
Attempted to create a Trading Networks IData object with keys as null. Keys cannot be null. |
Action |
Contact Software AG Global Support. |
1024 | index out of bounds: {0} |
Class | E |
Explanation |
Attempted to seek beyond the end of or before the start of a TNFixedData object. |
Action |
Supply a valid index to the seek method. |
1025 | TNFixedData does not support setKey |
Class | E |
Explanation |
Attempted to use an unsupported method. |
Action |
Do not call the setKey method. |
1027 | TNFixedData does not support delete |
Class | E |
Explanation |
Attempted to use an unsupported method. |
Action |
Do not call the delete method. |
1028 | illegal null key |
Class | E |
Explanation |
Supplied a null key to the keyMatch method on a TNFixedData object. |
Action |
Supply a valid key value. |
1031 | Must supply props |
Class | E |
Explanation |
A required value(props) is missing for wm.tn.admin:setProperties(). |
Action |
Supply the required value for field(props) and try again. |
1032 | Must shutdown before starting up again |
Class | E |
Explanation |
Invoked the wm.tn.admin:startup service while the WmTN package is enabled and loaded. |
Action |
Use the Integration Server Administrator to stop and start the WmTN package. Do not invoke the wm.tn.admin:start service directly. |
1042 | No such enum: {0} |
Class | E |
Explanation |
A wm.tn.enumerate service was invoked with an invalid query enumeration identifier. |
Action |
Supply a valid enumeration identifier. |
1043 | Either {0} or {1} must be supplied. Please supply one of these values. |
Class | E |
Explanation |
A valid value for either of the required field was not supplied. |
Action |
Supply one of the valid values which are listed in the error message. |
1044 | {0} is required whenever a value for {1} is supplied. Please supply a value for {0}. |
Class | E |
Explanation |
A storageRef value was supplied, but no value was supplied for storageType. |
Action |
Supply a value for the storageType variable. Either supply value for both related fields or keep both fields null and try again. |
1047 | The following TN properties can only take numeric values: {0} |
Class | E |
Explanation |
Attempted to assign non-numeric values to numeric system properties. |
Action |
Supply numeric values for numeric system properties. |
1048 | Error setting features on SAX parser. Exception message is: {0} |
Class | E |
Explanation |
Threw a SAXException while initializing the SAX parser. |
Action |
Contact Software AG Global Support. |
1056 | The {0} service is for Trading Networks internal use only. |
Class | E |
Explanation |
The specified service was invoked, but not by Trading Networks. This service is for Trading Networks internal use only. |
Action |
Do not invoke this service. |
1057 | Error encountered in invoking service wm.tn.samples.helpServices:installTNSamplesACLs |
Class | E |
Explanation |
Internal error installing ACLs for Trading Networks Sample services. |
Action |
If you want to protect the WmTNSamples services, invoke the wm.tn.samples:installTNSamplesACLs service. |
1058 | Error encountered in writing TN ACL information to disk |
Class | E |
Explanation |
An exception was thrown saving the Trading Networks ACLs to the file system. |
Action |
The exception was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
1059 | ThreadQueue: too many jobs waiting |
Class | E |
Explanation |
Attempted to spawn more threads than the configured limit. |
Action |
Use the wm.tn.admin:setThreadQueueConfig service to increase the value of the tn.thread.maxWaiting system property. |
1061 | {0} is not an Integer |
Class | E |
Explanation |
Invalid data type supplied to a service, expected an Integer value |
Action |
Supply an Integer for the specified field. |
1065 | Error encountered while unregistering TN''s XML content handler. The exception message is: {0} |
Class | |
Explanation |
Error occurred while unregistering TN's content handler and activating default XML content handler. |
Action |
See the server log for details. Take appropriate action to resolve the problem described in the exception. |
1066 | When scheduleType is {0}, a value must be supplied for {1}. Please supply a value for {1}. |
Class | |
Explanation |
Attempted to create new queue with schedule values null for a selected scheduleType. |
Action |
Supply valid values corresponding to selected schedule type. |
1067 | Unable to update password for {0} with handle {1} |
Class | E |
Explanation |
An exception was thrown when Trading Networks attempted to update the password associated with a profile delivery method. |
Action |
Take appropriate action to resolve the problem described in the exception. |
1068 | Unable to retrieve password for {0} with handle {1} |
Class | E |
Explanation |
An exception was thrown when Trading Networks attempted to retrieve the password associated with a profile delivery method. |
Action |
Take appropriate action to resolve the problem described in the exception. |
1069 | Unable to insert password for {0} with handle {1} |
Class | E |
Explanation |
An exception was thrown when Trading Networks attempted to insert the password associated with a profile delivery method. |
Action |
Take appropriate action to resolve the problem described in the exception. |
1070 | Unable to save password for {0} with handle {1} |
Class | E |
Explanation |
An exception was thrown when Trading Networks attempted to save the password associated with a profile delivery method. |
Action |
Take appropriate action to resolve the problem described in the exception. |
1071 | Unable to delete password for {0} with handle {1} |
Class | E |
Explanation |
An exception was thrown when Trading Networks attempted to delete the password associated with a profile delivery method. |
Action |
Take appropriate action to resolve the problem described in the exception. |
1072 | Either {0} or {1} must be supplied, but not both. Please supply a value for only one of these. |
Class | E |
Explanation |
You supplied the specified two values; however, only one value can be specified. |
Action |
Supply value for either partByets or partStream and try again. |
1073 | Unable to import document type {0}. Attribute {1} is used in the document type but, it is not defined. |
Class | |
Explanation |
While importing a doctype, related attribute not found, so unable to import the doctype. |
Action |
Please either import the related attribute or define before importing the doctype. |
1075 | Unable to import processing rule {0}. Sender profile {1} is used in the processing rule but, it is not defined. |
Class | |
Explanation |
While importing a processing rule, related sender profile not found, so unable to import the processing rule. |
Action |
Either import the related sender profile or define it before importing the processing rule. |
1076 | Unable to import processing rule {0}. Receiver profile {1} is used in the processing rule but, it is not defined. |
Class | |
Explanation |
While importing a processing rule, related receiver profile not found, so unable to import the processing rule. |
Action |
Either import the related receiver profile or define it before importing the processing rule. |
1077 | Unable to import processing rule {0}. Document type {1} is used in the processing rule but, it is not defined. |
Class | |
Explanation |
While importing a processing rule, related Document Type not found, so unable to import the processing rule. |
Action |
Either import the related document type or define it before importing the processing rule. |
1081 | Error encountered while extracting doctype with doctypeID {0}. Please check whether it is a valid ID. |
Class | |
Explanation |
Could not retrieve Document Type from BizDocStore with provided docTypeID, would not be able to enable/update doc type for monitoring. |
Action |
Please check whether provided docTypeID is a valid ID, as system was not able to retrieve corresponding Document Type from store. |
1083 | Error encountered while setting TN BAM Monitoring status to {0} |
Class | |
Explanation |
Error encountered while enabling/disabling TN BAM monitoring. This happened while setting monitoring properties invoking service wm.tn.admin:setProperties(). |
Action |
Please see the error log. |
2005 | Error(s) encountered in WmTN initialization: {0} |
Class | S |
Explanation |
Encountered an exception while Trading Networks was initializing.This happened during filling the cache of attribute, type, routing rule and profile. |
Action |
Take appropriate action to resolve the problem described in the exception and try to reload the package. |
2013 | The wm.tn.access:getConsoleRestrictions service has been deleted, renamed or replaced. Aborting Trading Networks initialization. |
Class | S |
Explanation |
Aborting Trading Networks initialization as the wm.tn.access:getConsoleRestrictions service has been tempered. |
Action |
Please contact your administrator to restore the original version of this service. |
2014 | Error filling BizDocAttributeStore cache |
Class | E |
Explanation |
Encountered an error while reading the document attributes from the database during startup. |
Action |
An exception was written to the server log. Take appropriate action to resolve the problem described in the exception. |
2018 | Unable to register content types with the FlatFile Content Handler. The WmFlatFile package may be disabled. The WmFlatFile package must be enabled in order to use FlatFile capabilities in Trading Networks. |
Class | W |
Explanation |
The WmFlatFile package is disabled. Unable to register content types with the FlatFile Content Handler. |
Action |
The WmFlatFile package may be disabled. The WmFlatFile package must be enabled in order to use FlatFile capabilities in Trading Networks. |
3007 | wm.tn.admin:installACLs: Unable to find group, {0} |
Class | E |
Explanation |
The specified group, <group>, has not been created. |
Action |
Run the wm.tn.admin:install service to create the Trading Networks user groups. |
3010 | Can not create IS user group {0} |
Class | S |
Explanation |
An exception was thrown while creating a user group during server startup. |
Action |
Contact Software AG Global Support. |
3011 | Can not create IS user {0} |
Class | E |
Explanation |
An exception was thrown while creating a user during server startup. |
Action |
Contact Software AG Global Support. |
4011 | Error encountered during TN server starting: {0} |
Class | E |
Explanation |
An exception was thrown while Trading Networks was starting. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4012 | Error encountered during TN server stopping: {0} |
Class | E |
Explanation |
An exception was thrown while Trading Networks was stopping. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4013 | Error encountered during TN server restarting: {0} |
Class | E |
Explanation |
An exception was thrown while Trading Networks was restarting. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4019 | TN database connection pool failed: error initializing Datastore |
Class | E |
Explanation |
An exception was thrown while initializing the Trading Networks database connection pool. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. Check TN DB configuration details. |
4020 | TN Server failed starting up: error initializing database connection pool |
Class | E |
Explanation |
An exception was thrown while initializing the Trading Networks database connection pool. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. Check TN DB configuration details. |
4021 | TN Server failed starting up: OEM restriction was hacked |
Class | E |
Explanation |
A user or developer attempted to bypass the OEM restrictions. The server will not start. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4024 | TN task manager encountered error: {0} |
Class | E |
Explanation |
An exception was thrown that has terminated execution of the task manager. |
Action |
Take appropriate action to resolve the problem described in the exception. You might need to contact Software AG Global Support. |
4025 | TN temporary storage space initialization failed: {0} |
Class | E |
Explanation |
An exception was thrown while preparing temporary disk space for large files. |
Action |
Take appropriate action to resolve the problem described in the exception. You might need to change the tn.tspace.location system property to a disk partition that has more free space. |
4028 | Invalid notification type encountered in pkginit:sendNotif |
Class | E |
Explanation |
Internal error. |
Action |
Contact Software AG Global Support. |
4039 | MBean cannot record statistics for document id {0}. Document does not exist. |
Class | E |
Explanation |
Internal error. |
Action |
Contact Software AG Global Support. |
4040 | Exception thrown while saving document processing statistics. |
Class | E |
Explanation |
Error encountered while saving document processing statistics to DB. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
1001 | Invalid datatype. "cert" must be a byte[] or a X509Certificate. |
Class | E |
Explanation |
You invoked a service and supplied a digital certificate value that is not a recognized data type. |
Action |
Supply either an X509Certificate or the bytes from an X509Certificate. |
1005 | The user associated with this certificate ({0}) does not have a TN profile. |
Class | E |
Explanation |
The supplied digital certificate is associated with an Integration Server user, but that user is not a Trading Networks partner. |
Action |
Either create a partner profile for the user, or supply a certificate that is associated with a Trading Networks partner. |
1007 | An error occurred when the intended receiver tried to accept this document. The original error message was {0}. |
Class | E |
Explanation |
An exception was thrown while accepting a polled document. |
Action |
Take appropriate action to resolve the problem described in the exception. |
1008 | Unable to retrieve partner profile associated with supplied certificate. |
Class | E |
Explanation |
An exception was thrown while retrieving the partner associated with a digital certificate. |
Action |
Trading Networks wrote the exception to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
1010 | Unable to save partner''s certificate. |
Class | E |
Explanation |
An exception was thrown while saving a partner's certificate. |
Action |
Trading Networks wrote the exception to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
1015 | Unable to retrieve signing keys to be used for sending documents to specified partner. |
Class | E |
Explanation |
The wm.tn.access:getSigningKeys service was unable to retrieve the security information needed to sign documents sent to a partner. |
Action |
Trading Networks wrote the exception to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
1028 | Invalid feature specified. |
Class | E |
Explanation |
While checking whether a feature was enabled, Trading Networks discovered that an invalid feature was specified. |
Action |
Contact Software AG Global Support. |
1029 | Error retrieving Console restrictions. |
Class | E |
Explanation |
An exception was thrown while determining what features are available to My webMethods Server. |
Action |
Contact Software AG Global Support. |
1030 | No session available |
Class | E |
Explanation |
Attempted an action that requires an active session, but no active session was found. |
Action |
Contact Software AG Global Support. |
1031 | No user available from session |
Class | E |
Explanation |
Unable to determine the connected user as session doesn't have any user defined. |
Action |
Try defining users and retry or contact your administrator to check database and Integtation Server status. |
1032 | Group TNPartners not defined |
Class | E |
Explanation |
TNPartners Group was not found |
Action |
Run the wm.tn.admin:install service to create TNPartners and other required user groups. |
1033 | Empty or null username for partner {0}.Also,The username may not have whitespace. |
Class | |
Explanation |
Encountered validation error while creating partner account. Iinput field username can't be null and should not contain spaces. |
Action |
Provide a valid user name and try again. |
2002 | An ID type named {0} already exists. |
Class | E |
Explanation |
Trading Networks attempted to create an external ID type with the provided name, but an external ID type with that name already exists. |
Action |
Specify the name of an external ID type that does not already exist when creating an external ID type. |
2003 | A contact type named {0} already exists. |
Class | E |
Explanation |
Trading Networks attempted to create a contact type with the provided name, but a contact type with that name already exists. |
Action |
Specify the name of a contact type that does not already exist when creating a contact type. |
2004 | A field group named {0} already exists. |
Class | E |
Explanation |
Trading Networks attempted to create a field group with the provided name, but a field group with that name already exists. |
Action |
Specify the name of a field group that does not already exist when creating a field group. |
2005 | Could not get profile dictionary |
Class | E |
Explanation |
Trading Networks encountered an unexpected error during profile dictionary initialization. |
Action |
The exception was written to the server log. See the server log for details. Take action appropriate to resolve the problem described in the exception. |
2006 | Could not retrieve field definitions |
Class | E |
Explanation |
An exception was thrown while retrieving profile field definitions. |
Action |
The exception was written to the server log. See the server log for details. Take action appropriate to resolve the problem described in the exception. |
2007 | Could not add field definition |
Class | E |
Explanation |
An exception was thrown while saving a profile field definition. |
Action |
The exception was written to the server log. See the server log for details. Take action appropriate to resolve the problem described in the exception. |
2008 | Could not update field definition |
Class | E |
Explanation |
An exception was thrown while updating a profile field definition. |
Action |
The exception was written to the server log. See the server log for details. Take action appropriate to resolve the problem described in the exception. |
2009 | "definition" is required. |
Class | E |
Explanation |
A required field value was not supplied. |
Action |
Supply the required value. |
3010 | Unable to map certificate to user for new partner {0}. |
Class | E |
Explanation |
The wm.tn.security:setVerifyCertificateSet service was unable to save certificates for a new trading partner. |
Action |
Save the partner's profile with no certificates and then add the partner's certificates. |
3019 | {0} could not retrieve the ProfileStore. |
Class | E |
Explanation |
The Profile Store is inaccessible. |
Action |
Reload the WmTN package or restart the Integration Serve that hosts Trading Networks Server. |
3030 | Unable to retrieve the {0} ID for partner {1}. |
Class | E |
Explanation |
Could not convert the internal partner ID into an external ID. |
Action |
Make sure the partner has a value for this type of external ID. |
3034 | An invalid or expired certificate was received from {0} and rejected. |
Class | W |
Explanation |
An invalid or expired certificate was received and rejected from the Trading Partner specified in the message. |
Action |
Notify the Trading Partner specified in the message that their certificate is either invalid or expired. |
3037 | Received a certificate issued by {0}, who is not on your list of trusted Certificate Authorities. |
Class | W |
Explanation |
The Certificate Authority specified in the message is not on your list of trusted sources. |
Action |
You either can add this Certificate Authority to your list of trusted Certificate Authorities, or you can notify the trading partner that you do not trust their Certificate Authority. |
3038 | Problem creating B2B account for partner (username={0}). |
Class | E |
Explanation |
An account could not be created on the Integration Server for the partner. |
Action |
Create the account manually for the partner. The user name must match the partner's required external ID. |
3050 | If {0} is supplied, {1} must also be supplied. |
Class | E |
Explanation |
You must supply either both values or neither value. |
Action |
Supply both values or neither value. |
3085 | The Trading Networks user does not have permission to change System properties. The certificate chain verifier is not correctly initialized. All incoming certificate chains will be trusted. |
Class | W |
Explanation |
The watt.security.cert.wmChainVerifier.trustByDefault property might not be set correctly. |
Action |
Ask the Administrator to set the watt.security.cert.wmChainVerifier.trustByDefault property appropriately. |
3102 | Either {0} or {1} must be supplied. |
Class | E |
Explanation |
A value must be supplied for one of the two variables, but no value was supplied for either variable. |
Action |
Supply a value for one of the variables. |
4001 | Could not delete field group. |
Class | E |
Explanation |
An exception was thrown while deleting a profile field group. |
Action |
The exception was written to the error log. See the log for details. Take appropriate action to resolve the problem described in the exception. |
4003 | Could not add partner profile for {0}. |
Class | E |
Explanation |
An exception was thrown while saving a partner profile. |
Action |
The exception was written to the error log. See the log for details. Take appropriate action to resolve the problem described in the exception. |
4005 | The partner specified (id={0}) has a {1} ID of {2}, but there is no matching IS user account. |
Class | E |
Explanation |
Trading Networks could not find an Integration Server user account for this partner. |
Action |
Verify that the partner has a user account on the Integration Server and that the account name matches the partner's required external ID value. |
4006 | Attempted to save an extended field value with an unknown field ID (id={0}). |
Class | E |
Explanation |
Field with this ID doesn't exist. Trading Networks could not save the extended field for this ID. |
Action |
Specify a valid field ID. |
4008 | Got null or empty extended profile fields |
Class | E |
Explanation |
The "fields" input variable is required. |
Action |
Pass the extended fields you want to save in the "fields" variable. |
4009 | Attempted to save an external ID that has an unknown type (type code={0}). |
Class | E |
Explanation |
Trading Networks attempted to save an external ID for a partner, but the external ID is associated with an external ID type that has not been defined. |
Action |
To save a new type of external ID for a partner, you must first define the external ID type. To do so, use the wm.tn.dictionary:addIDType service. |
4010 | ID Type {0} is not valid. Not found in the Trading Networks database. |
Class | E |
Explanation |
ID Type provided is not recognized by Trading Networks. |
Action |
Supply a valid external ID type. Use the wm.tn.dictionary:addIDType service to define a new external ID type. |
4011 | Attempted to save a contact that has an unknown type (type code={0}). |
Class | E |
Explanation |
Trading Networks attempted to save a contact for a partner, but the contact is associated with a contact type that has not been defined. |
Action |
To save a new type of contact for a partner, you must first define the contact type. To do so, use the wm.tn.dictionary:addContactType service. |
4012 | Cannot delete a standard field |
Class | E |
Explanation |
Attempted to delete a standard profile field. You can only delete extended profile fields. |
Action |
No action required. |
4014 | {0} not a valid Group ID. Must be greater than {1}. |
Class | E |
Explanation |
Group ID provided is not a positive integer. |
Action |
Supply a valid group ID value. It should be positive integer. |
4015 | Port must be a positive integer |
Class | E |
Explanation |
When specifying a partner's host and port, the port value must be greater than zero. |
Action |
Supply a valid value that is greater than zero for the port number. |
4016 | Could not decode bizdoc |
Class | E |
Explanation |
Trading Networks created an internal BizDocEnvelope to validate the profile data, but could not decode the BizDocEnvelope. |
Action |
Contact Software AG Global Support. |
4017 | Could not add {0}. A {0} with an ID of {1} already exists. |
Class | E |
Explanation |
While adding lookup type (Contact Type/ ID Type/ Binary Type), Trading Networks found that a similar lookup type with same ID already exists. Trading Networks did not add the lookup type. |
Action |
Save this type with a different ID. |
4018 | A profile already exists for the host of this Trading Network. Turn off the SELF setting on the corporate component of the profile and save it again. |
Class | E |
Explanation |
The Enterprise profile already exists. |
Action |
If you are programmatically saving profiles, set the Self? variable to false before attempting to save the profile. If you are using My webMethods to save profiles, contact Software AG Global Support. |
4019 | Could not validate profile: received null bizdoc |
Class | E |
Explanation |
Trading Networks should have created an internal BizDocEnvelope to validate profile data, but the BizDocEnvelope is null. |
Action |
Contact Software AG Global Support. Please have the server and error logs and the WmTN/config/properties.cnf file available. |
4020 | No ''{0}'' element found in bizdoc |
Class | E |
Explanation |
Trading Networks created an internal BizDocEnvelope to validate profile data, but the BizDocEnvelope did not contain the "errors" element. |
Action |
Contact Software AG Global Support. Please have the server and error logs and the WmTN/config/properties.cnf file available. |
4021 | Cannot set extended fields. |
Class | E |
Explanation |
An exception was thrown while saving extended fields to the database. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4024 | Cannot access profile store. |
Class | E |
Explanation |
An exception was thrown while accessing the Profile store. |
Action |
Contact Software AG Global Support. |
4026 | You are using webMethods Trading Partners. To be able to add more partner profiles, please upgrade to webMethods Trading Networks. |
Class | E |
Explanation |
When using webMethods Trading Partners, you are allowed to create only one profile other than your own. |
Action |
If you need to create additional partner profiles, upgrade to webMethods Trading Networks. |
4027 | Could not retrieve {0} using {1} |
Class | E |
Explanation |
Invalid id is provided. Trading Networks could not retrieve partner details using this ID. |
Action |
Supply a valid value. |
4028 | An error occurred while retrieving company logos. |
Class | E |
Explanation |
An exception was thrown while retrieving company logos. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4029 | Importing a profile for {0} (id={1}), which is marked as "My Enterprise", but it has different ID than the existing My Enterprise profile for this Trading Network. Cannot change the identity of the My Enterprise profile. Process terminated. |
Class | E |
Explanation |
You attempted to import the Enterprise. However, the target Trading Networks system already has an Enterprise profile, which has a different ID than the one you are attempting to import. Trading Networks cannot import the Enterprise profile. |
Action |
Import Enterprise profile carefully only to those Trading Networks Servers where it's not already defined. |
4030 | Could not get profile for user (username={0}). |
Class | E |
Explanation |
An exception was thrown while retrieving a partner profile for a user. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4032 | Extended fields cannot have a column name. |
Class | E |
Explanation |
Validation of profile fields failed.The column name on an extended profile field should be null. |
Action |
If you are programmatically creating extended fields, do not set the Column Name. |
4033 | Extended fields cannot have a table name. |
Class | E |
Explanation |
Validation of profile fields failed. The table name on an extended profile field should be null. |
Action |
If you are programmatically creating extended fields, do not set the Table Name. |
4034 | Partner status can only be ''Active'' or ''Inactive'' when adding a new profile. |
Class | E |
Explanation |
Invalid status provided for profile to be added. |
Action |
Supply a valid value for the Partner Status field. |
4035 | Corporation is invalid: no partnerID. |
Class | E |
Explanation |
Trading Networks attempted to update a partner profile, but the corporation component has no partner ID. |
Action |
Set the partnerID field to a valid value. |
4036 | Attempted to save a binary object that has an unknown type (type code={0}). |
Class | E |
Explanation |
The database does not have binary types defined. |
Action |
Populate your database with initial values by importing the file <IntegrationServer>/packages/WmTN/bin/init.xml, where <IntegrationServer> is the location where your server is installed. |
4037 | Could not add Field Group {0}. |
Class | E |
Explanation |
An exception was thrown while adding a profile field group. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4039 | Could not get {0} for partner (partnerID={1}). |
Class | E |
Explanation |
An exception was thrown while retrieving protocol information for a partner. |
Action |
Verify whether the database connection is available.Take appropriate action to resolve the problem described in the exception. |
4041 | Cannot delete the External ID,there has to be at least one external ID |
Class | E |
Explanation |
Each partner must have a value for the required external ID type. The required external ID value is used for the user name of the partner's Integration Server user account. |
Action |
Do not attempt to delete the required external ID from a partner's profile. |
4042 | The value for profile field {0} is not one of the valid values. |
Class | E |
Explanation |
Invalid value provided for profile field. |
Action |
Supply a valid value. |
4044 | Standard fields must have a column name. |
Class | E |
Explanation |
Profile field Validation failed. The column name on a standard profile field is null. |
Action |
Contact Software AG Global Support. |
4045 | Could not update {0}. |
Class | E |
Explanation |
An exception was thrown while updating a profile component. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4046 | A profile already exists in the database with the supplied PartnerID ({0}). |
Class | E |
Explanation |
Trading Networks attempted to save a new profile with the same partnerID as an existing profile. |
Action |
Do not specify a value for the partnerID when creating a new profile. Trading Networks will generate a unique ID for you. |
4047 | {0} cannot be null. |
Class | |
Explanation |
Partner ID is required field while fetching the Profile and it should not be null. |
Action |
Supply Partner ID to fetch profile. |
4048 | Could not get profile for partner (id={0}) |
Class | E |
Explanation |
An exception was thrown while retrieving a partner profile. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4049 | webMethods Trading Partners is restricted to the creation of one profile in addition to your own. |
Class | E |
Explanation |
When using webMethods Trading Partners, you can create only one profile other than your own. |
Action |
If you need to create additional partner profiles, upgrade to webMethods Trading Networks. |
4050 | Could not upgrade your profile. Please contact webMethods Customer Service. |
Class | E |
Explanation |
An exception was thrown while upgrading your profile from webMethods for Partners to webMethods Trading Networks. |
Action |
Take appropriate action to resolve the problem described in the exception. If necessary, contact Software AG Global Support. |
4051 | At least 1 field has been defined for this group. Cannot delete. |
Class | E |
Explanation |
Found at least one field still associated to group. Unable to delete this group. |
Action |
To delete this field group, you must first delete all extended profile fields in the group, or assign them to other groups. |
4053 | Could not delete {0} ({1}={2}). |
Class | E |
Explanation |
An exception was thrown while deleting a profile component. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4054 | Cannot set valid values for a standard field |
Class | E |
Explanation |
You cannot define a list of valid values for standard fields. |
Action |
Do not attempt to define a list of valid values for a standard field. Valid values are applicable for extended fields. |
4056 | Errors encountered validating profile/profile fields |
Class | E |
Explanation |
A list of one or more validation errors follows this message after invoking wm.tn:submit. |
Action |
Take appropriate action to resolve the errors. |
4058 | Another partner profile with the name "{0}" already exists. Cannot have duplicate partner names. Please enter a different name. |
Class | E |
Explanation |
You are attempting to create a profile; howeve , a profile with the Corporation Name and User Name that you specified already exists in Trading Networks. |
Action |
Supply a different Corporation Name and/or Unit Name. |
4060 | You must add a profile for your enterprise before you can upgrade to webMethods Trading Networks. Please create a profile for your enterprise. |
Class | E |
Explanation |
You have not defined the Enterprise profile. The Enterprise profile must exist before you can upgrade Trading Networks. |
Action |
Create the Enterprise profile. |
4062 | Cannot undelete a standard field |
Class | E |
Explanation |
Standard fields cannot be deleted or undeleted. |
Action |
Do not attempt to delete or undelete a standard field. |
4064 | {0}, no change made on server |
Class | E |
Explanation |
Trading Networks encountered an error while saving partner profile information. See the error message for details. |
Action |
Take appropriate action to resolve the problem described in the error message. |
4065 | An error was encountered deleting a partner''s profile (partnerID={0}). |
Class | E |
Explanation |
An exception was thrown while deleting a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4066 | Could not get host profile. |
Class | E |
Explanation |
An exception was thrown while retrieving the Enterprise profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4068 | {0} is required. |
Class | E |
Explanation |
No value was supplied for a required input variable. |
Action |
Supply the required value. |
4069 | Standard fields must have a table name. |
Class | E |
Explanation |
Trading Networks encountered an invalid field definition in the Trading Networks database. |
Action |
Contact Software AG Global Support. |
4072 | Error initializing ProfileStore |
Class | E |
Explanation |
Encountered error while initializing Profile Store. |
Action |
Contact Software AG Global Support. |
4073 | Could not set binary object for partner (id={0}). |
Class | E |
Explanation |
An exception was thrown while saving binary data to the Trading Networks database. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4075 | Could not get Extended Field template (group={0}). |
Class | E |
Explanation |
An exception was thrown while creating a new extended field. |
Action |
Contact Software AG Global Support. |
4076 | Invalid group specified. |
Class | E |
Explanation |
The group that was specified is not a valid group. |
Action |
Use the wm.tn.dictionary:getFieldGroups service to retrieve a list of valid groups. |
4077 | {0} must be specified for partner {1} |
Class | E |
Explanation |
Profile validation failed! Required data is missing from a partner profile. |
Action |
Supply a value for the required fields. |
4078 | Datatype cannot be null. |
Class | E |
Explanation |
Found Datatype parameter null while setting it to profile. |
Action |
Supply a valid data type. |
4079 | Your webmethods Trading Networks server is restricted to the creation of {0} profiles in addition to your own. |
Class | E |
Explanation |
Your Trading Networks Server is restricted to the creation of the number of profiles specified in the message. |
Action |
If you need to add more profiles, contact Software AG Global Support to upgrade your server. |
4080 | Attempted to set the datatype of a field to an unrecognized value: {0}. |
Class | E |
Explanation |
Provided datatype is not recognized by Trading Networks. |
Action |
Supply a valid data type. |
4082 | Binary type not found in the Trading Networks database: {0}. |
Class | E |
Explanation |
Trading Networks attempted to set the value of a binary object, but the type does not exist in the database. |
Action |
Supply a valid binaryTypeDescription or binaryTypeCode. If you have specified a valid binary type and the problem persists, import the init.xml file from the <IntegrationServer>packages/WmTN/bin directory, where <IntegrationServer> is the location where you installed your server. |
4083 | Could not change {0} Type {1}. |
Class | E |
Explanation |
An exception was thrown while attempting to update an external ID type or contact type. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4084 | Standard fields cannot have a set of extended valid values |
Class | E |
Explanation |
Trading Networks encountered an invalid field definition in the Trading Networks database. |
Action |
Contact Software AG Global Support. |
4085 | The specified delivery data (id={0}) does not exist in the database. Cannot delete. |
Class | E |
Explanation |
Trading Networks was unable to perform the specified database action because the Destination data does not exist. |
Action |
Contact Software AG Global Support. Have the server and error logs and the WmTN/config/properties.cnf file available. |
4086 | Standard fields cannot have an extended default value |
Class | E |
Explanation |
Trading Networks encountered an invalid field definition in the Trading Networks database. |
Action |
Contact Software AG Global Support. |
4087 | The value for {0} must be a String. |
Class | E |
Explanation |
Found unexpected non-String value when datatype is String, validation failed. |
Action |
Supply a String value for the field. |
4088 | A {0} ID of {1} already exists in the database. External IDs must be unique. |
Class | E |
Explanation |
Cannot have two external IDs of the same external ID type that have the same value. |
Action |
Supply another value for this external ID. |
4089 | Could not get internal ID for partner (id={0}, typeCode={1}, typeDesc={2}). |
Class | E |
Explanation |
An exception was thrown while retrieving the internal partnerID. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4090 | Fields must have a datatype |
Class | E |
Explanation |
Trading Networks encountered an invalid field definition in the Trading Networks database. |
Action |
Contact Software AG Global Support. |
4091 | Could not get profile summaries. |
Class | E |
Explanation |
An exception was thrown while retrieving profile summaries. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4092 | {0} cannot be null. {1} not {2}. |
Class | E |
Explanation |
Trading Networks did not add or update the changes because a required value is missing. |
Action |
Supply the required value. |
4093 | {0} must be equal or greater than {1} |
Class | E |
Explanation |
Numeric field validation failed as supplied value found lesser than limit value, should be greater or equal to limit value. |
Action |
Supply a valid value. |
4094 | You are already using webMethods Trading Networks. No upgrade is necessary. |
Class | E |
Explanation |
Attempted to upgrade from webMethods for Partners to webMethods Trading Networks, but you are already using webMethods Trading Networks. |
Action |
No action required. |
4096 | Could not get {0}. |
Class | E |
Explanation |
An exception was thrown while retrieving a profile component. |
Action |
An exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4099 | Status was not changed to {0} because the profile has the following errors {1} |
Class | E |
Explanation |
The profile has issues that must be resolved before the status can be changed. |
Action |
Take appropriate action to resolve the problem described in the errors. |
4100 | Cannot set Column Name for an extended field |
Class | E |
Explanation |
It is not valid for an extended profile field to have a value for Column Name. |
Action |
Do not attempt to set a value for Column Name for an extended profile field. |
4102 | Cannot set Table Name for an extended field |
Class | E |
Explanation |
It is not valid for an extended profile field to have a value for Table Name. |
Action |
Do not attempt to set a value for Table Name for an extended profile field. |
4105 | Could not add {0} Type {1}. |
Class | E |
Explanation |
An exception was thrown while attempting to create an IDType or ContactType. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4106 | Could not get profile summary (partnerID={0}). |
Class | E |
Explanation |
An exception was thrown while attempting to retrieve a profile summary. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4107 | An error occurred while retrieving polling frequencies. |
Class | E |
Explanation |
An exception was thrown while retrieving a partner's polling frequency. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4108 | Could not delete External Partner ID (internal PartnerID={0}). |
Class | E |
Explanation |
An exception was thrown while deleting a partner's external ID. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4109 | Got null profile field metadata for extended field at index {0} |
Class | E |
Explanation |
Required internal data is missing. |
Action |
Contact Software AG Global Support. |
4110 | Could not undelete profile for partner (id={0}). |
Class | E |
Explanation |
An exception was thrown while undeleting a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4113 | Attempted to save a field definition for an unknown group (group id={0}). |
Class | E |
Explanation |
The specified field group does not exist and is not valid. |
Action |
Supply a valid field group. If you are using the Trading Networks Console to create an extended field, contact Software AG Global Support. |
4114 | Could not get profile summary (username={0}). |
Class | E |
Explanation |
An exception was thrown while retrieving a profile summary. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4115 | Profile has errors. Saved with a status of {0}. |
Class | E |
Explanation |
Validation error found for the provided profile, saving with status as inactive. |
Action |
Take appropriate action to resolve the errors listed below this message. |
4116 | Could not add external ID data for partner (id={1}). |
Class | E |
Explanation |
Encountered an Exception while saving a profile component. |
Action |
See the Exception message for details. Take appropriate action to resolve the problem described in the exception. |
4117 | webMethods Trading Networks requires a special license key. Please contact webMethods to get a Trading Networks key. Until you do so, you will be limited to the creation of one profile in addition to your own. |
Class | E |
Explanation |
You currently have a webMethods for Partners license key, which allows you to create only a single partner profile. |
Action |
If you need to create additional partner profiles, upgrade to webMethods Trading Networks. |
4118 | Profile status may only be changed to {0} or {1}. |
Class | E |
Explanation |
Attempted to change the profile status to an invalid status. |
Action |
Supply a valid value. |
4120 | Could not change partner''s status. |
Class | E |
Explanation |
An exception was thrown while updating the status of a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4121 | {0} {1} delivery data already exists in the database for this partner. |
Class | E |
Explanation |
You attempted to add a delivery method for a partner that is already defined for the partner. You cannot have two instances of the same delivery method for a partner. |
Action |
If the existing delivery method contains the information you want, no action is required. Otherwise, you can update the information for the existing delivery method. |
4122 | Extended fields must have a name. |
Class | E |
Explanation |
You did not specify a name for the extended profile field. |
Action |
Supply the required value. |
4123 | Problem initializing Profile services. |
Class | E |
Explanation |
An exception was thrown during initialization. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4124 | Cannot set default value for a standard field. |
Class | E |
Explanation |
You cannot define a default value for a standard profile field. |
Action |
Do not attempt to define a default value for a standard profile field. |
4125 | Could not retrieve extended fields. |
Class | E |
Explanation |
An exception was thrown while retrieving extended fields for a partner. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4126 | Standard fields cannot be marked as deleted |
Class | E |
Explanation |
You cannot delete a standard profile field. |
Action |
Do not attempt to delete a standard profile field. |
4129 | Following errors occurred during updating profile |
Class | E |
Explanation |
A list of one or more errors follows this message. |
Action |
Take appropriate action to resolve the problems described in the errors. |
4130 | Cannot delete preferred delivery method |
Class | E |
Explanation |
The delivery method you tried to delete is the preferred delivery method for the partner. |
Action |
Before you can delete this delivery method, choose another delivery method to be "preferred." |
4131 | Could not delete {0} Type {1}. |
Class | E |
Explanation |
An exception was thrown while deleting profile data. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4132 | Could not update corporation. |
Class | E |
Explanation |
An exception was thrown while updating the Corporate component of a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4133 | Could not update addresses. |
Class | E |
Explanation |
An exception was thrown while updating one or more addresses on a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4136 | Could not delete connection ({1}={2}). |
Class | E |
Explanation |
An exception was thrown while deleting a delivery method from a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4138 | Could not update external IDs. |
Class | E |
Explanation |
An exception was thrown while updating one or more external IDs in a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4141 | Could not get binary object for partner (partnerID={1}). |
Class | E |
Explanation |
An exception was thrown while retrieving a binary object for a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4142 | "extID" is required. |
Class | E |
Explanation |
You attempted to invoke a service that requires a value for the extID input variable, but no value was supplied. |
Action |
Supply the required value. |
4143 | Either idTypeCode or idTypeDesc must be supplied (idTypeCode={0}, idTypeDesc={1}). |
Class | E |
Explanation |
You invoked a service without providing a required input variable to identify the external ID type. |
Action |
Supply one of the required values. |
4144 | partnerID is required. |
Class | E |
Explanation |
You invoked a service without providing a required input variable to identify the partner. |
Action |
Supply the required value. |
4145 | Could not get external ID for partner (partnerID={0}). |
Class | E |
Explanation |
An exception was thrown while retrieving an external ID for a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4146 | Error encountered updating binary object in the database (partnerID={0}). |
Class | E |
Explanation |
An exception was thrown while updating a binary object for a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4147 | {0} must be supplied. |
Class | E |
Explanation |
You called a Java method without supplying a value for a required field (<fieldName>). |
Action |
Supply the required value. |
4148 | A status of {0} is not one of the permitted values. |
Class | E |
Explanation |
Attempted to set the status to an invalid value. |
Action |
Supply a valid value. |
4149 | Error encountered changing partner status. |
Class | E |
Explanation |
An exception was thrown while updating the status of a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4151 | A profile is required. |
Class | E |
Explanation |
While adding profile to the Data store, profile found to be null. |
Action |
Supply the valid profile data. |
4152 | Error encountered adding profile to the database. |
Class | E |
Explanation |
An exception was thrown while adding a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4153 | Error encountered adding contacts to the database. |
Class | E |
Explanation |
An exception was thrown while adding one or more contacts to a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4155 | Error encountered adding destinations to the database. |
Class | E |
Explanation |
An exception was thrown while adding one or more delivery methods (destinations) to a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4156 | Error encountered adding IDs to the database. |
Class | E |
Explanation |
An exception was thrown while adding one or more external IDs to a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4157 | Error encountered adding addresses to the database. |
Class | E |
Explanation |
An exception was thrown while adding one or more addresses to a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4158 | Error encountered adding binary objects to the database. |
Class | E |
Explanation |
An exception was thrown while adding one or more binary objects to a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4160 | {0} cannot be null. |
Class | E |
Explanation |
When attempting to delete a profile-related asset from the Profile store, required asset ID was not provided. |
Action |
Supply the required asset ID. |
4161 | Error encountered deleting profile from the database. |
Class | E |
Explanation |
An exception was thrown while deleting a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4162 | Error encountered undeleting profile from the database. |
Class | E |
Explanation |
An exception was thrown while undeleting a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4163 | Error encountered deleting contact (contactID={0}, partnerID={1}). |
Class | E |
Explanation |
An exception was thrown while deleting a contact from a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4164 | Error encountered deleting address (addressID={0}, partnerID={1}). |
Class | E |
Explanation |
An exception was thrown while deleting an address from a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4165 | Error encountered deleting destination (destID={0}). |
Class | E |
Explanation |
An exception was thrown while deleting a delivery method (destination) from a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4166 | Error encountered deleting external id (id={0}). |
Class | E |
Explanation |
An exception was thrown while deleting an external ID from a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4167 | Error encountered retrieving extended fields. |
Class | E |
Explanation |
An exception was thrown while retrieving extended fields for a partner. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4168 | Error encountered adding extended field {0} to the database (partnerID={1}). |
Class | E |
Explanation |
An exception was thrown while adding an extended profile field for a partner. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4170 | Error encountered retrieving contact {0} (partnerID={1}). |
Class | E |
Explanation |
Encountered an exception while retrieving a contact for a partner. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4171 | Error encountered retrieving binary type {0} (partnerID={1}). |
Class | E |
Explanation |
An exception was thrown while retrieving a binary object for a partner. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4172 | Invalid binary type: {0}. |
Class | E |
Explanation |
The supplied binary type is not recognized as a valid binary type. It does not match any existing binary type. |
Action |
Supply a valid binary type value. |
4173 | A connection was requested for an unknown partner (partnerID={0}). |
Class | E |
Explanation |
Attempted to establish a connection to a partner's server, but the supplied partnerID was invalid. |
Action |
Supply a valid partner ID. |
4174 | Delivery method is {0}. Can only create contexts for HTTP or HTTPS destinations. |
Class | E |
Explanation |
A webMethods context can only be established when using HTTP or HTTPS. |
Action |
If you want to connect to a partner's server with a different protocol (e.g., FTP or SMTP) use the appropriate service in the WmPublic package or one of the delivery services in the wm.tn.transport folder. |
4175 | Error encountered connecting to partner''s server. |
Class | E |
Explanation |
An exception was thrown while connecting to a partner's server. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4181 | constant must start with FLD_[TBL]_ |
Class | E |
Explanation |
Internal error. |
Action |
Contact Software AG Global Support. |
4182 | bad constant results in non or multiple fields |
Class | E |
Explanation |
Internal error. |
Action |
Contact Software AG Global Support. |
4184 | RetryFactor cannot be zero |
Class | E |
Explanation |
Supplied RetryFactor is unexpectedly lower than 1, RetryFactor should be greater than or equal to 1. |
Action |
Supply a valid value for RetryFatctor. It should be greater than or equal to 1. |
4187 | External Field: {0} has errors. Error = {1} |
Class | E |
Explanation |
See the errors listed in the message. |
Action |
Take appropriate action to resolve the problems described in the errors. |
4188 | Is a required External Field |
Class | E |
Explanation |
No data was supplied for a required extended profile field. |
Action |
Supply a value for this field. |
4189 | Field value must be of data type java.lang.String |
Class | E |
Explanation |
Data type for the extended profile field is String, value must be a String. |
Action |
Supply a String value. |
4190 | Invalid value selected |
Class | E |
Explanation |
Supplied value for extended profile field found to be invalid. |
Action |
Supply a valid value. |
4192 | Could not retrieve ID Types from database |
Class | E |
Explanation |
An exception was thrown while retrieving external ID types. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4193 | Could not retrieve IDType Descriptions from database |
Class | E |
Explanation |
An exception was thrown while retrieving external ID type descriptions. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4194 | A database error occurred while adding an ID Type. |
Class | E |
Explanation |
An exception was thrown while adding an external ID type. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4195 | A database error occurred while changing an ID Type. |
Class | E |
Explanation |
An exception was thrown while updating an external ID type. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4196 | A database error occurred while deleting an External ID Type. |
Class | E |
Explanation |
An exception was thrown while deleting an external ID type. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4197 | Could not retrieve Contact Types from database |
Class | E |
Explanation |
An exception was thrown while retrieving contact types. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4198 | A database error occurred while adding a Contact Type. |
Class | E |
Explanation |
An exception was thrown while adding a contact type. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4199 | A database error occurred while changing a Contact Type. |
Class | E |
Explanation |
An exception was thrown while updating a contact type. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4200 | A database error occurred while deleting a Contact Type. |
Class | E |
Explanation |
An exception was thrown while deleting a contact type. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4201 | Could not retrieve Binary Types from database |
Class | E |
Explanation |
An exception was thrown while retrieving binary types. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4202 | Could not retrieve Field Groups from database |
Class | E |
Explanation |
An exception was thrown while retrieving field groups. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4203 | A database error occurred while adding a Field Group. |
Class | E |
Explanation |
An exception was thrown while adding a field group. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4204 | A database error occurred while changing a Field Group. |
Class | E |
Explanation |
An exception was thrown while updating a field group. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4205 | A database error occurred while deleting a Field Group. |
Class | E |
Explanation |
An exception was thrown while deleting a field group. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4206 | Error initializing Profile Dictionary. |
Class | E |
Explanation |
An exception was thrown during initialization. |
Action |
Contact Software AG Global Support. |
4207 | pfmd cannot be null. |
Class | E |
Explanation |
You did not supply a required value. |
Action |
Supply the required data. |
4208 | A problem was encountered updating the field defintion. |
Class | E |
Explanation |
An exception was thrown while updating a field definition. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4209 | Cannot add a standard field definition. Set Extended to true before saving this definition. |
Class | E |
Explanation |
Attempted to add a standard profile field. You cannot add standard profile fields. |
Action |
Add the profile field as an extended profile field. |
4210 | A problem was encountered adding the field defintion. |
Class | E |
Explanation |
An exception was thrown while adding a field definition. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4211 | Error retrieving profile |
Class | E |
Explanation |
Encountered an exception while retrieving a partner profile. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4212 | Could not retrieve profile from database using external ID |
Class | E |
Explanation |
An exception was thrown while retrieving a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4213 | Could not retrieve Profile Summaries from database |
Class | E |
Explanation |
An exception was thrown while retrieving a profile summary. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4216 | Could not retrieve Custom Fields from database |
Class | E |
Explanation |
An exception was thrown while retrieving extended profile fields. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4218 | Could not retrieve internal ID from database using PartnerIDID ({0}). |
Class | E |
Explanation |
An exception was thrown while retrieving a partner profile ID. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4219 | Could not retrieve internal ID from database using DestinationID ({0}). |
Class | E |
Explanation |
An exception was thrown while retrieving a partner profile ID. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4220 | Error retrieving {0} external ID for {1}. |
Class | E |
Explanation |
An exception was thrown while retrieving the external ID for a partner. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4221 | Could not retrieve IDType from database using PartnerIDID ({0}). |
Class | E |
Explanation |
An exception was thrown while retrieving an external ID type. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4222 | Could not update profile. |
Class | E |
Explanation |
An exception was thrown while updating a profile that has been marked deleted. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4223 | Corporation can not be null. |
Class | E |
Explanation |
Required Corporate information was not supplied. |
Action |
Supply the required Corporate information. |
4224 | Could not update Corporation. |
Class | E |
Explanation |
An exception was thrown while updating a partner profile. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4225 | Contacts can not be null. |
Class | E |
Explanation |
Required Contact information was not supplied. |
Action |
Supply the required data. |
4226 | At least one Contact is required. |
Class | E |
Explanation |
The supplied Vector must contain at least one contact. |
Action |
Supply the required data. |
4227 | Could not update Contacts. |
Class | E |
Explanation |
An exception was thrown while updating a partner's contact information. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4228 | Address can not be null. |
Class | E |
Explanation |
Required address information was not supplied. |
Action |
Supply the required data. |
4229 | At least one Address is required. |
Class | E |
Explanation |
The supplied vector must contain at least one address. |
Action |
Supply the required data. |
4230 | Could not update Addresses. |
Class | E |
Explanation |
An exception was thrown while updating a partner's address information. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4231 | Destinations can not be null. |
Class | E |
Explanation |
Required delivery method (destination) information was not supplied. |
Action |
Supply the required data. |
4232 | At least one Destination is required. |
Class | E |
Explanation |
The supplied vector must contain at least one delivery method (destination). |
Action |
Supply the required data. |
4233 | Could not update Destinations. |
Class | E |
Explanation |
An exception was thrown while updating a partner's delivery method (destination) information. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4235 | At least one ID is required. |
Class | E |
Explanation |
The supplied vector must contain at least one external ID. |
Action |
Supply the required data. |
4236 | Could not update IDs. |
Class | E |
Explanation |
An exception was thrown while updating a partner's external ID information. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4237 | A vector of Contacts is required |
Class | E |
Explanation |
The first argument to ProfileStore.addContacts is null. |
Action |
Supply the required data. |
4238 | A vector of Destinations is required |
Class | E |
Explanation |
The first argument to ProfileStore.addDestinations is null. |
Action |
Supply the required data. |
4239 | A vector of IDs is required |
Class | E |
Explanation |
The first argument to ProfileStore.addIDs is null. |
Action |
Supply the required data. |
4240 | A vector of Addresses is required |
Class | E |
Explanation |
The first argument to ProfileStore.addAddresses is null. |
Action |
Supply the required data. |
4242 | "addresses" is empty. At least one Address must be supplied. |
Class | E |
Explanation |
No address was supplied. |
Action |
Supply the required value. |
4243 | "connections" is empty. At least one Destination must be supplied. |
Class | E |
Explanation |
No delivery method (destination) was supplied. |
Action |
Supply the required value. |
4244 | Could not validate profile extended fields: received null bizdoc |
Class | E |
Explanation |
Internal error occurred during profile validation. |
Action |
Contact Software AG Global Support. |
4245 | No extended fields found in bizdoc |
Class | E |
Explanation |
Internal error occurred during profile validation. |
Action |
This error can be safely ignored. If it persists, contact Software AG Global Support. |
4246 | Could not validate profile standard fields: received null bizdoc |
Class | E |
Explanation |
Internal error occurred during profile validation. |
Action |
Contact Software AG Global Support. |
4247 | No standard fields found in bizdoc |
Class | E |
Explanation |
Internal error occurred during profile validation. |
Action |
Contact Software AG Global Support. |
4252 | Attempted to import extended field "{0}" for partner ID {1}, but this partner does not exist on your Trading Networks system. |
Class | E |
Explanation |
Attempted to import extended field for a partner, but this partner does not exist on your Trading Networks. |
Action |
You must import the partner's profile before you can import extended fields for the partner. |
4253 | Attempted to import extended field "{0}" that has an extended profile field ID of {1}, but this extended field is not defined on your Trading Networks system. |
Class | E |
Explanation |
Cannot import the value of the extended profile field because there is no definition for the extended field. |
Action |
You must import the extended field definitions before you can import extended field values. |
4254 | Error encountered invoking wm.tn.profile:addProfile {0}. |
Class | E |
Explanation |
An exception was thrown while saving a new partner profile. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4257 | Error encountered refreshing ID cache. |
Class | E |
Explanation |
An exception was thrown while refreshing an internal cache. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4258 | Could not get external IDs for partner (partnerID={0}). |
Class | E |
Explanation |
An exception was thrown while retrieving external IDs. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4259 | At least one ID must be specified for partner {0}. |
Class | E |
Explanation |
Because the value of the required external ID type is used as the user name for an Integration Server user account, it must be specified. |
Action |
Specify the required external ID. |
4260 | Could not retrieve Profile Groups from database. |
Class | E |
Explanation |
Encountered a SQLException while retrieving profile group information from the database. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4262 | profileGroupName can not be null or empty. |
Class | E |
Explanation |
Trading Networks cannot accept null or an empty string for the profile group name. |
Action |
Specify a non-null a profile group name. |
4263 | profileGroupName {0} already exists in database. |
Class | E |
Explanation |
Trading Networks cannot accept a duplicate profile group name. |
Action |
Specify a unique profile group name. |
4264 | A database error occurred while adding Profile Group {0}. |
Class | E |
Explanation |
Encountered a SQLException while adding the new profile group. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4265 | A database error occurred while changing Profile Group {0}. |
Class | E |
Explanation |
Encountered a SQLException while changing the profile group name from its old name to a new name. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4266 | A database error occurred while deleting Profile Group {0}. |
Class | E |
Explanation |
Encountered a SQLException while deleting the profile group from the database. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4267 | A databse error occurred while querying profile information. |
Class | E |
Explanation |
Encountered a SQLException while executing a profile query. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4275 | Error encountered invoking service {0} |
Class | E |
Explanation |
Encountered an exception while invoking the specified service. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4276 | {0} can not be null or a 0-length array. |
Class | E |
Explanation |
The input signature profileGroupIds should be a non-null array. |
Action |
Specify non-null values for the profileGroupIds input. |
4281 | Attempted to import security data for partner ID {0}, but this partner does not exist on your Trading Networks system. |
Class | E |
Explanation |
You attempted to import a trading partner's security data without first importing this trading partner's profile. |
Action |
Import the trading partner's profile before you attempt to import the security data for this trading partner. |
4282 | No {0} {1} delivery data exists in the database for this partner. Cannot update. |
Class | E |
Explanation |
The profile update operation cannot be completed because the delivery protocol data is not available. |
Action |
Provide the delivery protocol details. |
4283 | Could not add contact data for partner (id="{0}"). |
Class | E |
Explanation |
Encountered an exception while invoking wm.tn.profile:addContacts. The operation cannot be completed. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4284 | Could not add address data for partner (id="{0}"). |
Class | E |
Explanation |
Encountered an exception while invoking wm.tn.profile:addAddresses. The operation cannot be completed. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4285 | Could not add delivery data for partner (id="{0}"). |
Class | E |
Explanation |
Encountered an exception while invoking wm.tn.profile:addConnections. The operation cannot be completed. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4287 | Could not delete profile group {0}, it is still in use. |
Class | E |
Explanation |
The delete operation cannot be completed because the profile group is in use. |
Action |
Check the trading partner profiles to make sure that no partner belongs to the group you are attempting to delete. |
4289 | Database error in adding partner {0} to profile groups. Import operation aborted. |
Class | E |
Explanation |
Trading Networks encountered a problem with its database. There is a problem in the database or database driver. |
Action |
Use the JDBC Pools page on the Integration Server Administrator to ensure that the Integration Server can connect to the Trading Networks database. Correct all connection problems. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
4290 | Cannot import partner profile(s) without My Enterprise profile. |
Class | E |
Explanation |
You are attempting to import one or more partner profiles; however, the target Trading Networks server does not have an Enterprise profile. |
Action |
Create an Enterprise profile on the target server. Then, import the partner profiles. |
4291 | SQLException encountered in ProfileStore.addPartnerCertificate(). |
Class | E |
Explanation |
Trading Networks encountered a problem with its database. There is a problem in the database or database driver. |
Action |
Use the JDBC Pools page on the Integration Server Administrator to ensure that the Integration Server can connect to the Trading Networks database. Correct all connection problems. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
4292 | EXMLException encountered in ProfileStore.addPartnerCertificate(). |
Class | E |
Explanation |
Trading Networks encountered a problem when attempting to save a certificate for a partner. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4293 | SQLException encountered in ProfileStore.getPartnerIDForCertificate(). |
Class | E |
Explanation |
Trading Networks encountered a problem with its database. There is a problem in the database or database driver. |
Action |
Use the JDBC Pools page on the Integration Server Administrator to ensure that the Integration Server can connect to the Trading Networks database. Correct all connection problems. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
4294 | EXMLException encountered in ProfileStore.getPartnerIDForCertificate(). |
Class | E |
Explanation |
Trading Networks encountered a problem when attempting to retrieve a certificate for a partner. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4295 | Cannot deliver to My Enterprise. The supplied partnerID ({0}) is the partnerID of the My Enterprise profile. Please supply a different partnerID. |
Class | E |
Explanation |
The document receiver is the Enterprise profile, which indicates Trading Networks is to deliver the document to itself. This is not valid; Trading Networks cannot deliver a document to itself. |
Action |
Either change the receiver to specify a trading partner, or do not attempt to deliver this document. |
4296 | A deleted partner profile with the name "{0}" already exists. Cannot have duplicate partner names. Please enter a different name. |
Class | E |
Explanation |
You attempted to create a profile. However, the Corporation Name and Unit Name you specify will make the profile a duplicate of a profile that was previously deleted. Although a profile is deleted, Trading Networks continues to maintain information about it in its database. As a result, you cannot create another profile using the same Corporation Name and Unit Name. |
Action |
If you want to reinstate the deleted profile, use the wm.tn.profile:undeleteProfile service. Otherwise, enter a different Corporation Name and Unit Name when creating a profile. |
4297 | Importing a profile for {0} (id={1}), which is marked as "My Enterprise". A "My Enterprise" profile already exists for this Trading Network. If you want to update it, use the Force option. Process terminated. |
Class | E |
Explanation |
You attempted to import an Enterprise profile into a Trading Networks system that already has an Enterprise profile. |
Action |
If you want to replace the existing Enterprise profile with the profile you are trying to import, use the Force option. |
4298 | A deleted profile with the name "{0}" already exists. Unable to recreate a deleted profile. |
Class | E |
Explanation |
A deleted partner profile with this Corporation Name already exists. Trading Networks maintains information about deleted profiles in its database and does not allow duplicate partner names. |
Action |
You can either use a different Corporation Name, or use the wm.tn.profile:undeleteProfile service to reinstate the deleted partner profile. |
4299 | Could not get Users for partner (partnerID={0}). |
Class | |
Explanation |
Encountered SQL Exception, not able to fetch users for specified partner. |
Action |
Check database connection |
4300 | Could not get partners for user (username={0}). |
Class | |
Explanation |
Encountered SQL Exception, not able to fetch partners for specified user. |
Action |
Check database connection |
4301 | Could not add users data for partner (id={1}). |
Class | |
Explanation |
An exception was thrown while adding users to a partner. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4302 | Could not delete users data for partner (id={1}). |
Class | |
Explanation |
An exception was thrown while deleting users for a partner. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
4303 | Attempted to import a field definition "{0}" that uses a field group {1}, but this field group is not defined on your Trading Networks system. |
Class | |
Explanation |
You attempted to import a field definition that uses a field group, but this field group is not defined on your Trading Networks. |
Action |
Try importing field group before importing the field definition. |
4304 | Attempted to import a profile "{0}" that uses a contact type {1}, but this Contact Type is not defined on your Trading Networks system. |
Class | |
Explanation |
You attempted to import a profile that uses a contact type, but this contact type is not defined on your Trading Networks system. |
Action |
Try importing contact type before importing the profile. |
4305 | Attempted to import a profile "{0}" that uses an external id type {1}, but this external id type is not defined on your Trading Networks system. |
Class | |
Explanation |
You attempted to import a profile that uses an external ID type, but this external ID type is not defined on your Trading Networks system. |
Action |
Try importing external ID before importing the profile. |
4306 | Attempted to import a profile "{0}" that uses a profile group {1}, but this profile group is not defined on your Trading Networks system. |
Class | |
Explanation |
You attempted to import a profile that uses a profile group, but this profile group is not defined on your Trading Networks system. |
Action |
Try importing profile group before importing the profile. |
4309 | Could not validate the EXTERNAL ID with (idType={0}) and (externalID={1}) |
Class | |
Explanation |
An exception was thrown while validating the specified external ID. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4310 | Error encountered while getting the External IDs associated with partner with (partnerID={0}) |
Class | |
Explanation |
Error encountered while getting the External IDs associated with the supplied partnerID. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4311 | Following errors occurred during updating externalID |
Class | |
Explanation |
Errors occurred during updating external ID. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4312 | ID not added as the (externalIDType={0}) given is not a valid one. |
Class | |
Explanation |
Validation failed while updating the set of external IDs associated with a profile. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4313 | The partner specified (partnerID={0}) doesnot exist in the trading networks. Give a correct one. |
Class | |
Explanation |
Supplied partnerID does not exist in the Trading Networks. |
Action |
Supply valid partner ID. |
4314 | ID not added as the (externalIDType={0}) given already exists. |
Class | |
Explanation |
ID not added as the externalIDType=0 supplied already exists. |
Action |
Supply valid ID |
4316 | Error encountered while getting registered EDI IDTypes. |
Class | |
Explanation |
Error encountered while fetching registered EDI IDTypes. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4317 | Error encountered while cleaning up registered EDI IDTypes. |
Class | |
Explanation |
Error encountered while deregistering EDI ID Types. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4318 | Error encountered while getting the Internal ID of the Enterprise profile. |
Class | |
Explanation |
Error encountered while getting the Internal ID of the Enterprise profile. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4319 | Error encountered while getting the Internal Identifier for the environment. |
Class | |
Explanation |
Error encountered while getting the Internal Identifier for the environment. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4320 | "deliveryInfo" is empty. At least one Destination must be supplied. |
Class | |
Explanation |
While adding delivery settings, no destination supplied. At least one destination must be supplied. |
Action |
Supply at least one destination. |
4321 | "DestinationID" is empty. At least one DestinationID must be supplied. |
Class | |
Explanation |
While removing delivery settings, no destination ID supplied. At least one destination ID must be supplied. |
Action |
Supply at least one destination ID. |
4322 | Error encountered while adding the (externalIDType={0}). |
Class | |
Explanation |
Error encountered while adding the External ID type to Trading Networks. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4323 | Service Signature given (Service Signature ={0}) is invalid. Give a valid one. |
Class | |
Explanation |
Validation failed while retrieving the input or output signature of a specified service. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4324 | Error encountered while extracting Registered delivery Services. |
Class | |
Explanation |
Error encountered while extracting registered delivery Services. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4325 | Cannot set extended field {0} for partnerID {1}. |
Class | |
Explanation |
Error encountered while updating extended field for a profile. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4326 | Could not add user mapping for partnerID {0} and User {1}. |
Class | |
Explanation |
Error encountered while adding user mapping for a profile. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4327 | Either one of the inputs of simpleQuery or queryInput is mandatory for querying the profile. |
Class | |
Explanation |
Neither input of simpleQuery nor queryInput fields supplied for querying the profile. |
Action |
Supply either input of simpleQuery or queryInput fields for querying the profile. |
4328 | Error encountered while executing Profile Query |
Class | |
Explanation |
Error encountered while executing Profile Query |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4329 | My Enterprise Profile with specified (partnerID={0}) cannot be deleted. |
Class | |
Explanation |
You tried to delete the Enterpise Profile, but the Enterprise profile cannot be deleted. |
Action |
Don not attempt to delete the Enterprise profile. |
4332 | Please specify correct value for routing field. Mandatory values for it are true and false. |
Class | |
Explanation |
Supplied value for routing field is neither true nor false. |
Action |
Supply valid routing field value. It should be either true or false. |
4334 | Error encountered while adding DLS artifacts with name ({0}). |
Class | |
Explanation |
Error encountered while adding DLS artifacts, found artifact with specified name as null. |
Action |
Supply valid value for specified artifact name. |
4336 | Error encountered while querying on DLS Rules. |
Class | |
Explanation |
Error encountered while querying on DLS Rules and roles. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4337 | Pipeline for modifying the Rules and RuleRoleInfo shouldn''t be null. |
Class | |
Explanation |
Input fields found to be null, while modifying the Rules and RuleRoleInfo. |
Action |
Supply the input fields containing IData/pipeline. |
4338 | Either of the Rules or RoleRoleInfo shouldn''t be present. |
Class | |
Explanation |
Either Rules or RoleRoleInfo should be present while modifying. |
Action |
Supply either Rules or RoleRoleInfo. |
4339 | Error while Rule Addition/Modification, as a Rule already exists with the name ({0}). |
Class | |
Explanation |
Error encountered while adding or modifying rule, because a rule with the same name already exists. |
Action |
Supply rule with a different name. |
4340 | Error while Role Addition/Modification, as a Role already exists with the name ({0}). |
Class | |
Explanation |
Error encountered while adding or modifying a role, because a role with the same name already exists. |
Action |
Supply a role with different name. |
4341 | Please specify either Permission or ProfileID. Both of them are either null or empty. Either one of them is mandatory. |
Class | |
Explanation |
Found that Permission and ProfileID both are either null or empty while checking whether the current user can perform the required action. |
Action |
Supply either Permission and ProfileID. |
4342 | Please specify Permission. Either it is null or empty. Its a mandatory field. |
Class | |
Explanation |
During functional permission check, input field Permission found to be null or empty. |
Action |
Supply mandatory input field Permission. |
4343 | Error encountered while during operation on Functional Privileges. |
Class | |
Explanation |
Error encountered while checking functional privileges. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4344 | Error encountered while querying for Functional Privileges. |
Class | |
Explanation |
Error encountered while querying for functional privileges. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4345 | Please specify either Add or Remove. Both of them are either null or empty. Either one of them is mandatory. |
Class | |
Explanation |
While modifying functional privileges, both of the input field Add/Remove found empty or null. |
Action |
Supply valid values for the field Add/Remove. |
4346 | Access denied, as the User "{0}" does not have the permission to {1} {2}. |
Class | |
Explanation |
User is not permitted to perform the specified action. |
Action |
Contact your administrator. |
4347 | Access denied, as the User "{0}" does not have the permission to view {1}. |
Class | |
Explanation |
User is not allowed to perform the specified action. |
Action |
Contact your administrator. |
4348 | Access denied, as the User "{0}" does not have the privilege to {1} {2}. |
Class | |
Explanation |
User is not allowed to perform the specified action. |
Action |
Contact your administrator. |
4349 | Access denied, as the User "{0}" does not have the privilege to view {1}. |
Class | |
Explanation |
User is not allowed to perform the specified action. |
Action |
Contact your administrator. |
4393 | Access Denied. User "{0}" does not have permission to query expired certificates. |
Class | |
Explanation |
Specified user does not have permission to query expired certificates. |
Action |
Contact your administrator. |
4399 | Error encountered while getting list of permissions for the user "{0}". |
Class | |
Explanation |
Error encountered while getting list of permissions for the specified user. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4401 | Error encountered while profile "{0}" disassociation with DataSet "{1}". |
Class | |
Explanation |
Error encountered while profile disassociation with DataSet. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4402 | Disassociation of profile "{0}" from DataSet "{1}" is disallowed. Dissassociation would have made profile disappear from your profile list. |
Class | |
Explanation |
Disassociation of profile from DataSet is disallowed. Dissassociation would have made profile disappear from your profile list. |
Action |
No action required. |
4404 | Could not create delivery service {0}. A delivery service named {0} already exists. |
Class | |
Explanation |
Delivery service with the same name already exists in Trading Networks. |
Action |
Add delivery service with different name. |
4405 | The WmTN Property file {0} does not exist |
Class | |
Explanation |
Not able to locate Trading Networks properties file at expected location. |
Action |
Restore the TN Properties file. Contact Software AG Global Support. |
4406 | The WmTN Property file {0} is read only |
Class | |
Explanation |
Not able to write to the Trading Networks properties file. |
Action |
Make the Trading Networks properties file writable. Contact Software AG Global Support. |
5001 | This document type ({0}) is missing one or both of its signature queries (Signature and SignedBody). Signing cannot proceed. |
Class | E |
Explanation |
Trading Networks cannot create a digital signature because the TN document type did not instruct Trading Networks to extract the signature or signed body system attributes. |
Action |
Add queries to extract the Signature and SignedBody system attributes to the TN document type. For instructions, see the Trading Networks documentation. |
5002 | The signing service for this document ({0}) generated an error. The original error was {1}. |
Class | E |
Explanation |
Error encountered while signing the specified document. |
Action |
Take appropriate action to resolve the problem described in the exception. |
5003 | Signing Failed |
Class | E |
Explanation |
See message TRNSERV.000013.000002 for full details. |
Action |
Take appropriate action to resolve the problem described in the exception displayed with message TRNSERV.000013.000002. |
5005 | Base-64 encoding the signed body for this document failed to produce a value. The signed body (before encoding) was {0}. |
Class | E |
Explanation |
The query used to extract the signed body from the document might be invalid. You specify the query that Trading Networks uses in the TN document type used for the document. |
Action |
If the query used for the signed body returned an empty string, adjust the signed body query for this TN document type. For instructions, see the Trading Networks documentation. |
5006 | Encoding Error |
Class | E |
Explanation |
See message TRNSERV.000013.000005 for full details. |
Action |
Take appropriate action to resolve the problem described in the exception displayed with message TRNSERV.000013.000005. |
5007 | An error prevented fetching certificate info for the sender of this document. |
Class | E |
Explanation |
An exception was thrown while retrieving certificates needed to sign a document. |
Action |
Take appropriate action to resolve the problem described in the exception. |
5008 | Error fetching cert info |
Class | E |
Explanation |
See message TRNSERV.000013.000007 for full details. |
Action |
Take appropriate action to resolve the problem described in the exception displayed with message TRNSERV.000013.000007. |
5010 | No private key information was available for the sender of this document. {0} |
Class | E |
Explanation |
Trading Networks encountered an error while fetching a private key. See the error message for details. |
Action |
You might need to import security data for this partner. |
5012 | Applying the {1} query to this document failed. The error: {2} |
Class | E |
Explanation |
Trading Networks encountered an error while executing the query to extract the signature from a document. See the exception for details. |
Action |
Take appropriate action to resolve the problem described in the exception. |
5013 | Query Error |
Class | E |
Explanation |
See message TRNSERV.000013.000012 for full details. |
Action |
Take appropriate action to resolve the problem described in the exception displayed with message TRNSERV.000013.000012. |
5014 | The signature query for doctype {0} identified the {1} node as the target of the signature, but this node is missing in this document. Signing cannot proceed. |
Class | E |
Explanation |
The query used to extract the signature from the document identified a node that is not in the document. You specify the query that Trading Networks uses in the TN document type used for the document. |
Action |
Adjust the signature and/or signed body query for this TN document type. For instructions, see the Trading Networks documentation. |
5015 | Missing Document Node |
Class | E |
Explanation |
See message TRNSERV.000013.000014 for full details. |
Action |
Take appropriate action to resolve the problem described in the exception displayed with message TRNSERV.000013.000014. |
5017 | No cert chains are available for the sender of this document. {0} |
Class | E |
Explanation |
Trading Networks encountered an error while fetching a certificate chain. See the error message for details. |
Action |
Take appropriate action to resolve the problem described in the error. |
5019 | Cannot sign documents from UNKNOWN sender |
Class | E |
Explanation |
The sender of the document is unknown to Trading Networks. Reasons that Trading Networks might be unable to determine the sender are: 1) The query that Trading Networks uses to extract the Sender value from the document might be incorrect. The query is defined in the TN document type. 2) The value extracted from the document for the Sender query does not match the external ID of any partner in the Trading Networks database. 3) The structure of the document is incorrect. |
Action |
Do one of the following: 1) If the query used to extract the Sender value is not valid, adjust the query in the TN document type. For instructions, see the Trading Networks documentation. 2) If the value extracted for the Sender query does not match an external ID in the Trading Networks database, add the external ID to the appropriate partner's profile. For instructions, see the Trading Networks documentation. 3) If the document structure is incorrect, notify the partner that sent the document. |
5021 | This doctype ({0}) has no signing service defined. Signing cannot continue. |
Class | E |
Explanation |
This TN document type has no signing service defined, so Trading Networks cannot continue with signing. |
Action |
If this is an XML TN document type, contact Software AG Global Support. If this is not an XML TN document type and the TN document type supports signing services, define a signing service for the TN document type. |
5024 | The signature query for doctype {0} ({1}) failed to identify a node to insert the signature into. Signing cannot proceed. |
Class | E |
Explanation |
Either the query that Trading Networks uses to extract the signature is incorrect in the TN document type or the structure of the document is incorrect. |
Action |
If the query is not correct, adjust the signature query for this TN document type. For instructions, see the Trading Networks documentation. If the document structure is incorrect, notify the document sender. |
5025 | The signature query for doctype {0} identified the {1} node as the target of the signature, but this node is not unique in this document. Signing cannot proceed. |
Class | E |
Explanation |
Either the structure of the document is incorrect or the query that Trading Networks uses to extract the signature is incorrect in the TN document type. |
Action |
If the document structure is incorrect, notify the document sender. If the query is not correct, adjust the signature query for this TN document type. For instructions, see the Trading Networks documentation. Note that if your XQL query is returning an array of nodes, you can force it to return a single node by adding a subscript. For example, change "/anXMLtag" to "/anXMLtag[0]". |
5027 | No signing service for doctype {0} |
Class | W |
Explanation |
This TN document type has no signing service defined, so Trading Networks cannot continue with signing. |
Action |
If this is an XML TN document type, contact Software AG Global Support. If this is not an XML TN document type and the TN document type supports signing services, define a signing service for the TN document type. |
5030 | Trading Networks will not sign documents originating from the Unknown partner. Signing fails. |
Class | E |
Explanation |
The sender of the document is unknown to Trading Networks. Reasons that Trading Networks might be unable to determine the sender are: 1) The query that Trading Networks uses to extract the Sender value from the document might be incorrect. The query is defined in the TN document type. 2) The value extracted from the document for the Sender query does not match the external ID of any partner in the Trading Networks database. 3) The structure of the document is incorrect. |
Action |
Do one of the following: 1) If the query used to extract the Sender value is not valid, adjust the query in the TN document type. For instructions, see the Trading Networks documentation. 2) If the value extracted for the Sender query does not match an external ID in the Trading Networks database, add the external ID to the appropriate partner's profile. For instructions, see the Trading Networks documentation. 3) If the document structure is incorrect, notify the partner that sent the document. |
5031 | The signed body query for this document type ({0}) failed to produce a value. Signing the document fails. The query was {1}. |
Class | E |
Explanation |
Either the query that Trading Networks uses to extract the signature is incorrect in the TN document type or the structure of the document is incorrect. |
Action |
If the query is not correct, adjust the signature query for this TN document type. For instructions, see the Trading Networks documentation. If the document structure is incorrect, notify the document sender. |
6001 | Cannot persist a TPA |
Class | E |
Explanation |
An exception was thrown while saving a TPA to the database. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
6002 | Cannot retrieve a TPA |
Class | E |
Explanation |
An exception was thrown while reading a TPA from the database. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
6006 | Cannot delete a TPA with status="agreed" |
Class | E |
Explanation |
You cannot delete a TPA with status Agreed. |
Action |
Change the TPA's status to Proposed and then delete it. |
6007 | Cannot delete a TPA |
Class | E |
Explanation |
An exception was thrown while deleting a TPA from the database. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
6008 | Cannot update a TPA that has status="agreed" |
Class | E |
Explanation |
A TPA in "Agreed" status cannot be revised. |
Action |
Change the TPA's status to "Proposed" before updating the TPA. |
6009 | Cannot update a TPA |
Class | E |
Explanation |
An exception was thrown while updating a TPA in the database. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
6010 | Cannot get a TPA lock |
Class | E |
Explanation |
An exception was thrown while getting a lock on a TPA in the database. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
6011 | Cannot update controlNumber for a TPA |
Class | E |
Explanation |
An exception was thrown while updating the control number of a TPA in the database. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
6014 | Cannot update tpaData when status="agreed" and dataStatus="immutable" |
Class | E |
Explanation |
You attempted to update the TPA data that is associated with a TPA. The Agreement Status of the TPA is "Agreed" and the Data Status is "Non-modifiable." You cannot update the TPA data when the Data Status is "Non-modifiable." |
Action |
To be able to update the TPA data, perform one of the following actions: 1) change the Data Status to "Modifiable," or 2) change the Agreement Status to "Proposed." |
6017 | Cannot update tpaData |
Class | E |
Explanation |
An exception was thrown while updating the TPA data in a TPA in the database. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
6018 | Cannot get the next controlNumber for a TPA |
Class | E |
Explanation |
An exception was thrown while determining the next control number for a TPA in the database. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
6020 | Cannot change status for a TPA |
Class | E |
Explanation |
An exception was thrown while changing the status of a TPA in the database. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
6021 | A TPA that matches senderID, receiverID and agreementID does not exists |
Class | E |
Explanation |
Internal error |
Action |
Contact Software AG Global Support. |
6022 | Missing senderID, or receiverID, or agreementID or initService |
Class | E |
Explanation |
Internal error |
Action |
Contact Software AG Global Support. |
6023 | Cannot invoke initService |
Class | E |
Explanation |
Unable to initialize the data in a TPA because the TPA's initialization service could not be invoked. |
Action |
Make sure the TPA's initialization service is an existing service in an enabled package. |
6025 | Query TPA exception |
Class | E |
Explanation |
An exception was thrown while executing a TPA database query. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
6026 | Cannot get all TPAs |
Class | E |
Explanation |
An exception was thrown while retrieving a list of TPAs from the database. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
6027 | Cannot import TPA |
Class | E |
Explanation |
An exception was thrown while importing one or more TPAs. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
6028 | Missing data schema |
Class | E |
Explanation |
No IS document type is defined for the TPA. |
Action |
Define an IS document type for the TPA. |
6029 | Missing TPA data |
Class | E |
Explanation |
The TPA Data field in the TPA is empty. |
Action |
Enter values into the TPA Data field. |
6030 | Cannot invoke validation service |
Class | E |
Explanation |
An exception was thrown while invoking the pub.schema:validate service while validating the structure of the IS document type in the TPA. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
6031 | Missing {0} |
Class | E |
Explanation |
A required input variable was not supplied to the wm.tn.tpa:updateTPA service. |
Action |
Supply a value for the required variable. |
6032 | A TPA that matches senderID, receiverID and agreementID already exists |
Class | E |
Explanation |
Cannot save this TPA because it would duplicate an existing TPA. |
Action |
Either add the data in this TPA to the one that already exists, or specify a different agreementID. |
6033 | A TPA that matches senderID, receiverID and agreementID does not exist |
Class | E |
Explanation |
Cannot update the TPA because Trading Networks cannot locate a TPA in the database that has the supplied senderID, receiverID, and agreementID. |
Action |
Specify a senderID, receiverID and agreementID that matches an existing TPA. |
6034 | controlNumber cannot not be null |
Class | E |
Explanation |
Internal error. |
Action |
Contact Software AG Global Support. |
6035 | tpaData cannot not be null |
Class | E |
Explanation |
Internal error. |
Action |
Contact Software AG Global Support. |
6036 | Cannot update tpaData when dataStatus="immutable" |
Class | E |
Explanation |
You cannot make changes to a TPA's data when the TPA's Data Status is "Non-modifiable." |
Action |
To make changes to the TPA data, change the TPA's Data Status to "Modifiable." |
6037 | Cannot update controlNumber |
Class | E |
Explanation |
An exception was thrown while updating the control number of a TPA in the database. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
6038 | There are more than one TPA that matches senderID, receiverID and agreementID |
Class | E |
Explanation |
Internal error. |
Action |
Contact Software AG Global Support. |
6039 | Cannot serialize tpaData |
Class | E |
Explanation |
Internal error. |
Action |
Contact Software AG Global Support. |
6040 | Cannot de-serialize tpaData |
Class | E |
Explanation |
The supplied control number is not a valid integer. |
Action |
Supply a valid integer value. |
6041 | New controlNumber is not an integer |
Class | |
Explanation |
Encountered error while parsing supplied controlNumber because it is not an integer. |
Action |
Supply an integer value for controlNumber. |
6042 | A TPA with the supplied ID ({0}) does not exist. |
Class | E |
Explanation |
An invalid value was supplied for the tpaID field. |
Action |
Supply a valid TPA ID. |
6043 | If "tpaID" is not supplied, then "senderID", "receiverID" and "agreementID" must be supplied. |
Class | E |
Explanation |
The user did not supply the correct required inputs. |
Action |
Supply the required inputs. |
6044 | Attempted to import a TPA for Sender {0}, but the sender''s profile is not defined on your Trading Networks system. |
Class | |
Explanation |
Attempted to import a TPA for Sender, but the sender's profile is not defined on your Trading Networks system. |
Action |
Import Sender's profile first. |
6045 | Attempted to import a TPA for Receiver {0}, but the receiver''s profile is not defined on your Trading Networks system. |
Class | |
Explanation |
Attempted to import a TPA for Receiver, but the receiver's profile is not defined on your Trading Networks system. |
Action |
Import Receiver's profile first. |
6050 | Attempted to import a Archive Scheduled Service for Sender {0}, but the sender''s profile is not defined on your Trading Networks system. |
Class | |
Explanation |
Attempted to import a Archive Scheduled Service for specified Sender, but the sender's profile is not defined on your Trading Networks system. |
Action |
Import Sender's profile first. |
6051 | Attempted to import a Archive Scheduled Service for Receiver {0}, but the receiver''s profile is not defined on your Trading Networks system. |
Class | |
Explanation |
Attempted to import a Archive Scheduled Service for Receiver, but the receiver's profile is not defined on your Trading Networks system. |
Action |
Import Receiver's profile first. |
7002 | Document type {0} has no validation service defined. Validation fails. |
Class | E |
Explanation |
Supplied document type has no validation service defined. |
Action |
Contact Software AG Global Support. |
7003 | No Validation Service |
Class | E |
Explanation |
A TN document type has no validation service defined. Validation fails. |
Action |
Contact Software AG Global Support. |
7004 | {0}: {1} |
Class | E |
Explanation |
A document sent to Trading Networks failed validation. |
Action |
Notify the document sender. |
7005 | Doctype {0}: no validation svc. defined; validation skipped |
Class | W |
Explanation |
Document type has no validation service defined. Validation fails. |
Action |
Contact Software AG Global Support. |
7010 | The doctype for this document ({0}) does not have a validation schema defined; validation fails. |
Class | E |
Explanation |
The document matches a TN document type that indicates the document's structure should be validated, but no schema was defined. |
Action |
Update the TN document type, and specify the schema to use for document validation. |
7011 | No Validation Schema |
Class | E |
Explanation |
The document matches a processing rule that indicates the document's structure should be validated, but no schema was defined. |
Action |
Update the TN document type that the document matches to specify the schema to use for document validation. |
7012 | The validation service for this XML document, {0}, could not be successfully invoked. The original exception message is: {1} |
Class | E |
Explanation |
The service used to validate the document's structure threw an exception. |
Action |
Take appropriate action to resolve the problem described in the exception. |
7013 | The validation service used for this document ({0}) failed with the following exception message: {1} |
Class | E |
Explanation |
The service used to validate the document's structure threw an exception. |
Action |
Take appropriate action to resolve the problem described in the exception. |
7014 | Validation Service Failed |
Class | E |
Explanation |
The service used to validate the document's structure threw an exception. |
Action |
Take appropriate action to resolve the problem described in the exception. |
7015 | XML validation failed: does not apply to non-XML documents. |
Class | E |
Explanation |
Invoked the wm.tn.doc.xml:validate service with a document that is not XML. |
Action |
Supply an XML document. |
7016 | XML validation failed: no document content available |
Class | E |
Explanation |
Document is empty. |
Action |
Supply an XML document that has content. |
7017 | The validation service, {0} aborted processing of this document. The message was {1}. |
Class | E |
Explanation |
The document is not valid XML. |
Action |
Notify the document sender. |
7019 | Flat file validation failed. Document type is not "flat file". |
Class | E |
Explanation |
Attempted to use a flat file validation service to validate a document that is not a flat file. |
Action |
Supply a flat file document. |
7020 | Flat file validation failed: no document content available |
Class | E |
Explanation |
Document is empty. |
Action |
Supply a flat file document that has content. |
7021 | Flat file validation failed. Document type "{0}" has no parsing schema. |
Class | E |
Explanation |
The document matches a TN document type that indicates the document's structure should be validated, but no schema was defined. |
Action |
Update the TN document type, and specify the schema to use for document validation. |
7022 | Validation error |
Class | E |
Explanation |
The flat file document structure is invalid. |
Action |
Notify the document sender. |
1001 | Invalid or missing page number. |
Class | E |
Explanation |
This error occurs if a value for the pageNum variable is not specified for the wm.tn.enumerate:nth service or if a value for the pageNumber variable is not specified for the wm.tn.query:getQueryResults service. |
Action |
Specify a value for the pageNum variable or pageNumber variable. |
1002 | id is required. |
Class | E |
Explanation |
A value for the id input variable was not specified for either the wm.tn.enumerate:nth service or the wm.tn.enumerate:first service. |
Action |
Specify a value for the input variable id. |
1004 | Invalid time interval {0} for query. |
Class | E |
Explanation |
The wm.tn.query:createDocumentQuery service was supplied an invalid value for the input variable timeInterval. |
Action |
Provide a valid value for the input variable timeInterval. |
1005 | Unknown attribute ID: {0}. |
Class | E |
Explanation |
The wm.tn.query:createDocumentQuery service was provided an invalid value for the input variable attribId. |
Action |
Provide a valid value for the input variable attribId. |
1006 | Unknown attribute name: {0}. |
Class | E |
Explanation |
The wm.tn.query:createDocumentQuery service was provided an invalid value for the input variable attribName. |
Action |
Provide a valid value for the input variable attribName. |
1007 | Unknown op: {0}. |
Class | E |
Explanation |
The wm.tn.query:createDocumentQuery service was provided an invalid value for the input variable op. |
Action |
Provide a valid value for the input variable op. For more information about valid values, refer to the Trading Networks documentation. |
1008 | Invalid entry type {0} for event. |
Class | E |
Explanation |
The wm.tn.query:createEventQuery service was provided an invalid value for the input variable entryType. |
Action |
Provide a valid value for the input variable entryType. |
1009 | Invalid time interval {0} for query |
Class | E |
Explanation |
Either the wm.tn.query:createEventQuery service or the wm.tn.query:createTPAQuery service has an invalid value specified for the input variable timeInterval. |
Action |
Specify a valid value for the input variable timeInterval. |
1010 | Invalid timeCreated interval {0} for query |
Class | E |
Explanation |
The wm.tn.query:createTaskQuery service has an invalid value specified for the input variable timeCreated. |
Action |
Specify a valid value for the input variable timeCreated. |
1012 | Requested page is not available |
Class | D |
Explanation |
Requested page is not available. This error occurs when Trading Networks attempts to read beyond the end of the query results while invoking the wm.tn.enumerate:nth service. This error can also occur when data corresponding to the pageNumber input variable for the service wm.tn.query:getQueryResults is not available to Trading Networks. |
Action |
If the error occurs while invoking the wm.tn.enumerate:nth service, ensure the value specified for pageNum is valid. If the error occurs while invoking the wm.tn.query:getQueryResults service, ensure the value specified for pageNumber is valid. If the problem still persists, refresh the query. |
1013 | Unable to retrieve page. Operation timed out. |
Class | D |
Explanation |
The Integration Server might be busy doing other work. |
Action |
Attempt to retrieve the page again, or re-execute the query. |
1014 | Query execution failed. |
Class | E |
Explanation |
An exception occurred while executing a database query. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
1015 | External ID value is required. |
Class | E |
Explanation |
You created a profile query that specifies an externalIDType, but did not specify an externalIDValue. |
Action |
Provide a valid value for the externalIDValue input variable to the createProfileQuery service. |
1016 | fieldId[{0}] is null or empty. |
Class | E |
Explanation |
You created a profile query that specifies an externalIDValue, but you did not specify an externalIDType. |
Action |
Supply a valid value for the externalIDType input variable to the createProfileQuery service. |
2001 | Illegal query type: {0}. |
Class | E |
Explanation |
The query type specified as the input to the service is not valid. |
Action |
Supply a valid value for the query type. For a list of valid values, see the Trading Networks documentation. |
2002 | pageNumber should be a positive integer. |
Class | E |
Explanation |
The wm.tn.query:getQueryResults service was supplied an invalid value for the input variable pageNumber. |
Action |
Supply a valid value for the input variable pageNumber. The value must be a positive integer. |
2003 | A valid pageNumber is required. |
Class | E |
Explanation |
The pageNumber input variable for the wm.tn.query:getQueryResults service is not valid. |
Action |
Specify a valid value for pageNumber. The value must be a positive integer. |
2005 | Got null query result data for queryId={0}, page={1}. |
Class | E |
Explanation |
The wm.tn.query:getQueryResults service is not able to find the data corresponding to the specified queryId and pageNumber. |
Action |
Ensure the queryId and pageNumber are correct. If the issue persists, resumbit the query. |
2006 | Got null row at index {0}. |
Class | E |
Explanation |
There is no data corresponding to the specified index. |
Action |
Make sure the specified index is correct. |
2008 | Can not retrieve task {0}. |
Class | I |
Explanation |
While searching for tasks in My webMethods Server, no data corresponding to the specified taskid was found. |
Action |
Make sure the taskid is correct. If you update the taskid, then you must resubmit the query. |
2010 | User does not have adequate privilege to obtain requested data. |
Class | E |
Explanation |
The user's attempt to view the data failed because the user does not have permission to view the requested data. |
Action |
An administrator can grant permission to the user. For information about assigning permissions, refer to the Trading Networks documentation. |
2011 | Bizdoc with internal id={0} does not exist. |
Class | E |
Explanation |
The bizdoc with the specified docId cannot be found in the Trading Networks database . |
Action |
Make sure the docId is correct. If you change the docId, resubmit the query. |
2012 | Null bizdoc retrieved for internal id = {0}. |
Class | E |
Explanation |
The bizdoc with the specified docID cannot be found in the Trading Networks database. |
Action |
Make sure the specified docId is correct. If you change the docId, then you must resubmit the query. |
2013 | Can not parse {0}: {1}. |
Class | E |
Explanation |
The specified input value must be an integer. |
Action |
Supply a valid integer for the specified input value. |
2017 | Retrieved null content part for document id = {0}, part name = {1}. |
Class | E |
Explanation |
There are no content parts available for the bizdoc that corresponds to the specified docId. |
Action |
Make sure that the specified docId is correct and the content parts are recieved. After specifying the correct docId, resubmit the query. |
2019 | {0} encountered execution error. |
Class | |
Explanation |
An exception occurred while executing the service wm.tn.portal.queries.getContentPartBytes. |
Action |
The exception is in the full message. Take appropriate action to resolve the problem described in the exception. |
2027 | {0} encountered error resubmitting internalDocIDs[{1}] = {2}. |
Class | |
Explanation |
In webMethods Trading Networks, when you resubmit the Bizdocs, this exception is thrown if the resubmission fails. |
Action |
Contact your system administrator. |
2028 | {0} encountered error while resubmitting following internalDocIDs: {1}. Access denied, as user {2} doesn''t have permission to resubmit these documents. |
Class | |
Explanation |
In webMethods Trading Networks, while resubmitting the BizDoc documents, if the user does not have access permission to resubmit these documents, this error is thrown. |
Action |
The administrator needs to give permission to the user for resubmitting the BizDoc documents. |
2030 | {0} encountered null or empty internalDocIDs[{1}], this document was not reprocessed. |
Class | |
Explanation |
In webMethods Trading Networks, while reprocessing BizDocs, if null or empty internal DocIDs are passed, this error is thrown. |
Action |
Ensure that the internal DocIDs are not null or empty. |
2031 | {0} encountered error reprocessing internalDocIDs[{1}] {2}. |
Class | |
Explanation |
In webMethods Trading Networks, if an error is encountered while reprocessing BizDocs, this error is thrown. |
Action |
Contact your system administrator. |
2032 | {0} encountered error while reprocessing following internalDocIDs: {1}. Access denied, as user {2} doesn''t have permission to reprocess these documents. |
Class | |
Explanation |
In webMethods Trading Networks, if an error is encountered while reprocessing BizDocs, access is denied as the user does not have permission to reprocess the documents. |
Action |
Ensure that the administrator gives permission to the user to reprocess BizDocs. |
2034 | {0} encountered null or empty taskIDs[{1}] {2}, this task was not stopped. |
Class | |
Explanation |
In webMethods Trading Networks, while stopping the tasks, if null or empty taskIDs are passed, this error is thrown. |
Action |
Ensure that the taskID is not null or empty and try again. |
2035 | {0} encountered error stopping taskIDs[{1}] {2}. |
Class | |
Explanation |
In webMethods Trading Networks, while stopping the tasks, if the stopping fails for any reason, this error is thrown |
Action |
Contact your system administrator. |
2036 | {0} encountered error while stopping following tasks: {1}. Access denied, as user {2} doesn''t have permission to stop these tasks. |
Class | |
Explanation |
In webMethods Trading Networks, while stopping the tasks, if the user does not have permission to stop the tasks, this error is thrown. |
Action |
Ensure that the user has permission to stop the tasks. |
2038 | {0} encountered null or empty taskIDs[{1}], this task was not restarted. |
Class | |
Explanation |
In webMethods Trading Networks, while restarting tasks, if null or empty taskIDs are passed, this error is thrown. |
Action |
Ensure that the taskID is not null or empty and try again. |
2039 | {0} encountered error restarting taskIDs[{1}] {2}. |
Class | |
Explanation |
In webMethods Trading Networks, if restarting tasks fails, this error is thrown. |
Action |
Contact your system administrator. |
2040 | {0} encountered error while restarting following tasks: {1}. Access denied, as user {2} doesn''t have permission to restart these tasks. |
Class | |
Explanation |
In webMethods Trading Networks, while restarting tasks, if access is denied to the user, this error is thrown. |
Action |
Ensure that the user has access permission to restart tasks and try again. |
2042 | {0} encountered null or empty taskIDs[{1}], this task was not deleted. |
Class | |
Explanation |
In webMethods Trading Networks, while deleting tasks, if null or empty taskIDs are passed, this error is thrown. |
Action |
Ensure that the taskIDs passed are not null or empty, and try again. |
2043 | {0} encountered error deleting taskIDs[{1}] {2}. |
Class | |
Explanation |
In webMethods Trading Networks, if an error occurs while deleting the tasks, this error is thrown. |
Action |
Contact your system administrator. |
2044 | {0} encountered error while deleting following tasks: {1}. Access denied, as user{2} doesn''t have permission to delete these tasks. |
Class | |
Explanation |
In webMethods Trading Networks, while deleting tasks, if the user does not have permission, this error is thrown. |
Action |
Ensure that the user has permission to delete tasks, and try again. |
2048 | {0} encountered error while updating User Status for internalDocID {1}. Access denied, as user {2} doesn''t have permission to change UserStatus for this document. |
Class | |
Explanation |
In webMethods Trading Networks, while updating the user status for XXX, if access is denied because the user does not have permission to change UserStatus for this document, this error is thrown. |
Action |
Ensure to give permission to the user to change UserSTatus for the document, and try again. |
2050 | {0} encountered error while updating comments for internalDocID {1}. Access denied, as user {2} doesn''t have permission to edit comments for this document. |
Class | |
Explanation |
In webMethods Trading Networks, while updating comments for an internal document, if access is denied because the user does not have access permissions, this error is thrown. |
Action |
Ensure that the user has access permissions and try again. |
2052 | {0} encountered error while deleting following ActivityLogIDs: {1}. Access denied, as user {2} doesn't have permission to delete these activity logs. |
Class | |
Explanation |
In webMethods Trading Networks, while deleting activity logs, if access is denied because the user does not have access permissions, this error is thrown. |
Action |
Ensure that the user has access permissions, and try again. |
2054 | {0} can not reassign task {1} to {2}. |
Class | |
Explanation |
In webMethods Trading Networks, while reassigning the task to another server, if it is unsuccessful, this error is thrown. |
Action |
Contact your system administrator. |
2055 | {0} encountered error while reassigning following tasks. Access denied, as user {2} doesn''t have permission to reassign these tasks. |
Class | |
Explanation |
In webMethods Trading Networks, while reassigning tasks to another server, if the user does not have access permissions, this error is thrown. |
Action |
Ensure that the user has access permissions, and try again. |
2057 | ws.monitor.process.instance:getList returns null output. |
Class | |
Explanation |
In webMethods Trading Networks, while getting process information, if ws.monitor.process.instance:getList service returns null output, this error is thrown. |
Action |
Ensure that the ws.monitor.process.instance:getList service does not return null output, and try again. |
2058 | {0} can not get instance information for conversationId {1}. |
Class | |
Explanation |
In webMethods Trading Networks, when the user gets a null value of the process information for the conversation ID, this error is thrown. |
Action |
Ensure the conversation ID is valid and try again. |
2060 | {0} retrieved null instance at index 0 for conversationId {1}. |
Class | |
Explanation |
In webMethods Trading Networks, while getting process information for a conversation ID, if the instance at index 0 is null, this error is thrown. |
Action |
Ensure that the instance at index 0 is not null and try again. |
2065 | WmMonitor package is not enabled. |
Class | |
Explanation |
In webMethods Trading Networks, while checking process information, the WmMonitor package is not installed or enabled. |
Action |
Ensure that the WmMonitor package is installed and enabled. |
2066 | {0} can not submit document. |
Class | |
Explanation |
In webMethods Trading Networks, if resubmission of a modified document fails, this error is thrown. |
Action |
Contact your system administrator. |
2067 | {0} encountered error retrieving submitted document from pipeline. |
Class | |
Explanation |
In webMethods Trading Networks, while resubmitting documents with modifications, if the retrieved BizDoc is null, this error is encountered. |
Action |
Ensure that the resubmitted BizDoc is not null and try again. |
2071 | {0} encountered error while modifying & resubmitting following document {1}. Access denied, as user {2} doesn''t have permission to modify and resubmit this document. |
Class | |
Explanation |
In webMethods Trading Networks, while resubmitting modified BizDoc documents, if the user does not have access permissions, this error is displayed. |
Action |
Ensure that the user has access permissions to resubmit and modify BizDoc documents, and try again. |
2072 | {0} encountered execution error. |
Class | |
Explanation |
In webMethods Trading Networks, if the execution of any query related serivce fails, this error is displayed. |
Action |
Contact your system administrator. |
2074 | can not parse {0} to long number. |
Class | |
Explanation |
In webMethods Trading Networks Server portal util, in the getTimestampFromLong utility, if the time is not in numbered format, this error is thrown. |
Action |
Enter time in a numbered format and try again. |
2075 | null or empty field name |
Class | |
Explanation |
In webMethods Trading Networks portal util, the checkQueryColumnName utility throws this exception when the column name is null or empty. |
Action |
Enter a column name that is not null. |
2076 | Invalid query column name: {0}. |
Class | |
Explanation |
In webMethods Trading Networks portal util, the checkQueryColumnName utility throws an exception if the column name is invalid. |
Action |
Enter a valid column name and try again. |
2077 | Invalid document attribute ''{0}''. |
Class | |
Explanation |
In webMethods Trading Networks portal util, the checkQueryColumnName utility throws an exception if the query type is of doc query and the attribute list of the document does not contain the name passed to the utility. |
Action |
Ensure that the attribute list of the document contains the name passed to the utility and try again. |
2078 | Invalid whichQuery value ({0}) for PortalUtils.checkQueryColumnName(). |
Class | |
Explanation |
In webMethods Trading Networks portal util, the checkQueryColumnName utility throws an exception if the query type passed to the utility is invalid. |
Action |
Ensure to enter a valid query type and try again. |
2079 | Invalid value for {0}: null or empty. |
Class | |
Explanation |
In webMethods Trading Networks portal util, the validateOperator utility throws an exception if the operator passed to the utility is null or empty. |
Action |
Pass a valid operator to the utility and try again. |
2080 | Invalid operator {0} for data type {1}. |
Class | |
Explanation |
In webMethods Trading Networks portal util, the validateOpValPair utility throws an exception if the operator passed to the utility is null or empty. |
Action |
Enter a valid operator and try again. |
2081 | Invalid null value for {0}, corresponding operator is {1}. |
Class | |
Explanation |
In webMethods Trading Networks portal util, the validateOpValPair utility throws an exception if the value supplied corresponding to an operator is null. |
Action |
Enter a not null value corresponding to the operator. |
2082 | Illegal value for number query, {0}: {1}. |
Class | |
Explanation |
In webMethods Trading Networks portal util, the validateOpValPair utility throws this exception if the value passed to this utility corresponding to an operator is not in numeric value. |
Action |
Pass the value to the utility in numeric value and try again. |
2083 | Illegal value for date and time query, {0}: {1}. |
Class | |
Explanation |
In webMethods Trading Networks portal util, the validateOpValPair utility throws this exception if the value passed to this utility corresponding to an operator is not parsed to a long value. |
Action |
Enter a numeric long value for the date and time query and try again. |
2084 | Unable to display the error message. An internal error has occured. Please contact customer support. |
Class | |
Explanation |
In webMethods Trading Networks portal util, the decodeErrorMessage2 utility throws an exception and is unable to decode the error message. |
Action |
Contact your system administrator. |
2085 | Can not get related document information for docId={0}: null data returned |
Class | |
Explanation |
In webMethods Trading Networks, while getting document information for a document ID, If the data extracted for the document ID is null, it throws an error. |
Action |
Contact your system administrator. |
2086 | Invalid whichQuery value {0}. |
Class | |
Explanation |
In webMethod Trading Networks, this error message is shown if the query type (whichQuery) for creating a query is invalid. |
Action |
Enter a valid query type (whichQuery) in creating a query. |
2088 | Invalid non-number value for queryInput/pageSize: {0}. |
Class | |
Explanation |
In webMethods Trading Networks, in creating a query, the query input or page size entered is a non-number value. |
Action |
Enter a valid numeric value for the query input or the page size. |
2089 | queryInput/pageSize value is equal or less than 0. |
Class | |
Explanation |
In the webMethods Trading Networks, while creating or retrieving a query, the queryInput or pageSize value entered is not valid because it is equal to or less than 0. |
Action |
Enter a valid queryInput or pageSize value for creating or retrieving a query. |
2090 | queryInput/criteria/dateRange/startDate {0} is after queryInput/criteria/dateRange/endDate {1}.}, |
Class | |
Explanation |
In webMethods Trading Networks, while creating a query, if the start time is earlier than the end time, this error is shown. |
Action |
Ensure to correct the start time. |
2091 | Invalid null value for queryInput/sortOrder[{0}]. |
Class | |
Explanation |
In webMethods Trading Networks, while creating or retrieving a query, if any of the sorting columns is null, this error is shown. |
Action |
Ensure that the sorting column is not null. |
2092 | {0} queryInput/sortOrder[{1}]/columnName ({2}) is not valid, ignored this column for query sorting. |
Class | |
Explanation |
In webMethods Trading Networks, while creating a query, if the sorting column specified in the query input is not valid, the column is ignored for query sorting. |
Action |
Ensure to enter a valid sorting column in the query. |
2093 | Invalid null value for queryInput/criteria/fields[{0}]. |
Class | |
Explanation |
In webMethods Trading Networks, while creating a query, if any of the given fields is null, this error is shown. |
Action |
Ensure to enter a valid valiue (not null) for all the fields. |
2094 | Invalid null or empty queryInput/criteria/fields[{0}]/fieldName value. |
Class | |
Explanation |
In webMethods Trading Networks, while creating a query, if the field name is null or empty, this error is thrown. |
Action |
Ensure that all field names are valid. |
2095 | query criteria for field {0} already exists, additional criteria found at index {1}. |
Class | |
Explanation |
In webMethods Trading Networks, while creating a query, if the query criteria for the field already exists, this error is thrown. |
Action |
Enter a query criteria that is unique. |
2096 | Invalid value: {0} for queryInput/criteria/fields/isOrQuery. |
Class | |
Explanation |
In webMethods Trading Networks, while creating a query, an invalid value is entered for the IsOrQuery (value of OR is undefined). |
Action |
Enter a valid value for the IsOrQuery (value of OR). |
2097 | queryInput/criteria/fields[{0}]/criteria is null or 0-length. |
Class | |
Explanation |
In webMethods Trading Networks, while creating a query object based on filter criteria, the criteria list for query fields is null or empty. |
Action |
Enter a valid criteria list for query fields in queryInput. |
2100 | Invalid value for {0}: null or empty. |
Class | |
Explanation |
In webMethods Trading Networks, while creating a query object based on filter criteria, if the criteria does not contain any operator, this error is thrown. |
Action |
Enter the operator for the criteria. |
2101 | {0} criteria can only be a list plus a dynamic profile query. |
Class | |
Explanation |
In webMethods Trading Networks, while creating a query object based on filter criteria, if the query type is a doc query, there should be only one list of values and profile query in the sender and receiver criteria. |
Action |
Enter only one list of values and profile query in the sender and receiver criteria and try again. |
2102 | Invalid value for {0}. |
Class | |
Explanation |
In webMethods Trading Networks, while creating a query object based on filter criteria, if the query is of jobQuery type, the internal doc ID or the sender ID or the task ID or the server ID or the instance ID cannot be null. |
Action |
Ensure that the internal doc ID or the sender ID or the task ID or the server ID or the instance ID are not null and try again. |
2103 | Can not understand query {0}. |
Class | |
Explanation |
In webMethods Trading Networks, while performing a query, if the query type is not a doc, task, event, profile, bizdoc type, attrib, tpa, or invite type of query, this error message is thrown. |
Action |
Enter the valid query type and try again. |
1003 | Service manager create failed for server {0} - {1} |
Class | E |
Explanation |
Encountered a problem while communicating with the database. See the text in the SQL exception for details. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1005 | Unable to get profile for {0} - {1} |
Class | E |
Explanation |
Encountered a problem while communicating with the database. See the text in the SQL exception for details. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1006 | Unable to remove delivery service {0} - {1} |
Class | E |
Explanation |
Encountered a problem while communicating with the database. See the text in the SQL exception for details. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1014 | Unable to create delivery task {0} - service {1} does not exist |
Class | E |
Explanation |
Attempted to deliver a document using a non-existent delivery service. |
Action |
Correct the serviceName parameter sent to wm.tn.delivery:deliver. |
1027 | Unable to create service data for partner {0} - {1} |
Class | E |
Explanation |
Attempted to deliver a document to a partner that cannot receive the document. Receiver is either INACTIVE or is My Enterprise (the entity hosting this Trading Network). |
Action |
Deliver the document to a valid trading partner with an ACTIVE status. |
1028 | Unable to set private key and certificate chain - {0} |
Class | E |
Explanation |
Encountered an exception while setting the certificate chain and private key in preparation to deliver a document. See the exception message for details. |
Action |
Take appropriate action to resolve the problem described in the exception. |
1032 | {0} refreshing {1} cache: {2} |
Class | E |
Explanation |
Encountered an exception while refreshing an internal cache. See the exception message for details. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1038 | Error transporting via {0}: {1} |
Class | E |
Explanation |
Encountered an exception while delivering a document. See the exception message for details. |
Action |
Take appropriate action to resolve the problem described in the exception, if possible. It may be a network error beyond your control. |
1040 | {0} initializing task store: {1} |
Class | E |
Explanation |
Encountered an exception while initializing internal caches used for document delivery. See the exception message for details. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1041 | {0} deleting delivery service {1}: {2} |
Class | E |
Explanation |
Encountered an exception while removing a registered delivery service from the database. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1050 | {0} deleting task {1}: {2} |
Class | E |
Explanation |
Encountered an exception while deleting a delivery or routing task. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1054 | DeliveryUtils init error: Unable to get profile store: {0} |
Class | E |
Explanation |
Could not access the profile store during server initialization. |
Action |
Copy the exception details and call Software AG Global Support. |
1055 | Unable to register delivery service {0} - {1} |
Class | E |
Explanation |
Encountered an exception while registering a delivery service. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1064 | Unable to initialize delivery interface |
Class | E |
Explanation |
Encountered an exception while initializing the Delivery Service Manager. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1065 | Unable to register delivery defaults |
Class | E |
Explanation |
Encountered an exception while registering the built-in delivery services. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1066 | Unable to deliver bizdoc by service |
Class | E |
Explanation |
Encountered an exception when wm.tn.deliver:deliverByService was invoked. |
Action |
Take appropriate action to resolve the problem described in the exception, if possible. It may be a network error beyond your control. |
1067 | Error delivering bizdoc |
Class | E |
Explanation |
Encountered an exception while delivering a document. |
Action |
Take appropriate action to resolve the problem described in the exception, if possible. It may be a network error beyond your control. |
1068 | Error getting delivery job |
Class | E |
Explanation |
Encountered an exception while retrieving a delivery job. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1069 | Error getting delivery job output |
Class | E |
Explanation |
Encountered an exception while retrieving the output of a reliable delivery job. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1070 | Error getting delivery job status |
Class | E |
Explanation |
Encountered an exception while retrieving the status of a delivery job. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1071 | Error removing delivery job |
Class | E |
Explanation |
Encountered an exception while removing a reliable delivery job. |
Action |
Use the JDBC Pools page on the Integration Server Administrator to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1072 | Error restarting delivery job |
Class | E |
Explanation |
Encountered an exception while restarting a reliable delivery job. |
Action |
Use the JDBC Pools page on the Integration Server Administrator to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1073 | Error getting registered delivery service {0} |
Class | E |
Explanation |
Encountered an exception while retrieving a registered delivery service. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1074 | Error getting registered delivery services |
Class | E |
Explanation |
Encountered an exception while retrieving the set of registered delivery services. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1075 | Error determining if delivery service {0} is registered |
Class | E |
Explanation |
Encountered an exception while retrieving a named registered delivery service. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1076 | Error refreshing service cache |
Class | E |
Explanation |
Encountered an exception while refreshing the cache of registered delivery services. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1077 | Error registering service {0} |
Class | E |
Explanation |
Encountered an exception while registering a delivery service. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1078 | Error removing service {0} |
Class | E |
Explanation |
Encountered an exception while unregistering a delivery service. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1081 | Couldn''t query delivery service table |
Class | E |
Explanation |
Encountered a SQLException while reading delivery services. |
Action |
Take appropriate action to resolve the problem described in the exception, if possible. |
1082 | Couldn''t query delivery job table |
Class | E |
Explanation |
Encountered a SQLException while reading delivery jobs. |
Action |
Take appropriate action to resolve the problem described in the exception, if possible. |
1083 | Property watt.server.smtpServer is not set |
Class | E |
Explanation |
Cannot send e-mail messages because the system property, watt.server.smtpServer, has not been set. |
Action |
Use the Properties page of the Integration Server Administrator to supply a value for the watt.server.smtpServer property. |
1084 | Receiver of document cannot be self |
Class | E |
Explanation |
A document is being sent from this Trading Networks server and the receiver of the document is a host of Trading Network. You cannot send a document to yourself. |
Action |
Ensure that the receiver of the document is not a host of Trading Networks. |
1085 | Receiver of document is not Active |
Class | E |
Explanation |
Status of the partner profile for the receiver of the document is not in active state. Documents can only be sent to active partners. |
Action |
Ensure the receiver of the document is an active partner. |
1086 | Unknown protocol: {0} |
Class | E |
Explanation |
Attempted to send a document via an unknown protocol. Documents must be sent using one of the registered delivery services. |
Action |
Use a registered delivery service to send the document. |
1087 | Destination info not found |
Class | E |
Explanation |
Attempting to send a document, but the receiver's destination information cannot be found. |
Action |
Examine the document to learn the intended receiver. Make sure the receiver's profile has valid delivery method information. |
1090 | Unable to initialize DeliveryStore {0} |
Class | E |
Explanation |
Encountered an exception during initialization. |
Action |
Take appropriate action to resolve the problem described in the exception. |
1092 | Service not registered |
Class | E |
Explanation |
Attempted to remove a delivery service that is not registered. |
Action |
Check the name of the registered delivery service you want to remove. |
1096 | Delivery queue {0} refers to Delivery service {1} which is not registered. |
Class | E |
Explanation |
In webMethods Trading Networks, during batch delivery of queued tasks, if the delivery service used is not registered and the delivery queue refers to it, this error is thrown. |
Action |
Use the webMethods Trading Networks to update the delivery queue so that it uses a valid batch delivery service. |
1097 | Cannot deliver document. Receiver is not active. (DocID={0}, ReceiverD={1}) |
Class | E |
Explanation |
Queued a document for scheduled delivery, but the receiver is inactive and cannot receive documents. |
Action |
Activate the receiver's trading partner profile, if appropriate. |
1098 | Unable to get document content for delivery. (DocID={0}) |
Class | E |
Explanation |
Queued a document for scheduled delivery and encountered an error while retrieving document content. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1099 | Cannot register a delivery service with the same name as a built-in delivery service ({0}). |
Class | E |
Explanation |
This name is reserved for a built-in Trading Networks delivery service. |
Action |
Change the delivery service's name. |
1101 | Cannot get certificate information from security store for partner {0} in getting delivery information: {1} |
Class | E |
Explanation |
Encountered an exception while retrieving the certificate chain and private key for a trading partner. |
Action |
Take appropriate action to resolve the problem described in the exception. |
1105 | Unable to get profile for partner {0} - {1} |
Class | E |
Explanation |
Encountered an exception while retrieving a trading partner profile. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1106 | Unable to get destination info for partner {0} - {1} |
Class | E |
Explanation |
Encountered an exception while retrieving destination information from a trading partner profile in preparation for document delivery. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. If no connection problem exists, take appropriate action to resolve the problem described in the exception. |
1107 | Encountered error while delivering by context: {0} |
Class | E |
Explanation |
Encountered an exception while delivering a document using an internal webMethods protocol. |
Action |
Take appropriate action to resolve the problem described in the exception, if possible. It may be a network error beyond your control. |
1108 | Unable to deliver document {0}. Delivery service [{1}] does not exist |
Class | E |
Explanation |
Document delivery failed because the associated delivery service does not exist. |
Action |
Create the missing delivery service or specify a different delivery service. |
1109 | The document (id={0}) was not persisted. The "{1}" delivery service will not be invoked. The document will not be delivered. |
Class | |
Explanation |
In webMethods Trading Networks, while delivering documents, if the BizDoc is not persisted, the delivery service is not invoked and the document is not delivered. |
Action |
Contact your system administrator. |
1115 | Event found to be null |
Class | |
Explanation |
In webMethods Trading Networks, while writing routing events, if the event is found to be null, then this error is thrown. |
Action |
Contact your system administrator. |
1117 | Encountered error while creating TN document from service response: {0} |
Class | |
Explanation |
In webMethods Trading Networks, while delivering a document via WebService, if the document cannot be created from response data, this error is thrown. |
Action |
Contact your system administrator. |
1118 | Encountered error while adding service response to bizdoc: {0} |
Class | |
Explanation |
In webMethods Trading Networks, while delivering a document via WebService, if the response data cannot be added as content to the BizDoc, this error is thrown. |
Action |
Contact your system administrator. |
2002 | An error occurred when this partner polled for documents on this server. The original error message was {0}. |
Class | E |
Explanation |
An exception was thrown while polling for documents. |
Action |
Take appropriate action to resolve the problem described in the exception. |
2014 | Error polling for documents |
Class | E |
Explanation |
An exception was thrown while polling for documents. |
Action |
Take appropriate action to resolve the problem described in the exception. |
2017 | An error occurred when trying to connect to this partner for polling. The original error was: {0} |
Class | E |
Explanation |
In webMethods Trading Networks, during a remote checking of a partner, if the connection to the partner cannot be made, this error is thrown. |
Action |
Ensure that the partner connection information is valid and try again. |
2018 | Error connecting for polling |
Class | E |
Explanation |
An error occurred when trying to connect to this partner for polling. |
Action |
Take appropriate action to resolve the problem described in the exception. You might need to contact your trading partner about the error. |
2021 | The user account that schedules polling jobs is {0}. The account does not exist on the B2B Server. |
Class | E |
Explanation |
In webMethods Trading Networks, during scheduling of a polling job, if the user account that starts the polling job does not exist on the B2B server, this error is thrown. |
Action |
Create a user account for the user and reload the WmTN package or restart the Integration Server. |
2031 | An error occurred in the process of accepting a document polled from this partner. The original document ID was {0}. The original error message was {1}. |
Class | E |
Explanation |
In webMethods Trading Networks, if any error occurs during the process of submitting a document locally that is polled from a remote partner, this error is thrown. |
Action |
Contact your system administrator. |
2037 | Error accepting document |
Class | E |
Explanation |
An exception was thrown while accepting a document polled from a partner. |
Action |
Take appropriate action to resolve the problem described in the exception. |
2052 | Unable to initialize TN Polling. |
Class | E |
Explanation |
An exception was thrown during initialization. |
Action |
The exception was written to the server log. See the log for details. Take appropriate action to resolve the problem described in the exception. |
2053 | User {0} is not an administrator and attempted to accept a document (docID={1}) that does not belong to him. |
Class | E |
Explanation |
A partner attempted to accept a pollable document; however, the partner is not the specified receiver of the document. |
Action |
Review the log message. Contact the partner identified in the log message to explain that a partner can only accept pollable documents for which that partner is the specified receiver. |
2054 | You do not have the authority to accept this document. Only administrators may accept documents that they did not receive. |
Class | E |
Explanation |
A partner attempted to accept a pollable document; however, the partner is not the specified receiver of the document. |
Action |
Review the log message. Contact the partner identified in the log message to explain that a partner can only accept pollable documents for which that partner is the specified receiver. |
2055 | No document with an ID of {0} exists. No document accepted. |
Class | E |
Explanation |
A partner is trying to accept a pollable document that does not exist within Trading Networks. |
Action |
Review the log message. Work with the partner specified in the log message to resolve the issue. |
3001 | {0} is required. |
Class | E |
Explanation |
A service was invoked, and a required input variable was not supplied. |
Action |
Supply a value for the specified variable. |
3002 | Unable to save queue "{0}". |
Class | E |
Explanation |
Attempt to insert queue information into the Trading Networks database failed. |
Action |
Ask your database administrator (DBA) to examine the database logs to determine the cause of the problem. |
3003 | Cannot reassign tasks to a private queue. |
Class | E |
Explanation |
Each partner might have its own private queue. Private queues are defined in the profile for a partner. A private queue can contain only tasks for the partner identified by the profile; private queues cannot contain tasks from other partners. |
Action |
You can reassign these tasks to a public queue. |
3004 | Unable to remove queue "{0}". |
Class | E |
Explanation |
Attempt to delete queue information from the Trading Networks database failed. |
Action |
Ask your database administrator (DBA) to examine the database logs to determine the cause of the problem. |
3005 | Unable to update queue "{0}". |
Class | E |
Explanation |
Attempt to update queue information in the Trading Networks database failed. |
Action |
Ask your database administrator (DBA) to examine the database logs to determine the cause of the problem. |
3006 | The queue cannot be deleted because there is data that depends on it. |
Class | E |
Explanation |
The queue cannot be deleted for one or more of the following reasons: 1) There might be tasks currently on the queue. 2) There are partner profiles and/or processing rules that refer to the queue. A list of objects that depend on the queue follow this message. |
Action |
Take one or more of the following actions: 1) If there are tasks on the queue, place it in a DRAINING state so that the queue will empty. After all tasks in the queue are processed, you can delete the queue. 2) If there are profiles and/or processing rules that refer to the queue, remove those references. After you remove the references, you can delete the queue. |
3007 | There are {0} tasks on the queue. |
Class | E |
Explanation |
The queue cannot be removed because it has tasks on it. |
Action |
Place the queue in a DRAINING state so that the queue will empty. After the tasks in the queue have been processed, you can delete it. |
3008 | There are {0} partner profiles that refer to the queue. |
Class | E |
Explanation |
The queue cannot be removed because one or more partner profiles refers to it. |
Action |
This message is followed by a list of partners whose profiles refer to the queue. Modify these profiles so they no longer refer to the queue being removed. After you remove the references, you can delete the queue. |
3009 | There are {0} processing rules that refer to the queue. |
Class | E |
Explanation |
The queue cannot be removed because one or more processing rules refers to it. |
Action |
This message is followed by a list of processing rules that refer to the queue. Modify these processing rules so they no longer refer to the queue being removed. After you remove the references, you can delete the queue. |
3012 | There is no task with the supplied ID ({0}). |
Class | E |
Explanation |
The wm.tn.queuing:updateQueuedTask service was supplied an invalid task ID. |
Action |
Supply a valid task ID. |
3013 | updateQueuedTask may only be invoked for tasks that are currently being processed from a DeliveryQueue. This task ({0}) has a status of {1}. |
Class | E |
Explanation |
You attempted to run the wm.tn.queuing:updateQueuedTask service for a task; however, you did not first invoke the wm.tn.queuing:getQueuedTask service. |
Action |
Be sure to use the wm.tn.queuing:getQueuedTask service to retrieve a task from a queue. |
3018 | Attempted to update a DeliveryQueue that has not been registered (queue name={0}). |
Class | E |
Explanation |
The specified queue does not exist. |
Action |
Either supply a valid queue name or use My webMethods to define the delivery queue. |
3019 | status must be "success" or "fail". {0} was supplied. |
Class | E |
Explanation |
The wm.tn.queuing:updateQueuedTask service was supplied an invalid status. |
Action |
Supply a valid status value. |
3020 | Attempted to remove a DeliveryQueue that has not been registered (queue name={0}). |
Class | E |
Explanation |
The specified queue does not exist. |
Action |
Supply a valid queue name. |
3021 | Unable to decode TypeData for a DeliveryJob (ID={0}) while dequeuing from {1} |
Class | E |
Explanation |
Internal error. |
Action |
Contact Software AG Global Support. |
3023 | The scheduled delivery date/time is in the past. |
Class | E |
Explanation |
Trading Networks cannot schedule delivery to run in the past. |
Action |
Supply a future date and time. |
3024 | The delivery schedule is empty. It has been ignored. |
Class | E |
Explanation |
The delivery queue does not have a delivery schedule. The operation has failed. |
Action |
If you receive this error while invoking a service, make sure that you are supplying a valid DeliveryQueue object that contains a DeliverySchedule. If you receive this error while using My webMethods, contact Software AG Global Support. |
3025 | Delivery schedule dates must be in the format "YYYY/MM/DD" and times must be in the format "hh:mm:ss" |
Class | E |
Explanation |
A date and/or time in the delivery schedule is invalid. |
Action |
All dates and times in the delivery schedule must be in the specified formats. |
3027 | Unable to schedule delivery for queue "{0}". The pipeline for the delivery service does not contain "queue". |
Class | E |
Explanation |
The variable "queue" was not supplied in the pipeline. |
Action |
Supply the name of the delivery queue. |
3028 | The delivery schedule has no schedule type. It has been ignored. |
Class | E |
Explanation |
The delivery schedule must have a type of "repeat", "complex", or "once". |
Action |
Set the type on the delivery schedule to a valid value. |
3029 | The queue "{0}" does not exist. |
Class | E |
Explanation |
In webMethods Trading Networks, while updating a queue, if the queue does not exist, this error is thrown. |
Action |
Ensure that the queue that is to be updated exists, and try again. |
3037 | Scheduled delivery failed. No more retries. |
Class | E |
Explanation |
The final attempt to delivery a document failed. |
Action |
See the message TRNSERV.000022.000038 for full details. |
3038 | Scheduled delivery of document {0} failed. No more retries. {1} |
Class | E |
Explanation |
The final attempt to deliver a document failed. |
Action |
See the error message for details. You might need to contact your trading partner. |
3039 | The queue "{0}" has a status of "{1}". It is not accepting documents. This document will not be delivered. |
Class | E |
Explanation |
Attempted to route a document to a delivery queue that is either disabled or draining. Queues in either of these statuses cannot accept documents. |
Action |
Either change the status of this queue or route the document to a different queue. |
3040 | Unable to validate private queue/partner relationship (id={0}) because the partner could not be retrieved. The queue has been saved with a "disabled" status. |
Class | E |
Explanation |
You can only create a private queue for a partner that has an active profile. The specified partnerID identifies a partner that does not exist or whose profile is not active. |
Action |
Perform one of the following actions: 1) Specify a different queue. 2) If the profile is not active, change its status to active. |
3041 | Private queue "{0}" has a status of "{1}", but the partner''s profile is not active. The queue has been saved with a "disabled" status. |
Class | E |
Explanation |
Trading Networks attempted to route a document to a private queue that is defined for a profile that is not active. Trading Networks can only route documents to private queues belonging to active partners; it cannot route documents to private queues of inactive partners. Trading Networks has disabled the queue. |
Action |
Enable the partner by changing the profile status to active. Then enable the partner's private queue. |
3042 | Delivery not scheduled from queue. |
Class | E |
Explanation |
In webMethods Trading Networks, while scheduling delivery of documents from queues, if the queue is private and the partner is either inactive or not found, this error is thrown. |
Action |
Ensure that the partner of the private queue is available and active, and try again. |
3044 | Document was not queued for delivery on queue {0}. The receiver''s profile was not found. (receiverID={1}). |
Class | E |
Explanation |
A processing rule indicated that the document should be delivered to a queue that is associated with a receiver. However, there is no profile for the receiver. |
Action |
Use My webMethods to determine who the intended receiver is. If the receiver is valid but does not have a profile, create a partner profile for the receiver. If the receiver is not valid, notify the document sender that the receiver information in the document is incorrect. |
3045 | Document was not queued for delivery on queue {0}. The receiver is not active (receiverID={1}). |
Class | E |
Explanation |
A processing rule indicated that the document should be delivered to a queue that is associated with a receiver. However, the receiver's profile is not active. Trading Networks can only route documents to active partners. |
Action |
Enable the partner by changing the profile status to active. Then enable the partner's private queue. |
3046 | The queue "{0}" does not exist. |
Class | E |
Explanation |
The wm.tn.queuing:deliverBatch service was supplied an invalid queue name. |
Action |
Supply the name of an existing queue. |
3048 | The scheduled {0} is invalid. Format must be YYYY/MM/DD |
Class | E |
Explanation |
In webMethods Trading Networks, while validating scheduling of tasks, if the format of the schedule date is invalid, this error is thrown. |
Action |
Enter the schedule date in the correct format and try again. |
3049 | The scheduled {0} is invalid. Format must be hh:mm:ss |
Class | E |
Explanation |
In webMethods Trading Networks, while validing the schedule task, if the format of the time is invalid, this error is thrown. |
Action |
Enter the schedule time in the correct format and try again. |
3056 | Interval is required. |
Class | E |
Explanation |
An interval must be specified for repeating tasks. |
Action |
Supply an interval value. |
3057 | Interval is not a valid integer. |
Class | E |
Explanation |
In webMethods Trading Networks, while validing a scheduling task, if the time interval is not a valid integer, this error is thrown. |
Action |
Enter the time interval as a valid integer and try again. |
3058 | Interval must be greater than zero. |
Class | E |
Explanation |
In webMethods Trading Networks, while validing a scheduling task, if the time interval is not greater than zero, this error is thrown. |
Action |
Enter the time interval as a valid integer greater than zero and try again. |
3059 | End date/time is in the past. |
Class | E |
Explanation |
In webMethods Trading Networks, while validing a scheduling task, if the end date/time is occuring in the past, this error is thrown. |
Action |
Enter a valid end date/time and try again. |
3060 | End date/time is before start date/time. |
Class | E |
Explanation |
In webMethods Trading Networks, while validing a scheduling task, if the end date/time occurs before the start date/time, this error is thrown. |
Action |
Enter the valid end date/time and try again. |
3061 | Could not construct a valid timestamp from this schedule. Dates must be in YYYY/MM/DD format and times must be in hh:mm:ss format. |
Class | E |
Explanation |
In webMethods Trading Networks, while validating the scheduling task, if the end date is not in YYYY/MM/DD format and the end time is not in hh:mm:ss format, this error is thrown. |
Action |
Ensure that the end date and time are in the correct format and try again. |
3062 | A queue with this name already exists. |
Class | E |
Explanation |
In webMethods Trading Networks, while registering a queue, if a queue with this name already exists, this error is thrown. |
Action |
Ensure to have a unique queue name and try again. |
3063 | There is a task on the queue (task id={0}). |
Class | E |
Explanation |
The queue cannot be removed because it has tasks on it. |
Action |
Place the queue in a DRAINING state so that the queue will empty. After the tasks in the queue have been processed, you can delete it. |
3064 | The profile for {0} refers to the queue (partner id={1}). |
Class | E |
Explanation |
The queue cannot be removed because one or more partner profiles refers to it. |
Action |
This message is followed by a list of partners whose profiles refer to the queue. Modify these profiles so they no longer refer to the queue being removed. After you remove the references, you can delete the queue. |
3065 | The {0} processing rule refers to the queue. |
Class | E |
Explanation |
The queue cannot be removed because one or more processing rules refers to it. |
Action |
This message is followed by a list of processing rules that refer to the queue. Modify these processing rules so they no longer refer to the queue being removed. After you remove the references, you can delete the queue. |
3066 | If an end time is supplied, an end date must also be supplied. |
Class | E |
Explanation |
In webMethods Trading Networks, while validating a scheduling task, if the delivery schedule is of complex type, and the end time is supplied but the end date is not supplied, this error is thrown. |
Action |
Ensure to also supply the end date along with the end time and try again. |
3067 | Unable to import partner private queue {0}. Partner profile for {1} does not exist. |
Class | |
Explanation |
In webMethods Trading Networks, while importing Trading Networks assets, if the partner profile for which a partner private queue is to be imported does not exist, this error is thrown. |
Action |
Ensure that the partner profile exists, and try again. |
4002 | Processing recursion was detected: the processing rule {0} invoked itself, most recently with document {1}. Processing fails. |
Class | E |
Explanation |
A processing rule recursed. Either no recursion is allowed, or recursion is allowed, and the maximum recursion level was exceeded. |
Action |
If you want a processing rule to recurse (to call itself), set the tn.recursion.max property to an appropriate value. If you do not want the processing rule to recurse, check the service that the processing rule invokes. The service is submitting a document that matches the same routing rule. |
4004 | If alertPartner is not specified, neither alertContact, alertSubject nor alertMessage may be specified. |
Class | E |
Explanation |
An invalid combination of input values was sent to wm.tn.route:create. |
Action |
If you are not supplying a value for alertPartner, do not supply a value for alertContact, alertSubject, or alertMessage. |
4008 | Error sending mail: {0} |
Class | E |
Explanation |
Encountered an exception while sending an email alert. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4011 | An error occurred invoking the processing service ({2}) for this document. The original error was of type {0}; the message was {1} and the service output this pipeline: {3} |
Class | E |
Explanation |
A processing rule invoked a service, and that service returned an error. |
Action |
Take appropriate action to resolve the problem described in the error message. |
4012 | Error signaled in processing service |
Class | E |
Explanation |
A processing rule invoked a service, and that service returned an error. |
Action |
See the full message (TRNSERV.000014.000012) for details. |
4013 | An internal error prevented processing from finishing normally on this document. The aborted rule was {0}, and the original error message was {1}. |
Class | E |
Explanation |
See the exception message for details. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4014 | Internal processing error |
Class | E |
Explanation |
See the full message (TRNSERV.000014.000013) for details. |
Action |
See the full message for details. |
4017 | {0} loading rules |
Class | E |
Explanation |
Encountered an exception while reading processing rules from the database. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4023 | {0} saving rules |
Class | S |
Explanation |
Encountered an exception while saving processing rules to the database. Trading Networks wrote the exception to the server log. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4027 | An exception occurred invoking a processing service for document {0}. The processing service was {1}, and the original error message was: {2}. |
Class | E |
Explanation |
A processing rule invoked a service, and that service threw an exception. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4028 | An error occurred invoking the processing service {0} for this document. The original error was {1}. |
Class | E |
Explanation |
A processing rule invoked a service, and that service threw an exception. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4029 | Service invoke err: {0} |
Class | E |
Explanation |
A processing rule invoked a service, and that service threw an exception. |
Action |
See the full message for details. |
4034 | Error sending via {0} |
Class | E |
Explanation |
Error encountered. |
Action |
See the full message for details. |
4035 | Fatal processing error: {0} |
Class | E |
Explanation |
Encountered an exception while processing a document. See the exception for details. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4038 | Changing the user status on document {0} generated an error. The original error message was: {1} |
Class | W |
Explanation |
Encountered an exception while changing the status for a document. See the exception for details. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4039 | Error changing status |
Class | E |
Explanation |
Encountered an exception while changing the status for a document. See the exception for details. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4040 | An error occurred sending via protocol {0}. The original error message was: {1} |
Class | E |
Explanation |
Encountered an exception while sending a document. See the exception message for details. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4041 | Error delivering document |
Class | E |
Explanation |
Encountered an exception while sending a document. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4052 | Processing Alert Failed |
Class | E |
Explanation |
Encountered an error while sending an email alert. |
Action |
See full message for details. |
4053 | The server was unable to send email to {0} during processing. The subject of the email was {1}. The error message was: {2}. |
Class | E |
Explanation |
Encountered an error while sending an email alert. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4054 | PROCESSING ERROR: partner contact {0}/{1} is not defined |
Class | E |
Explanation |
Processing is configured to send alerts to a specific contact type, but the partner profile does not have a contact of that type. |
Action |
Either change the processing rule to send alerts to a different contact type (or use a hard-coded email address), or create a contact of this type for the partner. |
4055 | Partner {1} sent this document posing as {0}. |
Class | E |
Explanation |
When Trading Networks receives a document, it determines the partner initiating the request based on the user account that sent the document. The partner that sent the request does not match the sender from within the document content. |
Action |
You might want to notify the partner who sent the document and/or the partner being impersonated. |
4056 | Partner {1} sent document {2} posing as {0}. |
Class | E |
Explanation |
When Trading Networks receives a document, it determines the partner initiating the request based on the user account that sent the document. The partner that sent the request does not match the sender from within the document content. |
Action |
You might want to notify the partner who sent the document and/or the partner being impersonated. |
4057 | Partner ID mismatch |
Class | E |
Explanation |
The partner who sent the document does not match the partner in the document content. |
Action |
See full message for details. |
4058 | The sender of this document ({0}) has been deleted. Documents from this partner are not permitted at this time. |
Class | E |
Explanation |
Trading Networks received a document from a partner whose profile was deleted. Although Trading Networks still maintains a copy of the deleted profile in its database, it will not accept documents nor process documents from the partner. |
Action |
If you do not want to accept documents from the partner, you can either ignore this error or notify the partner to stop sending documents. If you want to receive and process documents from this partner, use the wm.tn.profile:undeleteProfile service to reinstate the partner's profile. |
4059 | The sender of document {2} ({0}) had been deleted. Documents from this partner are not permitted at this time. |
Class | E |
Explanation |
Trading Networks received a document from a partner whose profile was deleted. Although Trading Networks still maintains a copy of the deleted profile in its database, it will not accept documents nor process documents from the partner. |
Action |
If you do not want to accept documents from the partner, you can either ignore this error or notify the partner to stop sending documents. If you want to receive and process documents from this partner, use the wm.tn.profile:undeleteProfile service to reinstate the partner's profile. |
4060 | Partner deleted |
Class | E |
Explanation |
Received a document from a partner whose profile was deleted. |
Action |
See full message for details. |
4067 | An attempt was made to send email to the {0} contact of the Unknown partner. No email was sent. |
Class | E |
Explanation |
The processing rule is configured to send an alert to a partner's contact, but Trading Networks could not identify the partner. |
Action |
Examine the document content and the Sender/Receiver queries on the document type to determine why Trading Networks could not identify the partner. |
4068 | Can''t send to UNKNOWN |
Class | E |
Explanation |
The processing rule is configured to send an alert to a partner, but Trading Networks could not identify the partner. |
Action |
Examine the document content and the Sender/Receiver queries on the document type to determine why Trading Networks could not identify the partner. |
4070 | Processing aborted |
Class | E |
Explanation |
Threw a RoutingAbortedException while processing the document. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4071 | The processing service, {0} aborted processing of this document. The message was {1}. |
Class | E |
Explanation |
Threw a RoutingAbortedException while processing the document. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4074 | The user that posted this document ({0}) could not be associated with a partner to check their identity. |
Class | E |
Explanation |
Received a document from someone other than a trading partner. |
Action |
You can either ignore this error or contact the document sender. The sender is using a valid Integration Server account, but not the account associated with their profile. |
4075 | The user that posted document {1} ({0}) could not be associated with a partner to check their identity. |
Class | E |
Explanation |
Received a document from someone other than a trading partner. |
Action |
You can either ignore this error or contact the document sender. The sender is using a valid Integration Server account, but not the account associated with their profile. |
4076 | No user ID |
Class | E |
Explanation |
Received a document from someone other than a trading partner. |
Action |
You can either ignore this error or contact the document sender. The sender is using a valid Integration Server account, but not the account associated with their profile. |
4078 | No email address |
Class | E |
Explanation |
Could not determine the address to send an email alert. |
Action |
Examine the processing rule and the receiver's profile. You must specify an address either in the processing rule or the receiver's profile. |
4079 | No email address was available for sending to {0} ({1}). No email was sent. |
Class | E |
Explanation |
Could not determine the address to send an email alert. |
Action |
Examine the processing rule and the receiver's profile. You must specify an address either in the processing rule or the receiver's profile. |
4086 | No SMTP server defined: check property watt.server.smtpServer |
Class | E |
Explanation |
The processing rule is configured to send an email alert, but no email server is defined. |
Action |
Set the SMTP Server on the Settings > Logging page of the Integration Server Administrator, or directly set the watt.server.smtpServer property. |
4087 | Cannot specify a Sender of {0} and also supply a specific senderId''s. |
Class | E |
Explanation |
When invoking wm.tn.route:create, you cannot specify that the processing rule matches 'Any' sender or the 'Unknown' sender, and also supply specific senderIDs. |
Action |
Either remove "Any", "Unknown", or the specific senderIDs. |
4089 | Cannot specify a DocType of {0} and also supply specific docTypeId''s. |
Class | E |
Explanation |
When invoking wm.tn.route:create, you cannot specify that the processing rule matches 'Any' document type or the document type is 'Unknown', and also supply specific document type IDs. |
Action |
Either remove "Any", "Unknown", or the specific document type IDs. |
4090 | An exception prevented the sender''s identity from being completely checked. The original exception was {0}. |
Class | E |
Explanation |
Threw a ProfileStoreException while checking the identity of the document sender. |
Action |
Contact Software AG Global Support. |
4094 | The sender of this document ({0}/{1}) is in status {2}. Documents from this partner are not permitted at this time. |
Class | E |
Explanation |
The document sender is not active. Inactive partners are not allowed to send documents to Trading Networks. |
Action |
You can ignore this error, activate this partner's profile, or notify the partner to stop sending documents. |
4095 | The sender of document {3} ({0}/{1}) is in status {2}. Documents from this partner are not permitted at this time. |
Class | E |
Explanation |
The document sender is not active. Inactive partners are not allowed to send documents to Trading Networks. |
Action |
You can ignore this error, activate this partner's profile, or notify the partner to stop sending documents. |
4096 | Bad status |
Class | E |
Explanation |
The document sender is not active. Inactive partners are not allowed to send documents to Trading Networks. |
Action |
You can ignore this error, activate this partner's profile, or notify the partner to stop sending documents. |
4097 | An error occurred trying to send this document via {0} (intended receiver: {1}). The original error message was: {2}. |
Class | E |
Explanation |
Encountered an exception while sending a document. See the exception message for details. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4098 | An error occurred trying to send this document via {0} (sender: {1}). The original error message was: {2}. |
Class | E |
Explanation |
Encountered an exception while sending a document. See the exception message for details. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4099 | Couldn''t send doc {0} via {1}: {2} |
Class | E |
Explanation |
Encountered an exception while sending a document. See the exception message for details. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4100 | An error occurred trying to fetch profile information for sending email to the {1} contact of partner {0}. The original error was: {2} |
Class | E |
Explanation |
Unable to retrieve the partner profile while sending an email alert. See the exception message for details. |
Action |
Contact Software AG Global Support. |
4101 | Profile error |
Class | E |
Explanation |
Unable to retrieve the partner profile while sending an email alert. See the exception message for details. |
Action |
Contact Software AG Global Support. |
4102 | Processing aborted: {0} |
Class | E |
Explanation |
Threw a RoutingAbortedException while processing the document. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4104 | {0} is not a known document attribute. |
Class | E |
Explanation |
The wm.tn.route:create service was supplied an invalid attribute name. |
Action |
Supply only names of existing document attributes. |
4107 | No preferred protocol. Status changed to POLLABLE. |
Class | E |
Explanation |
The processing rule was configured to send the document using the receiver's preferred protocol, but the receiver does not have a preferred protocol. |
Action |
Signify one of the receiver's delivery methods as the preferred protocol. |
4111 | No profile summary was available for the sender of this document |
Class | E |
Explanation |
Could not process the document because Trading Networks could not find a partner profile for the sender. |
Action |
Modify either the sender identification in the document or the external ID in the profile. |
4112 | No profile summary was available for the sender of document {2}. The sender ID was {0}, and the sender logged in as {1}. |
Class | E |
Explanation |
Could not process the document because Trading Networks could not find a partner profile for the sender. |
Action |
Modify either the sender identification in the document or the external ID in the profile. |
4113 | No profile summary available |
Class | E |
Explanation |
Could not process the document because Trading Networks could not find a partner profile for the sender. |
Action |
Modify either the sender identification in the document or the external ID in the profile. |
4114 | A supplied attribute condition has an invalid combination of datatype, operator and value ({0} {1} {2}). |
Class | E |
Explanation |
The wm.tn.route:create service was supplied an invalid attribute condition. |
Action |
Correct the attribute condition. |
4115 | An invalid value was supplied for the tn.recursion.max property. No recursion of processing rules will be allowed. |
Class | E |
Explanation |
The value of the tn.recursion.max property is not a valid number. |
Action |
Supply a valid number for this property. |
4116 | Processing recursion exceeded the allowed recursion depth of {0}. The processing rule {1} invoked itself, most recently with document {2}. Processing fails. |
Class | E |
Explanation |
One or more processing rules invoked services that resubmitted documents to Trading Networks, exceeding the recursion limit defined by the tn.recursion.max property. |
Action |
Increase the value of the tn.recursion.max property, or configure your processing rules not to resubmit documents. |
4117 | Couldn''t load routing schedule: {0} |
Class | E |
Explanation |
Encountered an exception while reading the set of processing rules from the database. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4118 | Couldn''t save routing schedule: {0} |
Class | E |
Explanation |
Encountered an exception while saving the set of processing rules to the database. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4119 | Cannot specify a Receiver of Any and also supply a specific receiverId''s. |
Class | E |
Explanation |
When invoking the wm.tn.route:create service, you cannot specify that the processing rule matches 'Any' receiver and also supply specific receivers. |
Action |
Remove either "Any" or the specific receivers. |
4120 | Cannot specify a Receiver of Unknown and also supply a specific receiverId's. |
Class | E |
Explanation |
When invoking the wm.tn.route:create service, you cannot specify that the processing rule matches an 'Unknown' receiver and also supply specific receivers. |
Action |
Remove either "Unknown" or the specific receivers. |
4121 | Cannot specify a DocType of Any and also supply specific docTypeIds. |
Class | E |
Explanation |
When invoking the wm.tn.route:create service, you cannot specify that the processing rule matches 'Any' TN document type and also supply specific TN document types. |
Action |
Remove either "Any" or the specific TN document types. |
4122 | Cannot specify a DocType of Unknown and also supply specific docTypeIds. |
Class | E |
Explanation |
When invoking the wm.tn.route:create service, you cannot specify that the processing rule matches the 'Unknown' TN document type and also supply specific TN document types. |
Action |
Remove either "Unknown" or the specific TN document types. |
4123 | If deliverUsing is "Queue for delivery", then deliveryQueue cannot be null |
Class | E |
Explanation |
An invalid combination of input values was sent to the wm.tn.route:create service. |
Action |
Supply a value for the "deliveryQueue" variable. |
4125 | Cannot queue a bizdoc for deliver that has not been persisted. This bizdoc (id={0}) has not been persisted. |
Class | E |
Explanation |
The scheduled delivery mechanism requires that the document be saved to the database. |
Action |
Change the TN document type or processing rule to save documents of this type. |
4130 | qname is required |
Class | E |
Explanation |
Attempted to enqueue a delivery job without supplying a queue name for the "qname" parameter. |
Action |
Supply a valid queue name for the "qname" parameter. |
4131 | Invalid queue name ({0}). |
Class | E |
Explanation |
Attempted to enqueue a delivery job without supplying a queue name for the "qname" parameter. |
Action |
Supply a valid queue name for the "qname" parameter. |
4132 | Receiver does not have a delivery queue. |
Class | E |
Explanation |
The processing rule is configured to send the document to the receiver's private delivery queue, but the receiver does not have a delivery queue. |
Action |
Change the processing rule to deliver the document by a different means, or create a delivery queue for the receiver. |
4133 | Receiver does not have a delivery queue. Document has been made POLLABLE (document id={0}) |
Class | E |
Explanation |
The processing rule is configured to send the document to the receiver's private delivery queue, but the receiver's profile does not contain a definition for a delivery queue. |
Action |
Change the processing rule to deliver the document by a different means, or update the receiver's profile to specify a delivery queue. |
4134 | Receiver does not have a preferred protocol. Document has been made POLLABLE. (document id={0}) |
Class | E |
Explanation |
The processing rule is configured to send the document by the receiver's preferred delivery method, but the receiver does not have a preferred delivery method. |
Action |
Change the processing rule to deliver the document by a different means, or signify one of the delivery methods on the receiver's profile as "preferred". |
4135 | Error encountered in RoutingActions.invoke(): can not clone input pipeline. |
Class | E |
Explanation |
An internal error occurred while invoking a service to process the document. |
Action |
Contact Software AG Global Support. |
4136 | Unable to save document: {0}. |
Class | E |
Explanation |
Encountered an exception while saving the document to the database. |
Action |
Take appropriate action to resolve the problem described in the exception. |
4138 | The processing rule list has been modified by another user. Added this rule to the bottom of the list. Refresh your rule list. |
Class | E |
Explanation |
The rule list displayed on your Trading Networks Console is not the current list that resides in the database. As a result, the newly added rule is appended to the end of the rule list rather than the specific position required in the list. |
Action |
Refresh your routing rule list and move the newly added rule to the desired position. |
4139 | Error encountered while inserting processing rule {0}. The exception message is : {1}. |
Class | S |
Explanation |
Encountered an exception while inserting a processing rule. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4140 | Error encountered while updating processing rule {0}. The rule index cannot be changed during an update operation. |
Class | E |
Explanation |
You attempted to update both the contents of a processing rule and its location within the list of processing rules (its index) at the same time. You cannot make both these changes at the same time. |
Action |
Please update the rule first, and then move the rule to a new position in the rule list. |
4141 | Error encountered while updating processing rule {0}. The exception message is : {1}. |
Class | E |
Explanation |
Encountered an exception while updating a processing rule. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4142 | Processing rule update failed. Processing rule update collision detected. This rule has been modified by another user. Refresh your rule list and retry this operation. |
Class | E |
Explanation |
While you were updating this processing rule, another user edited and saved the same processing rule. To prevent your changes from overwriting those made by the other user, Trading Networks did not save your changes. |
Action |
Refresh the list of processing rules and update the processing rule again. |
4145 | Error encountered while deleting processing rule(s). The exception message is : {0}. |
Class | S |
Explanation |
Encountered an exception while deleting processing rule(s). |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4146 | Processing rule delete operation aborted. The processing rule list has been modified by another user. Refresh your rule list and retry this operation. |
Class | E |
Explanation |
While you were deleting this processing rule, another user edited and saved the rule. So that your changes do not overwrite those made by the other user, your changes have not been saved. |
Action |
Refresh your rule list, and then delete the rule again. |
4147 | Processing rule {0} does not exist. |
Class | E |
Explanation |
The specified routing rule cannot be retrieved because the rule ID does not exist in the database. |
Action |
Check that the rule ID is correct, modify it if necessary, and then attempt to retrieve it again. |
4148 | Error encountered while reading processing rules from the database. The exception message is : {0}. |
Class | S |
Explanation |
Encountered an exception while retrieving processing rules from the database. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4149 | Error encountered while moving processing rules. The exception message is : {0}. |
Class | S |
Explanation |
Encountered an exception while moving processing rules in the rule list. |
Action |
See the exception message for details. Take appropriate action to resolve the problem described in the exception. |
4150 | Processing rule move operation aborted. The processing rule list has been modified by another user. Refresh your rule list and retry this operation. |
Class | E |
Explanation |
While you were moving this processing rule, another user edited and saved the rule list. So that your changes do not overwrite those made by the other user, your changes have not been saved. |
Action |
Refresh the rule list, and then move the rule again. |
4151 | Illegal move operation. The insertAt position cannot be within the range of rules to be moved. |
Class | E |
Explanation |
The insertAt position must be outside the range of rules to be moved. |
Action |
Change the insertAt position to be outside of the range of rules to be moved. |
4152 | Illegal move operation. You cannot move a non-contiguous set of rules. |
Class | E |
Explanation |
You attempted to change the order of processing rules by moving a non-contiguous set of rules. Trading Networks does not support this type of operation. |
Action |
Define a contiguous set of rules to be moved. |
4156 | Encountered an error retrieving the Profile Summary for partner ID {0}. |
Class | E |
Explanation |
An error occurred attempting to look up the Profile Summary. |
Action |
Ensure that the partner IDs on the document being processed are valid. |
4157 | Encountered an error while sending MAPI event to Optimize for EventMap {0} and for Sender with PartnerID {1}. |
Class | E |
Explanation |
In webMethods Trading Networks, while routing a document, if a TN BAM monitoring event cannot be logged in Optimize, this error is thrown. |
Action |
Contact your system administrator. |
4160 | The content-length ({0}) specified in handleLargeDoc is less than the length of the content ({1}) sent. |
Class | E |
Explanation |
In webMethods Trading Networks, in a document transaction, while handling large documents, if the content length specified in the handleLargeDoc is less than the length of the BizDoc content, this error is thrown. |
Action |
Ensure that the content length specified in the handleLargeDoc is equal to the length of the BizDoc content and try again. |
4162 | Routing Aborted as the Receiver is disabled. |
Class | E |
Explanation |
In webMethods Trading Networks, while routing a document, if the receiver is in an inactive state, this error is thrown. |
Action |
Ensure to set the receiver to active state and try again. |
4163 | Routing Aborted as the Receiver is deleted. |
Class | E |
Explanation |
In webMethods Trading Networks, while routing a document, if the receiver is in deleted state, this error is thrown. |
Action |
Ensure to set the receiver profile is not deleted and try again. |
4164 | Routing Aborted as the Sender is disabled. |
Class | E |
Explanation |
In webMethods Trading Networks, while routing a document, if the sender is in inactive state, this error is thrown. |
Action |
Ensure to set the sender to active state and try again. |
4165 | Routing Aborted as the Sender is deleted. |
Class | E |
Explanation |
In webMethods Trading Networks, while routing a document, if the sender is deleted, this error is thrown. |
Action |
Ensure to set the sender profile is not deleted and try again. |
4166 | The processing service aborted processing of this document. The message was {0}. |
Class | E |
Explanation |
In webMethods Trading Networks, while routing a document, if an error occurs in processing the document, this error is thrown. |
Action |
Contact your system administrator. |
4167 | Posting of BAM events failed because of following errors - {0}. |
Class | E |
Explanation |
In webMethods Trading Networks, if any error occurs while posting BAM events, this error is thrown. |
Action |
Contact your system administrator. |
5002 | Delivery service for {0} failed with a status of {1} and status message of {2} |
Class | E |
Explanation |
Unable to deliver the document, possibly due to a problem with the network or the destination server. |
Action |
Verify that your server has network connectivity. If a problem exists with the destination server, contact the person responsible for that server. |
5004 | Unable to get output for task {0} - Task has not finished. Status is {1} |
Class | E |
Explanation |
The task was still executing when the request for output expired. |
Action |
Request the output again. |
5005 | Unable to refresh {0} cache on server {1} - {2} |
Class | E |
Explanation |
A cache could not be refreshed, probably due to a database problem. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. Verify that your database is successfully processing requests. |
5007 | Unable to remove task {0} - Does not exist |
Class | E |
Explanation |
An invalid task ID was supplied. |
Action |
Supply a valid task ID. |
5011 | Disabling reliable task manager at {0} - Fatal error: {1} |
Class | S |
Explanation |
Encountered an exception that requires the task manager to shut down. |
Action |
Take appropriate action to resolve the problem described in the exception. |
5013 | Unable to restart task {0} upon initialization |
Class | W |
Explanation |
The task status could not be updated to "Pending" in the database. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. Verify that your database is successfully processing requests. |
5015 | Unable to persist task {0} |
Class | E |
Explanation |
Encountered an exception while saving the task to the database. |
Action |
See the full message (TRNSERV.000015.000089) for details. |
5019 | Task {0} unable to move to server {1} - {2} |
Class | E |
Explanation |
Task has already completed. Status is "Done". |
Action |
No action required. |
5020 | Unable to refresh {0} cache - {1} |
Class | E |
Explanation |
See the exception message for details. |
Action |
Take appropriate action to resolve the problem described in the exception. |
5025 | Task {0} failed, status changed to {1} |
Class | E |
Explanation |
The task has failed. No more retries. |
Action |
See full message (TRNSERV.000015.000036) for details. |
5026 | Unable to init task manager for server {0} - {1} |
Class | E |
Explanation |
The task manager could not be initialized, probably due to a database problem. |
Action |
Use the Integration Server Administrator JDBC Pools page to check that the Integration Server can connect to the database. Verify that your database is successfully processing requests. |
5031 | Error invoking service {0} - message: {1} - stacktrace: {2} |
Class | E |
Explanation |
The task manager invoked a service to process a document, and that service threw an exception. |
Action |
See the exception message for details. Correct the invoked service to handle the exception condition. |
5036 | Task {0} failed with no more retries available. Reason for failure - {1} |
Class | E |
Explanation |
See the status message for details. |
Action |
If the failure is due to an error on another server, contact the person responsible for that server. |
5037 | Unable to restart task {0} - {1} |
Class | E |
Explanation |
The task status is neither "Failed" nor "Stopped", so the task cannot be restarted. |
Action |
No action necessary. |
5039 | Unable to shut down the task manager. |
Class | E |
Explanation |
The wm.tn.task:shutdown service was unable to stop the task manager. See the nested exception for details. |
Action |
Take appropriate action to resolve the problem described in the nested exception. |
5042 | Unable to initialize task manager. |
Class | E |
Explanation |
The wm.tn.task:init service was unable to start the task manager. See the nested exception for details. |
Action |
Take appropriate action to resolve the problem described in the nested exception. |
5043 | Unable to reset task manager. |
Class | E |
Explanation |
The wm.tn.task:restart service was unable to restart the task manager. See the nested exception for details. |
Action |
Take appropriate action to resolve the problem described in the nested exception. |
5044 | Unable to retrieve tasks. |
Class | E |
Explanation |
The wm.tn.task:getTasks service was unable to get tasks from the task manager. See the nested exception for details. |
Action |
Take appropriate action to resolve the problem described in the nested exception. |
5045 | Unable to retrieve task {0}. |
Class | E |
Explanation |
The wm.tn.task:getTask service was unable to get a task from the task manager. See the nested exception for details. |
Action |
Take appropriate action to resolve the problem described in the nested exception. |
5046 | Unable to get output for task {0}. |
Class | E |
Explanation |
The wm.tn.task:getTaskOutput service was unable to get output for a task. See the nested exception for details. |
Action |
Take appropriate action to resolve the problem described in the nested exception. |
5047 | Unable to get status for task {0}. |
Class | E |
Explanation |
The wm.tn.task:getTaskStatus service was unable to get the status of a task. See the nested exception for details. |
Action |
Take appropriate action to resolve the problem described in the nested exception. |
5048 | Unable to change server for task {0}. |
Class | E |
Explanation |
The wm.tn.task:changeServerForTask service was unable to move a task from one server to another. See the nested exception for details. |
Action |
Take appropriate action to resolve the problem described in the nested exception. |
5049 | Unable to remove task {0}. |
Class | E |
Explanation |
The wm.tn.task:removeTask service was unable to remove a task from the task manager. See the nested exception for details. |
Action |
Take appropriate action to resolve the problem described in the nested exception. |
5050 | Unable to restart task {0}. |
Class | E |
Explanation |
The wm.tn.task:restartTask service was unable to restart a task in the task manager. See the nested exception for details. |
Action |
Take appropriate action to resolve the problem described in the nested exception. |
5051 | Unable to stop task {0}. |
Class | E |
Explanation |
The wm.tn.task:stopTask service was unable to stop a task in the task manager. See the nested exception for details. |
Action |
Take appropriate action to resolve the problem described in the nested exception. |
5052 | Unable to move task {0} to server {1}. Task does not exist. |
Class | E |
Explanation |
An invalid task ID was supplied. |
Action |
Supply a valid task ID. |
5053 | Unable to move task {0} to server {1}. Task has completed. |
Class | E |
Explanation |
Task status is "Done". Cannot move a completed task. |
Action |
No action necessary. |
5054 | Unable to move task {0} to server {1}. Could not ''ping'' server: {2} |
Class | E |
Explanation |
Invoked the wm.server:ping service on the other server, and it threw an exception. |
Action |
Take appropriate action to resolve the problem on the other server as described in the exception. |
5055 | Unable to move task {0} to server {1}. Server {2} is up, but the task has not failed. |
Class | E |
Explanation |
The server that created this task is running. Therefore, the task cannot be moved because the task status is neither "Failed" nor "Stopped". |
Action |
No action necessary. |
5056 | Unable to move task {0} to server {1}. Server {2} is down, but the task is done. |
Class | E |
Explanation |
Task status is "Done". Cannot move a completed task. |
Action |
No action necessary. |
5057 | Unable to stop task {0}. Job has completed. |
Class | E |
Explanation |
Cannot stop a completed task. |
Action |
No action necessary. |
5058 | Unable to stop task {0}. Job does not exist. |
Class | E |
Explanation |
An invalid task ID was supplied. |
Action |
Supply a valid task ID. |
5060 | Delivery Job Manager error: task {0} is not NEW. |
Class | E |
Explanation |
Cannot start a task that does not have a "New" status. |
Action |
No action necessary. Task has already started. |
5061 | Delivery Job Manager error with task {0}. {1} |
Class | E |
Explanation |
Encountered an exception while writing to the database. See the exception message for details. |
Action |
Take appropriate action to resolve the problem described in the exception. |
5062 | Task {0} unable to restart. Does not exist. |
Class | E |
Explanation |
An invalid task ID was supplied. |
Action |
Supply a valid task ID. |
5064 | Unable to remove task {0}. {1} |
Class | E |
Explanation |
Encountered an exception while writing to the database. See the exception message for details. |
Action |
Take appropriate action to resolve the problem described in the exception. |
5065 | Cannot get job output. Job does not exist. |
Class | E |
Explanation |
An invalid task ID was supplied. |
Action |
Supply a valid task ID. |
5066 | Unable to initialize task manager. ServerId is null. |
Class | E |
Explanation |
Unable to determine server ID. |
Action |
Supply a value for the watt.net.localhost property in the server.cnf file on the Integration Server. |
5068 | Unable to delete tasks. There are {0} active jobs in the list of jobs to be deleted. Stop the active jobs and retry |
Class | E |
Explanation |
Cannot delete active tasks. |
Action |
If you want to delete tasks that are active, stop them first. |
5069 | Unable to get task |
Class | E |
Explanation |
The wm.tn.route:getTask service can only retrieve tasks that are service execution tasks. A taskID of a delivery task was supplied. |
Action |
Request only service execution tasks from the wm.tn.route:getTask service. |
5070 | Error getting task |
Class | E |
Explanation |
The wm.tn.route:getTask service encountered an exception while retrieving a task. See the nested exception for details. |
Action |
Take appropriate action to resolve the problem described in the nested exception. |
5072 | Unable to restart queued task (id={0}). Its delivery queue no longer exists. You can resubmit the document to process it again. |
Class | E |
Explanation |
The delivery queue for this document has been deleted. Cannot be requeued. |
Action |
Verify that the processing rule that handles this document is configured to use a valid delivery queue. Resubmit the document. |
5081 | Error invoking service, {0} - Service did not return valid output |
Class | E |
Explanation |
The task manager invoked a service to process a document. The output of the service did not conform to the expected format. |
Action |
If this is a delivery service, make sure the output matches the wm.tn.rec:DeliveryServiceOutput IS document type. If this is a service invoked by a service execution task, make sure the output matches the wm.tn.rec:reliableServiceOutput IS document type. |
5082 | ERROR: Unable to update task {0} due to database error : {1}. Since task update retry is turned off, manual correction is required. Please correct the database errors and manually update the task using the additional task details provided. Additional Details of this task : Task ID={2}; DocID={3}; TaskStatus={4}; Retries={5}; TransportStatus={6}; TransportStatusMessage={7}; TransportTime={8} |
Class | E |
Explanation |
Could not update the task. See exception message for details. |
Action |
Manually update the task in My webMethods using the details provided in the message. |
5089 | ERROR: Unable to update task {0} due to IOException : {1}. Task update will continue to fail until this exception is rectified. Until this error is rectified, manual correction is required. Manually update the task using the additional task details provided. Additional Details of this task : Task ID={2}; DocID={3}; TaskStatus={4}; Retries={5}; TransportStatus={6}; TransportStatusMessage={7}; TransportTime={8} |
Class | E |
Explanation |
Could not update the task. See exception message for details. |
Action |
Manually update the task in My webMethods using the details provided in the message. |
5091 | TN Job Manager sweep time property tn.task.sweepTime contains ({0}), which is not a numeric value. Using the default value 300 seconds |
Class | S |
Explanation |
The tn.task.sweepTime property contains an invalid value. |
Action |
Supply a valid numeric value. |
5094 | Task {0} failed at {1}: Probable reason for failure - {2}. {3} more retries left. |
Class | E |
Explanation |
In webMethods Trading Networks, if any error occurs while disabling the delivery for a partner, this error is thrown. |
Action |
Contact your system administrator. |
1001 | Cannot setIData for CertificateData because the supplied data is null. |
Class | E |
Explanation |
The setIData method on a CertificateData object passed a null IData object. |
Action |
If your code is calling CertificateData.setIData, supply an IData object that is not null. If it is not your code that is calling this method, contact Software AG Global Support. . |
1002 | Cannot setIData for CertificateData. |
Class | E |
Explanation |
The setIData method on a CertificateData object was not successful. |
Action |
If Integration Server logging is set to logging level 4 or higher, the exception was written to the server log. See the server log for more information. Take the appropriate action to resolve the problem described in the exception. |
1003 | Certificate provider Entrust/IAIK was not found, so Trading Networks cannot convert byte[] to java.security.cert.X509Certificate. Please ensure that entrust jar files are in the Integration Server''s classpath. |
Class | S |
Explanation |
The Entrust jar files are missing from the Integration Server's classpath. |
Action |
Place the Entrust jar files in the Integration Server's classpath. If you need assistance, contact Software AG Global support. |
1004 | CertificateException encountered; Trading Networks cannot convert byte[] to java.security.cert.X509Certificat. |
Class | E |
Explanation |
Trading Networks encountered a certificateException when attempting to convert a byte array to a java.security.cert.X509Certificat. |
Action |
If Integration Server logging is configured at logging level 4 or higher, the exception was written to the server log. See the server log for details. Take the appropriate action to resolve the problem described in the exception. |
1005 | Cannot convert byte[][] to X509Certificate[], exception encountered at index {0}. |
Class | E |
Explanation |
Trading Networks could not create a certificate chain from the bytes. Trading Networks encountered the error at <zeroBasedIndexNum> certificate. |
Action |
Check the byte array to ensure that it is in the correct format. |
1006 | Cannot convert byte[] to java.security.PrivateKey. |
Class | E |
Explanation |
Trading Networks could not create a private key object from bytes. |
Action |
Check the byte array to ensure that it is in the correct format. |
1007 | Cannot convert X509Certificate[] to byte[][], CertificateEncodingException encountered at index {0}. Please verify that the certificate is valid. |
Class | E |
Explanation |
The certificate chain is not valid. |
Action |
Provide a valid certificate chain. |
1008 | Cannot convert PKCS7 formatted byte[] into .der formatted byte[][]. |
Class | E |
Explanation |
The PKCS7-formatted bytes are not valid. |
Action |
Check the byte array to ensure that it is in the correct format. Provide a valid byte array. |
1009 | Cannot load certificate from null File. Please supply a valid File. |
Class | E |
Explanation |
The supplied certificate file is null. |
Action |
Supply a certificate file that is not null. |
1010 | Certificate provider Entrust/IAIK not found, so Trading Networks cannot load java.security.cert.X509Certificate from file <filename>. Ensure that entrust jar files are in the Integration Server''s classpath. |
Class | S |
Explanation |
The Entrust jar files are missing from the Integration Server's classpath. |
Action |
Place the Entrust jar files in the Integration Server's classpath. If you need assistance, contact Software AG Global Support. |
1011 | CertificateException encountered getting certificate from file {0}. |
Class | E |
Explanation |
An error occurred while attempting to load certificates from the specified file. |
Action |
Check the certificate file to ensure that it is in the correct format. |
1012 | Cannot load private key from null File. |
Class | E |
Explanation |
Trading Networks attempted to load the private key from a file; however, the file is null. |
Action |
Supply a private key file that is not null. |
1013 | IOException encountered loading RSA private key from file {0}. |
Class | E |
Explanation |
An error occurred while the server attempted to load a private key from the specified file. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem described in the exception. |
1014 | InvalidKeyException encountered loading RSA private key from file {0}. |
Class | E |
Explanation |
An error occurred while the server attempted to load a private key from the specified file. |
Action |
Check the private key file to ensure that it is in the correct format. |
1015 | Cannot determine whether the certificate is self-signed because the certificate byte[] is null. |
Class | E |
Explanation |
The supplied certificate byte array is null. |
Action |
Supply a non-null certificate byte array. |
1016 | Cannot determine whether the certificate is self-signed because both the subject and issuer are null. |
Class | E |
Explanation |
The supplied certificate is not in a valid format. Both the subject and issuer are null. |
Action |
Supply a valid certificate. |
1017 | Cannot determine whether the certificate is self-signed because the certificate is null. |
Class | E |
Explanation |
The supplied certificate is null. |
Action |
Supply a non-null certificate. |
1018 | Integration Server''s certificate file {0} not found. |
Class | E |
Explanation |
Trading Networks could not find the specified file that contains the Integration Server's client certificate. |
Action |
Specify a file that contains a client certificate for the Integration Server. |
1019 | Integration Server''s CA certificate file {0} not found. |
Class | E |
Explanation |
Trading Networks could not find the specified file that contains the Integration Server's CA certificate. |
Action |
Specify a file that contains the Integration Server's CA certificate. |
1020 | IOException encountered when retrieving the Integration Server''s private key from {0}. |
Class | E |
Explanation |
IOException thrown when Trading Networks was attempting to retrieve the Integration Server's private key from the specified file. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem described in the exception. |
1021 | InvalidKeyException encountered when retrieving the Integration Server''s private key from {0}. |
Class | E |
Explanation |
An error occurred when Trading Networks was attempting to retrieve the Integration Server's private key from the specified file. |
Action |
Specify a file that contains a valid private key for the Integration Server. |
1022 | Certificate chain bytes cannot be null or zero length. |
Class | E |
Explanation |
The certificate chainBytes parameter is either null or has a length of zero. |
Action |
Supply a valid certificate chain. |
1023 | Certificate chain contains a single certificate, and that certificate is not self-signed. |
Class | E |
Explanation |
The certificate chain is not valid. The certificate chain contains only one certificate, and that certificate is not self-signed. When you are not using a self-signed certificate, a certificate chain must include a certificate and its corresponding CA certificate(s). |
Action |
Supply a valid certificate chain. That is a single self-signed certificate or a certificate and its corresponding CA certificates. |
1024 | Entrust cannot verify the certificate chain: {0} |
Class | E |
Explanation |
Entrust could not verify the certificate chain. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take appropriate action to resolve the problem. |
1027 | Cannot determine whether to trust the sign/verify certificate because there is no Enterprise profile. |
Class | E |
Explanation |
Trading Networks cannot determine whether to trust the sign/verify certificate because there is no Enterprise profile. |
Action |
Create an Enterprise profile. For information about creating profiles, see the Trading Networks documentation. |
1028 | Cannot set sign/verify certificate for receiver, Enterprise, because a CertificateException was encountered when determining whether the Integration Server trusts the certificate chain. |
Class | E |
Explanation |
Before setting the sign/verify certificates that are specified in the Enterprise profile, Trading Networks ensures that the Integration Server trusts the certificates. A CertificateException was thrown when determining whether the Integration Server trusts the certificates. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take appropriate action to resolve the problem. |
1029 | Cannot set sign/verify certificate for receiver, Enterprise, because the Integration Server is not set up to trust the certificate specified in the Enterprise profile. |
Class | W |
Explanation |
Before setting the sign/verify certificate that is specified in the Enterprise profile, Trading Networks ensures that the Integration Server trusts the certificate. The certificate supplied in the Enterprise profile is not among the certificates that the Integration Server trusts. |
Action |
Add this certificate to the Integration Server's directory of trusted certificates. |
1031 | SQLException encountered when setting certificate data for partner {0}; error message is {1}. |
Class | E |
Explanation |
An error occurred when Trading Networks attempted to set the certificate data for the partner with the specified partner ID. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take appropriate action to resolve the problem described in the exception. |
1032 | SQLException encountered when retrieving certificate data for partner {0}; error message is {1}. |
Class | E |
Explanation |
An error occurred when Trading Networks attempted to retrieve the certificate data for the partner with the specified partner ID. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem described in the exception. |
1035 | Cannot setIData() for CertData: CertData is null. |
Class | E |
Explanation |
The setIData method on a CertData object passed a null IData object. |
Action |
If your code is calling CertData.setIData, supply a non-null IData object. If it is not your code that is calling this method, contact Software AG Global Support. |
1036 | EXMLException encountered in CertData.setIData(). |
Class | E |
Explanation |
com.wm.app.tn.err.EXMLException was thrown in the setIData() method. |
Action |
If your code is calling CertData.setIData, check the server log for a stack trace. Take the appropriate action to resolve the problem described in the exception. If it is not your code that is calling this method, contact Software AG Global Support. |
1037 | Cannot get expiration date for node certificate. |
Class | E |
Explanation |
The certificate does not have expiration date information. |
Action |
Ensure that the certificate is in a valid format. |
1038 | Cannot convert byte array to java.lang.PrivateKey. |
Class | E |
Explanation |
Trading Networks could not convert the byte array because it is corrupted. |
Action |
Ensure that the byte array in the private key file is in a valid format. |
1039 | Cannot set illegal usage {0} for CertData. |
Class | E |
Explanation |
The CertData object contains a certificate usage parameter that is not legal. |
Action |
Ensure the certificate usage parameter in the CertData object has one of the following values: "sign", "decrypt", or "ssl". |
1040 | Cannot insert CertData into database, CertData is null. |
Class | E |
Explanation |
The CertData object is null. |
Action |
Supply a non-null CertData object. |
1041 | Cannot insert CertData into database because data already exists for supplied owner={0}, partner={1} and usage={2}. |
Class | E |
Explanation |
You attempted to add certificate information for the specified owner/partner/usage combination. However, there is already certificate information for this owner/partner/usage combination in the Trading Networks database. |
Action |
If you want to update the certificate information for the specified owner/partner/usage combination, use the update operation instead of insert operation. Otherwise, specify a unique owner/partner/usage combination that does not already exist in the Trading Networks database. |
1042 | Error inserting CertData into the database; update row count is not 1. |
Class | E |
Explanation |
Trading Networks encountered a database error when performing the insert operation. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1043 | Error inserting CertData into the database; IOException encountered encoding data into binary format. |
Class | E |
Explanation |
Trading Networks encountered an error when performing the insert operation; an IOException was thrown when encoding data into binary format. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1044 | Error inserting CertData into the database; SQLException encountered with the error message {0}. |
Class | E |
Explanation |
An SQLException occurred while Trading Networks was attempting to perform a database insert operation. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1045 | Cannot update CertData because the supplied CertData object is null. |
Class | E |
Explanation |
Trading Networks was attempting to perform a database update operation to update certificate information. However, the supplied CertData object that Trading Networks is to use to update the existing certificate information is null. As a result, Trading Networks cannot perform the database update operation. |
Action |
Supply a non-null CertData object. |
1046 | Cannot update CertData because the supplied CertID is null. |
Class | E |
Explanation |
Trading Networks is not able to update the certificate information because the supplied unique identifier, CertID, is null. |
Action |
Supply a non-null CertID. |
1047 | Cannot update CertData because the specified CertID, {0} does not match the CertID that Trading Networks has for the supplied owner/partner/usage. |
Class | E |
Explanation |
You attempted to update certificate information for the specified owner/partner/usage combination. However, the supplied CertID does not match CertID that Trading Networks has for this owner/partner/usage combination. |
Action |
Retrieve the correct CertID for the owner/partner/usage combination from database, and issue the request again. This time specify the correct CertID for the owner/partner/usage combination. |
1048 | Error updating CertData; the update count from the update operation is not 1. |
Class | E |
Explanation |
Trading Networks encountered a database error when performing the update operation. |
Action |
If the Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1049 | Error updating CertData in the database; IOException encountered encoding data into binary format. |
Class | E |
Explanation |
Trading Networks encountered an error when performing the update operation; an IOException was thrown when encoding data into binary format. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1050 | Error updating CertData in the database; SQLException encountered with the error message {0}. |
Class | E |
Explanation |
An SQLException occurred when Trading Networks was attempting to perform a database update operation. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1051 | Cannot delete CertData because the supplied CertID is null. |
Class | E |
Explanation |
Trading Networks is not able to delete the certificate information because the supplied unique identifier, CertID, is null. |
Action |
Supply a non-null CertID. |
1052 | Error deleting CertData; the delete count from the delete operation is not 1. |
Class | E |
Explanation |
Trading Networks encountered a database error when performing the delete operation. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1053 | Error deleting CertData from the database; SQLException encountered with the error message {0}. |
Class | E |
Explanation |
An SQLException was thrown when Trading Networks was attempting to perform a database delete operation. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1054 | Cannot construct new CertData from SecurityOps.getCertificateData(). |
Class | E |
Explanation |
Internal error |
Action |
Contact Software AG Global Support. |
1055 | Error selecting CertData for ownerId={0}, partnerId={1}, usage={2}; IOException encountered decoding bytes to IData. |
Class | E |
Explanation |
When Trading Networks was attempting to select CertData for the owner/partner/usage combination, an IOException was thrown when decoding bytes to IData. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1056 | Error selecting CertData for ownerId={0}, partnerId={1}, usage={2}; SQLException encountered with the error message {3}. |
Class | E |
Explanation |
An SQLException occurred while Trading Networks was attempting select CertData for the owner/partner/usage combination. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1057 | Cannot construct new CertData from SecurityOps.getCertificateDataByCertID(). |
Class | E |
Explanation |
Internal error |
Action |
Contact Software AG Global Support. |
1058 | Error selecting CertData for CertId=<certID>; IOException encountered decoding bytes to IData. |
Class | E |
Explanation |
When Trading Networks was attempting to select CertData with the specified CertID, an IOException was thrown when decoding bytes to IData. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1059 | Error selecting CertData for CertId={0}; SQLException encountered with the error message {1}. |
Class | E |
Explanation |
An SQLException occurred while Trading Networks was attempting select CertData with the specified CertID. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1060 | Cannot construct new CertData from SecurityOps.getCertificateDataForOwner(). |
Class | E |
Explanation |
Internal error |
Action |
Contact Software AG Global Support. |
1061 | Error selecting CertData for ownerId={0}; IOException encountered decoding bytes to IData. |
Class | E |
Explanation |
When Trading Networks was attempting to select CertData for the specified owner, an IOException was thrown while decoding bytes to IData. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1062 | Error selecting CertData for ownerId={0}; SQLException encountered with the error message {1}. |
Class | E |
Explanation |
An SQLException occurred while Trading Networks was attempting to select CertData for the specified owner. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1063 | Cannot search certificate data because the expiration date is null. |
Class | E |
Explanation |
The certificate expiration date search criterion is null. |
Action |
Supply a valid certificate expiration date for this search criterion. |
1064 | Cannot construct new CertData from SecurityOps.getCertificateDataForUpdate(). |
Class | E |
Explanation |
Internal error |
Action |
Contact Software AG Global Support. |
1065 | Error selecting CertData for ownerId={0} and expDate={1}; IOException encountered decoding bytes to IData. |
Class | E |
Explanation |
While Trading Networks was attempting to select CertData for the specified owner and with the specified expiration date, an IOException was thrown when decoding bytes to IData. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1066 | Error selecting CertData for ownerId={0} and expDate={1}; SQLException encountered with the error message {2}. |
Class | E |
Explanation |
An SQLException occurred while Trading Networks was attempting to select CertData for the specified owner and with the specified expiration date. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1067 | Cannot construct new CertData from SecurityOps.getCertificateDataForPartnerAndUsage(). |
Class | E |
Explanation |
Internal error |
Action |
Contact Software AG Global Support. |
1068 | Error selecting CertData for partnerId={0} with usage={1}; IOException encountered decoding bytes to IData. |
Class | E |
Explanation |
While Trading Networks was attempting to select CertData for the specified partner and with the specified certificate usage, an IOException was thrown when decoding bytes to IData. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1069 | Error selecting CertData for partnerId={0} with usage={1}; SQLException encountered with the error message {2}. |
Class | E |
Explanation |
An SQLException occurred while Trading Networks was attempting to select CertData for the specified partner and with the specified certificate usage. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1070 | Cannot get profile store or profile summary list, so Trading Networks cannot migrate certificates. |
Class | E |
Explanation |
An exception was thrown while retrieving profile data. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1071 | Cannot get partner''s ({0}) profile data; skip migrating this partner''s certificate set. |
Class | W |
Explanation |
Trading Networks was not able to find profile data for the partner with the specified partner ID. As a result, Trading Networks cannot migrate this partners certificate set. |
Action |
Contact Software AG Global Support. |
1074 | Error loading partner''s ({0}) certificate; skip migrating this partner''s certificate set. |
Class | E |
Explanation |
An exception occurred while loading certificate data for the partner with the specified partner ID. As a result, Trading Networks cannot migrate this partner's certificate set. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1075 | Cannot migrate partner''s ({0}) certificate set because the certificate is null. |
Class | E |
Explanation |
While Trading Networks was attempting to migrate the specified partner's certificate set, it encountered a null certificate. As a result, Trading Networks cannot migrate the certificate set. |
Action |
Supply a valid, non-null certificate. |
1077 | Error loading partner''s ({0}) CACertificate; skip migrating this partner''s certificate set. |
Class | E |
Explanation |
An exception was thrown while loading certificate data for the partner with the specified partner ID. As a result, Trading Networks cannot migrate this partner's certificate set. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1078 | Cannot migrate partner''s ({0}) certificate set because a CA certificate is null. |
Class | E |
Explanation |
While Trading Networks was attempting to migrate the specified partner's certificate set, it encountered a null CA certificate. As a result, Trading Networks cannot migrate the certificate set. |
Action |
Supply a valid CA certificate. |
1079 | Error loading partner''s ({0}) private key; skip migrating this partner''s certificate set. |
Class | E |
Explanation |
An exception occurred while loading the private key for the partner with the specified partner ID. As a result, Trading Networks cannot migrate this partner's certificate set. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1080 | Cannot migrate partner''s ({0}) certificate set because the private key is null. |
Class | E |
Explanation |
The private key is null. When Trading Networks was attempting to migrate the specified partner's certificate set, it encountered a null private key. As a result, Trading Networks cannot migrate the certificate set. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1081 | Error adding partner''s verify certificate to Trading Networks database (partner ID={0}, Integration Server user account={1}); skip migrating this partner''s verify certificate set. |
Class | E |
Explanation |
An exception was thrown while attempting to add the verify certificate to the database. As a result, Trading Networks cannot migrate this partner's verify certificate set. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1082 | Found null node certificate for CertId={0} in migration. |
Class | E |
Explanation |
Trading Networks cannot migrate the certificate with the specified CertID because the node certificate is null. |
Action |
Supply a valid certificate. |
1083 | IOException encountered in migration, CertID={0}. |
Class | E |
Explanation |
IOException thrown when Trading Networks attempted to migrate the certificate with the specified CertID. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1084 | Error duplicating sign certitificate data to SSL certificate data for owner={0}, partner={1}. |
Class | E |
Explanation |
Internal error |
Action |
Contact Software AG Global Support. |
1085 | Cannot migrate certificate information. Cannot get current Trading Networks version from database. |
Class | E |
Explanation |
Trading Networks cannot migrate certificate information because it cannot determine the Trading Networks version. The database information is not up-to-date or the database is not running. |
Action |
Ensure that the Trading Networks database is running. Use the JDBC Pools page on the Integration Server Administrator to ensure that the Integration Server can connect to the Trading Networks database. |
1087 | fromVersion is required to run wm.tn.admin.migrate:migrateCerts. |
Class | E |
Explanation |
The required fromVersion parameter was not supplied. |
Action |
Supply a valid fromVersion. |
1092 | SQLException encountered in wm.tn.admin.migrate:migrateCerts. |
Class | E |
Explanation |
An SQLException thrown was when executing the wm.tn.admin.migrate:migrateCerts service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1093 | Error encountered in wm.tn.admin.migrate:migrateCerts. |
Class | E |
Explanation |
Internal error. |
Action |
Contact Software AG Global Support. |
1094 | Error encountered invoking service {0}. |
Class | E |
Explanation |
An error occurred when invoking the specified service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1098 | Cannot get certificate for verification of sender={0}, receiver={1}. |
Class | E |
Explanation |
The certificates used to verify the Sender-Receiver partner pair are not available. |
Action |
Specify the certificates that you want to use for the partners in the Trading Networks profiles. |
1099 | Cannot get certificate for verification of sender={0}, receiver={1}, stack trace is {2}. |
Class | E |
Explanation |
Trading Networks could not retrieve the verify certificate for the specified sender and receiver. |
Action |
Ensure the verify certificate information is provided for specified sender and receiver. |
1101 | No chain for signer {0} ({1}). |
Class | I |
Explanation |
Required security data is missing. |
Action |
If your application code is creating or updating certificates, ensure that you supply all required certificate data to the services you are invoking. If you receive this error while using the Trading Networks Console, contact Software AG Global Support. |
1102 | Cannot find verification cert. |
Class | E |
Explanation |
Trading Networks could not retrieve a verify certificate. |
Action |
Contact Software AG Global Support. |
1103 | Cannot find verification cert for sender={0}, receiver={1}. |
Class | E |
Explanation |
Trading Networks could not retrieve the verify certificate for the specified sender and receiver. |
Action |
Ensure the verify certificate information is provided for specified sender and receiver. |
1104 | Error encountered verifying XML document. |
Class | E |
Explanation |
An error was thrown when verifying an XML document. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1109 | Error encountered signing XML document. |
Class | E |
Explanation |
An error was thrown while signing an XML document. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1110 | Signing certificate for sender={0} receiver={1} not valid. |
Class | E |
Explanation |
The signing certificate for the specified sender and receiver is not valid. |
Action |
Provide a valid signing certificate for the sender/receiver pair. |
1111 | Verify certificate for sender={0} receiver={1} not valid. |
Class | E |
Explanation |
The verify certificate for the specified sender and receiver is not valid. |
Action |
Provide a valid verify certificate for the sender/receiver pair. |
1115 | Error encountered invoking wm.tn.security:getDecryptCACertificates. |
Class | E |
Explanation |
An error was encountered while invoking the wm.tn.security:getDecryptCACertificates service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1116 | Error encountered invoking wm.tn.security:getDecryptCertificate. |
Class | E |
Explanation |
An error was encountered while invoking the wm.tn.security:getDecryptCertificate service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1117 | Error encountered invoking wm.tn.security:getDecryptKey. |
Class | E |
Explanation |
An error was encountered while invoking the wm.tn.security:getDecryptKey service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1118 | Error encountered invoking wm.tn.security:getEncryptCACertificates. |
Class | E |
Explanation |
An error was encountered while invoking the wm.tn.security:getEncryptCACertificates service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1119 | Error encountered invoking wm.tn.security:getEncryptCertificate. |
Class | E |
Explanation |
An error was encountered while invoking the wm.tn.security:getEncryptCertificate service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1120 | Error encountered invoking wm.tn.security:getEncryptKey. |
Class | E |
Explanation |
An error was encountered while invoking the wm.tn.security:getEncryptKey service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1121 | Error encountered invoking wm.tn.security:getSecurity. |
Class | E |
Explanation |
An error was encountered while invoking the wm.tn.security:getSecurity service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1122 | Error encountered invoking wm.tn.security:getSignCACertificates. |
Class | E |
Explanation |
An error was encountered while invoking the wm.tn.security:getSignCACertificates service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1123 | Error encountered invoking wm.tn.security:getSignCertificate. |
Class | E |
Explanation |
An error was encountered while invoking the wm.tn.security:getSignCertificate service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1124 | Error encountered invoking wm.tn.security:getSignKey. |
Class | E |
Explanation |
An error was encountered while invoking the wm.tn.security:getSignKey service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1125 | Error encountered invoking wm.tn.security:getVerifyCACertificates. |
Class | E |
Explanation |
An error was encountered while invoking the wm.tn.security:getVerifyCACertificates service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1126 | Error encountered invoking wm.tn.security:getVerifyCertificate. |
Class | E |
Explanation |
An error was encountered while invoking the wm.tn.security:getVerifyCertificate service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1132 | Error encountered invoking wm.tn.security:setDecryptCertificateSet. |
Class | E |
Explanation |
An error was encountered while invoking the wm.tn.security:setDecryptCertificateSet service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1133 | cert is null; however, CACerts is not null. |
Class | E |
Explanation |
You provided information in CACerts to specify CA certificates; however, you did not specify a certificate for the cert variable. |
Action |
Provide a valid certificate for the cert variable. |
1134 | CACerts is required when the certificate is not self-signed. |
Class | E |
Explanation |
You did not specify CA certificates for the CACerts variable. CA certificates are required unless the certificate you specify is self-signed. |
Action |
Provide valid CA certificates for the CACerts variable. |
1137 | Error encountered invoking wm.tn.security:setEncryptCertificateSet. |
Class | E |
Explanation |
An error was encountered while invoking the wm.tn.security:setEncryptCertificateSet service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1151 | Error encountered invoking wm.tn.security:setSecurity. |
Class | E |
Explanation |
An error was encountered while invoking the wm.tn.security:setSecurity service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1152 | privateKey and cert should be both null or neither null. |
Class | E |
Explanation |
You specified a value for either privateKey or cert, but not for both. The values for privateKey and cert must either both be null or both have non-null values. |
Action |
Provide valid values for privateKey and cert. |
1153 | CACerts is required for non self signed certificates. |
Class | W |
Explanation |
A value for CACerts must be specified for non self-signed certificates. |
Action |
Provide valid value for CACerts. |
1156 | Error encountered invoking wm.tn.security:setSignCertificateSet. |
Class | E |
Explanation |
An error was encountered while invoking the wm.tn.security:setSignCertificateSet service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1159 | Error encountered invoking wm.tn.security:setVerifyCertificateSet. |
Class | E |
Explanation |
An error was encountered while invoking the wm.tn.security:setVerifyCertificateSet service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1164 | Error encountered invoking wm.tn.security:updateCertificate. |
Class | E |
Explanation |
An error was encountered while invoking the wm.tn.security:updateCertificate service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1165 | Error encountered in wm.tn.security:addCertificateData. |
Class | E |
Explanation |
An error was encountered while executing the wm.tn.security:addCertificateData service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1166 | Cannot get existing Certificate Data from supplied certID={0}. |
Class | E |
Explanation |
Cannot get existing certificate data for the certificate information with certID=<certID>. The supplied certID might be invalid. |
Action |
Ensure that the value for certID is valid. |
1167 | Cannot get existing CertID from supplied ownerID={0} partnerID={1} and usage={2}. |
Class | E |
Explanation |
Cannot get existing CertID for certificate data that is associated with ownerID=<ownerID> partnerID=<partnerID> and usage=<certificateUage>. |
Action |
Ensure that the values for ownerID, partnerID, and usage are valid. |
1168 | Cannot construct new CertData in wm.tn.security:updateCertificateData. |
Class | E |
Explanation |
Internal error. |
Action |
Contact Software AG Global Support. |
1169 | Error encountered in wm.tn.security:updateCertificateData. |
Class | E |
Explanation |
An error was encountered while executing the wm.tn.security:updateCertificateData service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1170 | Cannot delete non-existing CertData for ownerID={0}, partnerID={1} and usage={2}. |
Class | E |
Explanation |
Trading Networks could not locate certificate data for the specified ownerID, partnerID, or usage. |
Action |
Ensure the values for ownerID, partnerID, and usage are valid. |
1171 | Error encountered in wm.tn.security:deleteCertificateData. |
Class | E |
Explanation |
An error was encountered while executing the wm.tn.security:deleteCertificateData service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1172 | Error encountered in wm.tn.security:getCertificateData. |
Class | E |
Explanation |
An error was encountered while executing the wm.tn.security:getCertificateData service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1175 | Error encountered in wm.tn.security:getSigningKeyAndChain. |
Class | E |
Explanation |
An error was encountered while executing the wm.tn.security:getSigningKeyAndChain service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1176 | Error encountered in wm.tn.security:getVerifyingChain. |
Class | E |
Explanation |
An error was encountered while executing the wm.tn.security:getVerifyingChain service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1178 | Error encountered in wm.tn.security:getDecryptionKeyAndCert. |
Class | E |
Explanation |
An error was encountered while executing the wm.tn.security:getDecryptionKeyAndCert service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1179 | Error encountered in wm.tn.security:getEncryptionChain. |
Class | E |
Explanation |
An error was encountered while executing the wm.tn.security:getEncryptionChain service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1182 | {0} private key not defined. |
Class | E |
Explanation |
The private key for the SSL client certificate set was not defined. |
Action |
Provide a valid SSL private key for the SSL client certificate set. |
1183 | {0} certificate chain not defined. |
Class | E |
Explanation |
The certificate chain for the SSL client certificate set was not defined. |
Action |
Provide a valid SSL certificate chain for the SSL client certificate set. |
1184 | Error encountered in wm.tn.security:getSSLKeyAndChain. |
Class | E |
Explanation |
Error encountered when executing the wm.tn.security:getSSLKeyAndChain service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1185 | No SSL key and cert defined. |
Class | E |
Explanation |
The SSL private key and certificate are not defined. |
Action |
Provide a valid SSL private key and certificates. |
1187 | Error encountered in wm.tn.security:setSSLKeyAndChain. |
Class | E |
Explanation |
An error was encountered while executing the wm.tn.security:setSSLKeyAndChain service. |
Action |
If Integration Server logging is configured at logging level 4 or higher, a stack trace was written to the server log. See the server log for details. Take the appropriate action to resolve the problem. |
1190 | Certificate chain bytes cannot be null or zero length. |
Class | E |
Explanation |
The certificate chainBytes value is either null or a zero length. The certificate chain must contain data. |
Action |
Provide valid certificate chain byte array. |
1191 | Invalid RSA Private Key file. |
Class | E |
Explanation |
The RSA private key file is not valid. |
Action |
Provide a valid RSA private key file. |
1192 | Cannot construct new CertData. |
Class | E |
Explanation |
Internal Error. |
Action |
Contact Software AG Global Support. |
1193 | Bad private key for usage {0}: {1} |
Class | E |
Explanation |
The private key that was provide is not valid. |
Action |
Provide a valid private key. |
1194 | Unable to import security data for owner {0} because the owner is not defined in your Trading Networks system. |
Class | |
Explanation |
In webMethods Trading Networks, it is not possible to import the security data for the owner as the owner is not defined. |
Action |
Define the owner in webMethods Trading Networks and try again. |
1196 | Unable to import security data of owner {0} for partner {1} because the partner {1} is not defined in your Trading Networks system. |
Class | |
Explanation |
In webMethods Trading Networks, if the partner is not defined as the owner of the certificate, the security data cannot be imported. |
Action |
Ensure that the partner is the owner of the certificate and try again. |
1198 | Error encountered while viewing certificate data for partnerID={0}. The error is {1} |
Class | |
Explanation |
In webMethods Trading Networks, an error is encountered while viewing certicate data for the partner. |
Action |
Contact your system administrator. |
1199 | Error encountered in wm.tn.security:updateCertificateData for partnerID={0}. The error is {1} |
Class | |
Explanation |
In webMethods Trading Networks, an error is encounterred while updating a certificate. |
Action |
Contact your system administrator. |
1200 | Error encountered while validating chain The error is {0} |
Class | |
Explanation |
In webMethods Trading Networks, an error is encountered when the certificate details that are entered is not correct. |
Action |
Ensure to define the certificate details correctly and try again. |
1201 | Unable to import security data for partner {0} because this partner is not defined in your Trading Networks system. |
Class | |
Explanation |
webMethods Trading Networks is unable to import security data for the partner because this partner is not defined in your webMethods Trading Networks system. |
Action |
Define the partner in your webMethods Trading Networks system and try again. |
1001 | {0} is required. |
Class | E |
Explanation |
A value was not supplied for the specified variable. |
Action |
Supply the required value. |
1002 | wm.tnweb.wrapper:xmlEncode: could not encode IData to binary |
Class | E |
Explanation |
An exception was thrown while encoding an IData. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1003 | wm.tnweb.wrapper:xmlDecode: could not decode binary to IData |
Class | E |
Explanation |
An exception was thrown while decoding an IData. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1004 | wm.tnweb.wrapper:xmlDecode2: could not decode binary to Values |
Class | E |
Explanation |
An exception was thrown while decoding an IData. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1005 | wm.tnweb.wrapper:removeNullAlerts: error caught in removing null alerts |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1006 | wm.tnweb.wrapper:compareRights: error caught in comparing rights |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1007 | wm.tnweb.wrapper:getTNRights: error caught in getting Trading Networks partner ACL privilege |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1008 | wm.tnweb.wrapper:getUserGroups: error caught in getting Trading Networks partner ACL group memberships |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1009 | wm.tnweb.wrapper:getUserInfo: error caught in getting Trading Networks partner IS login name |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1010 | wm.tnweb.wrapper:getHashKeys: error caught in getting Hashtable keys |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1011 | {0} cannot be null |
Class | E |
Explanation |
A value was not supplied for the specified variable. |
Action |
Supply the required value. |
1012 | wm.tnweb.wrapper:IntegerToStrng: error caught converting Integer datatype to String datatype |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1013 | wm.tnweb.wrapper:ShortToStrng: error caught converting Short datatype to String datatype |
Class | E |
Explanation |
Trading Networks encountered an internal error |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1014 | wm.tnweb.wrapper:isBIEnabled: error caught in retrieving enabled Integration Server packages |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1015 | wm.tnweb.wrapper:isBIEnabled: could not find if Business Integrator (ProcessMonitor) package is installed and enabled |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1016 | wm.tnweb.wrapper:getStringFromBundle: could not get String from resource bundle wm.tnweb.wrapper_bundle for key = {0} |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1017 | wm.tnweb.querySvc:getQuery: could not get pre-saved query ({0}) for partnerID={1}. |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1018 | {0} cannot be null or empty |
Class | E |
Explanation |
A value was not supplied for the specified variable. |
Action |
Supply the required value. |
1019 | partnerID is null or empty in invoking wm.tnweb.querySvc:getSavedQueries |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1020 | wm.tnweb.querySvc:getSavedQueries: could not get pre-saved queries for partnerID={0} |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1021 | wm.tnweb.querySvc:getDocuments: could not get documents |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1022 | wm.tnweb.querySvc:createTaskQuery: could not create task query for document id={0} |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1023 | wm.tnweb.querySvc:getCalendar: invalid input {0} |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1024 | wm.tnweb.querySvc:getCalendar: could not get calender for year={0}, month={1} |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1025 | wm.tnweb.querySvc:getQueryRestriction: could not get document query restriction for document id = {0} |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1026 | Could not get profile store |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1027 | Could not get document attributes for id = {0} |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1028 | Could not get internal document type id for name = {0} |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1029 | wm.tnweb.configSvc:checkDefaultConfigLoaded: could not check if default config is loaded |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1030 | wm.tnweb.configSvc:getHashes: could not construct Hashtables for TNAdministrators and TNPartners |
Class | E |
Explanation |
Internal error Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1035 | wm.tnweb.configSvc:getUserConfig: could not get membership info for user {0}. |
Class | E |
Explanation |
The user account for the specified user does not exist in the Integration Server. |
Action |
If you have deleted the user account for this user, use the Integration Server Administrator to create the user account again. If this is for an external user, ensure that the user account is a member of the TNPartners group. |
1039 | wm.tnweb.configSvc:getUserConfig: could not get partner specific config for {0} |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1040 | wm.tnweb.configSvc:getGroupConfig: could not get group specific config for {0} |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1041 | wm.tnweb.configSvc:getTNPartners: could not get partner information |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1042 | wm.tnweb.configSvc:getTNGroups: could not get IS group information |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1043 | wm.tnweb.configSvc:getTNUsers: could not get Trading Networks IS user information |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1044 | wm.tnweb.configSvc:getUserConfigDisplay: could not get specific user config information |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1045 | wm.tnweb.configSvc:getAvailableStatus: could not get user status from database |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1047 | wm.tnweb.configSvc:saveCustomPages: error encountered in saving new custom pages setting |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1048 | wm.tnweb.configSvc:addToHashes: invalid type value |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1049 | wm.tnweb.configSvc:addToHashes: could not add new config IData to hashtable |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1050 | wm.tnweb.configSvc:changeConfig: could not change config setting |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1051 | wm.tnweb.querySvc:getQueryRestriction: do not have privilege to check query restriction |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1053 | wm.tnweb.wrapper:logBrowserLocale: error encountered in getting browser locale |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1054 | cert is null |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1055 | CACerts is null |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1056 | CACerts[{0}] is null |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1057 | privateKey is null |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1058 | Can not get user specific configuration: no such user {0} |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1059 | Error encountered calling wm.tnweb.configSvc:checkAndUpdateConfig |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1061 | Error updating/retrieving configuration info from repo |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1062 | Error encountered in invoking service wm.tnweb.querySvc:getPartnerNameAndID |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1063 | Can not get valid profile summary list: list is null or empty |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1064 | Error encountered in invoking service wm.tnweb.querySvc:runTaskQuery |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1065 | Error encountered in invoking service wm.tnweb.querySvc:taskQueryById |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1066 | Error encountered in invoking service wm.tnweb.querySvc:getDocDetails |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1067 | Got null bizdoc, docId = {0} |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1068 | Got null or 0-length bizdoc content parts, docId = {0} |
Class | E |
Explanation |
The contents of this document might not have been saved to the Trading Networks database. |
Action |
Check the corresponding TN document type and processing rule to determine whether Trading Networks has saved the document contents to the database. |
1069 | Invalid startIndex = {0} |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1070 | Can not convert content bytes to String: unsupported encoding |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1071 | NOTE: No privilege to view contents of this document |
Class | E |
Explanation |
You attempted to view a document of which you are neither the sender nor the receiver. |
Action |
You can only view a document that you have sent or received. |
1072 | NOTE: No more data to display |
Class | E |
Explanation |
Either the document has no content or the startIndex is beyond the end of the content. |
Action |
If you determine that this is an error, gather error information and contact webMethods Customer Care. |
1073 | Got null bizdoc content part, docId={0}, content part name={2} |
Class | E |
Explanation |
The content of this document might not have been saved to the Trading Networks database. |
Action |
Check the corresponding TN document type and processing rule to determine whether Trading Networks saved the document content to the database. |
1074 | Error encountered in invoking service wm.tnweb.wrapper:getTNInfo |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1075 | Error encountered in invoking service wm.tnweb.wrapper:registerTNOnIntegrationServer |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1076 | Error encountered parsing date {0} or {1}. |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
1077 | Error encountered in invoking service wm.tnweb.wrapper:installTNWebACLs |
Class | E |
Explanation |
Trading Networks encountered an internal error. |
Action |
Gather error information from the logs and contact Software AG Global Support. |
TRNSERV.000018.000001 | new String[]{"{0} is required","Please supply the required value","0"} |
Explanation |
A value for the specified input field is not supplied. |
Action |
Supply a valid value for the specified input field. |
TRNSERV.000018.000018 | new String[]{"{0} cannot be null or empty","","0"} |
Explanation |
The specified input field does not contain a value. A value for this input field is required. |
Action |
Supply a valid value for the specified input field. |
TRNSERV.000018.000025 | new String[]{"wm.tnweb.querySvc:getQueryRestriction: could not get document query restriction for document id = {0}","","0"} |
Explanation |
An error occurred while fetching a document query restriction for specified document. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
TRNSERV.000018.000051 | new String[]{"wm.tnweb.querySvc:getQueryRestriction: do not have privilege to check query restriction","","0"} |
Explanation |
You are not allowed to check the query restriction. |
Action |
Contact your administrator. |
TRNSERV.000018.000066 | new String[]{"Error encountered in invoking service wm.tnweb.querySvc:getDocDetails","","0"} |
Explanation |
An error occurred while retrieving content part bytes. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
TRNSERV.000018.000067 | new String[]{"Got null bizdoc, docId = {0}","","0"} |
Explanation |
While checking the query restriction, a null bizdoc was found for the specified docID. |
Action |
Supply a valid docId. |
TRNSERV.000024.000204 | new String[]{"Error attempting to parse message contents","","0"} |
Explanation |
A MessagingException error occurred while parsing the MIME message. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
TRNSERV.000024.000205 | new String[]{"Error attempting to read from message source","","0"} |
Explanation |
An IOException error occurred while reading a MIME message from the message source. |
Action |
The exception was written to the log. Take appropriate action to resolve the problem described in the exception. |
bizDocDeletionError | You did not select an item to delete. Select at least one item to delete. |
Explanation |
You did not select an item to delete. |
Action |
Select at least one item to delete. |
bizDocSelectionError | You did not select an item to archive. Select at least one item to archive. |
Explanation |
You did not select an item to archive. |
Action |
Select at least one item to archive. |
cert.err | An error occurred while validating the certificate chain. Take corrective action based on the error details. |
Explanation |
An error occurred while validating the certificate chain. |
Action |
Take corrective action based on the error details. |
corp.name.required | You did not supply a value for the required Corporation Name field. Provide a value for this field. |
Explanation |
You did not supply a value for the required Corporation Name field. |
Action |
Provide a value for this field. |
date.is.required | You did not specify a date. Specify a date to proceed. |
Explanation |
You did not specify a date. |
Action |
Specify a date to proceed. |
default.connection.error.msg | Trading Networks Server is not configured, or it is not available. |
Explanation |
Trading Networks server is not configured, or it is not available. |
Action |
Contact the Administrator. |
dlscheck.dialogMessage | You do not have permission to perform this action. Contact your system administrator for the required privileges. |
Explanation |
You do not have permission to perform this action. |
Action |
Contact your system administrator for the required privileges. |
docTypeDetails_NameRequiredError | The document type name is a required field. Provide a document type name. |
Explanation |
The document type name is required. |
Action |
Provide a document type name. |
docTypeSearch.fileInput.required.msg | No document was provided for testing. Provide the document. |
Explanation |
No document was provided for testing. |
Action |
Provide the document. |
doctype.instantiation.error | The EDI document type could not be instantiated. Make sure that a valid schema standard is specified. |
Explanation |
The EDI document type could not be instantiated. |
Action |
Make sure that a valid schema standard is specified. |
editor.detailsid.missing.error | Document Type ID is missing. |
Explanation |
In webMethods Trading Networks, if the Document Type ID is missing, this error shows up. |
Action |
Ensure to log out and log in again to webMethods Trading Networks. |
empty.attribute.name.error | The Name field cannot be blank. Provide a valid value for this field. |
Explanation |
The Name field cannot be blank. |
Action |
Provide a valid value for this field. |
error.InvalidDefaultValue | You specified a default value of %1$s. This value is not valid. Select a value from the list of valid values. |
Explanation |
The specified default value is not valid. |
Action |
Select a value from the list of valid values. |
error.InvalidFieldId | Invalid Field Id Specified: %1$s |
Explanation |
In webMethods Trading Networks, if the Field Definition ID of the profile is null or invalid, this error shows up. |
Action |
Contact your system administrator. |
error.InvalidFieldLength | You specified a field length of %1$s. This field length is not valid. Specify a positive integer value. |
Explanation |
The specified field length is not valid. |
Action |
Specify a positive integer value. |
error.WmEDIPackageNotEnabled | The WmEDI package is not enabled on the Integration Server. Enable the package. |
Explanation |
The WmEDI package is not enabled on the Integration Server. |
Action |
Enable the package. |
error.days.greaterthan.zero | Specify a value greater than zero for Days field. |
Explanation |
You entered a value for Days that is not valid. |
Action |
Enter an integer value greater than zero. |
error.defValue.exceeds.maxLength | Default Value %1$s exceeds specified Maximum Length %2$s |
Explanation |
In webMethods Trading Networks, if the default value of a field definition exceeds the maximum length permissible, this error throws up. |
Action |
Enter a field definition with default value within the permissible maximum length, and try again. |
error.delete | The activity log(s) could not be deleted. Take corrective action based on the error details. |
Explanation |
The activity log(s) could not be deleted. |
Action |
Take corrective action based on the error details. |
error.enter.valid.file.name | Enter a valid file name |
Explanation |
The file name is empty or contains invalid characters such as ", /, \, *, or ?. |
Action |
Specify a valid file name. |
error.enter.valid.solution.name | Enter a valid solution name |
Explanation |
The solution name is empty or contains invalid characters such as ", /, \, *, or ?. |
Action |
Specify a valid solution name. |
error.extract.file | The file you uploaded is not in a valid format. Provide an XML or a binary file containing valid asset data to import. |
Explanation |
The file you uploaded is not in a valid format. |
Action |
Provide an XML or a binary file containing valid asset data to import. |
error.getComment | An error occurred while retrieving comments from Trading Networks. Take corrective action based on the error details and trace. |
Explanation |
An error occurred while retrieving comments from Trading Networks. |
Action |
Take corrective action based on the error details and trace. |
error.getEDIINTProperties | My webMethods encountered an error while trying to retrieve WmEDIforTN package properties. Take corrective action based on the error details. |
Explanation |
My webMethods Server encountered an error while trying to retrieve WmEDIforTN package properties. |
Action |
Take corrective action based on the error details. |
error.getEDIProperties | My webMethods Server encountered an error while trying to retrieve WmEDI package properties. Take corrective action based on the error details. |
Explanation |
My webMethods Server encountered an error while trying to retrieve WmEDI package properties. |
Action |
Take corrective action based on the error details. |
error.getTNProperties | My webMethods Server encountered an error while trying to retrieve Trading Networks properties. Make sure the WmTN package is properly installed and loaded. |
Explanation |
My webMethods Server encountered an error while trying to retrieve Trading Networks properties. |
Action |
Make sure the WmTN package is properly installed and loaded. |
error.message | Download action failed. |
Explanation |
An exception occurred while downloading the file. |
Action |
Check the server connection. Contact the system administrator to check your security and locale settings. |
error.message.edi.not.installed | This feature requires the WmEDI and WmEDIforTN packages. These packages are either not loaded or are disabled. Enable these packages. |
Explanation |
This feature requires the WmEDI and WmEDIforTN packages. |
Action |
These packages are either not loaded or are disabled. Enable these packages. |
error.name.already.exists | The name you have chosen for this field, %1$s, already exists. Enter a different name. |
Explanation |
The name you have chosen for this field already exists. |
Action |
Enter a different name. |
error.noserver | My WebMethods Server could not reassign the task(s) because no target was specified. Specify the target server. |
Explanation |
My webMethods Server could not reassign the task(s) because no target was specified. |
Action |
Specify the target server. |
error.reassign | My WebMethods Server encountered an error while reassigning the task(s). Take corrective action based on the error details. |
Explanation |
My webMethods Server encountered an error while reassigning the task(s). |
Action |
Take corrective action based on the error details. |
error.restart | My WebMethods Server encountered an error while restarting the task(s). Take corrective action based on the error details. |
Explanation |
My webMethods Server encountered an error while restarting the task(s). |
Action |
Take corrective action based on the error details. |
error.saveEDIFormatSettings | My webMethods encountered an error while trying to update EDI Module format settings. Take corrective action based on the error details. |
Explanation |
My webMethods Server encountered an error while trying to update EDI Module format settings. |
Action |
Take corrective action based on the error details. |
error.saveEDIINTProperties | My webMethods encountered an error while trying to update EDI Module configuration properties. Take corrective action based on the error details. |
Explanation |
My webMethods Server encountered an error while trying to update EDI Module configuration properties. |
Action |
Take corrective action based on the error details. |
error.saveEDIProperties | My webMethods encountered an error while trying to save EDI Module configuration properties. Take corrective action based on the error details. |
Explanation |
My webMethods Server encountered an error while trying to save EDI Module configuration properties. |
Action |
Take corrective action based on the error details. |
error.saveTNProperties | My webMethods Server encountered an error while trying to save Trading Networks properties. Make sure the WmTN package is properly installed and loaded. |
Explanation |
My webMethods Server encountered an error while trying to save Trading Networks properties. |
Action |
Make sure the WmTN package is properly installed and loaded. |
error.setComment | An error occurred while setting comments from Trading Networks. Take corrective action based on the error details and trace. |
Explanation |
An error occurred while setting comments from Trading Networks. |
Action |
Take corrective action based on the error details and trace. |
error.stop | My WebMethods Server encountered an error while stopping the task(s). Take corrective action based on the error details. |
Explanation |
My webMethods Server encountered an error while stopping the task(s). |
Action |
Take corrective action based on the error details. |
error.submitDocument | An error occurred while submitting the document to Trading Networks. Check the file path and resubmit the document. |
Explanation |
An error occurred while submitting the document to Trading Networks. |
Action |
Check the file path and resubmit the document. |
file.validation.message | Invalid file format. Supported format: csv |
Class | E |
Explanation |
The file uploaded is not a valid file format. |
Action |
Upload .csv files. |
g11n.wm_tn_bam_attributes.default.optimize_not_installed | Optimize is not installed. Install webMethods Optimize. |
Explanation |
Optimize is not installed. |
Action |
Install webMethods Optimize. |
g11n.wm_tn_bam_doctypes.default.optimize_not_installed | Optimize is not installed. Install webMethods Optimize. |
Explanation |
Optimize is not installed. |
Action |
Install webMethods Optimize. |
g11n.wm_tn_dls_viewDataSet.default.at_least_one_permission | Permissions have not yet been granted to this role. Grant at least one permission to this role on the Permissions tab. |
Explanation |
Permissions have not yet been granted to this role. |
Action |
On the Permissions tab, grant at least one permission to this role. |
g11n.wm_tn_pf_profile.users.invalid_user_name | You did not specify a user name. Provide a valid user name. |
Explanation |
You did not specify a user name. |
Action |
Provide a valid user name. |
g11n.wm_tn_pf_profile.users.no_password | The password is missing. Provide and confirm the password. |
Explanation |
The password is missing. |
Action |
Provide and confirm the password. |
g11n.wm_tn_pf_profile.users.passwords_do_not_match | The values for Password and Confirm Password do not match. Enter the same values for these fields. |
Explanation |
The values for Password and Confirm Password do not match. |
Action |
Enter the same values for these fields. |
g11n.wm_tn_pf_profile.users.user_already_exists_please | The specified user name already exists. Provide a unique user name. |
Explanation |
The specified user name already exists. |
Action |
Provide a unique user name. |
g11n.wm_tn_pf_profile.users.user_name_invalid | The user name provided is not valid because it contains special characters.Specify a user name that contains only alphanumeric characters. |
Explanation |
The user name provided is not valid because it contains special characters. |
Action |
Specify a user name that contains only alphanumeric characters. |
id.generate.error | Can not generate EDI document type ID. Try again. |
Explanation |
Cannot generate EDI document type ID. |
Action |
Try again. |
invalid.file | Invalid file format. Supported formats: xml,txt |
Class | E |
Explanation |
The file uploaded is not a valid file format. |
Action |
Upload .xml or .txt files. |
invalid.integer.value.detail | The value you provided for the Control Number Minimum is not an integer. For the VDA standard, enter an integer value greater than or equal to 0. For other standards, enter an integer value greater than or equal to 1. |
Explanation |
The value you provided for the Control Number Minimum is not an integer. |
Action |
For the VDA standard, enter an integer value greater than or equal to 0. For other standards, enter an integer value greater than or equal to 1. |
invalid.message.minimum.value | The value you provided for the Control Number Minimum is not valid. For the VDA standard, enter a value greater than or equal to 0. For other standards, enter a value greater than or equal to 1. |
Explanation |
The value you provided for the Control Number Minimum is not valid. |
Action |
For the VDA standard, enter a value greater than or equal to 0. For other standards, enter a value greater than or equal to 1. |
invalid.role | You cannot add or remove privileges for Trading Networks or My webMethods administrators. Contact your system administrator. |
Explanation |
You cannot add or remove privileges for Trading Networks or My webMethods administrators. |
Action |
Contact your system administrator. |
invalid.value.inputcontrol | The value you provided for the Control Number Minimum is not valid. Enter an integer value. For the VDA standard, enter a value greater than or equal to 0. For other standards, enter a value greater than or equal to 1. |
Explanation |
The value you provided for the Control Number Minimum is not valid. Enter an integer value. |
Action |
For the VDA standard, enter a value greater than or equal to 0. For other standards, enter a value greater than or equal to 1. |
label.error.maxrowsexceeded | Number of records to fetch exceeds the maximum limit. |
Class | E |
Explanation |
Error occurred while trying to access Trading Networks dashboard because the number of records to fetch from the dashboard table (TransactionSummaryData table) exceeds the maximum limit. |
Action |
Contact your system administrator to either purge records or specify a larger value for the tn.chart.fetchMaxRows property. |
missing.required.extended | The required extended field {1} of group {0} is missing. Provide a value for this extended field. |
Explanation |
The required extended field is missing. |
Action |
Provide a value for this field. |
msg.badDateRange | The start date is later than the end date. Correct the start date so that it occurs before the end date. |
Explanation |
The start date is later than the end date. |
Action |
Correct the start date so that it occurs before the end date. |
msg.badDynamicData | You submitted dynamic query criteria that are incomplete. Provide all expected elements for the dynamic query. |
Explanation |
The dynamic query criteria are incomplete. |
Action |
Provide all expected elements for the dynamic query. |
msg.errSave | The content viewer page size is empty or is not valid. Enter an integer value greater than zero. |
Explanation |
The content viewer page size is empty or is not valid. |
Action |
Enter an integer value greater than zero. |
msg.maxReprocessDocuments | You cannot reprocess more than {0} documents. To change this limit, contact your system administrator. |
Explanation |
Reprocessing limit exceeded. |
Action |
To change this limit, contact your system administrator. |
msg.maxResubmitDocuments | You cannot resubmit more than {0} documents. To change this limit, contact your system administrator. |
Explanation |
Resubmission limit exceeded. |
Action |
To change this limit, contact your system administrator. |
name.is.required | You did not specify a queue name. Specify a queue name to proceed. |
Explanation |
You did not specify a queue name. |
Action |
Specify a queue name to proceed. |
no.data.set | My webMethods was unable to find the dataset for the specified ID. Log in to My webMethods again. |
Explanation |
Unable to find the dataset for the specified ID. |
Action |
Log in to My webMethods again. |
no.return.url | My webMethods could not navigate to the specified page because of a caching issue. Log in to My webMethods again. |
Explanation |
My webMethods could not navigate to the specified page because of a caching issue. |
Action |
Log in to My webMethods again. |
no.root.vailable.error | The sample document used for creating the XML document type does not contain a Root tag. Provide a properly formatted document that contains a Root tag. |
Explanation |
The sample document used for creating XML document type does not contain a Root tag. |
Action |
Provide a properly formatted document that contains a Root tag. |
not.valid.document | You uploaded a sample document that is not valid. Provide a sample document with a valid root node. |
Explanation |
You uploaded a sample document that is not valid. |
Action |
Provide a sample document with a valid root node. |
optionsTab.check.duplicate.doc.error.msg | You selected the "Check for Duplicate Document" option but did not specify a duplication service. Select a service. |
Explanation |
You selected the "Check for Duplicate Document" option but did not specify a duplication service. |
Action |
Select a service. |
partnerid.missing.message | The partner ID is missing. Click here to go to the Partner Profiles page, and then specify a valid partner ID. |
Explanation |
The partner ID is missing. |
Action |
Click here to go to the Partner Profiles page, and then specify a valid partner ID. |
problem.AccessException | You do not have permission to perform the requested action. Check with your system administrator. |
Explanation |
You do not have permission to perform the requested action. |
Action |
Request that your system administrator assign you the permission. |
problem.ConnectException | My webMethods Server could not connect to the Trading Networks Server because that server is not available. Make sure the server is running on the specified host and port ''{0}''. |
Explanation |
The specified Trading Networks server is not available. |
Action |
Make sure the server is running on the specified host and port. |
problem.UnknownHostException | My webMethods Server could not connect to the Trading Networks Server named ''{0}'' because that server is either not available or its host name is not recognized. Start the Trading Networks Server or specify a different server to connect to. |
Explanation |
The specified Trading Networks server is not available. |
Action |
Verify the host name of the Trading Networks Server. |
problem.noSelection | You did not select any items to act on. Select one or more items and retry the action. |
Explanation |
You did not select any items to act on. |
Action |
Select one or more items and then retry the action. |
proc.rules.detailsno.server.error | Trading Networks Server is not configured, or it is not available. |
Explanation |
The configured Trading Networks instance may be down, or the system administrator may not have granted you permission to access the Trading Networks Server. |
Action |
Make sure the server is running. If it is, contact the system administrator for permission to access the server. |
procrule.details.name.invalid.error | Invalid Processing rule name. Special characters are not allowed. |
Class | E |
Explanation |
Processing rule name cannot have special characters. |
Action |
Provide a valid name for the processing rule. |
profile.externalid.required | You did not specify an external ID for this profile. Provide the external ID. |
Explanation |
You did not specify an external ID for this profile. |
Action |
Provide an external ID. |
query.not.found.error | You uploaded a sample document that does not contain a valid root node. Provide a sample document with a valid root node. |
Explanation |
You uploaded a sample document that does not contain a valid root node. |
Action |
Provide a sample document with a valid root node. |
query.not.match | Your query does not match any of the nodes present in the sample document. Resubmit the query with a valid node. |
Explanation |
Your query does not match any of the nodes present in the sample document. |
Action |
Resubmit the query with a valid node. |
role.is.required | Permissions have not yet been granted to any roles. Grant permission(s) to at least one role on the Permissions tab. |
Explanation |
Permissions have not yet been granted to any roles. |
Action |
On the Permissions tab, grant permission(s) to at least one role. |
rule.name.is.required | The dataset could not be created or updated because no dataset name was specified. Provide the dataset name. |
Explanation |
Dataset name not specified while creating or updating the dataset. |
Action |
Enter the dataset name. |
std.version.trans.not.sel.error | You did not specify a standard, version, or transaction while creating the EDI document type. Select a standard, version, and transaction. |
Explanation |
You did not specify a standard, version, or transaction while creating the EDI document type. |
Action |
Select a standard, version, and transaction. |
text.futuredate.validation | Date selected cannot be in the future. |
Class | E |
Explanation |
Error occurred while trying to retrive records from the TransactionSummaryData table because the date selected was a future date. |
Action |
Select an appropriate date to view data. |
text.response.nodata | No records found for the selected date. |
Class | I |
tpa.details.agreementID.required.error | Agreement ID cannot be empty. |
Explanation |
Agreement ID is empty. |
Action |
Provide an Agreement ID. |
tpa.details.controlnumber.notInteger | Control Number must be an integer. Provide an integer value. |
Explanation |
Control Number must be an integer. |
Action |
Provide an integer value. |
tpa.details.profiles.required.error | Sender or Receiver fields cannot be empty. |
Explanation |
Sender or Receiver field is empty. |
Action |
Specify Sender and Receiver. |
tree.load.error | My webMethods encountered an error while loading the XML node tree. Click Upload to try loading the tree again. |
Explanation |
My webMethods Server encountered an error while loading the XML node tree. |
Action |
Click Upload to try loading the tree again. |
updateFAStatus.errorMsg | Error in updating EDI FA status. |
Explanation |
Error in updating EDI FA status. |
Action |
Take corrective action according to the error details. |
warn.noFileSelected | No document was chosen for submission. Specify the file path to the document to be submitted. |
Explanation |
No document was chosen for submission. |
Action |
Specify the file path to the document to be submitted. |