Trading Network Messages

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 Access denied, as the User "{0}" doesnot have the permission 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.


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}.