Integration Server Messages

0701.002 Mobile application "{0}" version {1} is already registered.
Class E
Explanation

A mobile application with this name and version already exists.
Action

Provide a different application name or version.
0701.003 Upload service "{0}" is not available.
Class E
Explanation

The upload service supplied during mobile sync component creation does not exist in the specified namespace.
Action

Make sure the service exists within the specified namespace and that the namespace and service name are typed correctly.
0701.004 Download service "{0}" is not available.
Class E
Explanation

The download service supplied during mobile sync component creation does not exist in the specified namespace.
Action

Make sure the service exists within the specified namespace and that the namespace and service name are typed correctly.
0701.005 Document type "{0}" is not available.
Class E
Explanation

The business doc type supplied during mobile sync component creation does not exist in the specified namespace.
Action

Make sure the document type exists within the specified namespace and that the namespace and document type are typed correctly.
0701.006 Mobile sync component "{0}" is suspended and cannot be changed.
Class E
Explanation

An attempt was made to edit the mobile sync component, but changes cannot be made to a mobile sync component when the component is suspended.

Action

Disable the mobile sync component and try to edit the component again.
0701.007 Mobile sync component "{0}" is associated with mobile application "{1}" version {2}. Remove association before deleting mobile sync component.
Class E
Explanation

An attempt was made to delete a mobile sync component that is associated with a mobile application.
Action

Remove the association between the mobile sync component and the mobile application. In the Integration Server Administrator, navigate to the Solutions > Mobile Support > Mobile Apps screen, click the name of the application to edit its associations, and deselect the mobile sync component from the Mobile Sync Component Alias list. Then, try deleting the mobile sync component again.

0701.008 Error: {0}
Class E
Explanation

Mobile Support encountered an error while validating the namespaces for the download service, upload service, or business doc type supplied during creation of a mobile sync component.

Action

Make sure that the service or doc type exists within the specified namespace and that the entry is typed correctly.
0701.009 Mobile application "{0}" version {1} was not found.
Class E
Explanation

Mobile Support could not find the specified mobile application and version while retrieving, updating, or deleting the mobile application or processing a synchronization request.

Action

Specify a valid mobile application and version.
0701.012 Mobile sync component "{0}" could not be suspended. Error: {1}
Class E
Explanation

Mobile Support could not suspend the mobile sync component for the reason indicated.
Action

Check the reason detailed in the message and take appropriate corrective action.
0701.014 Conflict resolution rule is not valid.
Class E
Explanation

The conflict resolution rule specified during mobile sync component creation is not valid.
Action

Specify a conflict resolution rule of either "Client wins" or "Server wins".
0701.015 Mobile sync component "{0}" already exists.
Class E
Explanation

Mobile Support could not create the mobile sync component because the specified alias already exists.
Action

Specify a different alias for the mobile sync component.
0701.016 Mobile sync component "{0}" was not found.
Class E
Explanation

Mobile Support could not find the specified mobile sync component while retrieving, updating, enabling or disabling, or deleting the mobile sync component or associating a mobile application with the component.

Action

Specify the alias of an existing mobile sync component.
0701.022 Mobile sync component "{0}" could not be created. Error: {1}
Class E
Explanation

Mobile Support could not create the mobile sync component for the reason indicated.
Action

Check the reason detailed in the message and take appropriate corrective action.
0701.023 Mobile sync component "{0}" could not be deleted. Error: {1}
Class E
Explanation

Mobile Support could not delete the mobile sync component for the reason indicated.
Action

Check the reason detailed in the message and take appropriate corrective action.
0701.024 Mobile sync component "{0}" could not be updated. Error: {1}
Class E
Explanation

Mobile Support could not update the mobile sync component for the reason indicated.
Action

Check the reason detailed in the message and take appropriate corrective action.
0701.025 Mobile sync component "{0}" could not be enabled. Error: {1}
Class E
Explanation

Mobile Support could not enable the mobile sync component for the reason indicated.
Action

Check the reason detailed in the message and take appropriate corrective action.
0701.026 Mobile sync component "{0}" could not be disabled. Error: {1}
Class E
Explanation

Mobile Support could not disable the mobile sync component for the reason indicated.
Action

Check the reason detailed in the message and take appropriate corrective action.
0701.027 Mobile sync components could not be retrieved.
Class E
Explanation

Mobile Support could not retrieve the list of mobile sync components.

Action

Check the server log for details about this error.
0701.028 Mobile sync component "{0}" could not be retrieved. Error: {1}
Class E
Explanation

Mobile Support could not retrieve the mobile sync component for the reason indicated.
Action

Check the reason detailed in the message and take appropriate corrective action.
0701.029 Mobile sync component "{0}" could not be deleted or edited.
Class E
Explanation

The mobile sync component cannot be deleted or edited because the component is still enabled.
Action

Disable the mobile sync component and try to edit or delete the component again.
0701.030 Upload service "{0}" is not implementing the "{1}" specification.
Class E
Explanation

The upload service provided during mobile sync component creation is not implementing the Mobile Support upload specification.
Action

Edit the upload service to include a reference to the wm.mobile.datasync.specs:uploadSpec specification.

0701.031 Download service "{0}" is not implementing the "{1}" specification.
Class E
Explanation

The download service provided during mobile sync component creation is not implementing the Mobile Support download specification.
Action

Edit the download service to include a reference to the wm.mobile.datasync.specs:downloadSpec specification.

0701.032 "{0}" is not a valid Integration Server service node.
Class E
Explanation

The download or upload service specified during mobile sync component creation is not a valid Integration Server service node.
Action

Ensure that element specified for the download or upload service is an Integration Server flow service (that is, a node type of NSService) and not another type of element.

0701.033 Mobile sync component state "{0}" is not valid.
Class E
Explanation

Mobile Support detected that an external attempt was made to invoke a mobile sync component that is in a state other than "enabled," "disabled," or "suspended." As a result, Mobile Support has rejected the request to invoke the mobile sync component.

Action

No action is necessary.
0701.034 Mobile application "{0}" version {1} could not be created. Error: {2}
Class E
Explanation

Mobile Support encountered an error while associating the mobile application with a mobile sync component.
Action

Check the reason detailed in the message and take appropriate corrective action.
0701.035 Mobile application "{0}" version {1} could not be updated. Error: {2}
Class E
Explanation

Mobile Support encountered an error while updating the mobile application.
Action

Check the reason detailed in the message and take appropriate corrective action.
0701.036 Mobile application "{0}" version {1} could not be retrieved. Error: {2}
Class E
Explanation

Mobile Support encountered an error while retrieving details about the association between the mobile application and a mobile sync component.

Action

Check the reason detailed in the message and take appropriate corrective action.
0701.037 Mobile applications could not be retrieved. Error: {0}
Class E
Explanation

Mobile Support encountered an error while retrieving details about the associations between mobile applications and mobile sync components.

Action

Check the server log for details and take appropriate corrective action.
0701.038 Mobile application "{0}" version {1} could not be removed. Error: {2}
Class E
Explanation

Mobile Support encountered an error while removing the association between the mobile application and a mobile sync component.
Action

Check the reason detailed in the message and take appropriate corrective action.
0701.041 Row identifier "{0}" is not present in business doc type "{1}".
Class E
Explanation

The business doc type does not contain the specified row identifier.
Action

When specifying row identifiers during mobile sync component creation, be sure the row identifiers are present in the specified business doc type.

0701.042 Row identifier "{0}" must be a string or an object.
Class E
Explanation

A row identifier was provided that is not a string or an object.
Action

When specifying row identifiers during mobile sync component creation, be sure the row identifiers are strings or objects.
0701.043 "{0}" is not a document type node.
Class E
Explanation

A business doc type was provided that is not of type NSRecord.
Action

When specifying a business doc type during mobile sync component creation, be sure the business doc type is of type NSRecord.
0701.044 Mobile application "{0}" version {1} is not associated with the mobile sync component "{2}".
Class E
Explanation

Mobile Support could not complete the synchronization operation because the mobile application is not associated with the specified mobile sync component.

Action

In Integration Server Administrator, go to the Mobile Support > Mobile App page and associate the mobile application with the specified mobile sync component.

0701.045 Mobile sync component "{0}" could not be suspended. Only enabled mobile sync components can be suspended.
Class E
Explanation

An attempt was made to suspend the mobile sync component, but the attempt failed because the mobile sync component was not enabled.

Action

Ensure that the mobile sync component is enabled before attempting to suspend it.
0701.046 Requested mobile sync component "{0}" is not enabled.
Class E
Explanation

Mobile Support could not process the synchronization request because the specified mobile sync component is not enabled.
Action

In Integration Server Administrator, go to the Mobile Support > Mobile Sync Components page and enable the mobile sync component. Then, resubmit the synchronization request.

0701.047 No mobile sync component was specified.
Class E
Explanation

Mobile Support could not process the synchronization request because no mobile sync component was specified.
Action

Ensure that the synchronization request includes a mobile sync component alias and a mobile application name and version.
0701.048 Mobile sync component "{0}" cannot be suspended because it was configured to not store business data in the sync store.
Class E
Explanation

Mobile Support could not suspend the specified mobile sync component because the Store Business Data check box was not selected in Integration Server Administrator when the mobile sync component was configured. When business objects are not stored in the sync store, mobile sync components can be disabled but not suspended.

Action

In Integration Server Administrator, on the Solutions > Mobile Support > Mobile Sync Components screen, disable the mobile sync component.

0701.049 Mobile sync component "{0}" cannot be refreshed because it was configured to not store business data in the sync store.
Class E
Explanation

Mobile Support could not refresh the specified mobile sync component because the Store Business Data check box was not selected when the mobile sync component was configured. When business objects are not stored in the sync store, mobile sync components cannot be refreshed.

Action

In Integration Server Administrator, on the Solutions > Mobile Support > Mobile Sync Components > Edit Mobile Sync Component screen, select the Store Business Data check box. Then, disable and enable the mobile sync component.

0701.057 Error occurred while processing record "{0}".
Class E
Explanation

Mobile Support encountered an error while processing the specified record.
Action

Check the server log for details and take appropriate corrective action.
0701.068 "{0}" is not locked by thread "{1}".
Class E
Explanation

The thread attempted to unlock the specified record, but the record is not owned by the thread.
Action

Try the request again. If the issue recurs, contact Software AG Global Support.
0701.069 Thread "{0}" could not unlock record "{1}" because record is already unlocked.
Class E
Explanation

The thread attempted to unlock the specified record, but the record was not locked.
Action

Try the request again. If the issue recurs, contact Software AG Global Support.
0701.080 Could not refresh mobile sync component "{0}". Mobile sync component is in "{1}" state.
Class E
Explanation

Mobile Support could not refresh the mobile sync component because the component is not suspended.
Action

Suspend the mobile sync component.
0701.093 Error occurred while initializing sync store.
Class E
Explanation

Mobile Support experienced an error while initializing the sync store.
Action

Check the server log for details and take appropriate corrective action.
0701.095 Validation Error occurred: {0}.
Class E
Explanation

Mobile Support could not process the data row because the data that was submitted was not valid.
Action

Correct the validation error.
0701.096 Message "{0}" skipped. Unique ID is missing.
Class E
Explanation

Mobile Support could not process the data row because the data does not contain row identifier(s).
Action

Supply one or more row identifiers.
0701.097 Unable to synchronize the mobile device. Exception: {0}
Class E
Explanation

Mobile Support could not synchronize the mobile device for the reason specified.
Action

Check the server log for details and take appropriate corrective action.
0701.112 Unable to save the record associated with unique ID and mobile sync component of "{0}". Exception: {1}
Class E
Explanation

Mobile Support could not save the record for the reason indicated.
Action

Check the reason detailed in the message and take appropriate corrective action.
0701.113 Unable to save record data. Exception: {0}
Class E
Explanation

Mobile Support could not save the record data for the reason indicated.
Action

Check the reason detailed in the message and take appropriate corrective action.
0701.114 Unable to write record data. Exception: {0}
Class E
Explanation

Mobile Support could not write the record data for the reason indicated.
Action

Check the reason detailed in the message and take appropriate corrective action.
0701.117 Unable to delete record associated with unique ID "{0}" and mobile sync component "{1}". Reason: {2}
Class E
Explanation

Mobile Support could not delete the record for the reason indicated.
Action

Check the reason detailed in the message and take appropriate corrective action.
0701.118 Unable to delete record associated with mobile sync component "{0}". Reason: {1}
Class E
Explanation

Mobile Support could not delete the record for the reason indicated.
Action

Check the reason detailed in the message and take appropriate corrective action.
0701.119 Unable to get records from sync store. Reason: {0}
Class E
Explanation

Mobile Support could not retrieve records from the sync store for the reason indicated.
Action

Check the reason detailed in the message and take appropriate corrective action.
0701.121 Unable to obtain connection from connection pool. Exception: {0}
Class E
Explanation

Mobile Support could not obtain a connection from the connection pool for the reason indicated.
Action

In Integration Server Administrator, on the Settings > JDBC Pools screen, select the pool alias associated with the MobileSupport functional alias. On the Connection Aliases > Edit screen, increase the number of maximum connections.

0701.122 Unable to obtain database connection from connection pool for sync store.
Class E
Explanation

Mobile Support could not obtain a connection to the database configured for the sync store.
Action

In Integration Server Administrator, on the Settings > JDBC Pools screen, test the connection from the MobileSupport functional alias to the database. Take appropriate corrective action to resolve any errors.

0901.001 Name cannot be null or empty.
Class E
Explanation

While creating or updating an OData element, Name cannot be null or empty.
Action

Provide a valid Name for the OData element.
0901.002 The specified name is invalid. Ensure that the name does not exceed 480 characters, does not start with a number or "_" symbol, and that it contains no special characters other than "_".
Class E
Explanation

Specified name is invalid because name can contain only alphanumeric characters and \"_\" symbol. Name must start with an alphabet and not with a number or \"_\" symbol.

Action

Provide a valid name that starts with an alphabet and contains only alphanumeric characters and \"_\" symbol. For information about other supported unicode characters, see SimpleIdentifier in Common Schema Definition Language (CSDL) documentation.

0901.003 Length of the Name cannot exceed 480 characters.
Class E
Explanation

The Name specified contains more that 480 characters.
Action

Ensure that the length of the Name does not exceed 480 charatcters.
0901.004 Cannot rename Complex Type name to "{0}". Complex Type name must be unique.
Class E
Explanation

The Complex Type name could not be renamed because a Complex Type with the same name already exists.
Action

Enter a unique Name for the Complex Type.
0901.005 Cannot rename Entity Type name to "{0}". Entity Type name must be unique.
Class E
Explanation

The Entity Type name could not be renamed because an Entity Type with the same name already exists.
Action

Enter a unique Name for the Entity Type.
0901.006 Cannot rename Property name to "{0}". Property name must be unique.
Class E
Explanation

The Property name could not be renamed because a Property with the same name already exists.
Action

Enter a unique Name for the Complex Type.
0901.007 Cannot delete Complex Type because it is referred to by "{0}".
Class E
Explanation

The Complex Type cannot be deleted because it is referred to by a Complex property.
Action

Ensure that all references to the Complex Type is removed before deleting it.
0901.008 A Property with the same name already exists in the Entity Type.
Class E
Explanation

The new Property with the specified name cannot be added because another Property with the same name already exists in the Entity Type.

Action

Enter a unique Name for the new Property that you want to add.
0901.009 A Property with the same name already exists in the Complex Type.
Class E
Explanation

The new Property with the specified name cannot be added because another Property with the same name already exists in the Complex Type.

Action

Enter a unique Name for the new Property that you want to add.
0901.010 An Entity Type with the same name already exists in the OData Service.
Class E
Explanation

The new Entity Type cannot be created with the specified name because another Entity Type with the same name already exists in the OData Service.

Action

Enter a unique Name for the Entity Type that you want to add.
0901.011 A Complex Type with the same name already exists in the OData Service
Class E
Explanation

The new Complex Type cannot be added with the specified name because another Complex Type with the same name already exists in the OData Service.

Action

Enter a unique Name for the Complex Type that you want to add.
0901.012 An Association with the same name already exists in the OData Service.
Class E
Explanation

A new Association with the specified name cannot be created because another Association with the same name already exists in the OData Service.

Action

Enter a unique name for the Association that you want to add.
0901.013 Invalid index position "{0}"; Unable to move the OData element.
Class E
Explanation

Unable to move the OData element to an invalid index position.
Action

Ensure that the element is moved to an index position within the same container.
0901.014 Invalid property. Property "{0}" does not exist and hence, cannot be moved.
Class E
Explanation

The specified Property cannot be moved because it does not exist.
Action

Ensure that the Property you want to move is already added to the OData service.
0901.015 Cannot delete Entity Type because it is referred to by one of the Associations.
Class E
Explanation

The Entity ype cannot be deleted bacause it is referred to by one of the Associations.
Action

Ensure that all references to the Entity Type is removed before deleting it.
0901.016 Facet "{0}" is not applicable for Type "{1}"
Class E
Explanation

The specified Facets property is not applicable for the selected Type.
Action

Ensure that only those Facets that apply to the selected Type are specified.
1000.0042 Error in parsing EDM simple type "{0}" while evaluating the filter query.
Class E
Explanation

Error in parsing the literal value of the filter expression because the literal value is incorrect.
Action

Ensure that the correct literal value is given in the filter expression.
1000.0043 Error in parsing property "{0}" in the Entity Data Model (EDM) while evaluating the filter query.
Class E
Explanation

Error in parsing the property value of the filter expression.
Action

Ensure that the correct property value is given in the Entity Data Model (EDM).
1000.0044 Error in evaluating the filter expression "{0}".
Class E
Explanation

The syntax of the filter expression is incorrect.
Action

Ensure that the syntax of the filter expression is correct.
1000.0047 Internal server error for request "{0}" due to "{1}"
Class E
Explanation

Validation error from Olingo.
Action

Refer to the error message text for more details and correct the URL specified.
1000.0048 OData request "{0}" failed with error code "{1}" reason "{2}"
Class E
Explanation

Validation error from Olingo.
Action

Refer to the error message text for more details and correct the URL specified.
1000.0049 Entity type "{0}" not found in the entity data model.
Class E
Explanation

The entity type specified in the OData request is incorrect, deleted, or not available in the entity type model.
Action

Ensure that the entity type that you specified exists in the entity data model.
1000.0050 Odata data request failed with the error "{0}"
Class E
Explanation

Error in the OData handler because the request is malformed.
Action

See the information provided in the error message and correct the request URL.
1000.0052 Error in retrieving NSOdata service node from OData Context.
Class E
Explanation

The OData service node in the OData context is null.
Action

Ensure that the path to the OData service node specified in the request URL is correct.
12.31 Invalid SAML assertion. The trust/signature validation failed with exception: {0}
Explanation

Integration Server received a SAML assertion that either failed during signature validation or it did not come from a trusted issuer.

Action

Review the request and work with the sender to correct the issues.

12.45 Error in getting security token form SAML assertion. SAML Assertion is: {0}
12.46 No user mapped to this X509 certificate.
12.47 No X509 certificate chain found.
12.48 No PAM authentication module.
12.49 No PAM user found.
12.50 Basic authentication, no user found.
12.51 Digest authentication, no user found.
12.52 Default authentication, no user found.
12.53 Request {0} for subject {1} was rejected.
12.54 Using account {0} for {1} subject {2}.
12.55 Error initializing OpenID Provider: {0}: {1}
12.56 Error initializing OpenID Providers
12.57 Requesting delegatable kerberos token for user: {0}
12.58 Server logged in as user : {0} into KDC
12.59 Kerberos delegated credentials set for user: {0}
12.60 Found kerberos delegated credentials for user: {0} . Placed in Context
12.61 Logged in as {0} . Using delegated kerberos credentials of {1} to request for service principal
12.62 Obtained delegated kerberos token for user : {0}
12.63 Kerberos ticket is set in the HTTP header: {0}
12.64 Kerberos delegated credentials set for : {0}
12.65 Unable to initialize the set of external OAuth Authorization Servers
12.66 Refreshing JAAS configuration.
12.67 NonceCacheManagerEhcacheV3 unable to store nonce {0}; caught: {1}
12.68 NonceCacheManagerEhcacheV3 unable to remove nonce {0}; caught: {1}
12.9999...0 {0}
13.10 Unable to register multipart coder {0} for service {1}. A coder is already registered with that service name.
13.11 Unable to deregister multipart coder for service {0}. There is no coder registered with that service name.
13.5 Deregistering multipart content handler for service {0}.
13.6 Registering multipart coder {0} for service {1}.
13.7 Deregistering multipart coder for service {0}.
13.8 Unable to register multipart content handler {0} for service {1}. A content handler is already registered with that service name.
13.9 Unable to deregister multipart content handler for service {0}. There is no content handler registered with that service name.
14.59 OutboundPasswordManager could not find package: {2}
14.60 Master password updated for package: {0}
14.61 Package {2} is not enabled.
14.62 Package name cannot be null.
14.63 The value specified for the watt.server.xml.encoding parameter is not supported by your JVM. Integration Server might not be able to process the XML files.
14.64 Error while sending password expiry email, error message : {0}.
14.65 Passwords for users {0} has expired, the current expiration interval is {1} days.
14.66 Passwords for users {0} will expire soon.
147.4 Error while executing command {0}: {1}
JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+DB_SQL_INJECTION_FILTER_FAILED Possible SQL injection threat for {0} database
Class W
Explanation

Incoming request to Enterprise Gateway Server contains suspicious data (payload), which could possibly cause an SQL injection attack.

Action

Contact the Integration Server system administrator to inspect and validate the incoming request to avert an SQL injection attack.

JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+STD_SQL_INJECTION_FILTER_FAILED Possible SQL injection threat detected with the incoming payload.
Class W
Explanation

Incoming request to Enterprise Gateway Server contains suspicious payload, which could possibly cause an SQL injection attack.
Action

Contact the Integration Server system administrator to inspect and validate the incoming request to avert an SQL injection attack.

15.9999 {0}
154.1 {0}
155.9998 Exception --> {0}
163.1 JWT Token is not present. Send a Bearer token along with the request.
163.10 The JWT does not contain an Issuer claim (iss).
163.11 The certificate used to verify the JWT signature has expired (trustStore={0}, keyStore={1}).
163.12 The certificate used to verify the JWT signature is not yet valid (trustStore={0}, keyStore={1}).
163.13 The JWT signature could not be verified by any of the certificates mapped to the JWT issuer ({0}).
163.2 Unable to find user corresponding to the JWT Bearer token.
163.3 Verifying with truststore alias "{0}" and certificate alias "{1}".
163.4 Verified claim : "{0}".
163.5 User "{0}" found in the JWT Bearer token.
163.6 JWT does not contain a Subject claim (sub).
163.7 The JWT aud claim does not contain the Audience configured for this Integration Server.
163.8 The JWT is not yet valid. The current time is before the nbf value.
163.9 The JWT has expired. The current time is after exp value.
163.9999 Exception --> {0}
21.1001 The on-premise service signature cannot be null or empty.
Class E
Explanation

While creating an Integration Cloud connector service, the service signature cannot be null or empty.
Action

Ensure that service signature is not null or empty while invoking the service to generate an Integration Cloud connector.

21.1002 Package name cannot be null or empty.
Class E
Explanation

While creating an Integration Live connector service, the package name cannot be null or empty.
Action

Ensure that you specify the package name while invoking the service to generate an Integration Live connector.
21.1003 The on-premise service name cannot be null or empty.
Class E
Explanation

While creating an Integration Live connector service, the on-premise service name cannot be null or empty.
Action

Ensure that you specify an on-premise service name while invoking the service to generate an Integration Live connector.
21.1004 Connector service name cannot be null or empty.
Class E
Explanation

While creating an Integration Live connector service, the connector service name cannot be null or empty.
Action

Ensure that the connector service name is not null or empty while invoking the service to generate an Integration Live connector.
21.1005 An error occurred while creating the webMethods Cloud connector service. Details: {0}
Class E
Explanation

Unknown error occurred while creating the Integration Live connector service.
Action

Contact Software AG global support.
21.1006 Interface name cannot be null or empty.
Class E
Explanation

While creating the Application folder structure, the Interface name cannot be null or empty.
Action

Ensure that you specify the Interface name while invoking the service to create the Application folder structure.
21.1007 Application name cannot be null or empty.
Class E
Explanation

While creating the Application folder structure, the Application name cannot be null or empty.
Action

Ensure that you specify the application name while invoking the service to create the Application folder structure.
21.1008 An error occurred while creating the application interface. Details: {0}
Class E
Explanation

Unknown error occurred while creating the application interface.
Action

Contact Software AG global support.
21.2001 An error occurred while connecting to the Universal Messaging Realm. Error: {0}
Class E
Explanation

Integration Server encountered the specified error while connecting to the Universal Messaging Realm.
Action

Ensure that the Realm URL and that the port identified in the URL is active on the Universal Messaging Server. In addition, take the appropriate action based on the details shown in the message.

21.2002 User {0} is not authorized to perform administrative functions on the Universal Messaging Realm.
Class E
Explanation

The specified user does not have the rights required to perform administrative functions.
Action

Log on with a user name that has the proper permissions to perform administrative functions.
21.3 No Git credentials were found for tenant {0} (user {1}). Cannot access the remote Git repository.
Class E
Explanation

Integration Server is not provisioned with Git credentials for the tenant.
Action

Contact the system administrator.
21.4 Tenant {0} has no credentials. Cannot fetch tenant's package from repository.
Class E
Explanation

Integration Server is not provisioned with GIT credentials for the tenant.
Action

Contact the system administrator.
21.5 The local Git repository does not exist for package {0}.
Class E
Explanation

The specified package is not associated with a local Git repository.
Action

Contact the system administrator.
21.6002 Settings could not be saved because of the following error: {0}
Class E
Explanation

The settings could not be saved because of the specified error.

Action

Take the appropriate action based on the details shown in the message.
21.6003 The following error occurred while saving settings: {0}. See the error log for the full stack trace.
Class E
Explanation

Integration Server encountered the specified error while saving the settings.
Action

Review the server log for details and take appropriate corrective action.
21.6004 An error occurred while loading information from the webMethods Clould environment.
Class E
Explanation

Integration Server encountered an error while loading information from the webMethods Cloud environment.
Action

Review the server log for details and take appropriate corrective action.
21.6005 webMethods Cloud information was not loaded because the settings are not specified.
Class E
Explanation

You must specify the settings on the Settings page to load webMethods Cloud information.
Action

Specify the settings on the Settings page.
21.7 An exception occurred during the Git operation for package {0}: {1}
Class E
Explanation

Integration Server encountered the specified error during the Git operation.
Action

Contact the system administrator.
21.7003 Could not save application {0}. A service with Display Name {1} already exists
Class E
Explanation

A service with the specified display name already exists within the application. The display name of each service in the application must be unique.

Action

Specify a unique display name for the service.
21.7004 Could not save application {0} because there are no services selected.
Class E
Explanation

There are no services specified for the application. You must specify at least one service for an application to be valid.
Action

Specify one or more services for the application.
21.7007 The following error occurred while saving application {0}: {1}. See the error log for the full stack trace.
Class E
Explanation

Integration Server encountered the specified error while saving the application.
Action

Review the error log and correct the error.
21.7008 The following error occurred while deleting application {0}: {1} See the error log for the full stack trace.
Class E
Explanation

Integration Server encountered the specified error while deleting the application.
Action

Review the error log and correct the error.
21.7009 The application named {0} does not exist.
Class E
Explanation

The application’s name contains too many characters.
Action

Rename the application using no more than 32 characters.
21.7009...0 The application named {0} does not exist.
Class E
Explanation

The application does not exist. It might have been deleted by another user.
Action

Retry the action. If the issue persists, contact your system administrator.
21.7010 An application named {0} already exists.
Class E
Explanation

The application is not valid because another application with the specified name already exists.
Action

Specify a unique application name.
21.7011 Could not save application {0} because the Display Name field for one or more of the services is empty.
Class E
Explanation

The Display Name field is not specified for one or more services selected for the application.
Action

Specify a valid Display Name for each service in the application.
21.7012 Application {0} could not be saved because the Name contains: {1}.
Class E
Explanation

The application’s name contains the specified illegal character, leading digit, or reserved word.
Action

Rename the application.
21.7013 Application {0} could not be saved because the service Display Name {1} contains: {2}
Class E
Explanation

The Display Name field of a service in the application contains the specified illegal character, value, or reserved word.
Action

Remove the specified character, value, or word from the Display Name.
21.7014 The following error occurred while uploading application {0}: {1}. See the error log for the full stack trace.
Class E
Explanation

The specified error occured while uploading the application.
Action

Review the error log and correct the error.
21.7016 Application {0} could not be uploaded because of the following error: {1}
Class E
Explanation

Integration Server encountered the specified error while uploading the application.
Action

Check the server log for details and take appropriate corrective action.
21.7020 Applications require that at least one account be selected before they can be uploaded.
Class E
Explanation

Applications require that at least one connection be selected before it can be uploaded.

Action

Select a connection for the application.
21.7021 No accounts exist. Go to webMethods Cloud > Accounts and create an account.
Class E
Explanation

Applications require that at least one account be selected before being uploaded, but no accounts have been created.
Action

Go to webMethods Clould > Accounts and create at least one account.
21.7022 The on-premise Integration Server could not upload the application because the service {0} does not exist.
Class E
Explanation

The specified service does not exist.
Action

Confirm that the service exists on the system.
21.8001 Account with alias name {0} does not exist.
Class E
Explanation

There is no account with the specified alias name on Integration Server.
Action

Check the alias name of the Integration Live account that you are attempting to use to ensure you have the correct name.
21.8002 Account with alias name {0} already exists.
Class E
Explanation

The account is not valid because another account already uses the specified alias name.
Action

Specify an alias name for the account that is unique for the Integration Server.
21.8003 The Alias Name parameter is required.
Class E
Explanation

The Alias Name parameter is required but is either missing or is null.
Action

Make sure the Alias Name parameter is specified and that the value is not null.
21.8005 The Tenant ID parameter is required.
Class E
Explanation

The Tenant ID parameter is required but is either missing or is null.
Action

Make sure the Tenant ID parameter is specified and that the value is not null.
21.8006 The Run As User parameter is required.
Class E
Explanation

The Run As User parameter is required but is either missing or is null.
Action

Make sure the Run As User parameter is specified and that the value is not null.
21.8012 Error while enabling the listener for account {0}.
Class E
Explanation

Integration Server encountered an error while enabling the listener for the specified account.
Action

Check the server log for details and take appropriate corrective action.
21.8013 Error while disabling the listener for account {0}.
Class E
Explanation

Integration Server encountered an error while disabling the listener for the specified account.
Action

Check the server log for details and take appropriate corrective action.
21.8019 Error sending response for request ID {1} to execute service {0}.
Class E
Explanation

Integration Server encountered an error while sending a response to the request received from webMethods Cloud for the specified request ID.

Action

Check the server log for details and take appropriate corrective action.
21.8021 Error executing service {0} for request ID {1}.
Class E
Explanation

Integration Server encountered an error while executing the specified service.
Action

Check the server log for details and take appropriate corrective action.
21.8022 Test of the account failed. Confirm that the parameters are correct and tenant is registered in webMethods Cloud.
Class E
Explanation

The test of the account failed.
Action

Make sure that the information provided is correct and that the tenant is registered in webMethods Cloud.
21.8024 An error was encountered while executing service {0}. The response was not received within {1} milliseconds.
Class E
Explanation

Integration Server did not receive a response from the service within the time allowed.
Action

Ensure that the on-premise Integration Server is connected to webMethods Cloud and that the account is enabled.
21.8026 The information for account {0} was not uploaded successfully on stage {1}. Check the Integration Server logs for more details. Error: {2}
Class E
Explanation

Integration Server encountered the specified error while uploading the account.
Action

Check the server log for details and take appropriate corrective action.
21.8027 Service {0} is not shared by on-premise for application {1}.
Class E
Explanation

The specified service is not shared by the on-premise Integration Server.
Action

Make sure that the service is assigned to the specified application.
21.8029 Invalid account {0} associated with the execution of service {1}.
Class E
Explanation

The specified account is not associated with the application that shares the service.
Action

Ensure that the application that shares the service is associated with the specified account.
21.8031 Account {0} was not removed from stage {1}. Check the Integration Server logs for more details. Error: {2}
Class E
Explanation

The specified account was not deleted from the stage.
Action

Check the server error log for more detailed information and take the appropriate corrective action.
21.8032 Invalid value {1} specified for the stage parameter of account {0}.
Class E
Explanation

The account settings were not retrieved correctly from webMethods Cloud.
Action

Make sure that you obtained the correct account settings from webMethods Cloud.
21.8033 No account information is configured for webMethods Cloud.
Class E
Explanation

You cannot upload or enable accounts or applications without first configuring the account settings.

Action

Specify the account settings and retry the operation.
21.8034 The webMethods Cloud account endpoint to which the on-premise Integration Server should send responses is not valid
Class E
Explanation

You cannot upload or enable accounts or applications without first configuring the account settings.

Action

Specify the account settings and retry the operation.
21.8035 Invalid account settings. Make sure that webMethods Cloud settings are configured.
Class E
Explanation

Integration Server cannot connect to webMethods Cloud because there are no settings configured for the webMethods Cloud.

Action

Configure a valid webMethods URL on the Settings screen of the Integration Server Administrator.
21.8036 Stage for the account is not configured on webMethods Cloud. Contact webMethods Cloud Administrator.
Class E
Explanation

The stage specified for the account does not exist on Integration Cloud.
Action

Contact the webMethods Cloud administrator.
21.8037 Stage for the application is not configured on webMethods Cloud. Contact webMethods Cloud Administrator
Class E
Explanation

The stage specified for the application does not exist on Integration Cloud.
Action

Contact the webMethods Cloud administrator.
21.9003 Cannot delete account {0} because it is in use by other applications.
Class E
Explanation

The specified account is in use by other applications and cannot be deleted.
Action

Modify the application to use a different account, or leave the account active.
21.9006 Unable to connect to on-premise Integration Server for account {0}.
Class E
Explanation

The specified account cannot be tested.
Action

Ensure that the specified account is enabled on the on-premise Integration Server.
24.23 Central User Manager queried for group "{0}" of type {1} and returned "{2}".
24.24 Central User Manager queried for user "{0}" and returned "{1}".
24.25 Central User Manager queried for membership. User "{0}" {1} a member of "{2}".
24.26 Central User Manager found user "{0}" in "{1}" of type {2}.
24.27 Central User Manager searched for group "{0}" and returned "{1}".
24.28 Central User Manager searched for user "{0}" and returned "{1}".
24.39 Error while creating Integration Live user groups, tenantID : {0}. Error message: {1}. Stack trace: {2}
Class E
Explanation

An unexpected error occurred while creating Integration Live user groups.
Action

Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

24.41 Integration Live Manager addUserInGroup(), --> group "{0}" reterived from UserManager for group id "{1}".
24.42 Integration Live Manager addUserInGroup(), --> user "{0}" added into group "{1}".
24.43 Integration Live Manager updateUserInGroup(), --> before update user "{0}", saml security token "{1}".
24.44 Integration Live Manager updateUserInGroup(), --> after update user "{0}", saml security token "{1}".
24.45 Integration Live Container UserManager addUser(), SagSecurityToken --> {0}.
24.46 Integration Live Container UserManager addUser(), tenantID: {0}.
24.47 Integration Live Container UserManager addUser(), user already present--> {0} but it got updated using this Assertion.
24.48 Integration Live Container UserManager addUser(), user added--> {0}.
24.49 Integration Live Container UserManager removeUser(), user--> {0}.
24.50 Integration Live Container UserManager removeUser(), user removed successfully--> {0}.
24.51 Integration Live Container UserManager getUser(), user not found --> {0}.
24.52 Integration Live Container UserManager addUserInGroup(), --> group "{0}" reterived from UserManager.
24.53 Integration Live Container UserManager addUserInGroup(), --> user "{0}" added into group "{1}".
24.54 Integration Live Container UserManager addUserInGroup(), --> group "{0}" is not found so not adding to user {1}.
24.55 Integration Live Container UserManager addUserInGroup(), --> role "{0}" reterived from UserManager.
24.56 Integration Live Container UserManager addUserInGroup(), --> user "{0}" added into role "{1}".
24.57 Integration Live Container UserManager addUserInGroup(), --> role "{0}" is not found so not adding to user {1}
24.58 Integration Live Container UserManager getUser(), userID: {0}.
24.59 Integration Live Container UserManager getUser(), user found --> {0}.
24.60 Could not access administrator user:{0} - user:{1} is not an administrator.
24.61 Could not access user:{0} - user:{1} is not a member of the same groups.
25.67 Integration Server could not initialize the cluster. Stopping Integration Server initialization. Use the server log and error log to diagnose and correct the problem.
25.71 The JCE Unlimited Strength Jurisdiction Policy File was not found
28.62 Unable to load keystores and truststores for package {0}.
28.63 Error in un-loading keystores and truststores for package {0}
28.64 Error loading web service descriptor {0} : {1}
3 Enabled
33.187 ClusterMembers Error getting TCDB Coordinator: {0}
35.5 Number of lines to display must be a non negative number. {0}.
4 Disabled
4.9998 Exception -> {0}
5 Suspended
50.22 ForEach failed: {0}: out-array={1}, in-array={2}
50.23 ForEach failed: No source data available for in-array {0}
50.24 ForEach failed: in-array {0} is not an array type.
50.25 ForEach out-array {0} is not the same length as in-array {1}.
53.15 The listener for the port with alias "{0}" does not exist.
53.9999 {0}
6.35 SSL port{0} is trying to enable protocol {1} which is not supported by the JVM. The protocol {1] is ignored.
6.36 Outbound SSL connection {0} is trying to enable protocol {1} which is not supported by the JVM. The protocol {1} is ignored.
62.39 JSON schema must not be empty
62.40 Invalid JSON schema: {0}
62.41 Could not create a JSON document type: Definition of references could not be found for: {0}
62.42 Invalid JSON string: {0}
62.43 Could not create JSON document type: {0}, Provided JSON type is not supported at the root level
64.32 HTTP Put {0}
64.33 HTTP Delete {0}
64.34 HTTP Head {0}
64.35 HTTP Options {0}
64.36 HTTP Trace {0}
68.29 {0}
68.30 {0}
68.31 {0}
7.5 Access Denied. User "{0}" in tenant {1} does not have permissions to access assets in package {2}.
70.9999 {0}
71.12 EPRT command refused. The EPRT address {0} does not match the original host address {1}.
72.19 Using default html encoding for input: "{0}"
72.20 Exception occurred while initializing encoder {0}. Reason: {1}
72.21 Initialization of encoder "{0}" failed
72.22 Performing "{0}" encoding for input: "{1}". Output is: "{2}"
72.23 Failed to initialize the bundle for encoder "{0}"
72.24 Initialization of encoder "{0}" completed
72.25 Exception occurred while getting file path of "{0}"
75.9998 Unable to extract the password associated with the alias: {0}
76.35 A valid encoding is not available in the XML header {0}. Proceeding with the encoding value specified in watt.server.xml.encoding = {1}.
76.9999 {0}
88.9443 One or more required Headers "{0}" are not present in the SOAP response.
95.27 The audit logging database does not populate the CHAR_OCTET_LENGTH field in its metadata. Integration Server cannot determine the maximum number of bytes for the WMSERVICEACTIVITYLOG.FULLMESSAGE and WMSERVICECUSTOMFLDS.STRINGVALUE columns. If the data inserted into these columns need to be truncated, they will be truncated based on the number of characters rather than the number of bytes. This may lead to SQLExceptions while writing to the audit log. To avoid this, use the ALTER TABLE command on your database to increase the size of these columns.
95.28 Audit Logging: The {0} has entered fail-fast mode.
95.29 Audit Logging: The {0} has exited fail-fast mode.
95.34 Audit Logging: Error occurred while reconnecting to session for messaging connection alias {0}; will retry after {1} seconds. Error message: {2}
95.35 Audit Logging: Starting monitor for creating session with messaging connection alias {0}; retry interval is {1} seconds.
95.36 Audit Logging: Attempting to reconnect to session for messaging connection alias {0}.
95.41 Skipping {0} audit log data. It is larger than {1} MB, the limit defined by watt.server.diagnostic.logFiles.maxMB.
95.42 The {0} field in a {1} audit record was truncated. CONTEXTID: {2}. MSGID: {3}. Full value: {4}
96.11 The DataStoreDBListener has been notified of SQLException. The JDBC connection to {0} is still valid. Returning it to the pool.
96.20 creation of JDBC connection failed with exception : {0}
96.21 JDBC Connection pool is currently in Fail-Fast mode for pool {0}:{1}
96.22 {0} threads are waiting to get the JDBC Connection for pool {1}:{2}
96.23 Connection pool size is {0}, Available pool size is {1} for pool {2}:{3}. The Maximum connection is {4}
96.24 Created a new JDBC Connection for pool {0}:{1}. Connection pool size is {2}.
96.25 Got Exception for pool {0}:{1}. Exception details: {2}
96.26 The JDBC function "{0}", pool alias "{1}" has entered fail-fast mode. The exception message is: {2}
96.27 The JDBC function "{0}", pool alias "{1}" has exited fail-fast mode.
96.28 Re-initializing the pool {0}:{1}.
96.29 Removed the connection from pool {0}:{1}. Connection pool size is {2}. Available pool size is {3}.
96.30 Released the connection to pool {0}:{1}. Connection pool size is {2}. Available pool size is {3}.
96.31 The JDBC function "{0}", pool alias "{1}" is in fail-fast mode. The exception message is: {2}
96.8 JDBC Connection pool threshold {0}, {1} available for pool {2}:{3}
96.9 JDBC Connection pool waiting threads threshold {0}, {1} threads waiting for connection for pool {2}:{3}
98.125 Exception:{0} while executing trigger. Rejecting Document for TriggerStore:{1}.
98.126 Exception:{0} while executing trigger. Unable to mark as complete to the Document History for TriggerStore:{1}.
ACCOUNT_LOCKED User {0} is locked.
ALREADY_MARKED_ROLLBACK tran was rolled back because tran was marked for rollback
ANNOTATION_FIELD_DUPLICATE_NAME {0} - {1} appears more than once in the document type
ANNOTATION_FIELD_ENV {0} - {1} envelope field is not allowed as an annotation field
ANNOTATION_FIELD_INVALID_NAME {0} - {1} is not a valid Digital Event Services field name
ANNOTATION_FIELD_NOT_FOUND {0} - {1} field not found in document type
ANNOTATION_FIELD_NOT_VALID {0} - {1} field is invalid type
ANNOTATION_NSR_NOT_PUBLISHABLE Document type is not publishable
ANNOTATION_NSR_NOT_SPECIFIED Document type not specified
APLog.string(APLog.AP_CONNECTION_TEST_FAILED) Test of CentraSite connection failed.
Explanation

An attempt was made to connect to CentraSite, but a connection could not be made.
Action

Check the connection parameters in Integration Server Administrator. Check the error log in both Integration Server and CentraSite.
FAC_ART+ART2 Unable to get adapter type information. Internal error.
Class E
Explanation

An error occurred while fetching the list of supported services for a particular adapter.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART3 Unable to get information about adapter type {0}.
Class E
Explanation

An error occurred while retrieving a service's localized deployment values (adapter name, adapter version, adapter JCA version) from the specified adapter's metadata.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART4 Error getting available packages.
Class E
Explanation

An error occurred while retrieving a list of packages available for node creation.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART5 Error(s) during Adapter Runtime startup.
Class E
Explanation

An error occurred during the initialization of the com.wm.pkg.art.AdapterRuntimeGlobals class.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART6 Unable to initialize transaction manager. Transaction manager already initialized.
Class E
Explanation

WmART has attempted to initialize the Transaction Manager twice.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART7 Unable to get managed connection factories for adapter type {0}.
Class E
Explanation

WmART was unable to obtain a list of connection factories for the specified adapter.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART8 Unable to get the description and display name for connection type "{0}" of adapter type "{1}".
Class E
Explanation

An error occurred while getting the display name and description for the specified connection/listener in the specified adapter.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART9 Error(s) while registering adapter type {0}.
Class E
Explanation

An error occurred while loading the specified adapter.
Action

This might be due to a connection that failed to initialize properly. Ensure that the adapter's connections can communicate with their respective resources. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART10 Error(s) while unregistering adapter type {0}.
Class E
Explanation

An error occurred while shutting down the specified adapter's connection resources.
Action

This might be due to problems in one or more connections. Ensure that all adapter connections shut down properly when the adapter was unloaded.

FAC_ART+ART11 Error occurred while Adapter Runtime was loading an adapter type. Missing required input, "{0}".
Class E
Explanation

The class name of an adapter was not present as the first item in the pipeline given to com.wm.pkg.art.deployment.Service.registerAdapterType.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART12 Error occurred while Adapter Runtime was loading an adapter type. Unexpected adapter type object "{0}" for input "{1}".
Class E
Explanation

The class name of the object passed to com.wm.pkg.art.deployment.Service.registerAdapterType is not derived from WmAdapter.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART13 Error occurred while Adapter Runtime was loading adapter type "{0}".
Class E
Explanation

An error occurred while loading the specified adapter.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART14 Error occurred while Adapter Runtime was unloading an adapter type. Missing required input, "{0}".
Class E
Explanation

The class name of an adapter was not present as the first item in the pipeline given to com.wm.pkg.art.deployment.Service.unregisterAdapterType.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART15 Error occurred while Adapter Runtime was unloading an adapter type. Unexpected adapter type object "{0}" for input "{1}".
Class E
Explanation

The class name of the specified object passed to com.wm.pkg.art.deployment.Service.unregisterAdapterType is not derived from WmAdapter.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART16 Error occurred while Adapter Runtime was unloading adapter type "{0}".
Class E
Explanation

An error occurred while loading the specified adapter.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART17 Error occurred while registering XidFactory for adapter type "{0}".
Class E
Explanation

WmART was unable to locate the Transaction Manager or Transaction ID Factory class for the specified adapter.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART18 Unable to get XidFactories for adapter type "{0}".
Class E
Explanation

WmART was unable to locate the class loader while retrieving the Transaction ID Factory map for the specified adapter.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART19 Unable to get XidFactory {0} for XAResource {1} in adapter type "{2}".
Class E
Explanation

WmART was unable to determine the corresponding XidFactory class for the specified XAResource class while loading the adapter.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART20 Error occurred while loading online help system for adapter type "{0}".
Class E
Explanation

An error occurred while WmART was attempting to fetch the path to the specified adapter's online help file.
Action

Ensure that a help page key exists in your AdapterResourceBundle for ADKGLOBAL.RESOURCEBUNDLEKEY_LISTRESOURCES, ADKGLOBAL.RESOURCEBUNDLEKEY_LISTCONNECTIONTYPES, ADKGLOBAL.RESOURCEBUNDLEKEY_LISTPOLLINGNOTIFICATIONS, ADKGLOBAL.RESOURCEBUNDLEKEY_LISTPOLLINGNOTIFICATIONDETAILS, and ADKGLOBAL.RESOURCEBUNDLEKEY_ABOUT.

FAC_ART+ART21 Error occurred while loading copyright for adapter type "{0}".
Class E
Explanation

Failed to read a third-party copyright file for the specified adapter.
Action

If you have explicitly specified ADKGLOBALS.RESOURCEBUNDLEKEY_THIRDPARTYCOPYRIGHTURL in the adapter's resource bundle, ensure that the file this key references is in the pub directory in the adapter's directory tree. Also ensure that this file is readable by Integration Server.

FAC_ART+ART22 Error in {0}. Missing or invalid parameter: {1}.
Class E
Explanation

A value was not specified for the parameter of the specified method.
Action

If you explicitly invoked the specified method, check your parameter values and resubmit. Otherwise, look in the error log for related errors.

FAC_ART+ART30 Unable to create node {0} in the namespace.
Class E
Explanation

WmART failed to create the specified connection or listener node in the namespace.
Action

The connection/listener information you provided in Integration Server Administrator is invalid, or perhaps duplicates an existing connection/listener in the same namespace. Refer to adjacent log entries for specifics.

FAC_ART+ART31 Unable to update node {0}. Package not found.
Class E
Explanation

WmART attempted to save changes to the specified namespace node, but could not determine its package.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART32 Unable to update resource {0}.
Class E
Explanation

An error occurred when updating a value in the specified namespace.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART33 Invalid folder name {0}.
Class E
Explanation

While creating a new connection node, a null folder name was passed to com.wm.pkg.art.util.ServiceHelper.checkInterfaceName.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART34 Unable to create folder {0}.
Class E
Explanation

WmART was unable to create the specified folder in the adapter's namespace.
Action

Ensure that the folder name conforms to naming conventions in your server's local file system, and that Integration Server has permissions to create folders under the packages folder. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART35 Unable to create record for {0}.
Class E
Explanation

An error occurred in ServiceHelper.createRecordFromBean while creating an NSRecord from the specified object. Adjacent log messages might contain additional details.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART36 Unable to create folder for service {0}.
Class E
Explanation

An error occurred in ServiceHelper.registerService while creating the file system infrastructure for the specified adapter service. Adjacent log messages might contain additional details.

Action

Ensure that the local operating system access permissions within the Integration Server packages folder will allow WmART to create folders and files dynamically.

FAC_ART+ART37 Unable to create service {0}.
Class E
Explanation

An error occurred in ServiceHelper.registerService while registering the adapter service. Adjacent log messages might contain additional details.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART38 Unable to create flow {0}.
Class E
Explanation

An error occurred in ServiceHelper.createFlowService. Adjacent log messages might contain additional details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART40 Unable to create interaction input record.
Class E
Explanation

An error occurred in RecordFactoryBridgeImpl.createInputRecord while creating a mapped Record. Adjacent log messages might contain additional details.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART41 Unable to create input record. createMappedRecord() returned {0}.
Class E
Explanation

A call to RecordFactory.createMappedRecord returned an object of the specified class rather than a WmRecord or IDataCodable object.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART42 Unable to convert interaction output record into IData. Output record is {0}.
Class E
Explanation

RecordFactoryBridgeImpl.createOutputData was passed an instance of the specified class rather than a WmRecord, IData, or IDataCodable instance.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART50 Unable to convert string to specific data type. The data type is not specified or the string value is null.
Class E
Explanation

While configuring a new connection or listener, WmART detected that the type or value of one of the connection's properties is null.

Action

Ensure that you enter values for all required properties. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART51 Unable to convert string to specific data type. Unsupported data type {0}.
Class E
Explanation

You omitted a value when configuring a connection or listener property from Integration Server Administrator.
Action

Reconfigure the connection/listener, entering valid values for all properties on the Integration Server Administrator page.
FAC_ART+ART53 Unable to convert string array to specific data type array. The data type is not specified.
Class E
Explanation

While configuring a new connection or listener, WmART detected that the type of a property array is null.
Action

This condition indicates a coding error in the adapter or the Adapter Runtime (WmART) itself. Ensure that the adapter is handling connection and listener properties correctly. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART54 Unable to convert string array to specific data type array. Unsupported data type {0}.
Class E
Explanation

The Adapter Runtime (WmART) has detected a property array in a connection or listener that has an unsupported data type.
Action

Change your connection/listener to use only supported data types for all properties.
FAC_ART+ART55 Unable to convert string array to data type {0} array.
Class E
Explanation

An unexpected property array conversion error has occurred while configuring a connection or listener.
Action

This might be due to invalid data in a property array on the Integration Server Administrator page, such as non-numeric data in a numeric property. Reconfigure the connection/listener to ensure that the entered data matches the expected data types for all properties.

FAC_ART+ART56 Unable to convert string array to primitive int array.
Class E
Explanation

A value has been entered in a connection or listener property array that cannot be converted to a Java int type.
Action

Reconfigure the connection/listener to ensure that the data entered conforms to the expected data types for all properties.
FAC_ART+ART57 Unable to convert string array to primitive long array.
Class E
Explanation

A value has been entered in a connection or listener property array that cannot be converted to a Java long data type.
Action

Reconfigure the connection/listener to ensure that the data entered conforms to the expected data types for all properties.
FAC_ART+ART58 Unable to convert string array to primitive float array.
Class E
Explanation

A value has been entered in a connection or listener property array that cannot be converted to a Java float type.
Action

Reconfigure the connection/listener to ensure that the data entered conforms to the expected data types for all properties.
FAC_ART+ART59 Unable to convert string array to primitive double array.
Class E
Explanation

A value has been entered in a connection or listener property array that cannot be converted to a Java double type.
Action

Reconfigure the connection/listener to ensure that the data entered conforms to the expected data types for all properties.
FAC_ART+ART60 Unable to convert string array to primitive boolean array.
Class E
Explanation

A value has been entered in a connection or listener property array that cannot be converted to a Java Boolean type.
Action

Reconfigure the connection/listener to ensure that the data entered conforms to the expected data types for all properties.
FAC_ART+ART61 Unable to convert string array to primitive short array.
Class E
Explanation

A value has been entered in a connection or listener property array that cannot be converted to a Java short type.
Action

Reconfigure the connection/listener to ensure that the data entered conforms to the expected data types for all properties.
FAC_ART+ART62 Unable to convert string array to primitive char array.
Class E
Explanation

A value has been entered in a connection or listener property array that cannot be converted to a Java char type.
Action

Reconfigure the connection/listener to ensure that the data entered conforms to the expected data types for all properties.
FAC_ART+ART63 Unable to convert string array to Integer array.
Class E
Explanation

A value has been entered in a connection or listener property array that cannot be converted to a Java integer instance.
Action

Reconfigure the connection/listener to ensure that the data entered conforms to the expected data types for all properties.
FAC_ART+ART64 Unable to convert string array to Long array.
Class E
Explanation

A value has been entered in a connection or listener property array that cannot be converted to a Java long instance.
Action

Reconfigure the connection/listener to ensure that the data entered conforms to the expected data types for all properties.
FAC_ART+ART65 Unable to convert string array to Float array.
Class E
Explanation

A value has been entered in a connection or listener property array that cannot be converted to a Java float instance.
Action

Reconfigure the connection/listener to ensure that the data entered conforms to the expected data types for all properties.
FAC_ART+ART66 Unable to convert string array to Double array.
Class E
Explanation

A value has been entered in a connection or listener property array that cannot be converted to a Java double instance.
Action

Reconfigure the connection/listener to ensure that the data entered conforms to the expected data types for all properties.
FAC_ART+ART67 Unable to convert string array to Boolean array.
Class E
Explanation

A value has been entered in a connection or listener property array that cannot be converted to a Java Boolean instance.
Action

Reconfigure the connection/listener to ensure that the data entered conforms to the expected data types for all properties.
FAC_ART+ART68 Unable to convert string array to Short array.
Class E
Explanation

A value has been entered in a connection or listener property array that cannot be converted to a Java short instance.
Action

Reconfigure the connection/listener to ensure that the data entered conforms to the expected data types for all properties.
FAC_ART+ART69 Unable to convert string array to Character array.
Class E
Explanation

A value has been entered in a connection or listener property array that cannot be converted to a Java character instance.
Action

Reconfigure the connection/listener to ensure that the data entered conforms to the expected data types for all properties.
FAC_ART+ART72 Unable to set JavaBean properties.
Class E
Explanation

WmART has detected an error while setting the properties on a listener or listener notification bean.
Action

Ensure that the adapter's listener and listener notification implementations adhere to the JavaBean standard.
FAC_ART+ART73 Unable to set property {0} to value {1} on class {1}.
Class E
Explanation

WmART failed to set the specified property on the specified (bean) class because it could not introspect the class.
Action

Ensure that the adapter's service template implementations adhere to the JavaBean standard. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART74 Property {0} not found in class {1}.
Class E
Explanation

After introspecting the specified class, WmART failed to find the specified property in that class.
Action

Ensure that the adapter's service template implementations support the JavaBean standard. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART75 Unable to set property descriptor.
Class U
Explanation

WmART failed to introspect an unspecified bean.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART76 Unable to set {0} to {1} because property is not writable.
Class E
Explanation

WmART was unable to locate the "set" method for the specified property on a bean class. The property appears to be read only.
Action

Ensure that the adapter's service template implementations support the JavaBean standard. To make the specified property writable, implement a "set" method for it.

FAC_ART+ART77 Error while setting property {0} of class {1} to {2}.
Class E
Explanation

An error occurred while setting the specified property on the specified class instance.
Action

Ensure that the adapter's service template implementations support the JavaBean standard. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART78 Unable to get JavaBean properties for {0}.
Class E
Explanation

An error occurred while reading the properties from the specified bean class.
Action

Ensure that the adapter's service template implementations support the JavaBean standard. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART81 Unable to create instance of {0}.
Class E
Explanation

WmART was unable to create a new instance of the specified class.
Action

Ensure that the adapter's service and notification template implementation classes expose a default public constructor and are not abstract. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART82 Unable to get JavaBean property {0} of class {1}.
Class E
Explanation

WmART failed to determine or invoke the "get" method for the property in the specified class.
Action

Ensure that the adapter's service template implementations support the JavaBean standard. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART83 Exception encountered attempting to load fix information for adapter type {0}.
Class E
Explanation

The Adapter Runtime (WmART) failed while attempting to load the installed update information for the adapter.
Action

This error is generated when an exception is caught during execution. Check the error logs for information on the original exception.

FAC_ART+ART84 Missing or invalid value. {0} is not a valid value for field {1}.
Class E
Explanation

An error occurred while validating the common values for a connection pool. The common values are settings, such as, Minimum Pool Size, Maximum Pool Size, etc.

Action

Change the invalid value. Then attempt to save and enable your connection.
FAC_ART+ART201 Unable to introspect "{0}". This service introspects the parameters of connection only.
Class E
Explanation

WmART failed to create a WmManagedConnectionFactory instance from the specified class name. The current WmART implementation does not allow this condition to occur.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART202 Failure when introspecting the connection properties.
Class E
Explanation

An error occurred while introspecting connection properties. Additional details are logged.
Action

Check adjacent log messages for specific error details. Correct any problems with your connection metadata. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART203 Unable to introspect "{0}"
Class E
Explanation

The Adapter Runtime (WmART) failed to create an instance of an adapter service, notification, or listener from the specified class name.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART204 Unable to introspect the parameters of service template.
Class E
Explanation

An error occurred while attempting to introspect a template or listener. Additional details are logged.
Action

Ensure that the adapter's implementation .class files are installed properly under the packages folder. If you modify the .class files for the adapter while the Integration Server is running, you must reload that adapter.

FAC_ART+ART205 Unable to lookup the resource domain values.
Class E
Explanation

This is a general processing error message. Details should appear in adjacent log messages.
Action

Refer to the Action column for the accompanying messages.
FAC_ART+ART206 Connection alias was not specified in "{0}".
Class E
Explanation

The connection, adapter, or listener could not be found in the request to the specified method.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART207 The connection alias "{0}" does not support webMethods metadata extensions. The adapter could be a third-party adapter.
Class E
Explanation

The specified connection alias is not derived from com.wm.adk.cci.connection.WmConnection.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART208 The connection alias "{0}" isn't configured or failed.
Class E
Explanation

WmART failed to create a ConnectionDataNode instance based on the specified connection alias.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART209 Cannot get the connection instance of connectionAlias "{0}".
Class E
Explanation

An error occurred while creating a WmConnection instance from the specified connection alias. Additional details are provided in adjacent log messages.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART213 Cannot get the listener instance of listenerNode "{0}".
Class E
Explanation

The method getListenerAdapterMetadata in com.wm.pkg.art.metadata.ConnectionMetadataService failed to locate and create a listener object for the specified listener node.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART216 Unable to validate the resource domain value.
Class E
Explanation

An error occurred while validating a resource domain. This is a general processing error message. Details should appear in adjacent log messages.

Action

Refer to the Action column for the accompanying messages.
FAC_ART+ART218 Failure when introspecting the parameters of the notification listener.
Class E
Explanation

WmART failed to lookup a resource domain. Additional details should appear in adjacent log messages.
Action

Ensure that the adapter's implementation(s) of WmNotification.fillWmTemplateDescriptor sets resource domains correctly.
FAC_ART+ART219 Failure when validating the resource domain "{0}". Null checkValues returned.
Class E
Explanation

WmART was unable to locate internal check values for the specified resource domain.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART220 Error occurred when closing the connection handle.
Class E
Explanation

An error occurred when closing a connection. Additional details are logged.
Action

Ensure that the connection is configured properly and is able to communicate with the back-end resource. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART221 No adapter type name specified in "{0}".
Class E
Explanation

The specified method in com.wm.pkg.art.metadata.ConnectionMetadataService failed to retrieve connection metadata because no adapter name was provided.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART222 No class name of WmManagedConnectionFactory specified in "{0}".
Class E
Explanation

The specified method in com.wm.pkg.art.metadata.ConnectionMetadataService failed to retrieve connection metadata because no connection factory class name was provided.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART225 Cannot get the connection handle of "{0}".
Class E
Explanation

WmART failed to create a WmConnection instance based on the specified connection alias.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART226 No class name of service template specified in "{0}".
Class E
Explanation

The specified method failed to retrieve metadata from an adapter template, notification template, or listener because no service class was provided in the request.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART227 No resource domain name specified in "{0}".
Class E
Explanation

The specified method failed because no resource domain was provided in the request.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART228 No statement specified in "{0}".
Class E
Explanation

The specified method in com.wm.pkg.art.metadata.InteractionMetadataService failed because the AdapterRuntimeGlobals.STATEMENT value was not provided in the request.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART230 Unable to get the list of service template metadata.
Class E
Explanation

The method getInteractionAdapterMetadataList in com.wm.pkg.art.metadata.InteractionMetadataService failed because the list of service templates supported by a connection was not provided in the request.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART231 Unable to get the list of notification template metadata.
Class E
Explanation

An error occurred in com.wm.pkg.art.metadata.InteractionMetadataService.getNotificationAdapterMetadataList. This is a general processing error message. Details should appear in adjacent log messages.

Action

Refer to the Action column for the accompanying messages.
FAC_ART+ART232 Unable to get the adapter type "{0}".
Class E
Explanation

The method getConnectionAdapterMetadata in com.wm.pkg.art.metadata.ConnectionMetadataService was unable to create a WmAdapterType instance using the specified adapter name.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART233 Unable to get the connection type "{0}".
Class E
Explanation

The method getConnectionAdapterMetadata in com.wm.pkg.art.metadata.ConnectionMetadataService was unable to create a connection factory using the specified class name.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART234 Unable to get a connection for resource "{0}".
Class E
Explanation

WmART failed to create a WmConnection instance based on the specified connection alias.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART235 Error in {0}. Missing parameter: {1}.
Class E
Explanation

The method in com.wm.pkg.art.metadata.InteractionMetadataService failed to retrieve notification metadata because the specified request parameter was missing.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART236 The connectionAlias or listenerNodeName must be specified.
Class E
Explanation

The method in com.wm.pkg.art.metadata.InteractionMetadataService failed to lookup/validate notification values because neither the connection node alias nor the listener node was provided in the request.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART237 Value for parameter missing: {0}.
Class E
Explanation

The operation input requires the metadata parameter listed in the message text, but the value was not provided.
Action

Add the metadata property and a value to the operation inputs and resubmit.
FAC_ART+ART238 Value for parameter {0} does not match data type {1}.
Class E
Explanation

The value submitted with the operation input does not match the metadata parameter listed in the message text.
Action

Change the type of the value for the operation and resubmit.
FAC_ART+ART239 Number of fields does not match number of types in a record definition.
Class E
Explanation

The operation input requires a field type and a field name for each output field specification.
Action

Ensure that the number of entries in the array of values for the field names and field types are equal and resubmit.
FAC_ART+ART240 Parameter missing: {0}.
Class E
Explanation

The operation input is missing the required parameter listed in the message text.
Action

Ensure that the input contains an entry for the parameter and resubmit.
FAC_ART+ART241 Unrecognized parameter {0} specified.
Class E
Explanation

The operation input contains the parameter listed in the message text, which is not defined for this template.
Action

Remove the parameter from the operation input and resubmit.
FAC_ART+ART242 Required parameter "{0}" is missing, or has no value.
Class E
Explanation

The operation is missing a required parameter.
Action

Provide the missing parameter value, and resubmit the operation.
FAC_ART+ART243 Failed to run {0} service. Details provided in error log.
Class E
Explanation

An exception was caught while executing the service.
Action

Look in the error log for details on the original exception.
FAC_ART+ART244 Resource domain "{0}" is not recognized by providor "{1}".
Class E
Explanation

The specified resource domain is not registered for the template.
Action

This error should only be encountered while using the webMethods ADK for adapter development. If you are developing an adapter, ensure that the specified resource domain is registered for your template. If you are not developing an adapter, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART245 Failed to update IO properties in template "{0}"
Class E
Explanation

An exception was caught while updating IO properties in the specified template.
Action

Look in the error log for details on the original exception.
FAC_ART+ART300 Unable to start transaction {0}.
Class
Explanation

An error occurred during the initiation of a transaction.
Action

Make sure that there is connectivity to the adapter backend, and that the connection associated with the transaction is enabled.
FAC_ART+ART301 Unable to commit transaction. A transaction name must be specified.
Class E
Explanation

WmART failed to determine the name of a transaction.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART302 Error while committing transaction {0}. The transaction in progress is {1}.
Class E
Explanation

The transaction name does not match the specified connection state.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART303 Unable to commit transaction.
Class E
Explanation

An error occurred while committing a transaction.
Action

If the adapter uses a connection that supports LocalTransaction, ensure that it is implemented properly. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART304 Unable to rollback transaction. A transaction name must be specified.
Class E
Explanation

WmART failed to determine the name of a transaction.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART305 Error while rolling back transaction {0}. The transaction in progress is {1}.
Class E
Explanation

The specified transaction name does not match the specified connection state.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART306 Unable to rollback transaction.
Class E
Explanation

An error occurred while committing a transaction.
Action

If the adapter uses a connection that supports LocalTransaction, ensure that it is implemented properly. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART307 Retryable Error during commit transaction.
Class E
Explanation

An unexpected system error occurred while committing a transaction. The transaction can be re-tried.
Action

Ensure that the back-end resource for the transaction can be reached from the server and is in a valid state. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART350 Unable to set transaction timeout to {0} seconds.
Class E
Explanation

WmART has detected that an XAResource failed to set the transaction timeout to the specified number of seconds.
Action

Verify that the back-end resource for the transaction can be reached from the server and is in a valid state. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART351 Unable to create Transaction Manager.
Class E
Explanation

WmTransactionManagerFactory failed to create a TransactionManager.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART352 Unable to create Transaction Manager with transaction timeout set to {0} seconds.
Class E
Explanation

WmTransactionManagerFactory failed to create a TransactionManager with the specified number of timeout seconds.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART353 Unable to set transaction timeout. Invalid timeout value {0}.
Class E
Explanation

com.wm.pkg.art.transaction.Service.setTransactionTimeout could not cast the specified object to type Integer.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART700 Errors occurred in cluster coordination repository access for {0}.
Class E
Explanation

An exception was caught during processing.
Action

Look in the error log for details on the original exception.
FAC_ART+ART701 Unable to retrieve ART instance/session ID.
Class E
Explanation

The Adapter Runtime (ART) session ID failed to initialize.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART702 Errors occurred attempting to stop {0}. See error log for details.
Class E
Explanation

An exception was caught when attempting to stop the notification.
Action

Look in the error log for details on the original exception.
FAC_ART+ART703 Errors occurred attempting to confirm cluster member. See error log for details.
Class E
Explanation

An exception was caught trying to validate Adapter Runtime (ART) cluster members.
Action

Look in the error log for details on the original exception.
FAC_ART+ART704 Internal Error-assert failed - node: {0}, detail:{1}.
Class E
Explanation

An unexpected exception occurred during processing.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, error logs with the stack trace exposed, and the detail in this error message.

FAC_ART+ART705 Errors occurred attempting to start {0}. See error log for details.
Class E
Explanation

An exception was caught when attempting to start the notification.
Action

Look in the error log for details on the original exception.
FAC_ART+ART707 "{0}" is an invalid setting for the cluster coordination mode of {1}. Valid values: {2}.
Class E
Explanation

An unsupported mode was encountered.
Action

Change the mode to one of the supported settings, and restart the notification.
FAC_ART+ART708 {0} is an invalid setting for max process time of {1}. Value must be an number between {2} and {3}.
Class E
Explanation

An invalid maximum process time was encountered for the notification.
Action

Change the maximum process time to a value within the specified range, and restart the notification.
FAC_ART+ART709 {0} is an invalid setting for max setup time of {1}. Value must be an number between {2} and {3}.
Class E
Explanation

An invalid maximum setup time was encountered for the notification.
Action

Change the maximum setup time to a value within the specified range, and restart the notification.
FAC_ART+ART710 Adapter cluster properties files are not the same across the cluster. Please synchronize all cluster properties files and restart servers.
Class E
Explanation

The Adapter Runtime encountered inconsistent cluster property files.
Action

Ensure the cluster property files are the same for the adapter on each clustered Integration Server.
FAC_ART+ART711 Notification {0} was unexpectedly removed from cluster.
Class E
Explanation

Another instance of this notification erroneously determined that this current instance failed. The current instance was removed.
Action

Check the logs on other servers in the cluster. A log on one of the servers will include message 1405, which indicates that this instance was removed. Check clock synchronization and network connectivity between the two servers.

FAC_ART+ART712 Operation failed because notification {0} was unexpectedly removed from cluster.
Class E
Explanation

Another instance of this notification erroneously determined that this current instance failed. The current instance was removed. Note that this error is similar to ART.0114.0711E; however, in this case the node was changing states.

Action

Check the logs on other servers in the cluster. A log on one of the servers will include message 1405, which indicates that this instance was removed. Check clock synchronization and network connectivity between the two servers.

FAC_ART+ART1004 Parameter parsing error.
Class E
Explanation

WmART attempted to encrypt or decrypt a null string value.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART1005 Parameter parsing error.
Class E
Explanation

WmART failed to encrypt a string value.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART1006 Parameter parsing error.
Class E
Explanation

WmART failed to decrypt a string value.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART1008 Jar file {0} is not an update jar file. Unable to read the {1} entry.
Class D
Explanation

This message applies to adapters that use update jar files to deliver updates. The update.cnf file is not readable in the update jar file.

Action

No action is required.
FAC_ART+ART1009 Jar file {0} is not an update jar file. It does not contain the {1} entry.
Class D
Explanation

This message applies to adapters that use update jar files to deliver updates. The update.cnf file is missing from the update jar file.

Action

No action is required.
FAC_ART+ART1010 File {0} is not an update file. It is not a jar file.
Class D
Explanation

This message applies to adapters that use update jar files to deliver updates. A file was found in the adapters update directory that is not a jar file.

Action

No action is required.
FAC_ART+ART1011 Error initializing UpdateFile. Missing required parameter.
Class D
Explanation

This message applies to adapters that use update jar files to deliver updates. A null value was supplied for the file name parameter. A value is required.

Action

No action is required.
FAC_ART+ART1012 No updates found for adapter: {0}.
Class D
Explanation

No installed updates were found for the adapter.
Action

No action is required.
FAC_ART+ART1013 Unable to locate the package name for adapter: {0}.
Class E
Explanation

The Integration Server package name for the adapter could not be determined.
Action

Ensure the adapter package depends on the WmART package, and reload the adapter package.
FAC_ART+ART1014 Adapter {0} is missing required fix {1}.
Class W
Explanation

This message applies to adapters that use update jar files to deliver updates. A fix required by the adapter was not found.
Action

Install the required fix, and reload the adapter.
FAC_ART+ART1015 Error loading update jar file {0}. An exception was encountered loading the {1} file.
Class E
Explanation

This message applies to adapters that use update jar files to deliver updates. An exception occurred trying to load the update.cnf file in the update jar.

Action

Look in the error log for details on the original exception.
FAC_ART+ART1016 Error loading update jar file {0}. The {1} file is missing the required property updateName.
Class E
Explanation

This message applies to adapters that use update jar files to deliver updates. The update.cnf file associated with the fix is missing a required value.

Action

Re-apply the fix, and reload the adapter.
FAC_ART+ART1017 Error loading update jar file {0}. The update name contains the illegal character ';'.
Class E
Explanation

This message applies to adapters that use update jar files to deliver updates. The fix name in the update.cnf file contains an illegal semicolon (;) character.

Action

Re-apply the fix, and reload the adapter.
FAC_ART+ART1018 Error loading update information. The '{0}' tag is missing.
Class E
Explanation

The fix name is missing.
Action

Re-apply the fix, and reload the adapter.
FAC_ART+ART1019 Illegal value is set for page size in watt.art.page.size - "{0}".
Class E
Explanation

An invalid value was specified for the watt.art.page.size parameter. This parameter must be a positive integer greater than or equal to 1.

Action

Set the value of watt.art.page.size to an integer greater than or equal to 1.
FAC_ART+ART1020 Error while storing/retrieving/removing the password for the connection "{0}".
Class
Explanation

An error occurred while storing, retrieving or removing the password for the connection from the Integration Server passman store. The error can occur when creating, updating, or deleting an adapter connection respectively.

Action

Make sure that the latest fix is installed on Integration Server. Try to restart Integration Server and perform the operation again. Also, make sure that the package containing the connection is imported properly into Integration Server.

FAC_ART+ART1103 Facility {0} - {1} error. Log handler not found.
Class E
Explanation

WmART failed to get a Log Handler from the Integration Server for the specified facility.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART1105 No LogProducer for facility {0} - {1}.
Class E
Explanation

WmART attempted to log a message, but no Log Producer exists for the specified facility.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART1106 Facility {0} - {1} error. No facilities registered.
Class E
Explanation

WmART failed to get the list of facility codes from the Log Handler.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART1112 Unable to instantiate class {1} in adapter {0}. See error log for details.
Class E
Explanation

An exception occurred trying to instantiate a template for the adapter.
Action

Ensure package dependencies are set correctly, and reload the adapter
FAC_ART+ART1113 Class {0} is not a Service or Notification template class.
Class E
Explanation

An invalid class was registered as a template.
Action

If you are using the webMethods ADK to develop an adapter, ensure your class is properly registered and coded to be a template. If this message is being issued from a webMethods adapter, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART+ART1401 Coordination data for {0} is invalid. Coordination will revert to a default state.
Class W
Explanation

Coordination data in the repository was not valid. If the server was recently upgraded, this might simply represent a change in record formats, and the operation you are performing will automatically correct the data for you. If you have not recently upgraded or the problem persists, it is likely that the repository is corrupted.

Action

If you recently performed a server upgrade, no action is required. If you have not recently upgraded or the problem persists, check repository logs for errors.

FAC_ART+ART1405 Processing for {0} on server {1} has timed-out or failed. Local instance will take over.
Class W
Explanation

Remote failure detected.
Action

Check logs on indicated server for messages ART.0114.0711E or ART.0114.0712E. If the messages are in the log, refer to those error messages for a resolution. If the messages do not appear in the logs, no action is required.

FAC_ART+ART1407 Illegal overlap occurred in node {0}. Please verify clock synchronization with cluster member '{1}'
Class W
Explanation

An illegal overlap exception was detected.
Action

Ensure the clocks are synchronized for all Integration Servers in the cluster.
FAC_ART+ART1411 Unable to access {0} file for adapter "{1}". Please check the file permissions. Running with default configuration.
Class E
Explanation

The cluster property file could not be read.
Action

Ensure the cluster property file exists and is readable for the specified adapter.
FAC_ART+ART1412 Unable to parse {0} file for adapter "{1}". Please correct file format. Running with default configuration.
Class E
Explanation

The cluster property file could not be parsed.
Action

Validate the cluster property file format for the specified adapter.
FAC_ART+ART1415 An internal error occurred while rendering cluster settings for adapter {0}. Updated settings will not be persisted.
Class E
Explanation

The settings could not be saved to the cluster property file.
Action

Ensure the directory and the cluster file are writable.
FAC_ART+ART1416 Error attempting to save cluster settings for adapter {0}. Error {1}
Class E
Explanation

An exception occurred trying to save the cluster settings.
Action

Look in the error log for details on the original exception.
FAC_ART+ART1418 Illegal overlap occurred in node {0}. Please increase setup timeout. Current setting: {1}, actual time: {2} seconds
Class W
Explanation

The requested operation took longer than the allotted time; the operation had no other errors.
Action

Increase the node's timeout value as indicated by the actual time.
FAC_ART+ART1419 Illegal overlap occurred in node {0}. Please increase execute timeout. Current setting: {1}, actual time: {2} seconds
Class W
Explanation

A polling operation took longer than the allotted time; the polling operation had no other errors.
Action

Increase the node's timeout value as indicated by the actual time.
FAC_NOTIFICATION+ANOT3139 EventType Definition doesnt exists in the EventTypeStore for notification : {0}.
Class E
Explanation

Event Type Definition is not present in the same namespace for the notification in the Event Type Store.
Action

Create an event type definition for the notification and manually copy it to the Event Type Store.
FAC_LISTENER+ALIS3202 Listener error releasing connection for {0}. Error: {1}.
Class E
Explanation

An error occurred while closing the connection associated with the specified listener.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3203 Error creating listener object: Null argument on init call.
Class E
Explanation

The method WmNotificationListener.initListenerNodeProperties was passed a null ListenerNode instance.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3204 Error creating listener object: NSName null.
Class E
Explanation

The method WmNotificationListener.initListenerNodeProperties was unable to derive the name of a listener node from the ListenerNode instance.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3207 Illegal event type received: {0}.
Class E
Explanation

The method WmNotificationListener.doNotify was passed the specified invalid event ID.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3208 Error during listener event. Error: {0}.
Class E
Explanation

An error occurred while processing a listener event. Refer to the error message text for more details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3209 Error creating listener object {0}. Error: {1}.
Class E
Explanation

An error occurred creating the specified listener or initializing its properties.
Action

Ensure that the listener and its properties are configured correctly. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3211 Existing transaction rolled back before execution of {0}.
Class E
Explanation

WmART detected an incomplete transaction for the specified listener prior to executing it. The transaction has been rolled back.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3212 Listener error during execution of {0}. Error: {1} rolling back existing transaction.
Class E
Explanation

WmART detected an incomplete transaction for the specified listener prior to executing it. WmART attempted to rollback the transaction, but failed. Refer to the error message text for more details.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3213 Listener error during execution of {0}. Error: {1} checking transaction.
Class E
Explanation

WmART failed to determine whether the specified listener has an open transaction. Refer to the error message text for more details.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3214 Listener {0} not Found.
Class E
Explanation

WmART failed to lookup the specified listener.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3215 Unable to create listener {0}. Listener node already exists.
Class E
Explanation

There was an attempt to create a duplicate listener node.
Action

Enter a new listener node name that is unique to its folder.
FAC_LISTENER+ALIS3217 Error creating listener object: {0}. Invalid package name: {1}.
Class E
Explanation

ListenerManager.createListener failed to create an instance of the listener because it could not find the package name in the pipeline.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3218 Error creating listener object: {0}. Invalid node name.
Class E
Explanation

ListenerManager.createListener failed to create an instance of the listener because the specified node name is missing or invalid.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3219 Error creating listener object: {0}. Error: {1}.
Class E
Explanation

An error occurred while creating the listener. This might be due to an invalid listener node name. Refer to the error message text for more details.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3220 Unable to get list of listener types supported by node {0}.
Class E
Explanation

An error occurred in ListenerManager.queryListenerTemplatesSupported for the specified adapter. See adjacent error messages for additional details.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3221 Unable to get listener node properties {0}.
Class E
Explanation

An error occurred while querying the specified listener's properties. See adjacent error messages for additional details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3223 Unable to update listener {0}: Error: {1}.
Class E
Explanation

An error occurred while updating the specified listener's properties. See adjacent error messages for additional details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3225 Unable to delete listener {0}: Error: {1}.
Class E
Explanation

An error occurred while deleting the specified listener. See adjacent error messages for additional details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3226 Unable to copy listener {0}: Error: {1}.
Class E
Explanation

An error occurred while copying the specified listener. See adjacent error messages for additional details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3227 Unable to copy listener. Error: Source nodeName is required.
Class E
Explanation

The method ListenerManager.copyAdapterListener failed because the source listener node name was not present in the pipeline.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3228 Unable to copy listener {0}. Error: newNodeName is required.
Class E
Explanation

The method ListenerManager.copyAdapterListener failed because the destination listener node name was not present in the pipeline.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3229 Unable to copy listener {0}. Error: publishableDocumentName is required.
Class E
Explanation

The method ListenerManager.copyAdapterListener failed because the destination listener publishable document name was not present in the pipeline.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3230 Unable to copy listener {0}. Error: newPkg is required.
Class E
Explanation

The method ListenerManager.copyAdapterListener failed because the destination listener node package name was not present in the pipeline.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3231 Unable to copy listener {0} to {1}. Error: Unable to get source listener node.
Class E
Explanation

The method ListenerManager.copyAdapterListener failed because the source listener node name is invalid.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3232 Unable to copy listener {0}. Error: New name already exists {1}.
Class E
Explanation

The method ListenerManager.copyAdapterListener failed because the specified destination listener node name already exists in the package.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3235 Unable to rename listener {0}. Error: {1}.
Class E
Explanation

An error occurred while renaming the specified listener. See adjacent error messages for additional details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3236 Unable to find listener {0}.
Class E
Explanation

The method ListenerManager.queryListenerStatistics failed because it could not locate the specified listener node.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3237 Unable to get listener {0}. Error: Listener class name is not specified.
Class E
Explanation

The method ListenerNode.getListener failed because it could not locate the WmConnectedListener implementation class name.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3238 Error in Listener Callback:{0} notification {1}.
Class E
Explanation

An error occurred while processing a listener notification event for the specified listener. If there is a callback name in the error message, it corresponds to the notification event.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3239 Missing required parameter on service: {0}
Class E
Explanation

The specified parameter is not present in the pipeline. This is an internal error.
Action

Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3240 Unable to retrieve listener data. No listener name specified.
Class E
Explanation

The method ARTAdmin.retrieveListenerData failed because no listener was present in the pipeline.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3241 Error retrieving listener: {0}. Error: {1}
Class E
Explanation

An error occurred while retrieving information about the listener. Refer to the error text for more details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3242 Unable to get listener properties for adapter: {0}, listener type: {1}.
Class E
Explanation

An error occurred while retrieving properties of the listener in the specified adapter.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3243 Error retrieving listeners. Missing parameter: {0}
Class E
Explanation

The method ARTAdmin.retrieveListeners failed because the adapter name was not present in the pipeline.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3244 Error setting listener status. Missing parameter: {0}
Class E
Explanation

The method ARTAdmin.setListenerStatus failed because the listener name was not present in the pipeline.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3245 Error retrieving listener types. Missing parameter: {0}
Class E
Explanation

The method ARTAdmin.retrieveListenerTypes failed because the adapter name was not present in the pipeline.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3246 Error retrieving listener types. Error: {0}
Class E
Explanation

An error occurred while retrieving the listener types supported by an adapter. Refer to the error text for more details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3247 Error deleting listener. Missing parameter: {0}
Class E
Explanation

The method ARTAdmin.deleteListener failed because the listener name was not present in the pipeline.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3248 Error deleting listener: {0}. Unable to find the node.
Class E
Explanation

The method ARTAdmin.deleteListener failed because the specified listener node name is invalid.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3249 Error deleting listener: {0}.
Class E
Explanation

An error occurred while deleting the specified listener. See adjacent error messages for additional details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3250 Error setting properties for listener: {0}.
Class E
Explanation

An error occurred while setting the properties of the specified listener. See adjacent error messages for additional details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3251 Invalid listener node name: {0}.
Class E
Explanation

The specified listener name is missing or invalid.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3252 Unable to commit transaction for listener {0}. Error: {1}.
Class E
Explanation

WmNotificationListener failed to commit a transaction for the specified listener. Refer to the error text for more details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3253 Listener {0} did not process notification.
Class E
Explanation

The listener received a notification and was unable to find a listener notification to process it.
Action

Check to ensure that the listed listener has listener notifications registered with it and that at least one of them is enabled.
FAC_LISTENER+ALIS3255 Unable to start listener: {0}. Cannot retrieve connection from connection node: {1}
Class E
Explanation

The listener requires a connection to start. The startup processing could not get a connection from the listed connection node.

Action

Check to ensure that the listed connection is enabled. If the connection is pooled, increase the maximum connections allowed in the pool.

FAC_LISTENER+ALIS3256 Unable to start listener: {0}. Error: {1}
Class E
Explanation

An unexpected exception occurred while trying to enable a notification.
Action

Check the Integration Server error log for details on the unexpected exception.
FAC_LISTENER+ALIS3257 Exceeded max retries. Shutting down listener {0}. Error: {1}
Class E
Explanation

A retryable error occurred while attempting to execute the listener. The maximum number of retries is exceeded.
Action

Check the Integration Server error log for details on the retryable exception. Correct the error and try to enable the listener.
FAC_LISTENER+ALIS3258 Fatal error in listener {0}. See error log for details
Class E
Explanation

An unexpected exception occurred during listener operation.
Action

Check the Integration Server error log for details on the unexpected exception.
FAC_LISTENER+ALIS3259 Unable to enlist connection transactional resource
Class E
Explanation

An unexpected exception occurred while trying to start a transaction within the listener.
Action

Check the Integration Server error log for details on the unexpected exception. If no related exceptions are found, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_LISTENER+ALIS3260 Unable to commit transaction for listener {0}. Listener disabled
Class E
Explanation

An unexpected exception occurred while trying to commit a transaction within the listener.
Action

Check the Integration Server error log for details on the unexpected exception.
FAC_LISTENER+ALIS3261 Connection Node {0} not enabled.
Class E
Explanation

An error occurred while trying to retrieve a connection for the listener.
Action

Check to ensure the connection is enabled and restart the listener.
FAC_LISTENER+ALIS3262 Fatal error initiating transaction in listener {0}. See error log for details
Class E
Explanation

An unexpected exception occurred while trying to start a transaction within the listener.
Action

Check the Integration Server error log for details on the unexpected exception.
FAC_LISTENER+ALIS3263 Connection error while retrieving metadata in listener {0}. See error log for details
Class E
Explanation

An error occurred while trying to retrieve a connection for the listener.
Action

Check to ensure the connection is enabled. Check the Integration Server error log for more information about the connection error.

FAC_LISTENER+ALIS3264 Unable to stop listener: {0}. Error: {1}
Class E
Explanation

An unexpected exception occurred while trying to stop the listener.
Action

Check the Integration Server error log for details on the unexpected exception.
FAC_LISTENER+ALIS3265 Errors occurred. {0} listeners were not suspended. See error log for details.
Class E
Explanation

While attempting to suspend all listeners, some of the listeners reported errors.
Action

Look in the error log for details on the specific exceptions.
FAC_LISTENER+ALIS3266 Errors occurred. {0} listeners were not enabled. See error log for details.
Class E
Explanation

While attempting to enable all suspended listeners, some of the listeners reported errors.
Action

Look in the error log for details on the specific exceptions.
FAC_LISTENER+ALIS3267 Cannot update adapter-defined settings in suspended listener {0}.
Class E
Explanation

The user attempted to update adapter-defined settings for a listener; however, the listener is currently suspended.
Action

Disable the listener, and retry the operation.
FAC_LISTENER+ALIS3268 {0} is in an invalid state for requested operation.
Class E
Explanation

The user attempted an operation on a listener; however, the listener was not in the proper state for the operation.
Action

Change the state of the listener to an acceptable state, and retry the operation.
FAC_LISTENER+ALIS3269 Unable to complete update. Setting connection for listener {0} is not supported.
Class E
Explanation

The user attempted to change the connection associated with a listener; however, the listener does not require a connection.
Action

This operation is not supported.
FAC_LISTENER+ALIS3270 Unable to create listener. Setting connection for listener type {0} is not supported.
Class E
Explanation

The user attempted to create a listener with a connection; however the listener does not require a connection.
Action

This operation is not supported.
FAC_LISTENER+ALIS3271 Unable to create listener. Must specify connection for listener type {0}.
Class E
Explanation

A user attempted to create a listener that requires a connection; however no connection was specified.
Action

Specify a connection, and retry the operation.
FAC_LISTENER+ALIS3272 Unable to identify adapter for listener type {0}.
Class E
Explanation

Integration Server cannot determine the adapter associated with the specified listener type.
Action

Ensure your package dependencies are set properly. Reload the adapter package, and retry the operation.
FAC_LISTENER+ALIS3712 Error during listener execution.
Class E
Explanation

Either a fatal error has occurred while executing a listener, or the maximum number of non-fatal errors has been exceeded while executing a listener.

Action

Ensure that the connection from the listener to the back-end EIS is still valid, and that a communications path between them exists.

FAC_LISTENER+ALIS3716 Failed to retrieve connection for callback in listener {0}. Error: {1}
Class W
Explanation

An error occurred while trying to retrieve a connection for the listener shutdown callback processing.
Action

Check to ensure the connection is enabled. Check the Integration Server error log for details on the unexpected exception.
FAC_LISTENER+ALIS3717 Failure in shutdown callback in listener {0}. Error: {1}
Class W
Explanation

An error occurred during the listener shutdown callback processing.
Action

Details on the error are included in the message. The shutdown will attempt to continue.
FAC_NOTIFICATION+ANOT3001 Notification error during execution of {0}. Error: {1}.
Class E
Explanation

An error occurred while executing the specified notification. Refer to the text in the error message for additional details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3002 Notification error releasing connection for {0}. Error: {1}.
Class E
Explanation

WmART failed to release the specified notification's connection back to the connection pool.
Action

For custom adapters, check the connection's implementation for possible blocking situations. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3003 Error creating notification object: Null argument on init call.
Class E
Explanation

The method WmNotification.initNotificationNodeProperties failed because it was passed a null NotificationNode object.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3004 Error creating notification object: NSName null.
Class E
Explanation

The method WmNotification.initNotificationNodeProperties failed because it was unable to get the node name from the NotificationNode object.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3005 Error creating notification object: {0}. Publishable Document name not set.
Class E
Explanation

The method WmNotification.initNotificationNodeProperties failed because it was unable to get the publishable document node name for the specified notification.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3006 Error creating notification object: {0}. UUID not set.
Class E
Explanation

The method WmNotification.initNotificationNodeProperties failed because it was unable to get the specified notification's universal unique identifier (UUID) from the NotificationNode object.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3007 Illegal event type received: {0}.
Class E
Explanation

The method WmNotification.notifyEvent was passed the specified invalid event ID.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3008 Error during notification event. Error: {0}.
Class E
Explanation

An error occurred in the method WmNotification.notifyEvent. Refer to the error message text for more details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3009 Error creating notification object {0}. Error: {1}.
Class E
Explanation

An error occurred in the method NotificationNode.getNotification while creating the notification. Refer to the error message text for more details.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3010 Error publishing notification {0}. Error: {1}.
Class E
Explanation

An error occurred in the method WmAsynchronousNotification.publishToDispatcher while publishing a non-duplicate document from the specified notification. Refer to the error message text for more details.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3011 Existing transaction rolled back before execution of {0}.
Class E
Explanation

WmART detected an incomplete transaction for the notification prior to processing a notification event. The transaction has been rolled-back.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3012 Notification error during execution of {0}. Error: {1} rolling back existing transaction.
Class E
Explanation

WmART detected an incomplete transaction for the specified notification prior to processing a notification event. It attempted to rollback the transaction, but failed. Refer to the error message text for more details.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3013 Notification error during execution of {0}. Error: {1} checking transaction.
Class E
Explanation

WmART failed to determine whether the specified notification has an open transaction. Refer to the error message text for more details.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3014 Notification {0} not Found.
Class E
Explanation

WmART failed to locate the specified notification.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3015 Unable to create notification {0}. Notification node already exists.
Class E
Explanation

WmART failed to create the specified notification because a notification with this name already exists.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3016 Unable to create publishable document {0}. Error: {1}.
Class E
Explanation

The method NotificationFactory.createPublishableDocument failed to create a document for the specified notification. Refer to the error message text for more details.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3018 Error creating notification object: {0}. Invalid node name.
Class E
Explanation

The specified notification node name is missing or improperly formatted.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3019 Error creating notification object: {0}. Error: {1}.
Class E
Explanation

An error occurred while creating the specified polling or listener notification. Refer to the error message text for more details.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3020 Unable to get list of notification types supported by node {0}.
Class E
Explanation

An error occurred in NotificationManager.queryNotificationTemplatesSupported for the specified adapter. See adjacent error messages for additional details.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3021 Unable to get notification node properties {0}.
Class E
Explanation

An error occurred while querying the specified notification's properties. See adjacent error messages for additional details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3022 Unable to update notification {0}. Error: Notification must be disabled.
Class E
Explanation

NotifcationManager received a request to update the properties of an active notification.
Action

Disable the notification from Integration Server Administrator prior to updating it.
FAC_NOTIFICATION+ANOT3023 Unable to update notification {0}.
Class E
Explanation

An error occurred while updating the notification's properties. See adjacent error messages for additional details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3024 Unable to delete notification {0}. Error: Notification must be disabled.
Class E
Explanation

NotifcationManager received a request to delete an active notification.
Action

Disable the notification from Integration Server Administrator prior to deleting it.
FAC_NOTIFICATION+ANOT3025 Unable to delete notification {0}.
Class E
Explanation

An error occurred while deleting the specified notification. See adjacent error messages for additional details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3026 Unable to copy notification {0}.
Class E
Explanation

An error occurred while copying the specified notification. See adjacent error messages for additional details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3027 Unable to copy notification {0}. Error: nodeName is required.
Class E
Explanation

The specified notification node name is missing or incorrectly formatted.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3031 Unable to copy notification {0}. Error: Invalid node name {1}.
Class E
Explanation

Notification Manager failed to validate the specified node name. Refer to the error message text for more details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3032 Unable to copy notification {0}. Error: New name already exists {1}.
Class E
Explanation

The method NotificationManager.copyAdapterNotification failed because the specified destination notification node name already exists in the package.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3033 Unable to copy notification {0}. Error: New document name already exists {1}.
Class E
Explanation

The method NotificationManager.copyAdapterNotification failed because the specified new publishable document name already exists in the package.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3034 Unable to rename notification {0}. Error: Notification must be disabled.
Class E
Explanation

NotificationManager received a request to rename an active notification.
Action

Disable the notification from Integration Server Administrator prior to renaming it.
FAC_NOTIFICATION+ANOT3035 Unable to rename notification {0}. Error: {1}.
Class E
Explanation

An error occurred while renaming the notification. Refer to the error message text for more details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3036 Unable to find notification {0}.
Class E
Explanation

The method NotificationManager.queryNotificationStatistics failed because the specified notification could not be located in the namespace.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3037 Unable to get notification {0}. Error: Notification class name is not specified.
Class E
Explanation

The method NotificationNode.getNotification failed to determine the implementation class name for the specified notification.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3038 Error in Notification Callback:{0} notification {1}.
Class E
Explanation

An error occurred in method WmNotification.notifyEvent while processing the specified callback.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3039 Missing required parameter on service: {0}
Class E
Explanation

The method NotificationManager.queryNotificationTemplatesSupported failed because the adapter name was not present in the pipeline.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3040 Error creating notification object: {0}. Missing parameter: {1}.
Class E
Explanation

NotificationManager failed to create the notification because the specified parameter was not in the pipeline.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3041 Error creating notification object: {0}. Invalid Package Name {1}.
Class E
Explanation

NotificationManager failed to create the notification because the specified package name is invalid.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3042 Error creating notification object: {0}. Invalid Service Name {1}.
Class E
Explanation

NotificationManager failed to create the notification because the service name is missing, improperly formatted, or otherwise invalid.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3043 Error deleting notification object. Invalid node name: {0}.
Class E
Explanation

The specified notification node name is missing or incorrectly formatted.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3044 Error deleting notification object: {0}. Error: {1}.
Class E
Explanation

NotificationManager failed to validate the specified node name. Refer to the error message text for more details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3045 Error deleting notification object: {0}. The specified node is not a Listener Notification node.
Class E
Explanation

NotificationManager.deleteListenerNotification was called to delete the specified notification, which is a polling notification, not a listener notification.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3046 Unable to create document {0}. Error: {1}.
Class E
Explanation

An error occurred while creating a document for the specified notification. Refer to the error message text for more details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3047 Unable to create notification {0}. Error deleting an existing record: {1}.
Class E
Explanation

NotificationFactory failed to create the notification because it could not delete existing document records. Refer to the error message text for more details.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3048 Unable to create notification {0}. The specified Listener does not exist: {1}.
Class E
Explanation

NotificationManager.createListenerNotification failed to create the notification because it could not locate the corresponding listener node. Refer to the error message text for more details.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3049 Unable to create notification {0}. The specified notification template is not synchronous: {1}.
Class E
Explanation

NotificationFactory failed to create the notification because the underlying specified implementation class is not derived from WmSynchronousNotification. Refer to the error message text for more details.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3050 Unable to create notification {0}. The specified notification template is not asynchronous: {1}.
Class E
Explanation

NotificationFactory failed to create the specified notification because the underlying specified implementation class is not derived from WmAsynchronousNotification. Refer to the error message text for more details.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3051 Unable to query properties for {0}. Invalid node name.
Class E
Explanation

The specified notification node name is missing or improperly formatted.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3052 Unable to query properties for {0}. Error: {1}.
Class E
Explanation

NotificationManager failed to validate the node name. Refer to the error message text for more details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3053 Unable to update notification {0}. Invalid node name.
Class E
Explanation

The specified notification node name is missing or incorrectly formatted.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3054 Unable to update notification {0}. Error: {1}.
Class E
Explanation

NotificationManager failed to validate the node name. Refer to the error message text for more details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3055 Error copying notification: {0}. Missing parameter: {1}.
Class E
Explanation

NotificationManager failed to copy the notification because the specified parameter was not in the pipeline.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3056 Error copying notification: {0}. Invalid Package Name {1}.
Class E
Explanation

NotificationManager failed to copy the notification because the specified package name is invalid.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3057 Error updating notification object: {0}. Missing parameter: {1}.
Class E
Explanation

NotificationManager failed to update the notification because the specified parameter was not in the pipeline.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3058 Unable to copy notification {0}. Error: New node name is invalid {1}.
Class
Explanation

Invalid connection name specified.

Action

Remove any unsupported special characters from the connection name.
FAC_NOTIFICATION+ANOT3059 Error trying to enable notification {0}. Error: Listener not found {1}.
Class
Explanation

The error occurs when trying to enable or disable a listener notification, and the associated listener is not available.
Action

Make sure that the associated listener is not deleted. If the associated listener is deleted, create the listener again with the same name.

FAC_NOTIFICATION+ANOT3060 Error setting notification schedule property {0}
Class E
Explanation

An unexpected exception occurred while trying to set the schedule parameter listed in the message.
Action

Check the Integration Server error log for details about the unexpected exception.
FAC_NOTIFICATION+ANOT3061 Unable to move notification. Error: Invalid node name {0}.
Class E
Explanation

The name of the notification you are trying to move is invalid.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3062 Unable to move notification {0}. Error: Invalid Node Name Format.
Class E
Explanation

The name of the notification listed in the message text is not in folder:nodename format.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3063 Error moving notification: {0}. Error: Missing parameter: {1}.
Class E
Explanation

The move operation is missing the required parameter listed in the message text.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3064 Error moving notification: {0}. Error: Invalid Package Name {1}.
Class E
Explanation

The name of the destination package for the move operation is invalid on Integration Server.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3065 Unable to move notification {0}. Error: Src/Dest Node names not the same.{1}
Class E
Explanation

The notification node name was changed during the move operation.
Action

Only the package name and folder are allowed to change during a move operation, while the actual node name is not allowed to change. This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3066 Unable to move notification {0}. Error: Notification must be disabled.
Class E
Explanation

This notification cannot be moved because it is enabled. To move a notification, it first must be disabled.
Action

In Integration Server Administrator, disable the notification and retry the move operation.
FAC_NOTIFICATION+ANOT3067 Unable to move notification {0}.
Class E
Explanation

An unexpected exception occurred while trying to move a notification.
Action

Check the Integration Server error log for details about the unexpected exception.
FAC_NOTIFICATION+ANOT3068 Unable to move notification {0}. Error: nodeName is required.
Class E
Explanation

The node name specified for the move operation is either missing or invalid.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3069 Unable to move notification {0}. Error: New node name is invalid {1}.
Class E
Explanation

The new node name specified for the move operation is either missing or invalid.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3100 Unable to obtain list of polling notifications for adapter type.
Class
Explanation

The adapter type passed is null or invalid while retrieving, suspending, or resuming the adapter notifications.
Action

Ensure that a valid adapter type is passed.
FAC_NOTIFICATION+ANOT3101 Unable to obtain detailed information for polling notification.
Class E
Explanation

The method ARTAdmin.retrievePollingNotificationData failed because the notification name was not present in the pipeline.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3102 Unable to set status for polling notification.
Class E
Explanation

The method ARTAdmin.forceNotificationDisable failed because the notification name was not present in the pipeline.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3103 Unable to set schedule for polling notification.
Class E
Explanation

The method ARTAdmin.setNotificationSchedule failed because the notification name was not present in the pipeline.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3104 Unable to retrieve listener notification list. Missing parameter: {0}
Class E
Explanation

The method ARTAdmin.retrieveListenerNotifications failed because the adapter name was not present in the pipeline.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3105 Unable to set notification status. Missing parameter: {0}
Class E
Explanation

The method ARTAdmin.setNotificationStatus failed because the notification name was not present in the pipeline.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3106 Unable to set notification status. Notification not found: {0}
Class E
Explanation

The method ARTAdmin.setNotificationStatus failed because it was unable to locate the node for the specified notification.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3107 Unable to set notification status for {0}. Error: {1}
Class E
Explanation

The method ARTAdmin.setNotificationStatus failed because it was unable to enable or disable the specified listener notification.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3108 Unable to publish notification. Message ID {0} exceeds maximum length of {1}.
Class E
Explanation

The message ID specified by the adapter is longer than the allowed maximum length.
Action

Integration Server restricts the length of the message ID for a published document. Contact Software AG Global Support to see how to increase this setting. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_NOTIFICATION+ANOT3115 Errors occurred. {0} notifications reported errors while attempting to suspend. See error log for details.
Class E
Explanation

While attempting to suspend all notifications, some of the notifications reported errors.
Action

Look in the error log for details on the specific exceptions.
FAC_NOTIFICATION+ANOT3116 Errors occurred. {0} notifications were not enabled. See error log for details.
Class E
Explanation

While attempting to enable all suspended notifications, some of the notifications reported errors.
Action

Look in the error log for details on the specific exceptions.
FAC_NOTIFICATION+ANOT3117 Non-fatal errors encounter while disabling notification {0}. Details recorded in error log.
Class E
Explanation

An exception was encountered during the disable callback for a notification.
Action

Look in the error log for details on the specific exception.
FAC_NOTIFICATION+ANOT3118 Non-fatal errors encounter while suspending notification {0}. Details recorded in error log.
Class E
Explanation

An exception was encountered during the suspend callback for a notification.
Action

Look in the error log for details on the specific exception.
FAC_NOTIFICATION+ANOT3119 Non-fatal errors encounter while stopping notification {0}. Details recorded in error log.
Class E
Explanation

An exception was encountered during the shutdown callback for a notification.
Action

Look in the error log for details on the specific exception.
FAC_NOTIFICATION+ANOT3120 {0} is not a valid node type for this operation.
Class E
Explanation

An attempt was made to change the connection associated with a polling notification; however, the specified node is not a polling notification node.

Action

Select a polling notification node, and retry the operation.
FAC_NOTIFICATION+ANOT3121 {0} is in an invalid state for the requested operation.
Class E
Explanation

An attempt was made to perform an operation on a notification; however, the notification was not in the correct state. Typically this occurs when you attempt to perform an update type of operation when the notification is not in a disabled or suspended state.

Action

Change the state of the notification to disabled or suspended, and retry the operation.
FAC_NOTIFICATION+ANOT3533 Error while executing Polling Notification {0}. Check if the notification is present in all clusters.
Class
Explanation

The error occurs when a polling notification does not exist on all nodes in an Integration Server cluster.
Action

Make sure that all clustered Integration Server nodes have the same set of adapter polling notifications.
FAC_ART_ADAPTERSVC+ASVC4000 Unable to invoke adapter service {0}. Unable to establish connection to connection {1}.
Class E
Explanation

WmART failed to create or locate the connection object associated with the specified adapter service.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4001 Unable to invoke adapter service {0}. Connection.createInteraction() returned null.
Class E
Explanation

WmART failed to create a new instance of WmInteraction for the specified adapter service.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4002 Unable to invoke adapter service {0}.
Class E
Explanation

An error occurred while running the specified adapter service and processing its output. Additional information might appear in adjacent log messages.

Action

Determine whether the implementation of the adapter's WmAdapterService.execute method is throwing an exception at run time, and correct as needed.

FAC_ART_ADAPTERSVC+ASVC4005 Connection not available.
Class E
Explanation

WmART failed to locate the connection data node for the specified connection and adapter service. This message will always appear in conjunction with 117.4020.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4006 Invalid adapter type {0}.
Class E
Explanation

WmART failed to create an instance of the specified adapter service. This message will always appear in conjunction with 117.4021.
Action

Ensure that the implementation class for the adapter service is installed correctly in the package. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4007 Unable to get record factory bridge.
Class E
Explanation

WmART failed to create or locate an input/output record factory bridge object.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4008 Unable to get connection factory from connection.
Class E
Explanation

WmART failed to locate the connection factory associated with a ConnectionResource.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4009 Unable to get record factory required for interaction input.
Class E
Explanation

An error occurred while locating a RecordFactory associated with a ConnectionFactory. Additional details might appear in adjacent log messages.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4010 Unable to get adapter record factory. ConnectionFactory.getRecordFactory() returned null.
Class E
Explanation

WmART failed to locate a RecordFactory associated with a ConnectionFactory.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4011 Unable to connect to resource {0}. The resource is already being used in a parent transaction.
Class E
Explanation

WmART attempted to create a new connection to the specified resource, but detected that the resource is currently enrolled in an ongoing transaction.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4012 Unable to run adapter service. Error occurred when connecting to resource {0}.
Class E
Explanation

An error occurred while creating a new connection to the specified resource. Additional details might appear in adjacent log messages.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4013 Internal Error: Unable to nest connection states.
Class E
Explanation

WmART attempted to start a new transaction, but detected that a parent transaction already exists.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4014 Error while starting nested transaction. The name {0} is already in use.
Class E
Explanation

WmART attempted to start a new transaction, but detected that the specified transaction ID is already in use.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4015 Error(s) occurred while closing adapter connections.
Class E
Explanation

Error(s) occurred while closing one or more connections involved in a transaction. Separate log messages are listed for each connection.

Action

Ensure that all EIS resources used in the transaction can communicate with the adapter. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4018 Error while closing transactions at service completion Error:{0}.
Class E
Explanation

The specified error occurred while closing the connections involved in a successful transaction.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4019 Error while rolling back transaction Error:{0}.
Class E
Explanation

The specified error occurred while closing the connections involved in a failed transaction.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4020 Unable to invoke adapter service {0}. Connection resource {1} not found.
Class E
Explanation

WmART failed to locate the connection data node for the specified connection and adapter service.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4021 Unable to invoke adapter service {0}. Unable to get adapter service template.
Class E
Explanation

WmART failed to create an instance of the specified adapter service.
Action

Ensure that the implementation class for the adapter service is installed correctly in the package. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4022 Unable to invoke adapter service {0}. Unable to get connection state.
Class E
Explanation

WmART failed to determine the connection state for the specified adapter service. This will prevent a resource connection from being created.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4023 Unable to properly handle adapter connection error for connection {0}.
Class E
Explanation

WmART was unable to successfully handle an error that occurred on the specified connection while executing a service.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4024 Unable to invoke adapter service {0}. An error occurred on connection {1}. Unable to recover from connection error.
Class E
Explanation

An error occurred in the error handling logic while invoking the specified service. Additional details might appear in adjacent log messages.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4026 Unable to rollback transaction Error:{0}.
Class E
Explanation

The specified error occurred while marking a failed transaction for rollback.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4027 Unable to create adapter service {0}. Invalid package name {1}.
Class E
Explanation

WmART failed to create the specified adapter service because it could not locate the Package object for the specified package name.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4028 Unable to create adapter service {0}. Invalid service name.
Class E
Explanation

WmART failed to create the specified adapter service because the service node name is missing or invalid.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4029 Unable to create adapter service {0} with connection {1}. Connection not found.
Class E
Explanation

WmART AdapterServiceManager failed to create the adapter service because it could not locate the ConnectionDataNode object for the connection.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4030 Unable to create adapter service {0}.
Class E
Explanation

An error occurred while creating the specified adapter service. Additional details should appear in adjacent log messages.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4032 Unable to find adapter service {0}.
Class E
Explanation

WmART failed to locate the namespace node (NSNode) for the adapter service.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4033 Retryable Error while closing transactions at service completion Error:{0}.
Class E
Explanation

The specified retryable run-time exception occurred while completing a successful service invocation.
Action

Ensure that all EIS resources used in the transaction can communicate with the adapter. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4034 Retryable Error(s) occurred while closing adapter connections.
Class E
Explanation

One or more retryable errors have occurred while closing connections used in a transaction. Additional log messages might be listed.

Action

Ensure that all EIS resources used in the transaction can communicate with the adapter. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4035 Error while completing service listener Error:{0}.
Class E
Explanation

An error occurred while calling method com.wm.pkg.art.transaction.ServiceListener.listenComplete.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4036 Unable to commit transaction. Transaction state:{0} .
Class E
Explanation

WmART was unable to commit a transaction because the transaction was in the specified, unexpected state.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_ADAPTERSVC+ASVC4037 Unable to invoke adapter service {0}. Unable to create Input record.
Class E
Explanation

An unexpected exception occurred during the adapter service execution.
Action

Check the Integration Server error log for details on the unexpected exception.
FAC_ART_ADAPTERSVC+ASVC4038 Unable to delete adapter service {0}.
Class E
Explanation

An unexpected exception occurred trying to delete the adapter service.
Action

Check the Integration Server error log for details on the unexpected exception.
FAC_ART_ADAPTERSVC+ASVC4039 Unable to update adapter service {0}.
Class E
Explanation

An unexpected exception occurred trying to update the adapter service.
Action

Check the Integration Server error log for details on the unexpected exception.
FAC_ART_ADAPTERSVC+ASVC4040 Unable to create adapter service {0}. Adapter service node already exists.
Class E
Explanation

It is illegal to create an adapter service with the same folder and node name.
Action

Use a different name for the adapter service and retry the create operation.
FAC_ART_ADAPTERSVC+ASVC4048 Unable to update adapter service {0}.
Class E
Explanation

An exception was encountered while attempting to update the adapter service.
Action

Check the Integration Server error log for details on the original exception.
FAC_ART_ADAPTERSVC+ASVC4049 Unable to retrieve connection from resource {0}. See error log for details.
Class E
Explanation

An exception was encountered while trying to retrieve a connection.
Action

Check the Integration Server error log for details on the original exception.
FAC_ART_CONNECTION+CONN5000 Unable to retrieve and process connection properties from pipeline.
Class E
Explanation

WmART failed to process a connection's properties. Additional log messages might be listed.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5001 Error processing connection property {0}. Unable to get property name.
Class E
Explanation

WmART failed to locate an expected connection property in the pipeline.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5002 Error processing connection property {0}. Invalid value entered. The minimum string length is {1}.
Class E
Explanation

The size of the specified connection property value is less than the specified minimum size.
Action

Reconfigure the connection from Integration Server Administrator using values that are within the constraints set by the connection.
FAC_ART_CONNECTION+CONN5003 Error processing connection property {0}. Invalid value entered. The maximum string length is {1}.
Class E
Explanation

The value of the specified property is not valid.
Action

Reconfigure the connection from Integration Server Administrator using values that are within the constraints set by the connection.
FAC_ART_CONNECTION+CONN5004 Error processing connection property {0}.
Class E
Explanation

An error occurred when converting a connection property value to its internal Java representation. Additional log messages might be listed.

Action

Reconfigure the connection from Integration Server Administrator ensuring that all data entered conforms to the underlying types in the connection class. If the problem persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5005 Unable to configure connection properties. Error occurred while processing connection properties.
Class E
Explanation

This is a general processing error message. See adjacent log messages for details.
Action

Refer to the Action column for the accompanying messages.
FAC_ART_CONNECTION+CONN5006 Unable to get list of connections for adapter type: {0}.
Class E
Explanation

An error occurred while retrieving the list of configured connections for the specified adapter.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5007 Unable to get list of connection types for adapter type: {0}.
Class E
Explanation

An error occurred while retrieving the list of connection factories for the specified adapter.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5008 Unable to get properties for connection {0}.
Class E
Explanation

An error occurred while retrieving the configuration details for a specific connection.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5009 Unable to get connection properties for adapter: {0}, connection type: {1}.
Class E
Explanation

An error occurred while retrieving the connection properties for the specified connection factory and adapter.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5010 Invalid connection name. The connection name must have a valid folder name and node name.
Class E
Explanation

An invalid folder and/or connection name was entered on the Integration Server Administrator Configure Connection Type page.
Action

Re-enter the new connection type information making sure that the Folder Name and Connection Name fields have valid entries.
FAC_ART_CONNECTION+CONN5011 Unable to create new connection {0}.
Class E
Explanation

An error occurred while configuring a new connection type.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5012 Unable to update connection {0}.
Class E
Explanation

An error occurred while editing the connection type.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5013 Unable to find connection {0}.
Class E
Explanation

WmART was unable to locate the specified connection while deleting it.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5014 Unable to delete connection {0}.
Class E
Explanation

An error occurred while deleting a connection.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5015 Unable to get connection manager properties.
Class E
Explanation

An error occurred while getting a list of Connection Manager properties.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5016 Unable to get configured values for connection manager.
Class E
Explanation

An error occurred while processing Connection Manager property values.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5017 Error occurred while getting connection manager properties.
Class E
Explanation

This is a general processing error message. See adjacent log messages for details.
Action

Refer to the Action column for the accompanying messages.
FAC_ART_CONNECTION+CONN5018 Error getting connection properties.
Class E
Explanation

An error occurred while fetching connection property values.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5019 Error getting connection metadata. Missing required parameter: adapterTypeName.
Class E
Explanation

WmART was unable to determine the adapter type name while processing a connection's metadata.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5020 Unable to process connection properties. Internal error.
Class E
Explanation

WmART failed to set properties for a connection node. The expected connection form fields were not found in the pipeline.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5021 Unable to process connection properties. Internal error.
Class E
Explanation

WmART failed to get properties for a connection node. The expected connection form fields were not found in the pipeline.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5022 Cannot create connection {0}. Adapter type {1} does not exist.
Class E
Explanation

WmART failed to start the specified connection because it was unable to locate the specified adapter type.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5023 Unable to configure connection manager. No connection manager properties provided.
Class E
Explanation

WmART was unable to validate Connection Manager properties because they were null.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5024 Unable set connection {0} state to {1}. Invalid state specified.
Class E
Explanation

WmART was unable to modify the connection's state because the intended state is missing or invalid.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5025 Unable to enable connection {0}.
Class E
Explanation

This is a general processing error message. See adjacent log messages for details.
Action

Refer to the Action column for the accompanying messages.
FAC_ART_CONNECTION+CONN5026 Unable to stop connection {0}.
Class E
Explanation

This is a general processing error message. See adjacent log messages for details.
Action

Refer to the Action column for the accompanying messages.
FAC_ART_CONNECTION+CONN5027 Unable to enable connection {0}. Connection is already enabled or is being shutdown.
Class E
Explanation

WmART is enabling a connection that is not currently in a disabled state.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5028 Unable to shutdown connection{0}. Connection is already disabled or in the process of being shutdown.
Class E
Explanation

WmART is attempting to shut down a connection that is not currently in an enabled state.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5029 Unable to disable connection {0}. Connection is already disabled.
Class E
Explanation

WmART is attempting to disable a connection that is already disabled.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5030 Unable to create connection {0}. Package {1} does not exist.
Class E
Explanation

WmART was unable to create the connection node because it could not locate the specified package.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5031 Unable to delete connection {0}. Internal error.
Class E
Explanation

An error occurred while deleting the specified connection.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5032 Unable to set connection resource properties. Internal error: ConnectionPropertiesBridge not found.
Class E
Explanation

WmART failed to create a configured managed connection factory because it could not locate the WmConnectionPropertiesBridge instance needed to set its properties.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5033 Error disabling connection resources.
Class E
Explanation

An error occurred while stopping the connection resources. See adjacent log messages for more details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5034 Connection type {0} does not exist in adapter {1}.
Class E
Explanation

WmART was unable to locate the specified connection factory in the specified adapter.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5035 Unable to create connection {0}. Internal error occurred while creating connection factory of type {1}.
Class E
Explanation

WmART was unable to create the specified connection factory for the connection. See adjacent log messages for more details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5036 Unable to configure connection manager.
Class E
Explanation

WmART was unable to create a Connection Manager. See adjacent log messages for more details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5037 Cannot create ResourceAdapterMetaData object. CCI Connection Factory is not an instance of WmConnectionFactory.
Class E
Explanation

The method ConnectionDataNodeManager.createCCIConnectionFactory could not get the ResourceAdapterMetaData object for a connection factory.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5040 Unable to get adapter service templates for connection {0}.
Class E
Explanation

WmART failed to locate any adapter service templates for the specified connection.
Action

Do not configure an adapter service with a connection for which no adapter service templates exist. Try another connection.
FAC_ART_CONNECTION+CONN5041 Unable to get connection status for connection resource {0}.
Class E
Explanation

WmART was unable to obtain connection state information for the specified connection.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5042 Unable to enable connection resource {0}.
Class E
Explanation

This is a general processing error message. See adjacent log messages for details.
Action

Refer to the Action column for the accompanying messages.
FAC_ART_CONNECTION+CONN5043 Unable to disable connection resource {0}.
Class E
Explanation

This is a general processing error message. See adjacent log messages for details.
Action

Refer to the Action column for the accompanying messages.
FAC_ART_CONNECTION+CONN5044 Unable to shutdown connection resource {0}.
Class E
Explanation

This is a general processing error message. See adjacent log messages for details.
Action

Refer to the Action column for the accompanying messages.
FAC_ART_CONNECTION+CONN5046 Unable to get a connection to resource {0}. Resource not available.
Class E
Explanation

WmART could not locate a connection factory for the specified connection.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5047 Unable to get a connection to resource {0}. Internal error occurred while restarting connection.
Class E
Explanation

An error occurred while creating the connection.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5048 Unable to get adapter service templates for connection resource {0}.
Class E
Explanation

WmART failed to locate any adapter service templates for the connection.
Action

Do not configure an adapter service with a connection for which no adapter service templates exist. Try another connection.
FAC_ART_CONNECTION+CONN5049 Unable to reset adapter connection {0}. Connection {1} is not supported.
Class E
Explanation

The method ConnectionResource.handleAdapterConnectionException reports that the specified connection class is not derived from WmConnection.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5050 Unable to reset adapter connection {0}. Unable to configure connection manager.
Class E
Explanation

The method ConnectionResource.handleAdapterConnectionException was unable to locate the ConnectionManager or ConnectionManagerPropertiesBridge for this connection.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5051 Unable to reset adapter connection {0}. Adapter type {1} does not exist.
Class E
Explanation

The method ConnectionResource.handleAdapterConnectionException was unable to determine the adapter type for this connection.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5052 Unable to create connection. Connection resource {0} is restarting.
Class E
Explanation

The method ConnectionResource.createConnection has been called against a connection resource in the restarting state.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5053 Unable to get a connection to resource {0}.
Class E
Explanation

WmART failed to create a connection because it could not communicate with the back-end connection resource.
Action

Check independently that the target resource is communicating and that it can be reached from the connection. If the condition persists, contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5054 Unable to reset adapter connection {0}.
Class E
Explanation

An error occurred while trying to restart the specified connection. See adjacent log messages for additional details.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5055 Unable to get adapter service templates for connection resource {0}.
Class E
Explanation

The method ConnectionResourceState.getInteractionSpecsSupported failed to locate the ResourceAdapterMetaData associated with specified connection.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5056 Unable to create connection for connection resource {0}, connection type {1}.
Class E
Explanation

The method ConnectionResourceState.createConnection failed to get the Connection object for the specified connection.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5057 Adapter Runtime was unable to initialize {0} connection resources for the adapter "{1}".
Class E
Explanation

com.wm.pkg.art.ns.ConnectionDataNodeManager.startConnectionResources detected failures in starting connection nodes for the specified adapter.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5058 Adapter Runtime was unable to stop {0} connection resources for the adapter "{1}".
Class E
Explanation

com.wm.pkg.art.ns.ConnectionDataNodeManager.stopConnectionResources detected failures in shutting down connection nodes for the specified adapter.

Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5059 Adapter Runtime was unable to stop connection resources for the {0} adapter types.
Class E
Explanation

com.wm.pkg.art.ns.ConnectionDataNodeManager.stopAllConnectionResources detected failures in shutting down connection nodes.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5060 Unable get properties for connection resource {0}.
Class E
Explanation

An error occurred while fetching the specified connection's properties.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5061 Unable to configure Connection Manager: Poolable property not set.
Class E
Explanation

WmART failed to determine whether a connection should be pooled.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5062 Unable to find connection {0}: error {1}.
Class E
Explanation

An error was encountered while validating the specified connection.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5063 Unable to start connection {0}: after {1} attempt(s).
Class E
Explanation

The startup of a connection pool has exceeded the maximum number of retries.
Action

Check the Integration Server error log for details on the retryable exception.
FAC_ART_CONNECTION+CONN5064 Cannot reconfigure connection {0}: it must be disabled first.
Class E
Explanation

To update a connection, it must be disabled.
Action

Disable the connection and retry the update operation.
FAC_ART_CONNECTION+CONN5065 Cannot delete connection {0}: it must be disabled first.
Class E
Explanation

To delete a connection, it must be disabled.
Action

Disable the connection and retry the delete operation.
FAC_ART_CONNECTION+CONN5066 Exception encountered processing {0} connection callback method. The {1} operation will proceed.
Class E
Explanation

An exception was encountered while executing the specified connection callback method.
Action

Look in the error log for details on the original exception. The callback processing did proceed even though the error was encountered.

FAC_ART_CONNECTION+CONN5067 Unknown callback event type received on connection node: {0}
Class E
Explanation

An unknown connection callback was made.
Action

This is an internal error. Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

FAC_ART_CONNECTION+CONN5068 Exception encountered processing {0} connection callback method.
Class E
Explanation

An exception was encountered while executing the specified connection callback method.
Action

Look in the error log for details on the original exception. When this error is received, the callback processing does not continue.

FAC_ART_CONNECTION+CONN5069 Cannot create connection factory for connection {0}. Adapter type {1} does not exist.
Class E
Explanation

The adapter associated with this connection is not registered.
Action

Verify the package dependencies are set correctly. Reload the adapter package, and retry the operation.
FAC_ART_CONNECTION+CONN5070 Exception encountered creating the connection factory for connection {0}.
Class E
Explanation

An exception was encountered creating the connection factory.
Action

Look in the error log for details on the original exception.
FAC_ART_CONNECTION+CONN5071 A non-fatal exception was encountered attempting to unregister {0}. The operation will proceed. See the error log for more details.
Class W
Explanation

An exception was encountered trying to unregister the connection node.
Action

Look in the error log for details on the original exception. The unregister processing continued.
FAC_ART_CONNECTION+CONN5072 Adapter service {0} cannot use connection {1}. The adapter service and connection are from different adapters.
Class E
Explanation

The user attempted to set the connection associated with an adapter service; however, the adapter service and connection were not from the same adapter.

Action

Retry the operation using a connection from the same adapter.
FAC_ART_CONNECTION+CONN5073 Adapter service {0} cannot use connection {1}. The connection is already being used by a listener.
Class E
Explanation

The user attempted to use a connection in an adapter service; however, the connection is already being used by a listener.
Action

Retry the operation using a connection that is not already being used by a listener.
FAC_ART_CONNECTION+CONN5074 "{0}" is not a valid connection name for adapter {1}
Class E
Explanation

The user attempted to use a connection in a polling notification or listener; however, the connection was not part of the same adapter.

Action

Retry the operation using a connection from the same adapter.
FAC_ART_CONNECTION+CONN5075 Listener {0} cannot use connection {1}. The connection is already being used by an adapter service or polling notification.
Class E
Explanation

The specified listener cannot use the specified connection because the connection is already being used by a polling notification or an adapter service.

Action

Retry the operation using a connection that is not being used by a polling notification or adapter service.
FAC_ART_CONNECTION+CONN5076 Polling notification {0} cannot use connection {1}. The connection is already being used by a listener.
Class E
Explanation

The user attempted to use a connection in a polling notification; however, the connection is already being used by a listener.
Action

Retry the operation using a connection that is not already being used by a listener.
FAC_ART_CONNECTION+CONN5077 Adapter service {0} cannot use connection {1}. The connection does not support this adapter service template.
Class E
Explanation

The user attempted to use a connection for an adapter service; however, the connection does not support the adapter service.
Action

Retry the operation using a connection that supports the adapter service.
FAC_ART_CONNECTION+CONN5078 Minimum pool size must not be greater than maximum pool size.
Class E
Explanation

The user attempted to set the minimum pool size to a value that is greater than the maximum pool size.
Action

Retry the operation specifying a minimum pool size that is lower than the maximum pool size.
FAC_ART_CONNECTION+CONN5079 Exception encountered while removing {0} connection from Connection cache.
Class
Explanation

An error occurred while invalidating a failed XA transaction.
Action

Make sure that there is connectivity to the adapter backend, and that the connection associated with the transaction is enabled. Check the server logs for transaction details.

FAC_ART_CONNECTION+CONN5080 Exception encountered while updating connection {0}.
Class
Explanation

An error occurred while updating a connection node from an old version to a new one.
Action

Make sure that the connection parameters are valid. Make sure that the user updating the connection has been assigned the appropriate ACL.

FAC_ART_CONNECTION+CONN5083 Invalid value {0} specified for {1} property, hence using default value as {2}
Class
Explanation

The value of the watt.art.connection.nodeVersion watt property is invalid. Hence, when creating the connection node, the specified node version is ignored and the default value for node version is used instead.

Action

Make sure the watt.art.connection.nodeVersion property has a valid value. For details, see the Integration Server administration guide.

AUTH055 Did not add user(s) {0}. Password was empty.
Explanation

The Password field requires a value.
Action

Enter a valid password.
BAB.0002.0000 Wrapped Exception:
Class E
Explanation

A communication failure occurred between Integration Server and a client resulting in the exception.
Action

Verify that the communication parameters are correct. Check the setup for any network issues.
BAB.0006.0001 CommException: LinkServer closed
Class E
Explanation

A client sent a request to Integration Server after a previous connection between the client and Integration Server was closed.
Action

Make sure that the client is not designed to send new requests to Integration Server when communication with the server is closed.

BAD_AUDIT_DIR The value supplied for watt.server.audit.logDir does not identify an existing directory that Integration Server can write to. watt.server.audit.logDir was not changed.
Class E
Explanation

The audit log directory was not changed because the watt.server.audit.logDir parameter refers to a directory that either does not exist or Integration Server does not have permission to write to.

Action

Specify a directory that exists on the server and that Integration Server can write to. You can specify the full path name, or a relative path in relation to the Integration Server.

BAD_SESSION_ID Invalid or expired session identifier.
BAF.0000.0001 No file or properites specified
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0002 Illegal set_mode: {2}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0003 FSDirCursor _encode exception
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0004 A minimum of three log segments required only {2} found
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0005 Unsupported BlockDevice specified: {2}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0006 BlockDevice Exception:
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0007 Unable to open FSData devices
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0008 Wrong number of Data Extents:{2} != {3}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0009 Invalid dataMaxExtents specified:{2}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0010 Invalid indexMaxExtents specified:{2}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0011 Invalid dataMaxExtents:{2} must be between 1 and {3}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0012 Invalid indexMaxExtents:{2} must be between 1 and {3}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0013 Invalid dataThreshold specified:{2}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0014 Invalid indexThreshold specified:{2}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0015 Invalid dataThreshold:{2} must be between 50% and 99%
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0016 Invalid indexThreshold:{2} must be between 50% and 99%
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0017 Log offset:{2} inside Superblock
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0018 Log offset:{2} > Meta offset:{3}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0019 Meta offset{2} > Data offset:{3}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0020 Error during create - Data store already exists
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0021 Exception during checkDataDevices:
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0022 Exception during newHashCode:
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0023 Unknown log type:{2}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0024 NOT RETURNABLE in finalize:{2}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0025 Finalizing undestroyed cursor (p={2} d={3})
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0026 No more null entries after {2} in {3}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0027 Filesystem full ({2} < {3})
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0028 Block write failure
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0029 Unable to locate block of sufficient size
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0030 Cannot unlink last remaining empty
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0031 Data Expansion required but Maximum Data Exceeded
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0032 Index expansion requested but maximum are allocated
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0033 CreateIndexExtent, unable to alloc block
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0034 Mismatch:{2} {3} != {4}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0046 Warning {2} failed
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0047 Notify() on null ref idx={2} hc={3} : {4}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0048 Transaction has no members:{2}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0072 Error during open - Log File does not exist
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0073 Error during create - Log File already exists
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0074 Error during create - Average Block Size or entries must be specified
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0075 Error during create - NumEntries exceeds size of integer
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0076 Error during open - data file segments do not match, input {2}, output {3}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0102 The FSData is damaged, see the journal log for details
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0000.0103 FSData checker. Bad NULL entry chain
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0035 Fatal Runtime Exception:{2}
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0036 No open TXN for dirty entry
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0037 Filesystem is in an invalid state
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0038 Improper deleted type:(2}
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0039 Can't unlink:(2}
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0040 Can't add first empty back to empty list
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0041 FreeBytes mismatch:{2} != {3}
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0042 Out of order merge:{2} & {3}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0043 First null entry cannot be null
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0044 First empty entry cannot be null
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0045 Transaction has no members:{2}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0049 Cannot use destroyed cursor
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0050 EndTXN called outside of a transaction
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0051 AbortTXN called outside of a transaction:{2}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0052 Log is not open
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0053 Log is not closed
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0054 Log is smaller than max block ({2} < {3})
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0055 Transaction larger than total log
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0056 Cursors already @ 0:{2}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0057 References negative!:{2}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0058 Entry is already unlinked!:{2}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0059 No backup to revert to:{2}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0060 Type mismatch: {2} != {3} on {4}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0061 Data length ({2}) != expected length:{3}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0001.0076 Illegal state change from {2} to {3}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0002.0000 Wrapped Exception:
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0003.0070 TransactionException: Wait to start transaction interrupted
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0003.0071 TransactionException: Resource already in a transaction
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0003.0072 TransactionException: Wait to start transaction not allowed
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0004.0062 Data: Unable to get cursor lock
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0004.0063 Data: Cannot get key, cursor is unpositioned
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0004.0064 Data: Cannot get value, cursor is unpositioned
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0004.0065 Data: Cannot get value reference, cursor is unpositioned
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0004.0066 Data: Cursor is unpositioned
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0004.0067 Data: Unable to delete: {2}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0004.0068 Data: Can not clone a destroyed cursor
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0004.0069 Data: Referenced object has been deleted
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0077 IOException: No Properties provied to JDBCBlockDev
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0078 IOException: No JDBC Driver provided to JDBCBlockDev
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0079 IOException: No URL provided to JDBCBlockDev
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0080 IOException: Unable to create table:{2}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0081 IOException: {2} JDBCBlockDevice doesn't support Logical Devices - offset:{3}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0082 IOException: {2} Attempted to write past final segment: {3}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0083 IOException: {2} Attempted to read past final segment: {3}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0084 IOException: {2} Blob length: {3} != Segment size:{4}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0085 IOException: {2} Not Found:
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0086 IOException: {2} Unable to Connect - Retries Exhausted
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0087 IOException: All component files must be the same length
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0088 IOException: Invalid logical position specified
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0089 IOException: Read error
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0090 IOException: Write error
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0091 IOException: Invalid Physical position
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0092 IOException: SplitExtent failed - Extent not found:{2}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0093 IOException: Unable to allocate new IBlockDevice in Device Group
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0094 IOException: Invalid Log Region detected - Timestamp mismatch
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0095 IOException: CompositeBlockDevice read error
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0096 IOException: missing {2} properties file
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0097 IOException: Illegal mode {2}. Must be 'rw' or 'r'
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0098 IOException: block device has 0 length
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0099 IOException: Unable to read {2} bytes
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0100 IOException: Unable to allocate write buffer
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAF.0005.0101 IOException: Native library unavailable
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAQ.0002.0000 Wrapped Exception:
BAQ.0003.0001 TransactionException: Resource already in a transaction
BAR.0001.1401 RuntimeException: unsupported cursor {2}
BAR.0002.0000 Wrapped Exception:
BAR.0005.1600 RepoDirCodec: DecodeParms must be called before decode
BAR.0005.1601 RepoDirCodec: Unserializable repo object
BAR.0005.1602 RepoDirCodec: Repo Must be Standalone
BAR.0006.1700 CommException: sendRequest() failed
BAR.0006.1701 CommException: ConnectionServer closed
BAR.0006.1702 CommException: Missing keyword:{2}
BAR.0010.0001 Directory: insert exception:
BAR.0010.0002 Directory: update exception:
BAR.0010.0003 Directory: rename exception:
BAR.0010.0004 Directory: get queue failed, invalid object type
BAR.0010.0005 Directory: entry version "{2}" does not exist for entry "{3}"
BAR.0010.0007 Directory: delete exception:
BAR.0010.0008 Directory: "{2}" already exists
BAR.0010.0009 Directory: entry "{2}" is not a symbolic link
BAR.0010.0011 Directory: object has been destroyed
BAR.0010.0012 Directory: null not allowed in compound directory path expression
BAR.0010.0013 Directory; key "{2}" not found
BAR.0010.0014 Directory: key "{2}" is not a repository directory
BAR.0010.0015 Directory: "{2}" can not be versioned
BAR.0010.0016 Directory: illegal state, directory may have been destroyed
BAR.0010.0017 Directory: "{2}" is an invalid symbolic link target
BAR.0010.0018 Directory: "{2}" is a repository directory and an invalid symbolic link target
BAR.0010.0019 Directory: "{2}" is a repository IData object and an invalid symbolic link target
BAR.0010.0021 Directory: new key {2} can not be a compound key
BAR.0010.0022 Directory: RepoQueue {2} can not be versioned
BAR.0010.0023 Directory: "{2}" is a symbolic link and is invalid as a symbolic link target
BAR.0010.0024 Directory: Entry {2} not versioned
BAR.0010.0025 Directory: reconnect attempt failed
BAR.0010.0026 Directory: get queue failed, object is null
BAR.0010.0027 Directory: can not be target of an update for entry {2}
BAR.0010.0028 Directory: invalid version number {2}
BAR.0010.0029 Directory: invalid relative version number {2}
BAR.0010.0030 Directory: cannot delete current version for entry {2}
BAR.0010.0031 Directory: illegal transaction state, {2} not allowed in active transaction
BAR.0010.0032 Directory: testAndSet failed for entry {2}:
BAR.0010.0033 Directory: testAndSet failed for entry {2} - Invalid Entry Type
BAR.0010.0034 Directory: key "{2}" is not a repository stream
BAR.0010.0035 Directory: internal error, unknown repository container type, {2}
BAR.0011.0100 Queue: constructor failure:
BAR.0011.0101 Queue: enqueue failure:
BAR.0011.0102 Queue: dequeue failure:
BAR.0012.0200 Stream: Invalid length key type: {2}
BAR.0012.0201 Stream: DataException: {2}
BAR.0012.0202 Stream: Invalid Object: {2} missing {3}
BAR.0012.0203 Stream: Invalid Segments key type: {2}
BAR.0012.0204 Stream: Segment {2} not found in {3}
BAR.0012.0205 Stream: Invalid Status key type: {2}
BAR.0012.0206 Stream: EOF - Pending stream
BAR.0012.0207 Stream: {2} already open for output
BAR.0012.0208 Stream: {2} closed
BAR.0012.0209 Stream: Error Writing byte[] to OutputStream: {2}
BAR.0012.0210 Stream: Error Flushing OutputStream: {2}
BAR.0012.0211 Stream: Error Closing OutputStream: {2}
BAR.0012.0212 Stream: Error Reading InputStream: {2}
BAR.0012.0213 Stream: Error Closing InputStream: {2}
BAR.0013.0300 NameParser: missing component key
BAR.0013.0301 NameParser: invalid key syntax: "{2}"
BAR.0013.0302 NameParser: index missing from key "{2}"
BAR.0013.0303 NameParser: index not numeric "{2}"
BAR.0013.0304 NameParser: bad array index syntax "{2}"
BAR.0014.0400 Illegal argument: Directory object cannot be stored
BAR.0014.0403 Illegal argument: Key must be specified
BAR.0014.0404 Illegal argument: Action must be ADD, DELETE, or CHANGE
BAR.0015.0500 Session: Logon required
BAR.0015.0505 Session: RepoStream object in use, RepoAPI calls not allowed
BAR.0015.0510 Session: Invalid logon URL "{2}" specified
BAR.0015.0511 Session: No default server specified
BAR.0015.0515 Session: Active repository session, logon not allowed
BAR.0015.0516 Session: Internal Error, invalid Transaction Resource object
BAR.0015.0518 Session: Duplicate logon not allowed
BAR.0015.0519 Session: Session not logged on
BAR.0015.0520 Session: Session disabled due to LUW timeout
BAR.0015.0521 Session: Previous LUW timeout still in progress, try again later
BAR.0016.0600 Internal Error: local server connection config invalid
BAR.0016.0601 Internal Error: during server initialization exception:
BAR.0016.0603 Internal Error: connection to repository server failed, missing remote refid
BAR.0016.0604 Internal Error: Repository server shutdown failed:
BAR.0016.0605 Internal Error: Repository server is not the primary server
BAR.0017.0700 RepoStore: Internal Error creating Repo Server object:
BAR.0017.0701 RepoStore: Unable to initialize Repository backing store
BAR.0017.0702 RepoStore: Repository server has been destroyed
BAR.0017.0703 RepoStore: Repository backing store not initialized
BAR.0017.0704 RepoStore: Missing 'persiststore' config parm
BAR.0018.0900 RepoConnection: Secondary server could not find primary repository server
BAR.0018.0901 RepoConnection: Could not find primary repository server: {2}
BAR.0018.0904 RepoConnection: Reconnect failed, no remote server cluster connection information available
BAR.0019.1100 Transaction: Resource already participating in a transaction
BAR.0019.1101 Transaction: Illegal transaction state, transaction destroyed
BAR.0019.1102 Transaction: Illegal transaction state, session mismatch
BAR.0019.1103 Transaction: Illegal transaction state, IDataSharedCuror Transactions not supported
BAR.0019.1104 Transaction: TransactionException: Cursor has been destroyed
BAR.0020.1200 SharedCursor: illegal state, cursor destroyed
BAR.0020.1201 SharedCursor: reconnect attempt failed
BAR.0020.1202 SharedCursor: invalid resource specified
BAR.0020.1203 SharedCursor: Reconnect Exception detected
BAR.0020.1204 SharedCursor: Can not get key, cursor is unpositioned.
BAR.0020.1205 SharedCursor: Can not get value, cursor is unpositioned.
BAR.0021.1300 Queue: reconnect attempt failed
BAR.0021.1301 Queue: illegal state, queue destroyed
BAR.0021.1302 Queue: object has been destroyed
BAR.0021.1303 Queue: Repository Queue entry corrupted
BAR.0022.1400 Data: illegal state, IData destroyed
BAR.0023.1500 Migration: export not implemented in RepoMigrate, use Repov2Migrate or Repov3Migrate to export your specific Repo version
BAR.0023.1501 Migration: exception:{2}
BAR.0023.1502 Migration: Error During Import, probably Coder mismatch between Export and Import utilities: exception:{2}
BAR.0023.1503 Migration: import not implemented in {2}, use RepoMigrate to import
4 FSData checker repair attempted. Zero length file deleted. {0}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
7 FSData checker. {0} entrys not in any chain.
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
8 FSData checker repair attempted. Bad NULL list entry removed. {0}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
9 FSData checker. Entry in {0} list has bad prev pointer. {1}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
10 FSData checker. Entry in {0} list has wrong type. {1} != {2} {3}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
11 FSData checker. Duplicate entry in {0} list. {1}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
12 FSData checker. Entry in {0} list contains bad reference count. {1}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
13 FSData checker. Data node has wrong type. {0}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
14 FSData checker. Hash tree node has wrong type. {0}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
15 FSData checker. Free byte count is wrong. {0} != {1}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
16 FSData checker repair attempted. {0} orphaned NULLs recovered.
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
17 FSData checker. Entry is in multiple chains. {0}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
18 FSData checker. Repair attempted - full check will be run again.
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
19 FSData checker. Attempting to recover orphaned NULL and EMPTY entries.
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
21 FSData checker. Dir entry has bad last node pointer. {0}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
22 FSData checker repair attempted. Bad EMPTY list entry removed. {0}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
BAT.0000.0001 duplicate endpoint id {2}
BAT.0000.0002 endpoint {2} not found.
BAT.0000.0003 endpoint {2} can not be deleted it has producers/consumers with active or pending messages.
BAT.0000.0004 duplicate producer id {2}
BAT.0000.0005 producer {2} not found.
BAT.0000.0006 producer {2} can not deleted, it has active or pending messages.
BAT.0000.0007 duplicate consumer id {2}
BAT.0000.0008 consumer {2} not found.
BAT.0000.0009 consumer {2} can not deleted, it has active or pending messages.
BAT.0000.0010 duplicate message store id {2} for producer {3}
BAT.0000.0011 consumer {2} message store id {3} not found.
BAT.0000.0012 consumer {2} message store {3} can not deleted, it has active or pending messages.
BAT.0000.0013 no active transaction for message store id {2} for parent container id {3}
BAT.0000.0014 transactions not enabled for message store id {2} for parent container id {3}
BAT.0000.0015 method disabled because transactions are enabled for message store id {2} for parent container id {3}
BAT.0000.0016 consumer {2} message store {3} this method requires transactions to be enabled.
BAT.0000.0017 duplicate sequence number {2} for message id {3} in store id {4} in parent container id {5}
BAT.0000.0018 message id {2} not found in message store id {3} for parent container id {4}
BAT.0000.0019 out of sequence message seq {2}, last seq {3} id {4} in store id {5} in parent container id {6}
BAT.0000.0020 argument arrays must be same length, message store id {2} for parent container id {3}
BAT.0000.0021 invalid timeout value {2}, must be > 0
BAT.0000.0022 invalid message sequence number {2}, must be >= 0
BAT.0000.0023 invalid message acknowledge mode {2}
BAT.0000.0024 message id can not be null, {2}
BAT.0000.0025 illegal state change request from {2} to {3}
BAT.0000.0026 {2} {3} has been closed
BAT.0000.0027 thread has been interrupted
BAT.0000.0028 method [{2}] is not allowed from a rejected message handler.
BAT.0000.0029 the transient store type {2} specified could not be initialized.
BAT.0000.0030 IData backing store is null, required
BAT.0000.0031 IDATASTORE type requires a transacted IData implemenation
BAT.0000.0032 duplicate message for store id {2} in parent container id {3}
BAT.0000.0033 {2} {3} is already started.
BAT.0000.0034 {2} {3} has been stopped.
BAT.0000.0035 Invalid reference: MessageStore[{2}] is null.
BAT.0000.0036 A ISimpleQueueProducer has already been created for this SimpleQueue
BAT.0000.0037 A ISimpleQueueConsumer has already been created for this SimpleQueue
BAT.0000.0038 Cannot ack not allowed for a zero-or-more SimpleQueue
BAT.0000.0039 Cannot nack not allowed for a zero-or-more SimpleQueue
BAT.0000.0040 SimpleQueue {2} not found.
BAT.0000.0041 SimpleQueue {2} can not be deleted it is not empty.
BAT.0002.0000 Wrapped Exception:
1 Recoverable Error skipped because warnonopen = continue. Db:{0} Error:{1}
Class
2 Recoverable Error encountered but warnonopen = fail. Db:{0} Error:{1}
Class
3 Error deleting damaged data file. Db:{0} Error:{1}
Class
4 Error renaming damaged data file. Db:{0} Error:{1}
Class
5 Error re-creating damaged data file. Db:{0} Error:{1}
Class
6 Damaged data file renamed. Db:{0} renamed:{1}
Class
7 Damaged data file deleted. Db:{0}
Class
8 Damaged data file re-created. Db:{0}
Class
9 Error during checkDataDevice. Db:{0} Error:{1}
Class
10 Damaged data file detected. Db:{0} Error:{1}
Class
11 Data file resize required. Db:{0}
Class
12 Error cleaning up resized Data file. Db:{0} Error:{1}
Class
13 Error creating resized Data file. Db:{0} Error:{1}
Class
14 Error copying resized Data file. Db:{0}
Class
15 Error renaming original data file. Db:{0} Error:{1}
Class
16 Error closing resized data file. Db:{0} Error:{1}
Class
17 Error renaming resized data file. Db:{0} Error:{1}
Class
18 Error restoring original data file. Db:{0} Error:{1}
Class
19 Error cleaning up copied Data file. Db:{0} Error:{1}
Class
20 Error closing original Data file. Db:{0} Error:{1}
Class
21 Data file resize completed. Db:{0}
Class
22 Resized Data file recovered. Db:{0}
Class
BEHAVIOUR_IS_INVALID Behaviour should be one of client or server
BROKER_NOT_REACHABLE Broker not connected.
CACHE_CACHE_MANAGER_NOT_INITIALIZED Cache manager {0} is not loaded or initialized.
CACHE_CACHE_NOT_FOUND Cache {1} for cache manager {0} not found.
CACHE_CANNOT_ACQUIRE_READ_LOCK Could not acquire a read lock for key {0} in cache {1} contained within the cache manager {2}.
CACHE_CANNOT_ACQUIRE_WRITE_LOCK Could not acquire a write lock for key {0} in cache {1} contained within the cache manager {2}.
CACHE_INVALID_INPUT Invalid value for input parameter {0}. Error:{1}.
CACHE_MISSING_PARAM_NAME Missing required parameter: {0}
CALLBACK_IS_REQD Callback is required
CALLBACK_SIGN_INVALID Callback service input signature for flow service "{0}" should be as per "{1}"
CALLBACK_SPEC_INVALID Callback service specification for flow service "{0}" should point to "{1}"
CALLBACK_SVC_EXISTS Callback service "{0}" cannot be created as another node with same name exists
CANNOT_CREATE_FOREACH Cannot make the For Each from: {0} to: {1}
CAN_NOT_RESUME can not resume due to state:
CAN_NOT_SUSPEND can not suspend due to state:
CLIENT_HTTP_EXP3 Do not use data.string, data.stream or data.mimeStream with the DELETE method.
CLIENT_HTTP_KERBEROS_DELEGATION_NO_CREDENTIALS Kerberos delegatable credentials do not exist.
Explanation

Delegatable credentials do not exist. Delegation is set to Kerberos without requesting for a delegatable token in the previous (parent) pub.client:http call.

Action

Ensure that the delegation input in the pub.client:http is set only after the requestDelegatableToken is set to true in the previous (parent) pub.client:http call.

CLIENT_HTTP_KERBEROS_INVALID_SPN_FORMAT Invalid Service Principal Name Format provided
CLIENT_HTTP_KERBEROS_PRINCIPALPASSWORD_DELEGATION_BOTHREQ Either both Kerberos clientPrincipal and clientPassword must be supplied or both should be left blank.
CLIENT_HTTP_KERBEROS_SPNFORM_DELEGATION_FORMAT Kerberos service principal name form must be either username or hostbased.
CLIENT_HTTP_KERBEROS_SPN_FORM_DELEGATION_BOTHREQ Either both Kerberos service principal name and service principal name form must be supplied or both should be left blank.
CLIENT_INPUT_NOT_BYTE_ARRAY Input {0} must be a byte array
CLIENT_WEBSOCKET_MISSING_INPUT "{0}" is a required input
CLIENT_WEBSOCKET_WRONG_URL URL is required and must begin with ws or wss
CURRENT_EVENT_IS_NOT_A_START_ELEMENT Current event is not a START_ELEMENT
CURRENT_STATE_NOT_START_ELEMENT Current state not START_ELEMENT
CURRENT_STATE_NOT_START_ELEMENT_END_ELEMENT_OR_ENTITY_REFERENCE Current state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE
CURRENT_STATE_NOT_START_ELEMENT_OR_END_ELEMENT Current state not START_ELEMENT or END_ELEMENT
DB_IS_REQD The ISCoreAudit functional alias on the JDBC Pools page must be configured to use the Service Monitoring capabilities
DEFAULT_ILIVE_TRUSTSTORE_DESCRIPTION Default truststore alias for webMethods Cloud.
DEPLOYER_PACKAGE_DISALLOW_INSTALL_ON_ENABLED Package"{0}" will not be deployed because deploying to an enabled package is disallowed
DEPLOYER_PACKAGE_INSTALL_ERR_MSG Package "{0}" did not install successfully. Messages: {1}
DEPLOYER_PACKAGE_NOT_ENABLED The deployed package {0} is disabled. Check the Integration Server logs for any errors that may have occurred during deployment. If the package contains Adapter or .NET assets for which variable substitution parameters were specified, you must perform the variable substitutions manually on the Integration Server for the changes to take effect.
DEPLOYER_PACKAGE_SERVICE_EXECUTION_CHECK Package"{0}" will not be deployed because at least one of the Package services is in execution
DISABLED Disabled
DUPE_EVENT_TYPE_NAME Document type {0} has failed to load. Duplicate Broker document type name {1} is also referenced by {2}
DUP_XID_RESOURCE_UPDT Failed attempt to store resource status={0} for xid={1}, resource={2}. XID not found.
DUP_XID_START Transaction start for xid={0} failed. Transaction for this xid has already been started.
EDA_ETD_ROOT_NODE Parameter xmldata must be XML with a root node element named "Event {http://namespaces.softwareag.com/EDA/Event}".
EGDOS002 Error occurred while updating global Denial of Service options for Enterprise Gateway rules. Details: {0}.
Class E
Explanation

Enterprise Gateway Server could not update the global Denial of Service options for Enterprise Gateway rules for the reason indicated.

Action

Ensure that the correct input parameters are provided to the service. Then, try to update the global Denial of Service options again.

EGDOS006 Error occurred while updating Denial of Service by IP address options for Enterprise Gateway rules. Details: {0}.
Class E
Explanation

Enterprise Gateway Server could not update DoS by IP address options for Enterprise Gateway rules for the reason indicated.

Action

Check the reason detailed in the message and take appropriate corrective action.
EGMAPP02 Error occurred while updating device types. Details: {0}.
Class E
Explanation

Enterprise Gateway Server could not update the list of device types. Possible reasons are: The device name is too long (exceeds 255 characters) or contains special characters; the device type was deleted by another user while the current user tried to update the list; the device type is specified in one or more Enterprise Gateway rules; or there was a problem saving the device types to the Enterprise Gateway rules configuration file.

Action

If you are adding a device type, use the correct format. If you are deleting a device type and the device type is used in one or more Enterprise Gateway rules, remove or change the condition in the mobile application protection filter where the device type is specified.

EGMAPP04 Error occurred while updating mobile applications. Details: {0}.
Class E
Explanation

Enterprise Gateway Server could not update the list of mobile applications. Possible reasons are: The application name is too long (exceeds 255 characters) or contains special characters; the application was deleted by another user while the current user tried to update the list; the application is specified in one or more rules; or there was a problem saving the application to the Enterprise Gateway rules configuration file.

Action

If you are adding a mobile application, use the correct format. If you are deleting a mobile application and the application is used in one or more Enterprise Gateway rules, remove or change the condition in the mobile application protection filter where the application is specified.

EGRULE002 Enterprise Gateway rule could not be created. Details: {0}.
Class E
Explanation

Enterprise Gateway Server could not create the Enterprise Gateway rule for the reason indicated.
Action

Ensure that the correct input parameters are provided to the rule creation service.
EGRULE004 Enterprise Gateway rule could not be updated. Details: {0}.
Class E
Explanation

Enterprise Gateway Server could not update the Enterprise Gateway rule for the reason indicated.
Action

Ensure that the correct input parameters are provided to the rule update service.
EGRULE006 Enterprise Gateway rule could not be deleted. Details: {0}.
Class E
Explanation

Enterprise Gateway Server could not delete the Enterprise Gateway rule for the reason indicated.
Action

Ensure that the correct input parameters are provided to the rule deletion service.
EGRULE007 A rule violation occurred for Enterprise Gateway rule "{0}". Filter: "{1}", message: "{2}", request IP: {3}, request URL: {4}, request time: {5}.
Class E
Explanation

Enterprise Gateway Server could not process the request because an Enterprise Gateway rule violation occurred.
Action

Either change the rule filter settings or modify the request so a rule violation does not occur.
EGRULE008 A rule violation occurred for Enterprise Gateway rule "{0}". Request IP: {1}, request URL: {2}, request time: {3}.
Class E
Explanation

Enterprise Gateway Server could not process the request because an Enterprise Gateway rule violation occurred.
Action

Either change the rule settings or modify the request so a rule violation does not occur.
ELEMENT_IS_NOT_A_TEXT_ONLY_ONE Element is not a text-only one
ELEMENT_TEXT_CONTENT_MAY_NOT_CONTAIN_START_ELEMENT element text content may not contain START_ELEMENT
EMPTY_KEYSTORE_ALIAS Alias is not specified
EMPTY_KEYSTORE_LOCATION Location is not specified
EMPTY_KEYSTORE_PROVIDER Provider is not specified
EMPTY_KEYSTORE_TYPE Type is not specified
ENABLED Enabled
ERROR_DRIVER_CONTAINS_INVALID_CHARS Driver alias definition cannot be created. Driver alias name contains one or more invalid characters.
Class I
Explanation

The Alias Name contains invalid characters. The Alias Name may contain: letters (a -z, A-Z), numbers (0-9), space ( ), underscore (_), period (.), and hyphen (-). The alias name must contain at least one letter or number.

Action

Revise the Alias Name so that it is valid.

ERROR_POOL_CONTAINS_INVALID_CHARS Pool alias cannot contain any of these characters: {0}
Class I
ER_SEND_MISSING_EVENT_PARAM Missing required parameter: {0}
EXCEPTION_PARSING_HELP_CONTEXT_FILE Exception occurred while parsing the file doc/OnlineHelp/context.xml from WmRoot package: {0}
EXPECTED_LOCAL_NAME_NOT_MATCHING Expected local name '{0}'; current local name '{1}'
EXPECTED_NON_NULL_LOCAL_NAME Expected non-null local name, but current token not a START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE (was {0})
FAC+"."+AUTO_CREATE_CONNECTION_FACTORY Automatically creating JMS Connection Factory {0} for JMS connection alias {1}.
FAC+"."+AUTO_CREATE_DESTINATION Automatically creating JMS Destination {0} for JMS connection alias {1}.
FAC+"."+ERROR_READING_SJO_FILE_FOR_CONNECTIONFACTORY Error occurred during lookup for SonicMQ ConnectionFactory object from "{0}".
FAC+"."+ERROR_READING_SJO_FILE_FOR_DESTINATION Error occurred during lookup for SonicMQ Destination object from "{0}".
FAC+"."+EXCEPTION_DURING_HOT_DEPLOYMENT Exception {0} occured while handling Hot Deployment notification for trigger {1}
FAC+"."+JMS_STARTING JMS subsystem is starting.
FAC+"."+PRODUCER_RETRY_FAILED Producer Retry for destination {0} alias {1} failed after {2} attempt(s): {3}
FAC+"."+PRODUCER_RETRY_FAILED_ATTEMPT Producer Retry for destination {0} alias {1} failed retry attempt {2}: {3}
FAC+"."+PRODUCER_RETRY_INTERRUPT_DISABLED Producer Retry for destination {0} alias {1} has been interrupted because the alias is now disabled.
FAC+"."+PRODUCER_RETRY_INTERRUPT_DISCONNECTED Producer Retry for destination {0} alias {1} has been interrupted because the connection is closed.
FAC+"."+PRODUCER_RETRY_INTERRUPT_SHUTDOWN Producer Retry for destination {0} alias {1} has been interrupted because the server is shutting down.
FAC+"."+PRODUCER_RETRY_NOTRUN_DISABLED Producer Retry not attempted for destination {0} alias {1} because the alias is disabled: {2}
FAC+"."+PRODUCER_RETRY_NOTRUN_DISCONNECTED Producer Retry not attempted for destination {0} alias {1} because the connection is closed: {2}
FAC+"."+PRODUCER_RETRY_NOTRUN_SHUTDOWN Producer Retry not attempted for destination {0} alias {1} because the server is shutting down: {2}
FAC+"."+PRODUCER_RETRY_STARTED Attempting Producer Retry for destination {0} alias {1}. Max Retry Attempts: {2}, Retry Interval: {3}, Error: {4}
FAC+"."+PRODUCER_RETRY_SUCCESS Producer Retry for destination {0} alias {1} was successful after {2} attempt(s).
FAC+"."+REGISTER_TRIGGER_FOR_HOT_DEPLOYMENT Registering trigger {0} for updates on Hot Deployment of dependent package
FAC+"."+RESUMING_TRIGGER_ON_HOT_DEPLOYMENT_CANCEL Resuming trigger {0} as the Hot Deployment of dependent package ended
FAC+"."+RESUMING_TRIGGER_ON_HOT_DEPLOYMENT_END Resuming trigger {0} as the Hot Deployment of dependent package ended
FAC+"."+SUSPENDING_TRIGGER_ON_HOT_DEPLOYMENT_START Suspending trigger {0} as the dependent package is under Hot Deployment
FAC+"."+UNABLE_TO_RESTART_TRIGGER Unable to re-start JMS Trigger {0}: {1}
FAC+"."+UNABLE_TO_START_TRIGGER_FIRST_TIME Unable to start JMS Trigger {0}: {1}
FAC+"."+UN_REGISTER_TRIGGER_FOR_HOT_DEPLOYMENT Unregistering trigger {0} for updates on Hot Deployment of dependent package
FAC_LISTENER+ALIS3300 MSGPREFIX_LISTENER+"Unable to handle the state change event of the listener {0} acrosss the cluster"
Explanation

An error occurred while processing a state change event for a listener in the cluster.
Action

Check the details for the error in the Integration Server error log.
FAC_LISTENER+ALIS3311 MSGPREFIX_LISTENER+"The cluster event can't be acted upon since the listener {0} is not present"
Explanation

The error occurs when a listener is not available on a cluster node because of incorrect cluster setup. The correct cluster setup requires copying the same package on all cluster nodes.

Action

Check if the package containing the listener is loaded properly. Verify if the WmART package dependency is set properly.
FAC_LISTENER+ALIS3312 MSGPREFIX_LISTENER+"unable to activate the listener {0}. "
Explanation

When a listener becomes disabled on an active node, another node becomes active. The system returns the exception if an unexpected error occurs during that process.

Action

Check the error log and try enabling the listener manually later on the node on which the failure occurred.
FAC_LISTENER+ALIS3313 MSGPREFIX_LISTENER+"Unable to perform the listener failover since the listener node {0} is not available."
Explanation

The error occurs during failover handling of a node when the active node is down, if the corresponding listener node is not available.

Action

Check whether the package with the corresponding listener node is enabled and active. If not, try enabling the package.
FAC_LISTENER+ALIS3314 MSGPREFIX_LISTENER+"Unable to perform the listener failover due to an error while accessing the listener state cache."
Explanation

This error occurs during failover handling of a node when the active node is down, if the listener state is not accessible from the Terracotta cache.

Action

If all nodes throw the same exception, try enabling the listener manually on any of the nodes.
FAC_LISTENER+ALIS3315 MSGPREFIX_LISTENER+"Unable to synchronize the listener {0} across the cluster since the shared cache isn't available."
Explanation

In a clustered environment, shared cache is used to synchronize the state of the listeners. The error occurs when the shared cache is not available.

Action

Check the connection of the shared cache server to the specified Integration Server node.
FAC_NOTIFICATION+ANOT3132 MSGPREFIX_NOTIFICATION+"Unable to set Publish Event status. Missing parameter: {0}"
Explanation

The Notification name input parameter is missing.
Action

Specify the notification name for which you want to set the Publish Event status.
FAC_NOTIFICATION+ANOT3133 MSGPREFIX_NOTIFICATION+"Unable to set Publish Event status. Notification not found: {0}"
Explanation

The specified notification does not exist.
Action

Check if the notification with the specified name exists in the system.
FAC_NOTIFICATION+ANOT3136 MSGPREFIX_NOTIFICATION+"Notification 'Disable' request is not initiated by any user explicitly."
Explanation

The polling notification is not disabled explicitly by any user. It was disabled automatically due to an error.

Action

Check the stack trace in the error log to find out the point at which the notification 'disable' operation was triggered.

FAILURE_INSTANCE_NOT_EXCEPTION FlowExit ''{0}'' -- failure instance object is not an Exception
FAILURE_INVALID_BRANCH_CHILD Invalid child of FlowBranch ''{0}''
FAILURE_NOT_FOUND_OR_INVALID FlowExit ''{0}'' -- class for specified failure not found or invalid
FASHHASH_NOSUCHELEMENT FastHashEnumerator
EX_NTH_NODE_INVALID Child at index [{0}] is cannot be added to this row.
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Action Information page from Developer, and the contents of the packages\WmFlatFile\config directory.

EX_NODE_INVALID Cannot add child
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Action Information page from Developer, and the contents of the packages\WmFlatFile\config directory.

EX_NODE_NOT_ALLOWED Cannot add child
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Action Information page from Developer, and the contents of the packages\WmFlatFile\config directory.

EX_CANT_ADD_RECORD_TO_RECORD Cannot put a record inside another record
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Information page from the Developer, and the contents of the packages\WmFlatFile\config directory.

EX_CANT_ADD_UNKNOWN_TYPE_TO_RECORD Cannot add unknown type to a record
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Action Information page from Developer, and the contents of the packages\WmFlatFile\config directory.

EX_CANT_ADD_CHILD_TO_FIELD Fields cannot have children
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Information page from the Developer, and the contents of the packages\WmFlatFile\config directory.

EX_CANT_ADD_COMP_TO_COMP Composites cannot contain composites
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Information page from the Developer, and the contents of the packages\WmFlatFile\config directory.

EX_CANT_ADD_RECORD_TO_COMP Cannot add record to a composite
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Information page from the Developer, and the contents of the packages\WmFlatFile\config directory.

EX_CANT_ADD_UNKNOWN_TO_COMP Cannot add unknown type to a composite
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Action Information page from Developer, and the contents of the packages\WmFlatFile\config directory.

EX_NODE_MUST_BE_USAGE Cannot add child
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Action Information page from Developer, and the contents of the packages\WmFlatFile\config directory.

EX_CANNOT_MODIFY_DETAILS Cannot add children to detail view
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Information page from the Developer, and the contents of the packages\WmFlatFile\config directory.

EX_CANNOT_MODIFY_DETAILS2 Cannot add children to detail view
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Information page from the Developer, and the contents of the packages\WmFlatFile\config directory.

EX_CANT_ADD_NON_RECORD Cannot add child of type: {0}
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Information page from the Developer, and the contents of the packages\WmFlatFile\config directory.

EX_CANT_CHANGE_FIRST_KID The first child of the Record Usage must be the Record Definition
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Action Information page from the Developer, and the contents of the packages\WmFlatFile\config directory.

EX_CANT_SET_USAGE_CHILDREN Cannot set the children of a usage node. The only child is the used node definition
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Action Information page from Developer, and the contents of the packages\WmFlatFile\config directory.

EX_CANT_EDIT Node is not editable
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Action Information page from Developer, and the contents of the packages\WmFlatFile\config directory.

EX_CANT_EDIT_REFERENCE Cannot modify the children of a reference
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Action Information page from Developer, and the contents of the packages\WmFlatFile\config directory.

EX_NODE_MUST_BE_X Cannot add child. Child must be of type: {0}
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Action Information page from Developer, and the contents of the packages\WmFlatFile\config directory.

EX_NODE_WITH_NAME_ALREADY_EXISTS Cannot add node, node with name {0} already exists
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Action Information page from Developer, and the contents of the packages\WmFlatFile\config directory.

EX_CANT_EDIT_BROKEN_LINK Cannot edit a broken link
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Action Information page from Developer, and the contents of the packages\WmFlatFile\config directory.

EX_SERVER_CANNOT_BE_NULL Server cannot be null
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support. Keep the following information handy before contacting the Software AG Global Support: server and error logs, a copy of the Support Action Information page from Developer, and the contents of the packages\WmFlatFile\config directory.

NO_MARK_SUPPORT The mark method is not supported by the supplied InputStream.
Class
NO_RESET_SUPPORT The reset method is not supported by the supplied InputStream.
Class
INPUT_VAR_GT_ZERO `{0}` must be greater than zero (0).
Class
INPUT_VAR_REQD_GT_ZERO `{0}` is required and must be greater than zero (0).
Class
INPUT_VAR_REQD_GT_ONE `{0}` is required and must be greater than one (1).
Class
INPUT_VAR_REQD_GE_ZERO `{0}` is required and must be zero (0) or greater.
Class
INPUT_VAR_OPT_GE_ZERO If `{0}` is supplied, it must be zero (0) or greater.
Class
OFFSET_LENGTH_TOO_BIG `offset` + `length` cannot exceed the size of `buffer`.
Class
FFDATA_CANNOT_BE_NULL Input parameter ffData cannot be null.
Class
CANT_PROCESS_TYPE Cannot process ffData of type: {0}.
Class
SCHEMA_NOT_FOUND Could not find flat file Schema: {0}.
Class
INVALID_SETTINGS Not validating, not keeping results, invalid settings.
Class
ENCODING_NOT_SUPPORTED Encoding not supported: {0}.
Class
INPUT_NAME_AND_PKG_REQ Name and package are required.
Class
DICT_NOT_FOUND Could not find dictionary: {0}.
Class
INPUT_FFSCHEMA_REQ Flat File Schema name must be specified.
Class
NO_INPUT_SIG No input signature presented.
Class
NODE_EXISTS Document Type `{0}` already exists. Please delete it before re-creating.
Class
INVALID_MAX_ERR Value specified for maxErrors must be an integer. Value specified: `{0}`.
Class
RECORD_NOT_FOUND Could not find record definition `{0}` in dictionary {1}.
Class
COMPOSITE_NOT_FOUND Could not find composite definition `{0}` in dictionary {1}.
Class
FIELD_NOT_FOUND Could not find field definition `{0}` in dictionary {1}.
Class
ENTRY_TYPE_REQ Please specify a valid value for entryType.
Class
NOT_FF_DICT {0} is not a flat file dictionary.
Class
NOT_FF_SCHEMA {0} is not a flat file schema.
Class
NO_FF_SCHEMA_ROOT Could not find root tag <FFSchmea>
Class
BAD_ENTRY_TYPE Could not find a valid value for input parameter `EntryType`
Class
NO_FF_DICT_ROOT Could not find root tag <FFDictionary>
Class
DICT_ALREADY_EXISTS Flat file dictionary {0} already exists in package {1}, cannot create it in package {2}.
Class
SCHEMA_ALREADY_EXISTS Flat file schema {0} already exists in package {1}, cannot create it in package {2}.
Class
PKG_AND_DICT_NAME_REQ Values are required for input parameters `FFDictionaryName` and `PackageName`.
Class
ENTRY_NOT_FOUND Could not find entry `{0}` in dictionary `{1}`.
Class
REC_ENTRY_NOT_FOUND Could not find record entry `{0}`, in dictionary `{1}`.
Class
COMP_ENTRY_NOT_FOUND Could not find composite entry `{0}` in dictionary `{1}`.
Class
FIELD_ENTRY_NOT_FOUND Could not find field entry `{0}` in dictionary `{1}`.
Class
CANT_BE_INTERFACE Document Type name `{0}` is not valid
Class
FOLLOWING_REQUIRED The following input parameters are required:{0}
Class
BROKEN_REF Cannot create document type. Referenced {0} {1} in flat file dictionary {2} could not be found
Class
NO_NAME_FOUND Please specify a value for name
Class
NODE_NOT_FOUND Could not find {0}
Class
MUST_BE_DICT_OR_DEF Specified value {0} must be a flat file dictionary or flat file schema.
Class
PACKAGE_NOT_FOUND Could not find package: {0}
Class
PACKAGE_NOT_ENABLED Package {0}, is not enabled. Please enable the package, or specify a different package
Class
SAVED_WITH_WARNINGS {0} was saved with the following warning(s):
Class
SAVED_WITH_ERRORS {0} was saved with the following error(s):
Class
NOT_FF_DICTIONARY {0} is not a flat file dictionary.
Class
CANT_ENCODE_DELIMITER Cannot encode the delimiter character `{0}` (U+{1}) using specified encoding: {2}}. Please select a different delimiter character.
Class
FOUND_DUP_RECORD_NAME_UM Cannot create field ''{0}'' in publishable document type ''{1}''; field with duplicate names are not permitted with protocol buffer encoding.
"1.0" Error processing Cleanup service: {0}
Class E
Explanation

An error occurred during the execution of the user-specified cleanup service.
Action

Check the server error log for more detailed information. This error is most likely caused by an exception that occurred in the user-written, cleanup service, which is identified in the message.

"1.1" Listener key not provided. Cleanup service not running
Class E
Explanation

Internal Error
Action

Contact Software AG Global Support. Please have the following information available: server and error logs, a copy of the Support Information page from the Developer, and the contents of the packages\WmFlatFile\config directory.

"1.2" Cleanup service access denied. User {0} not allowed to run service {1}
Class E
Explanation

The user specified in the message attempted to run the service specified in the message, but the user does not have the privileges required to run the service.

Action

Modify the "Run services as user" parameter on the file polling listener configuration page to specify a user that has the appropriate privileges. Make certain that the user you specify has the permissions to execute the processing service.

"1.3" Error processing service: {0}
Class E
Explanation

An error occurred during the execution of the user-specified cleanup service.
Action

Check the server error log for more detailed information. This error is most likely caused by an exception that occurred in the user-written cleanup service, which is identified in the message.

"1.4" Could not delete file: {0} - {1}
Class E
Explanation

An error occurred while attempting to delete the specified file.
Action

Check the file system to determine why the specified file has not been deleted. It might be necessary to delete the file manually.
"1.12" Could not move source file {0} to working directory {1}
Class E
Explanation

The system was unable to move the file from the monitoring directory to the working directory.
Action

On a Windows operating system this can be normal behavior because the operating system will not allow a file to be moved while the file is being written to. For Windows, this is an error if the file listed is never processed. On a non-Windows operating system, this error might occur because the source and destination directories are on different file systems. Specify the source and destination directories to be on the same file system.

"1.13" Error processing monitoring file. {0}.
Class E
Explanation

An error occurred during the execution of the user-specified processing service.
Action

Check the server error log for more detailed information. This error is most likely caused by an exception that occurred in the user-written cleanup service, which is identified in the message.

"1.14" Error processing cleanup. {0}.
Class E
Explanation

An error occurred during the execution of the user-specified cleanup service.
Action

Check the server error log for more detailed information. This error is most likely caused by an exception that occurred in the user-written cleanup service, which is identified in the message.

"1.20" Could not get canonical path for monitoring directory: {0} - {1}
Class E
Explanation

The system could not obtain the canonical path for the monitoring directory, which is identified in the message. The message also displays the reason.

Action

Take the appropriate action based on the reason for the error shown in the message.
"1.30" Error processing file: {0}
Class E
Explanation

An error occurred during the execution of the user-specified processing service.
Action

Check the server error log for more detailed information. This error is most likely caused by an exception that occurred in the user-written cleanup service, which is identified in the message.

"1.31" Listener key not provided. File polling listener not running
Class E
Explanation

Internal Error
Action

Contact Software AG Global Support. Please have the following information available: server and error logs, a copy of the Support Information page from Developer, and the contents of the packages\WmFlatFile\config directory.

"1.32" File polling processing service access denied. User {0} not allowed to run service {1}
Class E
Explanation

The specified user does not have privileges to run the specified service.
Action

Modify the "Run services as user" parameter in the file polling listener configuration page to specify a user that has the appropriate privileges. Make certain that the user you specify has the permissions to execute the processing service.

"1.33" Error processing service: {0}
Class E
Explanation

An error occurred during the execution of the user-specified processing service.
Action

Check the server error log for more detailed information. This error is most likely caused by an exception that occurred in the user-written cleanup service, which is identified in the message.

"1.34" Could not move file to finished directory. {0}
Class E
Explanation

The system was unable to move the file from the working directory to the finished directory.
Action

On a Windows operating system this can be normal behavior because the operating system will not allow a file to be moved while the file is being written to. For Windows, this is an error if the file listed is never processed. On a non-Windows operating system, this error might occur because the source and destination directories are on different file systems. Specify the source and destination directories to be on the same file system.

"1.35" File polling processing service indicated error - [{0}]
Class
Explanation

The processing service flagged an error to indicate there is an error.
Action

No action is required.
"1.36" File polling processing file: {0}
Class
Explanation

The indicated file is being processed.
Action

No action is required.
"1.37" Could not rename file {0} to {1}.
Class E
Explanation

The system was unable to move the file from the monitoring directory to the working directory.
Action

On a Windows operating system this can be normal behavior because the operating system will not allow a file to be moved while the file is being written to. For Windows, this is an error if the file listed is never processed. On a non-Windows operating system, this error might occur because the source and destination directories are on different file systems. Specify the source and destination directories to be on the same file system.

FILEPOLLING_INVALID_SVC Invalid processing service: {0}
Class E
Explanation

The specified processing service does not exist.
Action

Specify a service name that exists on the Integration Server.
FILEPOLLING_NO_SVC No such service: {0}
Class
FILEPOLLING_UNKNOWN_CONTENT Unknown content type: {0}
Class E
Explanation

No content handler is defined for the given content type.
Action

Specify a content type for which a content handler has been defined or define a content handler for the specified content type. For more details, see the Javadoc for the class com.wm.app.b2b.server.ServerAPI.

FILEPOLLING_SERVER_ERROR Server Error: {0}
Class E
Explanation

This is an internal error.
Action

Contact Software AG Global Support. Please have the following information available: server and error logs, a copy of the Support Information page from the Developer, and the contents of the packages\WmFlatFile\config directory.

FILEPOLLING_INVALID_CLEANUPSVC Invalid Cleanup service: {0}
Class E
Explanation

The specified processing service does not exist.
Action

Specify a service name that exists on the Integration Server.
MONITORDIR_REQUIRED Must provide Monitoring Directory
Class E
Explanation

No monitor directory was specified.
Action

Specify a monitor directory.
MONITORDIR_NOTEXIST Monitoring Directory does not exist
Class E
Explanation

The monitoring directory does not exist.
Action

Create the monitoring directory.
WORKDIR_NOTEXIST Working Directory does not exist
Class E
Explanation

The working directory does not exist.
Action

Create the working directory.
RUNUSER_REQUIRED Must provide User Name
Class E
Explanation

The user did not specify a value for the input "Run services as user".
Action

Specify a user to run the service as.
PROCESSINGSRV_REQUIRED Must provide Processing service
Class E
Explanation

The processing service was not specified.
Action

Specify a processing service.
INVALID_PROCESSING_SERVICE Invalid processing service {0}
Class E
Explanation

The specified processing service does not exist.
Action

Specify a service name that exists on the webMethods Integration Server.
MONITORDIR_NOTEXISTS Monitor Directory {0} does not exist
Class E
Explanation

The monitor directory does not exist.
Action

Create the monitor directory.
COMPDIR_NOTEXIST Completion Directory does not exist
Class E
Explanation

The completion directory does not exist or cannot be created.
Action

Determine whether the server has permissions to create the indicated directory, or create the directory manually.
ERRORDIR_NOTEXIST Error Directory does not exist
Class E
Explanation

The error directory does not exist or cannot be created.
Action

Determine whether the server has permissions to create the indicated directory, or create the directory manually.
INVALID_CLEANUP_SERVICE Invalid Cleanup service {0}
Class E
Explanation

The specified clean up service does not exist.
Action

Specify a clean up service that exists on the webMethods Integration Server.
INVALID_WORKDIR Invalid Working Directory
Class E
Explanation

The specified working directory is the same as either the monitoring directory or the completion directory.
Action

Specify a working directory that is not the same as the completion or monitoring directories.
INVALID_ERRORDIR Invalid Error Directory
Class E
Explanation

The specified error directory is the same as either the monitoring directory or the completion directory.
Action

Specify an error directory that is not the same as the completion or monitoring directories.
NO_CONDITION_STRING No condition string definied for the conditional validator.
Class
BAD_TYPE Internal Error: Unable to handle type: {0}.
Class
BAD_REC_IDENTIFIER Unable to handle recordIdentifier of type: {0}.
Class
NO_CHOICES Code list validatior contained no valid choices
Class
NO_COMPOSITE_ELEMENTS Composite does not contain any subfields.
Class
DEF_AND_REF Cannot contain both a definition and a reference.
Class
REC_ELEM_CANNOT_HAVE_BOTH_COMP_AND_FIELD A <RecordElement> tag cannot have both a <CompositeUsage> and a <FieldUsage> tag
Class
FIELD_ONLY_ONE_VALIDATOR A field can only have one validator
Class
FIELD_ONLY_ONE_EXTRACTOR A field can only have one extractor
Class
TOO_MANY_PARSERS Too many record parsers defined. A <RecordParser> tag can only contain one record parser.
Class
TOO_MANY_IDENTIFIERS Too many record identifiers defined. A <RecordIdentifier> tag can only contain one record identifier.
Class
MUST_HAVE_IDENTIFIER Flat file schema must have a record identifier defined.
Class
MUST_HAVE_PARSER Flat file schema must have a record parser defined.
Class
MUST_BE_INT_GT_ZERO Value {0} must be integer greater than or equal to zero.
Class
MAX_OCCURS_BAD <MaxOccur> value must be either "Unlimited" or a positive integer greater than zero. `{0}` is not a valid value.
Class
POS_KEY_BAD <Position> value must be either "NoPosition" or an integer. `{0}` is not a valid value.
Class
BAD_AREA_KEY <Area> must be either "NoArea" or a positive integer greader than zero. `{0}` is not a valid value.
Class
MUST_BE_INT_GT_ONE Value {0} must be integer greater than or equal to one.
Class
DEF_OR_REF Either <{0}> or <{1}> is required.
Class
END_LT_START The end position ({1}) must be greater than the start position ({0}).
Class
NO_RECORDS_DEFINIED The flat file schema has no records defined.
Class
COULD_NOT_FIND_DICTIONARY This element contains a reference to the flat file dictionary {0}, which does not exist
Class
REFERENCE_NOT_FOUND The {0} entry called {1} in flat file dictionary {2} in package {3} could not be found
Class
RECORD_HAS_NO_FIELDS_DEFINED Record has no fields or composites defined
Class
NO_RECORD_DELIMITER_DEFINED Must have a record delimiter defined when using delimited record parser
Class
NO_FIELD_DELIMITER_DEFINED Must have a field delimiter defined when using Nth field extractors
Class
NO_COMPOSITE_DELIMITER_DEFINED Must have a subfield delimiter defined when using composite extractors
Class
NO_EXTRACTOR_DEFINED Element has no extractor defined
Class
2.1 Unable to load resource bundle: {0}
Class
FTP_CMD_ERR Command {0} failed
HTTP_RESPONSE_HEADER_MISSING Required HTTP Response Headers missing from response.
IDLE_TIMEOUT_SHOULD_BE_GT_ASYNC_WRITE_TIMEOUT Idle timeout {0} should be greater than async write timeout of {1}
ILLEGAL_CHARACTER_EXISTS Illegal Character "{0}" exists in the provided input
IMPROPER_URI_AND_XMLOBJECTID The uri provided must be #{0} as [#idXmlObject] for an enveloping signature.
INCORRECT_SIGNATURE_TYPE The signature cannot be both enveloped and detached.
INIT_XASTORE_NULL The XA store could not be initialized.
INVALID_ALLOW_HOSTNAME Invalid character/s found in host name, {0}, in IP Access Allow list.
INVALID_CARDINALITY Invalid range ''{0}'' specified for cardinality.
INVALID_COPY_MODE Invalid Copy Mode ''{0}''.
INVALID_DATA_RANGE Select a date range of up to 30 days and then try again.
INVALID_DATE_COMPARISON End date can not be less than start date
INVALID_DATE_RANGE Select a date range of up to 30 days and then try again.
INVALID_DES_TRIGGER_DUP_DETECTION DES triggers do not support the duplicate document detection feature in this release.
INVALID_DES_TRIGGER_MULTI_DEST DES triggers cannot specify more than one condition or more than one document type within a condition.
INVALID_DES_TRIGGER_SERIAL DES triggers do not support serial processing mode in this release.
INVALID_EXIT FlowExit ''{0}'' -- invalid exit from try, catch, or finally
INVALID_EXIT_ITREATION FlowExit ''{0}'' -- invalid exit from iteration
INVALID_FIELD_NAME_UM Cannot create field ''{0}'' in publishable document type ''{1}''; this field name is not valid for use with protocol buffer encoding. The Universal Messaging provider will transport the field contents, which will be visible to Integration Server clients only.
INVALID_FOR_EACH_COPY_PATH Invalid Copy inside For Each.
INVALID_IDLE_TIMEOUT Invalid value for idle timeout={0}
INVALID_INPUT Incorrect Input "{0}"
INVALID_INPUT_INT Incorrect Input : "{0}" and "{1}" must be valid int types
INVALID_INPUT_INT...0 Incorrect Input : "{0}" and "{1}" must be valid int types
INVALID_INPUT_LONG Incorrect Input: "{0}" and "{1}" must be valid long types
INVALID_INPUT_STRING Incorrect Input : "{0}" and "{1}" must be valid String types
INVALID_JOIN_TYPE Invalid Join type
INVALID_KEYSTORE_ALIAS {0} alias is invalid. Only letters, numbers and underscores are allowed
INVALID_KEYSTORE_LOCATION Location ({0}) does not exists
INVALID_KEYSTORE_PROVIDER {0} is not a registered security provider
INVALID_KEYSTORE_TYPE {0} is not a supported Keystore type
INVALID_KEY_SPECIFIED Invalid keyStore {0} specified
INVALID_MAX_BINARY_MESSAGE_SIZE Invalid value for maximum binary message size {0}, should be greater than -1
INVALID_MAX_TEXT_MESSAGE_SIZE Invalid value for maximum text message size {0}, should be greater than -1
INVALID_TRIGGER_DUP_DETECTION {0} triggers do not support the duplicate document detection feature in this release.
INVALID_TRIGGER_MIXED_ALIASES webMethods Messaging trigger {0} is invalid. All document types in the trigger must use the same alias.
INVALID_TRIGGER_MULTI_DEST {0} triggers cannot specify more than one condition or more than one document type within a condition.
INVALID_TRIGGER_SERIAL {0} triggers do not support serial processing mode in this release.
INVALID_XML_CHARACTER The character {0} is not allowed in XML.
INVOKE_IFCNAME_MISSING Service interface name required.
INVOKE_SVCNAME_MISSING Service name required.
WS_ENDPOINT_ACCESS_DENIED Access denied to use the web service endpoint alias {0}.
Class E
Explanation

User does not have permission to use the specified web service endpoint alias.
Action

Using the Integration Server Administrator, examine the Execute ACL property of the web service endpoint alias. Make sure that the current user has the proper ACL to use the web service endpoint alias.

6.4 Error in SSL setup: {0}
Class S
Explanation

The server cannot configure SSL listener or SSL Sockets connections, most likely because of a problem with the SSL configuration settings.

Action

Review the exception message in the log and correct the configuration.
6.6 SSL listener restricted to 128 bit or better encryption.
Class I
Explanation

Integration Server configuration properties watt.net.ssl.client.strongcipheronly or watt.net.ssl.server.strongcipheronly or both are set to "true".

Action

No action is necessary. This message indicates that Integration Server is using strong encryption.
6.13 Peer certificate chain is not present
Class E
Explanation

Integration Server cannot retrieve the peer certificate chain from a client.
Action

Update your client program so that it provides a valid peer certificate to Integration Server.
6.14 SSL handshake failed on port {0} because peer certificate is not in IS Certificate Map, transfer is terminated
Class E
Explanation

While trying to connect to Integration Server, a client presented a certificate that is not contained in the store of client certificates that are mapped to Integration Server users.

Action

To import the client certificate to Integration Server and map it to a valid user, go to the Integration Server Administrator and click Security>Certificates>Configure Client Certificates. For additional information about certificate mapping, refer to the webMethods Integration Server documentation.

6.15 Peer certificate chain is not trusted
Class E
Explanation

While trying to connect to Integration Server, a client presented a certificate that is not trusted by Integration Server.
Action

Add the certificate to the trusted certificates directory for Integration Server. The name of this directory is specified on the Integration Server Administrator under Security>Certificates. For more information about trusted certificates, refer to the webMethods Integration Server documentation.

6.16 SSL handshake failed on port {0}, transfer is terminated
Class E
Explanation

An IOException occurred during the SSL handshake portion of a client's attempt to connect to Integration Server at the indicated port.

Action

Check the server log and error log for possible causes for the error.
6.17 Error in adding trusted certificates: {0}
Class S
Explanation

The Integration Server failed to add the specified CA certificate because it is not in the correct format. The CA certificate must be DER or PEM encoded.

Action

Check the certificate format. Configure CA certificates in DER or PEM format.
6.18 Error in initializing certificate chain verifier: {0}
Class S
Explanation

An error occurred when Integration Server initialized the certificate chain verifier while setting up the specified secure listener.

Action

Check the server log and error log to determine the cause of the error.
6.19 Not including Cipher {0} because it is not a strong Cipher.
Class W
Explanation

Integration Server generates this warning when either the watt.net.ssl.server.strongcipheronly or watt.net.ssl.client.strongcipheronly property is set to "true", and if any of the ciphers identified in either the watt.net.ssl.client.cipherSuiteList or watt.net.ssl.server.cipherSuiteList property are weak.

Action

To stop receiving this warning, remove the specified cipher from the watt.net.ssl.server.cipherSuiteList or watt.net.ssl.client.cipherSuiteList property.

6.20 Cipher ({0}) is not a valid CipherSuiteList.
Class W
Explanation

A CipherSuite specified as a value to either the watt.net.ssl.client.cipherSuiteList or watt.net.ssl.server.cipherSuiteList property is not valid. The invalid CipherSuite is shown in the log message.

One of the ChiperSuite that is specified as a value to either watt.net.ssl.client.cipherSuiteList or watt.net.ssl.server.cipherSuiteList property is not a valid CipherSuite. The invalid CipherSuite is shown in the log message.

Action

Remove the invalid CipherSuite.
9.12 Failed to create certificate: {0}
Class E
Explanation

The certificate specified in the Configure Client Certificates settings has a bad X509Certificate format.
Action

Make sure that the .der file specified in Configure Client Certificates settings is valid.
9.14 A certificate with the same issuer, serial number and usage is already mapped to user {0}.
Class E
Explanation

For a given usage type, only one user can be mapped to a certificate with the same issuer and serial number.
Action

To reassign this certificate to different user, edit the previously mapped certificate and change the user.
9.15 The certificate is already mapped to user {0}.
Class E
Explanation

Integration Server failed to map the client certificate to the user because the client certificate is already mapped to the user specified.

Action

To reassign this certificate to different user, edit the previously mapped certificate and change the user.
9.16 The ISInternal functional alias is not configured properly on the JDBC Pools page. Assign a valid database pool and restart the Integration Server.
Class E
Explanation

Integration Server failed to initilize client certificate mappings because it could not access the ISInternal JDBC Pool.
Action

Assign a valid database pool to ISInternal JDBC funtional alias and restart the Integration Server.
9.17 Certification chain trust verification failed.
Class W
Explanation

At least one of the certificates present in the certificate chain is not trusted by Integration Server.
Action

Check the certificate chain presented to Integration Server for trust verification.
CERT_CHAIN_BROKEN Certificate chain broken: not linked properly
Class E
Explanation

The certificate chain is out of order.
Action

Obtain a valid certificate chain.
CERT_UNSUPPORTED_CRITICAL_EXT Certificate contains an unsupported critical extension
Class E
Explanation

When watt.security.cert.wmChainVerifier.enforceExtensionsChecks property is set to "true", Integration Server checks the presented certificate for unsupported critical extentions. If Integration Server finds a certificate containing unsupported critical extensions, it will reject the certificate and fail the request.

Action

If you enabled Integration Server to perform a certificate extentions check, advise your cleints to use certificates that do not contain unsupported critical extentions. Whether Integration Server enforces a certificate check is configured on the watt.security.cert.wmChainVerifier.enforceExtensionsChecks configuration property.

CERT_EXPIRED Certificate issued to {0} has expired
Class E
Explanation

Unless configured to ignore expired certificates, Integration Server will reject any expired certificates. Whether Integration Server ignores expired certificates is configured on the watt.security.ssl.ignoreExpiredChains configuration property.

Action

Review the server log to see which client's certificate has expired. That client should renew their certificates and resubmit the request with the valid certificate.

CERT_USER_NULL User does not exist for certificate : {0}.
Class E
Explanation

The user associated with the imported client certificate in Integration Server has been deleted.
Action

Ensure that all imported client certificates in Integration Server are associated with a user. If you have deleted the user associated with a client certificate, you can take one of the following actions:

1) Modify the certificate mapping using Security > Certificates > Client Certificates > Details > Change Mapping in the Integration Server Administrator.

2) Add a user with the same name as the deleted user that was associated with the imported client certificate.
12.40 OSGi service for SAML authentication not initialized.
Class E
Explanation

There was a problem while attempting to access Integration Server from the Command Central user interface.
Action

Check the logs located in the Software_AG_directory/profiles/IS/logs directory and make sure that no errors were encountered during the initialization of the OSGi service specified in the error message.

12.41 Unable to initialize SAML authentication module. Cannot get reference of the OSGi service {0}.
Class E
Explanation

There was a problem while attempting to access Integration Server from the Command Central user interface.
Action

Check the logs located in the Software_AG_directory/profiles/IS/logs directory and make sure that no errors were encountered during the initialization of the OSGi service specified in the error message.

12.42 Error while adding Integration Live user: {0}. Error message: {1}. Stack trace: {2}
Class E
Explanation

An unexpected error occurred while adding an Integration Live user.
Action

Contact Software AG Global Support. Please have the following information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

12.44 Unable to get SAML assertion from REST URL {0} because of exception: {1}
Class E
Explanation

An error occurred while retrieving the SAML assertion from REST URL. Refer to the error message text for more details.
Action

Verify the REST URL and ensure that the REST service exists to generate SAML assertion.
18.1 Unable to read MIME types file
Class U
Explanation

During startup, Integration Server was unable to read the MIME types from the file "mime.types", which is located on the <IntegrationServer_dir>\lib directory. The most likely reason is that this file is corrupted.

Action

Contact Software AG Global Support for a copy of this file.
18.2 Deleted group {0} was removed from {1} ACL lists
Class
MUTEX Unlocking thread is not owner
Class E
TARGET_1 target directory does not exist
Class E
Explanation

Directory specified to make the tar (zip) file does not exist in the file system.
Action

Ensure that the directory exists in the file system.
TARGET_2 target is not a directory
Class E
Explanation

Only directories can be zipped. The File name field do not contain the path to a directory.
Action

Ensure that the File name field contains the path to a directory.
TARGET_3 extraction target is not a directory
Class E
Explanation

File name specified to extract a tar file is not a directory. A tar file can be extracted only to a directory.
Action

Enter the directory to which the tar file is to be extracted.
TARENTRY field length exceeded: {0} > {1} ({2}
Class E
Explanation

Integration Server encountered an internal error while adding a file to tar file.
Action

Contact Software AG Global Support.
OUTPUT_1 expected {0} bytes but got {1}
Class E
Explanation

While adding a file to a tar archive, the number of bytes added to the archive is less than the actual size of the file.
Action

Contact Software AG Global Support.
OUTPUT_2 No Tar Entry specified
Class E
Explanation

No directory is provided for zipping.
Action

Ensure that a directory is provided for zipping.
OUTPUT_3 data length is greater than entry specification: {0}
Class E
Explanation

Integration Server encountered an internal error while adding a file to the tar file.
Action

Contact Software AG Global Support.
37.1 Unable to Initialize {0}
Class
37.2 Unable to Shutdown {0}
Class
37.5 Unable to reset job manager {0}
Class
37.6 Unable to reset logfile {0}
Class
37.7 Unable to reset logstream {0}
Class
37.12 Unable to accept requests
Class
GD_DISABLED Guaranteed Delivery Disabled - Please correct error and reinitialize
Class E
42.2 Unsupported Encoding: {0}
Class E
Explanation

Integration Server did not recognize the encoding of the document. Therefore, the default encoding will be used.
Action

If Integration Server successfully uses the default encoding, no action is necessary. Otherwise, change the supplied document so that it has a valid encoding.

AMBIGUOUS_ROOT_MULTI_CONTAINER Cannot uniquely identify the root element : Every element may be contained in at least one other element -- Try loading the DTD from a sample XML document having a DOCTYPE declaration.
Class
AMBIGUOUS_ROOT_MULTI_TOP_ELEMENT Cannot uniquely identify the root element : Multiple elements are topmost elements ({0}) -- Try loading the DTD from a sample XML document having a DOCTYPE declaration.
Class
ELEMENT_DEF_ERROR <!ELEMENT {0} {1}> contains the following error at character {2} of the contentspec: {3}
Class
URI_NOT_DECLARED URI {0} not declared at node {1}
Class U
Explanation

webMethods Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
NODE_REFERENCE_NULL Node reference is null
Class U
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
NODE_IS_NOT_XML Node is not XML
Class U
Explanation

The pub.xml:getXMLNodeIterator service failed to execute because the node object supplied was not an XML node.
Action

Examine the service input and make sure the "node" parameter represents an XML node, not an HTML node.
MOVING_WINDOW_NOT_AVAILABLE Moving window mode is only available when iterating over XML nodes
Class U
Explanation

The pub.xml:getXMLNodeIterator service failed to execute because the XML node supplied did not represent a whole XML document.
Action

Examine the service input and make sure the "node" parameter represents an entire XML document, not an element of an XML document.
MOVING_WINDOW_NOT_FOR_SAX Moving window mode is not available with SAX parsers
Class U
Explanation

The pub.xml:getXMLNodeIterator service failed to execute because the moving window mode is not available with SAX parsers.
Action

Switch to the webMethods parser instead of the SAX parser.
SAX_NO_ENOUGH_DTD_INFO SAX parsers do not expose enough DTD info; try selecting the expandDTD option
Class U
Explanation

The pub.xml:loadXMLNode service failed to execute because it used a SAX parser. Integration Server does not support SAX parsers because they do not expose enough DTD information.

Action

Switch to the webMethods parser instead of the SAX parser.
FIRST_NODE_OF_REGION_NOT_FOUND First node of region not found in node parameter
Class U
Explanation

The pub.web:createRegions service failed to execute because the "regions" parameter did not correctly specify the first node of the region.

Action

Examine the service input for the "regions" parameter and check the query specified for identifying the first node. Make sure the query specified will correctly identify the first node.

LAST_NODE_OF_REGION_NOT_FOUND Last node of region not found in node parameter
Class U
Explanation

The pub.web:createRegions service failed to execute because the "regions" parameter did not correctly specify the last node of the region.

Action

Examine the service input for the "regions" parameter and check the query specified for identifying the ending node. Make sure the query specified will correctly identify the ending node.

49.1 Branch {0}: child {1} not found, default child not found for switch {2}
Class
49.2 Branch {0}: child {1} not found, invoking default child {2}
Class
49.10 Loop {0}: in-array {1} is not an array type.
Class
49.12 Set: invalid encoding: {0}
Class
49.13 Set: {0}
Class E
Explanation

While saving or loading a flow service, Integration Server encountered a problem with the base64 encoding of a Map operation.
Action

Contact Software AG Global Support.
49.15 Loop {0}: out-array is not the same length as in-array.
Class
49.16 Flow timed-out at {0}
Class
49.18 Branch {0}: no expressions evaluated true and no default child found
Class
49.19 Branch {0}: no expressions evaluated true, but default child found
Class
NO_ANCESTOR FlowExit ''{0}'' -- no valid ancestor to exit from $loop
Class E
Explanation

In a flow service, the Exit operation failed because an ancestor loop was not found.
Action

Move the Exit operation to be a child of a Loop or Repeat step. Alternatively, set the exit-on property for the Exit operation to a value other than $loop.

NO_COMPLEX_GET get: complex path is not supported
Class E
Explanation

A flow service tried to perform a get operation on a complex path, but Integration Server does not support complex path types. This is an internal error.

Action

Contact Software AG Global Support.
NO_COMPLEX_PUT put: complex path is not supported
Class E
Explanation

A flow service tried to perform a put operation on a complex path type, but Integration Server does not support complex path types. This is an internal error.

Action

Contact Software AG Global Support.
NO_COMPLEX_DELETE delete: complex path is not supported
Class E
Explanation

A flow service tried to perform a delete operation on a complex path, but Integration Server does not support complex path types. This is an internal error.

Action

Contact Software AG Global Support.
FAILED_INPUT_VALIDATION Input validation for service ''{0}'' failed: ''{1}''
Class E
Explanation

During service execution, Integration Server detected that the contents of the pipeline did not conform to the defined input signature of the service.

Action

Ensure that the inputs in the pipeline match the input signature of the flow service, or disable input validation for this service.

FAILED_OUTPUT_VALIDATION Output validation for service ''{0}'' failed: ''{1}''
Class E
Explanation

Upon completion of a service, Integration Server detected that the contents of the pipeline did not conform to the defined output signature .

Action

Ensure that the outputs in the pipeline match the defined output signature or disable output validation for this service.
NO_INPUT_VALIDATOR Failure creating input validator for ''{0}''
Class E
Explanation

During execution of a flow service, Integration Server determined that it could not create an input Validator from the parameters provided.

Action

Contact Software AG Global Support.
NO_OUTPUT_VALIDATOR Failure creating output validator for ''{0}''
Class E
Explanation

During execution of a Flow service, Integration Server determined that it could not create an output Validator from the parameters provided. This is an internal error.

Action

Contact Software AG Global Support.
NO_PROP_SWITCH Missing required property 'switch' at ''{0}''
Class E
Explanation

The Branch step has no switch property value.
Action

Specify the name of an pipeline object that is to be used as the switch value for the Branch step.
BAD_PROP_SERVICE Service ''{2}'' invoking unknown service ''{1}'' at ''{0}''. The service may have been renamed, moved or disabled.
Class E
Explanation

The failing flow service attempted to execute another servcie that could not be located or could not be executed. The most likely cause is that the target service has been removed or renamed.

Action

Determine the new name or location of the target service and modify the failing flow service to correctly identify the target service.

NO_PROP_IN_ARRAY Missing required property 'in-array' at ''{0}''
Class E
Explanation

The Loop step has no input array property.
Action

Specify the name of a pipeline object to use as the input array.
INVALID_SWITCH_LABEL Cannot define 'switch' and use label conditions at ''{0}''
Class E
Explanation

Integration Server tried to execute a Branch step, but the Branch properties were specified incorrectly. Specifically, the "evaluate labels" property was set to "true" while the "switch" property specified an expression. This is not a valid combination.

Action

Change the Branch step properties to either specify a switch value and set "evaluate-labels" to false, or do not specify a switch value and set "evaluate-labels" to true.

TIMEOUT Timeout at ''{0}''
Class E
Explanation

A step in a flow service exceeded its timeout value before returning.
Action

This is desired behavior. Examine the underlying services that did not return in time to determine the cause of the timeout.
BAD_SCOPE Scope ''{0}'' not found or invalid
Class E
Explanation

At run time, Integration Server could not resolve the scope of the pipeline in a flow step. The scope resolved to an object that was not an IData.

Action

Make sure that the path in the scope property resolves to an IData object at run time.
BAD_LABEL FlowExit ''{0}'' - label not found: ''{1}''
Class E
Explanation

In a flow service, the Exit operation failed because it could not locate the label anywhere in the ancestry of the Exit step.
Action

Make sure that an ancestor flow step has a label that matches the one in the Exit step.
BAD_SCOPE_PATH Invalid scope path
Class E
Explanation

At run time, Integration Server could not resolve the pipeline scope specified for a flow step because the syntax of the scope property is not valid.

Action

Make sure that the path syntax of the scope property is valid.
ILLEGAL_PATH (1) Illegal path from: ''{0}''
Class E
Explanation

In the pipeline, the map path for the source or destination is empty.
Action

If this error occurs while editing a flow service, save the flow service and then reload it.
CANT_COPY_PATH The path has been used: {0}
Class E
Explanation

More than one mapping operation is being performed on a pipeline object.
Action

Only one operation may be performed on a pipeline object in a Map step. Remove all but one of the map operations for the pipeline object, or ensure that only one operation is attempted at run time.

BAD_COPY More than one copy into the path with different common parent(s).
Class I
Explanation

When mapping data in the pipeline, under a single Map step, you tried to map from documents to two different document fields under a common parent. However, the source documents have different dimensions.

Action

Separate the data mapping into two different Map steps.
DATA_TYPE_NOT_MATCH Data type does not match the path.
Class E
Explanation

A pipeline mapping operation specifies a target type that does not match the source type at run time.
Action

Ensure that the source type at run time matches the target type specified by the map operation.
CANNOT_COPY Cannot make the copy from: {0} to: {1}
Class E
Explanation

While executing mapping in a flow step, Integration Server determined that it could not copy one field to another because the elements were of incompatible types.

Action

Make sure that the field types are compatible and have the same dimensions.
INVALID_SOURCE_PATH Invalid source path.
Class E
Explanation

While trying to execute a map between fields, Integration Server determined that no source field was specified.
Action

In the pipeline, make sure that a source field is specified.
INVALID_TARGET_PATH Invalid target path.
Class E
Explanation

While trying to execute a map between fields, Integration Server determined that no target path was specified.
Action

In the pipeline, make sure that tha the map specifies a target destination.
TRANSFORMER_LOOP_ERR Error at {0} - Transformers cannot loop over list elements
Class E
Explanation

A Map step includes a link from an array variable in Pipeline In to a scalar input variable for a transformer.
Action

Do one of the following: - Remove the mapping between the array variable in Pipeline in and the scalar input variable for the transformer. - Change the service invoked by the transformer to accept arrays as data. - Create a flow service in which a LOOP step loops over the array variable. Then, (in the same flow service) invoke the service you originally wanted to use as a transformer, and make that Invoke step a child of the Loop. Finally, insert the resulting flow service as a transformer in the Map step.

GLOBAL_VARIABLE_DOES_NOT_EXIST Global Variable {0} does not exist.
Class E
Explanation

The global variable that you assigned to a variable in the flow service does not exist in Integration Server.
Action

Ensure that global variable exists in IS, if it does not exist then contact IS Admin to add this Global Variable.
50.2 Invalid pipeline mapping: Cannot map two pipeline variables into the same field.
Class
50.3 Pipeline variable sources have different dimensions.
Class
50.4 Copy failed: {0}: to={1}, from={2}
Class
50.5 Set failed: {0}: field={1}
Class
50.7 Failed size check on path {0}
Class
50.8 No valid value objects for path {0}
Class
50.9 Data check: data type mismatch
Class
50.13 Copy failed: No source data available from {0}
Class
50.14 Field {0} incorrectly declared as array type
Class
50.15 Incomplete path: null value for {0}
Class
50.16 Cannot create object for the class: {0}
Class
50.17 Error encoding schema in FlowMap {0}
Class E
Explanation

While saving a flow service, Integration Server encountered an error trying to encode the input or output of a Map step.
Action

Contact Software AG Global Support.
50.18 Error decoding schema in FlowMap {0}
Class E
Explanation

While loading a flow service, Integration Server encountered an error trying to decode the input or output of a Map step.
Action

Contact Software AG Global Support.
50.19 Copy failed: No source data available: to={0}, from={1}
Class
50.20 Copy failed: Cannot create target data: to={0}, from={1}
Class
50.21 Copy failed: Cannot support the required class name: to={0}, from={1}
Class
62.1 CreateRegions createNsDecls type not supported
Class
62.2 CreateRegions createRegions type not supported
Class E
Explanation

The pub.web:createRegions service failed to execute because the input provided for the "regions" parameter was not an instance of IData[ ].

Action

Examine the service input make sure the "regions" parameter specifies an instance of IData[ ].
62.3 GenerateQueryString {0} setValues {1}
Class U
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
62.4 GenerateQueryStrings createFields type not supported
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
62.5 GenerateQueryStrings createNodeIDs type not supported
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
62.6 GenerateQueryStrings the bind failed
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
62.7 GetDocAsTable nodeTypeToString: {0} unknown type
Class U
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
62.8 MakeRules.makeNSRecordFromDTD root of doc:{0} sig:{1}
Class
62.9 MakeRules.makeNSRecordFromDTD root of doc:null
Class
62.10 MakeRules.findElementDef name {0} not found in DTD:{1}
Class
62.11 MakeRules.makeRecord ERROR ConnectParticleName:{0}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
62.12 MakeRules.generateFlowFromDTD node parameter is null
Class
62.13 MakeRules.generateFlowFromDTD no output signature
Class
62.14 QueryDocWithIdentity createFields type not supported:{0}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
62.15 QueryDocWithIdentity createNsDecls type not supported:{0}
Class
62.16 queryXMLNode createFields type not supported:{0}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
62.17 {0} createNsDecls type not supported:{1}
Class
62.18 DocumentToXMLString boundNode argument is null
Class U
Explanation

The pub.xml:documentToXMLString service failed to execute because the required "document" parameter was missing. This parameter specifies the name of the document to be converted to XML.

Action

Examine the service input and make sure it specifies a value for the "document" parameter.
62.19 ERROR unsupported type:{0} !!!!
Class
62.22 Server encountered an unknown error: {0}
Class
62.32 Invalid number format: {0}
Class
62.33 Illegal parameter value. {0} is too many root elements in boundNode. Number attributes:{1}.
Class
62.34 loadXMLNode called client.http pipe: {0}
Class
62.36 Invalid port number {2} for {3}
Class
62.37 loadXMLNode service encountered unsupported encoding: {0}
Class
SERVICE_ARGUMENT_NULL boundNode parameter is null
Class U
Explanation

The pub.xml:documentToXMLString service failed to execute because the required "document" parameter was missing.
Action

Examine the service input and make sure it contains the document to be converted in the form of an IData object.
ILLEGAL_XML_NAME Namespace prefix name "{0}" for uri {1} is not legal XML name
Class U
Explanation

The pub.xml:documentToXMLString service failed to execute because it detected illegal characters in the namespace prefix of the document to be converted. Integration Server flags invalid characters in the namespace prefix only if the value for the "enforceLegalXML" parameter is set to "true".

Action

To resolve this error, do one of the following:

(1) Set the input for the "enforceLegalXML" parameter to "false". This causes the service to produce an XML fragment.

(2) Make sure the input for the "nsDecls" parameter specifies a namespace prefix that starts with a letter or the underscore "_" character. In addition, it can only contain letters, digits, and the period ".", hyphen "-", and underscore "_" characters.

TOO_MANY_ROOTS Illegal parameter value. {0} is too many root elements in boundNode. Number attributes:{1}
Class U
Explanation

The pub.xml:documentToXMLString service failed to execute because the document to be converted contains multiple root elements. Integration Server flags this condition only if the input for the "enforceLegalXML" parameter is set to true.

Action

Examine the service input and make sure the "enforceLegalXML" parameter is set to "false". This will cause the service to produce an XML fragment composed of the multiple elements that were not enclosed within a root element.

ILLEGAL_ATTRIBUTE_NAME Attribute name "{0}" is not legal XML name
Class U
Explanation

The pub.xml:documentToXMLString service failed to execute because the prefix that designates the keys that contain attributes contains illegal characters. Integration Server flags this condition only if the input for the "enforceLegalXML" parameter is set to true.

Action

To resolve this error, do one of the following:

(1) Set the input for the "enforceLegalXML" parameter to "false" . This will cause the service to produce an XML fragment.

(2) Make sure the input for the "attrPrefix" parameter starts with a letter or underscore "_" character. In addition, it can only contain letters, digits, and the period ".", hyphen "-", and underscore "_" characters.

ILLEGAL_ELEMENT_NAME Element name "{0}" is not legal XML name
Class U
Explanation

The pub.xml:documentToXMLString service failed to execute because the document being converted contains illegal XML tag names. Integration Server flags this condition only if the input for the "enforceLegalXML" parameter is set to true.

Action

To resolve this error, do one of the following:

(1) Set the input for the "enforceLegalXML" parameter to "false". This causes the service to produce an XML fragment.

(2) Make sure the input for the "'document" parameter starts with a letter or underscore "_" character. In addition, it can only contain letters, digits, and the period ".", hyphen "-", and underscore "_" characters.

RECORD_NOT_FOUND Illegal parameter value. Document Type "{0}" not found.
Class U
Explanation

The pub.xml:xmlNodeToDocument service failed to execute because the "documentTypeName" was specified, but the document it represents does not exist on the Integration Server namespace.

Action

Examine the service input and make sure the "documentTypeName" parameter specifies the fully qualified name of the document type. Remember that namespace element names are case-sensitive.

COLLECTION_PARA_MUST_BE_NULL_REC collect parameter must be null when using recordName parameter
Class E
MAKEARRAY_PARA_MUST_BE_FALSE_REC MakeArrays parameter must be false when using recordName parameter
Class
ARRAY_PARA_MUST_BE_NULL_REC Arrays parameter must be null when using recordName parameter
Class
RECORD_PARA_MUST_BE_NULL Records parameter must be null when using recordName parameter
Class
NO_RECORD_GEN Internal error: no record generated by makeNSRecord
Class
NO_NSNAME_GEN Internal error: no NSName generated
Class
FOUND_NESTED_CP MakeRules.recursiveCollectRecordRefs found nested ContentParticleSet
Class
NO_ELEMENT_DEF_FOUND MakeRules.findElementDef no element definitions found
Class
NO_ELEMENT_DEF_NAME_FOUND MakeRules.findElementDef name "{0}" not found in DTD
Class
DOCUMENT_NODE_PARA_NULL XML node parameter is null
Class
NO_NSRECORD_GEN No NSRecord generated for package "{0}" Document Type "{1}"
Class
DOCUMENT_NODE_NULL XML node is null
Class
RECORD_ALREADY_EXISTS Document Type "{0}" already exists.
Class
OBJECT_IS_NULL "object" is null
Class U
Explanation

The object to be validated does not exist in the pipeline.
Action

Link an XML node or document variable to the object variable in Service In.
OBJECT_DOES_NOT_EXISTS "{0}" - object does not exist
Class U
Explanation

The document type or schema specified for the "conformsTo" parameter does not exist in the Integration Server namespace.
Action

Change the value of the "conformsTo" parameter to be a document type or schema that exists in the Integration Server namespace.
CONFORMS_PARA_NULL conformsTo parameter is null
Class U
Explanation

While executing the pub.schema:validatePipeline service, the Integration Server determined that no value was specified for the "conformsTo" property, which is a required parameter. This parameter specifies the IS document or IS schema against which the Integration Server performs validation.

Action

Specify a value for the "conformsTo" parameter that is an IS document type or schema type that exists in the IS namespace.
NOT_SUPPORTED Integration Server does not support this type of object in validation {0}
Class U
Explanation

The object to be validated is not one of the types supported by validation.
Action

Currently, only XML, pipeline, and document (IData object) validation are supported.
COLLECTION_PARA_MUST_BE_NULL collect parameter must be null when using documentTypeName parameter
Class
MAKEARRAY_PARA_MUST_BE_FALSE MakeArrays parameter must be false when using documentTypeName parameter
Class
ARRAY_PARA_MUST_BE_NULL Arrays parameter must be null when using documentTypeName parameter
Class
DOCUMENTS_PARA_MUST_BE_NULL Documents parameter must be null when using documentTypeName parameter
Class
SCHEMA_DOMAIN_MISMATCH The schema domain of the conformsTo object must match the schemaDomain parameter
Class
QUERY_WRONG_TYPE When node is an enhanced XML node, queryType must be XQL
Class E
Explanation

The queryType input parameter is set to WQL but the node is an enhanced XML node. Only XQL can be used to query an enhanced XML node.

Action

Set queryType to XQL and rewrite the query to use XQL instead of WQL.

63.6 Generate Transaction Ids {0}
Class
63.17 Retrieve completed job tid={0}
Class
63.20 Error (see job log) tid={0}
Class
63.27 Error loading tid={0}; skipping ...
Class
63.36 Can Still Retry {0}
Class
63.42 Job Manager not initialized.
Class
63.45 Deregister - already 0
Class
63.46 Jobs still active on shutdown
Class
63.49 Start for Nonexistent Tid={0}
Class
63.50 Job Expired for Tid={0}
Class
63.52 Retrieve on Nonexistent Tid={0}
Class
63.53 Retrieve on new job
Class
63.54 Retrieve on heuristic failure
Class
63.55 Retrieve on expired job
Class
63.56 Job Timed Out for Tid={0}
Class
63.58 Restart for Nonexistent Tid={0}
Class
63.59 Restart for Ended Tid={0}
Class
63.60 Restart on active Tid={0}
Class
63.61 Restart on non-pending Tid={0}
Class
63.62 Status for non-existent Tid={0}
Class
63.63 ChainedWait for non-existent Tid={0}
Class
63.64 Get Remote TID for non-existent Tid={0}
Class
63.69 Administrator email is not set.
Class
63.70 Administrator email is {0}.
Class
63.71 Logfile used:{0}. Jobdir used:{1}.
Class
63.72 {0} broke lock for guaranteed job, tid={1}.
Class
63.73 The IS Internal database pool is not configured properly. Assign a valid database pool for the "ISInternal" functional alias and restart the Integration Server.
Class E
Explanation

The ISInternal functional alias on the Settings > JDBC Pools page in the Integration Server Administrator is not properly configured, or the database it refers to is unavailable.

Action

Configure the ISInternal functional alias on the Settings > JDBC Pools page in the Integration Server Administrator and use the "Test" button to verify that it can connect to the database. After configuring the ISInternal functional alias, restart the Integration Server.

63.74 End for Nonexistent Tid={0}
Class
63.75 Failed to obtain repository context : {0}
Class
63.78 Unable to accept requests
Class
63.79 End: Invalid Transaction Id
Class
63.80 Unable to accept requests
Class
63.84 Unable to accept requests
Class
63.86 Unable to accept requests
Class
63.90 No Output Writer specified
Class
63.98 Not a custom stream
Class
63.100 Not a custom Writer
Class
63.101 Don't close user stream
Class
63.103 {0} property is invalid. Using default value of {1}.
Class
63.104 {0}:{1} did not create remote tid
Class
64.1 HttpContext cannot clone self
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
64.11 Invalid maxRedirects setting {0}
Class W
Explanation

The watt.net.maxRedirects property is not valid. It must be an integer.
Action

Change the value of the watt.net.maxRedirects property to an integer.
64.12 Class not found: {0}
Class E
Explanation

Integration Server encountered an internal error because it could not find a class in the namespace.
Action

Contact Software AG Global Support.
64.18 Unable to instantiate class: {0}
Class E
Explanation

Integration Server encountered an internal error because it could not instantiate a class in the namespace.
Action

Contact Software AG Global Support.
64.29 Could not open Socket connection to proxy={0} Exception:{1}
Class D
Explanation

An exception was encountered while making an FTP connection through a proxy server. See the exception for details.
Action

Check that the FTP proxy you are using is correctly configured on the Settings > Proxy Servers page of Integration Server Administrator.

64.30 The {0} property is not a valid integer: {1}.
Class W
Explanation

An invalid value was specified for the property identified in the message. The value for this property must be an integer.
Action

Change the value of the property to an integer.
64.31 Unexpected NTLM message sequence. The expected message type is not NTLM Type 1 Message.
Class E
Explanation

The provided NTLM authentication credentials are not valid.
Action

Provide valid NTLM authentication credentials.
FTP_CONNECT_ERROR Could not connect to ftp server: {0}
Class E
Explanation

FTP server is not accessible.
Action

Ensure that the FTP server and port are valid. If FTP proxy is configured in Integration Server, ensure that the proxy settings are correct.

FTP_INVALID_HOST_PORT FTP host name or port number is not specified
Class E
Explanation

FTP hostname cannot be null and port cannot be zero.
Action

Ensure that you provide valid values for FTP host and port fields.
FTP_PROXY_ERR Fail to connect to FTP proxy: {0}+ port: {1}
Class
FTP_SERVER_CONNECT_ERR Fail to connect to FTP server: {0} port: {1}
Class E
Explanation

Integration server is unable to access the FTP server.
Action

Ensure that the FTP host and port fields contain valid values. If FTP host and port fields contain valid values and if Integration Server is still unable to access FTP server, contact Software AG Global Support.

FTP_LOGIN_FAILED {0}
Class E
Explanation

Credentials of the FTP user are invalid.
Action

Ensure that the FTP user, password, and account fields have correct and valid values. Set the log level of Network Services component (64) to 'trace' to get more details.

FTP_SITE_FAILED {0}
Class E
Explanation

FTP proxy server that you have configured does not support the SITE command.
Action

Check the FTP proxy server configuration to ensure that the FTP proxy server supports the SITE command. Set the log level of Network Services component (64) to 'trace' to get more details.

FTP_OPEN_FAILED {0}
Class E
Explanation

FTP proxy server that you have configured does not support the OPEN command.
Action

Check the FTP proxy server configuration to ensure that the FTP proxy server supports the OPEN command. Set the log level of Network Services component (64) to 'trace' to get more details.

FTP_PORT_FAILED FTP PORT command failed
Class E
Explanation

FTP server encountered an error while sending the PORT command.
Action

The following lists the actions you can take:

1. Ensure that the FTP server implements the PORT command.

2. Ensure that the user has the permission to execute the command.

3. If the problem still persists, contact Software AG Global Support. Set the log level of Network Services component (64) to 'trace' to get more details.

FTP_INVALID_DATA_CH Invalid Data Channel
Class E
Explanation

FTP client is not able to create a data port for listening. In FTP Active mode, client creates a port for data connection and FTP server opens a connection to the client data port.

Action

Ensure that the data port specified in the FTP client is available.

-OR-

Use FTP passive transfer mode.

Set the log level of Network Services component (64) to 'trace' to get more details.
FTP_ACCEPT_ERR {0}
Class E
Explanation

FTP server is not able to connect to the data port of the client. The possible cause for this is that the data port might be blocked by a firewall on the client side.

Action

The following lists the actions you can take:

1. Check whether the client is behind a firewall. If yes, make sure that the firewall allows the connection from the server.

2. Use FTP passive transfer mode.

3. Increase the connection timeout of data port using watt.net.ftpClientDataConnTimeout property.
FTP_SOCKET_CLOSE_ERR Socket close err. {0}
Class E
Explanation

FTP server encountered an error while closing the FTP client socket.
Action

Contact Software AG support team.
FTP_WELCOME_MSG_ERR {0}
Class E
Explanation

FTP server is not accessible.
Action

Contact Software AG support team. Set the log level of Network Services component(64) to trace to get more details.
FTP_FTP_SEND_ERR Content must be of type byte[], String or InputStream
Class E
Explanation

The content type of the data sent to the FTP server is not of type byte array, string, or InputStream.
Action

Make sure that the data sent to the FTP server is of type byte array, string, or InputStream.
FTP_AUTH_CMD_ERR FTP AUTH command failed with error code {0}
Class E
Explanation

An FTP client sent an AUTH command to establish an FTPS connection with the Integration Server, but the command failed with the indicated return code.

Action

Check your FTP documentation for the possible causes of the FTP return code. In addition, check the server log and error log for possible causes for the error.

FTP_SSL_SETUP_ERR FTP AUTH command failed with error {0}
Class E
Explanation

An FTP client sent an AUTH command to establish an FTPS connection with the Integration Server, but the command failed.
Action

Check your FTP documentation for the possible causes of the FTP error message. In addition, check the server log and error log for possible causes for the error.

FTP_PBSZ_CMD_ERROR FTP PBSZ command failed with error code {0}
Class E
Explanation

An FTP client sent a PBSZ command to establish a secure connection between the client and Integration Server, but the command failed with the indicated return code.

Action

Check your FTP documentation for the possible causes of the FTP error message. In addition, check the server log and error log for possible causes for the error.

FTP_PROT_CMD_ERROR FTP PROT command failed with error code {0}
Class E
Explanation

An FTP client sent a PROT command to establish a secure connection between the client and Integration Server, but the command failed with the indicated return code.

Action

Check your FTP documentation for the possible causes of the FTP error message. In addition, check the server log and error log for possible causes for the error.

FTP_EPRT_FAILED FTP EPRT command failed with error {0}
Class E
Explanation

The FTP server returned an error for the EPRT command sent by the Integration Server FTP client.
Action

Ensure that the FTP server implements the EPRT command. Ensure that the user has the permission to execute the command. Set the log level of Network Services facility (facility number 64) to 'trace' to get more details. If the problem persists, contact Software AG Global Support.

72.10 Index {0} out of bounds for key {1}
Class
72.11 value missing name. key={0}
Class
72.14 LoopToken.evalArray unknown array type:{0}
Class
72.16 Exception:{0} executing included template.
Class
72.17 IfVarToken.processArgs value:{0} index:{1} ret:{2}
Class
REPORTER_1 Unknown service: {0}
Class E
Explanation

Integration Server encountered an internal error because it could not find a requested service in the namespace.
Action

Contact Software AG Global Support.
REPORTER_2 Reporter died from IOException: {0}
Class E
Explanation

The Reporter.createTemplateFromFile() class issued an error because it could not read the template from the supplied file.
Action

Examine the use of the Reporter class in your application and make sure that the application has proper Read access to the template file.

76.1 BinCoder decode error creating IData {0}, using {1} instead. Excpt:{2}
Class
76.2 BinCoder decode error creating IDataCodable {0}, using {1} instead. Excpt:{2}
Class
76.3 BinCoder decode error creating Codable {0}. Excpt:{1}
Class
76.4 BinCoder decode error creating as String {0}, s={1}. Excpt:{2}
Class
76.5 BinCoder decode error creating Java serialized object. Excpt:{0}
Class E
Explanation

The java.io.ObjectInputStream.readObject() service encountered an error while trying to decode a Java serialized object. For a ClassNotFoundException, the most likely cause is that a client performing a remote invoke placed a class definition into the pipeline, but the class definition does not exist on the receiving Integration Server. For an InvalidClassException, the most likely cause is that the class definition on the Integration Server does not match the class definition placed in the pipeline by the client.

Action

Make sure that the originating client and the receiving Integration Server have the same class definitions. For other I/O exceptions, there might be corruption in the input stream; therefore, you should try the request again.

76.6 BinCoder decode error creating array {0}
Class
76.7 XMLCoder decode invalid data type: {0}
Class
76.8 XMLCoder decode exception: {0}
Class E
Explanation

Integration Server threw an exception while decoding an IDataXML encoded document.
Action

The document is corrupt. Contact Software AG Global Support.
76.9 RPCBinCoder2 decode error for array class: {0}
Class E
Explanation

Integration Server encountered an error while trying to decode an array of remote objects. Class definitions might be out of sync.

Action

Contact Software AG Global Support.
76.10 RPCBinCoder2 decode error for Codable class: {0}
Class E
Explanation

Integration Server encountered an error while trying to decode a codable class. Class definitions might be out of synch.
Action

Contact Software AG Global Support.
76.11 RPCBinCoder2 decode error for as_String class: {0}
Class E
Explanation

Integration Server encountered an error while trying to decode an object that was encoded as a String.
Action

Contact Software AG Global Support.
76.12 SOAP Encoding Registrar cannot register schema type {0}; schema type already exists.
Class E
Explanation

The SOAP Encoding Registrar could not register the indicated schema type. This is a serious internal error.
Action

Contact Software AG Global Support.
76.13 SOAP Message Coder cannot encode output data; pipeline does not match output signature
Class E
Explanation

The SOAP message coder could not XML-encode the results of a SOAP remote procedure call because a variable appeared in the pipeline more than once.

Action

Examine the target service to determine why it is not producing output values that match the output signature. Correct the service's signature and/or logic after identifying the source of the problem.

76.14 SOAP Message Coder failure; a RuntimeException was thrown in the SOAP Coder
Class U
Explanation

The message coder encountered a serious internal error.
Action

Contact Software AG Global Support.
76.15 SOAP Message Coder cannot encode variable {0}; variable does not have a valid XML name
Class E
Explanation

The message coder could not XML-encode the SOAP RPC request or response because the pipeline contained the variable <varName>, whose name is not a valid name for an XML element.

Action

This error often occurs because the variable name contains a colon (:). Change the name of <varName> to one that is also valid as an XML element name (or map <varName> to a new variable, and use that variable as your SOAP RPC input or output parameter).

76.16 Soap Message Coder warning; unregistered coder for variable {0}, using String
Class
76.17 SOAP Message Coder error; no coder is registered for encoding style {0}
Class E
Explanation

The message coder encountered a serious internal error.
Action

Contact Software AG Global Support.
76.18 Soap Message Coder warning; unregistered coder for variable {0}, using BasicData
Class
76.19 SOAP Message Coder cannot decode message; encoding style {0} is not a registered style
Class E
Explanation

The message coder could not decode the submitted XML because it does not support the specified encoding style.
Action

Check the incoming XML and verify that the encodingStyle attribute is specified correctly and that it specifies a style that Integration Server supports.

76.20 Soap Message Coder warning; invalid HREF found {0}
Class E
Explanation

The message coder could not resolve the href pointing to reference. A null value was produced instead.
Action

Examine the incoming XML and make sure that the specified reference points to an element that exists in the body of the message.
76.21 SOAP Message Coder cannot decode message; arrayType attribute value {0} is malformed
Class E
Explanation

The message coder could not decode an XML-encoded array because it cannot understand the value of the "arrayType" attribute.
Action

Check the incoming XML and make sure that the "arrayType" attribute is using the correct syntax. For example, make sure that it is not missing a "[" symbol.

76.22 SOAP Message Coder cannot decode message; cannot determine type of element {0}
Class E
Explanation

The message coder could not decode the XML-encoded parameters it has received, because the simple element <elementName> has an unknown data type (for example, xsi:type="myDataType").

Action

Check the incoming XML and make sure the data type has been specified correctly. Also make sure that it is using the correct namespace.

76.23 SOAP Message Coder cannot decode message; unable to create array for arrayType attribute value {0}
Class E
Explanation

The message coder could not decode an XML-encoded array because it could not allocate an array of the specified dimensions.
Action

Check the incoming XML and make sure that the arrayType attribute is specified correctly. For example, make sure that it does not specify a negative dimension or an invalid array size (e.g., too many dimensions or dimensions that are unrealistically large). If the array is unusually large or the server is extremely very low on memory, the possibility also exists that this error was the result of an out-of-memory condition.

76.26 Broker Coder cannot encode document; the document, document type or both are null values
Class E
Explanation

While attempting to process a document from the Broker, Integration Server determined that the document, the document type, or both are null values. This is an internal error.

Action

Contact Software AG Global Support.
76.27 Broker Coder cannot encode document; Broker document type name is missing
Class E
Explanation

The subscribing Integration Server received a document from the Broker or a publishing Integration Server, but was unable to encode the document because the document type name was missing from the event subscription. There are three possible reasons: (1) the document to be encoded is corrupted (2) the document type is out of sync with the corresponding document type on the Broker (3) an internal error occurred.

Action

Examine the document to be encoded and synchronize the document type with the Broker. If the error persists after the synchronization, contact Software AG Global Support.

76.28 Broker Coder cannot decode document; byte[] is in wire format version {0}. Latest supported format is version {1}
Class
76.29 Broker Coder warning; multi-reference with sequence id {0} does not exist; using null value
Class
76.30 Broker Coder warning; cannot parse value {0}; using {1} instead
Class E
Explanation

Integration Server was not able to parse the document. There are two possible reasons: (1) the document might be corrupted (2) the document type is out of sync with the corresponding document type on the Broker.

Action

Examine the document and make sure that it is not corrupted. Also, synchronize the document type with the corresponding Broker document type.

76.31 Broker Coder warning; cannot create an instance of {0}
Class E
Explanation

Integration Server could not create an instance of the indicated class. This is an internal error.
Action

Contact Software AG Global Support.
76.32 Broker Coder cannot decode document; the document, document type or both are null values
Class
76.33 Broker Coder cannot decode document; the document does not conform to the document type, {0}
Class E
Explanation

The subscribing Integration Server was not able to decode the incoming document from either the Broker or the publishing Integration Server because the document type on the local Integration Server is out of sync with the corresponding document types on the publishing Integration Server and the Broker.

Action

Synchronize the publishable document type on the subscribing Integration Server with the corresponding Broker document type.
76.34 The {0} class loader could not load class {1} while decoding. Trying next classloader.
Class
IDATABINCODER_DECODE_IO Unsupported RPC type: {0}
Class U
Explanation

Integration Server RPC Bin Coder does not support the version specified in the input stream to be decoded. This is an internal error.

Action

Contact Software AG Global Support.
IDATAXMLCODER_DATATYPE incorrect IDataXMLCoder file format: no element 'IDataXMLCoder' found
Class U
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
IDATAXMLCODER_ENCODING encoding {0}
Class U
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
IDATAXMLCODER_DECODING decoding: {0} ex:{1}
Class U
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
IDATAXMLCODER_DECODING_1 decoding: boolean ex:{0}
Class U
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
IDATAXMLCODER_DECODING_2 decoding: {0}
Class U
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
IDATAXMLCODER_RECORDDECODE decoding: No null-arg create method in class: {0}
Class U
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
RPCBINCODER_UNSUPPORT Unsupported RPC type: {0}
Class U
Explanation

Integration Server RPC Bin Coder does not support the version specified in the input stream to be decoded. This is an internal error.

Action

Contact Software AG Global Support.
XMLCODER_ROOTNULL Root element is null
Class U
Explanation

The flow.xml or node.ndf file is corrupt.
Action

Contact Software AG Global Support.
XMLCODER_ROOTTAG Sibling root element is null rootTag:{0} localName:{1} root:{2}
Class U
Explanation

The XMLCoder class issued an error because the supplied XML input stream cannot be decoded.
Action

Examine the use of the XMLCoder class in your application and make sure that the XML input stream has the correct format and it only contains supported object types. If the error still occurs, use the setIgnoreInvalid() class to set the flag to false so that XMLCoder ignores the unsupported object type that it decodes.

XMLCODERWRAPPER_FILE illegal file format
Class U
Explanation

The service pub.flow:restorePipelineFromFile failed to execute because the file containing the saved pipeline was not encoded with XMLCoder or IDataXMLCoder.

Action

Examine the file containing the saved pipeline and make sure it is not corrupt. If the file was saved using the pub.flow:savePipelineToFile service, and it is not corrupt, contact Software AG Global Support.

JSONCODER_INVALID_JSON_STREAM Invalid state. JSON input stream does not start with the "{" character.
Class E
Explanation

The input stream does not contain valid JSON content. JSON content must begin with the "{" character.
Action

Add a "{" character to the beginning of the JSON content.
JSONCODER_NO_OBJECT_END Invalid state. JSON Object in the input stream does not end with "}" character.
Class E
Explanation

The JSON object in the input stream does not contain valid JSON content. The JSON object content must end with the \"}\" character.
Action

Add a \"}\" character to the end of the JSON object.
JSONCODER_INCORRECT_SYNTAX Invalid state. JSON input stream contains incorrect syntax.
Class E
Explanation

The JSON input stream contains incorrect JSON syntax.
Action

Correct the errors in the JSON input stream.
JSONCODER_NO_OBJECT_START Invalid state. JSON Object in the input stream does not start with "{" character.
Class E
Explanation

The JSON object in the input stream does not contain valid JSON content. The JSON object content must begin with the "{" character.
Action

Add a "{" character to the beginning of the JSON object in the input stream.
JSONCODER_NO_ARRAY_END Invalid state. Array in the JSON input stream does not end with "]" character.
Class E
Explanation

The JSON array in the input stream does not contain valid JSON content. The JSON array must end with the "]" character.
Action

Add the "]" character from the end of the JSON array.
JSONCODER_INVALID_INT_NUMBER Numeric value ({0}) for field {1} is outside the range for integer values. Integers must be within the range of -2147483648 to 2147483647. Error:{2}
Class E
Explanation

Integration Server encountered an invalid integer value while parsing a JSON object.
Action

Correct the value before parsing the JSON object.
JSONCODER_INVALID_LONG_NUMBER Numeric value ({0}) for field {1} is outside the range for long numbers. Long numbers must be within the range of -9223372036854775808 to 9223372036854775807. Error:{2}
Class E
Explanation

Integration Server encountered an invalid long number value while parsing a JSON object.
Action

Correct the value before parsing the JSON object.
JSONCODER_INVALID_FLOAT_NUMBER Numeric value ({0}) for field {1} is outside the range for float values. Error:{2}
Class E
Explanation

Integration Server encountered an invalid float value while parsing a JSON object.
Action

Correct the value before parsing the JSON object.
JSONCODER_INVALID_DOUBLE_NUMBER Numeric value ({0}) for field {1} is outside of the range for double values. Error:{2}
Class E
Explanation

Integration Server encountered an invalid double value while parsing a JSON object.
Action

Correct the value before parsing the JSON object.
DUPLICATE_ENTRY SOAP Encoding Registrar cannot register encoding style {0}; encoding style already exists.
Class E
Explanation

Integration Server cannot register the specified encoding style because the encoding style is already registered.
Action

Contact Software AG Global Support.
DUPLICATE_JAVATYPE_CODER SOAP Encoding Registrar cannot register Java type {0}; Java type already exists.
Class E
Explanation

Integration Server cannot register the specified Java type because it already exists in the registry.
Action

Contact Software AG Global Support.
DIFFERENT_SCHEMATYPE_CODER SOAP Encoding Registrar cannot register Schema type {0}; Schema type already exists.
Class E
Explanation

Integration Server cannot register the specified Schema type because it already exists in the registry.
Action

Contact Software AG Global Support.
UNREGISTERED_JAVA_TYPE SOAP Encoding Registrar cannot unregister Java type {0}; doesn't exist in the registry
Class E
Explanation

Integration Server cannot unregister the specified Java type becaues it does not exist in the registry.
Action

Contact Software AG Global Support.
UNREGISTERED_SCHEMA_TYPE SOAP Encoding Registrar cannot unregister Schema type {0}; doesn't exist in the registry
Class E
Explanation

Integration Server cannot unregister the specified Schema type becaues it does not exist in the registry.
Action

Contact Software AG Global Support.
RUNTIME_EXCEPTION SOAP Message Coder failure; a RuntimeException was thrown in the SOAP Coder
Class E
Explanation

The SOAP message contains an element that does not have a valid QName.
Action

Make sure the elements in the SOAP message have valid QNames.
NUMBER_FORMAT_EXCEPTION SOAP Message Coder cannot decode message; Invalid number {0}
Class E
Explanation

The message coder could not decode an XML-encoded array because one of its dimensions is set to a nonnumeric value.
Action

Check the incoming XML and make sure that the arrayType attribute specifies a positive integer. For example, make sure it has not been inadvertently set to a nonnumeric value such as “A”.

TYPE_MISMATCH_DUPLICATES SOAP Message Coder cannot encode output data; pipeline does not match output signature, duplicate variable {0} in pipeline
Class E
Explanation

The message coder could not XML-encode the results of a SOAP remote procedure call because the specified variable appeared in the pipeline more than once.

Action

On the Integration Server, examine the target service to determine why it is not producing output values that match the output signature. Correct the service’s signature and/or logic after identifying the source of the problem.

NCNAME SOAP Message Coder cannot encode variable {0}; variable does not have a valid XML name
Class E
Explanation

The message coder could not XML-encode the SOAP RPC request or response because the pipeline contained the specified variable, whose name is not a valid name for an XML element.

Action

This error often occurs because the variable name contains a colon (:). Change the name of specified variable to one that is also valid as an XML element name (or map the variable to a new variable, and use the target variable as your SOAP RPC input or output parameter).

NO_ENCODING_REGISTRY SOAP Message Coder error; no coder is registered for encoding style {0}
Class E
Explanation

Integration Server encountered a serious internal error when encoding the SOAP message.
Action

Contact Software AG Global Support.
NO_TYPE_CODER SOAP Message Coder cannot decode message; cannot determine type of element {0}
Class E
Explanation

The message coder could not decode the XML-encoded parameters it has received, because the specified element has an unknown data type (for example, xsi:type="myDataType").

Action

Check the incoming XML and make sure the data type has been specified correctly. Also make sure that it is using the correct namespace.

CREATE_ARRAY SOAP Message Coder cannot decode message; unable to create array for arrayType attribute value {0}
Class E
Explanation

The message coder could not decode an XML-encoded array because it could not allocate an array of the specified dimensions.
Action

Check the incoming XML and make sure that the arrayType attribute is specified correctly. For example, make sure that it does not specify a negative dimension or an invalid array size (e.g., too many dimensions or dimensions that are unrealistically large). If the array is unusually large or the server is extremely very low on memory, the possibility also exists that this error was the result of an out-of-memory condition.

INVALID_ARRAY_TYPE SOAP Message Coder cannot decode message; arrayType attribute value {0} is malformed
Class E
Explanation

The message coder could not decode an XML-encoded array because it cannot understand the value of the arrayType attribute.
Action

Check the incoming XML and make sure that the arrayType attribute is using the correct syntax. For example, make sure that it is not missing a “[” symbol.

TYPE_MISMATCH_MISSING SOAP Message Coder cannot encode output data; pipeline does not match output signature, required variable {0} is missing
Class E
Explanation

The message coder could not transform the results of a SOAP remote procedure call because the required variable varName was not in the pipeline.

Action

On Integration Server, examine the target service to determine why it is not producing the required output variables. Correct the service signature and/or logic after identifying the source of the problem.

TYPE_MISMATCH_EXTRAS SOAP Message Coder cannot encode output data; pipeline does not match output signature, extra variable {0} in pipeline
Class E
Explanation

Integration Server encountered an error while processing an RPC/Encoded SOAP message. Either the SOAP message does not match the output signature of the service or the contents of the output pipeline produced by the service do not match the service signature.

Action

Do one or more of the following:

- Change the SOAP message response so that it matches the service output signature.

- Change the service output signature so that it matches the expected SOAP message response.

- Ensure that the service produces an output pipeline that matches the service signature.
ILLEGAL_INPUT_PARAMETER_VALUE {0} Coder: decoding error; illegal input parameter value(s)
Class E
Explanation

One of the input parameters to the encode or decode method is null.
Action

Make sure that the input parameters passed to the encode or decode methods are not null.
NO_SOAP_BODY {0} Coder: decoding error; can't get the SOAP Body from the SOAP Message
Class E
Explanation

The SOAP body element cannot be retrieved from the SOAP message.
Action

Make sure that the SOAP message is valid and contais a SOAP body element.
NO_SOAPMSG_TO_ISDOC {0} Coder: decoding error; can't convert SOAP Message to IS Document
Class E
Explanation

Integration Server cannot convert a SOAP message to a document (IData) because of a decoding error.
Action

Contact Software AG Global Support.
CANT_CREATE_SOAP_MESSAGE {0} Coder: encoding error; can't create SOAP Message
Class E
Explanation

Integration Server cannot create the SOAP message because an encoding error occurred.
Action

Contact Software AG Global Support.
CANT_ADD_BODY_ELEMENT {0} Coder: encoding error; can't add SOAP Body Element to SOAP Message
Class E
Explanation

Integration Server cannot add the SOAP body element to the SOAP message because of an encoding error.
Action

Contact Software AG Global Support.
NO_ISDOC_TO_XMLSTR {0} Coder: encoding error; can't convert IS Document to XML String
Class E
Explanation

Integration Server cannot convert the document (IData) to an XML String because of an encoding error.
Action

Contact Software AG Global Support.
INVALID_DATE_PATTERN SOAP Message Coder cannot decode message; value "{0}" doesn't match expected pattern yyyy-MM-dd
Class E
Explanation

The date pattern is invalid.
Action

Make sure that the date value uses the pattern yyyy-MM-dd.
77.1 Config set local host error. Excpt:{0}
Class E
Explanation

During startup, Integration Server was not able to set local host information from the values specified on the "watt.net.localhost" property.

Action

Examine the value specified for property "watt.net.localhost". The value can either be a machine host name or a string representing the machine's IP address, such as "localhost" or "127.0.0.1".

77.2 Unsupported email encoding {0} specified. Defaulting to {1}
Class
77.3 Cannot initialize password store with null manager
Class S
Explanation

Initialization of the code that manages outbound passwords failed. The most likely cause is a problem with the outbound password configuration files.

Action

Make sure that the following outbound password configuration files reside on the Integration Server:

config/txnPassStore.dat

config/empw.dat

config/configPassman.cnf

config/passman.cnf

See the webMethods Integration Server documentation for information about these files and to determine whether you can restore them. If you cannot determine the source of the problem, contact Software AG Global Support.

77.4 Exception during {0}, type: {1}, msg: {2}
Class S
Explanation

A problem occurred when Integration Server tried to store or retrieve an outbound password or retrieve an encryption code from the outbound password store.

Action

The outbound password data store, config/txnPassStore.dat, is probably corrupted. See the webMethods Integration Server documentation for information about this file and how to restore it and other outbound password configuration files. If you cannot determine the source of the problem, contact Software AG Global Support.

77.5 Unable to {0}, password mgr is null
Class
77.6 System property "{0}" equals "{1}". This value is not valid. The default value of "{2}" will be used instead.
Class E
Explanation

Integration Server detected an invalid value on the indicated configuration file property.
Action

Refer to the webMethods Integration Server documentation for a description of the property and its required or allowed values.
BYTEOUTPUTBUFFER_IO Stream is already closed
Class
FILE_IO_DIR Source directory does not exist
Class
FILE_IO_FILE Source File not a directory
Class
UNKNOWN_ENCODING Could not determine encoding of file {0}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
INVALID_ENCODING Invalid encoding, {0}, specified for file {1}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
INVALID_LOCALNAME0 Local name cannot be null
Class
INVALID_LOCALNAME1 Local name cannot be an empty string.
Class
EMPTY_NAMESPACE_NAME Namespace name cannot be an empty string.
Class
INVALID_LOCALNAME2 Invalid value {0} specified for local name.
Class
PREFIX_WO_NAMESPACE Document to XSD error: Field {0} cannot be represented in XML Schema. The field name contains a prefix but an XML Namespace property is not assigned to the field
Class U
Explanation

The document type being used to generate a WSDL document contains a top-level variable whose name includes a prefix (that is, the name is in the format prefix:local name). This variable is not associated with an XML namespace.

Action

Do one of the following:

(1) Associate the variable with an XML namespace by specifying a value for the variable's XML Namespace property.

(2) Remove the prefix. Note that some protocols require the use of a prefix. Before removing the prefix, check the service signature's input and output requirements as documented for each protocol in the webMethods Integration Server documentation.

INVALID_NC_NAME Document to XSD error: Field {0} cannot be represented in XML Schema. The field name does not conform to the XML NCName definition
Class U
Explanation

The document type being used to generate a WSDL document contains field names that do not conform to the XML NCName definition.
Action

To resolve this error, rename the fields to conform to the QName lexical rules specified in http://www.w3.org/TR/REC-xml-names/#NT-QName and the XML namespace and local naming conventions specified in http://www.w3.org/TR/REC-xml-names/#NT-NCName.

RESV_DATAINUSE_GT_DATARESERVED The amount of data needed is greater than the amount of data reserved.
Class E
Explanation

A service needed to write a large amount of data to tspace, but the space the service reserved is not large enough to hold the data.

Action

Update your program to reserve more tspace. If your program does not reserve tspace directly, contact Software AG Global Support.
INVALID_PRIVATE_KEY Provided private key {0} is invalid.
Class
IO_EXCEPTION_WHILE_READING_KEY_FILE Unable to read the key/certificate file(s) {0}.
Class
INVALID_CERTIFICATE Provided certificate(s) {0} is/are invalid.
Class
DUPLICATE_READ_NOT_ALLOWED XOPObject content cannot be read more than once.
Class E
Explanation

You attempted to read the contents from an XOPObject. However, previous logic in either the same service or a previous service has already read the XOPObject. The XOPObject instance can only be read one time.

Action

Update the service logic so that it reads an XOPObject only one time.
INVALID_XML_PROVIDED Error while parsing the "{0} {1}" XML string. Parser error: {2}; XML: {3}
Class E
Explanation

One of the reference parameters or metadata elements that you specified as message addressing property is not a valid XML string.

Action

Ensure that the XML string that you specify as message addressing reference parameter or metadata element is correct.
INVALID_REFERENCE_PARAMETER_PROVIDED Error while parsing the "{0} {1}" XML string. The XML that you specify should be namespace qualified. XML: {2}
Class E
Explanation

One of the reference parameters that you specified as the message addressing property is not a namespace qualified XML string.
Action

Ensure that the XML string that you specify as message addressing reference parameter element is namespace qualified.
81.2 Error registering universal name {0}, already registered to {1}
Class
81.3 Registered universal name {0} on service {1}
Class
81.4 Duplicate universalName {0} registered to a different service {1}, not this service {2}. Unregister failed.
Class
81.5 Could not create a unique ID for the trigger from the trigger's name.
Class E
Explanation

Integration Server was unable to create a unique identifier for the trigger. This is an internal error.
Action

Try to recreate the trigger. If that fails, contact Software AG Global Support. Be prepared to provide logs and the version number and patch level for Integration Server and your operating system.

ILLEGAL_ARGUMENT_PATH Illegal argument: path={0}
Class E
Explanation

The specifed path does not exist.
Action

Make sure that you specify a path that is valid.
NS_NO_WRITE_PRIVS Cannot perform operation without Write ACL privileges on {0}
Class E
Explanation

The specified element cannot be locked because the user attempting to lock the element does not have write permissions to the element. To lock an element, a user must be a member of the Write ACL assigned to the element.

Action

Make sure that the user has write access to the element before attempting to lock it

NOT_A_SIGNATURE Illegal argument: not a signature
Class E
Explanation

The specified path item is not a signature type in the service path information.
Action

Contact Software AG Global Support.
UID_ALREADY_REGISTERED universalName {0} is already registered
Class E
Explanation

The specified universal name already exists and is assigned to another element.
Action

Specify a unique universal name that is not already used by another element.
UNKNOWN_CONTENT_TYPE Unknown content type: {0}
Class E
Explanation

Integration Server cannot create an instance of the specified content type because Integration Server does not recognize or does not support the spedcified content type.

Action

Specify a content type supported by Integration Server.
NODE_EXISTS Node exists
Class E
Explanation

An element with this fully qualified name already exists on the Integration Server. Integration Server uses the following format for the fully qualified name: folder.subfolder1.subfolder2:element

Action

Specify an element name whose fully qualified name will be unique to the Integration Server.
NODE_DOES_NOT_EXIST Node '{0}' does not exist
Class E
Explanation

A node (element) in the Integration Server namespace was not specified.
Action

Specify a node (element) in the Integration Server namespace.
NOT_WELL_FORMED Search expression {0} is not well-formed. Enter a valid regular expression or element name.
Class E
Explanation

The regular expression syntax is not valid.
Action

Ensure that specified regular expression is valid and can be complied into a valid pattern.
WSDL_GENERATION_EXCEPTION Exception occurred during generation of WSDL for service {0}: {1}
Class E
Explanation

An error occurred while attempting to validate or generate WSDL for a Web service descriptor. The error text identifies the specific error details.

Action

Use the error details to correct the issue before attempting to save the Web service descriptor or request WSDL for the Web service descriptor.

WSDL_ATTRIBUTE_NOT_FOUND_EXCEPTION Invalid WSDL. Attribute {0} must appear in element {1} at Operation: {2}, Binding: {3}
Class E
Explanation

While creating a Web service descriptor from a WSDL document, Integration Server found an invalid WSDL attribute. Most likely it was a soap:fault definition that was missing the name attribute.

Action

Correct the WSDL document before attempting to create the Web service descriptor.
INVALID_USE_IN_OPERATION_EXCEPTION Invalid "use" detected in Operation {0} at Binding {1}
Class E
Explanation

While consuming a WSDL document to create a Web service descriptor, Integration Server encountered an invalid value for the use= attribute. The only valid values for the use attribute are "literal" or "encoded".

Action

Correct the use attribute value in the WSDL document and then attempt to create the Web service descriptor.
INVALID_INPUT_SIGNATURE_FOR_LITERAL_SVC_EXCEPTION Input signature of an RPC/Literal or a Document/Literal operation cannot have top-level fields that are named "*body" or that begin with the "@" symbol. Operation Name : {0}
Class E
Explanation

A service used as an operation in an RPC/Literal binder cannot have top-level fields named "*body" or top-level fields that begin with an "@" in the service signature.

Action

Before attempting to use the service as an operation in an RPC/Literal binder, change the service signature to remove or rename top-level fields named "*body" or top-level fields that begin with an "@".

INVALID_INPUT_SIGNATURE_FOR_ENCODED_SVC_EXCEPTION Input signature of an RPC/Encoded operation cannot have fields named "*body" or that begin with the "@" symbol. Operation Name : {0}
Class e
Explanation

A service used as an operation in an RPC/Encoded binder cannot contain fields named "*body" or fields with a name that starts with "@" symbol.

Action

Before using the service as an operation in an RPC/Encoded binder, change the service signature to remove or rename the fields named "*body" or fields with a name that start with "@" symbol.

INVALID_OUTPUT_SIGNATURE_FOR_ENCODED_SVC_EXCEPTION Output signature of an RPC/Encoded operation cannot have fields named "*body" or that begin with the "@" symbol. Operation Name : {0}
Class
Explanation

The output signature of a service used as an operation for an RPC/Encoded binder cannot contain a field named "*body" or a field with a name that starts with "@ ".

Action

Change the output signature of the service before using the service as an operation in an RPC/Encoded binder.
INVALID_REQUEST_HEADER_FOR_ENCODED_SVC_EXCEPTION Request header of an RPC/Encoded operation cannot have fields named named "*body" or that begin with the "@" symbol. Operation Name : {0}, Header : {1}
Class E
Explanation

An attempt was made to add a Request Header to an operation used in an RPC/Encoded binder but the document type being added either has a field named "*body" or a field name starting with" @". Neither is allowed in a Header for an operation in an RPC/Encoded binder.

Action

Remove the fields named "*body" and the fields that start with "a" from the document type. Or use a document type that meets the field name requirements to define the format of the Header.

INVALID_RESPONSE_HEADER_FOR_ENCODED_SVC_EXCEPTION Response header of an RPC/Encoded operation cannot have fields named "*body" or that begin with the "@" symbol. Operation Name : {0}, Header : {1}
Class E
Explanation

An attempt was made to add a Response Header to an operation in an RPC/Encoded binder but the document type being added either has a field named "*body" or a field name starting with "@". Neither is allowed in a Header for an operation in an RPC/Encoded binder.

Action

Change the document type to meet the field name requirements or use a different document type that meets the requierments to define the format of the Header.

INVALID_FAULT_FOR_ENCODED_SVC_EXCEPTION Fault for an RPC/Encoded operation cannot have fields named "*body" or that begin with the "@" symbol. Operation Name : {0}, Fault : {1}
Class E
Explanation

An attempt was made to add a Fault to an RPC/Encoded operation but the document type being added either has a field named *body or a field name starting with @. Neither is allowed in a Fault for an RPC/Encoded operation.

Action

Edit the document type to remove the fields named *body or those that begin with the "@" symbol and then add the Fault to the RPC/Encoded operation. Or, select a different document type to define the format of the Fault.

INVALID_INPUT_LIST_FOR_RPC_LITERAL_EXCEPTION Input signature of an RPC/Literal operation cannot have a List field at the top level. Operation Name : {0} Field : {1}
Class E
Explanation

The input signature of a service used as an operation in a RPC/Literal binder contains a List field at the top level. Services used as operations in RPC/Literal binders cannot have List fields at the top level of the service input signature.

Action

Remove the List field from the service input signature before attempting to use the service as an operation in a RPC Literal Binder.

INVALID_OUTPUT_LIST_FOR_RPC_LITERAL_EXCEPTION Output signature of an RPC/Literal operation cannot have a List field at the top level. Operation Name : {0} Field : {1}
Class E
Explanation

The output signature of a service used as an operation in an RPC/Literal binder contains a List field at the top level. Services used as operations in RPC/Literal binders cannot have signatures that use List fields at the top level.

Action

Correct the service output signature before attempting to use the service as an operation in a RPC/Literal binder
INVALID_INPUT_TABLE_FOR_LITERAL_EXCEPTION Input signature of an RPC/Literal or a Document/Literal operation cannot have a String Table field. Operation Name : {0} Field : {1}
Class E
Explanation

A service with a String table in its service signature cannot be used as an operation for an RPC/Literal or Document/Literal binder.

Action

Change the service signature before attempting to use it as an operation in a an RPC/Literal or Document/Literal binder.
INVALID_OUTPUT_TABLE_FOR_LITERAL_EXCEPTION Output signature of an RPC/Literal or a Document/Literal operation cannot have a String Table field. Operation Name : {0} Field : {1}
Class E
Explanation

The output signature of a service used as an operation in an RPC/Literal or Document/Literal binder cannot contain a a String table.

Action

Change the servie output signature before attempting to use the service as an operation in an RPC/Literal or Document/Literal binder.

INVALID_INPUT_REPEAT_FOR_RPC_LITERAL_EXCEPTION Input signature of an RPC/Literal operation cannot have identically named fields at the top level. Operation Name : {0} Field : {1}
Class E
Explanation

A service used as an operation in a RPC/Literal binder has an input signature containing identically named fileds at the top level. All top-level field names must be unique for services used as operations in an RPC/Literal binder.

Action

Change the service signature before attempting to use the service as an operation in an RPC/Literal binder.
INVALID_OUTPUT_REPEAT_FOR_RPC_LITERAL_EXCEPTION Output signature of an RPC/Literal operation cannot have identically named fields at the top level. Operation Name : {0} Field : {1}
Class E
Explanation

A service used as an operation in an RPC/Literal binder contains fileds with duplicate names at the top level in the output signature. All top-level field names must be unique for operations in RPC/Literal binders.

Action

Change the output signature of the service before attempting to use the service as an operation in an RPC/Literal binder.
UNKNOWN_REFERENCE_EXCEPTION Unable to find {0}, needed to generate WSDL for operation {1}
Class E
Explanation

A service first provider Web service descriptor uses an IS serivce as an operation, but that IS service no longer exists in the Integration Server namespace.

Action

Edit the Web service descriptor to use an existing IS service as the operation or recreate the missing IS service.
NSOWNER_NOT_EXISTS_OR_INVALID Cannot find document type {0} needed to generate WSDL
Class E
Explanation

An internal error has occurred while attempting to validate a Web service descriptor or generate WSDL for the Web service descriptor. The specified document type is used within the definition of the Web service descriptor but it cannot be found in the Integration Server namespace.

Action

If the Web service descriptor was created from WSDL document, for example a consumer Web service descriptor a WSDL first provider Web service descriptor, delete the Web service descriptor and recreate it. If the Web service descriptor is a service first provider Web service descriptor, manuallly create the missing document type, or correct the references to the document type from the Web service descriptor (for example update the signatures of service used sa operations, update Header definitions, or update Fault definitions).

WSDL_SCHEMA_VALIDATION_EXCEPTION Invalid WSDL schema generated for the service signatures or the document types referred by the WSD ''{0}''. To view the generated WSDL change the logging level of Namespace(0081) to Trace. Error details: {1}
Class E
Explanation

This is a generic message that Integration Server throws for all Xerces parser errors.
Action

If Xerces parser throws "Unique Particle Attribute" error, then a possible workaround for this issue is to set the value of the 'Allow unspecified fields' constraint of the variables in the IS doc type referred by the Web service descriptor to 'False'.

INVALID_HEADER_PART_USING_TYPE The header has a message part "{0}" defined by the type "{1}". Message parts in a header must be defined by the element attribute instead of the type attribute.
Class E
Explanation

An attempt was made to set the Pre 8.2 compatibility mode property to false for a Web service descriptor, but the WSDL document used to create the Web service descriptor has Header parts defined using the type attribute. For the Web service descriptor to have the Pre 8.2 compatibility mode property set to false, the Header parts in the WSDL document must use the element attribute.

Action

If you want the Web service descriptor to have a Pre 8.2 compatibility mode property set to false, change the Header parts in WSDL document to use the element attribute and then use Designer recreate the Web service descriptor.

INVALID_MESSAGE_PART_EXCEPTION Invalid message part(s) defined in the wsdl: {0}
Class E, W
Explanation

An invalid Message Part definition was found while consuming WSDL to create a Web service descriptor. The error message lists the specific error details .

Action

Use the error details in the message to correct the WSDL. Then, use the corrected WSDL document to create the Web service descriptor.

ERROR_NO_SOAP_TRIGGER Cannot find SOAP-JMS trigger "{0}" specified in the provider Web service endpoint alias "{1}" assigned to binder "{2}" in the web service descriptor "{3}".
Class E
Explanation

The Web service endpoint alias assigned to the provider Web service descriptor uses a SOAP-JMS trigger that cannot be found. The provider Web service endpoint alias for use with a JMS binder is not valid if the SOAP-JMS trigger specified in the alias cannot be found. The Web service descriptor cannot be saved if a valid Web service endpoint alias is not assigned to a binder that specifies JMS as the transport.

Action

Update the provider Web service endpoint alias to use a different SOAP-JMS trigger. Alternatively, assign a different valid provider Web service endpoint alias to the binder.

ERROR_NO_JMS_PROVIDER_ALIAS Cannot find provider Web service endpoint alias "{0}" assigned to binder "{1}" in the web service descriptor "{2}".
Class E
Explanation

The Web service endpoint alias assigned to the provider Web service descriptor cannot be found. The Web service descriptor cannot be saved if a Web service endpoint alias is not assigned to a binder that specifies JMS as the transport.

Action

Assign a valid provider Web service endpoint alias to the binder.
WARNING_MEP_IMPACTED_INONLY2INOUT MEP for operations {0} has changed from In-Only MEP to In-Out MEP. As a result, Integration Server will now execute the corresponding response handlers.
Class W
Explanation

Changing the Pre-8.2 compatibility mode property of the Web service descriptor from false to true resulted in a change of the Message Exchange Pattern (MEP) for the specified operations to In-Out. At run time, Integration Server will execute response handler services for the specified operations.

Action

No action required.
WARNING_MEP_IMPACTED_INOUT2INONLY MEP for operations {0} has changed from In-Out MEP to In-Only MEP. As a result, Integration Server will no longer execute the corresponding response handler services.
Class W
Explanation

Because the specified operation has no defined output, changing the Pre-8.2 compatibility mode property of the Web service descriptor from true to false resulted in a change of the Message Exchange Pattern (MEP) for the specified operations to In-Only. At run time, Integration Server will no longer execute the response handler services for the specified operations.

Action

No action required.
WARNING_MEP_IMPACTED_ROBUSTINONLY2INOUT MEP for operations {0} has changed from Robust In-Only MEP to In-Out MEP.
Class W
Explanation

Changing the Pre-8.2 compatibility mode property of the Web service descriptor from false to true resulted in a change of the Message Exchange Pattern (MEP) for the specified operations to In-Out.

Action

No action required.
WARNING_MEP_IMPACTED_CONSUMER Invoke RefreshConnectors against the Web service descriptor to have the Web service connector''s signature updated to reflect the change to the compatibility mode.
Class W
Explanation

After changing the Pre-8.2 compatibility mode property for a consumer Web service descriptor, the Web service connectors need to be refreshed. If an operation does not have any defined output, refreshing the Web service connectors will update the output signature to reflect the compatibility mode change. If you changed the Pre-8.2 compatibility mode property to false, the Web service connector will no longer have any SOAP message-related output parameters. If you changed the Pre-8.2 compatibility mode property to true, the output signature will include an output parameter for a SOAP fault.

Action

Refresh the Web service connectors for this Web service descriptor.
POLICY_UNAVAIABLE_FOR_CONSUMER_EXCEPTION Web service descriptor {0} is not available because the WS-Policy file with policy ID {1} attached to the WSD is not present in the policy repository.
Class E
Explanation

The Web service descriptor is not available because the WS-Policy file attached to the Web service descriptor is deleted or moved from the policy repository.

Action

The following lists the actions you can take: 1) Ensure that the WS-Policy that is attached to the Web service descriptor resides in the policy repository. -OR- 2) Edit the Web service descriptor so that it no longer uses the deleted or moved WS-Policy file.

INVALID_WSDL_MISSING_FAULT_IN_PORTTYPE_OPERATION Invalid WSDL. wsdl:fault element named {0} must be present in operation {1} of port type {2}
Class E
Explanation

The WSDL document used to create the WSDL first provider or consumer Web service descriptor does not contain wsdl:fault element in the wsd:operation of the portType.

Action

Ensure that the WSDL contains the correct wsdl:fault element in the wsd:operation of the portType. Contact Software AG Global Support for further assistance.

82.1 Type {0} exists in schema {1}. Set {1} as owner schema.
Class
FRACTION_DIGIT_BASE_IS_FIXED "fractionDigits"+STR_BASE_FACET_FIXED
Class E
Explanation

The fractionDigits facet is fixed for the type and cannot be changed
Action

Do not attempt to change the fractionDigits value for the type.
MESSAGE_MISSING_AII Missing Attribute Information Item
Class E
Explanation

The attribute is declared as required but is missing from the instance document.
Action

Correct the instance document.
MESSAGE_ANGRY_PARSER Error while parsing "{0}"
Class E
Explanation

An unexpected error occurred while valiating the instance document.
Action

Contact Software AG Global Support.
MESSAGE_MISSING_ROOT_EII Unable to retrieve root element
Class E
Explanation

The instance document does not have a root element and cannot be validated.
Action

Correct the instance document.
MESSAGE_MISSING_ELEMENT_DECL Unable to locate a matching element declaration
Class E
Explanation

The element in the instance document does not have an element declaration.
Action

Correct the instance document. Ensure that the element name is correctly spelled.
MESSAGE_AIIS_FOUND [attributes] property must be empty
Class E
Explanation

The element is defined to be of simple type. No attributes may be present.
Action

Remove the attributes from the element in the instance document, or use an element that permits the attribute.
MESSAGE_EIIS_FOUND EII (s) are not allowed in [children] property
Class E
Explanation

The element type does not allow child elements to be present in the content.
Action

Remove the child elements from the instance document, or use a type definition that permits the desired child elements.
MESSAGE_OPRHAN_AII Unable to locate a matching attribute declaration
Class E
Explanation

Integration Server could not locate an attribute declaration for the attribute.
Action

Correct the instance document to reference an attribute for which there is a declaration or remove the attribute from the instance document.

MESSAGE_INVALID_CII Invalid value - does not match fixed value
Class E
Explanation

The element declaration has a fixed value. Only that value may be present in the instance document.
Action

Correct the instance document.
MESSAGE_INVALID_CONTENTMODEL Child element {0} at position {1} is unexpected
Class E
Explanation

The instance document contains an element at the specified location that does not match what is expected.
Action

Correct the instance document.
MESSAGE_INVALID_CONTENTMODEL2 Incomplete content - one or more child elements are expected
Class E
Explanation

The instance element does not contain the expected child elements. Content is missing.
Action

Correct the instance document to contain the missing content.
MESSAGE_LOST_ATTRIBUTE_DECL Unable to locate attribute declaration
Class E
Explanation

Integration Server could not locate a corresponding schema definition for the attribute.
Action

Ensure that a schema for the relevant namespace has been created and that it contains a declaration for the attribute.
MESSAGE_LOST_TYPE_DEF Unable to locate type definition
Class E
Explanation

Integration Server could not locate a corresponding schema definition for the type.
Action

Ensure that a schema for the relevant namespace has been created and that it contains a definition for the type.
MESSAGE_LOST_TYPE_DEF2 Unable to locate type definition {0}
Class E
Explanation

Integration Server could not locate a corresponding schema definition for the type.
Action

Ensure that a schema for the relevant namespace has been created and that it contains a definition for the type.
MESSAGE_LOST_ELEMENT_DECL Unable to locate element declaration
Class E
Explanation

Integration Server could not locate a corresponding schema definition for the element.
Action

Ensure that a schema for the relevant namespace has been created and that it contains a declaration for the element.
MESSAGE_AMBIGUOUS_CONTENT_MODEL Ambiguous content model in schema - not LL(1)
Class E
Explanation

The content model is ambiguous. The given set of particle can validate the same instance with more than one unique set of occurrence counts.

Action

A schema must not be ambiguous. It must be possible to validate an instance without looking ahead in the content model definition. Modify the schema so that the content model is not ambiguous.

MESSAGE_UNABLE_TO_RESOLVE Unable to resolve QName: {0}
Class E
Explanation

The type reference cannot be resolved to a defined type.
Action

Specify a defined type.
MESSAGE_TYPE_DERIVATION_NOK {0} is not validly derived from {1}
Class E
Explanation

The type specified in the instance document is not a valid subtype of the type specified in the schema element declaration.
Action

Correct the instance document by specifying a valid subtype.
MESSAGE_ABSTRACT_TYPE {0} is an abstract type and cannot be used directly to validate content
Class E
Explanation

An abstract type cannot be specified in an instance document.
Action

Specify a concrete type that has been derived from the abstract type.
MESSAGE_ABSTRACT_ELEMENT {0} is an abstract element and cannot appear in an instance
Class E
Explanation

The instance document contains an element that has been declared abstract in the schema. Abstract elements may not appear in an instance document.

Action

Remove the abstract designation rfom the schema element definition or use a member of the abstract element's substitution group in the instance document.

MESSAGE_INCORRECT_XSITYPE {0} - xsi:type is used incorrectly (declared type is anonymous)
Class E
Explanation

The element declaration does not reference a named type. It is not possible to specify a type in the instance document.
Action

Do not use a type specification for an element that has an anonymous type declaration.
MESSAGE_NIL_SHOULD_NOT_EXIST The nillable value of {0} is false, hence xsi:nil cannot appear in an instance
Class E
Explanation

The element declaration does not have the nillable attribute set to true. The element in the instance document may not have a nil attribute.

Action

Correct the instance document or modify the element declaration to have the nillable attribute set to true.
MESSAGE_INVALID_NIL_VALUE The value of xsi:nil is invalid
Class E
Explanation

The instance document element contains a value for the nil attribute that is not valid. The nil attribute must have a value of true or false.

Action

Correct the instance document to specify a valid value for the nil attribute.
MESSAGE_NO_CHAR_OR_CHILD {0} cannot have content or child elements since xsi:nil is true
Class E
Explanation

An element is marked nill in the instance document. The element cannot have any content.
Action

Correct the element in the instance document.
MESSAGE_ORPHAN_OBJECT Undefined Object found
Class E
Explanation

An unexpected object was found in the document.
Action

Correct the instance document by removing the unexpected object.
MESSAGE_ARRAY_EXPECTED Dimension mismatch, List expected
Class E
Explanation

The instance document contains a scalar value where an array is expected.
Action

Correct the input data.
MESSAGE_SCALAR_EXPECTED Dimension mismatch, Single item expected
Class E
Explanation

An array was encountered where a scalar item was expected.
Action

Correct the instance document to specify a scalar item instead of an array.
MESSAGE_TABLE_EXPECTED Dimension mismatch, Table expected
Class E
Explanation

The instance document contained an object type other than String array of dimension two.
Action

Correct the instance document
MESSAGE_STRING_EXPECTED Type mismatch, String expected
Class E
Explanation

The instance document contained an object type other than String.
Action

Correct the instance document.
MESSAGE_VALUES_EXPECTED Type mismatch, Document expected
Class E
Explanation

The document field was expected to reference another document but instead referenced some other data type.
Action

Correct the instance document.
MESSAGE_WRAPPER_TYPE_EXPECTED Java type mismatch; expected {0}, got {1}
Class E
Explanation

The field is declared to contain one of the supported Java wrapper types but the instance document contains some other data type.

Action

Correct the instance document.
MESSAGE_TAG_IS_ABSENT Field is absent, field must exist
Class E
Explanation

The specified element or attribute is required but is not present in the instance document.
Action

Correct the instance document to contain the required element or attribute.
MESSAGE_VALUE_IS_NULL Value cannot be null, allow null value is false
Class E
Explanation

The field is declared to not contain nulls, but the instance document contains a null.
Action

Correct the instance document.
MESSAGE_DUPLICATE_ROOT_ELEMENT Duplicate root element {0} found
Class E
Explanation

An instance document may contain only one root element.
Action

Correct the instance document so that it has only one root element.
MESSAGE_CONTENT_TYPE_ELEMENT_ONLY Element [{0}] cannot have characters [{1}], because the type''s content type is element-only
Class E
Explanation

The element's type declaration does not permit text nodes to be present.
Action

Remove the embeded text from the instance document, or use an element type declaration that permits text.
MESSAGE_FIELD_COUNT_MAXOCCURS Tag occurs too many times
Class E
Explanation

The element occurs more times than permitted by the element declaration's maxOccurs attribute.
Action

Correct the instance document.
MESSAGE_FIELD_COUNT_MINOCCURS Tag occurs too few time
Class E
Explanation

The element occurs fewer times than required by the element declaration's minOccurs attribute.
Action

Correct the instance document.
MESSAGE_BUILDER_NOT_FOUND Document Type generation error: {0}
Class S
Explanation

An internal failure has occurred.
Action

Contact Software AG Global Support.
MESSAGE_ANGRY_SERVER Integration Server says - {0}
Class S
Explanation

An unexpected error has interrupted the conversion process.
Action

Retry the request. If the error recurs contact Software AG Global Support.
MESSAGE_MISSING_ROOT_ELEMENT {0} - unable to locate the root element
Class S
Explanation

An internal error has interrupted the conversion process.
Action

Contact Software AG Global Support.
DIMENSION_OVER_FLOW Cannot process multi-dimensional array {0}. The maximum supported dimensionality for arrays is 2.
Class E
Explanation

Document types may not conmtain String arrays with dimension greater than two
Action

Do not use String arrays with dimension greater than two.
CONTENT_TYPE_RECURSION Complex type {0} is recursive. Recursive types are supported only when selecting the option "Generate complex types as document types"
Class E
Explanation

It is not possible to expand a type inline if it has a recursive reference. The expansion become infinite.
Action

Use the Generate complex types as document types option.
MESSAGE_UNSUPPORTED_SCHEMA_FEATURE Nested and repeating model groups are not yet supported by strict compliance for the {0} component
Class E
Explanation

This version of Integration Server does not support strict conversion of schema content models that have nested or repeating model groups.

Action

Do not use the Strict conversion option. Use the Lax or None option instead.
INVALID_LENGTH Invalid: length
Class E
Explanation

The length facet value must be a non-negative integer.
Action

Specify a valid value for the length facet.
INVALID_MIN_LENGTH Invalid: minLength
Class E
Explanation

The minLength facet value must be a non-negative integer.
Action

Specify a valid facet value.
INVALID_MAX_LENGTH Invalid: maxLength
Class E
Explanation

The maxLength facet value must be a non-negative integer.
Action

Specify a valid facet value.
INVALID_TOTAL_DIGIT Invalid: totalDigits
Class E
Explanation

The totalDigits facet value must be a posative integer.
Action

Specify a valid facet value.
INVALID_FRACTION_DIGIT Invalid: fractionDigits
Class E
Explanation

The fractionDigits facet value must be a non-negative integer.
Action

Specify a valid value for the fractionDigits facet.
MAXLENGTH_LESS_THAN_MIN maxLength is less than minLength
Class E
Explanation

The maxLength facet value is less than the minLength facet value.
Action

Adjust the minLength or maxLength facet so that minLength is less than or equal to maxLength.
ENUM_NOT_EQUAL_LENGTH Invalid enumerated item: {0}. Length of value is not equal to specified length
Class E
Explanation

The enumerated item length is not equal to the length required by its type.
Action

Specify a valid value for the type.
ENUM_SHORTER_THAN_LENGTH Invalid enumerated item: {0}. Value is shorter than minimum length
Class E
Explanation

The enumerated item is shorter than the required length of its type.
Action

Specify a valid value for the type.
ENUM_LONGER_THAN_LENGTH Invalid enumerated item: {0}. Value is longer than maximum length
Class E
Explanation

The enumerated value is longer than the maximum length allowed by its type.
Action

Specify a valid value for the type.
INVALID_MIN_E Invalid: minExclusive
Class E
Explanation

The minExclusive facet value exceeds the values permitted by the totalDigits or factionDigits facets.
Action

Specify a valid facet value.
INVALID_MAX_I Invalid: maxInclusive
Class E
Explanation

The maxInclusive facet value exceeds the values permitted by the totalDigits or factionDigits facet.
Action

Specify a valid value for the maxInclusive facet.
INVALID_MAX_E Invalid: maxExclusive
Class E
Explanation

The maxExclusive facet value exceeds the values permitted by the totalDigits or factionDigits facets.
Action

Specify a valid value for the maxEclusive facet.
MAXI_LESS_THAN_MINI maxInclusive is less than minInclusive
Class E
Explanation

The maxInclusive facet value is less than the minInclusive facet value.
Action

Change the value of the maxInclusive facet or the minInclusive facet.
MAXE_LESS_THAN_MINE maxExclusive is less than minExclusive
Class E
Explanation

The maxExclusive facet value is less than the minExclusive facet value.
Action

Change the value of the maxEclusive facet or the minExclusive facet.
MAXE_LESS_THAN_MINI maxExclusive is less than minInclusive
Class E
Explanation

The maxExclusive facet value is less than the minInclusive facet value.
Action

Change the value of the maxEclusive facet or the minInclusive facet.
MAXI_LESS_THAN_MINE maxInclusive is less than minExclusive
Class E
Explanation

The maxInclusive facet value is less than the minExclusive facet value.
Action

Change the value of the maxInclusive facet or the minExclusive facet.
INVALID_ENUM Invalid enumerated item: {0}
Class E
Explanation

The enumeration is empty.
Action

Specify a value for the enumeration facet.
INVALID_ENUM_OUT_OF_RANGE Invalid enumerated item ( Out of range ): {0}
Class E
Explanation

The enumeration facet value is outside of the permitted value range of the type.
Action

Correct the enumeration facet value.
INVALID_ENUM_NOT_MATCH_PATTERN Invalid enumerated item ( Does not match pattern ): {0}
Class E
Explanation

The enumeration value does not match the pattern facet for the type.
Action

Correct the enumeration value to match the pattern facet.
LIST_ENUM_NOT_EQUAL_LENGTH Invalid enumerated item. Length of value is not equal to specified length
Class E
Explanation

The length of an enumeration value for a list must be equal to the length facet of the list.
Action

Specify a list enumeration facet with the correct length.
LIST_ENUM_SHORTER_THAN_LENGTH Invalid enumerated item. Value is shorter than minimum length
Class E
Explanation

The length of an enumeration value for a list must be greater than or equal to the minLength facet of the list.
Action

Specify a list enumeration facet with the correct length.
LIST_ENUM_LONGER_THAN_LENGTH Invalid enumerated item. Value is longer than maximum length
Class E
Explanation

The length of an enumeration value for a list must be less than or equal to the maxLength facet of the list.
Action

Specify a list enumeration facet with the correct length.
INVALID_VALUE Value does not conform to datatype
Class E
Explanation

The value is not a valid instance of the type.
Action

If the error occurs during schema compilation, correct the value specification in the schema. If the error occurs during document validation, it indicates that validation successfully detected an invalid document.

LENGTH_OUT_OF_BOUNDARY "length"+STR_OUT_OF_BOUND
Class E
Explanation

The length facet for the list is outside of the permissible range. It must not be less than the minLength facet and it must not be greater than the maxLength facet.

Action

Specify a valid length facet.
MIN_LENGTH_OUT_OF_BOUNDARY "minLength"+STR_OUT_OF_BOUND
Class E
Explanation

The minLength facet value is either less than the minLength facet value or greater than the maxLength facet value of the base type

Action

Specify a minLength facet value that is within the range allowed by the base type.
MAX_LENGTH_OUT_OF_BOUNDARY "maxLength"+STR_OUT_OF_BOUND
Class E
Explanation

The maxLength facet value is either greater than the maxLnegth facet value or less than the minLength facet value of the base type.

Action

Specify a maxLength facet value that is within the range allowed by the base type.
MINI_OUT_OF_BOUNDARY "minInclusive"+STR_OUT_OF_BOUND
Class E
Explanation

The minInclusive facet value is either less than the minInclusive facet value or greater than the maxInclusive facet value of the base type.

Action

Specify a minInclusive facet value that is within the range allowed by the base type.
MINE_OUT_OF_BOUNDARY "minExclusive"+STR_OUT_OF_BOUND
Class E
Explanation

The minExclusive facet value is either less than the minExclusive facet value or greater than the maxExclusive facet value of the base type.

Action

Specify a minExclsuive facet value that is within the range allowed by the base type.
MAXI_OUT_OF_BOUNDARY "maxInclusive"+STR_OUT_OF_BOUND
Class E
Explanation

The maxInclusive facet value is less than the minInclusive facet value or greater than the maxInclusive facet value of the base type

Action

Specify a correct maxInclusive facet or remove it.
MAXE_OUT_OF_BOUNDARY "maxExclusive"+STR_OUT_OF_BOUND
Class E
Explanation

The maxExclusive facet value is less than the minInclusive facet value or greater than the maxInclusive facet value of the base type.

Action

Specify a correct maxExclusive facet or remove it.
TOTAL_DIGIT_OUT_OF_BOUNDARY "totalDigits"+STR_OUT_OF_BOUND
Class E
Explanation

The totalDigits facet value is greater than the totalDigits facet value of the base type.
Action

Specify a totalDigits facet value that is within the range allowed by the base type.
FRACTION_DIGIT_OUT_OF_BOUNDARY "fractionDigits"+STR_OUT_OF_BOUND
Class E
Explanation

The fractionDigits facet of a derived type may not exceed the fractionDigits facet of the base type
Action

Correct the fractionDigits facet value so that it does not exceed the fractionDigits facet value of the base type.
WHITE_SPACE_OUT_OF_BOUNDARY "whiteSpace"+STR_OUT_OF_BOUND
Class E
Explanation

The whiteSpace facet value is incompatible with the whiteSpace facet value of the base type
Action

Th whiteSpace facet value must specify white space handling that is more restrictive than the base type facet.
NO_MATCH_CHOICE No matching enumeration value
Class E
Explanation

The element value in the instance document contains a token that is not specified in the element type's enumeration facet.
Action

None. Validation successfully detected an invalid document.
NOT_EQUAL_LENGTH Length of value is not equal to specified length
Class E
Explanation

The length of the element value in the instance document does not match the length specified by the element type's length facet.

Action

None. Validation successfully detected an invalid document.
SHORTER_THAN_LENGTH Value is shorter than minimum length
Class E
Explanation

The instance document element value is shorter than the minLength facet for the element type, or the element contains a list with fewer items than the minLength facet of the list type.

Action

None. Validation successfully detected an invalid document.
LONGER_THAN_LENGTH Value is longer than maximum length
Class E
Explanation

The instance document element value is longer than the maxLength facet for the element type, or the element contains a list with more items than the maxLength facet of the list type.

Action

None. Validation successfully detected an invalid document.
LIST_NO_DATATYPE_DEFINATION_MSG Datatype definition is missing
Class E
Explanation

The list specification does not include a type definition for the items of the list.
Action

Specify an item type definition for the list.
NOT_MATCH_PATTERN_MSG Value does not match pattern(s)
Class E
Explanation

The element value in the instance document does not match the element type's facet pattern.
Action

None. Validation successfully detected an invalid document.
YEAR_ZERO_NOT_ALLOWED The year 0000 is prohibited
Class E
Explanation

The facet value may not contain a year value of 0000.
Action

Do not use 0000.
TOTAL_D_LESS_THAN_FRACTION_D totalDigits is less than fractionDigits
Class E
Explanation

The factionDigits facet value must be less than or equal to the totalDigits facet value.
Action

Adjust the fractionDigits or the totalDigits facet value.
INVALID_FACET_TYPE Invalid facet type
Class E
Explanation

An invalid facet is specified.
Action

Specify a valid facet.
INVALID_WHITE_SPACE_VALUE The input has invalid characters
Class E
Explanation

An invalid whitespace character is present in the instance document.
Action

None. Validation successfully detected an invalid document.
LENGTH_BASE_IS_FIXED "length"+STR_BASE_FACET_FIXED
Class E
Explanation

The length of the list is fixed and cannot be changed.
Action

Remove the length facet.
MIN_LENGTH_BASE_IS_FIXED "minLength"+STR_BASE_FACET_FIXED
Class E
Explanation

The minLength facet of the base type is fixed; it cannot be customized.
Action

Remove the minLength facet from the type specification.
MAX_LENGTH_BASE_IS_FIXED "maxLength"+STR_BASE_FACET_FIXED
Class E
Explanation

The maxLength facet of the base type is fixed; it cannot be customized.
Action

Remove the maxLength facet from the type specification.
MINI_BASE_IS_FIXED "minInclusive"+STR_BASE_FACET_FIXED
Class E
Explanation

The minInclusive facet of the base type is fixed; it cannot be customized.
Action

Remove the minInclusive facet from the type specification.
MINE_BASE_IS_FIXED "minExclusive"+STR_BASE_FACET_FIXED
Class E
Explanation

The minExclusive facet of the base type is fixed; it cannot be customized.
Action

Remove the minExclusive facet from the type specification.
MAXI_BASE_IS_FIXED "maxInclusive"+STR_BASE_FACET_FIXED
Class E
Explanation

The maxInclusive facet of the base type is fixed; it cannot be customized.
Action

Remove the maxInclusive facet from the type specification.
MAXE_BASE_IS_FIXED "maxExclusive"+STR_BASE_FACET_FIXED
Class E
Explanation

The maxExclusive facet of the base type is fixed; it cannot be customized.
Action

Remove the maxExclusive facet from the type specification.
TOTAL_DIGIT_BASE_IS_FIXED "totalDigits"+STR_BASE_FACET_FIXED
Class E
Explanation

The totalDigits facet of the base type is fixed; it cannot be customized.
Action

Remove the totalDigits facet from the type specification.
WHITE_SPACE_BASE_IS_FIXED "whiteSpace"+STR_BASE_FACET_FIXED
Class E
Explanation

The whiteSpace facet of the base type is fixed; it cannot be customized.
Action

Remove the whiteSpace facet from the type specification.
SHOULD_NOT_HAVE_THIS_FACET This datatype cannot have this facet
Class E
Explanation

The specified facet is not defined for the type on which it appears.
Action

Remove the facet from the type specification where it appears.
LEN_CANNOT_CO_EXIST Cannot specify length with minLength or maxLength
Class E
Explanation

The length facet cannot be specified along with the minLength or maxLength facets.
Action

Remove the length facet or the minLength and maxLength facets.
ENUM_INVALID_TOTAL_DIGIT "Invalid enumerated item: {0}. "+STR_EXCEEDS_TOTAL_DIGIT
Class E
Explanation

The enumerated item has more total digits than allowed by its type.
Action

Specify a valid value for the type.
ENUM_INVALID_FRACTION_DIGIT "Invalid enumerated item: {0}. "+STR_EXCEEDS_FRACTION_DIGIT
Class E
Explanation

The enumerated item has more fraction digits than allowed by its type.
Action

Specify a value that is valid for the type.
EXCEEDS_TOTAL_DIGIT STR_EXCEEDS_TOTAL_DIGIT
Class E
Explanation

The total digits in the instance item exceeds the total digits that is valid for the type.
Action

None. Validation has successfully detected an invalid document.
EXCEEDS_FRACTION_DIGIT STR_EXCEEDS_FRACTION_DIGIT
Class E
Explanation

The instance item exceeds the fraction digits allowed for its type
Action

None. Validation successfully detected an invalid document.
LESS_THAN_MIN_I Value is less than minInclusive
Class E
Explanation

The element value in the instance document is less than the minInclusive facet for the element type.
Action

None. Validation successfully detected an invalid document.
LESS_THAN_MIN_E Value is less than or equal to minExclusive
Class E
Explanation

The element value in the instance document is less than or equal to the minExclusive facet for the element type.
Action

None. Validation successfully detected an invalid document.
GREATER_THAN_MAX_I Value is greater than maxInclusive
Class E
Explanation

The element value in the instance document exceeds the value of the maxEclusive facet for the element type
Action

None. Validation successfully detected an invalid document.
GREATER_THAN_MAX_E Value is greater than or equal to maxExclusive
Class E
Explanation

The element value in the instance document exceeds or equals the value of the maxEclusive facet for the element type
Action

None. Validation successfully detected an invalid document.
LENGTH_BASE_EXISTS "Length constraint cannot be customized. "+STR_LENGTH_EXISTS
Class E
Explanation

The base type already has a length facet; it is not possible to change the length facet.
Action

Remove the length facet from the type specification.
LEN_BASE_MIN_CANNOT_CO_EXIST "Cannot specify minLength if length is specified. "+STR_LENGTH_EXISTS
Class E
Explanation

The length and minLength facets are mutually exclusive.
Action

Remove one of the facets from the type specification.
LEN_BASE_MAX_CANNOT_CO_EXIST "Cannot specify maxLength if length is specified. "+STR_LENGTH_EXISTS
Class E
Explanation

The maxLnegth and length facets are mutually exclusive.
Action

Remove one of the facets from the type specification.
CANNOT_CO_EXIST Cannot specify both {0} and {1}
Class E
Explanation

The schema properties are mutually exclusive. Only one can be specified.
Action

Decide which property is relevant and remove the other.
MESSAGE_INVALID_SCHEMA_FROM_XERCES Xerces Java parser determined that the XML schema definition is invalid
Class E
Explanation

The Xerces Java parser determined that an XML schema definition is invalid. This can occur in the following situations:

- When creating an asset (IS schema, document type, or flow service) from an XML Schema definition.

- When creating a Web service descriptor from a WSDL document that contains a schema element or references an XML schema definition.

- When refreshing Web service connectors

- When executing a Web service connector

- When changing the IS schemas, document types, or service signatures associated with a Web service descriptor
Action

Use the information returned by the Xerces Java parser to make the schema valid.

Alternatively, if you do not want the Xerces Java parser to perform schema validation, do one of the following:

- When creating the asset, clear the Validate schema using Xerces check box

- For an existing Web service descriptor, set the Validate schema using Xerces property to False.
MSG_TYPE_UNAVAILABLE Requested type not available
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the Integration Server XQL query engine encountered an internal error.

Action

Contact Software AG Global Support.
MSG_TREE_UNSUPPORTED Tree type not supported
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the supplied query object supplied was not a valid XML Node object.
Action

Examine the service input and ensure it is a valid XML node object. You can invoke the pub.xml:xmlStringToXMLNode or pub.xml:loadXMLNode service to obtain the document and transform it to an XML node object before performing the query.

MSG_EMPTY_EXPRESSION Expression is empty
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because no query expression was specified.
Action

Examine the logic and make sure that the query expression is not empty.
NODE_PARA_NULL Node parameter is null
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the XML Node to be queried was empty or missing.
Action

Examine the XML node object submitted for query and make sure it is not null.
OBJ_TYPE_UNSUPPORTED ''{0}'' object type not currently supported.
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the document submitted was not an instance of an XML Node object. This service can obtain information from XML nodes only. Note: An XML node is a special representation of an XML document that can be consumed by the Integration Server. Most webMethods services that operate on XML documents require an XML node as input.

Action

Examine the document submitted and make sure that you have used pub.xml:xmlStringToXMLNode or pub.xml:loadXMLNode service to convert the document to an XML Node object before performing the query.

IDATA_REGION_UNSUPPORTED Regions are not supported on IData objects
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because it tried to perform a region query on an IData object; the Integration Server does not support this type of query. Currently only XML node objects are supported for region queries. Note: An XML node is a special representation of an XML document that can be consumed by the Integration Server. Most webMethods services that operate on XML documents require an XML node as input.

Action

Do not attempt to query regions on IData objects.
IDATA_SOURCE_UNAVAILABLE Source not available for IData objects
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because it tried to obtain information from a Document (an IData object) instead of an XML Node. This service can obtain information from XML Nodes only. Note: An XML node is a special representation of an XML document that can be consumed by the Integration Server. Most webMethods services that operate on XML documents require an XML node as input.

Action

Do not attempt to query the source from Documents (IData objects).
IDATA_HAS_RECURSION Recursion detected in IData at {0}; can't have recursion when query contains | or //
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because it tried to perform a query on a recursive IData object, but the query contained "|" (a union operator) or "//" (a path operator). These operators are not allowed when querying a recursive IData object.

Action

Do not attempt to query a recursive IData object when the query contains "|" or "//".
IDATA_ILLEGAL_CAST Illegal typecast in query expression
Class
BOOLEAN_EXPECTED 'true()' or 'false()' expected
Class
LEFT_PARATHE_EXPECTED '(' expected
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because it specified an incorrect syntax. Specifically, the left-hand parenthesis "(" was missing after the "true" or "false" Boolean function.

Action

Examine the query expression and make sure it uses the correct syntax. There must be matching parentheses after any "true" or "false" functions, e.g., true(), false().

RIGHT_PARATHE_EXPECTED ')' expected
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the right-hand parenthesis ")" was missing after the "true" or "false" Boolean function.

Action

Examine the query expression and make sure it uses the correct syntax. There must be matching parentheses after any "true" or "false" functions, e.g., true(), false().

INVALID_BOOLEAN_METHOD Invalid boolean method: {0}
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the Integration Server XQL query engine encountered an internal error.

Action

Contact Software AG Global Support.
MSG_MISSING_RVALUE Comparison requires an rvalue
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the right-hand operand was not present in the query. Left- and right-hand operands are required for a comparison query.

Action

Examine the query expression and make sure that both the left- and right-hand operands are supplied.
MSG_TOO_MANY_RVALUES Comparison righthand operand evaluates to more than one value
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute a comparison query because the value of the right-hand operand was not a scalar.

Action

Examine the query expression and make sure the value of the right-hand operand is a scalar or a value that can be cast at runtime to a scalar.

MISSING_COMPARE_OPERATOR Comparison operator is missing.
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute a comparison query because the expression contained $any$ or $all$, but no comparison operator. A comparison operator must be specified in an expression that contains $any$ or $all$.

Action

Examine the query expression and make sure it contains a comparison operator.
ALLOW_ONLY_RELATIVE_QUERY Only relative queries allowed inside filters.
Class E
Explanation

The XQL query expression contains an absolute path inside the filter. For example, "book[/author]".
Action

Make sure that the XQL query expression contains a relative path inside the filter. For example, "book[author]".
BRACET_NOT_MATCH '[' is not matched by ']'
Class U
Explanation

The pub.xml:queryXMLNode service failed to execute because the left-hand square bracket "[" was specified but the right-hand square "]" bracket was missing. An expression that uses a filter operator or a subscript operator must contain matching parentheses.

Action

Examine the query expression and make sure it contains matching brackets "[ ]" .
SELECT_NODE_OR_ATTRIBUTE Filter brackets may only select nodes or attributes
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because a subquery within the "[ ]" was not a node or attribute. A subquery must be a node or an attribute when a filter operation is used.

Action

Examine the query expression and make sure that the subquery contained within the "[ ]" is a node or attribute.
TERM_MISSING_OR_INVALID Invalid or missing term
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because a query expression using a filter operator specified an invalid term or no terms at all.

Action

Examine the query expression and make sure it specifies a valid term. Valid terms are: dot('.'), left parenthesis('('), at('@'), and wildcard('*').

PARATHE_NOT_MATCH_TOKEN '(' is not matched by ')'. Token "{0}" found.
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the query expression contained a left parenthesis "(" that was not matched by a right parenthesis ")", but rather by another character. The query expression must specify matching parentheses when a filter operator is used.

Action

Examine the query expression and make sure it contains matching parentheses "()".
PARATHE_NOT_MATCH_TOKEN_END '(' is not matched by ')'. End of query found.
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the query expression contained a left parenthesis "(" but no right parenthesis ")". A query expression must specify matching parentheses when a filter operator is used.

Action

Examine the query expression and make sure it contains matching parentheses "()".
TERM_MISSPLACE_OR_INVALID Invalid or misplaced term "{0}"
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because an invalid character was specified in a query expression that contains a filter operator. Valid characters are dot ".", left and right parentheses ''(" and ")", at "@", and wildcard "*".

Action

Examine the query expression and ensure that only valid characters are specified.
INVALID_ATTRIBUTE_NAME Invalid attribute name "{0}:"
Class E
Explanation

The XQL query expression contains an invalid attribute name. This attribute belongs to a namespace. For example, "//@prefix:123".
Action

Make sure that the XQL query expression contains a valid attribute name. For example, "//@prefix:a123".
INVALID_OR_MISSING_ATTRI_NAME Invalid or missing attribute name
Class E
Explanation

The XQL query expression contains an invalid or undefined attribute name. For example, "//@123" or "//@".
Action

Make sure that the XQL query expression contains a valid attribute name. For example, "//@a123".
FUNC_ATTR_QUOTED_STRING attribute() takes a quoted string
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the optional parameter passed to attribute() function was not a quoted string.

Action

Examine the query expression and make sure that it uses the correct syntax and passes a quoted string to the attribute() function.
INCORRECT_ATTRIBUTE_NAME attribute() incorrect attribute name "{0}"
Class E
Explanation

The XQL query expression contains an invalid attribute name inside the attribute(). For example, "//book/attribute('123')".
Action

Make sure that the XQL query expression contains a valid attribute name inside the attribute(). For example, "//book/attribute('a')".
ONLY_NODE_HAS_ATTRIBUTE Only nodes have attributes
Class
COUNT_QUERY_PARA count() takes a query parameter
Class E
Explanation

The XQL query expression contains a parameter in the count(), which is not allowed. For example, "//book/count(1)".
Action

Make sure that the XQL query expression does not contain a parameter in the count(). For example, "//book/count()".
DATE_INVALID_TYPE Type {0} can't be cast to Date
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the query engine returned a value that could not be cast as a date.
Action

Examine the query expression and make sure it uses the correct syntax and specifies the correct query.
DATE_INVALID_VALUE date({0}){1}
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the parameter passed to the XQL date() function was not in a format that could be converted to a date.

Action

Examine the detailed error message and make sure that the string parameter passed to the XQL date() function can be converted to a date.

DATE_ERROR_OFFSET date(){0} Error offset:{1}
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the parameter passed to the XQL date() function could not be parsed.
Action

Examine the detailed error message and the position provided in it and make sure that the string parameter passed to the date() function in the query expression can be parsed to a date.

ELEMENT_INVALID_NAME Invalid element name "{0}:"
Class E
Explanation

The XQL query expression contains an invalid element name. This element belongs to a namespace. For example, "//a:1".
Action

Make sure that the XQL query expression contains a valid element name. For example, "//a:b".
ELEMENT_INVALID_OR_MISSING_NAME Invalid or missing element name
Class
ELEMENT_QUOTED_STRING element() takes a quoted string
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the optional parameter passed to XQL element() function was not a quoted string.

Action

Examine the query expression and make sure it uses the correct syntax and passes a quoted string to the element() function.
ELEMENT_INCORRECT_NAME element() incorrect attribute name "{0}"
Class E
Explanation

The XQL query expression contains an invalid parameter in element(). For example, "/book/element("1")".
Action

Make sure that the XQL query expression contains a valid parameter name in element(). For example, "/book/element("a")".
ONLY_NODE_HAS_CHILD Only nodes have child elements
Class
FLOAT_INVALID_TYPE Type {0} can't be cast to Float
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because it expected a float, but the value it received was not a float.
Action

Examine the query expression. Make sure it uses the correct syntax and specifies the query you intended.
ID_QUOTED_STRING id() takes a quoted string
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the optional parameter passed to XQL id() function was not a quoted string.

Action

Examine the query expression and make sure it uses the correct syntax and passes a quoted string to the XQL id() function.
INTEGER_INVALID_TYPE Type {0} can't be cast to Integer
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because it expected an integer, but the value it received could not be cast as an integer.

Action

Examine the query expression. Make sure it uses the correct syntax and specifies the query you intended.
NAME_QUOTED_STRING name() takes a quoted string
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the optional parameter passed to XQL name() function was not a quoted string.

Action

Examine the query expression and make sure it uses the correct syntax and passes a quoted string to the XQL name() function.
NAME_NON_EMPTY_STRING name() requires a non-empty string
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the parameter passed to the XQL name() function was empty.
Action

Examine the query expression and make sure it uses the correct syntax and passes a non-empty quoted string to the name() function.
NODE_RELATIVE_TO_NODE node() must be used relative to a node
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because it specified an incorrect syntax for the XQL node() function or tried to execute the function against a non-node object.

Action

Examine the query expression and make sure it uses the correct syntax for the node() function and executes the function against a node.

REGION_RELATIVE_TO_NODE region() must be used relative to a node
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because it specified an incorrect syntax for the XQL region() function or tried to execute the function against a non-node object.

Action

Examine the query expression and make sure it uses the correct syntax for the region() function and executes the function against a node.

REGION_MUST_RETURN_NODE Query parameters of region() must return nodes
Class
REGION_NO_MUPTIPLE_START region() can't have more than one region start node
Class
REGION_NO_MUPTIPLE_END region() can't have more than one region end node
Class
TEXTNODE_RELATIVE_TO_NODE textnode() must be used relative to a node
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because it specified an incorrect syntax for the XQL textnode() function or tried to execute the function against a non-node object.

Action

Examine the query expression and make sure it uses the correct syntax for the textnode() function and executes the function against a node.

NAME_EXPECTED Function or method name expected
Class
INVOKE_PARATHE_MISSING '(' missing after function or method name
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because a left-hand parenthesis "(" was missing after the function or method name. The correct syntax is functionname() or methodname() .

Action

Examine the query expression and make sure that it uses the correct syntax for the function or method.
INVOKE_TRUNCATED_INVOKE Query contains truncated invocation
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because an incomplete expression was provided for a function call. Specifically, the expression contained a left parenthesis "(" but the invocation parameter or right parenthesis ")" was missing. Examples: function() function(parameter

Action

Examine the query expression and make sure it uses the correct syntax.
PARATHE_TERMINATE_LIST ')' must terminate parameter list
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the right parenthesis ")" was missing from the parameter list that was passed to the XQL function.

Action

Examine the query expression and make sure it uses the correct syntax and includes the right parenthesis to terminate the parameter/parameter list.

INVOKE_MISSING_PARAMETER missing function parameter
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the parameter required by the XQL function was not provided.
Action

Examine the query expression and make sure it uses the correct syntax and includes the required parameter.
INVOKE_WRONG_PARA_NUMBER Invalid number of parameters in function or method "{0}"
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because an invalid number of parameters were passed to the XQL function or method.

Action

Examine the query expression and make sure it uses the correct syntax and passes the correct number of parameters to the XQL function. See XQL Query Language at http://www.w3.org/TandS/QL/QL98/pp/xql.html for method or function reference.

FUNCTION_NAME_NOT_RECOGNIZED "{0}" is not a recognized function name
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because an invalid XQL function name was provided.
Action

Examine the query expression and make sure that it only uses the valid XQL functions. Integration Server currently supports the following pre-defined functions: attribute(), Boolean(), comment(), count(), date(), element(), float(), id(), integer(), name(), node(), not(), pi(), region(), textnode(), true(), false().

METHOD_NAME_NOT_RECOGNIZED "{0}" is not a recognized method name
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because an invalid XQL method name was provided.
Action

Examine the query expression and make sure that it only uses the valid XQL methods. Integration Server currently supports the following pre-defined methods: basename(), count(), end(), index(), namespace(), nodename(), nodetype(), nodetypestring(), prefix(), regex(), regexinsensitive(), regexinsensitivematch(), regexmatch(), rawtext(), stringmatch(), source(), text(), value().

METHOD_APPLY_TO_NODE_ATTR Methods may only be applied to nodes and attributes
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the Integration Server XQL query engine encountered an internal error.

Action

Contact Software AG Global Support.
METHOD_REGEX_QUOTED_STRING regex() takes a quoted string
Class
REGEXINSENSITIVE_QUOTED_STRING regexinsensitive() takes a quoted string
Class
REGEXINSENSITIVEMATCH_QUOTED_STRING regexinsensitivematch() takes a quoted string
Class
REGEXMATCH_QUOTED_STRING regexmatch() takes a quoted string
Class
STRINGMATCH_QUOTED_STRING stringmatch() takes a quoted string
Class
PQ_CONTAIN_EX_TERMS Query contains extraneous terms
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because there was a syntax error in the expression. Specifically, there were extraneous terms in the expression.

Action

Examine the query expression and make sure it uses the correct syntax.
PQ_INVALID_TYPE Cannot parse queries of type {0}
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the XQL query engine encountered an internal error.
Action

Contact Software AG Global Support.
RCPATH_NODE_ATTRI Left operand of / must be either a node or an attribute
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the query expression specified the unary child operator "/" but the value specified by the left-hand operand was not a node type or an attribute type.

Action

Examine the query expression and make sure the left-hand operand is a node or attribute.
RCPATH_ONLY_RELATIVE Only relative queries allowed in relative paths.
Class E
Explanation

The XQL query expression contains an absolute path inside another absolute path. For example, "/x/(/y)".
Action

Make sure that the XQL query expression does not contain an absolute path embedded inside another absolute path.
RDPATH_NODE Left operand of // must be a node
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the query expression specified the unary child descendant operator "//" but the value specified by the left-hand operand was not a node.

Action

Examine the query expression and make sure the left-hand operand is a node.
SUBSCRIPT_INVALID_ARGUMENT Invalid subscript argument
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because no argument was supplied for the subscript operator or the argument supplied was not an integer.

Action

Examine the query expression and make sure that a valid integer is provided for the subscript operator.
UNION_SAME_TYPE Only values of the same type may be unioned
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute a union operation because the left-hand operand is not the same type as the right-hand operand.

Action

Examine the query expression and make sure that both operands are of the same type. Valid types are node, attribute, string, integer, float, and Boolean.

RSPEC_TYPE_NOT_COMPARABLE {0} and {1} types are not comparable
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute a comparison operation because the left-hand operand is not the same type as the right-hand operand.

Action

Examine the query expression and make sure that the left-hand operand and right-hand operand are of the same type. Valid types are node, attribute, string, integer, float, and Boolean.

RSPEC_RELATION_NOT_DEFINED The {0} relation is not defined on {1} types
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
TE_UNRECOGNIZED_TYPE Unrecognized expression type "{0}"
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the XQL query engine encountered an internal error.
Action

Contact Software AG Global Support.
TE_NULL_NODE_PARA generateQueryString Node doc is a required parameter. Must not be null.
Class
TE_NULL_STRING_PARA generateQueryString String queryType is a required parameter. Must not be null.
Class
TE_UNSUPPORTED_TYPE generateQueryString only supports WQL, XQLVALUES and XQL types. Unsupported type "{0}"
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because an expression attempted to evaluate an unsupported type. Integration Server currently only supports WQL,XQLVALUES and XQL.

Action

Contact Software AG Global Support.
TE_UNKNOWN_TYPE Unknown TreeExpression type
Class E
Explanation

Integration Server tried to process an unsupported type. This is an internal error. Currently only the WQL, XQLVALUES and XQL types are supported.

Action

Contact Software AG Global Support.
TC_NOT_CAST_TO_BOOL Cannot cast "{0}" to boolean
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because it attempted to cast a string value to a Boolean type. The possible causes are: (1) the left-hand and right-hand operands specified with a comparison operator were not of the same type (2) the value returned by the query was of an unexpected type.

Action

Examine the query expression and make sure it specifies the correct syntax and performs the query you expected.
TC_NOT_CAST_TO_FLOAT Cannot cast "{0}" to a float
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because it attempted to cast a string value to a float. The possible causes are: (1) the left-hand and right-hand operands specified with a comparison operator were not of the same type (2) the value returned by the query was of an unexpected type.

Action

Examine the query expression and make sure it specifies the correct syntax and performs the query you expected.
TC_NOT_CAST_TO_INTEGER Cannot cast "{0}" to an integer
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because it attempted to cast a string value to an integer. The possible causes are: (1) The left-hand and right-hand operands specified with a comparison operator were not of the same type. (2) The value returned by the query was of an unexpected type.

Action

Examine the query expression and make sure it specifies the correct syntax and performs the query you expected.
TC_NOT_CAST_TO_LONG Cannot cast "{0}" to a long
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because it attempted to cast a string value to a long type. The possible causes are: (1) the left-hand and right-hand operands specified with a comparison operator were not of the same type (2) the value returned by the query was of an unexpected type.

Action

Examine the query expression and make sure it specifies the correct syntax and performs the query you expected.
VNE_IO_ERROR IO error occurred while parsing a grove in a VARNAME expression: {0}
Class
XQ_STRING_IDEN_NO_STRING XqlQuery.getStringWithIdentities: Query "{0}" does not yield strings:{1}
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the XQL query engine encountered an internal error.
Action

Contact Software AG Global Support.
XQ_STRING_NO_STRING XqlQuery.getString: Query "{0}" does not yield strings:{1}
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the XQL query engine encountered an internal error.
Action

Contact Software AG Global Support.
XQ_UNKOWN_TYPE XqlQuery: Query yields unknown type
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the XQL query engine encountered an internal error.
Action

Contact Software AG Global Support.
XQ_NODE_IDEN_NO_NODE XqlQuery.getNodeWithIdentities: Query "{0}" does not yield nodes
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the XQL query engine encountered an internal error.
Action

Contact Software AG Global Support.
XQ_NODE_NO_NODE XqlQuery.getNode: Query "{0}" does not yield nodes
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the XQL query engine encountered an internal error.
Action

Contact Software AG Global Support.
XQ_NODEARRAY_IDEN_NO_NODE XqlQuery.getNodeArrayWithIdentities: Query "{0}" does not yield nodes
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the XQL query engine encountered an internal error.
Action

Contact Software AG Global Support.
XQ_NODEARRAY_NO_NODE XqlQuery.getNodeArray: Query "{0}" does not yield nodes
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the XQL query engine encountered an internal error.
Action

Contact Software AG Global Support.
XQ_IDATA_NO_NODE XqlQuery.getIData: Query "{0}" does not yield nodes
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the XQL query engine encountered an internal error.
Action

Contact Software AG Global Support.
XQ_NO_IDATA_INSTANCE Query does not yield an IData instance as expected
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the XQL query engine encountered an internal error.
Action

Contact Software AG Global Support.
XQ_IDATAARRAY_NO_NODE XqlQuery.getIDataArray: Query "{0}" does not yield nodes
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the XQL query engine encountered an internal error.
Action

Contact Software AG Global Support.
XQ_ONLY_IDATA Query ''{0}'' does not yield only IData instances as expected
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the XQL query engine encountered an internal error.
Action

Contact Software AG Global Support.
MSG_FLOAT_DOT_ERROR Floating point numbers must begin with a digit
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because an invalid query expression was provided. Specifically, a floating point number was provided in an incorrect format. A digit must immediately precede and follow the dot "." term. Examples of the correct format are "1.23" and "-0.99.". Examples of incorrect formats are ".99" and "1.".

Action

Examine the query expression and make sure that it uses the correct format for floating point numbers.
TB_UNRECOGNIZED_OPERATOR Unrecognized operator '${0}
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because an expression contained an unrecognized operator.
Action

Examine the query expression and make sure it only uses the valid operators specified in the XQL specification. For more information, see XQL Query Language at http://www.w3.org/TandS/QL/QL98/pp/xql.html.

TB_INVALID_NUMBER Invalid number: "{0}"
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the XQL query engine could not parse a numberString to an integer or a float because the string does not represent an integer or float number.

Action

Examine the query expression and make sure that it uses the correct syntax. See XQL Query Language at http://www.w3.org/TandS/QL/QL98/pp/xql.html for more information.

TB_MISSING_TERMINAL_QUOTE Missing terminal quote: {0}{1}
Class
NAME_NOT_RECOGNIZED "{0}" is not a recognized function or method name
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because an invalid XQL function or method was specified in the query expression.
Action

Examine the query expression and make sure that you only use a set of pre-defined XQL function names or method names in the query. For a list of pre-defined functions and methods in XQL, see The XML Query Language (XQL) at http://www.w3.org/TandS/QL/QL98/pp/xql.html.

XQ_NODE_TREE Method requires Node tree for query ''{0}''.
Class E
Explanation

The pub.xml:queryXMLNode service failed to execute because the XQL query engine encountered an internal error.
Action

Contact Software AG Global Support.
ATTRIBUTE_UNSUPPORTED Queries on attributes are not supported by IData trees.
Class
NSDECLS_UNSUPPORTED nsDecls and namespaces are not supported by IData trees.
Class
ACCESS_DENY Access Denied
Class E
Explanation

The user does not have permission to access an Integration Server resource. Review the server log to find the resource and the user who was denied access.

Action

If the user should have access to this resource, either add the user to the group that is in the Allowed list of the execute ACL of the resource, or add one of this user's groups to the Allowed list of the execute ACL of the resource.

INVALID_SESSION_ID Invalid Session ID or Session Expired
Class E
Explanation

Whenever a client presents a Session ID that is no longer valid, Integration Server throws this exception and sets the 401 HTTP response code to force the client to re-authenticate.

Action

No action is necessary.
NOT_ACCEPT_REQS Server is not accepting new requests at this time
Class E
Explanation

A client request was submitted during Integration Server shutdown. Integration Server does not accept requests during shutdown.
Action

Resubmit the request after Integration Server becomes available again.
SERVER_REACH_LIMIT Server has reached client limit
Class E
Explanation

Integration Server was not able to create a session to service a client requet. Integration Server sends this error with HTTP response code 503 to the client.

Action

Review the server log and error log to find possible causes of this error.
RESUBMIT_DATAARRAY_NULL Resubmit data array cannot be null.
Class E
Explanation

webMethods Monitor failed to resubmit the rejected document because the data array for resubmission was not supplied.
Action

Examine the document to be resubmitted and make sure that it is valid and not empty.
RESUBMIT_DATA_NULL Resubmit data cannot be null.
Class E
Explanation

webMethods Monitor failed to resubmit the rejected document because the data for resubmission was not supplied.
Action

Examine the document to be resubmitted and make sure that it is valid and not empty.
RESUBMIT_AUDITCONTEXT_NULL Auditcontexts cannot be null or empty.
Class E
Explanation

webMethods Monitor failed to resubmit the rejected document because the "auditContexts" field in the data was either null or empty.

Action

Examine the document to be resubmitted and make sure that it is valid and that the "auditContexts " field is not missing.
RESUBMIT_SERVICENAME_NULL Service name cannot be null or empty.
Class E
Explanation

webMethods Monitor failed to resubmit the rejected document because the "serviceName" field in the data was either null or empty.

Action

Examine the document to be resubmitted and make sure that it is valid and that the "serviceName" field is not missing.
RESUBMIT_NONEXISTANT_SERVICE Service for resubmission does not exist on the server.
Class U
Explanation

webMethods Monitor failed to resubmit the rejected document because the service for resubmission does not exist on Integration Server.

Action

Examine the document to be resubmitted and make sure that the name specified in the "serviceName" field is a valid service and exists on Integration Server.

RESUBMIT_INPUTPIPELINE_NULL Input pipeline cannot be null.
Class E
Explanation

webMethods Monitor failed to resubmit the rejected document because the "pipeline" field in the data was either null or empty.
Action

Examine the document to be resubmitted and make sure that it is valid and that the "pipeline" field is not missing.
RESUBMIT_USERNAME_NULL User name cannot be empty or null.
Class E
Explanation

webMethods Monitor failed to resubmit the rejected document because the "userName" field in the data was either null or empty.
Action

Examine the document to be resubmitted and make sure that it is valid and that the "userName" field is not missing.
RESUBMIT_USERACCESS_DENIED Access is denied to the user.
Class E
Explanation

The current user does not have permission to invoke the service that is being resubmitted.
Action

To grant permission to the user, add the user to a group that is listed in the Execute ACL assigned to the service.
NOT_AUTH_USE_SERVER Not Authorized to use Server
Class E
SMIME_INVALID_RECIP_CERT_ATIDX_NOTRECOG Recipient certificate at index {0} not in recognizable format
Class
BYTE_ARRAY_NEEDED bytes must be byte[]
Class
URL_WRONG_BEGINNING URL must begin with "http:" or "https:"
Class
HTTP_METHOD_NULL HTTP method is null
Class
CLIENT_HTTP_EXP1 Only use one of data.stream, data.bytes or data.mimeStream with the POST, PUT or PATCH method.
Class
CLIENT_HTTP_EXP2 Do not use data.bytes, data.stream or data.mimeStream with the GET method.
Class
CLIENT_HTTP_INPUT_PARAM_REQ {0}: input parameter required
Class
INVALID_HTTP_METHOD invalid HTTP method: {0}
Class
CLIENT_SMTP_INVALID_TO_FIELD Invalid TO field: {0}
Class
CLIENT_SMTP_INVALID_CC_FIELD Invalid CC field: {0}
Class
CLIENT_SMTP_INVALID_BCC_FIELD Invalid BCC field: {0}
Class
CLIENT_SMTP_INVALID_FILES files must be of type Values[]
Class
CLIENT_SMTP_NO_FILE_CONTENT No filename nor content included in the attachment!
Class
CLIENT_SMTP_INVALID_MIMESTREAM mimeStream must be an InputStream
Class
DATE_PATTERN_REQUIRED 'pattern' is a required input
Class
FILE_DOESNOT_EXIST {0} does not exist
Class
FILE_CANNOT_BE_READ {0} cannot be read
Class
FILE_IS_DIR {0} is a directory
Class
MISSING_PARAM_NAME Missing required parameter: '$name'
Class
MISSING_PARAM_FILENAME Missing required parameter: 'fileName'
Class
SAVE_PIPELINE_NAME_NOT_EXIST Saved pipeline {0} does not exist
Class
MISSING_PARAM_RESPONSE Missing required parameter: 'response'
Class
INVOKED_OUTOF_FLOW getLastError invoked outside of a Flow
Class
LIST_PARAM_KEY_REQUIRED parameter 'key' is required when fromList is not null
Class
MIME_CREATE_MIME_DATA input must be an InputStream
Class
MIME_INDEX_NOT_INTEGER index must be a non-negative integer
Class
MIME_MISSING_MIMEMSG {0} input parameter required
Class
MIME_MISSING_CONTENT_INPUT content input parameter required
Class
MIME_CONTENT_NOT_EMPTY Message content is not empty
Class
RECORD_MISSING_XMLVALUES Missing required value: {xmlvalues}
Class
RECORD_MISSING_RECORD Missing required value: {record}
Class
RECORD_MISSING_RECORDLIST_NAME Missing one or more required values: {recordList,name}
Class
SMIME_CERT_NOT_RECOGNIZABLE Certificate not in recognizable format
Class
SMIME_CERT_ATIDX_NOT_RECOG Certificate at index {0} not in recognizable format
Class
SMIME_INVALID_CERT_ATIDX Invalid certificate input at index {0}
Class
SMIME_CANNOT_CREATE_SMIMEOBJ Could not create certs only SMIME object {0}
Class
SMIME_INVALID_INPUTSTREAM Not a valid InputStream
Class
SMIME_INPUTDATA_NOT_RECOG InputData not in recognizable format
Class
SMIME_INVALID_RECIP_CERT Invalid recipient certificates information
Class
SMIME_INVALID_RECIP_CERT_ATIDX Invalid recipient certificate input at index {0}
Class
SMIME_INCORRECT_KEYLENGTH Incorrect keylength specified: {0}
Class
SMIME_UNSUPPORTED_ALGTHM Unsupported encryption algorithm specified: {0}
Class
SMIME_COULD_NOT_CREATE_SMIME_ENVOBJ Could not create SMIME Enveloped object {0}
Class
SMIME_INVALID_PRIVKEY_INFO Invalid private key information
Class
SMIME_INVALID_SIGNER_CERT Invalid signer certificate file information
Class
SMIME_CERT_FILE_NOT_RECOG Certificate file not in any recognizable format
Class
SMIME_NOT_CREATE_SIGNED_OBJ Could not create signed SMIME object {0}
Class
SMIME_COULD_NOT_RETR_CONTENT Could not retrieve content from input
Class
SMIME_ENCRYPTED_CONTENT_NOT_RECOG Encrypted Content not in recognizable format
Class
SMIME_RECIP_CERT_NOT_RECOG Recipient certificate not in any recognizable format
Class
SMIME_CERT_CANNOT_DECRYPT Supplied certificate cannot decrypt content
Class
SMIME_NOT_VALID_PRIVKEY Not a valid privateKey
Class
SMIME_UNABLE_DECRYPT_SYMKEY Unable to decrypt symmetric key
Class
SMIME_CERTS_ONLYDATA_NOTRECOG Certs-Only data not in recognizable format
Class
SMIME_SIGNED_CONTENT_NOTRECOG Signed Content not in recognizable format
Class
STRING_BYTES_MUST_BYTES bytes must be type byte[]
Class
SYNC_EXCLU_WAIT already in exclusive wait
Class
SYNC_CANNOT_OBTAIN_WAIT cannot obtain exclusive wait
Class
TABLE_NO_STRINGTABLE_DATA No string table data supplied
Class
TABLE_NO_COLUMN_NAME No column names supplied
Class
TABLE_WRONG_COLUMN_NAME {0} Maybe the wrong number of column names
Class
TABLE_NO_ROW_DATA No row data supplied
Class
TABLE_DEPRECATED_SVC Deprecated Service: table to documentList conversion is now automatic.
Class
UTIL_CANNOT_PROCESS_NULL Cannot process null input
Class
UTIL_INPUT_NOT_BYTE_ARRAY Input not a byte array
Class
UTIL_INPUT_INCORRECT_FORMAT Input in incorrect format, certificate cannot be loaded
Class
UTIL_NO_ALG_SPECIFIED No algorithm has been specified
Class
PKCS7_NO_KEYS No keys provided to sign the provided data
Class
PKCS7_DATA_INCORRECT_FORMAT Data to sign not in the expected format (byte[])
Class
PKCS7_ERROR_PROCESS_SIGNERINFO An error occurred processing the signer information for {0}, {1}
Class
PKCS7_ERROR_CREATE_SIGNATURE An error occurred creating the signature for the data: {0}
Class
PKCS7_NO_SIGNATURE No signature provided to verify
Class
PKCS7_NO_DATA_TO_VERIFY No data provided to verify detached signature
Class
PKCS7_ERROR_RECONSTRUCT_SIG An error occurred attempting to reconstruct the signature: {0}
Class
PKCS7_NOT_PKCS7_DATA Signature provided is not PKCS#7 SignedData
Class
PKCS7_INVALID_DATA_BUILD_CHAIN Invalid data encountered when building the certificate chain, either an instance of a certificate or a byte[] expected
Class
PKCS7_INVALID_DATA_FOR_CERT_ENTRY Invalid data provided for certificate entry {0}, expecting a byte[]
Class
WEB_PARAM_MISSING Parameter {0} is missing
Class
WEB_PARAM_INCORRECT_TYPE Parameter {0} is of incorrect type
Class
WEB_PARSEXMLDATA_MISSING Parameters {0}, '$filestream' and '$filedata' are all missing. One of these must not be null.
Class
WEB_HTTP_ERROR_WITH_STATUS Http Error: {0} - {1}
Class
LDAP_NO_URL_SPECIFIED No LDAP URL specified
Class
LDAP_NO_CONNECTION_KEY No connection key provided
Class
LDAP_BAD_CONNECTION_KEY Bad connection key: {0}
Class
LDAP_NO_LOOKUP_NAME No lookup name provided
Class
LDAP_NO_SEARCH_FILTER No search filter provided
Class
LDAP_NO_TARGET_NAME No target name provided
Class
LDAP_NO_SCHEMA_INFO No schema information available
Class
REP_MISSING_PKGNAME Required parameter 'packageName' is missing
Class
REP_MISSING_PUBLISHER Required parameter 'publisher' is missing
Class
REP_MISSING_FILTER The 'fileList' or 'fileNamePattern' parameter is required
Class
REP_MISSING_PACKAGE Required parameter 'package' is missing
Class
REP_RELEASE_EXISTS Package ''{0}'' has already been released, select a different name instead
Class
PKGS_MISSING_PACKAGE Required parameter 'package' is missing
Class
PKGS_MISSING_PACKAGE_FILE Required parameter 'packageFile' is missing
Class
SCHEDU_NO_SUCH_USER No such user present : {0}
Class
SCHEDU_NOT_ONETIME_TASK Task being updated is not a one-time task
Class
SCHEDU_NOT_REPEATING_TASK Task being updated is not a repeating task
Class
SCHEDU_NOT_COMPLEX_TASK Task being updated is not a complex task
Class
SECURITY_INPUT_NOT_NULL Inputs cannot be null
Class
SECURITY_FILE_NOT_FOUND Certificate file not found: {0}
Class
SECURITY_FILE_NOTRECOG_FORMAT Certificate file {0} not in any recognizable format
Class
SECURITY_ERROR_READ_FILE IO Exception encountered while reading file: {0}
Class
STORAGE_INVALID_LOCK_MODE lockMode must be "{0}" or "{1}". Supplied value was {2}.
Class
STORAGE_EMPTY_UNLOCK_KEY key of entry to unlock can not be null
Class
STORAGE_EMPTY_ADD_KEY key of value to add can not be null
Class
STORAGE_EMPTY_PUT_KEY key of entry to insert or update can not be null
Class
STORAGE_EMPTY_GET_KEY key of entry to get can not be null
Class
STORAGE_EMPTY_REMOVE_KEY key of entry to remove can not be null
Class
STORAGE_EMPTY_PUT_VALUE value to insert or update can not be null
Class
STORAGE_NOLOCK_GET_KEY Cannot obtain entry lock for key
Class
GD_MISSING_TID Missing required parameter: tid
Class
GD_MISSING_ALIAS Missing required parameter: alias
Class
GD_MISSING_SVC Missing required parameter: service
Class
PKGS_NOT_ALLOWED_ACT_WMROOT Not allowed to activate package ''{0}''
Class
PKGS_NOT_ALLOWED_INS_WMROOT The target name specified by {0} is {1}, not allowed to install package or patch to {1}
Class
PKGS_NOT_ALLOWED_ENABLE_WMROOT Not allowed to enable package ''{0}''
Class
PKGS_NOT_ALLOWED_DISABLE_WMROOT Not allowed to disable package ''{0}''
Class
PKGS_NOT_ALLOWED_RECOVER_WMROOT Not allowed to recover package ''{0}''
Class
PKGS_WRONG_PACKAGE_FILE Package file ''{0}'' does not exist in Inbound directory
Class
PKGS_IO_EXCEPTION Exception occurred while checking target package name
Class
PKGS_INVALID_PKGNAME Invalid or non-existing package name ''{0}'' provided
Class
UNIVERSALNAME_MISSING_PARAMETER A required parameter {0} was not supplied
Class
UNIVERSALNAME_QNAME_NOT_FOUND The Universal Name {0} is unknown
Class
UNIVERSALNAME_ALREADY_DEFINED The Universal Name {0} is already defined for {1} in the registry
Class
UNIVERSALNAME_DEFINED_IN_NS The Universal Name {0} is already defined as a Service
Class
UNIVERSALNAME_NOT_VALID The Universal Name {0} is not a valid QName
Class
UNIVERSALNAME_PARAMETER_TYPE Parameter {0} is the wrong data type
Class
PKGS_NOT_ALLOWED_RELOAD_WMROOT Not allowed to reload package ''{0}''
Class
PKGS_NOT_EXIST_IN_SALVAGE Unknown package name ''{0}'' provided
Class
PKGS_ALREADY_ACTIVE Package ''{0}'' is already active
Class
PKGS_ALREADY_ENABLED Package ''{0}'' is already enabled
Class
PKGS_ALREADY_DISABLED Package ''{0}'' is already disabled
Class
MIME_CANNOT_CONVERT_HEADER Not able to convert headerLines to byte array
Class
MIME_MISSING_HEADER Missing required parameter: 'headerLines'
Class
MIME_HEADER_NOT_IDATA Invalid input. 'headerLines' must be an instance of IData
Class
MIME_MISSING_BODY Missing required parameter: 'body'
Class
MIME_BYTES_NOT_BYTE_ARRAY Invalid input. 'bytes' must be an instance of byte array
Class
MIME_BYTES_NOT_INPUTSTREAM Invalid input. 'stream' must be an instance of InputStream
Class
MIME_BODY_NOT_IDATA Invalid input. 'body' must be an instance of IData
Class
MIME_ERROR_READING_INPUTSTREAM Error reading inputstream: 'stream'
Class
MIME_BOTH_BYTES_STREAM_NOT_NULL Both 'bytes' and 'stream' cannot be absent
Class
IO_MISSING_BYTES bytes is a required field
Class
IO_MISSING_STREAM stream is a required field
Class
PKCS7_CANNOT_RETRIEVE_CONTENT Could not retrieve raw data from implicitly signed message
Class
REVINVOKE_MISSING_REVPROXY_ALIAS Alias for Enterprise Gateway Proxy not specified
Class
REVINVOKE_MISSING_REVPROXY_NOCONN No of Connections to Enterprise Gateway Proxy not specified
Class
REVINVOKE_MISSING_THRESHOLD New threshold for outstanding Requests not specified
Class
REVINVOKE_MISSING_CONID Connection ID not specifie
Class
REVINVOKE_MISSING_LISTENER_TYPE Listener Type not specified
Class
PUBLISH_REQUIRED_PARAM_TYPE_IDATA Invalid input. ''{0}'' is a required parameter of type IData
Class
PUBLISH_REQUIRED_PARAM_TYPE_STRING Invalid input. ''{0}'' is a required parameter of type String
Class
PUBLISH_PARAM_TYPE_STRING Invalid input. ''{0}'' must be of type String
Class E
Explanation

The specified input parameter must have a value of type String, but does not.
Action

Set the specified input paramater to a value that is of type String.
PUBLISH_PARAM_TYPE_POSITIVE_INT Invalid input. ''{0}'' must be a positive integer
Class
Explanation

The specified input paramater contains an invalid value.
Action

Set the value of the specified input parameter to a positive integer.
PUBLISH_PARAM_TYPE_BOOLEAN Invalid input. ''{0}'' must be true or false
Class
Explanation

The specified parameter must be set to true or false.
Action

Set the specified parameter to true or false.
MATH2_REQUIRED_PARAM_NUM Missing required parameter: {0}
Class
MATH2_PARAM_NUM_NOT_NUMBER Invalid value for parameter: {0}. {0} is not a recognized numeric type
Class
DATE2_REQUIRED_PARAM_PATTERN Missing required parameter: pattern
Class E
Explanation

The pattern input paramteter is required, but has not been provided.
Action

Supply a value for the pattern input parameter.
DOCUMENT_MISSING_DOCUMENT Missing required value: {document}
Class
DOCUMENT_MISSING_DOCUMENTLIST_NAME Missing one or more required values: {documentList,name}
Class
REP_INVALID_PKGNAME Invalid or non-existing package name ''{0}'' provided
Class
REP_MISSING_RELEASE_VERSION Missing required parameter: version
Class
REP_MISSING_JVM_VERSION Missing required parameter: JVMversion
Class
REP_MISSING_TARGET_VERSION Missing required parameter: targetPkgVersion
Class
INVALID_DT_PATTERN_OR_INPUT Invalid date pattern or input
Class
FTP_MISSING_FTP_SESSION_KEY FTP session key not specified
Class
FTP_MISSING_CONTENT_OR_FILENAME Missing content or filename
Class
FTP_INVALID_DIR {0} is not a valid directory!
Class
SECURITY_INPUT_PRIV_KEY_NOTBYTES Private key data must be in a byte array (byte[]).
Class
SECURITY_INPUT_CERTS_NOTBYTES Certificate chain data must be an array of byte array (byte[][]).
Class
SECURITY_CERT_NOTRECOG_FORMAT Certificate at position {0} in array is not in any recognizable format
Class
FTP_BAD_LARGEFILETHRESHOLD Not a valid long number
Class
IO_VAR_REQD ''{0}'' is required.
Class E
Explanation

A required input value is missing.
Action

Supply the missing input value and re-execute the service.
IO_VAR_OPT_GE_ZERO If ''{0}'' is supplied, it must be zero (0) or greater.
Class E
Explanation

The indicated input value is a negative number, but it must be zero or a positive number.
Action

For the specified parameter, enter a value of 0 or a positive integer. Alternatively, if the specified parameter is optional, delete the supplied value.

IO_OFFSET_TOO_BIG ''offset'' + ''length'' cannot exceed the size of ''{0}''.
Class E
Explanation

The values specified for offset and length are invalid because they will cause Integration Server to write data from the stream past the end of the supplied buffer.

Action

Supply valid values for offset and length.
IO_NO_MARK_SUPPORT The mark method is not supported by the supplied InputStream.
Class E
Explanation

A service invoked the pub.io:mark service to mark a location on a stream, but the supplied stream does not implement the mark and reset methods.

Action

If you are invoking a user-written service, either use a different kind of InputStream that implements the mark and reset methods, or do not invoke the pub.io:mark service. Otherwise, contact Software AG Global Support.

IO_NO_RESET_SUPPORT The reset method is not supported by the supplied InputStream.
Class E
Explanation

A service invoked the pub.io:reset service to reset to a location on a stream, but the supplied stream does not implement the mark and reset methods.

Action

If you are invoking a user-written service, either use a different kind of InputStream that implements the mark and reset methods, or do not invoke the pub.io:reset service.

IO_VAR_GT_ZERO ''{0}'' must be greater than zero (0).
Class E
Explanation

The input variable specified is negative or zero, but the value must be a positive number.
Action

Supply a value greater than zero for the indicated input parameter.
FTP_ENC_NOT_MATCH User specified encoding ''{0}'' does not match content encoding received from remote server.
Class
CLIENT_LDAP_NO_CREDENTIALS No LDAP credentials provided
Class
CLIENT_LDAP_MISSING_INPUT {0} is a required input
Class
CLIENT_LDAP_NOTIF_EXISTS Notification for {0} is already registered
Class
CLIENT_LDAP_NO_NOTIF Notification for {0} does not exist
Class
CLIENT_INVALID_PRIVATE_KEY Invalid private key provided
Class
CLIENT_INVALID_CERT_CHAIN Invalid certificate chain provided
Class
CLIENT_INVALID_PARTNER_CERT Invalid partner certificate provided
Class
OPE_INTERNAL_ACCESS_DENIED Access to internal passwords denied
Class
OPE_PASSWORD_REQUIRED Password input is required
Class
OPE_SEC_PASSWORD_REQUIRED Password input must be WmSecureString
Class
OPE_OLD_PASSWORD_REQUIRED Old password input is required
Class
OPE_NEW_PASSWORD_REQUIRED New password input is required
Class
OPE_INVALID_PASSWORD Password must be of type WmSecureString
Class
OPE_KEY_ALREADY_EXISTS Password for key already exists
Class
OPE_KEY_DOES_NOT_EXIST Password for key does not exist. Must add password as new entry
Class
OPE_KEY_IS_NULL Key cannot be null
Class
OPE_KEY_IS_EMPTY Key cannot be empty
Class
OPE_UTIL_INVALID_INPUT Must input string, bytes, or chars
Class
XML_NOT_PROVIDED XML needs to be provided.
Class
NODE_SELECTOR_EMPTY A set of values for nodeSelectors must be provided.
Class
NO_RECIPIENT Either a recipientID or a recipientCert must be provided.
Class
XML_PARSE_EXC The XML could not be parsed.
Class
XPATH_CONTXT_FAILURE Unable to set up the XPath context.
Class
IMPROPER_KEY_INFO The keystore or key alias information is incorrect.
Class
BASE_URI_EMPTY_WHEN_ENVLPING A value for baseURI must be provided for an enveloping signature.
Class
URI_PROVIDES_NO_CTNT The reference URI did not provide any content to sign.
Class
SIGNATURE_SEL_EMPTY The signatureSelector parameter must contain a value.
Class
SIGNATURE_NOT_FOUND The signature could not be found.
Class
INVALID_PARAM_TYPE Parameter [{0}] is not of type: [{1}]
Class
COLUMN_IS_MISSING Column [{0}] is missing for the parameter: [{1}]
Class
KEY_DOES_NOT_EXIST key[{0}] does not exist in the pipeline
Class
VALUE_NOT_A_NUMBER [{0}] could not be converted to a number
Class
VALUE_NOT_A_DATE [{0}] could not be converted to a date
Class
INVALID_DATE_PATTERN Invalid date pattern[{0}] specified.
Class
FILE_DOES_NOT_EXISTS File [{0}] does not exist
Class
FILE_IS_A_DIRECTORY File [{0}] exists, but is a directory
Class
DIR_CANNOT_CREATED Directory [{0}] cannot be created
Class
FILE_READONLY File [{0}] exists, but is read-only
Class
DIRECTORY_DOES_NOT_EXIST Directory [{0}] does not exist
Class
NOT_A_DIRECTORY [{0}] is not a directory
Class
FAILED_TO_DELETE Failed to delete original file [{0}] after copying the [{1}]
Class
FAILED_TO_LOAD_PROPS Error reading properties file: [{0}]
Class
NOT_SERIALIZABLE originalObject parameter does not implement java.io.Serializable interface
Class
FILE_ALREADY_EXISTS File [{0}] already exists
Class
PARAM_NUMLIST_CONVERSION_FAILED PARAM_NUMLIST [{0}]: [{1}] could not be parsed
Class
SMIME_KEY_ENTRY_NULL No PrivateKey entry found for key alias {0}.
Class
INDEX_NOT_IN_RANGE Invalid index[{0}]. Value should be between {1} and {2}
Class
EMPTY_PARAM {0} cannot be empty
Class
INVALID_HOLIDAY_DATE_PATTERN Invalid holiday date pattern [{0}] specified in the holidays.cnf file
Class
INVALID_HOLIDAY_DATE Could not parse the holiday date [{0}] specified in the holidays.cnf file using the pattern [{1}]
Class
INVALID_WEEKEND Invalid weekend [{0}]. Valid value should be one of the following: 'sunday', 'monday', 'tuesday', 'wednesday', 'thursday', 'friday', 'saturday'
Class
NOT_AN_ARRAY 'itemList' parameter should be an array
Class
OSCOMMAND_ACCESS_DENIED Specified command [{0}] is not on the allowedOSCommands list in the OSCommands.cnf file
Class
WORKING_DIR_DOESNOT_EXIST [{0}] may not exist or it may not be a directory
Class
WORKING_DIR_ACCESS_DENIED Specified working directory [{0}] is not on the 'allowedWorkingDirectories' list in the OSCommands.cnf file
Class
INVALID_SIGNATURE_NODE_SELCTOR_XPATH Unable to find the node corresponding to the provided signature node selector xpath {0}.
Class
ENCRYPT_CERT_NOT_FOUND Unable to find the encryption certificate for recipient {0}.
Class
UNABLE_TO_RESOLVE_CERT_FOR_SIGNATURE_VERIFICATION Unable to resolve the certificate to verify the signature.
Class
INVALID_SCHEMA_LOC_PROVIDED An invalid schema location pair was provided
Class
HANDLER_FOLDER_NON_EMPTY Folder{0} is not empty
Class
Explanation

The specified folder must be empty.
Action

Delete the contents of the specified folder or specify an empty folder.
HANDLER_INVALID_FOLDER_NAME Invalid folder name {0}. Error : {1}
Class
Explanation

The specified folder name is invalid.
Action

Specify a valid folder name.
HSM_KEYSTORE_NOT_SUPPORTED HSM based Keystore is not supported
Class
RESPONSE_CODE_NOT_ALLOWED Applications cannot use an HTTP Status-Code of {0}
Class E
Explanation

Only valid HTTP Status-Codes may be supplied.
Action

Supply a valid HTTP Status-Code.
PIPELINE_RESTORE_FAILED Could not restore pipeline from file {0}.
Class E
Explanation

The pub.flow:restorePipelineFromFile service failed because the specified pipeline file could not be found in the IntegrationServer_directory\pipeline directory.

Action

Make sure the specified pipeline file exists in the IntegrationServer_directory\pipeline directory, and then restore the pipeline.
PIPELINE_SAVE_FAILED Could not save pipeline to file {0}.
Class E
Explanation

The pub.flow:savePipelineToFile service failed because the IntegrationServer_directory\pipeline directory could not be found or does not exist.

Action

Make sure the IntegrationServer_directory\pipeline directory exists, and then save the pipeline.
OAUTH_2_VALID_VALS {0} must be "{1}" or "{2}".
Class E
Explanation

The service failed because the specified input variable contains an invalid value. The values allowed for the input variable are listed in the message text.

Action

Enter a valid value for the input variable.
OAUTH_4_VALID_VALS {0} must be "{1}", "{2}", "{3}" or "{4}".
Class E
Explanation

The service failed because the specified input variable contains an invalid value. The values allowed for the input variable are listed in the message text.

Action

Enter a valid value for the input variable.
OAUTH_ONE_REQS_OTHER If {0} is supplied, {1} must also be supplied.
Class E
Explanation

The service failed because the combination of input variables defined in the service is invalid. The message text lists the required input variable combinations.

Action

Provide a valid combination of input variables.
OAUTH_ONE_VAL_REQS_OTHER If {0} is "{1}", {2} must be supplied.
Class E
Explanation

The service failed because the combination of input variables defined in the service is invalid. The message text lists the required input variable combinations.

Action

Provide a valid combination of input variables.
OAUTH_5_VALID_VALS {0} must be "{1}", "{2}", "{3}" or "{4}" or "{5}".
Class E
Explanation

The service failed because the specified input variable contains an invalid value. The values allowed for the input variable are listed in the message text.

Action

Enter a valid value for the input variable.
OAUTH_3_VALID_VALS {0} must be "{1}", "{2}" or "{3}".
Class E
Explanation

The service failed because the specified input variable contains an invalid value. The values allowed for the input variable are listed in the message text.

Action

Enter a valid value for the input variable.
OAUTH_ONE_VAL_REQS_2OTHERS If {0} is "{1}", {2} and {3} must be supplied.
Class E
Explanation

The service failed because the combination of input variables defined in the service is invalid. The message text lists the required input variable combinations.

Action

Provide a valid combination of input variables.
88.1 SOAPException: {0}
Class U
Explanation

The SOAP message handler could not process the message because an error occurred.
Action

Examine the details element in the SOAP exception message for information about the specific failure that occurred.
88.2 Failed registering SOAP Processor, missing parameter: {0}
Class E
Explanation

Integration Server failed to add the specified SOAP processor to the processor registry using the pub.soap.processor:registerProcessor service.

Action

Examine the service input and make sure that the fully qualified service name is specified correctly for input parameter "svcName".
88.3 Failed registering SOAP Processor {0} as directive {1}; directive already registered
Class E
Explanation

Integration Server failed to add the specified SOAP processor to the processor registry using the pub.soap.processor:registerProcessor service.

Action

Make sure that the "directive" parameter specifies the correct directive. (Directive names are case-sensitive.) In addition, make sure that the specified directive is not already registered in the SOAP Processor registry. Often, this error occurs because the registry already contains a processor registered to the specified directive.

88.4 Failed registering SOAP Processor {0} as directive {1}; unknown service {0}
Class E
Explanation

Integration Server failed to add the specified SOAP processor to the processor registry using the pub.soap.processor:registerProcessor service.

Action

Examine the service input and make sure that the fully qualified service name is specified correctly for input parameter "svcName". (Service names are case-sensitive.) Often, this error occurs because the service does not exist on the Integration Server.

88.5 Failed unregistering SOAP Processor, missing parameter: {0}
Class E
Explanation

The pub.soap.processor:unregisterProcessor service failed to execute because the "directive" parameter was not supplied.
Action

Examine the service input and make sure that the "directive" parameter specifies the correct directive. (Directive names are case-sensitive.) Often, this error occurs because the directive is not specified.

88.6 Failed unregistering SOAP Processor {0}; no such directive registered
Class E
Explanation

Integration Server failed to remove the specified processor from the SOAP Processor registry using the pub.processor:unregisterProcessor service.

Action

Make sure that the "processorName" parameter specifies the correct directive. (Remember that directive names are case-sensitive.) In addition, make sure that the specified directive is currently registered in the SOAP Processor registry. It may have already been removed. Usually, this error occurs because the registry does not contain a processor registered to the specified directive.

88.7 Failed registering SOAP Processor {0} as directive {1}; invalid character(s) in directive
Class E
Explanation

Integration Server failed to add the specified processor to the SOAP Processor registry using the pub.processor:registerProcessor service.

Action

Examine the service input and make sure that the value for the "directive" parameter only contains characters that are part of a Unicode identifier. See the description of the Java standard for the full range of Unicode values. Usually, this error occurs because the specified directive contains characters that are not part of a Unicode identifier.

88.8 Failed registering JAX Handler {0}; Handler already registered
Class
88.9 Failed initializing JAX Handler {0}; error {1}
Class
88.10 Failed destroying JAX Handler {0}; error {1}
Class
88.11 Failed registering JAX Handler {0}, missing parameter {1}
Class
88.12 Failed unregistering JAX Handler {0}; handler not registered
Class
88.13 Failed unregistering JAX Handler {0}, missing parameter {1}
Class
88.14 Failed listing JAX Handlers, missing parameter {0}
Class
88.15 Failed finding JAX Handler {0}, missing parameter {1}
Class
88.16 Failed finding JAX Handler {0}, handler not registered
Class
88.17 Failed finding JAX Handler for header {0}:{1}
Class
88.20 pub.client:soapClient SOAP request sent: {0}
Class
88.22 pub.client:soapClient OutputValidationError - pipeline: {0} result: {1}
Class
88.23 pub.client:soapClient InputValidationError - result: {0}
Class
88.24 Encode input ({0}): {1}
Class
88.26 Decode input ({0}): {1}
Class
88.28 Service handler {0} could not be registered. A service handler by that name already exists
Class E
Explanation

A service handler with the provided name already exists.
Action

Specify a unique name for the service handler.
88.29 Error initializing handler {0}. Error {1}
Class E
Explanation

An error occurred while initializing the JAX-RPC header handler.
Action

The init() method of the JAX-RPC handler threw an error. Correct the error in init() method.
88.30 Error destroying service handler {0}. Error:{1}
Class E
Explanation

An error occurred while destroying the JAX-RPC handler.
Action

The destroy() method of the JAX-RPC Handler has thrown an error. Correct the error in destroy() method.
88.31 Service handler {0} could not be registered. Missing required parameter {1}
Class E
Explanation

A parameter required to register the service handler was not provided.
Action

Provide the missing parameter.
88.32 Service handler {0} could not be unregistered. A service handler by that name is not registered
Class E
Explanation

The specified service handler is not registered.
Action

Provide the name of a registered service handler.
88.33 Service handler {0) could not be unregistered. Missing required parameter {1}
Class E
Explanation

The service handler could not be unregistered because a required parameter is missing.
Action

Provide the missing parameter.
88.34 Registered service handlers could not be listed. Missing required parameter {0}
Class E
Explanation

The list of registered service handlers could not be created because a required input parameter was not provided.
Action

Provide the missing input parameter.
88.35 Service handler {0} could not be found. Missing required parameter {1}
Class E
Explanation

Service handler could not be found because a required input parameter was not provided.
Action

Provide the missing input parameter.
88.36 Service handler {0} could not be found. Service handler is not registered
Class E
Explanation

A service handler with the provided name does not exist.
Action

Register a service handler with the provided name or specify the name of an existing registered service handler.
88.37 Could not find service handler for header {0}:{1}
Class E
Explanation

The QName of the header does not correspond to a registered service handler.
Action

Verify that the QName of the header corresponds to a registered service handler or register a service handler for the provided universal name.

88.38 Error while processing asynchronous SOAP response received by the consumer Web service descriptor {0}. SOAP Message : {1}
Class E
Explanation

Integration Server failed to process the asynchronous SOAP response directed to the consumer web service descriptor specified in the message.

Action

Check the server log and error log to find possible causes of this error and take corrective steps.
88.39 Error while processing asynchronous SOAP response received by the consumer Web service descriptor {0}.
Class E
Explanation

Integration Server failed to process the asynchronous SOAP response directed to the consumer Web service descriptor specified in the message, possibly because the SOAP response is not well formed.

Action

Check the server log and error log to find possible causes of this error and take corrective steps.
88.100 WS Security processing failed : Unable to convert SOAPMessage into a Document : {0}
Class
88.101 WS Security processing failed : Unable to convert Document into a SOAPMessage : {0}
Class
88.102 WS Security processing failed : A valid Document was not specified. Unable to create SOAPMessage
Class
88.103 WS Security processing failed : UsernameToken supported only with PasswordType as Text
Class
88.104 WS Security processing failed : Invalid Credentials. User name {0}
Class
88.105 WS Security processing failed : Authentication failed for user : {0}
Class
88.106 WS Security processing failed : X509 Authentication failed with exception : {0}
Class
88.107 WS Security processing failed : Unable to create Keystore
Class
88.108 WS Security processing failed : Unable to create Crypto
Class
88.109 WS Security processing failed : Invalid private key passed in to the Web service connector.
Class
88.110 WS Security processing failed : Invalid certificate chain passed in to the Web service connector.
Class
88.111 WS Security processing failed : Error while reading the private key/certificates from the Web service endpoint
Class
88.112 WS Security processing failed : Error while operating on Keystore
Class
88.113 WS Security processing failed : Unable to resolve partner certificate for encrypting the response
Class
88.114 WS Security processing failed : Untrusted certificate chain
Class
88.115 WS Security processing failed : Error during response encryption while retrieving partner certificate from the certificate mapper.
Class
88.116 WS Security processing failed : Invalid outbound security policy. Username token assertion not supported in the response
Class
88.117 WS Security processing failed : Invalid outbound security policy. X509Authentiction token assertion not supported in the response
Class
88.118 WS Security processing failed : Unable to resolve private key for signing or decrypting the message
Class
88.119 WS Security processing failed : Unexcected error occurred while accessing the Keystore/Truststore
Class
88.120 WS Security processing failed : Unable to resolve partner certificate for encrypting the request
Class
88.200 WS Security processing failed: Unable to retrieve {0} provider Web service endpoint alias named "{1}"
Class E
Explanation

Integration server could not find the provider Web service endpoint alias with the type and name specified in the message.
Action

Create an appropriate provider Web service endpoint alias.
88.201 WS Security processing failed: Decryption of encrypted key failed because the key is encrypted with an unknown certificate.
Class E
Explanation

Integration Server is unable to find a private key corresponding to the certificate used to encrypt the key.
Action

Configure an appropriate keystore in the WS Security Properties section of the appropriate consumer or provider Web service endpoint alias or by using the Decryption Key option under Security > Certificates in the Integration Server Administrator.

88.202 WS Security processing failed: Unable to resolve the private key required for signing the SOAP request.
Class E
Explanation

Private key required for signing the SOAP request is not configured.
Action

Configure a keystore by adding the values in the WS Security Properties section of the appropriate consumer Web Service endpoint alias or by using the Signing Key option under Security > Certificates in the Integration Server Administrator.

88.203 WS Security processing failed: Unable to resolve the private key required for signing the SOAP response.
Class E
Explanation

Private key required for signing the SOAP response is not configured.
Action

Configure a keystore by adding the values in the WS Security Properties section of the appropriate provider Web Service endpoint alias or by using the Signing Key option under Security > Certificates in the Integration Server Administrator.

88.204 WS Security processing failed: Invalid partner certificate passed into the Web service connector.
Class E
Explanation

Value provided for auth/message/partnerCert field while executing the Web service connector is invalid.
Action

Provide a valid certificate for auth/message/partnerCert.
88.205 WS Security processing failed: Invalid partner certificate provided in the endpoint alias "{0}".
Class E
Explanation

Partner certificate file provided in the endpoint alias mentioned in the message is invalid.
Action

Specify a valid partner certificate file in the endpoint alias mentioned in the message.
88.206 WS Security processing failed: Unable to resolve the private key required for decrypting the SOAP request.
Class E
Explanation

Private key required for decrypting the SOAP request is not configured.
Action

Configure a keystore by adding the values in the WS Security Properties section of the appropriate provider Web service endpoint alias or by using the Decryption Key option under Security > Certificates in the Integration Server Administrator.

88.207 WS Security processing failed: Unable to resolve the private key required for decrypting the SOAP response.
Class E
Explanation

Private key required for decrypting the SOAP response is not configured.
Action

Configure a keystore by adding the values in the WS Security Properties section of the appropriate consumer Web service endpoint alias or by using the Decryption Key option under Security > Certificates in the Integration Server Administrator.

88.208 WS Security processing failed: Decryption failed because the SOAP message is encrypted with an unknown certificate.
Class E
Explanation

Integration server is unable to find a private key corresponding to the certificate used to encrypt the message.
Action

Configure an appropriate keystore in the WS Security Properties section of the appropriate consumer or provider Web service endpoint alias or by using the Decryption Key option under Security > Certificates in the Integration Server Administrator.

88.209 WS Security processing failed: Signature verification failed because the certificate associated with the sigining private key is unknown.
Class E
Explanation

Integration server is unable to find a certificate corresponding to the private key used to sign the message.
Action

Ensure that the certificate corresponding to the private key used to sign the message is imported into the certificate mapper using Security > Certificates > Configure Client Certificates in the Integration Server Administrator.

88.210 WS Security processing failed: Error retrieving certificate from certificate mapper.
Class E
Explanation

Integration Server failed to retrieve the certificate corresponding to the private key that was used to sign the message. Integration Server encountered an unexpected error when attempting to retrieve the certificate from the certificate mapper.

Action

Probable cause is that the embedded database of Integration Server that is used to store the certificates is corrupted. Contact Software AG Global Support.

88.211 WS Security processing failed: Binder for the SOAP action "{0}" in the Web service descriptor "{1}" not found. Integration Server will use server private keys and certificates for handling WS-Security.
Class W
Explanation

Integration Server cannot find the binder for the specified SOAP action in the Web service descriptor. Integration Server is unable to use the private keys and certificates from the endpoint alias. As a result, Integration Server will use the server private keys and certificates.

Action

Ensure that the correct SOAP action is specified in the incoming SOAP request.
88.212 WS Security processing failed: HSM keystores are not supported.
Class E
Explanation

The Integration Server WS-Security functionality does not support HSM keystores.
Action

Use a supported keystore type, for example, PKCS12 or JKS.
88.213 WS Security processing failed: Integration server only supports Username token with password type {0}, but received with password type {1}.
Class E
Explanation

Incoming SOAP request has an unsupported password type in the Username token. Integration Server supports Username tokens with passwords of type: {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0}#PasswordText only.

Action

Ensure that the SOAP request the requester/client sends has a valid Username token.
88.214 WS Security processing failed: Unable to retrieve {0} consumer Web service endpoint alias named "{1}"
Class E
Explanation

Integration server could not find the consumer Web service endpoint alias with the type and name specified in the message.
Action

Create an appropriate consumer Web service endpoint alias.
NOT_ELEMENT_NODE Invalid node: XML blocks must be in a container
Class E
INVALID_XML Invalid node: must be well-formed XML
Class E
BODY_MISSING_NS Invalid Body Entry. SOAP Body Entries must have a namespace name.
Class E
HEADER_MISSING_NS Invalid Header Entry. SOAP Header Entries must have a namespace name.
Class E
SOAPCODER_NOT_FOUND Soap Coder not found for a {0} SOAPMessage
Class E
SERVICE_NOT_FOUND Service not found for soapAction = {0}
Class E
WSD_SOAP_VERSION_MISMATCH SOAP Version Mismatch: SOAP Version "{0}" in request does not match the SOAP version "{1}" of the Web service.
Class E
INVALID_WSD_TYPE External WSDL URL does not exist for {0}, its a service first WSD.
Class E
WSD_SOAP_RESPONSE_VERSION_MISMATCH SOAP Version Mismatch: SOAP Version "{0}" in response does not match the SOAP version "{1}" of the Web service.
Class E
FAULT_RETURNED_BY_SERVICE Fault returned by invoked service
Class E
CANT_GET_SIZE Attachment Processing Failed: Can't get the size of the attachment due to an I/O Error
Class E
CANT_GET_CONTENT_IO_ERROR Attachment Processing Failed: Can't retrieve the content due to an I/O Error
Class E
NULL_CONTENT Attachment Processing Failed: Attachment contains 'null' content
Class E
NULL_DH Attachment Processing Failed: The value for Data Handler is 'null'
Class E
NULL_DH_IS Attachment Processing Failed: Data Handler contains 'null' Input Stream
Class E
NULL_WSD MTOM Attachments Processing Failed: Cannot convert SOAP Message to XOP Package; 'null' value for 'Web Service Descriptor'
Class E
88.9321 MTOM Attachments Processing Failed: Cannot convert SOAP Message to XOP Package; base64Binary encoded data is not in the Canonical Lexical form
Class E
Explanation

Base64Binary encoded data is not in Canonical Lexical form; it contains line break characters or tabs.
Action

Convert the Base64Binary data into Canonical Lexical form.
INVALID_SOAP_MESSAGE MTOM Attachments Processing Failed: Cannot convert SOAP Message to XOP Package; invalid SOAP Message
Class E
IO_ERROR MTOM Attachments Processing Failed: Cannot convert SOAP Message to XOP Package; I/O Error occurred
Class E
CONTENT_ID_MISSING MTOM Attachments Processing Failed: Cannot convert XOP Package to SOAP Message; 'Content-Id' header field is missing in some of the attachments
Class E
ENCODING_NOT_SUPPORTED MTOM Attachments Processing Failed: Cannot serialize the XOP Message; unable to retrieve bytes from SOAP String using the SOAP Message Content Encoding
Class E
CANT_MIME_SERIALIZE MTOM Attachments Processing Failed: Cannot serialize the XOP Message; MIME serialization has failed
Class E
INVALID_OUTER_CONTENT_TYPE MTOM Attachments Processing Failed: Cannot de-serialize the input MIME Stream; value of the 'Content-Type' header of the MIME message is not equal to 'multipart/related'
Class E
INVALID_OUTER_TYPE_PARAM MTOM Attachments Processing Failed: Cannot de-serialize the input MIME Stream; value of the 'type' parameter of the 'Content-Type' header of the MIME message is not equal to 'application/xop+xml'
Class E
INVALID_OUTER_START_INFO MTOM Attachments Processing Failed: Cannot de-serialize the input MIME Stream; value of the 'start-info' parameter of the 'Content-Type' header of the MIME message is not equal to 'application/soap+xml'
Class E
INVALID_ROOT_PART_CONTENT_TYPE MTOM Attachments Processing Failed: Cannot de-serialize the input MIME Stream; 'Content-Type' header of the Root MIME Part is invalid
Class E
ROOT_PART_CONTENT_TYPE_MISMATCH MTOM Attachments Processing Failed: Cannot de-serialize the input MIME Stream; 'Content-Type' header of the Root MIME Part does not match with the 'type' parameter of the MIME message
Class E
ROOT_PART_TYPE_PARAM_MISMATCH MTOM Attachments Processing Failed: Cannot de-serialize the input MIME Stream; value of 'type' parameter of the 'Content-Type' header of the Root MIME Part does not match with the value of the 'start-info' parameter of the MIME message
Class E
NOT_SOAP_12_MESSAGE MTOM Attachments Processing Failed: Cannot de-serialize the input MIME Stream; SOAP Message in the Root MIME part is not of version 1.2
Class E
INVALID_ROOT_PART_CONTENT MTOM Attachments Processing Failed: Cannot de-serialize the input MIME Stream; Root MIME Part contains invalid SOAP Message
Class E
INVALID_MIME_STREAM MTOM Attachments Processing Failed: Cannot de-serialize the input MIME Stream; input stream is not a valid MIME stream
Class E
NULL_SIG MTOM Attachments Processing Failed: Cannot convert SOAP Message to XOP Package; Some of the operation in a 'Web Service Descriptor' contains 'null' value for either input or output signature
Class E
WSD_NOT_FOUND Could not find Web Service Descriptor with name {0}
Class E
WSD_HANDLER_NOT_FOUND Handler {1} not associated with Web Service Descriptor {0}
Class E
POLICY_NOT_FOUND Could not find policy with name {0}
Class E
MISSING_REQUIRED_PARAMETER Missing required parameter : {0}
Class E
FIRST_NODE_MISSING_QNAME First element of the SOAP-ENV:Body must have a QName
Class E
ILLEGAL_BOOLEAN_1_2 Invalid BOOLEAN value {0} for variable {1}; must be true or false
Class E
HEADER_VALIDATION_FAILED SOAP Header data does not conform to Header Record: {0}
Class E
SERVICE_HANDLER_ACCESS_DENIED Access denied to Handler Service {0} in the Handler Chain
Class E
INVALID_HEADER_COUNT Provided header data for the header named ''{0}'' exceeds the number of headers expected by Web Service Descriptor ''{1}''
Class E
UNABLE_TO_DETERMINE_SOAP_VERSION Unable to determine SOAP version. Make sure that entry has a valid parent.
Class E
UNKNOWN_NAMESPACE Invalid namespace: {0}
Class E
INVALID_URI_SYNTAX Invalid WSDL; URISyntaxException - Invalid URI found in the {0} attribute of the {1} element - BASE={2} URI={3}
Class E
Explanation

The WSDL document used to create a WSDL first provider web service descriptor or a consumer web service descriptor contains a URI with invalid characters or syntax at the specified location.

Action

Correct the invalid URIs in the WSDL document and attempt to create the web service descriptor again.
PORT_NOT_UNIQUE Port ''{0}'' is not unique within service ''{1}''
Class E
Explanation

When creating a consumer Web service descriptor from a WSDL with the specified service, the service definition contains multiple ports that all have the same name.

Action

Update the WSDL so that the port name is unique within the service definition.
MISSING_LOCATION Schema definition not found for imported namespace(s):{0}
Class E
Explanation

While creating a consumer Web service descriptor or a WSDL first provider Web service descriptor from a WSDL document, Integration Server determined that the WSDL document contained one or more xsd:import elements that did not specify the schemaLocation attribute. Consequently, the schema processor in Integration Server cannot locate the schema definition for the imported namespace and Web service descriptor creation fails. When this message appears at run time, the {0} in the message is replaced by the list of the imported namespaces for which a schemaLocation attribute is not specified.

Action

Correct the WSDL document by adding a valid schemaLocation attribute for each xsd:import element that did not specify a schemaLocation. The value of the schemaLocation attribute is a URI to the XML Schema definition for the imported namespace. Alternatively, modify the WSDL document by adding in inline schema definition for each namespace with a missing schemaLocation to the wsdl:types element in the WSDL document. Then attempt to create the Web service descriptor from the WSDL document.

RECORD_ALREADY_EXIST Cannot create element ''{0}''; a document type or schema with this name already exists on the Integration Server.
Class E
Explanation

While trying to pull a document from the Broker, Integration Server determined that a record being referenced already existed on the Integration Server. As a result, synchronization could not continue.

Action

When synchronizing document types, clear the "Overwrite existing elements when importing referenced elements" check box.
INVALID_FIELD_NAME Cannot create field ''{0}'' in Broker document type for ''{1}''; this field name is not valid on the Broker. The Broker will transport the field contents, which will be visible to Integration Server clients only.
Class
CANNOT_GET_RECORD Cannot retrieve ''{0}''; document type with this name does not exist on the Integration Server.
Class
NORMAL_RECORD_ALREADY Cannot make ''{0}'' unpublishable; it is not a publishable document type.
Class
EVENT_DESCP_ALREADY Cannot make ''{0}'' publishable; it is already a publishable document type.
Class
FOUND_RECUSIVE_RECORD Cannot create field ''{0}'' in Broker document type for ''{1}''; recursive types cannot be represented on the Broker. The Broker will transport the field contents, which will be visible to Integration Server clients only.
Class
ENV_FIELD_ALREADY_EXISTS Cannot make ''{0}'' publishable; it contains the field name '_env'.
Class
INVALID_EVENTTYPE_NAME Cannot make document type ''{0}'' publishable; this name is not valid.
Class
REF_RECORD_NOT_EXIST Cannot make ''{0}'' publishable; the referenced document type ''{1}'' does not exist.
Class
FOUND_DUP_RECORD_NAME Cannot create field ''{0}'' in Broker document type for ''{1}''; field with duplicate names are not permitted on the Broker.
Class
MISSING_SCHEMA_REF SimpleType with the name ''{0}'' does not exist on the Integration Server.
Class
COULD_NOT_LOCK_NODE Could not lock node ''{0}''{1}
Class
COULD_NOT_CREATE_NODE Could not create node ''{0}''. User ''{1}'' does not have write permission on folder ''{2}''.
Class
NAMESPACE_WO_PREFIX Document to XSD error: Field {0} cannot be represented in XML Schema. The field contains an XML Namespace property but the field name does not contain a prefix
Class E
Explanation

A service for which a service first provider web service descriptor is being created uses an IS document type that contains a field with an assigned XML namespace property value. However, the field name does not include a prefix to associate with the XML namespace. That is, the field name is not in the format prefix:localName.

Action

Either add a prefix to the field name using the format prefix:localName or remove the value assigned to the XML namespace property. Important! Some protocols require the use of an XML namespace. Review the documentation for service signature requirements for service first provider web service descriptors.

XMLDATA_NOT_SUPPORTED Document to XSD error: Document type {0} cannot be represented in XML Schema. The document type is an XML document type.
Class E
Explanation

Integration Server cannot create an XML Schema definition from an XML document type. Integration Server can create an XML Schema definition from an IS document type only. This error can appear whenever Integration Server creates an XML schema definition, such as when executing the pub.schema:createXSD service or when generating WSDL from a web service descriptor.

Action

Replace the XML document type with an IS document type.

01 Specified instance {0} is not a multiple of {1}.
Class Error
Explanation

The object instance in the JSON input is not a multiple of the value specified in the schema.
Action

Ensure that the object instance in the JSON input is a multiple of the value specified in the schema.
02 Specified numeric instance: {1} is greater than the allowed maximum value: {0}.
Class Error
Explanation

The value of the numeric instance in the JSON input is not less than or equal to the value specified in the schema.
Action

Reduce the specified value in the JSON input to be less than or equal to the maximum value allowed in the schema.
03 Specified numeric instance is not strictly less than the allowed maximum value: {0}.
Class Error
Explanation

The value of the numeric instance in the JSON input is greater than the value specified in the schema.
Action

Reduce the specified value in the JSON input to be strictly less than the maximum value allowed in the schema.
04 Specified numeric instance: {1} is less than the required minimum value: {0}.
Class Error
Explanation

The value of the numeric instance in the JSON input is not greater than or equal to the value specified in the schema.
Action

Change the specified value in the JSON input to be greater than or equal to the minimum value required in the schema.
05 Specified numeric instance is not strictly greater than the required minimum value: {0}.
Class Error
Explanation

The value of the numeric instance in the JSON input is less than the value specified in the schema.
Action

Change the specified value in the JSON input to be greater than the minimum value required in the schema.
06 Specified string: {0} of length: {1} is longer than the allowed maximum value: {2}.
Class Error
Explanation

The length of the string provided in the JSON input is greater than the value specified in the schema.
Action

Reduce the length of the string in the JSON input to be less than or equal to the maximum length specified in the schema.
07 Specified string: {0} of length: {1} is shorter than the required minimum value: {2}.
Class Error
Explanation

The length of the string provided in the JSON input is less than the value specified in the schema.
Action

Increase the length of the string in the JSON input to be greater than or equal to the minimum value specified in the schema.
08 Specified string: {0} does not match the ECMA 242 pattern: {1}.
Class Error
Explanation

The string provided in the JSON input does not match the pattern specified in the schema.
Action

Ensure that the input string matches the pattern specified in the schema.
10 Schema allows only {0} elements in an array, but the specified instance has {1} elements.
Class Error
Explanation

The array has elements other than those specified in the schema.
Action

Remove additional elements from the array to include only those that are specified in the schema.
11 Schema allows a maximum of {0} elements in an array, but the specified instance has {1} elements.
Class Error
Explanation

The specified array has more elements than the maximum allowed in the schema.
Action

Remove additional elements from the array to ensure that the total number of elements is less than or equal to the maximum allowed in the schema.

12 Schema requires a minimum of {0} elements in an array, but the specified instance has {1} elements.
Class Error
Explanation

The specified array has fewer elements than the minimum required in the schema.
Action

Add more elements to the array to ensure that the total number of elements is greater than or equal to the minimum required in the schema.

13 Array must not contain duplicate elements.
Class Error
Explanation

The specified array has duplicate elements.
Action

Remove duplicate elements from the array to ensure that it contains only unique elements.
15 Schema allows a maximum of {0} properties, but the specified object instance has {1} properties.
Class Error
Explanation

The specified object instance has more properties than the maximum allowed in the schema.
Action

Remove additional properties to ensure that the number of properties in the object instance is less than or equal to the maximum allowed value in the schema.

16 Schema requires a minimum of {0} properties, but the specified object instance has {1} properties.
Class Error
Explanation

The specified object instance has more properties than the minimum required in the schema.
Action

Add properties to ensure that the number of properties in the object instance is greater than or equal to the minimum required value in the schema.

17 Specified object instance must have the following required properties: {0}. The following properties are missing: {1}.
Class Error
Explanation

The object instance must have all the required properties specified in the schema.
Action

Add the required properties that are missing to the object instance.
20 Specified object instance has the following additional properties that the schema does not allow: {0}.
Class Error
Explanation

The object instance has properties other than those specified in the schema.
Action

Remove the additional properties from the object instance.
21 Property {0} is missing the following required property dependencies: {1}.
Class Error
Explanation

The JSON input does not contain dependency details for the specified property.
Action

Add the dependency for the specified property to the JSON input.
23 Specified instance value: {0} not found in enumeration with the following possible values: {1}.
Class Error
Explanation

The specified value is not among the possible enumeration values given in the schema.
Action

Make the required changes so that the specified values is among the possible enumeration values given in the schema.
25 Specified instance type: {0} does not match any of the allowed primitive types: {1}.
Class Error
Explanation

The specified input does not match any of the primitive types allowed in the schema.
Action

Change the input type to match the primitive types allowed in the schema.
26 Specified instance failed to match all the required schemas. Matched only {0} out of {1}.
Class Error
Explanation

The specified instance does not match all the schema instances.
Action

Change the input content so that it matches all the specified schema instances.
27 Specified instance failed to match at least one required schema out of {0}.
Class Error
Explanation

The specified instance does not match at least one of the schema instances.
Action

Change the input content so that it matches at least one of the specified schema instances.

28 Specified instance failed to match exactly one schema. Matched {0} out of {1}.
Class Error
Explanation

The specified instance matches more than one of the schema instances.
Action

Change the input content so that it matches exactly one of the specified schema instances.

29 Specified instance should not have matched the schema.
Class Error
Explanation

The specified instance matches the schema.
Action

Change the input content to not match the specified schema.
WARNING_JAX_RPC_HANDLERS_PRESENT JAX-RPC handlers are not supported when the Pre-8.2 compatibility mode is false. The following handlers will be ignored at run time: {0}
Class W
Explanation

Integration Server only supports JAX-RPC handlers for use with Web service descriptors that run in pre-8.2 compatibility mode (i.e., when the Pre-8.2 compatibility mode property is true).

Action

To continue using the JAX-RPC handler, change the Web service descriptor to run in pre-8.2 compatibility mode. If you do not want to run the Web service descriptor in pre-8.2 compatibility mode, replace the JAX-RPC handler with a service handler that has the same behavior.

WARNING_PORT_TYPE_NAME_CHANGED Port type names of all the binders will be changed to "{0}". As a result, all bindings in the generated WSDL will use the same port type.
Class W
Explanation

When a Web service descriptor's Pre-8.2 compatibility mode property is set to false, Integration Server generates WSDL with all the bindings referring to same port type. As a result, when you change the Pre-8.2 compatibility mode property from true to false, Integration Server changes the port type names of all the binders to (wsdName)_PortType, where (wsdName) is the Web service descriptor name.

Action

Depending on your web service client framework, you may need to regenerate or recreate existing Web service clients from the WSDL.

INVALID_MIXED_USE_AND_STYLE All binders must have the same binding style and use when Pre-8.2 compatibility mode is false.
Class E
Explanation

When a Web service descriptor's Pre-8.2 compatibility mode property is set to false, Integration Server does not allow the Web service descriptor to have binders that have different binding styles and use. Integration Server issues this message when either you are attempting to create a new binder for a Web service descriptor and the new binder has a different binding style or use from the existing binders, or when you are trying to consume a WSDL to create a Web service descriptor and WSDL has multiple bindings with different style and use.

Action

If you are trying to create a new binder for a Web service descriptor, use the same binding style and use as the existing binders. If you are trying to consume a WSDL that contains multiple bindings with different style and use, split the WSDL into multiple WSDLs that each use the same style and use.

INVALID_MULTIPLE_PORT_TYPES Multiple port types are not supported when Pre-8.2 compatibility mode is false.
Class E
Explanation

Tthe WSDL document used to create the Web service descriptor consists of multiple port types. When creating a Web service descriptor in Designer, Integration Server does not support multiple port types.

Action

Split the WSDL document that consists of multiple port types into multiple WSDL documents that each use a single port type. Then, create Web service descriptors from each WSDL document.

WARNING_MTOM_STREAMING_DISABLED MTOM streaming is not supported when the Pre-8.2 compatibility mode is true.
Class W
Explanation

When the Pre-8.2 compatibility mode property of a Web service descriptor is set to true, Integration Server does not support MTOM streaming of attachments. Integration Server issues this message when you change the Pre-8.2 compatibility mode property from false to true and when at least one of the operation's input or output signature contains a field of type Object and the java wrapper type is set to com.wm.util.XOPObject.

Action

To continue using MTOM streaming, set the Pre-8.2 compatibility mode property of the Web service descriptor to false. If you want to run the Web service descriptor in pre-8.2 compatibility mode, ensure that the attachment size is not very large to avoid out of memory errors.

OPERATION_NOT_FOUND Operation not found for soapAction = {0}
Class E
Explanation

Integration Server could not find the operation for the SOAP action specified in the incoming SOAP request.
Action

Ensure that the correct SOAP action is specified in the incoming SOAP request. For a service first provider, if needed, you can edit the SOAP action to operation map present in the binder properties.

ENDPOINT_SERVICE_NOT_FOUND Web service cannot be found for endpoint reference (EPR) = {0}
Class E
Explanation

Integration Server could not find the Web service with the specified endpoint reference.
Action

Ensure that the Web service descriptor with the endpoint reference exists in the Integration Server.
BINDING_OPERATION_NOT_FOUND Operation can not be found for endpoint reference (EPR) = {0} and soapAction = {1}
Class E
Explanation

Integration server could not find the operation in the Web service identified with the specified endpoint reference and SOAP action.

Action

Ensure that the operation with the specified SOAP action is present in the Web service descriptor identified by the endpoint reference.

APLICABLE_ONLY_FOR_WSD_WITH_COMPATIBILITY_MODE_ENABLED You cannot use this service against the specified Web service descriptor because its Pre-8.2 compatibility mode property is set to false.
Class E
Explanation

Either pub.soap.utils:resetWSDEffectivePolicy or pub.soap.utils.setWSDEffectivePolicy services were specified with a Web service descriptor with Pre-8.2 compatibility mode property set to false. These services can only be used with Web service descriptors that are running in pre-8.2 compatibility mode (i.e., the Pre-8.2 compatibility mode property is set to true)

Action

Change the Web service descriptor's Pre-8.2 compatibility mode property to true.
SERVICE_EXCEPTION Error occurred while invoking a service : {0}
Class E
Explanation

The Integration Server encountered an internal error while invoking a service. More information about the error is provided in the error message.

Action

Contact Software AG Global Support.
UNIMPLEMENTED_EXCEPTION Not implemented
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
UNKNOWN_SESSION Unknown session: {0}
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
INVALID_PARAMETER Parameter {0} specified for method is invalid
Class E
Explanation

The parameter that you specified is not valid.
Action

Specify a valid parameter.
OBJECT_STATUS_FAILED FAILED
Class E
Explanation

Integration Server is unable to retrieve the status of Repository Server V2.
Action

Ensure that the port and host information that you specified to retrieve the status of Repository Server V2 is correct.
INEXISTENT_SERVICE Service {0} doesn't exist or was removed.
Class E
Explanation

The service that you are trying to execute does not exist in Integration Server.
Action

Ensure that the service exists in Integration Server.
INEXISTENT_PACKAGE Package {0} doesn't exist or was removed.
Class E
Explanation

The package that you are trying to access does not exist or is deleted.
Action

Ensure that the package you want to access exists in the IntegrationServer_directory\packages directory.
INEXISTENT_PORT Port {0} doesn't exist or was removed.
Class E
Explanation

The e-mail port that you are trying to access is not configured or enabled.
Action

Ensure that the e-mail port you want to access is configured and enabled.
ACCESS_DENIED Access was denied to resource {0}
Class E
Explanation

The Integration Server encountered an internal error due to resource access.
Action

Contact Software AG Global Support.
JAVA_EXCEPTION A Java exception occurred {0}
Class E
Explanation

Integration Server encountered an unexpected error.
Action

Contact Software AG Global Support.
INEXISTENT_RESOURCE Resource {0} doesn't exist or was removed.
Class E
Explanation

The Integration Server encountered an internal error due to resource access.
Action

Contact Software AG Global Support.
ISKeyStoreBundle.getKeyForJournalLogger(DEFAULT_ILIVE_TRUSTSTORE_CREATION_ERROR) Error: Truststore alias "DEFAULT_INTEGRATION_LIVE_TRUSTSTORE" cannot be created. Details: {0}
WIN32_UNABLE_REG_NTLMCRA_HANDLER Unable to register NTLM Challenge Response Authentication handler
Class E
Explanation

A handler was registered and then re-registered without first being unregistered.
Action

Register a handler only once. If you want to re-register a handler, first unregister it.
46.1 Could not initialize {0} Listener. Invalid port specified: {1}
Class E
Explanation

While attempting to initialize a port, Integration Server detected that the port was improperly configured. Specifically, an invalid port number was specified for the port in the server.cnf, ports.cnf, or listeners.cnf file.

Action

Edit the appropriate configuration file and specify a port number from 1 through 65534 that is not already in use.
46.6 Cannot initialize {0} Listener on port {1}. No socket available.
Class E
Explanation

While trying to initialize an HTTP listener, Integration Server determined that the socket associated with the requested port is already in use by another application. As a result, the requested port is unavailable.

Action

Specify a port that is not already in use, or disable the application that is using the requested port.
46.7 {0} Access denied. Connection disallowed {1}
Class W
46.19 Unable to establish connection to Enterprise Gateway Server {0}:{1}. Exception: {2}.
Class S
Explanation

The Internal Server could not establish a connection to Enterprise Gateway Server for the reason indicated.
Action

Ensure that the Enterprise Gateway registration port is enabled.
46.20 Unable to establish connection to Enterprise Gateway Server {0}:{1}. Internal Server was not authenticated on the Enterprise Gateway.
Class S
Explanation

Internal Server authentication failed on the Enterprise Gateway.
Action

Ensure that the registration credentials specified during the creation of the Internal Server port are correct.
46.24 Unable to establish connection to Enterprise Gateway Server {0}:{1}. Internal Server version {2} does not support Enterprise Gateway version {3}
Class E
Explanation

The version of Enterprise Gateway Server must be equal to or higher than the versions of Integration Servers acting as the Internal Server.

Action

Use the same or higher version of Enterprise Gateway Server.
46.25 Rejected a connection from Internal Server {0} on port {1}. Enterprise Gateway version {2} does not support Internal Server version {3}
Class E
Explanation

The version of Enterprise Gateway Server must be equal to or higher than the versions of Integration Servers acting as the Internal Server.

Action

Use the same or higher version of Enterprise Gateway Server.
47.1 47.1 obsolete
Class E
Explanation

While attempting to initialize a port, Integration Server detected that the port was improperly configured. Specifically, an invalid port number was specified for the port in the server.cnf, ports.cnf, or listeners.cnf file.

Action

Edit the appropriate configuration file and specify a port number from 1 through 65534 that is not already in use.
47.2 Resuming HTTPS Listener on port {0}
Class
47.3 Starting HTTPS Listener on port {0}
Class
47.5 Stopping HTTPS Listener on port {0}
Class
47.8 Could not start HTTPS Listener on port {0}. No SSL support available.
Class
47.9 Error in SSL setup: {0}
Class
47.10 Certificate Authority was recognized
Class
47.11 Certificate Authority was not recognized {0}
Class
47.12 Client does not have a digital certificate
Class
47.13 Access denied to host {0}
Class
47.14 Error in SSL Setup: {0}
Class
47.15 Error in SSL setup: Not all certificate fingerprints were loaded
Class
47.16 The required client certificate was not provided by {0}
Class
47.17 Could not start HTTPS listener on port {0}
Class
47.18 Aborting connection from {0}: {1}
Class E
Explanation

Integration Server encountered a problem while trying to establish a secure connection with the client at the indicated address.
Action

Make sure the client properly supports SSL connections.
47.19 SSL listener restricted to 128 bit or better encryption:
Class E
Explanation

Integration Server configuration property watt.net.ssl.server.strongcipheronly is set to "true", but the list of ciphers includes weak ciphers. Integration Server displays these weak ciphers in subsequent messages.

Action

Either use only strong ciphers, or set watt.net.ssl.server.strongcipheronly to "false".
47.20 cipher {0} = {1} ({2} bit)
Class E
Explanation

Integration Server configuration property watt.net.ssl.server.strongcipheronly is set to "true", but the list of ciphers includes the weak ciphers displayed by this message.

Action

Either use only strong ciphers, or set watt.net.ssl.server.strongcipheronly to "false".
47.21 Aborting connection request on {0} port {1}, a certificate map does not exist for {2}
Class E
Explanation

A client presented a certificate to Integration Server, but the certificate has not been mapped to a user on Integration Server. For a certificate to be mapped to a user, the certificate must have been previously stored on Integration Server and associated with that user.

Action

Use the Server Administrator interface to import the certificate to Integration Server and map it to the appropriate user.
47.22 Access denied to host: Hostname verification failed. The CN "{0}" in the subject DN of the certificate does not match the hostname "{1}".
Class
47.23 Aborting connection, Server Certificate purpose verification failed
Class
47.9998 Exception --> {0}
Class U
Explanation

Integration Server encountered an error. This message contains the exception produced by the server.
Action

Examine the error message to determine the problem.
57.1 Delete operation completed
Class I
61.1 Access denied to remote server {0} for user {1}
Class
61.2 Expired remote connection to {0} for user {1}
Class
61.3 Established new remote connection to {0} for user {1}
Class
61.4 Established new remote connection to {0}
Class
61.5 Error expiring remote connection: {0}
Class
61.6 Error expiring remote connection for user {0}: {1}
Class
61.7 Expired remote connection to {0}
Class
61.8 Could not create default Remote Server Alias: {0}
Class
61.9 The default Remote Server Alias was created.
Class
68.1 Successfully logged in as user {0} on host {1}
Class
68.2 Login attempt as user {0} on host {1} failed
Class
68.4 Processed {0} new message(s)
Class
68.5 Error processing email message. {0}.
Class
68.6 EMAIL Access denied. Connection disallowed from host {0}
Class
68.7 EMAIL Access denied. Invalid host in senders address: {0}
Class
68.8 EMAIL Access denied. Could not figure out senders email address.
Class
68.9 EMAIL Access denied. User {0} not allowed to run service {1}
Class
68.10 Could not decode body part of email message
Class
68.11 Could not decode message body into input parameters
Class
68.12 Listener key not provided. Not running email listener
Class
68.13 Error processing service: {0}
Class
68.14 Could not get message content: {0}
Class
68.15 Could not get body part of message: {0}
Class
68.16 Error parsing message: {0}
Class
68.17 Could not get message UID: {0}
Class
68.18 Could not start listener threads: {0}
Class
68.20 Could not get message with uid {0}
Class
68.21 Could not process message with uid {0}
Class
68.22 Could not send reply message to {0}. Check email address and smtp settings.
Class
68.23 Received reply message. Not processing
Class
68.24 The connection to the IMAP server {0} for user {1} was temporarily lost. Some messages may not have been processed.
Class
68.25 No content handler for content type {0}. Service {1} called without content handler.
Class
68.26 Content type: {0} Subject: {1}
Class
68.27 {0} lost connection to {1} server {2}
Class
68.28 {0} reconnected to {1} server {2}
Class
EMAIL_SKIP_REPLY_MSG Skipping processing reply email message
Class E
Explanation

The subject line of the e-mail received on the e-mail port starts with "Re:". Hence, it is treated as a reply message and its processing is skipped.

Action

Investigate why the subject line of the e-mail starts with "Re:". Usually, this is an indicator of a reply message.
EMAIL_SKIP_RETURNED_MSG Skipping processing returned email message
Class E
Explanation

The subject line of the e-mail received on the e-mail port starts with "Returned". Hence, it is treated as a message that is returned by the recipient and its processing is skipped.

Action

Avoid the error and process the returned messages by setting the extended property "watt.server.email.processReturnedEmails" to true.

EMAIL_INVALID_SVC Invalid service: {0}
Class E
Explanation

Integration Server received a message on the e-mail port listener, but the service specified to perform the message processing is invalid. The service that Integration Server selects to execute message processing depends on how the server is configured. Integration Server searches for the value in the locations listed below in order of precedence:

- The Global Service field on the Email Client Configuration screen on the Server Administrator.

- The e-mail message from the e-mail client.

- The Default Service field on the Email Client Configuration screen on the Server Administrator.

The problem is often that the service name is specified in the wrong case (service names are case sensitive). Other causes could be that no service was specified at all or the service is not in its specified location.

Action

Make sure the service name is specified correctly and exists in the location specified.
EMAIL_NO_SVC No such service: {0}
Class E
Explanation

The Integration Server FTP listener encountered an internal error.
Action

Contact Software AG Global Support.
EMAIL_UNKNOWN_CONTENT Unknown content type: {0}
Class E
Explanation

The Integration Server does not support the MIME type specified.
Action

Only use the MIME types supported by the Integration Server.
EMAIL_SERVER_ERROR Server Error: {0}
Class E
Explanation

An unexpected error occurred when invoking the service.
Action

If the exception details provided as part of the message does not give any hint, contact Software AG Global Support.
SMTP_INVALID_HEADER Invalid header {0}
Class E
Explanation

The header specified is invalid.
Action

Ensure that a valid header is provided. Keep the following points in mind when specifying a header:

1. Header name should not contain spaces.

2. Header value should not be empty.

3. Header name and value should not be the same.
SMTP_INVALID_TO_FIELD Invalid TO field: {0}
Class E
Explanation

Either the recipient e-mail address is not provided in the "to" field or the address provided is invalid.
Action

Enter a valid e-mail addess in the "to" field. Refer to "pub.client:smtp" service in webMethods Integration Server documentation for further details.

SMTP_INVALID_CC_FIELD Invalid CC field: {0}
Class E
Explanation

The e-mail address entered in the "cc" field is invalid.
Action

Enter a valid e-mail addess in the "cc" field. Refer to "pub.client:smtp" service in webMethods Integration Server documentation for further details.

SMTP_INVALID_BCC_FIELD Invalid BCC field: {0}
Class E
Explanation

The e-mail address entered in the "bcc" field is invalid.
Action

Enter a valid e-mail addess in the "bcc" field. Refer to "pub.client:smtp" service in webMethods Integration Server documentation for further details.

SMTP_NO_FILE_CONTENT No filename nor content included in the attachment!
Class E
Explanation

Content or filename is not provided in the attachments field.
Action

Provide either the content or the filename in the attachments field. Refer to "pub.client:smtp" service in webMethods Integration Server documentation for further details.

SMTP_INVALID_CHARSET charset {0} is not valid
Class E
Explanation

Character set encoding specified for the body or attachement is invalid.
Action

Ensure that the Character set encoding specified is valid. Refer to "pub.client:smtp" service in webMethods Integration Server documentation for further details.

SMTP_INVALID_MAILHOST_FIELD Invalid MAILHOST field: {0}
Class E
Explanation

No value is provided for the mailhost parameter of the pub.client:smtp service.
Action

Provide a valid value for the mailhost parameter of the pub.client:smtp service. Refer to "pub.client:smtp" service in webMethods Integration Server documentation for further details.

SMTP_INVALID_RECIPIENT_FIELD Invalid Message Recipient: {0}
Class E
Explanation

Either the recipient e-mail address is not provided in the "to" field or the address provided is invalid.
Action

Enter a valid e-mail addess in the "to" field. Refer to "pub.client:smtp" service in webMethods Integration Server documentation for further details.

71.1 Could not initialize FTP Listener. Invalid port specified: {0}
Class
71.2 Suspending FTP(S) Listener on port {0}
Class
71.3 Can not build data channel, the exception is {0}, the message is {1}
Class
71.4 The port range specified for passive data connections to FTP(S) listeners is invalid: please specify both "watt.net.ftpPassivePort.min" and "watt.net.ftpPassivePort.max" values
Class
71.5 The port range specified for passive data connections to FTP(S) listeners is invalid: "watt.net.ftpPassivePort.min" value is not a number
Class
71.6 The port range specified for passive data connections to FTP(S) listeners is invalid: "watt.net.ftpPassivePort.max" value is not a number
Class
71.7 The port range specified for passive data connections to FTP(S) listeners is invalid: "watt.net.ftpPassivePort.min" and "watt.net.ftpPassivePort.max" values are not within 1-65534 range
Class
71.8 The port range specified for passive data connections to FTP(S) listeners is invalid: "watt.net.ftpPassivePort.min" value is greater than "watt.net.ftpPassivePort.max" value
Class
71.9 All ports within the port range specified for passive data connections to FTP(S) listeners are in use
Class
71.10 PORT command refused. The PORT address {0} does not match the original host address {1}.
Class E
Explanation

In FTP active mode, the PORT command specifying the IP address does not match the client IP address in the control connection. Possible reason for this could be that your FTP client is compromised.

Action

Contact your network security team to take necessary action in case your FTP client is compromised.
71.11 Cannot build data connection: client address {0} does not match the original host address {1}.
Class E
Explanation

In FTP passive mode, the client address associated with the control port does not match the client address in the data port connection. Possible reason for this could be that your FTP client is compromised.

Action

Contact your network security team to take necessary actions in case your FTP client is compromised.
FTPD_NO_PORT_PASV Cannot build data connection: use PORT or PASV first
Class E
Explanation

The Integration Server failed to connect to a port on the FTP client because the FTP client did not provide valid port information.
Action

Check the Integration Server configuration and restart the server. If the problem persists, contact Software AG Global Support.
FTPD_CANNOT_CREATE {0}: cannot create
Class E
Explanation

An FTP client application connected to an FTP port on the Integration Server and tried to create a remote directory on the FTP server, but the "mkdir" command failed.

Action

Make sure the directory name was specified correctly. Also, examine the remote file system and make sure that you have permission to create the directory there.

FTPD_CANNOT_DELETE {0}: cannot delete
Class E
Explanation

An FTP client application connected to an FTP port on the Integration Server and tried to delete a file on the FTP server, but the "delete" command failed.

Action

Make sure the file name was specified correctly and that the file exists on the remote server. Also, examine the remote file system and make sure that you have permission to delete the file from the remote file system.

FTPD_CANNOT_RENAME Cannot rename File to {0}
Class E
Explanation

An FTP client application connected to an FTP port on the Integration Server and tried to rename a file on the FTP server, but the "rename" command failed.

Action

Make sure the old and new file names were specified correctly. Also, examine the remote file system and make sure that you have write permission to both the old and new file names.

FTPD_UNABLE_TO_MAKEDIR Unable to make dir {0}
Class U
Explanation

An FTP client application connected to an FTP port on the Integration Server and tried to create a remote directory on the FTP server, but the "mkdir" command failed.

Action

Make sure the directory name is specified correctly. Also, examine the remote file system and make sure that you have the appropriate permissions to create the directory there.

FTPD_UNABLE_TO_DELETE Unable to delete {0}
Class U
Explanation

An FTP client application connected to an FTP port on the Integration Server and tried to delete a file on the FTP server, but the "delete" command failed.

Action

Make sure the file name is specified correctly and that the file exists. Also, examine the remote file system and make sure that you have permission to delete the file.

FTPD_UNABLE_TO_RENAME Unable to rename to {0}
Class U
Explanation

An FTP client application connected to an FTP port on the Integration Server and tried to rename a file on the FTP server, but the "rename" command failed.

Action

Make sure the old and new file names are specified correctly. Also, examine the remote file system and make sure that you have write permission to both the old and new file names.

FTPD_CANNOT_WRITE Cannot write
Class E
Explanation

Integration Server failed to put the file in the folder directory. The file must be in the service directory for processing.
Action

Put the file in the service directory.
FTPD_INVALID_TRANS_NAME Invalid transaction name. Not in the form 'tid[;mime.type][;encoding]'.
Class E
Explanation

The MIME type specified in the FTP request is incorrect. It should be in the form of 'tid[;mime.type][;encoding]'."
Action

Make sure to provide the name in the correct format.
FTPD_UNABLE_DETER_MIMETYPE Uable to determine mime type
Class U
Explanation

Integration Server does not support the MIME type specified.
Action

Only use the MIME types supported by Integration Server. Refer to the webMethods Integration Server documentation for more information.

FTPD_CANNOT_READ Cannot read
Class E
Explanation

Ensure that the specified file exists in the FTP server.
Action

The Integration Server failed to read the specified file from the FTP server.
FTPD_NO_SERVICE No such service: {0}
Class U
Explanation

The Integration Server FTP listener encountered an internal error.
Action

Contact Software AG Global Support.
FTPD_UNKNOWN_CONTENT_TYPE Unknown content type: {0}
Class U
Explanation

The Integration Server does not support the MIME type specified.
Action

Only use the MIME types supported by the Integration Server. Refer to the webMethods Integration Server documentation for more information.

FTPD_SERVER_ERROR Server Error: {0}
Class U
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
FTPD_STOR_CANNOT_PUBLISH Cannot publish STOR complete event
Class E
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
FTPD_PASVCONN_REJECTED Cannot build data connection: client address {0} does not match the original host address {1}.
Class E
Explanation

In FTP passive mode, the client address associated with the control port does not match the client address in the data port connection. Possible reason for this could be that your FTP client is compromised.

Action

Contact your network security team to take necessary action in case your FTP client is compromised.
CERTIFICATE_MISSING_DN Issuer DN must be provided
Class E
Explanation

The certificate is incomplete. It must include an Issuer DN.
Action

Supply a certificate that includes an Issuer DN.
CERTIFICATE_MISSING_SERIAL_NUMBER Serial number must be provided
Class E
Explanation

The certificate is incomplete. It must contain a serial number.
Action

Supply a certificate that includes a serial number.
CERTIFICATE_NOT_EXPECTED_FORMAT data provided for certificate not in expected format
Class E
Explanation

Only X509Certificates may be used to identify Integration Server clients.
Action

Supply a valid X509Cerificate.
CERTIFICATE_NOMAPENTRY_EXISTS No map entry exists for the specified information
Class E
Explanation

Internal error.
Action

Contact Software AG Global Support.
CERTIFICATE_MISSING_FILENAME Certificate's file name is required
Class E
Explanation

Certificate Path is empty.
Action

Supply the fully qualified file name for a certificate file.
CERTIFICATE_CERT_FILE_NOTEXIST Specified certificate file does not exist
Class E
Explanation

The Certificate Path field refers to a non-existent file.
Action

Supply the fully qualified file name of a certificate file.
CERTIFICATE_CERT_FILE_EMPTY Specified certificate file is empty
Class E
Explanation

The Certificate Path field refers to an empty file.
Action

Supply the fully qualified file name of a certificate file.
CERTIFICATE_UPDATE_NONEXIST_ENTRY Attempted to update a non-existent entry
Class E
Explanation

Internal error.
Action

Contact Software AG Global Support.
CERTIFICATE_INVALID_USERNAME {0} is not a valid user
Class E
Explanation

The supplied user name does not identify a user on this Integration Server.
Action

Supply a valid user.
DEPENDENCY_MISSING_OLDNAME Missing input for the parameter 'oldName'
Class E
Explanation

Internal error.
Action

Contact Software AG Global Support.
DEPENDENCY_NOSVCEXIST_OLDNAME No service/Document Type exist for: {0}
Class E
Explanation

Internal error.
Action

Contact Software AG Global Support.
DEPENDENCY_MISSING_NEWNAME Missing input for the parameter 'newName'
Class E
Explanation

Internal error.
Action

Contact Software AG Global Support.
DEPENDENCY_NOT_RECORD Not a Document Type: {0}
Class E
Explanation

Internal error.
Action

Contact Software AG Global Support.
DEPENDENCY_NOT_FLOW_SVC Not a flow service: {0}
Class E
Explanation

Internal error.
Action

Contact Software AG Global Support.
DEPENDENCY_MISSING_PATH Missing input parameter: path
Class E
Explanation

Internal error.
Action

Contact Software AG Global Support.
DEPENDENCY_MISSING_NAME No input for the parameter {0}
Class E
Explanation

This is an internal error.
Action

Contact Software AG Global Support.
DEPENDENCY_NODSP_EXIST Specified node {0} not found
Class E
Explanation

Internal error.
Action

Contact Software AG Global Support.
PIPE_MISSING_FILENAME Missing required parameter: 'fileName'
Class
PIPE_MISSING_PIPELINE Missing required parameter: 'pipeline'
Class
XIDL_UNKNOWN_IFC No such folder: {0}
Class
XIDL_INVALID_IFCTYPE Invalid folder type: {0}
Class
XIDL_NULL_IFCNAME Provided folder name is null
Class
XIDL_NULL_SOURCE Provided source is null
Class
XIDL_NULL_PKGNAME Provided package name is null
Class
XIDL_NO_SUCH_IFCNAME No such folder: {0}
Class
XIDL_NO_SUCH_SVC No such service: {0}
Class U
Explanation

Integration Server FTP listener encountered an internal error.
Action

Contact Software AG Global Support.
CODEGEN_NO_SPEC_NO_SIG Must specify either Specification or Signature
Class
CODEGEN_FAILED_REG_SVC Failed to register {0}
Class
NS_NO_SUCH_SVC no such service {0}
Class
NS_NOT_JAVAIM service {0} is not a Java IM
Class
NS_NODE_MISSING_NAME node is missing a name
Class
NS_INVALID_PKG invalid package
Class E
Explanation

An application tried to delete a service, but the package specified does not exist on the Integration Server.
Action

Examine the service input and verify that a valid package name is specified.
NS_NO_NODE_NAME Node name was not provided
Class
NS_NODE_NOT_EXIST Node {0} does not exist
Class
NS_NO_TARGET_NAME Target name was not provided
Class
NS_TARGET_NOT_EXIST Target package does not exist. Create it first
Class
NS_IO_FILE_ERROR IOException occurred file={0}: {1}
Class
NS_SAME_NODE_EXISTS Similarly-named node "{0}" already in use
Class
NS_NO_PKGNAME Package name was not provided
Class E
Explanation

An application tried to export a package, but the package name was not provided.
Action

Examine the service input make sure it provides a valid package name.
NS_PKG_NOT_EXIST {0} package does not exist
Class
NS_NODE_DIR_NOT_EXIST Node directory does not exist
Class
NS_ERROR_CREATE_ZIP_FORNODE IOException occurred creating zip for {0} node
Class
NS_PKG_NOT_FOUND {0} package not found
Class
NS_PKGDIR_NOT_FOUND {0} package directory not found
Class
NS_ERROR_CREATE_ZIP_FORPKG IOException occurred creating zip for {0} package
Class
NS_NO_SUCH_CLASS no such class {0}
Class
NS_PKG_NOT_ENABLED Package {0} is not enabled
Class
NS_CLASS_NOTIN_PKG class not in package
Class
NS_NODE_NOTIN_PKG node is not in a package
Class
NS_NODE_BELONG_INVALID_PKG node belongs to invalid package
Class E
Explanation

An application tried to create a service, but the package name specified to contain the service was missing or invalid.
Action

Examine the service input and make sure a valid package name is provided.
NS_INVALID_IFCNAME not a valid folder name
Class E
Explanation

An application tried to create a new service, but the folder name was missing or invalid.
Action

Examine the service input and verify that a valid folder name is provided.
NS_NODE_NAME_INUSE node name "{0}" already in use
Class
NS_IFCNODE_NOT_EXIST folder node "{0}" in path "{1}" doesn't exist
Class
NS_IFC_EXISTS_INPKG folder node "{0}" exists in package
Class
NS_UNSUPPORTED_NODE_TYPE unsupported node type: {0}
Class
NS_UNABLE_TO_LOCK Unable to lock: {0}. It has been locked by user {1}.
Class
NS_UNABLE_TO_MODIFY_OTHER_USER Unable to modify; node {0} is locked by another user.
Class
NS_UNABLE_TO_PERFORM_DUE_TO_LOCK Unable to perform the required operation. The destination folder has locked services which share a common Java source file.
Class
PACKAGES_MISSING_PKG Required parameter 'package' is missing
Class
PACKAGES_INVALID_VERSION Invalid package version {0}, the accepted format is #.#.#.#.###
Class E
Explanation

The supplied package version is an invalid version number. The correct format is "x.y" or "x.y.z" (x, y, z all must be digits from 0-9, e.g. 2.0, 4.0.1 etc.).

Action

Examine the service input and make sure a valid package version is provided.
PACKAGES_UNKNOWN_NAME Not allowed to add unknown package(s) {0} to dependency list
Class E
Explanation

The package that was added to another package's dependency list does not exist on Integration Server.
Action

Specify the package name again, this time specifying a package that exists on Integration Server and is enabled.
PORTACCESS_PORT_NOT_NUMERIC Port must be numeric
Class
PORTACCESS_INVALID_SERVICE_NAME Invalid Folder/Service Name
Class E
Explanation

The service, folder,or provider Web service descriptor that was added to a port's access list does not exist on Integration Server.

Action

Enter the name of the service, folder, or Web service descriptor again, making sure to specify one that exists on Integration Server.

PORTACCESS_UNABLE_TO_ADDSERVICE Unable to add service to this port
Class
REMOTE_NO_PASSWORD No password specified
Class E
Explanation

The alias created for a remote server omitted the remote server's password.
Action

Enter a valid password in the password field.
REMOTE_MISSING_ALIAS_SVC Missing one or more required parameters: $alias, $service
Class E
Explanation

The pub.remote:invoke service failed to execute because one or both of the required "$alias" or "$service" parameters were not supplied.

Action

Examine the service input and ensure that both the parameters are specified.
REMOTE_NO_REMOTE_SERVER No such remote server: {0}
Class E
Explanation

The pub.remote:invoke service failed to execute because an invalid server alias was provided.
Action

From the Settings>Remote Servers page of the Server Administrator examine the Remote Servers List and make sure an alias exists for the remote server. If not, create one before invoking the pub.remote:invoke service again.

REMOTE_SESSION_REQED_SVR User session required to invoke a protected remote server
Class E
Explanation

Integration Server encountered a serious internal error because the user session object that invokes the service on the remote server is null.

Action

Contact Software AG Global Support.
REMOTE_ACCESS_DENY Access denied to invoke on remote server {0}
Class E
Explanation

The pub.remote:invoke service failed to invoke the service on the remote server because the current user does not have the proper ACL.

Action

Using the Integration Server Administrator, examine the remote server alias properties as well as the service's Execute ACL setting on the remote server. Make sure that the current user has the proper ACL to invoke the service.

REMOTE_SESSION_REQED_SCOPE User session required to invoke a remote server with SESSION scope
Class E
Explanation

Integration Server encountered a serious internal error because the user session object that invokes the service on the remote server is null.

Action

Contact Software AG Global Support.
REMOTE_MISSING_JOBID Missing required parameter: $jobID
Class
SCHEDU_NO_SUCH_JOB No such job: {0}
Class
SCHEDU_NO_SUCH_SVC_LOADED No such service is currently loaded {0}
Class
SCHEDU_INVALID_DATE_FORMAT Invalid Date format.Date must be in YYYY/MM/DD format.
Class E
Explanation

When attempting to schedule a one-time task, an invalid date or time format was specified.
Action

Enter the date and/or time again, this time using the correct format.
SCHEDU_PAST_DATE You specified a date/time in the past
Class
SCHEDU_INVALID_TIME_FORMAT Invalid Time format.Time must be in HH:MM:SS format
Class
SCHEDU_INVALID_INTERVAL Interval must be a positive integer {0}
Class E
Explanation

A repeating task could not be scheduled because the specified interval is not valid.
Action

Specify the interval again, this time specifying a positive integer.
SCHEDU_INVALID_TASK_TYPE Invalid task type: {0}
Class E
Explanation

The WmRoot service wm.server.schedule:createUserTask failed to execute because an invalid task type was supplied. Valid task types are: "once", "repeat", and "complex".

Action

Examine the service input and ensure that the "type" parameter specifies a valid task type.
SERVICES_UNKNOWN_SVC_TYPE Unknown service type: {0}
Class
SERVICES_NSN_MISSING {0} is missing or package is disabled
Class
SERVICES_CANNOT_CREATE_TMPLDIR Templates directory for package {0} could not be created
Class
SERVICES_TMPLFILE_EXISTS Template file exists but is not writable
Class
UTIL_TO_IS_NULL nobody to send message to
Class U
Explanation

Integration Server failed to invoke a service on the remote server using the e-mail port because the "to" parameter was not supplied.

Action

Examine the logic to make sure that it passes the correct input to the "to" parameter when invoking services remotely using the e-mail listener.

UTIL_NO_ATTACHMENT no attachment
Class U
Explanation

Integration Server failed to invoke a service on the remote server using the e-mail port because the "attachments" parameter was not supplied.

Action

Examine the logic to make sure that it passes the correct input to the "attachments" parameter when invoking services remotely using the e-mail listener.

UTIL_ATT_NOT_VALUES attachments must be of type Values[]
Class U
Explanation

Integration Server failed to invoke a service on the remote server using the e-mail port because the input for the "attachments" parameter was not of Values[] type.

Action

Examine the logic to make sure that it passes the correct Values[] input to the "attachments" parameter when invoking services remotely using the e-mail listener.

UTIL_INVALID_FILE_NAME Invalid attachment file {0}
Class E
Explanation

Integration Server failed to invoke a service on the remote server using the e-mail port because the file attachment specified in the "filename" parameter does not exist in the system.

Action

Examine the logic to make sure that it passes a valid file to the "filename" parameter and make sure that it exists in the file system.

UTIL_CONTENT_IS_NULL No filename nor content included in the attachment!
Class
LISTENERS_ERROR_REMOVE An error was encountered removing {0}
Class
PACKAGES_NULL_VERSION Not allowed to add empty package version, the accepted format is *.*
Class E
Explanation

The package dependency list does not specify a version for the package.
Action

Enter a valid package version in the format "x.y" or "x.y.z" (x, y, z all must be digits from 0-9, e.g. 2.0, 4.0.1 etc.).
PACKAGES_UNABLE_TO_DELETE Unable to perform operation. {0} has entities locked by another user. Please unlock these entities before performing this operation
Class
UNIVERSALNAME_MISSING_PARAMETER A required parameter {0} was not supplied
Class
UNIVERSALNAME_ALREADY_DEFINED The Universal Name {0} is already defined for {1} in the registry
Class
UNIVERSALNAME_DEFINED_IN_NS The Universal Name {0} is already defined as a Service or Document
Class
NS_UNABLE_TO_SAVE Cannot {0} changes because the file(s) representing {1} may have been changed to 'Read-Only'. To {0} changes, change the following file(s) from 'Read-Only' to 'Read/Write' either manually or through a source control system: {2}
Class E
Explanation

Integration Server could not compile the Java or C service, possibly because the files have changed to Read-Only.
Action

Examine the file permissions and change the file permission from Read-Only to Read/Write, either manually or through a source control system.

NS_UNABLE_TO_LOCK_USER_UNKNOWN Unable to lock: {0}. It might be locked by another user.
Class
UNIVERSALNAME_INVALID_CHAR The Universal Name {0} contains an invalid character
Class E
Explanation

This is an internal error.
Action

Contact Software AG Global Support.
UTIL_INVALID_INPUT Invalid input
Class E
Explanation

A WmRoot service failed to execute because the service input is not of the type required by the service.
Action

Examine the error stack trace to determine the exception that was thrown and the service that threw it. For example, the service may require an IData object, but the supplied input was not an instance of IData.

SCHEDU_CANNOT_SCHEDULE Cannot schedule service. Input has unsupported datatypes
Class
UTIL_MISSING_HEADER Missing required parameter: 'header'
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact wSoftware AG Global Support.
UTIL_INVALID_HEADER 'header' must be of type IData
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
NS_NO_READ_PRIVS Cannot perform operation without Read ACL privileges on {0}
Class
NS_NO_PACKAGE_BROWSE_PRIVS Cannot perform operation without List ACL on package {0}
Class
NS_BAD_EXECUTE_ACL Cannot set Execute ACL {1} on {0}. You do not have permission to access the {1} ACL.
Class
NS_BAD_BROWSE_ACL Cannot set List ACL {1} on {0}. You do not have permission to access the {1} ACL.
Class
NS_BAD_READ_ACL Cannot set Read ACL {1} on {0}. You do not have permission to access the {1} ACL.
Class
NS_BAD_WRITE_ACL Cannot set Write ACL {1} on {0}. You do not have permission to access the {1} ACL.
Class
NS_BAD_PACKAGE_BROWSE_ACL Cannot set List ACL {1} on package {0}. You do not have permission to access the {1} ACL.
Class
NS_NO_BROWSE_PRIVS Cannot perform operation without List ACL privileges on {0}
Class E
Explanation

You do not have List access to the element that you tried tried to lock for editing or the service you attempted to view.
Action

Contact the Administrator of the Integration Server to request List ACL permission for the service or element.
NS_NO_WRITE_PRIVS Cannot perform operation without Write ACL privileges on {0}
Class
SVC_MISSING_PARAM Required parameter ''{0}'' is missing in invoke of {1}
Class
PUBLISH_REQUIRED_PARAM_TYPE_IDATA Invalid input. ''{0}'' is a required parameter of type IData
Class
PUBLISH_REQUIRED_PARAM_TYPE_STRING Invalid input. ''{0}'' is a required parameter of type String
Class
PUBLISH_PARAM_TYPE_STRING Invalid input. ''{0}'' must be of type String
Class
PUBLISH_PARAM_TYPE_POSITIVE_INT Invalid input. ''{0}'' must be a positive integer
Class
PUBLISH_PARAM_TYPE_BOOLEAN Invalid input. ''{0}'' must be true or false
Class
BROKER_UTIL_IFC_NOT_FOUND Folder {0} not found
Class
NS_BROKER_REPORTS_ERROR Unable perform the operation because Broker reports: {0}
Class
BROKER_UTIL_INVALID_COND_TYPE Not a valid condition type
Class E
Explanation

An invalid condition type was provided. The condition type must be "simple" or "join."
Action

Examine the service input and ensure that the condition type provided is "simple" or "join."
BROKER_UTIL_INVALID_TRIGGER_NAME Not a valid trigger name. Trigger name must be of type String
Class E
Explanation

An invalid trigger name was provided. The trigger name must be of type String.
Action

Examine the service input and ensure that the trigger name is of type String.
BROKER_UTIL_TRIGGER_NOT_FOUND Specified trigger name does not exist: {0}
Class
BROKER_UTIL_NOT_A_PUB_RECORD Could not validate data corresponding to publishable document: {0}
Class
BROKER_UTIL_TRIGGER_NOT_SATISFIED Trigger condition not satisfied by this document: {0}
Class
BROKER_UTIL_INVALID_COND_NAME Not a valid condition name. Condition name must be of type String
Class E
Explanation

During a trigger test, Integration Server encountered an invalid condition name. The condition name must be of type String.
Action

Examine the service input and ensure that the condition name is of type String.
BROKER_UTIL_COND_NOT_FOUND Specified condition name does not exist: {0}
Class E
BROKER_UTIL_TRIGGER_NOT_SATISFIED_AND Trigger condition not satisfied. All documents must be submitted incase of ''AND'' join type
Class
PACKAGES_NOT_EXIST Package ''{0}'' does not exist.
Class
SVC_REQUIRED Trigger condition ''{0}'' does not have a service
Class
PDT_REQUIRED Trigger condition ''{0}'' does not have a document type; A trigger condition must have at least one document type
Class
Explanation

To be considered valid, a trigger condition must identify at least one document type.
Action

Edit the trigger condition to specify a document type.
SVC_NOT_EXIST ''{0}'' does not exist or it is not a service
Class
PDT_NOT_EXIST Document type ''{0}'' does not exist
Class
MUST_BE_PDT ''{0}'' is not a publishable document type.
Class
NS_NODE_NOT_WRITABLE Node ''{0}'' is not writable.
Class
TRIGGER_INVALID_FILTER Invalid filter ''{0}'' for document type ''{1}'': {2}
Class
MULTIPLE_JOIN_CONDITION Multiple join conditions are not allowed in a single trigger.
Class
COPY_ERROR Could not copy folder completely: {0}
Class
DELETE_ERROR Could not delete folder completely: {0}
Class
MOVE_FOLDER_ERROR Could not move folder completely: {0}
Class
MOVE_LOCK_ERROR Reference(s) for ''{0}'' could not be automatically updated, because the element(s) are currently locked.
Class
UPDATE_REF_ERROR Internal reference(s) could not be automatically updated.
Class
TARGET_EXISTS Target node ''{0}'' already exists.
Class
REMOTE_UPDATE_MSG Errors occurred while updating remote aliases ({0} of {1} updates failed). See server logs for more details.
Class
LOCAL_UPDATE_FAILED_NO_CS Local update failed: {0} (Note: The cluster synchronization will not run until all local errors are resolved.)
Class
PASSWORD_REQUIRED Password input is required
Class
SEC_PASSWORD_REQUIRED Password input must be WmSecureString
Class
OLD_PASSWORD_REQUIRED Old password input is required
Class
NEW_PASSWORD_REQUIRED New password input is required
Class
WS_NO_HOST Host Name not specified
Class
WS_NO_WSDL No WSDL specified: wsdlURL or wsdlString input is required
Class
WS_NO_PKGNAME Provided package name is null
Class
WS_NO_NSNAME Provided name is null
Class
WS_INVALID_BINDING Invalid SOAPBinding found: {0}
Class
SCHEDU_DB_ISSUE Cannot schedule service. Error is : {0}
Class
SCHEDU_GENERIC Cannot schedule service. Please contact your System Administrator
Class
SCHEDU_INVALLID_OPTION The Lateness Action option that you have selected is invalid for this Schedule Type
Class
SCHEDU_CANNOT_RESUME This One time task was suspended since it was overdue. It cannot be resumed
Class
SCHEDU_INVALID_LATENESS The lateness time that you have selected is invalid for this Lateness Action. Overdue time must be 0 minutes for 'Run the task immediately' Overdue option and must be greater than 0 minutes for 'Suspend and wait for administrator action' and 'Skip and run at next scheduled time' Overdue options.
Class
SCHEDU_NO_SUCH_USER No such user present: {0}
Class
SCHEDU_CHILD_TASK Cannot update child task
Class
SCHEDU_INVALID_INTERVAL_1 Interval time is greater than or equal to the difference between the start time and end time.
Class
WS_NO_WSD Web Services Descriptor name not specified, or Web Services Descriptor not found
Class
WS_NOT_CONSUMER Web Services Descriptor is not a Consumer, no WSConnectors exist.
Class
WS_DELETE_FAILED Web Services Connector {0} was not deleted. Reason= {1}.
Class
IMPLICT_EXPLICIT_UNIVERSAL_NAME_SAME Implicit and Explicit Universal names of the node are identical. The Universal name is registered for the node {1}
Class
CERTIFICATE_DETAILS_ERROR Unable to get information for user/certificate mapping: {0}
Class E
Explanation

An error was enountered while getting details for a certificate. The error may have occurred while reading from the database or while constructing an X509Certificate object. See the error message for details.

Action

If it is a database error, go to the Settings > JDBC Pools page and use the Test button for the ISInternal functional alias to verify that you can still connect to the database. If you can, it may have been a transient error. Try displaying or importing this certificate again. If you cannot, contact your DBA to troubleshoot your database connection problem. If it is not a database error, contact Software AG Global Support.

SCHEDU_USR_DISABLED Cannot resume the task as the User {0} is disabled.
Class
SCHEDU_USR_REMOVED Cannot resume the task as the User {0} is removed.
Class
WS_INVALID_PORT A positive integer must be provided for the port
Class E
WS_NO_TRANSPORT_USER User Name for Transport not specified
Class
WS_NO_MESSAGE_USER User Name for WS Security not specified
Class
WS_URL_WRONG_BEGINNING URL must begin with "http:" or "https:"
Class
WS_HTTP_METHOD_NULL HTTP method is null
Class
WS_CLIENT_HTTP_EXP1 only use one of: data.stream, data.bytes or data.mimeStream on a POST
Class
WS_CLIENT_HTTP_EXP2 do not use: data.stream, data.bytes or data.mimeStream on a GET
Class
WS_CLIENT_INVALID_PRIVATE_KEY Invalid private key provided
Class
WS_CLIENT_INVALID_CERT_CHAIN Invalid certificate chain provided
Class
WS_CLIENT_INVALID_PARTNER_CERT Invalid partner certificate provided
Class
WS_CLIENT_INVALID_HTTP_METHOD invalid HTTP method: {0}
Class
WS_HTTP_ERROR_WITH_STATUS Http Error: {0} - {1}
Class
NS_UNABLE_TO_MODIFY_SYSTEM Unable to modify; node {0} is system locked.
Class
SCHEDU_INVALID_TIME Invalid Date or Time.
Class
SCHEDU_INVALID_REFERENCES Found unresolved dependent services: {0}
Class
REMOTE_INVOKE_NO_LICENSE Remote Invoke not licensed.
Class
WS_NO_TRANSPORT_TYPE Transport Type not specified
Class
WS_RPC_ENC_SOAP12_NOT_SUPPORTED Binding with style="rpc" and use="encoded" is not supported for SOAP version 1.2. Binding {0} ignored.
Class
Explanation

Integration Server does not support RPC/Encoded for SOAP version 1.2. Integration Server ignores bindings that specify this style/use.

Action

No action is required.
WS_MIXED_USE_NOT_SUPPORTED Bindings or operations with mixed "use" are not supported
Class
WS_INVALID_ASC_HOST Host Name must be ASCII characters
Class
WS_INVALID_ASC_TRANSPORT_USER User Name for Transport must be ASCII characters
Class
WS_INVALID_ASC_TRANSPORT_PASSWORD Password for Transport must be ASCII characters
Class
WS_INVALID_ASC_MESSAGE_USER User Name for WS Security must be ASCII characters
Class
WS_INVALID_ASC_MESSAGE_PASSWORD Password for WS Security must be ASCII characters
Class
WS_DOC_ENC_NOT_SUPPORTED Binding with style="document" and use="encoded" is not supported. Binding {0} ignored.
Class W
URLALIAS_ALREADY_REGISTERED The HTTP URL alias "{0}" is already registered for the path: {1}
Class
URLALIAS_MISSING_PARAMETER A required parameter {0} was not supplied
Class
WS_NO_VALID_BINDINGS_FOUND No valid bindings found in the WSDL.
Class
WS_NO_VALID_SERVICES_FOUND No Valid services found in the WSDL. The WSConnector may not work until a valid _url is given as input.
Class
WS_CLIENT_HSM_KEYSTORE_NOT_SUPPORTED HSM based Keystore is not supported
Class
WS_USUPPORTED_BINDING_EXTENSION2 Unsupported ExtensibleElement ''{0}'' found in Operation ''{1}'' and SOAPBinding ''{2}''
Class
WS_DUPLICATE_SOAP_ACTION_FOUND SOAP Action ''{0}'' already found in Operation ''{1}'' and Binding ''{2}''. SOAP Action must be unique for Operation and or Binding for a specified SOAP Version.
Class
URLALIAS_BADNAME_LEAD_CHAR "{0}" is not a valid HTTP URL Alias name. ''{1}'' leading character prohibited.
Class
URLALIAS_BADPATH_LEAD_CHAR "{0}" is not a valid HTTP URL Alias target path. ''{1}'' leading character prohibited.
Class
URLALIAS_BADNAME_CHAR "{0}" is not a valid HTTP URL Alias name. ''{1}'' character prohibited.
Class
URLALIAS_BADPATH_CHAR "{0}" is not a valid HTTP URL Alias target path. ''{1}'' character prohibited.
Class
URLALIAS_BADNAME_SPACE "{0}" is not a valid HTTP URL Alias name. Space character prohibited.
Class
URLALIAS_BADPATH_SPACE "{0}" is not a valid HTTP URL Alias target path. Space character prohibited.
Class
URLALIAS_BADNAME_LEAD "{0}" is not a valid alias name. HTTP URL Alias must not start with "{1}".
Class
URLALIAS_BADPATH_LEAD "{0}" is not a valid HTTP URL Alias target path. URL path must not start with "{1}".
Class
DEPLOYER_ACTIVATE_DEPLOYMENT_FAILED Deployment activation for deployment ID {0} failed with an exception. For more information, see the Integration Server logs.
Class E
Explanation

The deployment was not activated due to the reason specified in the Integration Server logs.
Action

See the Integration Server logs for more information.
DEPLOYER_DELIVER_ARTIFACTS_FAILED Artifact delivery for deployment ID {0} failed with an exception. For more information, see the Integration Server logs.
Class E
Explanation

The artifacts relating to the specified deployment ID were not delivered due to the reason specified in the Integration Server logs.

Action

See the Integration Server logs for more information.
DEPLOYER_DEL_DELIVERED_ARTIFACTS_FAILED Deletion of artifacts delivered for deployment ID {0} failed with an exception. For more information, see the Integration Server logs.
Class E
Explanation

The artifacts relating to the specified deployment ID were not deleted due to the reason specified in the Integration Server log.

Action

See the Integration Server logs for more information.
DEPLOYER_DEL_CHECKPOINTED_ARTIFACTS_FAILED The deletion of artifacts for checkpoint ID {0} failed with an exception. For more information, see the Integration Server logs.
Class E
Explanation

The artifacts associated with the specified checkpoint ID could not be deleted due to the reason specified in the Integration Server log.

Action

Check the Integration Server log for details.
DEPLOYER_ACTIVATE_CHECKPOINT_NO_ASSETS There are no assets for the specified checkpoint ID: {0}. Deployer cannot activate checkpoint.
Class I
DEPLOYER_CHECKPOINT_ERROR_DURING_EXTRACT Extraction of assets for checkpoint ID {0} failed for the composite {1}. For more information, see the Integration Server logs.
Class E
Explanation

Assets for the specified checkpoint ID could not be extracted due to the reason specified in the Integration Server log.
Action

Check the Integration Server log for details.
DEPLOYER_ACTIVATE_DEPLOYMENT_NO_ASSETS There are no assets for the specified deployment ID: {0}. Deployer cannot activate deployment.
Class I
DEPLOYER_CHECKPOINT_UNSUCCESSFUL Checkpoint operation for the checkpoint ID {0} was not successful. For more information, see the Integration Server logs.
Class E
Explanation

The checkpoint operation failed due to the reason specified in the Integration Server log.
Action

Check the Integration Server log for details.
DEPLOYER_ACTIVATECHECKPOINT_UNSUCCESSFUL Checkpoint activation for the checkpoint ID {0} was not successful. For more information, see the Integration Server logs.
Class E
Explanation

The checkpoint could not be created due to the reason specified in the Integration Server log.
Action

Check the Integration Server log for details.
DEPLOYER_ACTIVATECHECKPOINT_FAILED Checkpoint activation for the checkpoint ID {0} failed with an exception. For more information, see the Integration Server logs.
Class E
Explanation

The checkpoint activation failed due to the reason specified in the Integration Server logs.
Action

See the Integration Server logs for more information.
MISSING_PARAM_NAME Missing required parameter: {0}
Class E
Explanation

A required parameter was not supplied.
Action

Supply a value for the missing parameter and execute the service again.
90.6 recursive IData reference key:'{0}'
Class
90.7 {0} recursive IDataCodable reference key:'{1}'
Class
91.1 {0} in {1} minutes or as soon as idle
Class
91.2 Pending shutdown/restart request has been canceled
Class
91.3 Grace period has expired. Server is shutting down.
Class
91.4 Grace period has expired. Server is restarting.
Class
108.8 Encryption and Signing key pairs have been updated: {0}
Class W
Explanation

The encryption certificate in the user's profile is not synchronized with the one in the JNDI directory. In this case, the signing and encryption key pairs are updated and this warning message is displayed.

Action

Ensure that the encryption certificates are synchronized with those available in the JNDI directory.
108.9 Could not check profile ''{0}'' for key pair update: {1}
Class W
Explanation

When the encryption certificates in the user's profile are not synchronized with those available in the JNDI directory, the signing and encryption key pairs are updated. This warning message is displayed when there are errors when accesing the LDAP directory while updating the key value pairs.

Action

Contact Software AG Global Support.
147.6 Error while closing sftp session: Details: {0}
Class E
Explanation

The session key that you specified has expired.
Action

Ensure that the session corresponding to this session key exists and has not expired.
147.7 Error in sftp session sweeper thread. Details: {0}
Class E
Explanation

Integration Server encountered an error in the SFTP session sweeper thread.
Action

Read through the details provided in the error message and take corrective steps.
1.1 All licenses have been consumed.
Class
1.2 {0} License key expired or invalid.
Class
1.3 {0} License will expire in {1} days.
Class
1.4 Integration Server will shutdown in 30 minutes, unless a valid license key is provided.
Class
1.5 Unable to load package {0} due to invalid license for package {1}.
Class
1.6 Could not add {0} as dependent package due to invalid license.
Class
1.7 Could not load {0} because one of the dependent package is not loaded.
Class
1.8 {0} Functionality disabled due to license restrictions.
Class
1.9 License key file is read-only. License settings cannot take effect until you make the file read/write.
Class
1.10 The license key is not valid with this version of Integration Server. License key is version {0} and Integration Server is version {1}.
Class
1.11 The Integration Server is not licensed by the current license key.
Class U
Explanation

Integration Server has reached its client limit. Your license for Integration Server allows only a certain number of sessions to be used at a time. Integration Server issues this message when the number of users trying to use the server exceeds the number specified in the license.

Action

Check the number of licensed sessions specified in your Integration Server license. Consider upgrading the license to obtain more user "seats" if the number of users requiring access to your Integration Server has increased.

JournalLogger.FAC_LDAP+"."+LUM_LOAD_ERR Error loading LDAP settings: {0}
Class E
Explanation

Integration Server encountered an IOException while reading the ldap.cnf file.
Action

Check to make sure that the operating system user that is running Integration Server has permission to read and write to the ldap.cnf file. In addition, make sure that the ldap.cnf file is a valid XML file and has not been corrupted in some way. As a last resort, delete the ldap.cnf file and reconfigure the LDAP settings from the Server Administrator.

JournalLogger.FAC_LDAP+"."+LUM_SAVE_ERR Error saving LDAP settings: {0}
Class E
Explanation

An IOException occurred while Integration Server was writing the ldap.cnf file.
Action

Check to make sure that the operating system user that is running Integration Server has permission to read and write to the ldap.cnf file and to the server config directory. In addition, make sure that there is sufficient disk space and quota space for creating and writing a new file.

JournalLogger.FAC_LDAP+"."+LUM_NOCS LDAP User Manager enabled, but no LDAP directories are configured
Class W
Explanation

The Integration Server is attempting to perform operations that require a connection to an LDAP server, but the Integration Server is only partially configured to use LDAP. Specifically, the configuration does not include a list of LDAP directories to which the Integration Server can connect.

Action

Use the Integration Server Administrator to configure the Integration Server to connect to one or more LDAP directories. For more information about working with LDAP, refer to the webMethods Integration Server documentation.

JournalLogger.FAC_LDAP+"."+CS_AMBIG Query returned multiple DNs for a single user with filter ({0}={1})
Class W
Explanation

The values specified in the Query DN field on the LDAP directory settings screen are not sufficient to uniquely identify a user. Integration Server uses this field to build a query to send to the LDAP server so that the LDAP server can authenticate the user.

Action

Make sure that the user root, user property, and user names specified on the Query DN field are not ambiguous.
JournalLogger.FAC_LDAP+"."+CS_TIMEOUT Could not get a connection from the pool in the time allowed
Class E
Explanation

Integration Server was unable to connect to the LDAP server because the request to obtain a connection timed out. This error can occur if the LDAP directory server is slow, is under high load, or is experiencing high latency, and there are insufficient connections in the connection pool to meet demand.

Action

This error is probably transient. It is usually sufficient to wait a few seconds and try the operation again (for example logging in, executing a service) when the load has decreased and resources have become available. If the problem persists, then from the LDAP Directory Settings page of the Server Administrator, try increasing the size of the LDAP connection pool. Also check to make sure the LDAP directory server is properly configured and that the network is able to handle the load being placed on it by the application.

JournalLogger.FAC_LDAP+"."+CS_NOCONTEXT Unable to open a connection to {0}
Class E
Explanation

The Integration Server was unable to open a connection to the indicated LDAP directory server.
Action

To resolve this issue, do the following:

- Make sure the LDAP server is running and that the Integration Server has permission to connect to it.

- Make sure that the connection parameters specified on the LDAP Settings screen of the Server Administrator are properly configured.

- If you are using SSL, make sure that the directory URL specified on the LDAP Settings screen specifies an SSL port on the LDAP server and that both the Integration Server and LDAP server support SSL.

- If you are specifying credentials, make sure the principal specified on the LDAP Settings screen of the Server Administrator is correct and that the password matches. This error can also occur if the Integration Server cannot establish a connection to the LDAP server within the configured time limit because of a problem such as network latency. For more information about connecting the Integration Server to an LDAP server, see the webMethods Integration Server documentation.

JournalLogger.FAC_LDAP+"."+CS_QUERY_NE Error querying for user {0}: {1}
Class E
Explanation

During a user log in, the Integration Server encountered an error while performing a query to obtain the user's Distinguished Name.

Action

In the Server Administrator, on the LDAP Settings screen for the LDAP directory, ensure that the user root and user properties are set correctly.

JournalLogger.FAC_LDAP+"."+CS_NO_GATTR Found group {0}, but it contained no attribute {1}
Class W
Explanation

During ACL mapping, Integration Server determined that the value specified in the group attribute field does match the attribute values of the group that Integration Server found.

Action

Make sure the group name attribute field contains a valid group name attribute.
JournalLogger.FAC_LDAP+"."+CS_GQUERY_NE Error querying for groups on {0} with root {1} and filter {2}: {3}
Class E
Explanation

Integration Server encountered an error when looking for LDAP groups to map to an Integration Server ACL.
Action

If the text of the exception indicates a connection issue, try performing the mapping later. Otherwise, check the values specified for group name, filter, and group name attribute on the Map Groups to ACLs screen.

JournalLogger.FAC_LDAP+"."+CS_NOLUM Unable to create ACL mapping: LDAP User Manager not initialized
Class E
Explanation

An attempt to map an LDAP group to an ACL failed because the LDAP User Manager function of the Integration Server is not running. This error occurs when one user disables LDAP while another user is trying to perform ACL mapping.

Action

Use the Integration Server Administrator to check the External User Management Configuration screens for possible configuration problems. In addition, try checking the server and error logs for messages about problems with the LDAP manager. For information about using the Integration Server with an external directory, refer to the webMethods Integration Server documentation.

JournalLogger.FAC_LDAP+"."+CS_NOACL Unable to create ACL mapping: ACL {0} not found
Class E
Explanation

An attempt to map an LDAP group to an ACL failed because the ACL specified on the Map Groups to ACLs screen does not exist. This error occurs if one user deletes the ACL in question when another user is trying to map an LDAP group to it.

Action

Determine why the other user changed the Integration Server configuration then reconfigure the Integration Server to use LDAP, if appropriate. For information about using the Integration Server with an external directory, refer to the webMethods Integration Server documentation.

JournalLogger.FAC_LDAP+"."+CS_GETPW Unable to retrieve password for handle {0}: {1}
Class E
Explanation

The Integration Server is trying to connect to an LDAP server. As part of connecting, the Integration Server needs to send a password to the LDAP server. This error occurs when the Integration Server cannot find the password it stored for this purpose. A likely cause is that the ldap.cnf file was moved from one system to another, but the stored outbound passwords were not.

Action

Make sure the Outbound Password Manager is properly configured, and that its files are readable by the Integration Server process. If the Outbound Password Manager is set up correctly, and the error still occurs, go to the LDAP Configuration screen of the Server Administrator and reenter the existing password.

JournalLogger.FAC_LDAP+"."+CS_STOPW Unable to store password for handle {0}: {1}
Class E
Explanation

The Integration Server was unable to store the password needed to connect to an LDAP server. The Integration Server must supply passwords to many of the applications it connects to. It stores these outbound passwords in encrypted form on the Integration Server. This error occurs when an administrator enters or changes the password, but the Integration Server cannot subsequently store it.

Action

Check to see if the Integration Server is properly configured to handle outbound passwords. Make sure that the following outbound password configuration files reside on the Integration Server and are readable and writable: config/txnPassStore.dat, config/empw.dat, config/configPassman.cnf and config/passman.cnf. Refer to the webMethods Integration Server documentation for more information.

JournalLogger.FAC_LDAP+"."+CS_DELPW Unable to delete password for handle {0}: {1}
Class E
Explanation

An administrator updated the Integration Server configuration so that it no longer connects to an LDAP server. As part of this process, the Integration Server tried to delete the password it uses to connect to the LDAP server, but was unable to. The Integration Serve deletes the LDAP server from the configuration, but the password remains, in encrypted form, on the Integration Server. The most likely cause is that the files used to store outbound passwords on the Integration Server are read-only.

Action

Refer to the webMethods Integration Server documentation for more information about outbound passwords and the files used to store them. Then try to determine why the files are in read-only mode.

JournalLogger.FAC_LDAP+"."+LU_NOLUM Unable to check password: LDAP User Manager not initialized
Class E
Explanation

The Integration Server tried to check the password of an LDAP user but could not because the LDAP user manager is not running. This error occurs when one user updates the Integration Server configuration to disable LDAP directory use while another user is trying to perform an LDAP operation.

Action

Determine why the other user changed the Integration Server configuration. Then, reconfigure the Integration Server to use LDAP, if appropriate. For information about using the Integration Server with an external directory, refer to the webMethods Integration Server documentation.

JournalLogger.FAC_LDAP+"."+LU_MNOLUM Unable to check group membership: LDAP User Manager not initialized
Class E
Explanation

The Integration Server tried to find members of an LDAP group but could not because the LDAP user manager is not running. This error occurs when one user updates the Integration Server configuration to disable LDAP directory use while another user is trying to perform an LDAP operation.

Action

Determine why the other user changed the Integration Server configuration. Then, reconfigure the Integration Server to use LDAP, if appropriate. For information about using the Integration Server with an external directory, refer to the webMethods Integration Server documentation.

JournalLogger.FAC_LDAP+"."+PC_INIT_NE Error initializing a connection to {0}: {1}
Class E
Explanation

The Integration Server encountered an exception while trying to connect to the indicated LDAP server.
Action

Check the following:

- Make sure the LDAP directory server is running and that the Integration Server has permission to access it.

- Make sure the parameters on the External User Management Configuration screens of the Server Administrator have been properly set.

JournalLogger.FAC_LDAP+"."+PC_CLOSE_NE Error closing connection to {0}: {1}
Class W
Explanation

Integration Server encountered an exception while trying to connect to the indicated LDAP server. Integration Server will clean up the connection.

Action

No action is required.
JournalLogger.FAC_LDAP+"."+UPG_FAILED While attempting automatic LDAP configuration, some invalid settings were found. It is necessary to complete the configuration manually.
Class E
Explanation

When you upgrade from Integration Server release 6.1 or earlier to Integration Server release 6.5 or later, the upgrade process tries to automatically configure the external user management facilities in your new Integration Server based on these settings in your old Integration Server. To determine the old configuration settings, the upgrade process looks for the following properties:

watt.server.ldap.server

watt.server.ldap.attr.userId

watt.server.ldap.attr.member

This error indicates that the upgrade process was unable to find one of these properties. The automatic configuration does not continue.

Action

Go to the Security > Users and Groups > External User Management Configuration screen of the Server Administrator and configure the Integration Server to use an external LDAP directory. For additional information, refer to the webMethods Integration Server documentation.

JournalLogger.FAC_LDAP+"."+PC_BAD_AUTH Invalid credentials connecting to {0} as {1}
Class E
Explanation

The Integration Server encountered an Authentication Exception because the indicated user could not log in to the indicated LDAP server.

Action

This error can occur for a number of reasons. Make sure that the DN of the user is valid, the credentials (i.e. password) specified are valid, and the user account is enabled.

JournalLogger.FAC_LDAP+"."+PC_BAD_AUTH_EXPL Invalid credentials connecting to {0} as {1}: {2}
Class E
Explanation

The Integration Server encountered an Authentication Exception because the indicated user could not log in to the indicated LDAP server. The last part of the message <errorMessage> includes extra information provided by the LDAP server about the error. You can use this data to audit authentication errors when the Integration Server connects to Microsoft Active Directory.

Action

This error can occur for a number of reasons. Check to make sure that the DN of the user is valid, the credentials (i.e. password) specified are valid, and the user account is enabled. Note: The errorMessage portion of this error displays only if the watt.server.ldap.extendedMessages property in the server.cnf file is set to true. If you do not find the extended message useful, you can disable extended messaging by setting this property to false.

JournalLogger.FAC_LDAP+"."+LUM_QUERY_USER Error querying for users : {0}
Class E
Explanation

Error while listing users from the LDAP server, a runtime exception occurred while querying users for the provided search criteria.

Action

Ensure that the search criteria is defined properly, the LDAP server is configured properly, and it is running.
JournalLogger.FAC_LDAP+"."+LUM_QUERY_GROUP Error querying for users : {0}
Class E
Explanation

Some errors occurred while searching for a particular group, or a search string in the LDAP Server.
Action

Ensure that the search criteria is defined properly, the LDAP server is configured properly, and it is running.
JournalLogger.FAC_LDAP+"."+CS_RETURNING_EMPTY Bailing out query as {0} is null or empty.
Class W
Explanation

While listing users from the LDAP server, either the directory name suffix or directory name prefix returned from the server is null or empty.

Action

Ensure that the LDAP configuration is correct and the LDAP server is not disconnected.
JournalLogger.FAC_LDAP+"."+CS_USER_NE Error querying for user(s) on {0} with search root {2}: {3}
Class E
Explanation

Error while listing users from the LDAP server, a runtime exception occurred while querying users for the provided search criteria.

Action

Ensure that the search criteria is defined properly, the LDAP server is configured properly, and it is running.
JournalLogger.FAC_LDAP+"."+CS_GQUERY_NULL Found No Group on quering on {0} with root {1} and filter {2}
Class W
Explanation

No group is found in the LDAP server for the search criteria.
Action

Refine the search query to get the required result.
LDAP_GROUP_NOT_EXIST Selected group {0} does not exist.
Class E
Explanation

The Integration Server group associated with the LDAP configuration is deleted.
Action

Ensure that the group selected while configuring LDAP exists. If the group does not exist, you can take one of the following actions:

1) Modify the LDAP configuration to specify another group.

2) Add a group with the same name as the deleted group that was associated with the LDAP configuration.
LDAP_E_NOLUM LDAP User Manager not initialized
Class E
Explanation

A user is trying to execute an operation on the LDAP server but LDAP user manager is not initialized.
Action

Check the LDAP settings.
LDAP_E_SAVEACLS Error saving new ACL Mappings: {0}
Class E
Explanation

A runtime exception occurred while adding new mappings to the LDAP Server.
Action

Ensure that the mapping strings are correct (they should be in the following format - name; dn), the LDAP server is configured properly and it is running.

SERVICE_MISSING_REQUIRED_ARGUMENT Transformation: Required argument "{0}" missing.
Class
SERVICE_MISSING_XML_SOURCE Transformation: No XML source provided
Class
SERVICE_NO_RESULT_TYPE_SPECIFIED Transformation: No result type specified
Class
SERVICE_NO_RESULT_FILENAME_SPECIFIED Transformation: No result filename specified
Class
SERVICE_NO_RESULT_SYSTEMID_SPECIFIED Transformation: No result system ID specified
Class
SERVICE_DOCUMENT_CONVERSION_ERROR Transformation: PipedInputStreamException - {0}
Class
SERVICE_HTTPS_URL_ERROR Transformation: HTTPS URL error - {0}
Class
SERVICE_HTTPS_URL_ERROR_CODE Transformation: HTTPS URL error - Response returned with HTTP protocol error {0}.
Class
SERVICE_MISSING_XSL_PARAM_INPUT XSLT Samples: No XSLT input paramters provided
Class
SERVICE_MISSING_VALID_INPUT XSLT Service: No valid input provided
Class
SERVICE_MISSING_XSL_FILE XSLT Service: No associated .xsl file for this service
Class
6.30 Unable to set javax.net.ssl.keyStore: Keystore location could not be retrieved from {0}.
Class E
Explanation

Integration Server could not set the javax.net.ssl.keyStore system property because Integration Sever could not retrieve the keystore location from the keystore file. Integration Server looks in the keystore file associated with the specified keystore alias. At run time, the {0} in the error message is replaced with the name of the keystore alias assigned to the watt.sever.ssl.keyStoreAlias parameter.

Action

Make sure the keystore alias assigned to the watt.server.ssl.keyStoreAlias parameter contains the correct keystore details including the correct location of the keystore file.

6.31 Unable to set javax.net.ssl.keyStorePassword: Keystore password could not be retrieved from {0}.
Class E
Explanation

Integration Server could not set the javax.net.ssl.keyStorePassword system property because Integration Server could not retrieve the password from the keystore file. Integration Server looks in the keystore file associated with the specified keystore alias. At run time, the {0} in the error message is replaced with the name of the keystore alias assigned to the watt.server.ssl.keyStoreAlias parameter.

Action

Make sure the keystore alias assigned to the watt.server.ssl.keyStoreAlias parameter contains the correct keystore details including the correct password for accessing the keystore file.

6.32 Unable to set javax.net.ssl.trustStore: Truststore location could not be retrieved from {0}.
Class E
Explanation

Integration Server could not set the value of the javax.net.ssl.trustStore system property because Integration Server could not retrieve the truststore location from the truststore file. Integration Server looks in the truststore file associated with the specified truststore alias. At run time, the {0} in the error message is replaced with the name of the truststore alias assigned to the watt.server.ssl.trustStoreAlias parameter.

Action

Make sure the truststore alias assigned to the watt.server.ssl.trustStoreAlias parameter contains the correct truststore details including the correct location of the truststore file.

6.33 Unable to set javax.net.ssl.trustStorePassword: Truststore password could not be retrieved from {0}.
Class E
Explanation

Integration Server could not set the javax.net.ssl.trustStorePassword system property because Integration Server could not retrieve the password for the truststore. Integration Server looks in the truststore file associated with the specified truststore alias. At run time, the {0} in the error message is replaced with the name of the truststore alias assigned to the watt.server.ssl.keyStoreAlias parameter.

Action

Make sure the truststore alias assigned to the watt.server.ssl.trustStoreAlias parameter contains the correct truststore details including the correct password for accessing the truststore file.

6.34 Error setting javax.net.ssl properties: {0}
Class E
Explanation

The javax.net.ssl system properties cannot be set because the keystore and/or truststore is invalid.

Action

Use the exception included in the error message to determine why the javax.net.ssl properties could not be set. Actions to be taken might include the following:- Making sure the keystore or truststore file is valid and contains the correct information. - Making sure that the keystore alias assigned to watt.server.ssl.keyStoreAlias contains the correct details for the keystore. - Making sure that the truststore alias assigned to watt.server.ssl.trustStoreAlias contains the correct details for the truststore.If the keystore file is invalid, create a new keystore, kesystore alias, truststore, and truststore alias. Use the new keystore alias as the value of watt.server.ssl.keyStoreAlias. Use the new truststore alias as the value of watt.server.ssl.trustStoreAlias.If the truststore file is invalid, create a new truststore and truststore alias and use the new alias as the value of watt.server.ssl.trustStoreAlias.

7.1 Access Denied. User "{0}" does not have permissions to invoke service: {1}.
Class E
Explanation

The user does not have permission to invoke an Integration Server resource. Read through the details provided in the server log to find the user name and the name of the service.

Action

To grant permission to the user, either add the user to a group that is listed in the Execute ACL assigned to the service, or add one of this user's groups to the Execute ACL assigned to the service.

7.2 Access Denied. No permissions to invoke service ({0}) on port "{1}".
Class E
Explanation

The Access Mode for the specified port is configured to Deny by Default. With this configuration, the port only allows the services explicitly listed in the Allow List. The identified service is not in the Allow List of the identified port.

Action

If this service should be allowed on this port, add the service to the Allowed Services list of the port.
ISS.0010.8050 Error while connecting to the remote authorization server using the remote server alias "{0}". Error details: {1}
Explanation

Integration Server cannot connect to the specified remote OAuth authorization server.
Action

Edit the remote server alias and ensure that all the parameters are specified correctly. If needed, run a test of the remote server alias.

ISS.0010.9016 The cache manager required for OAuth operations is not available. Verify that the cache manager initialized successfully and then restart Integration Server
Class E
Explanation

During the initialization of Cache Managers an error was encountered.
Action

Examine the Integration Server Error logs and Server logs for details about the error. Use the information in the logs to correct the error and then restart Integration Server.

12.14 Unable to initialize JAAS login context. JAAS configuration file in use: {0}. Error message: {1}. Stack trace: {2}
Class E
Explanation

Integration Server uses IntegrationServer/config/is_jaas.cnf file for its JAAS configuration. If there is any problem loading this file, Integration Server throws this exception.

Action

The entries found in a JAAS configuration file should follow the JAAS syntax. If you made any changes to the IntegrationServer/config/is_jaas.cnf, review your changes and make sure there are no syntax errors in the file.

12.16 Initialization of X509ValidatorModule failed with exception: {0}.
Class E
Explanation

The X509ValidatorModule defined in the IntegrationServer/config/is_jaas.cnf file is incorrect.
Action

Review the Integration Server error log for the actual exception. Refer to the webMethods Integration Server documentation for information about how to use this module and correct any errors found.

12.17 Authentication failed because the X.509 certificate path validation has failed.
Class E
Explanation

The X509ValidatorModule is enabled in the IntegrationServer/config/is_jaas.cnf file. As a result, Integration Server performed certificate path validation using the information provided, but the client certificates failed the certificate path validation.

Action

Make sure that the truststore used by the X509ValidatorModule contains the intermediary certificates as well.
12.20 Authentication failed because the X.509 certificate has been revoked.
Class E
Explanation

The X509ValidatorModule is enabled in the IntegrationServer/config/is_jaas.cnf file. As a result, Integration Server checked the client certificate against the Certificate Revocation List (CRL) and the client certificate was found to be revoked.

Action

Advise the client to resubmit the request using a valid certificate.
12.22 Access Denied. Authentication resolved to user "{0}". User is not defined in any of the available user stores.
Class E
Explanation

Integration Server JAAS authentication modules return the username in the Subject. Integration Server then tries to retrieve the definition of this user either locally in its user store, or in Central Users (if configured), or LDAP (if configured). If Integration Server is not able to find the user anywhere, it rejects the client request with this error.

Action

If this user should be allowed accessing Integration Server resources, make sure this user is defined in any of the user stores accessible to Integration Server.

12.23 SAML assertion verification failed. The current time {0} violates the "Not Before" setting {1} specified in the SAML assertion.
Class E
Explanation

Integration Server received a SAML assertion that arrived before the "Not Before" setting.
Action

Check the clock time of the issuer. If it is significantly different from the clock time on the Integration Server machine, adjust the Clock Skew value on the Security -> SAML screen.

12.24 SAML assertion verification failed. The current time {0} violates the "Not On Or After" setting {1} specified in the SAML assertion.
Class
Explanation

Integration Server received a SAML assertion that arrived later than the "Not On Or After" setting.
Action

Check the clock time of the issuer. If it is significantly different from the clock time on the Integration Server machine, adjust the Clock Skew value on the Security -> SAML screen.

12.25 Rejecting SAML assertion from issuer "{0}" because issuer is not configured on the Security > SAML screen.
Class E
Explanation

Integration Server received a SAML assertion from an issuer that has not been configured on the Security -> SAML screen.
Action

Configure the issuer on the Security -> SAML screen.
12.27 {0}% or more of maximum number of concurrent stateful sessions are in use. {1} sessions are available.
Class W
Explanation

Integration Server is approaching the threshold for concurrent stateful sessions.
Action

No immediate action is required. Once the limit is reached, all new requests to create stateful sessions will be rejected. You can increase the limit using the Resources screen in the Integration Server Administrator; however, doing so could increase the server's resource requirement.

12.30 Rejecting SAML assertion because the subject identified in the SAML assertion is not the one who signed the request.
Class E
Explanation

For security reasons, Integration Server cannot accept requests that are not signed by the subject identified in the SAML assertion.

Action

Sign the message using the subject identified in the SAML assertion.
13.1 Binding XML. Service {0} was unable to bind incoming XML data
Class
13.4 Registering multipart content handler {0} for service {1}.
Class E
Explanation

The syntax for the watt.server.content.type.mappings parameter is invalid.
Action

Use the correct syntax for this parameter. See Administering webMethods Integration Server for more information about using watt.server.content.type.mappings.

14.1 Encountered fatal errors while starting License Manager. Shutting down server.
Class E
Explanation

Integration Server encountered a serious internal error while validating the license.
Action

Contact Software AG Global Support.
14.4 No listening ports were available. Shutting down server.
Class
14.9 Server is unable to determine its own name.
Class
14.12 watt.server.fileEncoding unsupported by JVM. Server may be unable to continue.
Class
14.13 watt.server.netEncoding unsupported by JVM. Text may not process properly.
Class
14.14 watt.server.logEncoding unsupported by JVM. Logging in default encoding.
Class
14.17 Warning: {0} when initializing ACL Manager file {1}
Class
14.21 Failed to invoke notification callback {0}: {1}
Class E
Explanation

Integration Server encountered an error while updating ACLs. Specifically, an error occurred when Integration Server invoked a service that is registered as a notification callback.

Action

Make sure that the service being invoked exists and can be executed.
14.22 Retrying service {0}. Retry count is {1}
Class E
Explanation

Integration Server is retrying a service that was previously unsuccessful.
Action

No action is required.
14.23 Available Thread Pool Threshold No Longer Exceeded: {0}% available
Class E
Explanation

Integration Server is no longer exceeding the specified threshold for thread pool usage.
Action

No action is required.
14.24 Server Initialization Aborted. See log messages.
Class E
Explanation

During start up, Integration Server encountered a serious internal error that caused it to shut down immediately.
Action

Make sure that the machine on which Integration Server runs has sufficient disk space. In addition, make sure the operating system user that is trying to start Integration Server has a sufficient space allowance and has read/write permission to the directory on which Integration Server resides.

14.25 Master password for outbound password encryption has expired. Password was last changed on {0}. The current expiration interval is {1} days
Class
14.26 Master password for outbound password encryption expires in {0} days
Class
14.27 Unable to remove outbound password handle {0}
Class
14.28 Cannot initialize OutboundPasswordManager with null Password Manager
Class
14.29 Master password failed a sanity check
Class S
Explanation

During Integration Server initialization, the sanity check of the master password for outbound passwords failed. Integration Server uses the master password to encrypt outbound passwords, which the Integration Server uses to connect to applications or systems such as remote Integration Servers, proxy servers, or databases. The outbound passwords are stored in files on Integration Server and encrypted for security purposes. During initialization, Integration Server performs a sanity check of the master password by attempting to use it to decrypt a special, internal string that it previously encrypted using the master password. If the decrypted internal string matches the clear text version of the string, Integration Server knows the correct master password was provided. This error is issued when the decrypted and clear text versions of the string do not match.

Action

The sanity check of the master password can fail for a number of reasons:

- The outbound password file is corrupted.

- The master password file is corrupted.

- You mistyped the master password when you were prompted for it.

If you suspect you have mistyped the password, shut down the server and restart it, this time entering the correct password. If this does not correct the problem, refer to the webMethods Integration Server documentation.

14.30 Master password updated
Class S
Explanation

The master password, which Integration Server uses to encrypt outbound passwords, has been successfully updated.
Action

No action is required.
14.35 OutboundPasswordManager configuration directory cannot be null
Class S
Explanation

Integration Server cannot locate the configuration directory it uses for managing outbound passwords.
Action

Contact Software AG Global Support.
14.39 OutboundPasswordManager, {0} caught this: type {1}, msg {2}
Class S
Explanation

The code that Integration Server uses to manage outbound passwords encountered a problem while trying to perform the indicated operation.

Action

If the exception message text does not suggest a solution, contact Software AG Global Support.
14.47 com.wm.app.b2b.server.DataStore must be initialized before it can be used.
Class
14.48 The ISInternal functional alias is not configured properly on the JDBC Pools page. Assign a valid database pool and restart the Integration Server.
Class
14.51 Cannot aquire the lock.
Class
14.54 Error occurred while initializing server: {0}
Class
14.55 Cannot acquire an exclusive lock. Another session is holding a shared lock on the requested item.
Class
14.56 Cannot acquire an exclusive lock on the requested context. Another session has locked it.
Class
14.57 Integration Server is quiesced and is not accepting new requests at this time.
Class
14.58 Integration Server has reached the license limit for concurrent sessions.
Class
USER_DOES_NOT_EXIST User does not exist: {0}
Class
NO_PKGNAME_SPECIFIED No package name specified
Class
NO_LISTENER_SPECIFIED A listener must be provided
Class
NO_LISTENER_FACT_SPECIFIED A listener factory must be provided
Class
LISTENER_FACT_REGED A listener factory with {0} is already registered in the {1} package
Class
REG_FACT_WITH_INVALID_KEY Attempted to register a factory with an invalid identifying key
Class
REG_LISTENER_WITH_INVALID_KEY Attempted to register a listener with an invalid identifying key
Class
LISTENER_REGED_WITH_KEY A listener is already registered with the key {0}. The existing listener must be unregistered first
Class
FAILED_UPDATE_LISTENER_CONFIG Failed to update listener configuration information
Class
COULD_NOT_UPDATE_CONFIG Unregistration failed, could not update the configuration
Class
SVC_UNABLE_BIND_XNLDATA Service {0} unable to bind incoming XML data
Class
NO_VALID_ACTIVE_PKG No Valid Active Packages
Class
PKG_DIR_NOT_EXIST Package directory for {0} does not exist
Class
PKG_NOT_EXIST Package {0} does not exist
Class
UNABLE_LOCATE_COMPILER Unable to locate or start compiler
Class
UNABLE_SAVE_FILE Unable to save file {0} for {1}
Class
CANNOT_GET_SESSION ServerReferenceManager can't get session to access object cache
Class U
Explanation

Integration Server encountered an internal error with the object cache.
Action

Contact Software AG Global Support.
SRV_NO_THREAD Unable to allocate a new thread in the time specified
Class U
Explanation

Integration Server has reached the configured limit for the number of new threads it can create. After waiting unsuccessfully for resources to become available, Integration Server issued this ISRuntime exception. This exception usually indicates a transient condition in which resources are temporarily unavailable. If this error occurs during execution of a trigger, and retry is enabled, Integration Server will automatically retry the service. If, after a configured amount of time, the resources are still unavailable, Integration Server throws this exception.

Action

If the problem persists, use the Resource Settings page of the Server Administrator to specify thread pool settings that are more appropriate for your environment.

THREADPOOLERR1 Can not set thread pool max to zero or less than min, max={0}, min={1}
Class
REPO4_LOCAL_CFG_ERR Repository config file repository4.cnf not found.
Class
PKG_PARTIAL_LOAD_MISSING {0} package not reloaded; missing the following assets: {1}
Class E
Explanation

An internal error occurred while using the local service development feature in Software AG Designer. An attempt to reload an updated IS asset (flow service, Java service, document type, etc. ) failed because the specified IS asset does not exist in the IS namespace. At run time, the {0} in the error message is replaced with the package name and the {1} is replaced with the IS assets that do not exist in the namespace.

Action

Contact Software AG Global Support.
PKG_PARTIAL_LOAD_ALREADY_LOADED {0} package not reloaded. {1} already registered in {2}
Class E
Explanation

While using the local service development feature in Software AG Designer, an attempt to reload an updated IS asset (flow service, Java service, document type, etc. ) failed because Integration Server determined that another package contains an asset with the same name. At run time, the {0} in the error message is replaced with the package name, the {1} is replaced with the IS asset name for which a reload was attempted, and the {2} is replaced with the name of the package that contains the already loaded, identically named asset.

Action

Ensure that each IS asset uses a name that is unique across the Integration Server namespace. To rename one of the assets, you might need to disable the package that contains the asset whose name you do not want to change. Change the name of the IS asset in the package that you want to change. Then, re-enable both packages.

PRIMARY_LISTENER_PKG_WMROOT Primary port change failed. The primary port must be a port associated with the WmRoot package.
Class E
Explanation

An attempt to change the primary port failed because the chosen port is associated with a package other than WmRoot.
Action

Select a port associated with the WmRoot package as the primary port. Alternatively, change the chosen port to associate it with the WmRoot package and then designate the port as the primary port.

PRIMARY_LISTENER_ENABLED Primary port change failed. The primary port must be an enabled port.
Class E
Explanation

An attempt to change the primary port failed because the chosen port is not enabled.
Action

Select an enabled port as the primary port. Alternatively, enable the chosen port and then designate the port as the primary port.

PRIMARY_LISTENER_PROTOCOL Primary port change failed. The primary port must be an HTTP or HTTPS port.
Class E
Explanation

An attempt to change the primary port failed because the chosen port is not an HTTP or HTTPS port.
Action

Select an HTTP or HTTPS port to use as the primary port.
PRIMARY_LISTENER_TYPE Primary port change failed. The primary port must be a standard port.
Class E
Explanation

An attempt to change the primary port failed because the chosen port was not a standard port. Currently, the only non-standard port type is the diagnostic port.

Action

Select a standard HTTP or HTTPS port to use as the primary port. Do not select a diagnostic port to be the primary port.
15.2 Error {0} initializing Invoke Manager class {1} from {2}
Class E
Explanation

Integration Server failed to initialize InvokeManager from the configuration file located at <IntegrationServer_dir>/config/invokemanager.cnf file at startup.

Action

Contact Software AG Global Support.
15.3 Error {0} initializing Invoke Manager with {2}
Class E
Explanation

Integration Server failed to initialize InvokeManager from the configuration file located at <IntegrationServer_dir>/config/invokemanager.cnf file at startup.

Action

Using a text editor, open the <IntegrationServer_dir>/config/invokemanager.cnf file and make sure that the content is not corrupt. If the error still occurs, consider removing the invokemanager.cnf file and restarting Integration Server.

15.4 Service {0} failed ACL access checking for user {1}
Class E
Explanation

The client application failed to invoke the service because the current user did not have the Execute ACL privileges to execute the service.

Action

Using the Integration Server Administrator, examine the ACL settings of the service as well as the ACL group to which the current user belongs. Make sure that the user has the proper ACL settings.

FAC+"."+SERVICE_CACHE_NOT_AVAILABLE Cannot cache {0} service. The cache manager {1} is not initialized.
Class E
Explanation

The cache manager SoftwareAG.IS.Services is not initialized.
Action

Check the configuration of the SoftwareAG.IS.Services cache manager.
17.1 An error was encountered parsing {0}: {1}. See the Integration Server error log for the full stack trace.
Class E
Explanation

Either the format of XML in the configuration file is invalid, or a specific setting is not allowed. 
Action

Read through the details provided in the error message and edit the configuration file to correct the problem.
17.2 Cache manager {0} created.
Class I
17.3 {0} is required.
Class E
Explanation

A value is required for the indicated parameter.
Action

Supply a value for the parameter.
17.4 There is no cache manager named {0}.
Class E
Explanation

There is no cache manager with this name on Integration Server.
Action

Make sure the cache manager name is typed correctly and that it exists on the Integration Server.
17.5 There is no cache named {0} in the {1} cache manager.
Class E
Explanation

Integration Server tried to connect to the indicated cache, but there is no cache with this name associated with the cache manager.

Action

Provide the name of a cache that is managed by the supplied cache manager.
17.6 Cache {0} created.
Class I
17.7 Cache manager names starting with "SoftwareAG" are reserved.
Class E
Explanation

The cache manager could not be created because the name is invalid.
Action

Choose a different name for the cache manager.
17.8 Successfully deleted cache manager {0}.
Class I
17.9 All elements have been removed from cache {1} of cache manager {0}.
Class I
17.10 Disabled cache {1} of cache manager {0}.
Class I
17.11 Enabled cache {1} of cache manager {0}.
Class I
17.12 Cache manager {0} is not started.
Class E
Explanation

The service failed to execute because the specified cache manager is not available.
Action

Open Integration Server Administrator and go to the Settings > Caching page to verify that the cache manager is started and the cache the service wants to use is enabled.

17.13 Cache {1} for cache manager {0} not enabled.
Class E
Explanation

The operation could not be completed because the indicated cache could not be found in the indicated cache manager.
Action

Make sure the cache name is typed correctly and that it is contained in the indicated cache manager.
17.14 Cache manager {0} already exists.
Class E
Explanation

The cache manager could not be created because a cache manager with the indicated name already exists on the Integration Server. The name you specify must be unique on the Integration Server.

Action

Enter a new name for the cache manager that is unique to the Integration Server.
17.15 The {0} cache manager attempted to connect to a Terracotta Server Array, but the Integration Server license does not allow it. This cache manager will not be usable.
Class E
Explanation

To use this feature, Integration Server must have a license that allows distributed caching.
Action

Obtain the appropriate license from Software AG Global Support and add it to the Integration Server.
17.16 If rejoin is enabled, a Terracotta Server Array URL must be supplied.
Class E
Explanation

You selected the Rejoin check box, but did not configure the cache manager to connect to a Terracotta Server Array.
Action

Specify a Terracotta Server Array URL or clear the Rejoin check box.
17.17 Cannot use the administrative services to change a system cache manager: {0}.
Class E
Explanation

The cache could not be created because a cache with that name already exists in the cache manager. The name you specify must be unique within the cache manager.

Action

See Administering webMethods Integration Server for more information about system cache managers.
17.18 The {0} cache already exists.
Class E
Explanation

The cache could not be created because a cache with that name already exists in the cache manager. The name you specify must be unique within the cache manager.

Action

Enter a name for the cache that is unique within the cache manager.
17.19 Cannot delete a system cache manager: {0}.
Class E
Explanation

The cache manager you attempted to delete is a system cache manager and cannot be deleted.
Action

See Administering webMethods Integration Server for more information about system cache managers.
17.20 Cache manager name cannot contain any of these characters: ? [ ] / = + < > : ; " , * | ^ @
Class E
Explanation

The cache manager could not be created because the name you specified contains invalid characters.
Action

Specify a new name using valid characters.
17.21 Cache manager name cannot start with a '.' or end with a space.
Class E
Explanation

The cache manager could not be created because the name you specified contains invalid characters.
Action

Specify a new name using valid characters.
17.22 Cache manager name cannot be an operating system device name.
Class E
Explanation

The cache manager could not be created because the name you specified is a reserved word as specified by your operating system.
Action

Specify a new name for the cache manager. Refer to your operating system's documentation for a list of reserved words.
17.23 An error was encountered updating {0}: {1}. See the Integration Server error log for the full stack trace.
Class E
Explanation

While attempting to enable or disable clustering for the Integration Sever, an error occurred while updating the Terracotta Cache Manager configuration files.

Action

Review the error details provided in the message and in the Integration Server error log. After correcting the issue that caused the error, use Integration Server Administrator to enable or disable clustering for the Integration Server.

17.24 When a cache is distributed, Overflow to Disk, Overflow to Off-heap and Persist to Disk cannot be selected.
Class E
Explanation

The Overflow to Disk, Overflow to Off-heap and Persist to Disk options are not allowed with distributed caches.
Action

If you are creating a distributed cache, remove the values from the Overflow to Disk, Overflow to Off-heap and Persist to Disk fields.

17.26 Cache manager name is null in {0}. The cache manager will not be used
Class E
Explanation

A cache manager configuration file was supplied with a null cache manager name.
Action

Edit the configuration file and provide a name for the cache manager.
17.27 A cache manager named "{0}" has already been loaded from {1}. The name cannot also be used in {2}. The cache manager in {2} will be ignored.
Class E
Explanation

More than one configuration file in the Integration Server_directory\config\Caching directory contains the specified cache manager. Integration Server cannot load two instances of the same cache manager. The cache manager that is already loaded is being used. The cache manager in the second configuration file will be ignored.

Action

Either remove one of the configuration files or change the cache manager name in one of the configuration files.
17.29 Cache manager {0} successfully started.
Class I
17.30 Cache manager {0} successfully reloaded.
Class E
Explanation

A value is required for the indicated parameter.
Action

Supply a value for the parameter.
17.31 Cache manager {0} is already running.
Class I
17.32 Cache manager {0} is not running.
Class I
17.33 Cannot enable a system cache.
Class E
Explanation

The cache you attempted to enable is a system cache. System caches are used by internal processes and cannot be modified.
Action

See Administering webMethods Integration Server for more information about system caches.
17.34 Cannot disable a system cache.
Class E
Explanation

The cache you attempted to disable is a system cache. System caches are used by internal processes and cannot be modified.
Action

See Administering webMethods Integration Server for more information about system caches.
17.35 Cannot clear the contents of a system cache.
Class E
Explanation

The cache you attempted to clear is a system cache. System caches are used by internal processes and cannot be modified.
Action

See Administering webMethods Integration Server for more information about system caches.
17.36 Cannot start a system cache manager.
Class E
Explanation

The cache manager you attempted to start is a system cache manager. System cache managers are used by internal processes and cannot be modified.

Action

See Administering webMethods Integration Server for more information about system cache managers.
17.37 Cannot shutdown a system cache manager.
Class E
Explanation

The cache manager you attempted to shutdown is a system cache manager. System cache managers are used by internal processes and cannot be modified.

Action

See Administering webMethods Integration Server for more information about system cache managers.
17.38 Cannot reload a system cache manager.
Class E
Explanation

The cache manager you attempted to reload is a system cache manager. System cache managers are used by internal processes and cannot be modified.

Action

See Administering webMethods Integration Server for more information about system caches.
17.39 Attempted to create cache manager {0} that connects to a Terracotta Server Array, but the Integration Server license does not allow it. Cannot save cache manager configuration.
Class E
Explanation

To use this feature, Integration Server must have a license that allows distributed caching.
Action

Obtain the appropriate license from Software AG Global Support and add it to Integration Server.
17.40 Successfully evicted expired elements from the cache {0} contained in cache manager {1}.
Class I
17.41 Cleared all caches starting with name {0} contained within the cache manager {1}.
Class I
17.42 Cleared all caches contained within the cache manager {0}.
Class I
17.43 Error occurred while clearing caches starting with name {0} contained within the cache manager {1}. Details:{2}
Class E
Explanation

The service cannot remove the element from the cache for the reason indicated in the message.
Action

Take the appropriate action based on the details shown in the message.
17.44 Error occurred while clearing caches contained within the cache manager {0}. Details:{1}
Class E
Explanation

The service did not clear the caches in the specified cache manager because of the specified error.
Action

Take the appropriate action based on the details shown in the message.
17.45 Added cache {0}.
Class I
17.46 Updated cache {0}.
Class I
17.47 Deleted cache {0}.
Class I
17.48 {0} is not a distributed cache. Integration Server cannot synchronize with the Terracotta Server Array.
Class E
Explanation

You can only synchronize distributed caches with a Terracotta Server Arrays.
Action

Set the Distributed option on all the caches you want to synchronize with the Terracotta Server Array.
17.49 The {0} cache manager is not running. Start the cache manager to synchronize the cache with the Terracotta Server Array.
Class E
Explanation

You cannot synchronize caches against the Terracotta Server Array when the cache manager is not running.
Action

Start the cache manager and then synchronize the cache with the Terracotta Server Array.
17.50 The configuration for the {0} cache has been synchronized with the Terracotta Server Array.
Class I
17.51 Integration Server cannot evict expired elements for caches contained in a system cache manager.
Class I
17.52 Integration Server cannot reload the {0} cache manager because it is not running.
Class I
17.53 The {0} cache in {1} has a different local configuration than the configuration on the Terracotta Server Array. Integration Server is using the configuration from the Terracotta Server Array.
Class E
Explanation

The configuration of the local cache should match that of the associated Terracotta Server Array. If the local cache configuration does not match the configuration of the Terracotta Server Array, Integration Server ignores the local cache configuration and uses the configuration of the Terracotta Server Array.

Action

Configure the local cache to match the configuration of the Terracotta Server Array.
17.54 Use Integration Server Administrator to synchronize mismatched cache configurations with the Terracotta Server Array.
Class I
17.55 Integration Server has registered a cache manager, but the configuration file is not in the config/Caching directory. Integration Server cannot manage this configuration.
Class E
Explanation

Integration Server saved the configuration for a cache manager, but the configuration file is not in the IntegrationServer/config/Caching directory. If the configuration is valid, you can still use the cache manager, but you cannot use Integration Server Administrator to stop or start the cache manager or edit its configuration.

Action

Copy the configuration file to the IntegrationServer/config/Caching directory and restart Integration Server.
17.56 The {0} cache manager is shut down but there is no configuration file associated with it. Integration Server cannot restart this cache manager.
Class E
Explanation

The cache manager configuration file is not in the IntegrationServer/config/Caching directory.
Action

Restore the missing configuration file to the IntegrationServer/config/Caching directory.
17.57 The {0} cache manager is shut down but its corresponding configuration file ({1}) no longer exists. Integration Server cannot restart this cache manager.
Class E
Explanation

The cache manager configuration file is not in the IntegrationServer/config/Caching directory.
Action

Restore the missing configuration file to the IntegrationServer/config/Caching directory.
17.58 Integration Server cannot remove the Terracotta Server Array URLs for this cache manager because one or more of its caches are distributed. Clear the Distributed option on all the caches.
Class E
Explanation

Integration Server cannot remove Terracotta Server Array URLs if any of the caches contained in the cache manager are distributed.
Action

Shut down the cache manager and then change the Terracotta Server Array URLs.
17.59 Integration Server cannot modify the Terracotta Server Array URLs for a cache manager while it is running. Shut down the cache manager, then change the Terracotta Server Array URLs.
Class E
Explanation

Integration Server cannot modify the Terracotta Server Array URLs for a cache manager while it is running.
Action

Shut down the cache manager and then change the Terracotta Server Array URLs.
17.60 Updated cache manager {0}.
Class I
17.61 Added cache manager {0}.
Class I
17.62 Integration Server encountered an error while parsing {0}: {1}.
Class E
Explanation

The cache manager configuration file contains invalid syntax.
Action

Manually edit the cache manager configuration file so that it is syntactically correct.
17.63 The current Terracotta license is not valid for the BigMemory settings configured for the {0} cache manager. To use the cache manager, either remove the BigMemory settings from the configuration file or obtain a valid Terracotta license for BigMemory.
Class I
17.64 Deployment of cache manager {0} failed because of invalid license. Check the Integration Server log for details.
Class E
Explanation

Integration Server could not deploy the cache manager because the license for Integration Server or Terracotta is invalid.
Action

Acquire the correct license file for Terracotta, Integration Server, or both and then redeploy the cache manager.
17.65 Reading cache manager configuration from file {0}.
Class I
17.66 {0} is a system cache manager.
Class I
17.67 Read cache manager {0} from file {1}.
Class I
17.68 Integration Server is running in safe mode. Cache manager {0} not initialized.
Class I
17.69 Initializing cache manager {0}.
Class I
17.70 Cache manager {0} initialized.
Class I
17.72 Shutting down cache manager {0}.
Class I
17.73 Cache manager {0} is shut down.
Class I
17.74 Shutting down cache managers.
Class I
17.75 Finished shutting down cache managers.
Class I
17.76 The value specified in the "Maximum Elements in Memory" field must be an integer no larger than 2147483647.
Class E
Explanation

An invalid value was specified in the Maximum Elements in Memory field.
Action

Change the value to an integer no larger than 2147483647.
17.77 Field cannot be changed while the cache manager is running: {0}
Class E
Explanation

The specified field cannot be modified while the cache manager is running.
Action

Shut down the cache manager, and then update the field. To shut down the cache manager, open Integration Server Administrator and go to the Settings > Caching page, then click the "Shutdown" link for the cache's cache manager.

ISS.0019.7005 Unable to retrieve client_secret for {0} from the secure password store. See the error log for a full stack trace.
Class E
Explanation

Integration Server cannot retrieve the client secret for the specified OpenID Provider.

Action

Re-enter the client_secret value in the OpenID Provider’s configuration file and click the Reload OpenID Providers link on the Security > OpenID page.If none of the passwords work, the password store might be corrupt. Contact Software AG Global Support.

ISS.0019.7007 ID Token''s issuer claim {0} is invalid. It does not match the application''s OpenID Provider issuer ID.
Class E
Explanation

Integration Server expected the iss field in the token to match the issuer value in the OpenID Provider’s configuration file; however, the iss and issuer values do not match.

Action

Check that the issuer value in the OpenID Provider’s configuration file is correct. If it is not, edit the OpenID Provider configuration file to include the correct issuer value. Then, click the Reload OpenID Providers link on the Security > OpenID page.

ISS.0019.7008 ID Token''s audience claim {0} does not match the application''s OpenID Provider client ID.
Class E
Explanation

Integration Server expected the aud field in the token to match the client_id value in the OpenID Provider’s configuration file.

Action

Check that the client_id value in the OpenID Provider’s configuration file is correct. If it is not, edit the OpenID Provider configuration file to include the correct client_id value. Then, click the Reload OpenID Providers link on the Security > OpenID page.

ISS.0019.7009 ID Token''s audience claim has multiple values "{0}" but the required authorized party claim is not present.
Class E
Explanation

The audience for an ID Token must contain the OAuth 2.0 client_id of the Relying Party as an audience value but the required client_id is missing.

Action

No action required.

ISS.0019.7010 ID Token''s authorized party claim {0} does not match the OpenID Provider client ID {1}.
Class E
Explanation

The authorized party claim in the ID Token either does not contain or does not match the OAuth 2.0 client_id for the Authorized Party. The ID token must contain the authorized party claim when the ID Token has a single audience value and the audience is not the Authorized Party.

Action

No action required.

ISS.0019.7011 ID Token has expired. Expiration claim value is {0}, current time is {1}.
Class E
Explanation

The ID Token issued by the OpenID Provider has expired and cannot be used for authentication.
Action

Set the prompt value in the OpenID Provider’s configuration file to “login”, which instructs the OpenID Provider to require the end user to log in using their credentials. Then, click the Reload OpenID Provider link on the Security > OpenID page. Have the user reissue the original request.

ISS.0019.7012 ID Token has expired. Issued at time value is {0}, current time is {1}, provider''s max_age limit is {2}.
Class E
Explanation

The age of the ID Token issued by the OpenID Provider exceeds the max_age value in the OpenID Provider’s configuration file. The token cannot be used for authentication.

Action

Increase the max_age value in the OpenID Provider’s configuration file and click the Reload OpenID Provider link on the Security > OpenID page. Have the user reissue the original request.

ISS.0019.7013 ID Token''s asserted claim value(s) "{0}" do not match any of the provider''s asserted claim values "{1}".
Class E
Explanation

The claim values in the token do not match any of the claim values for the OpenID Provider.
Action

No action required.

ISS.0019.7015 ID Token requires re-authentication, Maximum Authentication Age {0} has expired. Authentication time was {1}, current time is {2}
Class E
Explanation

The user must be re-authenticated because the time elapsed since the token authentication time exceed the Maximum Authentication Age.

Action

Re-authenticate the token. Set the prompt value in the OpenID Provider’s configuration file to “login” and click the Reload OpenID Provider link on the Security > OpenID page. Have the user reissue the request.

ISS.0019.7016 {0} is null.
Class E
Explanation

The OpenID Provider’s token endpoint or userinfo endpoint did not return a token.
Action

Check the error log for an exception related to the request. Set watt.server.oauth.custom.responseHeader to true and the server logging facility “0040 HTTP Response” to TRACE. Recreate the problem and check the server log for a response header of X-OAuth-Error. If no error is reported, contact the OpenID Provider.

20.7020 Timeout occurred during execution of a service {0} configured for circuit breaker.
Class E
Explanation

The service execution time exceeded the configured timeout period for the service.

Action

Identify and correct the cause of the slow service execution. You can generate a thread dump of Integration Server and examine Integration Server logs to assist with identifying the source of the slow behavior. Then correct the component that exhibits the slow behavior.

24.1 Could not initialize User Manager.
Class
24.2 Error occurred while initializing User Manager: Class {0} was not found in CLASSPATH.
Class
24.3 Error occurred while initializing User Manager: {0}
Class
24.4 Could not access User Manager
Class
24.5 Could not read users.cnf (the file may be corrupt)
Class E
Explanation

Integration Server could not read user and group configuration information from the users.cnf file. The file might be corrupt.
Action

Examine this file in the Integration Server /config directory. Ensure that the server has read access to it. If the file is corrupted, you might need to set up the users and/or groups again through the Integration Server Administrator.

24.6 Could not write users.cnf (the file may be corrupt)
Class E
Explanation

Integration Server could not write user and group configuration information to the users.cnf file. The file might be corrupt.
Action

Examine this file in the Integration Server /config directory. Ensure that the server has write access to it. If the file is corrupted, you might need to set up the users and/or groups again through the Integration Server Administrator.

24.7 The JDBCPool {0} associated with Central Users JDBC function is not defined so the Central User Manager is not enabled
Class
24.10 Central User Manager initialization failed with error : {0}
Class
24.11 Not able to load the {0} Role/Group.
Class
24.13 Integration Server cannot add group to ACL because the required parameter "{0}" is not supplied.
Class
24.14 Integration Server cannot add group "{0}" to ACL "{1}" because ACL "{1}" is not defined.
Class
24.15 Integration Server cannot add group "{0}" to ACL "{1}" because group "{0}" is not found.
Class
24.18 Integration Server failed to add group "{0}" to ACL "{1}" because of exception: {2}.
Class
25.9 Integration Server could not initialize the cache manager. Stopping Integration Server initialization. Use the server log and error log to diagnose and correct the problem.
Class E
Explanation

This error occurs when Integration Server is configured to be in a cluster and cannot connect to the Terracotta Server Array (TSA). This could happen because the TSA URL in your cluster configuration is incorrect, the TSA is offline, or because there is a network problem.

Action

(1) Verify that the Terracotta Server Array is available and accepting connections. (2) If it is, start the server in safe mode by including the "-safeboot" argument in the command line. On the Settings > Clustering page of Integration Server Administrator, check that the Terracotta Server Array URL value is correct. (3) Make sure the network configuration of the host is correct and there are no problems with your network.

25.34 Dispatcher could not be shutdown: {0}
Class U
Explanation

Integration Server encountered a serious internal error while shutting down.
Action

Contact Software AG Global Support.
25.35 Dispatcher could not be started: {0}
Class
25.40 FIPS mode initialized
Class I
Explanation

Integration Server is operating under Federal Information Processing Standards.
Action

No action is required.
25.41 FIPS mode not initialized
Class I
Explanation

Integration Server is not operating under Federal Information Processing Standards.
Action

No action is required.
25.42 FIPS mode could not be initialized. Shutting down server: {0}
Class S
Explanation

An error was encountered during initialization of FIPS mode operation.
Action

Contact Software AG Global Support. Be prepared to provide configuration information related to security provider and FIPS mode.

25.43 Integration Server started in Safe Mode
Class S
Explanation

Integration Server is operating in safe mode either because it was started using the safeboot switch or because there were problems with the master password. When running in safe mode, Integration Server is not connected to any external resources, except the server’s own external repository, and you cannot update any passwords. If it is a master password problem, there will be other messages logged that indicate that there was a master password problem.

Action

If you intended to start the Integration Server in safe mode, then no action is required. If the Integration Server automatically started in safe mode due to a master password problem, see the webMethods Integration Server Administrator documentation.

25.46 Monitoring API could not be initialized. JmsUrl = {0}. Value must be supplied for JmsUrl.
Class
25.47 Monitoring API could not be initialized because of following exception. Check JMS Provider. {0}
Class
25.48 Monitoring API could not be initialized. Check JMS Provider.
Class
25.50 The JCE Unlimited Strength Jurisdiction Policy File was not found. Please install it.
Class
25.53 Error encountered while disabling Monitoring API.
Class
25.54 Fabric Agent initialization failed.
Class
25.56 FIPS could not be initialized because the JCE Unlimited Strength Jurisdiction Policy File was not found. Shutting down Integration Server.
Class
25.58 Error reading system level information: {0}
Class
25.59 Error initializing cluster node name: {0}
Class W
Explanation

The specified cluster node name is an empty node name.
Action

Specify a non-empty cluster node name.
25.60 Falling back on the fully qualified domain name as the cluster node name, cluster node name is :{0}
Class W
Explanation

Integration Server is using the default cluster node name for the machine because the cluster node name is empty or not provided.
Action

No action is required.
25.61 The logical name for the cluster node is not correct: {0}
Class E
Explanation

The name for the cluster node is not valid. The logical host name you specify must be unique within the cluster and cannot contain a semicolon (;).

Action

Specify a unique logical name to identify the Integration Server instance in the cluster.
25.62 Web services stack could not be initialized. Shutting down server: {0}
Class C
Explanation

Integration Server encountered an error while initializing the Web services stack. Typical reasons are:

1) Loading of axis2.xml file located in Integration Server_directory/config/wss or Integration Server_directory/config/wssClient/conf folders failed because the file has been modified.

2) Integration Server failed to initialize the policy manager for the Web service.
Action

If you have modified the axis2.xml file located in Integration Server_directory/config/wss or Integration Server_directory/config/wssClient/conf folders, make sure that the changes made are correct. For all other reasons, refer to the details listed in the error message and respond accordingly.

EDA_MANAGER_DOWN The pub.event.eda:send service failed because the EDA Manager failed to initialize due to the following error: {0}.
Class E
Explanation

The pub.event.eda:send service failed because the EDA Manager did not initialize. Integration Server uses the EDA Manager to retrieve information about event types.

Action

Review the error message that indicates why the Event Manager failed to initialize and attempt to resolve the cause of the failure.

25.64 EDA Manager initialized.
Class E
Explanation

The EDA Manager initialized successfully.
Action

No action required.
25.65 Encountered an error while disabling listeners. Proceeding with server shutdown.
Class W
Explanation

An error occurred while shutting down Integration Server. If the logging level for logging facility 0025, Initialization, is set to Debug or higher, the server log will include a stack trace with more details about the error.

Action

No action is required. Integration Server will shut down as requested.
25.66 Encountered an error while suspending triggers. Proceeding with server shutdown.
Class W
Explanation

An error occurred while shutting down Integration Server. If the logging level for logging facility "0025 Initialization" is set to Debug or higher, the server log will include a stack trace with more details about the error.

Action

No action is required. Integration Server will shut down as requested.
25.70 Integration Server detected files in config/work directory which suggests unapplied configuration changes.
Class C
Explanation

When saving changes to configuration files, Integration Server first saves the configuration changes in a temporary file in the IntegrationServer_directory/instances/instanceName/config/work directory. After saving the changes in a temporary file, Integration Server moves the temporary file to the actual configuration file. This ensures that if unexpected behavior occurs before the configuration changes are initially saved to the temporary file, only the temporary file is impacted. The actual configuration file is not corrupted. If Integration Server detects files in in the IntegrationServer_directory/instances/instanceName/config/work, it suggests that changes to a configuration file were not saved to the temporary file and that, therefore, the changes were not made to the actual configuration file.

Action

Use the contents of the IntegrationServer_directory/instances/instanceName/config/work directory to determine which configuration files were in the process of being changed. Decide whether or not you want to redo the changes to the configuration files. Delete the files under the directory and redo the configuration change if you so choose.

26.2 Failure while loading service {0}: {1}
Class E
Explanation

Integration Server failed to install, enable, or reload the package because it could not load a service in the package into its namespace.

Action

Examine the error message to determine the problem service. Usually this error occurs when a Java service was not compiled before loading the package.

26.5 Flow service could not be registered with the server: folder.servicename may already exist.
Class
26.6 Warning missing type name while loading service {0}
Class
26.7 Warning missing type name in operation {0} while loading service {1}
Class
26.8 Error: Exception serializing Flow Service {0}
Class E
Explanation

Integration Server encountered an internal error with a flow service.
Action

Contact Software AG Global Support.
26.9 Error: unknown flow operation type for node:{0} in file:{1}
Class E
Explanation

Integration Server encountered an internal error with a flow service.
Action

Contact Software AG Global Support.
26.10 Warning: {0} Operation with no body in service {1}
Class
26.11 Warning: {0} Operation missing service name in {1}
Class
26.12 Warning: Flow Branch Operation must have switch name or use conditional labels in {0}
Class W
26.13 Warning: Flow Branch Operation cannot have switch name and use conditional labels in {0}
Class
26.14 Warning: {0} Operation missing target path in {1}
Class
26.15 Warning: {0} Operation missing source path name in {1}
Class
26.16 Warning: Flow Map Delete Operation missing field name in {0}
Class
26.17 The HTTP URL alias could not be registered by the service {0}. "{1}" is already registered as an alias for the path: {2}
Class
MISSING_FLOW_XML Missing flow.xml
Class E
Explanation

The flow.xml file does not exist. When a flow service is created, Integration Server creates a flow.xml file and a node.ndf file in the IntegrationServer\packages\packageName\ns\folderName directory that corresponds to the package and folder in which the flow service was created.

Action

Contact Software AG Global Support.
READ_ONLY_FLOW_XML Read only {0}
Class E
Explanation

The flow.xml file cannot be updated because it is read-only.
Action

Navigate to the directory of the flow.xml file and make it a writable file.
UNABLE_TO_WRITE_TO_FLOW_XML Unable to write to flow.xml
Class E
Explanation

An exception occurred while writing to the flow.xml file.
Action

Contact Software AG Global Support.
MISSING_CLASS Missing class {0}
Class E
Explanation

The specified Java class cannot be found. This error is returned by the JVM.
Action

Contact Software AG Global Support.
METHOD_NOT_DEFINED Method {0} is not defined with the proper signature
Class E
Explanation

The signature of the Java service does not have a return type of void.
Action

Contact Software AG Global Support.
NO_SUCH_METHOD No method {0} in class {1}
Class E
Explanation

The service is to be supported by a specific method in a class. However, the loaded class does not contain the specified method.
Action

Make sure the class contains the method that you want to use to support the service.
METHOD_IS_NULL Method {0} is unexpectedly null
Class E
Explanation

Method defined to support the invoked service is null.
Action

Contact Software AG Global Support.
SVC_NAME_MISSING Unable to create service; Service name missing
Class E
Explanation

The service cannnot be created because the service name is missing. Integration Server can only create and register services that have a name.

Action

Make sure to specify a name for the service.
SVC_ALREADY_REGISTERED Already registered in {0}
Class E
Explanation

An identically named element already exists in another package. The fully qualified element name must be unique across Integration Server. Fully qualified element names use the format: folder.subfolder.subfolder:elementName

Action

Provide a different name for the element.
SVC_NAME_ALREADY_USED {0} : Name already used by another service type in {1} package
Class E
Explanation

Integration Server cannot save or register the service because a service with that name already exists in the package.
Action

Specify a different name for the service.
UNABLE_TO_REG_SVC Unable to register service; Package {0} is not enabled
Class E
Explanation

An attempt was made to register a service in a disabled package. A service can be registered in an enabled package only.
Action

Enable the package and then attempt to register the service.
UNKNOWN_SERVICE Unknown service: {0}
Class E
27.1 nCipher Hardware accelerator not available
Class W
Explanation

An error occurred while accessing the nCipher hardware.
Action

Turn the "0027 Server Configuration" logging facility up to TRACE on the Settings > Logging > Server Logger page of the Integration Server Administrator and try again. See the details of the error in the server log.

28.2 Packages directory missing or corrupted
Class
28.3 Unable to copy the original package manifest file: {0}
Class
28.6 Unable to load {0} package (possibly due to circular dependencies)
Class
28.7 This package requires {0} package (Version {1}) to load
Class
28.8 Warning! Loading package from backup manifest file
Class
28.9 Unable to read manifest file for {0} package
Class
28.10 Unknown service type ({0}) in {1} package
Class
28.11 Unable to write package manifest file: {0}
Class
28.13 Startup service exited with the following error: {0}
Class
28.14 Startup service {1} was not found in {0} package
Class
28.16 Shutdown service exited with the following error: {0}
Class
28.17 Shutdown service {1} was not found in {0} package
Class
28.18 Server could not update the node definition file. Changes to the package were not saved.
Class
28.20 Unable to read node definition file
Class
28.21 Server could not update the node subdirectory. Changes to the package were not saved.
Class
28.22 Unable to locate class: {0}
Class
28.23 Could not delete service
Class
28.24 Invalid Package License key for Package: {0}
Class
28.25 Unable to save Package Key for Package: {0}
Class
28.26 Invalid or corrupt namespace plug-in configuration found in {0} package
Class E
Explanation

Integration Server could not read plug-in configuration information from the nsplugins.cnf file associated with the indicated package.

Action

Contact Software AG Global Support.
28.27 Namespace plug-in type name {0} in package {1} conflicts with existing type
Class
28.28 Cannot create namespace factory class {0} in package {1}: {2}
Class
28.29 Namespace factory class invalid type {0} in package {1}
Class
28.30 Error: Will not load deprecated service type ({0}) in service {1} in package {2}
Class
28.35 Package {0} has failed to load.
Class
28.36 Document type {0} has failed to load. Duplicate Broker document type name {1} is also referenced by {2}
Class
28.38 Error loading {0} : Name already used by another item in package {1}
Class
28.39 Failure while loading document type {0}: {1}
Class E
Explanation

Integration Server failed to load the document type into the namespace because another document type with the same name was already being loaded into the Integration Server namespace.

Action

Examine the error message to determine the problem document types. Check both document types to make sure they have different names. If they have the same name and both need to be loaded into the namespace, rename one and try again.

28.40 Failure while loading schema {0}: {1}
Class E
Explanation

Integration Server failed to load the schema into the namespace because another schema with the same name was already being loaded into the Integration Server namespace.

Action

Examine the error message to determine the problem schemas. Check both schemas to make sure they have different names. If both need to be loaded into the namespace, rename one and try again.

28.41 Failure while loading element {0}: {1}
Class E
Explanation

Integration Server failed to load the element into the namespace because another element with the same name was already being loaded into the Integration Server namespace.

Action

Examine the error message to determine the problem elements. Check both elements to make sure they have different names. If both need to be loaded into the namespace, rename one and try again.

28.43 Error unregistering node {0}: {1}
Class
28.44 Invalid classpath entry: {0}
Class W
Explanation

An I/O error occurred when Integration Server tried to access the file system to resolve the canonical name of the directory in which the file exists.

Action

Check the file system for errors, such as problems with permissions and cyclical links.
28.45 Failed to install package {0}. Another package exists with the name {1}
Class E
Explanation

Integration Server was unable to install a package because a package with the same name already exists on the Integration Server.

Action

Rename one of the packages, either the existing package or the one you are trying to install. Note that case does not matter; Integration Server considers "ABC" the same name as "abc".

28.46 Unable to load package replication passwords from {0}
Class E
Explanation

Integration Server encountered an error while loading the indicated class.
Action

Check the audit log for messages about the underlying cause of the exception.
28.47 Unable to save package replication passwords to {0}
Class E
Explanation

Integration Server encountered an error while loading the indicated resource.
Action

Check the Audit log for messages about the underlying cause of the exception.
28.48 Failed to read class {0} from input stream
Class
28.49 Unable to locate resource {0}
Class
28.51 Task Scheduler startup service exited with the following error: {0}
Class E
Explanation

Integration Server encountered an error while executing the scheduler startup service task.
Action

Contact Software AG Global Support.
28.52 Task Scheduler startup service {1} was not found in {0} package
Class E
Explanation

The package startup process could not locate the service named in the message.
Action

Contact Software AG Global Support.
28.55 Caching of package classes is disabled due to the following error for file [{0}]: {1}
Class
28.56 The post-initialization startup service {0} threw an exception: {1}. See the error log for the full stack trace.
Class
28.57 Failure while registering HTTP URL alias "{0}" for the package {1}. Already registered as an alias for the path: {2}
Class
28.58 Failure while registering HTTP URL alias "{0}" for the package {1}. Already registered by package {2} as an alias for the path: {3}
Class
28.59 Failure while registering HTTP URL alias "{0}". Already registered as an alias for the path: {1}
Class
28.60 Failure while registering HTTP URL alias "{0}". Already registered by package {1} as an alias for the path: {2}
Class
28.61 Unable to load system package {0} due to dependency on non-system packages.
Class E
Explanation

Integration Server cannot load the specified system package because it depends on a non-system package. System packages are pre-defined packages that are part of the Integration Server product (for example, WmPublic). A system package can have dependencies on other system package(s) only.

Action

Using Designer, edit the package dependencies for the specified system package to remove the dependency on the non-system package.

REST_RESOURCE_NOT_LOADED Unable to load the REST resource with URL template {0}, HTTP method(s) {1}, and service {2} because the URL template contains either illegal or unsupported characters.
Class Error message
Explanation

The information you have specified for configuring the REST resource contains either illegal or unsupported characters.

Action

Update the REST resource configuration to not include illegal or unsupported characters.
33.1 Inactive server {0} was removed from cluster {1}
Class
33.100 If any multicast setting is supplied (Discovery Address, Discovery Port, Time To Live), they must all be supplied.
Class
33.103 Could not open the session cache. {0}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
33.104 Could not add server to the cluster. {0}
Class E
Explanation

Integration Server failed to add a server to the cluster.
Action

Make sure that the server repository is running and that the connection to other servers is valid.
33.108 Could not remove server from cluster. {0}
Class
33.114 Failed to add server statistics to the cluster cache. {0}.
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
33.124 Local Address
Class E
Explanation

Integration Server failed to remove expired sessions from the Repository. This is an internal error.
Action

Contact Software AG Global Support.
33.128 Unable to save settings to the server's configuration file.
Class
33.143 Please restart the server to make the new settings take effect.
Class
33.144 Changes not saved: {0} is required.
Class
33.146 Evaluating host {0} to receive Session Document.
Class
33.147 Register Session Document handler with host {0}.
Class
33.148 Received unknown special document. Body = <<{0}>>.
Class
33.149 Changes not saved. Invalid value. {0} must be an integer.
Class
33.150 Changes not saved. Invalid Well Known Address. If either host or port is supplied, both must be supplied. host={0}, port={1}.
Class
33.151 Communication with Terracotta Server Array has been lost.
Class U
Explanation

During server startup, Integration Server detected a problem with its configuration that will prevent it from being part of a cluster.

Action

Check the Clustering and Repository settings for your Integration Server. Refer to the webMethods Integration Server documentation for more information about clustering. If you cannot determine the cause of the problem, contact Software AG Global Support.

33.153 Could not obtain a handle to ConnectionManager.
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
33.154 Could not save session {0} to the session cache. {1}.
Class E
Explanation

Integration Server failed to persist the indicated session to the Repository. This is an internal error.
Action

Contact Software AG Global Support.
33.155 Could not create local session {0} from the cached session values. {1}.
Class E
Explanation

An Integration Server in a cluster tried to update a session object, but was unable to find it. This in an internal error.
Action

Contact Software AG Global Support.
33.156 Cluster Invoke did not complete successfully. Cluster Synchronization feature is not configured.
Class E
Explanation

After a trigger configuration update, Integration Server attempted to apply the change to other Integration Servers in the cluster, but was unable to. The most likely reason is that the Cluster Synchronization feature has not been properly configured.

Action

Review the cluster synchronization for rrigger management text in the webMethods Integration Server documentation for instructions on configuring your cluster to propagate trigger changes to other Integration Servers in the cluster.

33.159 The TSA URL must be specified on the Settings > Clustering page in order to join a cluster. Clustering has been disabled. This server is running in stand-alone mode.
Class
33.161 CLUSTERING DISABLED: Could not create or join distributed clustering cache "{0}". This server is NOT a member of a cluster.
Class
33.162 The Cluster Name can contain only the following characters: alphanumerics, dashes, underscores, and colons.
Class
33.163 Cache configuration is invalid. Settings were not saved: {0}
Class
33.164 The ISInternal functional alias on the JDBC Pools page must be configured to use an external database in order to enable clustering.
Class
33.167 The ISInternal functional alias on the JDBC Pools page must be configured to use an external database in order to join a cluster. Clustering has been disabled. This server is running in stand-alone mode.
Class
33.169 Logical cluster node name, {0}, is not valid.
Class
Explanation

A cluster node name is either empty or null. Integration Server detects invalid cluster node names at server initialization or when someone attempts to pin a scheduled task to cluster node with an invalid name.

Action

Provide a non-empty cluster node name for the cluster node.
33.181 Cluster name cannot contain any of these characters: ? [ ] / = + < > : ; " , * | ^ @
Class I
33.182 Cluster name cannot start with a '.' or end with a space.
Class I
33.183 Cluster name cannot be an operating system device name.
Class I
33.184 Cluster name cannot be null or empty.
Class I
33.186 Statsitics polling time set to 60 seconds because clustering is configured.
Class W
Explanation

Integration Server uses a value of 60 for the statistics polling time because the watt.server.stats.pollTime server configuration parameter is set to a value less than or equal to 0 (zero) or greater than 60. When clustering is configured, watt.server.stats.pollTIme must be greater than 0 and less than or equal to 60.

Action

Set watt.server.stats.pollTime to value greater than 0 (zero) but less than or equal to 60.
35.2 Initial log rotation interval could not be set: {0} ms in not valid
Class
35.4 Returned {0} lines while requested for {1} number of lines for error logs.
Class
36.2 Errors occurred invoking URL {0}
Class E
Explanation

A client application using the Java API did one of the following:

1) Tried to invoke the indicated folder or service name, but specified the wrong folder/service name.

2) Specified invalid certificates when setting up the SSL connection to the Integration Server.
Action

Examine the error stack trace to determine which exception was thrown. If it is a MalformedURLException, check the folder/service name provided in the API call and make sure that you specified the fully qualified service name. If it is a CertificateException, an IOException, or an InvalidKeyException, check the certificates provided and make sure that they are valid.

36.4 Error occurred while pinging server: {0}
Class
36.5 Error occurred while disconnecting from server: {0}
Class
36.9 Ping Failed to server: {0} Exception: {1}
Class E
Explanation

A client application performed a periodic ping of a remote Integration Server. The ping resulted in an exception.
Action

Verify that the remote Integration Server is up and running. In addition, verify that there is network connectivity between the two servers.

51.2 Error: {0}
Class E
Explanation

Integration Server failed to add a port, remove a port, or edit an existing port because it could not save ports properties to <IntegrationServer_dir>/config/port.cnf.

Action

Examine the port.cnf file to make sure that it is not corrupt and not Read-Only. If the file is corrupt, you may need to remove the file and restart Integration Server. After you do this, you can re-add ports to the Integration Server.

51.3 Port {0} already registered
Class
51.5 Unable to unregister port {0}
Class
51.8 Listener {0} was denied access to service {1}
Class
53.2 Access denied for user {0} on port {1} from {2}.
Class
53.3 Dispatch caught exception in run loop: {0}
Class
53.5 Dispatch caught exception while trying to send response: {0}
Class
53.6 (tid={0}) Enterprise Gateway Server encountered the error "{1}" while handling a request from client "{2}" at request URL "{3}".
Class S
Explanation

Enterprise Gateway Server experienced an internal error while handling the request.

Action

If the issue persists, contact the system administrator.
53.8 (tid={0}) Attempting to forward the request to the Internal Server again because the original attempt failed with exception "{1}". The retry count is {2} and the request URL is "{3}". Internal Server Host is "{4}" and Port is "{5}"
Class I
Explanation

Enterprise Gateway Server failed to transmit the client request to the Internal Server due to the indicated network exception. The server will automatically try to send the request again. If the retry attempts fail, the server will log a message and fail the client request.

Action

The action you take depends on the exception issued. Look at the exception message for specific information.
53.9 (tid={0}) Enterprise Gateway Server encountered an I/O error while writing the Internal Server''s response back to the client at "{1}". The request URL is "{2}".
Class W
Explanation

An input/output error occurred between Enterprise Gateway Server and the Internal Server.
Action

If the issue persists, contact the system administrator.
53.10 (tid={0}) Enterprise Gateway Server encountered error "{1}" while handling the request. The server is unable to retry the request at this time. The retry count is {2}.
Class E
Explanation

Enterprise Gateway Server experienced an internal error while handling the request.

Action

If the issue persists, contact the system administrator.
53.11 (tid={0}) Enterprise Gateway Server is stopping attempts to retry the request because the content length "{1}" of the retry request does not match the content length "{2}" of the original request. The retry count is {3}.
Class W
Explanation

Enterprise Gateway Server could not complete the request for the reason indicated.
Action

If the issue persists, contact the system administrator.
53.12 Access is denied for user "{0}" on port {1} from client "{2}" through Enterprise Gateway "{3}".
Class S
Explanation

Incorrect credentials were specified while connecting to the Internal Server through the Enterprise Gateway.
Action

Supply valid credentials.
53.13 (tid={0}) API Gateway encountered an I/O error while responding to a request from the client at "{1}". The request URL is "{2}".
Class
Explanation

API Gateway cannot respond to the specified client request because of an I/O error.
Action

Retry the request. If the issue persists, contact your system administrator.
53.14 (tid={0}) API Gateway encountered the error "{1}" while handling a request from the client. The server is unable to retry the request at this time. The retry count is {2}.
Class
Explanation

The server is unable to retry the request after the retry count exceeded the predefined threshold.
Action

Contact your system administrator.
53.16 (tid={0}) API Gateway encountered an error while handling a request from client "{1}" at the request URL "{2}".
Class
Explanation

API Gateway encountered an error while handling the specified client request.
Action

Retry the request. If the issue persists, contact your system administrator.
53.17 Access denied for user "{0}" on port {1} from client "{2}" through API Gateway "{3}".
Class
Explanation

The current user cannot access API Gateway on the specified port because of not having the proper ACLs.
Action

Check the ACLs for the current user. Ensure that the user has the correct ACLs to access API Gateway on the specified port.

54.2 CSRF attack detected. CSRF token is not present in the request URL: {0}
Class E
Explanation

CSRF secure token is missing in the request URL, possibly due to a CSRF attack.
Action

If the request is valid, provide a valid CSRF secure token for the request.
55.1 Critical Java Service error
Class E
Explanation

Integration Server encountered a serious internal error.
Action

Contact Software AG Global Support.
55.2 Service setup {0} uses old-style signature
Class
55.3 Initialization of Java Service {0} failed due to error: {1}
Class
56.1 No SMTP server set. Cannot deliver mail
Class
56.2 No recipient specified. Cannot deliver mail
Class
56.3 Unable to send mail. *{0}*
Class
56.4 Invalid SMTP port specified {0}. SMTP logging turned off
Class
59.1 Interrupted {0}
Class U
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
70.3 Error encountered creating {0} listener on port {1}: {2}
Class W
Explanation

An error was encountered while creating a listener.
Action

See the excpetion message for details about the error. Use the exception message to correct the error.
70.4 Failed to load configuration information
Class E
Explanation

An error occurred while creating a listener from the settings in a package's listeners.cnf file.
Action

Go to the Settings > Logging > Server Log page in the Integration Server Administrator and increase the logging level for the "0070 Listeners" logging facility to TRACE. Reload the package that has the affected port or restart Integration Server. If the problem recurs, capture the exception written to the server log and send it to Software AG Global Support. If you cannot connect to Integration Server because all ports are affected, contact Software AG Global Support and provide them with the listener.cnf file from the WmRoot package.

70.6 Failed to save configuration information
Class E
Explanation

An error occurred while saving listener settings.
Action

Increase the logging level for the "0070 Listeners" logging facility to TRACE and try to save the listener settings again. If the problem recurs, capture the exception written to the server log and send it to Software AG Global Support.

70.8 Failed to bootstrap listener {0}
Class W
Explanation

The listener could not be started from the settings in the listeners.cnf file in a package's config directory. This file may have been manually edited or corrupted.

Action

If you have a backup of the listeners.cnf file, restore it and reload the package or restart Integration Server.
70.13 Failed to start listener {0}. The following error was encountered: {1}
Class W
Explanation

Could not start the listener.
Action

See error details in the message.
70.25 Access to {0} from host {1} was denied.
Class I
Explanation

The host with the specified IP address is unable to invoke services through the specified port. Possible reason for this could be the following:- The host with the specified IP address is in the deny list of the port. - In case of an Enterprise Gateway, the host is in the Enterprise Gateway deny list.

Action

The following lists the actions you can take:- If the host with the specified IP address is in the deny list of the port, delete the host from the Deny List table in the Security > Ports > IP Access > <port> page in the Integration Server Administrator.- If the host with the specified IP address is in the Enterprise Gateway deny list, delete the IP address of the host from the Denied IP Address List table in the Security > Enterprise Gateway Rules > Denial of Service Options page in the Integration Server Administrator.

70.27 An I/O or Socket exception has occurred on {0}
Class E
Explanation

An error occurred while listening on a port.
Action

See the exception message for details about the error.
70.30 Duplicate alias {2} encountered creating {0} listener on port {1}
Class W
Explanation

When loading a package, Integration Server encountered a port alias that is the same as an existing port alias on Integration Server. The alias for a port must be unique across the Integration Server. Integration Server loads and enables the package but will not create the port with the duplicate alias.

Action

If you do not want the port created, you do not need to do anything. However, if you want the port to be created when the package is loaded, delete the existing port with that alias, create a new port that has the same properties as the just deleted port, and then reload the package containing the duplicate alias. Integration Server creates the port when the package is reloaded.

INVALID_GLOBAL_SERVICE Invalid global service {0}
Class E
Explanation

Invalid global service name provided for message processing. An e-mail listener was started. When the Integration Server tried to determine which service to use for message processing for this listener, the Integration Server detected a problem with the name of the service specified as the Global Service. The Global Service overrides the setting for the Default Service or the service specified in the e-mail message from the e-mail client. The problem could be that the service name is specified in the wrong case (service names are case sensitive) or that the specified service does not exist in the Integration Server's namespace.

Action

Examine the Global Service name provided. Make sure the name is in the correct case and that the service exists in the Integration Server's namespace.

INVALID_DEFAULT_SERVICE Invalid default service {0}
Class E
Explanation

An e-mail listener was started. When the Integration Server tried to determine which service to use for message processing for this listener, the Integration Server detected a problem with the name of the service specified as the Default Service. The Integration Server executes the Default Service if no service is specified in the e-mail message and no service is specified for the Global Service in the Email Client Configuration screen on the Integration Server Administrator. The problem could be that the service name is specified in the wrong case (service names are case-sensitive) or that the specified service does not exist in the Integration Server's namespace.

Action

Examine the Default Service name provided. Make sure the name is in the correct case and that the service exists in the Integration Server's namespace.

EMAIL_LOGGED_IN Enable failed: Could not log into account {0}@{1}
Class
HOST_REQUIRED Must provide Server Host
Class
TYPE_REQUIRED Must provide Server Type
Class
USERNAME_REQUIRED Must provide User Name
Class
ERROR_START_LISTEN Error starting to listen: {0}
Class
PORT_NUMBER_REQUIRED A number must be provided for the port
Class
INVALID_PORT An invalid port number was provided
Class E
Explanation

An administrator entered an invalid port number on a port configuration screen in the Integration Server Administrator.
Action

Specify a positive integer from 1 through 65534 for the port number.
PORT_REQUIRED A port number must be provided
Class
PRIVKEY_NOT_SPECIFIED Private key not specified
Class
PRIVKEY_FILE_NOT_EXIST Private key file does not exist
Class
LISTENER_NOT_ENABLED Listener is not enabled
Class
LISTENER_REQUIRED A listener must be provided
Class
BAD_CERTIFICATE Could not process certificate {0}
Class
NO_PEER_CERT_CHAIN Peer certificate chain is not present
Class
PEER_CERT_NOT_MAPPED Peer certificate is not in IS Certificate map
Class
PEER_CERT_CHAIN_NOT_TRUSTED Peer certificate chain is not trusted
Class
INVALID_LISTENERTYPE Invalid/unsupported listener type found, {0}
Class
INVALID_MINTHREAD Invalid value for minimum threads={0}
Class
INVALID_MAXTHREAD Invalid value for maximum threads={0}
Class
INVALID_THREADPRTY Invalid value for thread priority={0}, minimum priority=1 and maximum priority=10
Class
INVALID_MINMAX Invalid min/max threads min={0} is greater than max={1}.
Class
INVALID_PRIORITY Invalid thread priority={0}, minimum priority={1} and maximum priority={2}
Class
INVALID_BACKLOG Invalid port backlog queue value={0}
Class
INVALID_KEEPALIVETO Invalid keep alive timeout value={0}
Class
INVALID_INTERNALPORT Invalid Enterprise Gateway internal port number {0}
Class
INVALID_PROXYPORT Invalid port number {0}
Class
INVALID_MAXCONNS Invalid maximum number of connections value {0}
Class
HOSTNAME_VERIFICATION_FAILED Access denied to host: Hostname verification failed. The CN "{0}" in the subject DN of the certificate does not match the hostname "{1}".
Class
PURPOSE_VERIFICATION_FAILED Aborting connection, Server Certificate purpose verification failed
Class
KEY_ALIAS_EMPTY Key alias is empty. Specify a key alias for the port or a global SSL key alias on the Security > Certificates > Edit page.
Class
Explanation

The port cannot be enabled because a key alias was not specified and there is not a default SSL key alias for the Integration Server.

Action

Before enabling the port, either define a key alias or specify a default SSL key alias for the Integration Server. The default SSL key alias is the keys alias specified during configuration of the SSL authentication credentials for the Integration Server. To use a defined key alias with the HTTPS port, specify that keystore alias in the create or update operation. To use the Integration Server's default SSL key alias with the HTTPS port, do not supply key alias information for the create or update operations.

KEY_STORE_EMPTY Keystore alias is empty. Specify a keystore alias for the port or a global SSL keystore alias on the Security > Certificates > Edit page.
Class
Explanation

The port cannot be enabled because a keystore alias was not specified and there is not a default SSL keystore alias for the Integration Server.

Action

Before enabling the port, either define a keystore alias or specify a default SSL keystore alias for the Integration Server. The default SSL keystore alias is the keystore alias specified during configuration of the SSL authentication credentials for the Integration Server. To use a defined keystore alias with a port, specify that keystore alias when creating or updating the port. To use the Integration Server's default SSL keystore alias with the port, do not supply keystore alias information when creating or updating the port.

INVALID_KEYPAIR Invalid keypair specified. Public and private keypair moduli don't match
Class
INVALID_KEY_TYPE Unsupported key type: {0}. The HTTPS/FTPS listener supports RSA keys only. Specify a key store that contains the appropriate RSA private key.
Class E
Explanation

HTTPS or FTPS listener is configured with a keystore having DSA or EC key types. The HTTPS/ FTPS listener currently supports only RSA keys.

Action

Configure the HTTPS or FTPS listener to use a keystore that contains the RSA key.
INVALID_DENY_HOSTNAME Invalid character/s found in host name, {0}, in IP Access Deny list.
Class E
Explanation

The specified host in the deny list contains one or more invalid characters.

Action

Correct the host name to remove the invalid characters. The host names or IP addresses can include upper and lower case alphabetic characters, digits (0-9), hyphens (-), and periods (.) and cannot include spaces. For IPv6, IP addresses can also include colons (:) and brackets ([])

CIHPERS_FILE_NOTFOUND Integration Server cannot find the file {0} specified for the server configuration parameter {1}.
Class E
Explanation

The specified server configuration parameter uses a file to identify the allowed cipher suites; however, Integration Server cannot find the file.

Action

Make sure the server configuration parameter specifies the correct location of an existing file.
PROTOBUF_COMPILER_ERROR Error invoking the protocol buffer compiler. Error: {0}
Class E
Explanation

An error has occurred while trying to compile a message descriptor for a publishable document type. At run time, the error text from the compiler replaces the {0} placeholder in the message. This error could occur under several circumstances including: when an IS document type is made publishable for the first time, when a publishable document type is edited and then saved, or when the publishable document type is synchronized with the Universal Messaging server.

Action

Use the error message to identify and correct the error. Then, repeat the action that led to the error. For example, if the error occurred when saving changes to a publishable document type, retry saving the publishable document type.

PROTOBUF_CODER_NO_DESCRIPTOR Protocol buffer coder cannot find descriptor in document type: {0}
Class E
Explanation

An error occurred while encoding or decoding an instance of the specified publishable document type. Integration Server cannot find the message descriptor for the publishable document type. Integration Server creates a message descriptor for a publishable document type with an encoding type set to protocol buffers.

Action

Make sure the publishable document type is synchronized with the messaging provider.

INVALID_MULTI_BINDER_OPERATIONS All binders must contain the same operations
Class E
Explanation

The binders in the Web service descriptor do not contain the same operations. In a service first provider Web service descriptor with multiple binders, the binders must contain the same operations.

Action

Modify the binders to contain the same operations.
WARNING_NO_OPERATIONS The web service descriptor does not contain any operations
Class W
Explanation

A provider Web service descriptor cannot be saved if it does not contain any operations.
Action

Add operations to the provider Web service descriptor.
UNABLE_TO_LOOKUP_OPERATION Cannot resolve operation {0} in binding {1}; operation does not have a unique SOAPAction or a unique first element name.
Class E
Explanation

The provider Web service descriptor could not be created because the operation in the specified binding does not have a unique SOAPAction value or the first part element in the operation's input message is not unique. If neither of these values are unique, Integration Server cannot match an incoming web service request with an operation.

Action

Modify the WSDL document so that operations within a binding have unique SOAPAction values or make sure operations with duplicate SOAPAction values have an input message in which the first part element is unique.

WARNING_SERVICE_NAME_CHANGED Web service name will change from: {0} to: {1}
Class W
Explanation

Changing the value of the Pre-8.2 compatibility mode property for a provider Web service descriptor results in a change to the value of the name attribute in the wsdl:service element in the associated WSDL document. Web service descriptors that run in pre-8.2 compatibility mode use the local name of the Web service descriptor as the service name. Web service descriptors that do not run in pre-8.2 compatibility mode use the fully qualified name of the Web service descriptor as the service name.

For example, suppose that a Web service descriptor has the fully qualified name folder.myFolder:myWebService. If the Web service descriptor runs in pre-8.2 compatibility mode, in the WSDL document, the value of the name attribute in the wsdl:service element is "myWebService". If the Web service descriptor does not run in pre-8.2 compatibility mode, in the WSDL document, the value of the name attribute in the wsdl:service element is "folder.myFolder:myWebService".

Action

Existing consumer Web service descriptors and Web service connectors created from an earlier version of the WSDL document are not affected by the service name change and will execute as expected. However, web service clients created on other platforms might be affected. If a web service client is affected by the name change, regenerate the client using the updated WSDL document.

INVALID_PART_USING_TYPE_WARNING The fault has a message part "{0}" defined by the type "{1}". Message parts in a fault must be defined by the element attribute instead of the type attribute.
Class W
Explanation

The WSDL for the Web service descriptor contains a fault message part defined by the type attribute. To be deployed to the Web services stack in version 8.2 or later of Integration Server, the fault message part must be defined using the element attribute.

Action

To enable the WSDL for the Web service descriptor to be deployed to the Web services stack, modify the fault message part in the source WSDL used to create the Web service descriptor.

WARNING_SECURITY_HANDLER_IN_82_WSD WS Security Handler has no effect when the Pre-8.2 compatibility mode property is false. To enforce WS Security attach WS Policies.
Class W
Explanation

When a Web service descriptor is not running in pre-8.2 compatibility mode (i.e., the Pre-8.2 compatibility mode property is set to false), Integration Server does not execute the WS Security Handler. As a result, the WS Security Handler has no effect and WS Security will not be enforced.

Action

If you want to enforce WS Security, create the appropriate WS Policies and attach the WS Policies to the Web service descriptor.
WARNING_POLICIES_IN_PRE82_WSD WS Policies has no effect when the Pre-8.2 compatibility mode property is true.
Class W
Explanation

When a Web service descriptor is running in pre-8.2 compatibility mode (i.e., the Pre-8.2 compatibility mode property is set to true), Integration Server does not enforce WS Policies attached to the Web service descriptor.

Action

If you want to enforce WS Policies (including those with WS-Security assertions), set the Pre-8.2 compatibility mode property to false. As an alternative, if you want to keep the Pre-8.2 compatibility mode property is set to true and still enforce WS Security policies, you can use the Integration Server WS Security facility. In this case, remove all WS Policies that you have attached to the Web service descriptor and attach the WS Security Handler. For more information about the WS Security Handler, see the Designer online help.

INVALID_JMSBINDER_USAGE JMS Binders are not supported when Pre-8.2 compatibility mode is true.
Class E
Explanation

One of the following situations occurred: the Pre-8.2 compatibility mode property was changed from false to true for a Web service descriptor that contains a binder with a Transport property set to JMS, a binder that specifies the JMS transport was added to a Web service descriptor that runs in compatibility mode (the Pre-8.2 compatibility mode property is set to true), or the Transport property for an existing binder was changed to JMS for a Web service descriptor that runs in compatibility mode. A Web service descriptor for which the Pre-8.2 compatibility mode property is set to true does not support binders with a JMS transport.

Action

If you want to keep the JMS binder, change the Pre 8.2 compatibility mode property from true to false. If you want to keep the Web Service descriptor in Pre 8.2 compatibility mode, delete any binders using the JMS transport or change the binder Transport property to a supported transport (HTTP or HTTPS). Then, save the modified Web service descriptor.

INVALID_CREDENTIALS Invalid credentials
Class E
Explanation

Integration Server validates any credentials (username/password or certificates) that are supplied by the client, and if those credentials fail to match any user known to Integration Server, Integration Server will return this exception back to the client.

Action

Supply the correct credentials.
INVALID_CSRF_TOKEN_REDIRECT Warning: CSRF secure token is not present in the request. If you still want to complete this request, click Continue.
Class W
Explanation

CSRF token is missing in the request URL, possibly due to a CSRF attack.
Action

If the request is valid, click Continue to complete the request.
INVALID_CSRF_TOKEN_ERROR CSRF secure token is not present in the request.
Class E
Explanation

CSRF token is missing in the request URL, possibly due to a CSRF attack.
Action

If the request is valid, provide a valid CSRF token for the request.
ACCESS_DENY Access Denied
Class E
INVALID_WSDL_OPERATION Service first provider Web service descriptors cannot be refreshed.
Class E
Explanation

An attempt was made to refresh a service first provider Web service descriptor. Only WSDL first provider Web service descriptors and consumer Web service descriptors can be refreshed.

Action

None.
WS_NO_NSNODE Cannot refresh Web service descriptor. The Web service descriptor cannot be found in the Integration Server namespace.
Class E
Explanation

A Web service descriptor cannot be refreshed because it does not exist in the Integration Server namespace.
Action

None.
ROLLBACK_UNSUCCESSFUL Cannot roll back Web service descriptor to previously saved version.
Class E
Explanation

An attempt to refresh a Web service descriptor failed. However, Integration Server could not roll back to the most recently saved version of the Web service descriptor and its associated assets. This can happen if Integration Server becomes unresponsive when rolling back the Web service descriptor.

Action

Delete the Web service descriptor and recreate it using the updated WSDL document. Note that any changes made to the Web service descriptor, such as new headers or faults, will be lost. Alternatively, if the Web service descriptor was checked into a version control system, check out the last checked in version of the Web service descriptor and then refresh the Web service descriptor

REFRESHEDWSDSAVE_UNSUCCESSFUL Cannot Save the refreshed Web service descriptor.Integration Server will rollback to the most recently saved versions of the Web service descriptor and its associated assets.
Class E
Explanation

The WSDL file used to refresh the Web service descriptor contains or references an invalid schema.
Action

Use the information in the server log to determine why the schema is invalid. Correct the WSDL file or the associated XML Schema definition. Then, refresh the Web service descriptor.

MERGEOPR_UNSUCCESSFUL Cannot refresh Web service descriptor. One or more operations cannot be merged. Integration Server will roll back to the most recently saved versions of the Web service descriptor and its associated assets.
Class E
Explanation

As part of refreshing a Web service descriptor, Integration Server merges in changes made to existing services used as operations. One of the following can prevent Integration Server from merging the changes in successfully: - The contents or properties of an existing service could not be merged into the refreshed version of the service. - The ACL information could not be set for the refreshed service. - An existing service could not be locked. Integration Server will roll back to the most recently saved versions of the Web service descriptor and its associated assets.

Action

Contact Software AG Global Support. Obtain a copy of the server log before contacting support.
INVALID_HEADER_DOCTYPE The {0} docTypes folder contained one or more user-defined document types used for headers. These document types were deleted when the Web service descriptor was refreshed.
Class W
Explanation

The specified docTypes folder contains a document type used for a header in the Web service descriptor. This document type will be deleted upon refresh. When refreshing a Web service descriptor, Integration Server deletes the WSDName_docTypes folder and all elements contained in that folder and its subfolders. Integration Server will not recreate any assets manually added to the folder or its subfolders.

Action

Do not add any assets to any of the folders created automatically by Integration Server for a Web service descriptor including the WSDName_doctypes folder. If you added any assets to the folders, move the assets to another folder before refreshing the Web service descriptor.

INVALID_FAULT_DOCTYPE The {0} docTypes folder contained one or more user-defined document types used for faults. These document types were deleted when the Web service descriptor was refreshed.
Class W
Explanation

The specified docTypes folder contained a document type used for a fault in the Web service descriptor. This document type will be deleted upon refresh. When refreshing a Web service descriptor, Integration Server deletes the WSDName_docTypes folder and all elements contained in that folder and its subfolders. Integration Server will not recreate any assets manually added to the folder or its subfolders.

Action

Do not add any assets to any of the folders created automatically by Integration Server for a Web service descriptor including the WSDName_doctypes folder. If you added any assets to the folders, move the assets to another folder before refreshing the Web service descriptor.

WS_NO_HANDLER No registered handler found for Header QName:{0}
Class
Explanation

The WSDL you are using to create the Web service connector has a header defined, but a matching header handler is not registered in Integration Server.

Action

Add a header handler with a QNAME matching the Document Universal Name to Integration Server, then create the Web service connector. If you do not have the appropriate header handler, you can continue the process and Developer will create the Web service connector without the header information.

WS_USUPPORTED_BINDING_EXTENSION Unknown ExtensibleElement ''{0}'' found in SOAPBinding ''{1}''
Class
Explanation

The WSDL used to create the Web service descriptor contains a binding element with a child other than SOAP 1.1 or SOAP 1.2. Integration Server does not support extensions to SOAP, such as sdk:binding (Microsoft SOAP-Toolkit extensions). Integration Server will process the valid portions of the SOAP 1.1 or SOAP 1.2 binding, but will skip processing of the unsupported extension.

Action

Verify that the WSDL contains a valid SOAP 1.1 or SOAP 1.2 binding, and is usable without the extension.
DUPLICATE_OPERATION_NAME Binding {0} contains duplicate operation names {1}
Class E
Explanation

Web service descriptor cannot be generated. A binding in the WSDL document contains more than one operation with the same name.

Action

Modify the WSDL document so that operation names are unique within a binding.
DEPLOYER_EXPORT_ERR Error occurred during export of the package {0}. Details : {1}
Class E
Explanation

Integration Server could not export the package because an error occurred during export.
Action

Read through the details provided in the error message and take corrective steps.
DEPLOYER_EXPORT_INVALID_PARAM Invalid parameters passed. Make sure each required parameter is passed as an input to the service.
Class E
Explanation

Integration Server cannot export the assets because the required input parameters are not specified.
Action

Specify all the required parameters.
ARCHIVE_NAME_INVALID Archive name passed ''{0}'' is invalid
Class E
Explanation

The name of the archive contains illegal characters.
Action

Remove all illegal characters from the archive name.
WS_INVALID_BINDING_NO_PORT_FOUND Invalid service found; service {0} does not define any ports
Class E
Explanation

The WSDL document contains a wsdl:service element that does not define any ports. A Web service descriptor cannot be created.
Action

Modify the WSDL document to include ports in the wsdl:service element.
WS_INVALID_BINDING_NO_BINDING_FOUND Invalid port found; port {0} does not specify a binding
Class E
Explanation

The WSDL document contains a wsdl:port element that does not specify a binding. A Web service descriptor cannot be created.
Action

Modify the WSDL document to include a binding for the port.
WS_INVALID_BINDING_OPERATION_MISSING Invalid SOAP binding found; binding {0} does not contain all operations for corresponding portType {1}
Class E
Explanation

The specified binding does not contain all of the operations declared in the specified portType.
Action

Modify the WSDL document so that the binding contains all of the operations declared in the specified portType.
WS_WARNING_SET_JMS_PORT_ALIAS Port alias for JMS Binder ''{0}'' set to ''{1}''. Ensure that this is the correct port alias.
Class W
Explanation

When creating a WSDL first provider Web service descriptor, Integration Server uses the first JMS provider web service endpoint alias listed on the Settings > Web Service Endpoints page in Integration Server Administrator as the port alias.

Action

If you want to use a different JMS provider web service endpoint alias as the port alias, select the JMS binder and assign a different port alias.

WS_NO_JMS_ALIAS_DEFINED Unable to create JMS Binder for binding {0}. There is not a defined JMS provider web service endpoint alias.
Class E
Explanation

When creating a WSDL first provider Web service descriptor, Integration Server uses the first JMS provider web service endpoint alias listed on the Settings > Web Service Endpoints page in Integration Server Administrator as the port alias. If there is no defined JMS provider web service endpoint alias, Integration Server does not create the Web service descriptor.

Action

Create a JMS provider web service endpoint alias. Then create the WSDL first provider Web service descriptor.
DEPLOYER_DEPLOY_INVALID_PARAM Invalid parameter passed. {0} is a required parameter.
Class E
Explanation

Integration Server cannot export the assets because the required input parameters are not specified.
Action

Specify all of the required parameters.
DEPLOYER_EXPORT_RUNTIME_ERR Error occurred while exporting runtime configurations: {0}. For more information, see the Integration Server logs.
Class E
Explanation

Deployer encountered an error while exporting runtime configurations: {0}.
Action

Check Integration Server log for more information.
WS_UNKNOWN_TRANSPORT Unknown transport found in binding {0}. {1} is not a valid transport value.
Class E,W
Explanation

The WSDL document used as the source for the Web service descriptor contains a binding with an invalid transport attribute. Integration Server will not create a WSDL first provider Web service descriptor when a binding transport is invalid. Integration Server will create a consumer Web service descriptor when a binding transport is invalid if the WSDL document contains other valid bindings.

Action

No action is required.
WS_NO_TRANSPORT_URI No transport found in binding {0}. Valid transport value is required.
Class E,W
Explanation

The WSDL document used as the source for the Web service descriptor contains a binding that does not specify a transport. Integration Server will not create a WSDL first provider Web service descriptor when a binding transport is missing. Integration Server will create a consumer Web service descriptor when a binding transport is missing if the WSDL document contains other valid bindings.

Action

If possible, determine the actual transport type and then edit the WSDL document to specify that transport for the specified binding.

WS_JMS_INCOMPATIBLE Unable to create JMS Binder for binding {0}. JMS Binders can be created using Designer only.
Class E,W
Explanation

The source WSDL document for the Web service descriptor contains a SOAP JMS binding. Developer cannot be used to create a WSDL first provider Web service descriptor from a WSDL document with a SOAP JMS binding. Developer can be used create a consumer Web service descriptor from a WSDL document with a SOAP JMS binding if the WSDL document contains other valid SOAP HTTP bindings, but the resulting consumer Web service descriptor will not have a JMS binder.

Action

Use Designer to create the Web service descriptor.
DEPLOYER_DEPLOY_ERROR Error occurred while deploying the asset: {0}. For more information, see the Integration Server logs.
Class E
Explanation

Integration Server encountered an error while deploying the asset. Typical reasons for this error are: 1) Stream is already read. 2) An I/O error occurred. 3) Value for aclData input parameter is not provided. 4) Any other error that occurred during deployment.

Action

Read through the details provided in the error message and take corrective steps.
DEPLOYER_PKG_JVM_VERSION_ERROR JVM "{0}" of the target Integration Server for installing package "{2}" is older than the recommended JVM "{1}".
Class W
Explanation

The target Integration Server is running a JVM version that is older than the version recommended by the source package.
Action

Ensure that the target Integration Server is running the same or a later version of the JVM specified during release creation.
DEPLOYER_NO_TARGET_PACKAGE_VERSION The version of target package cannot be null for a patch release.
Class E
Explanation

The source package being installed is a patch release, but when the patch release was created, no version was specified for the target package.

Action

Specify a version for the target package when creating the patch release.
DEPLOYER_PKG_RECOMMENDED_TARGET_IS_VERSION_INCOMPATIBLE_WITH_TARGET The target Integration Server version "{2}" and the Integration Server version "{1}" recommended by source package "{0}" are incompatible.
Class W
Explanation

The target Integration Server version does not match the Integration Server version recommended by the source package.
Action

Ensure that the version of the target and source Integration Servers are the same.
DEPLOYER_TARGET_PACKAGE_VERSION_ERROR Package "{2}" will not be deployed because the source package is a patch release and target package version: "{0}" does not match the required target package version: "{1}".
Class W
Explanation

During installation of a patch release, Integration Server detected that the version of the target package is not the version required by the patch release.

Action

Install the correct version of the target package before applying the patch.
DEPLOYER_NO_TARGET_PACKAGE_ERROR Package "{0}" will not be deployed because the source package is a patch release and the target package does not exist.
Class W
Explanation

Integration Server could not install the package because the source package being installed is a patch release and the required package does not exist on the target server.

Action

The following lists the actions you can take: 1) Install the package in the target server before applying the patch. -OR- 2) Redefine the source package to a full release before deploying the package on the target server.

DEPLOYER_PKG_VERSION_INSUFFICIENT Package "{2}" will not be deployed because the version of source package: "{0}" is older than the version of target package: "{1}".
Class W
Explanation

The package installed in the target server is of a later version than the source package being installed.
Action

Ensure that the version of the package on the target server is earlier than or the same as the package being installed.
REMOTE_INVOKE_ON_LOCALHOST_NOT_ALLOWED Recursive invoke of wm.server.util:remoteInvoke service on a local server is not allowed.
Class E
Explanation

You cannot invoke the wm.server.util:remoteInvoke service using the wm.server.util:remoteInvoke service recursively on a local server. Recursive invoke of wm.server.util:remoteInvoke service on a local server results in reduced thread availability and after sometime, Integration Server stops responding.

Action

Make sure that you are not invoking the wm.server.util:remoteInvoke service recursively on a local server.
NS_INTERNAL_ERROR_NODE_NOT_EXIST Internal Error - Asset {0} does not exist
Class E
Explanation

While using the local service development feature in Software AG Designer, an attempt to move, copy, or rename an IS asset, such as a flow service, java service, document type, or trigger, resulted in an internal error occurred. At run time, the {0} in the message is replaced with the name of the IS asset being moved, copied, or renamed.

Action

Contact Software AG Global Support.
HANDLER_INVALID_FOLDER_NAME Invalid folder name {0}. Error : {1}
Class E
Explanation

The specified folder name is invalid.
Action

Specify a valid folder name.
HANDLER_FOLDER_NON_EMPTY Folder {0} is not empty
Class E
Explanation

The specified folder must be empty.
Action

Delete the contents of the specified folder or specify an empty folder.
WS_MISSING_ADDRESSING_ENDPOINT Message addressing endpoint alias "{0}" of type "{1}" does not exist.
Class E
Explanation

The specified message addressing endpoint alias does not exist.
Action

Ensure that the message addressing endpoint alias name that you specified is correct and that this endpoint alias exists.
CAN_NOT_DELETE_WS_ADDRESSING_ENDPOINT_REFERRED Can not delete the WS-Addressing endpoint "{0}", as it is referred from the following provider endpoint aliases {1}
Class E
Explanation

A Web service endpoint alias for provider Web service descriptor is using the message addressing endpoint alias you specified as a part of the Response Map.

Action

Before deleting a message addressing endpoint alias, ensure that the endpoint alias is not associated with the Response Map of any provider Web service endpoint alias.

RM_SEQUENCE_NOT_FOUND Reliable messaging sequence {0} not found.
Class E
Explanation

No reliable messaging sequence for the specified internal Sequence Id was not found.
Action

Ensure that a valid Internal Sequence Id is specified.
PROXY_INVALID_ASC_HOST Host Name must be only ASCII characters.
Class E
Explanation

Host Name contains non-ASCII characters. Host Name must consist of only ASCII characters.
Action

Specify a valid host name consisting of only ASCII characters.
PROXY_INVALID_ASC_USER User Name must be only ASCII characters.
Class E
Explanation

User Name contains non-ASCII characters. Host Name must consist of only ASCII characters.
Action

Specify a valid User Name consisting of only ASCII characters.
PROXY_INVALID_PORT Port Number must be positive integer between 0 and 65535 (inclusive).
Class E
Explanation

Port must be a positive integer.
Action

Specify a valid integer between 0 and 65535 (inclusive) for Port.
PROXY_INVALID_ASC_PASS Password must be only ASCII characters.
Class E
Explanation

Password contains non-ASCII characters. Password must consist of only ASCII characters.
Action

Specify a valid password consisting of only ASCII characters.
PROXY_ALIAS_NOTEXISTS Proxy server alias {0} does not exist.
Class E
Explanation

Proxy server alias does not exist.
Action

Specify a valid configured proxy server alias.
PROXY_INVALID_PROTOCOL Protocol must be either HTTP or HTTPS or FTP or SOCKS.
Class E
Explanation

The specified protocol is not valid. Protocol must be HTTP, HTTPS, FTP or SOCKS.
Action

Specify one of the following as the protocol: HTTP, HTTPS, FTP, or SOCKS.
PROXY_INVALID_FTP_TYPE Invalid FTP proxy type.
Class E
Explanation

Invalid FTP proxy type. The FTP proxy type must be an integer within the range of 0 and 7 (inclusive).
Action

Specify an interger within the range of 0 to 7 (inclusive).
PROXY_ALIAS_ILLEGAL_CHARS Proxy server alias contains illegal characters.
Class E
Explanation

The Proxy server alias name is invalid because it contains invalid characters such as #&@^!%*:$./\\~;,~+=)(|}.{/\><.

Action

Specify a proxy server alias name that does not contain the following characters: #&@^!%*:$./\\~;,~+=)(|}.
STRING_MISSING_STRING Missing required value: string
Class E
Explanation

The string parameter is required but is either missing from the pipeline or is null.

Action

Make sure the string parameter is being supplied to the service and that the value of string is not null.
FILE_ACCESS_DENIED Specified path [{0}] is not on the [{1}] allowed list in the fileAccessControl configuration file
Class E
Explanation

The specified path is not in the list of allowed directories and/or files for the specified parameter in the fileAccessControl.cnf file. For the pub.file services, Integration Server provides additional validation checks by ensuring that the paths supplied to the pub.file services are listed in the relevant parameter (allowedReadPath, allowedWritePath, or allowedDeletePath) in the fileAccessControl.cnf file. At run time, the {0} is replaced by the supplied path and the {1} is replaced with the parameter that is being checked in the fileAccessControl.cnf file.

Action

If the supplied path is listed for the specified parameter in the fileAccessControl.cnf, make sure that the supplied path does not contain any errors such as misspellings, misplaced punctuation, and so forth. Keep in mind that path names are case-sensitive on a UNIX-based system. Additionally, note that if the path includes a semicolon, the two backslashes that must precede the semicolon for a parameter in the fileAccessControl.cnf file do not need to be included in the path supplied to the input parameter of a pub.file service. If the specified path should be in the allowed list for the specified parameter but is not, edit the parameter in the fileAccessControl.cnf file to include the path.

RESPONSE_HDRFLD_NOT_ALLOWED Applications cannot set the "{0}" field in the HTTP response header.
Class E
Explanation

The input to the pub.flow:setResponseHeader service specifies a header field that cannot be set by an application.
Action

Change the input to the pub.flow:setResponseHeader service so that it does not specify a header field that cannot be set by an application.

RESPONSE_ONE_OF_TWO_REQD Either "{0}" or "{1}" must be supplied
Class E
Explanation

A value is required for one of the two indicated parameters.
Action

Supply the missing value.
RESPONSE_HDRFLD_NOT_JAVA_IDENTIFIER Invalid JMS property name "{0}"; property name must contain only Java identifier part characters.
Class E
Explanation

The property name specified as input to pub.flow:setResponseHeaders does not meet the syntax requirement for JMS properties as described in the Java Message Service standard.

Action

Modify the property name to meet the syntax requirements for JMS properties. Refer to the Java Message Service standard for information about syntax requirements for message properties.

RESPONSE_HDRFLD_RESERVED_WORD Invalid JMS property name "{0}"; reserved word.
Class E
Explanation

The property name specified as input to pub.flow:setResponseHeaders contains a reserved word as described in the Java Message Service standard.

Action

Modify the property name by removing the reserved word. Refer to the Java Message Service standard for information about reserved words for message properties.

RESPONSE_HDRFLD_NOT_ALLOWED_4JMS Applications cannot set the "{0}" field in the JMS response header.
Class E
Explanation

The input to the pub.flow:setResponseHeader service specifies a message header field that cannot be set by an application.
Action

Change the input to the pub.flow:setResponseHeader service so that it does not specify a header field that cannot be set by an application.

HANDLER_INVALID_GENERATE_FLAGS At least one of the parameters, "generateHeaderDocumentTypes", "generateBodyDocumentTypes" or "generateFaultDocumentTypes", must be set to true.
Class E
Explanation

The "generateHeaderDocumentTypes", "generateBodyDocumentTypes", and "generateFaultDocumentTypes" parameters are all set to false while executing the pub.soap.handler:generateDocumentTypesFromWSDL service.

Action

Set the value of any one of these parameters to true.
COMPAT_UTIL_ALL_AND_SPECIFIC If convertAllPackages is set to true, packageNames cannot be specified.
Class E
Explanation

When convertAllPackages is set to true, the pub.ws.utils:setCompatibilityModeFalse service sets the Pre-8.2 compatibility mode property to false for each Web service descriptor in an enabled package. It is invalid to specify individual packages in packageNames as well.

Action

Either remove the specified value for packageNames or set convertAllPackages to false.
COMPAT_UTIL_ALL_FALSE_NO_SPECIFIC If convertAllPackages is set to false, packageNames must be specified.
Class E
Explanation

When convertAllPackages is set to false, the packageNames parameter must specify the names of the packages that contain the Web service descriptors for which to change the Pre-8.2 compatibility mode value.

Action

Either specify packages in packageNames or set convertAllPackages to true.
COMPAT_UTIL_PACKAGE_DISABLED Package {0} not enabled.
Class E
Explanation

The specified package is not enabled. The pub.ws.utils:setCompatibilityModeFalse service can change Web service descriptors in enabled packages only.

Action

Enable the package.
COMPAT_UTIL_PACKAGE_NOT_FOUND Package {0} not found.
Class E
Explanation

The packageNames parameter specifies a package that does not exist.
Action

Ensure that the package name is spelled correctly. Additionally, verify that package exists on the Integration Server.
COMPAT_UTIL_LOCK_ERROR Unable to lock Web service descriptor for editing.
Class E
Explanation

The Pre-8.2 compatibility mode property cannot be changed because an error occurred while attempting to lock the Web service descriptor for editing.

Action

Determine what error prevents locking of the Web service descriptor by examining the lock properties of the Web service descriptor or by attempting to lock (or check out) the Web service descriptor. Either action should provide a detailed error message that you can use to resolve the error. Then either run the pub.utils.ws:setCompatibilityModeFalse service again or lock (check out) the Web service descriptor and change the value of the Pre-8.2 compatibility mode property manually.

COMPAT_UTIL_LOCK_OTHER Web service descriptor is locked by another user.
Class E
Explanation

The Pre-8.2 compatibility mode property cannot be changed because another user has the Web service descriptor checked out or locked for editing.

Action

Review the lock properties of the Web service descriptor to determine which user has it checked out or locked for editing. After the user unlocks (or checks in) the Web service descriptor, either run the pub.utils.ws:setCompatibilityModeFalse service again or lock (check out) the Web service descriptor and change the value of the Pre-8.2 compatibility mode property manually.

CACHE_CANNOT_RELEASE_LOCK Could not release a lock of type {0} for key {1} in cache {2} contained within the cache manager {3}. Error:{4}
Class E
Explanation

The specified lock type for the specified key, cache, and cache manager does not match the actual lock type held. This error also occurs if a release lock is called from a thread that did not lock the key.

Action

Specify the correct lock type or invoke the service from the same thread that acquired the lock.
SFTP_COMMAND_EXEC_FAIL Error while executing command {0}: {1}
Class E
Explanation

Integration Server encountered an error while executing the command. Typical reasons are: 1) The session is invalid. 2) The command parameter is invalid. 3) The SFTP server is not reachable.

Action

Read through the details provided in the error message and take corrective steps.
SFTP_INVALID_SESSION Invalid session {0}
Class E
Explanation

The session key that you specified is invalid.
Action

Ensure that session key is correct and that the session corresponding to this session key exists.
SFTP_SESSION_EXPIRED Session {0} expired.
Class E
Explanation

The session key that you specified has expired.
Action

Adjust the session timeout value for this SFTP user alias according to your requirements. Once a session expires, you must create a new session.

SFTP_SESSION_IN_USE Session {0} is in use. Integration Server does not support parallel command execution on a session.
Class E
Explanation

You attempted to execute commands in parallel.
Action

Integration Server does not support parallel command execution on a session. Ensure that you execute the commands sequentially.
SFTP_ALL_PARAM_MISSING One or more required values are missing: {0}.
Class E
Explanation

You have not provided all the mandatory input parameters that Integration Server requires to execute the SFTP put command.
Action

Ensure that you provide all the input parameters to execute the SFTP put command. For example, to execute the put command, you have the option to provide a combination of contentStream and remote file name. Integration Server throws this error if you do not provide both the input parameters in this combination.

SFTP_INVALID_MODE Invalid mode: {0}.
Class E
Explanation

The mode that you specified to execute an SFTP command is invalid.
Action

Ensure that you specify a valid value for mode. Valid values are "OVERWRITE","RESUME", and "APPEND".
UM_MIGRATE_PACKAGE_DOCTYPE The packageNames and documentTypeNames input parameters are mutually exclusive.
Class E
Explanation

Values cannot be specified for both the packageNames and documentTypeNames input parameters.
Action

Specify either packageNames or documentTypeNames or neither. If you specify neither, Integration Server searches through all the pub.utils:messaging:migrateDocTypesTriggersToUM attempts to migrate all publishable document types contained in packages that do not start with the letters “wm” in any case combination.

UM_MIGRATE_PACKAGE_ARCHIVE_ERROR Error creating package archive:{0}.
Class E
Explanation

Integration Server could not create an archive for a package. At run time, the {0} is replaced by the error message that caused package archiving to fail.

Action

Use the error message to correct the cause of the error, then , execute the pub.utils.messaging:migrateDocTypesTriggersToUM service. Note that when using the service to migrate the contents of multiple packages, it might be hard to determine for which package Integration Server could not create an archive. If the server log facility 0153 Dispatcher (Universal Messaging) is set to the Debug level, when the pub.utils.messaging:migrateDocTypesTriggersToUM service executes, the server log will indicate which package Integration Server attempted to archive when the error occurred.

UM_MIGRATE_UTIL_LOCK_ERROR Unable to lock for editing. Lock status:{0}.
Class E
Explanation

The publishable document type could not be locked and therefore cannot be updated.

Action

Use the lock status to determine why the publishable document type is locked. Once the publishable document type is unlocked, execute the pub.utils.messaging:migrateDocTypesTriggersToUM service.

UM_MIGRATE_UTIL_LOCK_OTHER Locked by another user:{0}.
Class E
Explanation

The publishable document type could not be locked because it is already locked by the specified user. For the publishable document type to be updated, it must be unlocked or locked by the user executing the pub.utils:messaging:migrateDocTypesTriggresToUM service.

Action

Ask the user who has the publishable document type locked to unlock it. Once the publishable document type is unlocked, execute the pub.utils.messaging:migrateDocTypesTriggersToUM service.

UM_MIGRATE_CONNECTION_ALIAS_NOT_FOUND Could not find newConnectionAlias {0}.
Class E
Explanation

Integration Server cannot find the Universal Messaging connection alias specified for the newConnectionAlias parameter. It is possible the alias does not exist or there is an error in the supplied alias name.

Action

Specify an Universal Messaging connection alias that exists on Integration Server as the value for newConnectionAlias. Make sure you spell the alias name properly. Universal Messaging connection alias names are case sensitive. Then, re-execute the pub.utils.messaging.migrateDocTypesTriggersToUM service.

UM_MIGRATE_DOCTYPE_NOT_FOUND Cannot find document type:{0}.
Class E
Explanation

Integration Server cannot locate the document type.
Action

Make sure the document type exists on Integration Server. Then, re-execute the pub.utils.messaging.migrateDocTypesTriggersToUM service.

UM_MIGRATE_NODE_NOT_DOCTYPE The specified element is not a document type.
Class E
Explanation

An element specified for the documentTypeNames parameter is not a document type. Valid values for the documentTypeNames parameter are names of publishable document types that exist on Integration Server.

Action

Make sure the documentTypeNames parameter specifies only publishable document types that exist on Integration Server. Then, re-execute the pub.utils.messaging.migrateDocTypesTriggersToUM service.

UM_MIGRATE_NODE_NOT_PUBLISHABLE_DOCTYPE The specified element is not a publishable document type.
Class E
Explanation

An element specified for the documentTypeNames parameter is not a publishable document type. Valid values for the documentTypeNames parameter are names of publishable document types that exist on Integration Server.

Action

Make sure the documentTypeNames parameter specifies only publishable document types that exist on Integration Server. Then, re-execute the pub.utils.messaging.migrateDocTypesTriggersToUM service.

UM_MIGRATE_PACKAGE_NOT_FOUND Package not found
Class E
Explanation

The contents of the package could not be migrated because Integration Server cannot find the package. The packageNames input parameter specifies a package that does not exist on Integration Server.

Action

Make sure the packageNames parameter specifies only packages that exist on Integration Server. Then re-execute the pub.utils.messaging:migrateDocTypesTriggersToUM service.

UM_MIGRATE_PACKAGE_DISABLED Package disabled
Class E
Explanation

The contents of the package could not be migrated because the package is disabled. Only the contents of enabled packages can be migrated.

Action

Enable the package and re-execute the pub.utils.messaging:migrateDocTypesTriggersToUM service.

UM_MIGRATE_NO_PKG_OR_SYSTEM_PKG Document type does not belong to a package or belongs to a system package.
Class W
Explanation

The pub.utils.messaging.migrateDocTypesTriggersToUM service skipped migration for a publishable document type because the publishable document type did not belong to a package or belongs to a system package. A system package begins with the letters “wm” in an case combination. The service modifies publishable document types or webMethods messaging triggers in a system package only when the system package is specified in the packageNames input parameter or the publishable document type was specified in the documentTypeNames input parameter.

Action

To migrate the skipped publishable document type, re-execute the pub.utils.messaging.migrateDocTypesTriggersToUM service and specify the publishable document type name in the documentTypeNames input parameter. Alternatively, to migrate multiple publishable document types in a system package, re-execute the pub.utils.messaging.migrateDocTypesTriggersToUM service and specify the system package in the packageNames input parameter.

UM_MIGRATE_NO_CHANGE Document type not changed.
Class I
Explanation

Integration Server skipped migration for the document type because the pub.utils.messaging.migrateDocTypesTriggersToUM service did not make any changes to the publishable document type.

Action

No action required.
UM_MIGRATE_PACKAGE_NO_PDTS_FOUND Package does not contain publishable document types.
Class I
Explanation

Migration failed for the package because it does not contain any publishable document types that can be migrated.

Action

No action required.
BATCH_SERVICE_NAME_MISSING The "serviceName" input parameter is required.
Class E
Explanation

There is no service name specified for the serviceName input parameter.
Action

Specify a service name for the serviceName input parameter.
BATCH_SERVICE_RESULTSETKEY_MISSING The "resultSetKey" input parameter is optional.
Class E
Explanation

The pipeline key name specified for the resultSetKey input parameter does not exist in the pipeline.
Action

Specify the correct pipeline key name for the servicePipeline input parameter.
BATCH_SERVICE_RESULTSET_MISSING The pipeline key name "{0}" does not exist in the wrapped service pipeline.
Class E
Explanation

The specified pipeline key name does not exist in the wrapped service.
Action

Verify the resultset key value returned by the wrapped service.
BATCH_SERVICE_INTERNAL_ARG_MISSING The $internal service input parameter is required.
Class E
Explanation

The calling service must create the $internal service input parameter before calling iterator.
Action

Create the required $internal input parameter for the iterator service and rerun.
BATCH_SERVICE_TIMETOLIVE_ERROR The timeToLive input parameter must be greater than 0.
Class E
Explanation

The timeToLive input parameter must have a value of greater than 0.
Action

Specify a value that is greater than 0 for the timeToLive input parameter.
BATCH_SERVICE_BATCHSIZE_ERROR The batchSize input parameter must be greater than 0.
Class E
Explanation

The batchSize input parameter requires a value greater than 0.
Action

Set the batchSize input parameter to a value greater than 0 and rerun the service.
BATCH_SERVICE_REQUEST_EXPIRED The service request has expired.
Class E
Explanation

The value specified in the timeToLive input parameter has expired and the result set has been removed from the cache.
Action

Increase the value for timeToLive and rerun the service.
UM_MIGRATE_CONNECTION_NOT_UM Document type is not assigned to a UM connection alias.
Class W
Explanation

Integration Server skipped the document type during migration because a value was not specified for newConnectionAlias or a newConnectionAlias specified a Broker connection alias and the document type is either associated with a Broker connection alias or is publishable locally.

Action

Specify a value for newConnectionAlias and re-execute the pub.utils.messaging:migrateDocTypesTriggersToUM service. Alternatively, use Designer to assign the document type a Universal Messaging connection alias and then re-execute the pub.utils.messaging:migrateDocTypesTriggersToUM service.

UM_MIGRATE_CONNECTION_ALIAS_NOT_UM newConnectionAlias:{0} must be an existing UM connection alias.
Class E
Explanation

The newConnectionAlias input parameter specifies an alias that does not exist or specifies a Broker connection alias. The pub.utils.messaging.migrateDocTypesTriggersToUM service can be used to migrate publishable document types to a UM connection alias only

Action

Specify the name of a Universal Messaging connection alias that exists on Integration Server and then re-execute the pub.utils.messaging:migrateDocTypesTriggersToUM service.

UM_MIGRATE_NO_FILTERS Trigger does not contain any filters.
Class I
Explanation

Integration Server skipped the trigger during migration because the trigger does not contain any filters.

Action

No action required.

UM_MIGRATE_CONTAINS_PROVIDER_FILTER Trigger already specifies a value for Provider Filter (UM).
Class W
Explanation

Migration of the filters in the trigger failed because one or more of the trigger conditions already contains a value for Provider Filter (UM). A trigger filter cannot be migrated if a value already exists in Provider Filter (UM).

Action

Manually create the needed Provider Filter. For information about creating trigger filters for use with Universal Messaging, see the documentation.

UM_MIGRATE_NO_BROKER_TRANSORT_FACTORY Error retrieving Broker Transport Factory.
Class E
Explanation

Integration Server cannot connect to the Broker. Specifically, the Broker Transport Factory cannot be located. Either the connection to the Broker is unavailable or the connection to the Broker is not configured correctly. A Broker connection is required for the pub.utils.messaging:migrateDocTypesTriggersToUM service to execute successfully.

Action

Make sure the Broker connection alias is properly configured, the Broker is installed and properly configured, and that the Broker is available.

UM_MIGRATE_NO_BROKER_TRANSORT Error retrieving Broker Transport.
Class E
Explanation

Integration Server cannot connect to the Broker. Either the connection to the Broker is unavailable or the connection to the Broker is not configured correctly. A Broker connection is required for the pub.utils.messaging:migrateDocTypesTriggersToUM service to execute successfully.

Action

Make sure the Broker connection alias is properly configured, the Broker is installed and properly configured, and that the Broker is available

UM_MIGRATE_NO_BROKER_ADMIN_CLIENT Error retrieving Broker Admin Client.
Class E
Explanation

Integration Server cannot connect to the Broker. Either the connection to the Broker is unavailable or the connection to the Broker is not configured correctly. A Broker connection is required for the pub.utils.messaging:migrateDocTypesTriggersToUM service to execute successfully.

Action

Make sure the Broker connection alias is properly configured, the Broker is installed and properly configured, and that the Broker is available.

UM_MIGRATE_CONVERTED Converted Filter:{0} to Provider Filter (UM):{1}.
Class I
Explanation

Integration Server converted the expression in Filter to the expression in Provider Filter (UM).
Action

No action required.

UM_MIGRATE_PARTIAL_WARNING Partial filter conversion - Dropped:{0}.
Class W
Explanation

The complete filter in the Filter field could not be migrated to the Provider Filter (UM) field. Integration Server migrated some expressions in the filter successfully, but could not migrate one or more expressions in the original filter. The pub.utils.messaging:migrateDocTypesTriggersToUM service returns this message for each expression that could not be migrated. At run time, the portion of the expression that could not be migrated replaces the {0} in the message. The contents of the Filter field will not change. That is, Integration Server does not remove the filter expressions that it migrated to Provider Filter (UM) field from the Filter field.

Action

No action is required. However, you might want to edit the contents of the Filter field by removing the expressions that were migrated to Provider Filter (UM). This will eliminate duplicate filter processing.

XMLDATA_NODE_NOT_DOM The node specified as input for the node parameter does not exists or is not a DOM node
Class E
Explanation

The node specified as input to the node parameter for the pub.xmldata:domNodeToXMLData service does not exist or is not a DOM node.

Action

Make sure the node specified as input for the node parameter for the pub.xmldata:domNodeToXMLData service exists and is a DOM node.

XMLDATA_RECORD_NOT_XMLDATA The document type specified for the conformsTo input parameter does not exist or is not an XML document type.
Class E
Explanation

The document type specified for the conformsTo input parameter for the pub.xmldata:domNodeToXMLData service either does not exist or is not an XML document type.

Action

Make sure that the document types specified as input to the conformsTo parameter exists and is an XML document type..

XMLDATA_INPUT_NOT_XMLDATA The document specified as input for the xmlDataDocument parameter does not exist or is not of type XMLData.
Class E
Explanation

Either the specified document as input for the xmlDataDocument parameter does not exist or it is not of type XMLData. The pub.xmldata.xmlDataToXMLString service requires that the input document be of type XMLData.

Action

Make sure the document specified as input for xmlDataDocument exists and is of type XMLData. Use the Document data type property for the specified document to determine if it is of type XML Data.

CLIENT_HTTP_KERBEROS_SVCPRINCIPAL_REQ The servicePrincipal input parameter is required if a jaasContext is specified.
Class E
Explanation

If the pub.client:http service specifies a value for the auth/kerberos/jaasContext input parameter, the auth/keberos/servicePrincipal input parameter must be specified as well.

Action

Specify a value for the auth/Kerberos/servicePrincipal input parameter.
CLIENT_HTTP_KERBEROS_PRINCIPALPASSWORD_REQ A value is not supplied for the Kerberos clientPassword input parameter. The Keberos clientPassword must be specified if the Kerberos clientPrincipal is supplied.
Class E
Explanation

The pub.client:http service specifies a value for the auth/kerberos/clientPrincipal input parameter but does not specify a value for the auth/kerberos/clientPassword input parameter. If clientPrincipal is specified, then clientPasswoard must be specified.

Action

Specfiy a value for the auth/kerberos/clientPassword field.

UTIL_INPUT_NOT_INPUT_STREAM Input to {0} must be an inputstream.
Class E
Explanation

The input must be an input stream.

Action

Specify an inputstream.

UTIL_INPUT_NOT_BYTE_OR_STREAM Input must be a byte array or an inputstream.
Class E
Explanation

The input must be a byte array or an input stream.

Action

Specify a byte array or input stream.
PKCS7_INPUT_NOT_BYTE Input to {0} must be a (byte[]).
Class E
Explanation

If the user does not provide a byte[] type
Action

User should provide a byte[].
PKCS7_ERROR_READ_SIGNATURE Error while processing the signature stream:
Class E
Explanation

User encounters problem while reading the stream
Action

To inform the user that there is a problem in processing the stream.
HANDLER_ALREADY_REGISTERED SOAP Handler {0} already registered
Class E
Explanation

While executing pub.soap.processor:registerProcessor, Integration Server could not register the custom SOAP message processor because the registry already has a SOAP message processor registered for the supplied directive.

Action

When registering a custom SOAP message processor using pub.soap.processor:registerProcessor, specify a directive for which there is not already a custom SOAP message processor. Alternatively, use pub.soap.processor:unregisterProcessor to unregister the custom SOAP message processor that is currently registered to the specified directive and then register the new SOAP message processor with that directive.

HTTP_GET SOAP is only supported using HTTP POST protocol
Class
Explanation

The SOAP message handler was not able to accept the request because the SOAP message was submitted to Integration Server using the HTTP GET method. The SOAP message handler only accepts requests via the POST method (per W3C specification).

Action

Modify the client to use HTTP POST to submit SOAP messages to Integration Server.
ILLEGAL_BOOLEAN Invalid BOOLEAN value {0} for variable {1}; must be 0 or 1
Class E
Explanation

The addHeaderEntry service failed because the mustUnderstand attribute was not set correctly.
Action

Check the logic in the process that failed to make sure that it sets the value of the specified variable to either 0 or 1. No other values are permitted when setting the mustUnderstand attribute.

ILLEGAL_SOAP_HANDLER Cannot load or execute the SOAP processor {0}
Class E
Explanation

The SOAP message handler cannot process the SOAP message because the requested SOAP processor is non-operational.
Action

On the server, check the status of the service that is registered to directiveName. Make sure this service is loaded and operating successfully. (Frequently this error occurs because the processor was modified and then did not recompile successfully.)

INTERNAL_SERVER_ERROR An Exception was thrown in the server:{0}
Class E
Explanation

Integration Server, the SOAP processor, or one of the services processing the message has thrown an exception.
Action

See the detail element in the SOAP fault to determine the exception that was thrown and which process it was thrown by.
MISSING_BODY_BLOCK The SOAP Envelope does not have a Body block
Class E
Explanation

The SOAP client was given a soapRequestData that did not contain a body element.
Action

Examine the logic in the client to see whether it uses the stringToSoapData or streamToSoapData service to generate their SOAP objects. If so, determine whether the String or stream from which the SOAP object was generated represented a valid SOAP message. Also check whether the SOAP processor or client used any of the data removal utilities (such as removeHeaderEntry or removeBodyEntry) and might have inadvertently removed the entire Body element.

MISSING_PARAMETER The server cannot execute the requested SOAP utility; required parameter {0} is missing or invalid
Class E
Explanation

The requested SOAP utility service failed to execute because a required parameter was not supplied.
Action

Check the logic in the SOAP processor or client to make sure that it passes the correct parameters to each SOAP utility service that it invokes.

MUST_UNDERSTAND One or more header entries were not understood by the SOAP processor
Class E
Explanation

The SOAP processor has rejected the SOAP message because it cannot obey a mandatory header entry (a header entry whose mustUnderstand attribute is enabled).

NOT_A_SOAP_MESSAGE Parameter {0} must be a valid soapData
Class E
Explanation

The requested SOAP utility service failed to execute because the value supplied to the specified parameter s not a SOAP object.
Action

Examine the logic in the SOAP processor or client and make sure that it passes a SOAP object to the specified parameter.
NO_RESPONSE SOAP Processor did NOT return a valid SOAP Response
Class E
Explanation

The message handler did not receive a valid SOAP message from the SOAP processor.
Action

Examine the logic in the SOAP processor to make sure that it composes the SOAP response message correctly. For example, check to see whether it the processor uses the stringToSoapData or streamToSoapData services to generate soapResponseData. If so, determine whether the original String or stream represents a valid SOAP message. If the SOAP processor logic seems correct, contact Software AG Global Support. This would indicate a serious internal error.

PARAMETER_TYPE Parameter {0} is not one of the valid data types: {1}
Class E
Explanation

The requested SOAP utility failed to execute because the specified parameter did not have the correct data type. The exception message identifes the data type that is expected.

Action

Examine the logic in the SOAP processor or client and make sure that it passes an object of the specified data type to the specified parameter.

UNKNOWN_SERVICE Service {0} does not exist
Class E
Explanation

The SOAP facility could not complete the requested operation because it could not find the specified service. This error is issued by various SOAP processes (e.g., registering a SOAP processor, invoking a SOAP processor, invoking a target service).

Action

Examine the process that failed and make sure that it specifies the name of the requested service correctly. For example, if you receive this error when registering a SOAP processor, check that you have specified the svcName parameter correctly. Remember that service names are case-sensitive.

UNKNOWN_SOAP_HANDLER Requested SOAP processor {0} is not registered on this server
Class E
Explanation

The Integration Server could not process the SOAP message because it does not have the SOAP processor requested by the client.
Action

On the client side, verify that the correct process directive is specified in the URL (remember that the directive is case-sensitive). If the client has specified the process directive correctly, then use pub.soap.processor:list to verify that the requested processor is registered on the Integration Server.

VALIDATE_FAILED SOAP Message does not conform to the SOAP message model
Class E
Explanation

The SOAP message passed to the validateSoapData utility failed validation (for example, it is missing the Body element or the Header element follows the body).

Action

Examine the logic that produced the message and see whether it uses the stringToSoapData or streamToSoapData service to manually generate a SOAP object instead of using the message composition services (e.g., createSoapData, addHeaderEntry, addBodyEntry). If so, determine whether the String or stream from which the SOAP object is generated represents a valid SOAP message. Also check whether the SOAP processor or client used any of the data removal utilities (such as removeHeaderEntry or removeBodyEntry) and might have inadvertently removed required portions of the SOAP object (for example, the entire Body element).

VALIDATE_REQUEST_FAILED SOAP request does not conform to the SOAP message model
Class E
Explanation

The SOAP message handler could not process the SOAP request because it violates the SOAP message schema (for example, it is missing the Body element or the Header element follows the body).

Action

On the client side, correct the logic that builds the message to ensure that it produces a valid SOAP message.
VALIDATE_RESPONSE_FAILED SOAP response does not conform to the SOAP message model
Class E
Explanation

The SOAP message handler could not return the SOAP response generated by a SOAP processor on the Integration Server because the message violates the SOAP message schema.

Action

Examine the logic in the SOAP processor and see whether it uses the stringToSoapData or streamToSoapData service to generate a SOAP object. If so, determine whether the String or stream from which the SOAP object is generated represents a valid SOAP message. Examine the logic that produced the message and see whether it uses the stringToSoapData or streamToSoapData service to manually generate a SOAP object instead of using the message composition services (e.g., createSoapData, addHeaderEntry, addBodyEntry). If so, determine whether the String or stream from which the SOAP object is generated represents a valid SOAP message. Also check whether the SOAP processor or client used any of the data removal utilities (such as removeHeaderEntry or removeBodyEntry) and might have inadvertently removed required portions of the SOAP object (for example, the entire Body element).

VALIDATOR_MISSING The server could not load the SOAP XML Validator
Class E
Explanation

The SOAP message handler encountered a serious internal error.
Action

Contact Software AG Global Support.
VERSION_MISMATCH Request is from namespace {0}, server requires namespace {1}
Class E
Explanation

The SOAP message handler could not process the message because the message is not from a version of SOAP that the Integration Server supports. Integration Server supports the version indicated in the exception message.

Action

From the client side, resubmit the message using a version of SOAP that Integration Server supports.
INVALID_DIRECTIVE Failed to register SOAP Handler {0}, illegal characters in directive name.
Class E
Explanation

Integration Server was not able to successfully register the SOAP processor, because directiveName contains characters that are not allowed in a directive name.

Action

Register the SOAP processor under a name that is composed only of letters, digits, or the characters -_.!~*'( ).
ENCODE Error while encoding RPC output
Class E
Explanation

While encoding RPC output, an exception occurred which resulted in an Integration Server error.
Action

Use the underlying exception to help determine what caused the error.
CLIENT_EXCEPTION Exception occurred while processing the body of the message
Class E
Explanation

Integration Server, the SOAP processor, or one of the services processing the SOAP message has thrown an exception.
Action

See the detail element in the SOAP fault to determine the exception that was thrown and by which process it was thrown.
WMDOCUMENT_EXCEPTION A WMDocument Exception was thrown in the server, usually because an XML block was not well-formed
Class E
Explanation

The SOAP message handler, the soapHTTP service, or the soapRPC service has received a SOAP message that contains invalid XML.
Action

Check the process that submitted the SOAP message to the Integration Server and make sure that it is producing valid XML. This error usually occurs because of a basic error in the XML document, such as missing tags or overlapping elements.

INVALID_IDATA Invalid input parameter; {0} must be a Document (IData)
Class E
Explanation

The requested SOAP service failed to execute because the object passed into the specified parameter is not an IData object.
Action

Check the logic in the SOAP processor or client to make sure that it passes an IData into the specified parameter.
SIGNATURE_MISMATCH Input parameters do not conform to targetInputSignature: {0}
Class E
Explanation

The pub.client:soapRPC service could not submit the remote procedure call because the input parameters did not pass the data-validation process.

Action

This error is thrown when a client supplies an invalid set of input parameters for a SOAP remote procedure call. Specifically, it indicates that the parameters submitted to pub.client:soapRPC in reqParms do not match the structure and constraints of the document type specified in targetInputSignature. Generally, you will want to code your client to detect this kind of error and take some type of corrective action when it occurs.

OUTPUT_SIGNATURE_MISMATCH Output parameters do not conform to targetOutputSignature: {0}
Class E
Explanation

The SOAP RPC client could not submit the remote procedure call because the output parameters returned by the remote server did not pass the data-validation process.

Action

This error is thrown when a client receives an invalid set of output parameters (results) from a SOAP remote procedure call. Specifically, it indicates that the parameters returned to pub.client:soapRPC in respParms do not match the structure and constraints of the document type specified in targetOutputSignature. Generally, you will want to code your client to detect this kind of error and take some type of corrective action when it occurs.

NOT_A_SIGNATURE Invalid target signature {0}, must be a Document Type
Class E
Explanation

The SOAP RPC client could not process the remote procedure call because it was not able to validate the input or output parameters associated with the request. The signature it was given for validation is not a document type.

Action

Examine the logic in the SOAP RPC client and make sure that the object it specifies in targetInputSignature and/or targetOutputSignature is a document type. That is, these parameters, if used, specify the fully qualified name of a document type that exists on Integration Server.

SIGNATURE_NOT_FOUND Invalid target signature {0}, Document Type does not exist
Class E
Explanation

The SOAP RPC client could not process the remote procedure call because it was not able to validate the input or output parameters associated with the request. The specified document type does not exist on the Integration Server.

Action

Examine the logic in the SOAP RPC client and make sure that targetOutputSignature and/or targetOutputSignature are correctly specified. (Remember that the names of document types are case sensitive.). Also verify that the specified document type exists on the server and the package in which it resides is loaded and enabled.

HEADER_EXISTS this SOAPEnvelope object already contains a valid SOAPHeader object
Class
Explanation

An attempt was made to add a SOAPHeader object to the SOAPEnvelope of a SOAPMessage that already contains a SOAPHeader object.
Action

The SOAPEnvelope object may contain a maximum of one SOAP Header.
NO_HEADER_EXISTS this SOAPEnvelope object does not contain a valid SOAPHeader object
Class E
Explanation

An attempt was made to access the SOAPHeader object, but the SOAPEnvelope of the SOAPMessage does not contain a SOAPHeader object.

Action

Add a SOAPHeader object to the SOAPEnvelope before accessing it.
NO_BODY_EXISTS this SOAPEnvelope object does not contain a valid SOAPBody object
Class E
Explanation

An attempt was made to access the SOAPBody object, but the SOAPEnvelope of the SOAPMessage does not contain a SOAPBody object.
Action

Add a SOAPBody object to the SOAPEnvelope before accessing it.
HEADER_EXCEPTION Exception occurred while retrieving SOAPHeader object
Class E
Explanation

The specified exception occurred while attempting to access the SOAPHeader object.
Action

Correct the error and retry.
BODY_EXCEPTION Exception occurred while retrieving SOAPBody object
Class E
Explanation

The specified exception occurred while attempting to access the SOAPBody object.
Action

Correct the error and retry.
HEADER_ENTRY_EXCEPTION Exception occurred while retrieving SOAPHeaderElement objects
Class E
Explanation

The specified exception occurred while attempting to access the SOAPHeaderElement object.
Action

Correct the error and retry.
BODY_ENTRY_EXCEPTION Exception occurred while retrieving SOAPBodyElement objects
Class E
Explanation

The specified exception occurred while attempting to access the SOAPBodyElement object.
Action

Correct the error and retry.
UNKNOWN_PROPERTY The property {0} is unknown
Class E
Explanation

An attempt was made to either get or set a property of the specified SOAPMessage, but the property name is unknown. The only valid SOAPMessage property names are javax.xml.soap.WRITE_XML_DECLARATION and javax.xml.soap.CHARACTER_SET_ENCODING.

Action

Specify the name of a valid property.
DETAIL_EXISTS this SOAPMessage object already contains a valid Detail object
Class E
Explanation

An attempt was made to add a Detail object to the SOAPBody of this SOAPMessage, but the SOAPBody already contains a Detail object. The SOAPBody can contain one and only one Detail object.

Action

Remove the existing Detail object before adding the new one.
FAULT_EXISTS this SOAPMessage object already contains a valid Fault object
Class
Explanation

An attempt was made to add a Fault object to the SOAPBody of this SOAPMessage, but the SOAPBody already contains a Fault object. The SOAPBody can contain one and only one Fault object.

Action

Remove the existing Fault object before adding the new one.
NO_ENVELOPE this SOAPMessage does not contain a valid Envelope object
Class E
Explanation

The specified SOAPMessage does not contain a valid SOAPEnvelope object.
Action

Create a new SOAPMessage that contains a valid SOAPEnvelope object.
WSDL_SERVICE_NOT_FOUND Could not retrieve WSDL for service {0}, WSD not found.
Class E
Explanation

Integration Server could not retrieve the WSDL for the specified Web service descriptor because the specified Web service descriptor does not exist on Integration Server.

Action

Ensure that the specified Web service descriptor exists on Integration Server.
WSD_ACCESS_DENIED Access to WSDescriptor {0} denied.
Class E
Explanation

The user is not authorized to access the specified Web service descriptor.
Action

Specify a username that is authorized to access the specified Web service descriptor.
BINDER_NOT_FOUND Binder not found for soapAction = {0}
Class E
Explanation

The Web service descriptor has more than one binder, with the same operation name. Developer cannot calculate a default soapAction attribute to identify the correct operation.

Action

Include a unique soapAction attribute in the SOAPAction HTTP Header for every request.
FAULT_STRING_RPC_HANDLER_FAILURE JAX-RPC Handler failed to process the message
Class E
Explanation

The JAX-RPC handler was invoked to process the message. Either the handleRequest() or handleResponse() method returns false, indicating a failure.

Action

Check the webMethods Integration Server log for error messages generated by the JAX-RPC handler.
EXCEPTION_OCCURRED An Exception has been caught: {0}
Class E
Explanation

An exception was caught while attempting to process a SOAP message.
Action

Correct the problem indicated by the exception message.
LOCALE_MISSING Could not add "Text" element to "Reason" element, locale is null
Class E
Explanation

An attempt to add a Text element to the existing Reason element failed because the locale was not specified.
Action

Specify the locale when adding the Text element.
CANNOT_CHANGE_NAME This element's QName cannot be changed
Class I
Explanation

An attempt to change the QName of a SOAPEnvelope, SOAPBody, or SOAPHeader failed, because the QName cannot be changed.
Action

No action is required.
MISSING_HEADERS One or more required Headers "{0}" are not present in the SOAP request.
Class E
Explanation

The SOAP request received by the provider does not contain one or more required headers. Note that Integration Server considers all headers defined in a Web service descriptor to be required.

Action

Determine why the SOAP request does not contain the required headers, which might involve contacting the client to determine why the client did not include the required headers in the request.

SERVICE_HANDLER_MISSING_PARAMETER Required parameter {0} is missing
Class E
Explanation

A required input parameter was not provided.
Action

Provide the required input parameter.
SERVICE_HANDLER_INVALID_SVC The service {0} does not exist
Class E
Explanation

The specified service does not exist.
Action

Specify an existing service.
SERVICE_HANDLER_MISSING_MUTUALLY_EXCLUSIVE_PARAMETER Either parameter {0} or {1} must be provided
Class E
Explanation

The service requires either one of the specified parameters, but neither was provided.
Action

Provide one of the required parameters.
SERVICE_HANDLER_ALREADY_REGISTERED Service handler {0} is already registered
Class E
Explanation

A service handler with that name is already registered.
Action

Specify a different name when registering the service handler.
SERVICE_HANDLER_DESTROY_ERROR Error destroying service handler {0}. Error:{1}
Class E
Explanation

An error occurred while destroying the JAX-RPC handler.
Action

The destroy() method of the JAX-RPC Handler has thrown an error. Correct the error in destroy() method.
SERVICE_HANDLER_NOT_REGISTERED Service handler {0} could not be unregistered. A service handler by that name is not registered
Class E
Explanation

A service handler with the provided name is not registered.
Action

Specify the name of a registered service handler.
SERVICE_HANDLER_NOT_FOUND Service handler {0} could not be found. A service handler by that name is not registered
Class E
Explanation

The specified service handler could not be found because it is not registered.
Action

Provide the name of a registered service handler.
SERVICE_HANDLER_QNAME_NOT_FOUND Could not find service handler for header {0}:{1}
Class E
Explanation

The header QName does not correspond to a registered service handler.
Action

Verify that the QName of the header corresponds to a registered service handler or register a service handler for the provided QName.

FAULT_STRING_SERVICE_HANDLER_FAILURE Handler processing failed on the provider
Class E
Explanation

A handler service failed on the provider.
Action

Examine the handler services for errors and correct any errors that are found.
FAULT_STRING_HANDLER_FAILURE Handler processing failed on the consumer: {0}
Class E
Explanation

A handler service failed on the consumer.
Action

Examine the handler services for errors and correct any errors that are found.
MISSING_HEADERS_RESPONSE One or more required Headers "{0}" are not present in the SOAP response.
Class E
Explanation

The SOAP response received by the Web service connector does not contain one or more required headers. That is, the SOAP response does not contain a header with a QName that matches the QName of a header defined in the consumer Web service descriptor. Note that Integration Server consider all headers defined in a Web service descriptor to be required.

Action

Determine why the SOAP response does not contain the required headers, which might involve contacting the provider to determine why the provider did not include the required headers in the response.

SERVICE_HANDLER_XMLDOCUMENT_NOT_SUPPORTED Handler services do not support XML document type usage
Class E
Explanation

The name of the document type supplied to the pub.soap.handler* service is an XML document type. Integration Server does not support the use of XML document types with web services. As a result, the pub.soap.handler* services will not accept the name of XML document type as input for the documentType or documentTypes names input parameters.

Action

Modify the documentType or documentTypes input parameter to specify an IS document type name instead of an XML document type name.

WSI_ERROR_NAMESPACE A WS-I compliant Web Service Descriptor cannot contain a header or fault with a different namespace. Source: {0}
Class E
Explanation

The supplied WSDL document is not WS-I compliant because it contains a header or a fault with a different namespace.
Action

Edit the WSDL document to be WS-I compliant.

ELEMENT_AND_TYPE_CANNOT_COEXIST Cannot specify both 'element' and 'type'.
Class E
Explanation

The supplied WSDL document is invalid because element and type are both used to define a message part.

Action

Edit the WSDL document so that either element or type is used to define the message part.
NOT_A_VALID_WSD {0}: not a valid web service description document
Class E
Explanation

The file identified as the source for creating the Web service descriptor is not a .wsdl or .wsd file. A consumer Web service descriptor or a WSDL first provider Web service descriptor can be generated from a .wsdl or .wsd file only.

Action

Provide a .wsdl or .wsd file to use as the source for the Web service descriptor.

UNABLE_TO_PARSE {0}: invalid file, unable to parse root element
Class E
Explanation

The WSDL document does not contain a proper root element. Integration Server is unable to determine which element is the root element and cannot parse the root element.

Action

Ensure that the WSDL document contains a proper root element.

NODE_IS_NULL Cannot find the specified Document Type or input/output parameter.
Class E
Explanation

While creating an XML Schema definition, Integration Server cannot find the specified document type or the Input/Output parameters are not mentioned.

Action

When creating an XML Schema definition from an document type, service (input/output parameters), or specification, ensure that the chosen source exists and is not null.

CANNOT_CONVERT_TABLE_TO_XSD Field {0} is multi-dimensional which cannot be converted to xsd without using SOAP_ARRAY
Class E
Explanation

The specified field is a table (multi-dimensional) and cannot be represented in XML Schema.

Action

A multi-dimensional field such as a table can be represented as a nested fields in an array.

PORT_NULL_EXTENTED_ELEMENT Port {0} is missing required extended element.
Class E
Explanation

The WSDL document is invalid because the specified port is missing a required element. Integration Server cannot create a Web service descriptor.

Action

Edit the WSDL document to include a valid port.

BASE_TYPE_IS_NULL SimpleType {0} does not have base type.
Class E
Explanation

In the WSDL or WSD document the specified simple type definition does not have a base type.

Action

Edit the simple type definition in the WSDL document to include a base data type.

FILE_NOT_FOUND The system cannot find {0}
Class E
Explanation

The Web service descriptor cannot be created because the specified WSDL file cannot be found on the file system.

Action

Make sure that the specified WSDL file exists on the file system or that the provided URL for the WSDL file is correct.

INVALID_GENERATEXSD_PARAM Element must be a document type, service, or specification
Class E
Explanation

The specified source from which Integration Server is to create an XML Schema definition is not a document type, service, or specification.

Action

Make sure the specified source is a document type, service, or specification.

INVALID_SERVICE_SIGNATURE The service does not have a valid signature
Class E
Explanation

The service signature from which Integration Server is to create the XML Schema definition is not valid.

Action

Make sure the specified service has a valid signature that describes the expected names and data types for the inputs and outputs to the service.

WS_UNSUPPORTED_EXTENSION Unknown ExtensibleElement ''{0}''
Class E
Explanation

The portType element in the WSDL document is missing required extensions (document OR operation).

Action

Edit the WSDL document to include the required extension in the that the portType element.
ARRAY_TYPE_INVALID_QNAME Invalid WSDL; 'arrayType' attribute value {0} is malformed. Invalid QName {1}
Class E
Explanation

The supplied WSDL document is invalid because the specified arrayType attribute value contains the specified invalid QName.

Action

Edit the WSDL document to supply a valid QName for the arrayType attribute value.

ARRAY_TYPE_NO_BRACKET Invalid WSDL; 'arrayType' attribute value {0} is malformed. It should contain characters '[' and ']'
Class E
Explanation

The supplied WSDL document is invalid because the specified arrayType attribute value does not contain the opening and/or closing bracket characters '[' and ']'.

Action

Edit the WSDL by correcting the arrayType attribute value so that it includes the opening and closing bracket characters '[' and ']'.

ARRAY_TYPE_INVALID_RANK_SIZE Invalid WSDL; 'arrayType' attribute value {0} is malformed. Invalid rank size {1}
Class E
Explanation

The supplied WSDL document is invalid because the specified arrayType attribute value contains an invalid rank size. The rank size should follow the pattern: "(\\[,*\\])*\\[((\\d+,)*\\d+)?\\]" OR "(\\[,*\\])*" OR "(\\[((\\d+,)*\\d+)?\\])*")

Action

Edit the WSDL document to specify a valid rank size for the attribute. A valid rank size follows this pattern: "(\\[,*\\])*\\[((\\d+,)*\\d+)?\\]" OR "(\\[,*\\])*" OR "(\\[((\\d+,)*\\d+)?\\])*")

94.1 Repository Exception: {0}
Class E
Explanation

During initialization, Integration Server could not initialize the Repository Manager. The most likely reason is that the repository4.cnf file is corrupted.

Action

Check the directory that contains the repository files. By default, they are located at <IntegrationServer_dir>\WmRepository4\ directory. Try renaming the repository4.cnf file manually (to something like "damagedrepository4.cnf") or deleting it, then try re-initializing Integration Server. If that does not work, contact Software AG Global Support.

94.3 RepositoryManager detected damaged data files : {0}
Class E
Explanation

During initialization, Integration Server detected that some of the data files that make up the repository were corrupted. In a recovery attempt, Integration Server tried to open the files, but was unable to.

Action

Check the directory that contains the data files. By default, the data files are located at <IntegrationServer_dir>\WmRepository4\ directory. You can also look in the repository4.cnf file for the location of the data files. Try manually renaming the files (to something like "damagedFSData00000000") or deleting them, then try re-initializing Integration Server. If that does not work, contact Software AG Global Support.

94.4 RepositoryManager Exception renaming damaged data files : {0}
Class E
Explanation

During initialization, Integration Server detected that some of the data files that make up the repository were corrupted. In an attempt to correct the problem, Integration Server tried to rename the damaged files before creating new ones but encountered an exception when trying to rename the damaged files.

Action

Check the directory that contains the data files. By default, the data files are located at <IntegrationServer_dir>\WmRepository4\ directory. You can also look in the repository4.cnf file for the location of the data files. Try manually renaming the files (to something like "damagedFSData00000000") or deleting them, then try re-initializing Integration Server. If that does not work, contact Software AG Global Support.

94.6 RepositoryManager Exception creating new data files : {0}
Class E
Explanation

During initialization, Integration Server detected that some of the data files that make up the repository were corrupted. In an attempt to correct the problem, Integration Server renamed the damaged files and tried to create new ones but encountered an exception when trying to create new files. Possible reasons for the problem are that the file system does not have enough space for the data files or that Integration Server does not have write access to the directory that contains the files.

Action

Check the directory that contains the data files. By default, the data files are located at <IntegrationServer_dir>\WmRepository4\ directory. You can also look in the repository4.cnf file for the location of the data files. Make sure the file system has space for the files and that Integration Server has write access to the directory.

95.6 AuditLogManager: Exception auditing start of service {0}: {1}
Class E
Explanation

An error was encountered while audit logging the start of a service invocation.
Action

Set the logging level of the "0095 Audit Log Manager" logging facility to TRACE on the Settings > Logging > Server Logger page of the Integration Server Administrator. If the error recurs, see the error details in the server log.

95.7 AuditLogManager: Exception auditing end of service {0}: {1}
Class E
Explanation

An error was encountered while audit logging the start of a service invocation.
Action

Set the logging level of the "0095 Audit Log Manager" logging facility to TRACE on the Settings > Logging > Server Logger page of the Integration Server Administrator. If the error recurs, see the error details in the server log.

95.8 AuditLogManager: Exception auditing error for service {0}: {1}
Class E
Explanation

An error was encountered while audit logging a service invocation.
Action

Set the logging level of the "0095 Audit Log Manager" logging facility to TRACE on the Settings > Logging > Server Logger page of the Integration Server Administrator. If the error recurs, see the error details in the server log.

95.9 AuditLogManager: Audit runtime interface object cannot be initialized: {0}
Class E
Explanation

The Integration Server Audit Log Manager encountered an internal error.
Action

Contact Software AG Global Support.
95.10 AuditLogManager Runtime Exception: {0} publishing log entry {1}. {2}
Class E
Explanation

An error was encountered while audit logging a service error.
Action

See the detailed error message and stack trace that follow. If audit logging to a database, you may have to work with your DBA to diagnose a database problem.

95.14 Audit Logging initialized with errors.
Class E
Explanation

An error was encountered while starting the audit logging facility.
Action

Set the logging level of the "0095 Audit Log Manager" logging facility to TRACE on the Settings > Logging > Server Logger page of the Integration Server Administrator. If the error recurs, contact Software AG Global Support and provide them with the server log.

95.15 Database at URI {0} is not available.
Class W
Explanation

An audit logger is configured to write log messages to a database, but the database is not available.
Action

Go to the Settings > JDBC Pools page of the Integration Server Administrator and verify that the ISCoreAudit functional alias is correct. For process auditing, check the ProcessAudit functional alias. Use the Test button to check that Integration Server can reach the configured database.

95.16 Changing destination of queue {0} from database {1} to file system {2}.
Class W
Explanation

An asynchronous audit logger is configured to write log messages to a database, but the database is not available. The audit logger is being reconfigured to write audit messages to the file system.

Action

Go to the Settings > JDBC Pools page of the Integration Server Administrator and verify that the ISCoreAudit functional alias is correct. For process auditing, check the ProcessAudit functional alias. Use the Test button to check that Integration Server can reach the configured database.

95.17 Changing destination of logger {0} from database {1} to file system {2}.
Class W
Explanation

A synchronous audit logger is configured to write log messages to a database, but the database is not available. The audit logger is being reconfigured to write audit messages to the file system.

Action

Go to the Settings > JDBC Pools page of the Integration Server Administrator and verify that the ISCoreAudit functional alias is correct. For process auditing, check the ProcessAudit functional alias. Use the Test button to check that Integration Server can reach the configured database.

95.18 Cannot change destination of logger {0} to file system.
Class W
Explanation

An audit logger is configured to write log messages to a database, but the database is not available. It is not possible to write messages for this audit logger to the file system because the messages contain binary data. This audit logger is being disabled.

Action

Go to the Settings > JDBC Pools page of the Integration Server Administrator and verify that the ISCoreAudit functional alias is correct. For process auditing, check the ProcessAudit functional alias. Use the Test button to check that Integration Server can reach the configured database.

95.19 Disabling the logger {0}.
Class W
Explanation

The audit logger is being disabled. This is probably happening because the logger's database is not available.
Action

Go to the Settings > JDBC Pools page of the Integration Server Administrator and verify that the ISCoreAudit functional alias is correct. For process auditing, check the ProcessAudit functional alias. Use the Test button to check that Integration Server can reach the configured database.

95.20 Audit Logging Initialization: The {0} JDBC Pool Alias was not configured with enough connections. The Maximum Connections have been increased to {1}.
Class W
Explanation

The auditing system needed more database connections than were provided in the JDBC Pools configuration. The configuration was changed as needed.

Action

No action is required.
95.21 ERROR: Audit Logging Initialization: The {0} JDBC Pool Alias was not configured with enough connections. Unable to automatically increase the Maximum Connections setting.
Class E
Explanation

The auditing system needed more database connections than were provided in the JDBC Pools configuration. An attempt was made to automatically increase the number of connections, but it failed.

Action

Go to the Settings > JDBC Pools page of the Integration Server Administrator and increase the Max Connections setting for the ISCoreAudit functional alias. Restart Integration Server.

95.22 Audit Logging Initialization: Unable to verify the Max Connections setting for the Audit Logging database.
Class W
Explanation

Integration Server encountered an error while checking the Max Connection setting for the ISCoreAudit functional alias.
Action

If the auditing system is slow or unresponsive, go to the Settings > JDBC Pools page of the Integration Server Administrator and increase the Max Connections setting for the ISCoreAudit functional alias.

95.24 The value for watt.server.audit.logDir has been changed and does not identify an existing directory that Integration Server can write to. File-based audit logs will continue to be written to the {0} directory.
Class W
Explanation

The audit log directory was not changed because the watt.server.audit.logDir parameter refers to a directory that either does not exist or Integration Server does not have permission to write to. As a result, Integration Server will write file-based audit logs to the last valid directory specified.

Action

Go to the Settings > Extended page in the Integration Server Administrator and change the value for the watt.server.audit.logDir parameter. Specify a directory that exists on the server and that Integration Server can write to. You can specify the full path name, or a relative path in relation to the Integration Server.

95.25 The {0} file was not found and is being created.
Class W
Explanation

Upon start up, Integration Server could not find the specified file, for which {0} is a placeholder, in the following directory: IntegrationServer/instances/instanceName/config/auditing where instanceName is the Integration Server instance that was started. Integration Server will create the file. The file specifies which database errors are considered transient.

Action

If the specified file has been modified, restore the file from a backup, if possible. If the file has not been modified, no action is necessary.

95.26 The {0} file was not found and is being created. The audit logging system is using default settings.
Class W
Explanation

Upon start up, Integration Server could not find the specified file, for which {0} is a placeholder, in the following directory: IntegrationServer/instances/instanceName/config/auditing where instanceName is the Integration Server instance that was started. The specified file contains the configured auditing logging settings. Integration Server will create the file, which will contain the default auditing logging settings.

Action

If the specified file has been modified, restore the file from a backup or use Integration Server Administrator to restore the configured audit logging settings . If the file has not been modified (that is, you have not modified the audit logging configuration), no action is necessary.

95.30 Audit Logging: The {0} has entered fail-fast mode for messaging connection alias {1}.
Class I
Explanation

The specified audit logger has entered queue fail-fast mode lost the connection to the Universal Messaging server established through indicated messaging connection alias. The audit logger will write log entries to the internal audit logging queue instead of the Universal Messaging

Action

Make sure that Universal Messaging server is up and running and that there are no network related problems between Integration Server and Universal Messaging server.

95.31 Audit Logging: The {0} has exited fail-fast mode for the messaging connection alias {1}.
Class I
Explanation

The specified audit logger has exited queue fail-fast mode because connectivity to the Universal Messaging server has been restored. The audit logger writes new log entries to the Universal Messaging queue.

Action

None.
95.32 Audit Logging: Session for messaging connection alias {0} disconnected.
Class I
Explanation

The session on a Universal Messaging server created using the specified messaging connection alias has disconnected. Any audit loggers that use the specified messaging connection alias to write log entries to a Universal Messaging queue will enter queue fail-fast mode and begin writing log entries to the internal audit logging queue.

Action

Make sure that Universal Messaging server is up and running and that there are no network related problems between Integration Server and Universal Messaging server.

95.33 Audit Logging: Reestablished connection with session for messaging connection alias {0}.
Class I
Explanation

The session on a Universal Messaging server created using the specified messaging connection alias has been re-established. Any audit loggers that user the specified messaging connection alias will exit queue fail-fast mode and resume writing new log entries to the Universal Messaging queue

Action

None.

95.37 Pool with messaging connection alias name {0} does not exist.
Class E
Explanation

For an audit logger configured to use Universal Messaging as the queue provider, Integration Server requested a session from a pool for a Universal Messaging connection alias that does not exist. The Universal Messaging connection alias specified in the Connection Alias field for the logger does not exist.

Action

Make sure the logger specifies an existing Universal Messaging connection alias for the Connection Alias field.

95.38 watt.server.audit.um.sessionPool.min.value is invalid {0}. Value must be an integer greater than zero. Integration Server will use default value of 2.
Class W
Explanation

The watt.server.audit.um.sessionPool.min value is invalid because it is not an integer greater than zero. Integration Server will use the default value of 2 until a valid value is specified.

Action

Set watt.server.audit.um.sessionPool.min to an integer greater than 0 (zero) but less than or equal to the value of watt.server.audit.um.sessionPool.max.

95.39 watt.server.audit.um.sessionPool.max.value is invalid {0}. Value must be an integer greater than zero. Integration Server will use default value of 10.
Class W
Explanation

The watt.server.audit.um.sessionPool.max value is invalid because it is not an integer greater than zero. Integration Server will use the default value of 10 until a valid value is specified.

Action

Set watt.server.audit.um.sessionPool.max to an integer greater than 0 (zero) but greater than or equal to watt.server.audit.um.sessionPool.min.

95.40 Invalid watt.server.audit.um.sessionPool.min value {0) and watt.server.audit.um.sessionPool.max value {1}. watt.server.audit.um.sessionPool.min must be less than or equal to watt.server.audit.um.sessionPool.max. Integration Server will use the default values of 2 and 10, respectively.
Class W
Explanation

The watt.server.audit.um.sessionPool.min value and watt.server.audit.um.sessionPool.max value are invalid because the watt.server.audit.um.sessionPool.min value is greater than the watt.server.audit.um.sessionPool.max value. Integration Server will use the default values of 2 and 10, respectively, until valid values are specified

Action

Set watt.server.audit.um.sessionPool.mim and watt.server.audit.um.sessionPool so that both are integers greater than 0 (zero) and watt.server.audit.um.sessionPool.min value is less than or equal to the watt.server.audit.um.sessionPool.max value.

95.9998 AuditLogManager Exception: {0}
Class E
Explanation

An error was encountered using the audit logging database.
Action

Try logging again. It may be a transient error. If the error persists, examine the detailed message and stack trace that follow. You may need to work with your DBA to diagnose a problem with the audit logging database.

96.1 JDBCConnectionManager: initialization failed for {0} functional alias, check configuration.
Class E
Explanation

Unable to initialize the functional alias. Integation Server will not be able to connect to the database for this functional alias.

Action

Go to the Settings > JDBC Pools page of the Integration Server Administrator and verify that the functional alias settings are correct. Use the Test button to check that Integration Server can reach the configured database.

96.2 JDBCConnectionManager: creating Embedded Pool Alias for {0}.
Class W
Explanation

The connection pool for the embedded database is being created.
Action

No action is required.
96.4 JDBCConnectionManager: embedded database objects not created: {0}
Class E
Explanation

Unable to create tables, keys, or other database objects while initializing the embedded database.
Action

Verify that Integration Server has write access to the file system. If the problem persists, contact Software AG Global Support.
96.5 JDBCConnectionManager: initialization failed with exception {0}
Class E
Explanation

Initialization of the JDBC Connection Manager failed.
Action

Contact Software AG Global Support.
96.10 The DataStoreDBListener has detected a bad connection for the {0} JDBC functional alias. The JDBC connection pool is being reinitialized
Class E
Explanation

A database connection being used by the pub.storage services is no longer functional. This often indicates a network interruption has broken all existing database connections. Integration Server is reinitializing the pool of connections for the JDBC functional alias. If network connectivity has been restored, the pub.storage services may continue to be used without interruption. If network connectivity has not been restored, the pub.storage services will continue to fail until it is restored.

Action

If the network interruption is transient and connectivity to the database is restored quickly, no immediate action is required. If the network interruption persists, or if transient network interruptions continue to occur, this indicates a problem in the network or in the networking implementation of the host that Integration Server is running on. Seek assistance from a networking expert in your company to investigate and resolve this problem.

97.4 Failed to lock Repository entry {0}
Class E
Explanation

Integration Server encountered an internal error when trying to lock the repository.
Action

If the error continues, contact Software AG Global Support.
SHUTDOWN Messaging synchronizer shutdown
Class I
Explanation

The Broker Synchronizer has shut down.
Action

No action is required. This message is displayed when Integration Server is shutting down.
CAN_NOT_OPEN_REPO Messaging Synchronizer cannot open repository for sync-state storage
Class E
Explanation

An error was encountered while trying to open WmRepository4.
Action

Contact Software AG Global Support.
CAN_NOT_DESTROY Messaging Synchronizer cannot update sync state; cannot remove sync data from repository: {0}
Class E
Explanation

An error occurred while removing sync state data from WmRepository4.
Action

Contact Software AG Global Support.
NSNAME_REQUIRED Messaging Synchronizer cannot update sync state; document type not specified
Class E
Explanation

The document type to be syncrhonized was not specified; the nsName input variable is null.
Action

Specify a document type name for nsName.
NSNAME_HAS_NO_SYNC_STATE Messaging Synchronizer cannot update sync state; document type {0} has no sync state
Class D
Explanation

The requested document type has no sync state.
Action

No action is required.
IS_NOT_CONNECTED_TO_BROKER Messaging Synchronizer cannot perform sync; Integration Server cannot connect to provider
Class E
Explanation

Synchronization cannot occur because Integration Server cannot connect to the message provider.
Action

Make sure the message provider is running and that the message connection alias is enabled in Integration Server Administrator.
98.3 Exception occurred while decoding Broker Document {0} : {1}
Class U
Explanation

Integration Server failed to decode the document received from the Broker. The document may be corrupt.
Action

Check the publisher of the document. Consider redelivering the document from the Broker.
98.10 Exception initializing Dispatcher configuration from file: {0}
Class U
Explanation

Integration Server encountered the indicated exception while trying to initialize the Dispatcher. This is a serious internal error.

Action

Contact Software AG Global Support.
98.23 Document Router for Consumer Queue:{0} encountered error: {1}
Class E
Explanation

Integration Server encountered an error while routing a document to a Broker.
Action

The action to take depends on the exception that occurred. Review the returned exception for more guidance.
98.24 No Trigger available for incoming Document {0}. Rejecting Document
Class U
Explanation

Integration Server failed to deliver the incoming document to thea trigger because there is not a trigger that subscribes to the document. The intended trigger may be disabled or deleted.

Action

Examine the existing triggers. If a trigger that subscribes to the document is disabled, enable it and ask the publisher to re-publish or deliver the document.

98.25 Document {0} from store {1} exceeded Redelivery Count.
Class E
98.29 Exception while doing Request Reply: {0}
Class U
Explanation

Integration Server encountered an internal error while executing a request reply.
Action

Contact Software AG Global Support.
98.30 {0} received duplicate document(s). Error {1}
Class E
Explanation

Integration Server determined that it received duplicate documents from a publisher.
Action

If you determine that the Integration Server did receive duplicate messages, check the publishing source to learn the source of the problem.

In some cases, Integration Server did not really receive duplicates. For example, two documents might use the same tracking ID but have different content. If Integration Server did not receive a duplicate document, try resubmitting the document using webMethods Monitor.

98.31 Consumer:{0} unable to persist Document(s) to Document Store. Error: {1}
Class E
Explanation

Integration Server failed to write a document to the transient store. A likely cause is that the Integration Server JVM has run out of memory.

Action

Try increasing the heap size of the JVM. The heap size indicates how much memory is allotted for server processes.

98.33 Error while shutting down Dispatcher: {0}
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
98.36 {0} encountered Transport Exception: {1}
Class U
Explanation

Integration Server failed to publish the document because of one of the following:

1) The Broker is temporarily unavailable.

2) The client does not have the canPublish permission for its associate Broker document.

3) The document being published does not conform to the Broker document on the Broker. This may be because the document was not synchronized with the one on the Broker.

4) An internal error occurred.
Action

Do one of the following:

1) Check the Broker status. If the Broker or network connection is temporarily down, wait until they are up to re-publish the document.

2) Using the Broker administration tool, check the publication permissions of the client group to which the trigger client belongs. Make sure that the client is allowed to publish the document.

3)Synchronize the document and make sure that the document being published matches its associate Broker document type.

4) If the previous actions fail to correct the problem, contact Software AG Global Support.
98.38 {0} handling invalid Document. Exception: {1}
Class E
Explanation

Integration Server encountered an error while processing a document. Specifically, the document does not have a corresponding publishable document type on the Integration Server or the publishable document type does not have a matching schema.

Action

Make sure that the appropriate document types and schemas for the document exist on the Integration Server.
98.41 Unable to connect to Broker. Starting to poll
Class E
98.44 Exception while interacting with the Document Store name:{0} Problem:{1}
Class U
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
98.45 Unrecoverable Exception while initializing the Dispatcher: {0}
Class U
Explanation

Integration Server encountered the indicated exception while trying to initialize the Dispatcher. This is an internal error.
Action

Contact Software AG Global Support.
98.47 Connection to Broker unavailable. Unable to create transport for Trigger:{0}.
Class E
98.48 Unable to remove subscription for Publishable Document {0} from transport:{1}. If connected, please remove subscription from {2} manually.
Class U
Explanation

Integration Server failed to remove the document type subscription before unregistering the trigger. The Broker may be unavailable.
Action

In the Broker Administrator, check the status of the Broker and the network connection. If one or both are down, then you will need to manually remove the stale subscriptions for the trigger when they are back up.

98.49 Exception:{0} while executing trigger. Unable to acknowledge Document for TriggerStore:{1}.
Class U
Explanation

Integration Server failed to execute the trigger. This indicates an internal error.
Action

Contact Software AG Global Support.
98.55 Exception during attempt to register Trigger: {0}
Class U
Explanation

Integration Server failed to register the trigger. This indicates an internal error.
Action

Contact Software AG Global Support.
98.56 Unable to acknowledge Document {0} to transport for Trigger {1}. Exception:{2}
Class U
Explanation

Integration Server encountered an internal error while acknowledging the document to the transport for the trigger.
Action

Contact Software AG Global Support.
98.57 Unable to delete Document Store for Trigger:{0}. Exception:{1}
Class U
Explanation

Integration Server encountered an internal error while deleting the document store associated with the trigger.
Action

Contact Software AG Global Support.
98.58 Stopping delivery of {1} to trigger {0} to prevent infinite loop.
Class E
98.59 Exception while shutting down the Document Stores:{0}.
Class U
Explanation

Integration Server encountered a serious internal error while shutting down.
Action

Contact Software AG Global Support.
98.60 Exception while saving Dispatcher configuration :{0}.
Class U
Explanation

Integration Server encountered an exception while trying to save Dispatcher configuration information to the dispatch.cnf file in the <IntegrationServer_dir>/config directory.

Action

If the dispatch.cnf file is set to read-only, change it to read/write. If the file is not set to read-only, this error indicates a serious internal error and you should contact Software AG Global Support.

98.62 {0} encountered Exception: {1}
Class E
98.73 ControlledPublishOnSuccess max exceeded while processing {0}
Class U
Explanation

Integration Server failed to publish a document because the maximum concurrent publish-on-success value was exceeded.
Action

Do one of the following:

1) On the Integration Server, increase the "concurrent publish on success" setting by editing the "watt.server.control.maxPublishOnSuccess" property.

2) Decrease the number of concurrent publish operations in the service.
98.74 Outbound msg store max exceeded, services blocking. Start broker to drain store.
Class E
98.75 Insufficient memory while decoding event:{0} for {1}.
Class E
Explanation

Integration Server does not have sufficient memory to decode the documents being retrieved from the Broker. Integration Server will attempt to decode the documents one more time.

Action

Check the size of the documents sent by the Broker and consider increasing the heap size of the Integration Server's JVM.

98.76 Unable to decode events for {0}. Please check JVM Heap size and/or size of Documents on the Broker.
Class U
Explanation

Integration Server does not have sufficient memory to decode the documents from the Broker.
Action

Check the document size sent by the Broker and consider increasing the heap size of the JVM used by Integration Server.

98.77 Dispatcher out of memory. Retrying operation.
Class E
Explanation

Integration Server does not have sufficient memory to continue its document publishing operations. Integration Server will attempt to process this message again.

Action

Consider increasing the heap size of the JVM used by Integration Server.

98.78 Dispatcher out of memory. Operation failed. Check error log.
Class E
Explanation

Integration Server does not have sufficient memory to continue its document publishing operations. Integration Server has exceeded its retry count, and an exception will be thrown.

Action

Consider increasing the heap size of the JVM used by Integration Server.

98.79 Dispatcher out of memory. Retry succeeded.
Class E
Explanation

Integration Server successfully retried a publishing operation after an OutOfMemory error prevented the operation from working the first time.

Action

If the Integration Server continues to issue this message, check the JVM Heap size and/or size of Documents on the Broker. The Trigger configuration (possibly the acknowledgment queue size) may need to be adjusted.

98.80 Insufficient memory while persisting messages for Trigger: {0}.
Class U
Explanation

Integration Server does not have sufficient memory to persist the documents to the document store for the trigger.
Action

Check the size of the documents being persisted and consider increasing the heap size of the JVM used by Integration Server.

98.81 Insufficient memory while persisting message: {1} for Trigger: {0}.
Class U
Explanation

Integration Server does not have sufficient memory to persist a single document to the document store for the trigger.
Action

Check the size of the document being persisted and consider increasing the heap size of the JVM used by Integration Server.
98.82 Unable to persist Document: {0} to Document Store: {1}. Exception: {2}
Class U
Explanation

Integration Server failed to persist the document to the document store. This indicates a serious internal error.
Action

Contact Software AG Global Support.
98.83 Unable to acknowledge Document: {0} for Trigger Store: {1}. Insufficient memory.
Class U
Explanation

Integration Server does not have sufficient memory to acknowledge the document to the document store.
Action

Check the size of the document being persisted and consider increasing the heap size of the JVM used by Integration Server.

98.84 Exception:{0} during Trigger dispatching.
Class U
Explanation

Integration Server encountered an internal error while which processing a document destined for an individual trigger.
Action

Contact Software AG Global Support.
98.85 Unable to remove all subscriptions for transport:{0} while unregistering trigger. If connected, please remove subscription from {1} manually.
Class U
Explanation

Integration Server failed to remove all stale subscriptions before unregistering the trigger. The Broker may be unavailable.
Action

In the Broker Administrator, check the status of the Broker and the network connection. If one or both are down, then you will need to manually remove the stale subscriptions for the trigger when they are back up.

98.86 Unable to remove all subscriptions for transport:{0} before registering trigger. If connected, please remove stale subscriptions from {1} manually.
Class U
Explanation

Integration Server failed to remove all stale subscriptions before registering the trigger. The Broker may be unavailable.
Action

In the Broker Administrator, check the status of the Broker and the network connection. If one or both are down, then you will need to manually remove the stale subscriptions for the trigger when the Broker and network are back up.

98.87 Duplicate document of type:{0} with Id:{1} received for trigger:{2}.
Class E
98.89 Transaction size (no of documents * size of documents) is too large for Document Store: {0}. Please reduce capacity of Trigger and /or increase initial size of Document Stores.
Class U
Explanation

The Integration Server failed to persist documents because the document store did not contain enough space. Documents received from the Broker are persisted in the triggers' persistent stores.

Action

In the Integration Server Administrator, click Settings>Resources>Document Stores. On this page, consider increasing the initial size of the document store. Also, consider reducing the number of triggers that subscribe to the document.

98.90 Size of Document: {0} for Document Store: {1} is too large. Server is unable to persist. Audit logging the document.
Class U
Explanation

Integration Server failed to persist a document because the document store did not contain enough space.
Action

In the Integration Server Administrator, click Settings>Resources>Document Stores. On this page, consider increasing the initial size of the document store.

98.96 Integration Server is now connected to a Broker that tracks document redelivery counts. Restart the Integration Server to make use of redelivery counts in duplicate detection.
Class I
Explanation

Integration Server connects to a version of the Broker that supports redelivery count. Previously it was connected to a Broker that did not support this feature.

Action

Restart Integration Server so that it can take advantage of the redelivery count feature supported by the Broker.
98.100 Copying of documents to trigger store started.
Class
98.103 {0} not initialized. Adjust document store settings and restart server.
Class S
Explanation

Integration Server was unable to create the Document Store on disk. The Document Store is essential for Integration Server functioning, therefore startup terminates.

Action

Check to see if there is enough disk space on the drive where the Document Store is being created (usually under <IS_SERVER_ROOT>\DocumentStore directory). If there is sufficient disk space, then check to see if the dispatch.cnf file under <IS_SERVER_ROOT>\config directory is corrupted. If the problem persists despite a re-start, contact Software AG Global Support.

98.104 Integration Server is now connected to a Broker that does not track document redelivery counts. Restart the Integration Server so that duplicate detection does not expect document redelivery counts.
Class I
Explanation

Integration Server connects to a version of the Broker that does not support the redelivery count. Previously it was connected to a Broker that does support this feature.

Action

Restart the Integration Server so that its duplicate detection mechanism does not expect redelivery counts to be present in documents delivered by the Broker.

98.105 Unable to fully build comparable trigger: {0}
Class E
Explanation

During Cluster Synchronization, Integration Server was unable to compare trigger nodes across all the nodes in the cluster. The most likely cause is that one or more triggers are not completely configured. Cluster Synchronization makes sure that changes made to a trigger's configuration on one Integration Server are propagated to other servers in the cluster. If an Integration Server is configured for Cluster Synchronization, this process runs when an administrator makes a trigger configuration change through the Integration Server Administrator or when a user-written service calls one of the pub.trigger:* services.

Action

Using the development tool, check the trigger configuration. After correcting the problem, retry the task you were performing when the error occurred.

98.106 Trigger comparison failed: trigger = {0}; parameter = {1}; local value = {2}; remote value = {3}.
Class
98.107 Error occurred during cluster invoke: Alias = {0}; Service = {1}; Exception = {2}.
Class E
Explanation

During Cluster Synchronization, Integration Server threw an exception while invoking a service on a remote node in the cluster. Cluster Synchronization makes sure that changes made to a trigger's configuration on one Integration Server are propagated to other servers in the cluster. If an Integration Server is configured for Cluster Synchronization, this process runs when an administrator makes a trigger configuration change through the Server Administrator or when a user-written service calls one of the pub.trigger:* services.

Action

The action you take depends on the exception issued. Look at the exceptionMessage for specific information.
98.108 Serial trigger {0} has been automatically suspended due to an exception: {1}.
Class
98.109 Unable to establish secure connection to Broker. Password needed for SSL connection to Broker:{0}.
Class
98.112 Trigger Resource Monitor now monitoring resource availability for trigger "{0}".
Class
98.113 Trigger Resource Monitor invoked "{0}". Status of resource is "available".
Class
98.114 Trigger Resource Monitor invoked "{0}". Status of resource is "not available".
Class
98.115 Trigger Resource Monitor has resumed trigger "{0}".
Class
98.116 Trigger Resource Monitor encountered an exception while attempting to resume trigger "{0}": {1}
Class
98.117 The ISInternal functional alias is not configured properly on the JDBC Pools page. It is required in order to create and manage AND and XOR trigger joins. Assign a valid database pool and restart the Integration Server.
Class
98.118 The ISInternal functional alias on the JDBC Pools page must be configured to use an external database in order to create and manage AND and XOR trigger joins.
Class
98.119 Trigger Retry Failure occurred for trigger "{0}" : "{1}" . This trigger is being suspended and the message is being rolled back to the Broker because the Audit Logging subsystem also failed: "{2}"
Class
98.120 The default Broker was detected while initializing the dispatch.cnf file. Broker Settings will automatically be enabled.
Class
98.121 The default Broker was not detected while initializing the dispatch.cnf file. Broker Settings will automatically be disabled.
Class
98.122 The subscription for publishable document {0} will not be removed or recreated because the client prefix {1} used by the Broker connection for trigger {2} may be shared by multiple clients. If required, please remove subscription from Broker manually.
Class
98.123 The subscription for publishable document {0} will not be removed or recreated because the client prefix {1} used by the Broker connection for trigger {2} may be shared by multiple clients. If required, please remove subscription from Broker manually.
Class
98.124 A username and password are required for Username/Password authentication.
Class E
Explanation

Authentication credentials were not specified.
Action

Provide a username and password.
INCOMPLETE_TRANSPORT_PROPERTIES Required property missing for creating {0} transport: {1}
Class U
Explanation

Integration Server could not read properties from the <IntegrationServer_dir>\config\dispatch.cnf file. The file may be corrupt.
Action

Examine the dispatch.cnf file to make sure that it is not corrupt and that the "clientGroupName" and "brokerHost" fields exist. If the file is corrupt, rename it and restart Integration Server. After you do this, you can re-configure the Broker Settings using the Integration Server Administrator.

INVALID_CONNECTION_PROPERTIES Invalid connections properties for creating {0}
Class
NO_PUBRECORD No matching Document Type exists for {0}
Class U
Explanation

A pub.publish* service returned an error because the document specified in the "documentTypeName" parameter does not exist on the Integration Server.

Action

Examine the input for the "documentTypeName" parameter. Make sure that the parameter specifies the fully qualified name of the document type for which you want to publish or deliver an instance. Keep in mind that document type names are case-sensitive. Additionally, ensure that the specified document type exists on Integration Server.

INVALID_DOCUMENT Data does not conform to the Publishable Document Type {0} errors: {1}
Class E
Explanation

A pub.publish* service issued an error because the IData input for the "document" parameter does not conform to the document type specified in the "documentTypeName" parameter.

Action

Examine the validation error message and the IData object passed to the "document" parameter. Make sure that it conforms to the document type specified in the "documentTypeName" parameter.

NO_TRANSPORT_FOR_ID No registered Transport for the given id: {0}
Class U
Explanation

Integration Server failed to create a subscription to the publishable document type specified in a trigger. The transport information does not exist, which indicates an internal error.

Action

Contact Software AG Global Support.
CERTFILE_REQUIRED_FOR_SSL Certificate file require for using SSL encryption
Class
REQUEST_REPLY_ERROR No waiting thread for Document Id: {0}. Requestor might have timed out.
Class E
Explanation

Integration Server encountered an internal error while publishing the document and waiting for a reply.
Action

Contact Software AG Global Support.
NOT_PUB_RECORD {0} is not a Publishable Document Type.
Class U
Explanation

A pub.publish* service returned an error because the document type specified in the "documentTypeName" parameter was not publishable.
Action

Ensure that the Publishable property is set to "true" for the document type."
DISPATCHER_NOT_INITIALIZED Dispatcher is not initialized
Class U
Explanation

Integration Server was not able to publish, deliver, or reply to a document because the dispatcher that is responsible for performing these operations was not initialized.

Action

Log on to the Integration Server Administrator and make sure that you have correctly configured Integration Server for document publishing.

BROKER_EXCEPTION BrokerException: {0}
Class U
Explanation

Integration Server was unable to publish or retrieve documents from the Broker because the operation failed on the Broker.
Action

Examine the error message provided by the Broker. Refer to the webMethods Broker API documentation for the Java Client for a detailed description of the error.

MSG_EXCEEDED_DELIVERY_COUNT Rejected document because Dispatcher was unable to deliver document after {0} attempts
Class
UNABLE_TO_SUBSCRIBE Broker Transport unable to subscribe to Publishable Document Type:{0} BrokerEvent Type:{1}
Class U
Explanation

Integration Server failed to create a subscription to the publishable document type specified in a trigger. The client is not allowed to subscribe to the Broker document type associated with the publishable document type.

Action

In the Broker Administrator, check the subscription permissions of the client group to which the trigger belongs. Make sure that the client is allowed to subscribe to the Broker document type associated with the publishable document type.

NO_TRIGGER_FOR_EVENT Rejecting document as there is no enabled Trigger registered:
Class
UNABLE_TO_INIT_DISPATCHER Unrecoverable Error while initializing the webMethods Messaging Subsystem (Dispatcher): {0}. No webMethods Messaging features will be available until this issue is resolved and the server is restarted.
Class E
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
REQUEST_REPLY_TIMED_OUT Request timed out while waiting for reply
Class U
Explanation

Integration Server encountered an internal error while publishing or delivering the document and waiting for a reply.
Action

Contact Software AG Global Support.
REQUEST_REPLY_INCORRECT_REPLY_TYPE Received incorrect document as Reply. Expecting {0} and received {1}
Class U
Explanation

Integration Server failed to receive the expected reply document while publishing or delivering the document and waiting for a reply.

Action

Check the subscriber of the publisher document. Make sure that the subscriber delivers a correct reply document.
INVALID_DISPATCHER_MESSAGE Invalid DispatcherMessage {0}
Class E
Explanation

Integration Server failed to deliver the document to the subscribing triggers. The document is null, which indicates an internal error.

Action

Contact Software AG Global Support.
UNABLE_TO_REGISTER_FACTORY Transport Factory: {0} not found.
Class U
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
UNKNOWN_TRANSPORT_TYPE {0} Unknown Transport Type specified. Unable to create transport.
Class U
Explanation

Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
UNABLE_TO_DELIVER {0} not configured. {1} operation can only be done after a {0} is configured.
Class U
Explanation

The pub.publish:deliver or pub.publish:deliverAndWait service failed to execute because Integration Server is not configured to connect to the Broker.

Action

Use Integration Server Administrator to configure the server to connect to a Broker.
BROKER_VERSION_UNKNOWN Unknown broker version.
Class U
Explanation

Integration Server failed to connect to the Broker because the version of the Broker is not supported.
Action

Do not attempt to set up such an environment. See the "Installing webMethods Products" for supported configurations.
BROKER_VERSION_NOT_SUPPORT Incompatible Broker version. The minimum Broker version required is 6.0.
Class
INVALID_TRIGGER_DUPLICATE_CONDITION_NAMES Duplicate condition name ''{1}'' in Trigger ''{0}''
Class E
Explanation

Integration Server could not save the condition settings of a trigger because the trigger has duplicate condition names.
Action

Edit the trigger so that each condition has a unique name.
INVALID_TRIGGER_INVALID_TRIGGER_INVALID_JOIN_CONDITION Condition name ''{0}'' - Cannot have duplicate document types in AND join.
Class E
Explanation

Integration Server could not save a trigger because a condition has duplicate document types in an "AND" join.
Action

Edit the trigger condition to make sure that unique document types are specified in the "AND" join.
INVALID_TRIGGER_FILTER_MISMATCH Cannot specify different filters for document type ''{0}'' within a single trigger
Class E
Explanation

Integration Server could not save the condition settings of a trigger because more than one filter is specified for a document type in the trigger.

Action

If multiple conditions in the trigger specify the same document type, make sure that the filter applied to the document type is the same for each condition.

UNABLE_TO_ACK Unable to ack
Class U
Explanation

Integration Server failed to acknowledge the document to the trigger document store. This indicates an internal error.
Action

Contact Software AG Global Support.
BROKER_NOT_CONNECTED Unable to publish volatile Document: {0}. Broker not connected.
Class U
Explanation

Integration Server published a volatile document while the Broker was down. A service exception occurred for the publishing service and the volatile document was lost.

Action

Make sure the Brroker is available and re-publish the document.
JOIN_NULL_ACTIVATION No activation specified for Join Document:{0}.
Class U
Explanation

The published document cannot be processed in a join because it is missing an activation ID.
Action

The publisher of the document needs to set an activation ID for the document.
CMDS_NOT_ALL_SAME cmd for msgs all not the same or null
Class U
Explanation

A flow service mixed the pub.publish:deliver and pub.publish:publish steps when the "delayUntilServiceSuccess" parameter is set to "true".

Action

Use separate flow services to deliver and publish a message when the "delayUntilServiceSuccess" parameter is set to "true".
DESTS_NOT_ALL_SAME destination for msgs all not the same or null
Class U
Explanation

A flow service contains multiple pub.publish:deliver steps where the "delayUntilServiceSuccess" parameter is set to "true", but the destination IDs are not identical.

Action

Use separate flow services to deliver a message to different destination IDs when the "delayUntilServiceSuccess" parameter is set to "true".

CPOS_SUSPENDED publish-on-success is suspended
Class E
Explanation

The publish-on-success facility has been programmatically suspended. Therefore, the publish-on-success operation will not work.

Action

Restart the Integration Server.
CPOS_EXCEEDED max concurrent publish-on-success is exceeded
Class E
Explanation

The watt.server.control.maxPublishOnSuccess parameter was exceeded by a publishing flow. The maxPublishOnSuccess parameter controls the maximum number of documents that Integration Server publishes on success at one time.

Action

Decrease the number of documents published by a flow service that uses publish-on-success, or increase the value of the maxPublishOnSuccess parameter.

DOCUMENT_STORE_CAPACITY Document store runtime capacity
Class
STORE_MISSING Document store is missing for {2}
Class U
Explanation

Integration Server encountered an internal error in the document store.
Action

Contact Software AG Global Support.
STEP_SIZE_POSITIVE Step size for {2} must be positive and no greater than 100: {3}
Class
UNABLE_TO_REMOVE_FROM_IDR Unable to mark as complete to the Document History
Class
REQUEST_REPLY_ERROR_REPLY Error reply {0} received. adapterType:{1}, errorCategory:{2},errorText:{3},eventId:{4}
Class E
Explanation

A client, typically an Integration Server but possibly a Broker client or Adapter, sent a request document to an Integration Server, but received an error reply (a document of type pub.publish.notification:error ) in response. This happens when the service executing the request document on the target server encounters an error. Instead of sending the expected reply document type, it sends an error document indicating it could not process the request document correctly.

Action

Check the Error log of the target Integration Server, that is, the Integration Server to which the request document was sent. If the error occurred when a document was being published to a single subscriber, you will know which target server issued the error reply. However, if the error occurred during a publish to multiple Integration Servers, you will have to determine which target server issued the error.

MISSING_REQUIRED_PARAMETER Missing required parameter: "{0}".
Class E
Explanation

A client tried to invoke a service, but did not specify a required parameter.
Action

Supply the missing required parameter.
TRIGGER_NOT_FOUND Trigger not found for triggerName: "{0}".
Class E
Explanation

Integration Server tried to suspend or fetch metadata for the indicated trigger, but there is no trigger with this name enabled on Integration Server.

Action

Make sure the trigger name is typed correctly and that the trigger is enabled.
UNABLE_TO_GET_TRIGGER_STATUS Unable to get status for Trigger "{0}": No IControlObject found.
Class E
Explanation

Integration Server encountered an error while trying to perform an action against a trigger, but the trigger was not completely configured, and as a result, not fully initialized.

Action

Verify that the trigger is properly configured and is considered to be valid. After correcting the problem, retry the task you were performing when the error occurred.

UNABLE_TO_GET_TRIGGER_STATUS_EX Unable to get status for Trigger "{0}": {1}
Class E
Explanation

Integration Server encountered an error while trying to perform an action against a trigger.

- For trigger retrieval, the status indicates whether the trigger is active or suspended.

- For trigger processing, the status indicates whether the trigger is active or suspended and shows the current threads being used, the current volatile queue size, and the current persisted queue size.

Action

The action you take depends on the exception issued. Look at the exception message and the server log for additional details.
TRIGGER_IS_LOCKED Trigger "{0}" is locked. Change not permitted.
Class E
Explanation

A user tried to modify the indicated trigger using the Trigger Management screens in Integration Server Administrator or the built-in services, but the trigger is locked.

Action

Unlock the trigger and try again.
UNABLE_TO_SUSPEND Unable to suspend document {0} for Trigger "{1}": No IControlObject found.
Class E
Explanation

A request to suspend document processing failed. The most likely cause is that the trigger was not completely configured, and as a result, not fully initialized.

Action

Make sure the trigger is configured properly and is considered to be valid. After correcting the problem, retry the task you were performing when the error occurred.

UNABLE_TO_SUSPEND_EX Unable to suspend document {0} for Trigger "{1}": {2}
Class E
Explanation

A request to suspend document processing failed due to the indicated exception.
Action

The action you take depends on the exception issued. Look at the exception message value in the message for specific information.
UNABLE_TO_RESUME Unable to resume document {0} for Trigger "{1}": No IControlObject found.
Class E
Explanation

A request to resume document processing failed. The most likely cause is that the trigger was not completely configured, and as a result, not fully initialized.

Action

Make sure the trigger is properly configured and is considered to be valid. After correcting the problem, retry the task you were performing when the error occurred.

UNABLE_TO_RESUME_EX Unable to resume document {0} for Trigger "{1}": {2}
Class E
Explanation

A request to resume document processing failed due to an exception.
Action

The action you take depends on the exception issued. Look at the exception message value in the message for specific information.
UNABLE_TO_PERSIST_CHANGE Unable to persist the change made to Trigger "{0}": {1}
Class E
Explanation

The configuration change for a trigger was not saved to file. As a result, the change will revert back to its original value after Integration Server restarts or someone reloads the package.

Action

The action you take depends on the exception issued. Look at the exception message value in the message for specific information.
EXTHREADS_CANT_EXCEED_CAP maxExecutionThreads cannot exceed queueCapacity
Class E
Explanation

The value specified for the number of maximum execution threads exceeds the queue capacity. This is not permitted because the number of documents the Integration Server can process concurrently (maxExecutionThreads) cannot exceed the maximum number of documents that can be in the trigger's queue (queueCapacity).

Action

Change the maximum execution threads value to be less than or equal to the queue capacity. Alternatively, change the queue capacity value so that it is greater than or equal to the maximum execution threads.

REFILL_CANT_EXCEED_CAP queueRefillLevel cannot exceed queueCapacity
Class E
Explanation

The value specified for the queue refill level exceeds the queue capacity. The queue refill level is the number of unprocessed documents that must remain in the trigger queue before Integration Server retrieves more documents for the queue from the Broker. This level cannot exceed the maximum number of documents that can be in the trigger's queue (queueCapacity).

Action

Change the queue refill level value so that it is less than or equal to the queue capacity. Alternatively, change the queue capacity value so that it is greater than or equal to the queue refill level.

NUMBER_MUST_BE_POSITIVE {0} must be a positive number.
Class E
Explanation

The value specified for the indicated parameter was zero or a negative number. This value must be positive number.
Action

Supply a positive number for the indicated parameter.
BROKER_NOT_CONNECTED_GENERAL Unable to publish Document: {0}. Broker not connected.
Class
UNABLE_TO_CREATE_TRIGGER_EX Unable to create trigger "{0}": {1}
Class
UNABLE_TO_CREATE_TRIGGER_INVALID_NAME Unable to create trigger "{0}". Invalid Trigger Name.
Class
UNABLE_TO_CREATE_TRIGGER_INVALID_NSNAME Unable to create trigger "{0}". Invalid NSName.
Class
UNABLE_TO_CREATE_TRIGGER_INVALID_PACKAGE Unable to create trigger "{0}". Package "{1}" does not exist.
Class
UNABLE_TO_CREATE_TRIGGER_INSUFFICIENT_PERMISSION Unable to create trigger "{0}": Insufficient Write ACL privileges.
Class
UNABLE_TO_CREATE_DUP_TRIGGER Unable to create trigger "{0}". A trigger with this name already exists.
Class
NUMBER_MUST_BE_GT_0_OR_EQ_NEG1 {0} must me greater than 0 or -1.
Class
NUMBER_MUST_BE_GT_OR_EQ_0 {0} must me greater than or equal to 0.
Class
SUSPECT_NEED_TO_SYNC_DOC_TO_BROKER Unable to publish to the broker the Document: {0}. Sync the document with the broker.
Class
UM_MIGRATE_NOT_MIGRATABLE_FILTER Filter cannot be migrated to UM Povider Filter, it uses an unsupported construct:{0}.
Class W
Explanation

The contents of the Filter field could not be migrated to the Provider Filter (UM) field because the filter contains the specified unsupported constructs. At run time, the unsupported constructs replace {0}, {1}, and {2}.

Action

No action is required. The contents of the Filter field will not change. The trigger will apply the filter to any messages that it receives. Note that while Broker might have applied portions of the filter to received messages before routing the message to the trigger, once the trigger and it’s document types have been updated to work with Universal Messaging, the contents of the Filter field become a local filter only. If you want the filter to become a provider filter applied by Universal Messaging, you must specify a filter in the Provider Filter (UM) field.

UM_MIGRATE_NOT_MIGRATABLE_FILTER_DUPLICATE_FIELDNAME Filter cannot be completely migrated to Provider Filter (UM). Contains duplicate field name:{0}.
Class W
Explanation

The contents of Filter could not be migrated to Provider Filter (UM) because the filter contains the specified duplicate field name. Universal Messaging cannot filter on duplicate field names because duplicate field names cannot be encoded as protocol buffers.

Action

No action is required. The contents of the Filter field will not change. The trigger will apply the filter to any messages that it receives. Note that while Broker might have applied portions of the filter to received messages before routing the message to the trigger, once the trigger and it’s document types have been updated to work with Universal Messaging, the contents of the Filter field become a local filter only. If you want the filter to become a provider filter applied by Universal Messaging, you must specify a filter in the Provider Filter (UM) field.

UM_MIGRATE_NOT_MIGRATABLE_FILTER_INVALID_FIELDNAME Filter cannot be completely migrated to Provider Filter (UM). Contains field with an invalid name:{0}.
Class W
Explanation

The contents of Filter could not be migrated to Provider Filter (UM) because the filter contains a name considered to be invalid by Universal Messaging or a field name that cannot be encoded as protocol buffers.

Action

No action is required. The contents of the Filter field will not change. The trigger will apply the filter to any messages that it receives. Note that while Broker might have applied portions of the filter to received messages before routing the message to the trigger, once the trigger and it’s document types have been updated to work with Universal Messaging, the contents of the Filter field become a local filter only. If you want the filter to become a provider filter applied by Universal Messaging, you must specify a filter in the Provider Filter (UM) field.

UM_MIGRATE_NOT_MIGRATABLE_FILTER_INVALID_FIELDTYPE Filter cannot be completely migrated to Provider Filter (UM). Contains an Object or Object List field:{0}.
Class W
Explanation

The contents of Filter could not be migrated to Provider Filter (UM) because the filter contains a field of type Objects and Object Lists which is defined to be an unknown Java wrapper type. Object and Object Lists defined to be an unknown Java wrapper type cannot be encoded with protocol buffers.

Action

No action is required. The contents of the Filter field will not change. The trigger will apply the filter to any messages that it receives. Note that while Broker might have applied portions of the filter to received messages before routing the message to the trigger, once the trigger and it’s document types have been updated to work with Universal Messaging, the contents of the Filter field become a local filter only. If you want the filter to become a provider filter applied by Universal Messaging, you must specify a filter in the Provider Filter (UM) field.

UM_MIGRATE_NOT_MIGRATABLE_FILTER_INVALID_AND Filter cannot be completely migrated to Provider Filter (UM). Contains an invalid AND condition:{0} - {1}.
Class W
Explanation

The contents of Filter could not be migrated to Provider Filter (UM) because the filter contains an AND condition that specifies a null value. Because a null value cannot be included in a protocol buffer message, a filter that checks for a null value is invalid.

Action

No action is required. The contents of the Filter field will not change. The trigger will apply the filter to any messages that it receives. Note that while Broker might have applied portions of the filter to received messages before routing the message to the trigger, once the trigger and it’s document types have been updated to work with Universal Messaging, the contents of the Filter field become a local filter only. If you want the filter to become a provider filter applied by Universal Messaging, you must specify a filter in the Provider Filter (UM) field.

UM_MIGRATE_NOT_MIGRATABLE_FILTER_INVALID_FUNCTION Filter cannot be completely migrated to Provider Filter (UM). Contains an invalid FUNCTION.
Class W
Explanation

The contents of Filter could not be migrated to Provider Filter (UM) because the filter contains an invalid FUNCTION.

Action

No action is required. The contents of the Filter field will not change. The trigger will apply the filter to any messages that it receives. Note that while Broker might have applied portions of the filter to received messages before routing the message to the trigger, once the trigger and it’s document types have been updated to work with Universal Messaging, the contents of the Filter field become a local filter only. If you want the filter to become a provider filter applied by Universal Messaging, you must specify a filter in the Provider Filter (UM) field.

UM_MIGRATE_NOT_MIGRATABLE_FILTER_INVALID_COMPARATOR Filter cannot be completely migrated to Provider Filter (UM). Contains an invalid comparator value:{0} - {1}.
Class W
Explanation

The contents of Filter could not be migrated to Provider Filter (UM) because the filter contains a comparison considered invalid by Universal Messaging or protocol buffers. At run time, the {0} in the message is replaced the contents of the left side of the expression and {1} is replaced by the contents of the right side of the expression.

Action

No action is required. The contents of the Filter field will not change. The trigger will apply the filter to any messages that it receives. Note that while Broker might have applied portions of the filter to received messages before routing the message to the trigger, once the trigger and it’s document types have been updated to work with Universal Messaging, the contents of the Filter field become a local filter only. If you want the filter to become a provider filter applied by Universal Messaging, you must specify a filter in the Provider Filter (UM) field.

UM_MIGRATE_NOT_MIGRATABLE_FILTER_NULL_COMPARATOR Filter cannot be completely migrated to Provider Filter (UM). Contains a NULL comparator value:{0} - {1}.
Class W
Explanation

The contents of Filter could not be migrated to Provider Filter (UM) because the filter compares a field to a NULL value. Because a null value cannot be included in a protocol buffer message, a filter that checks for a null value is invalid.

Action

No action is required. The contents of the Filter field will not change. The trigger will apply the filter to any messages that it receives. Note that while Broker might have applied portions of the filter to received messages before routing the message to the trigger, once the trigger and it’s document types have been updated to work with Universal Messaging, the contents of the Filter field become a local filter only. If you want the filter to become a provider filter applied by Universal Messaging, you must specify a filter in the Provider Filter (UM) field.

UM_MIGRATE_NOT_MIGRATABLE_FILTER_REGEX Filter cannot be completely migrated to Provider Filter (UM). Contains a REGEX value:{0} {1}.
Class W
Explanation

The contents of Filter could not be migrated to Provider Filter (UM) because the filter contains a regular expression. Universal Messaging filtering syntax does not support the use of regular expressions.

Action

No action is required. The contents of the Filter field will not change. The trigger will apply the filter to any messages that it receives. Note that while Broker might have applied portions of the filter to received messages before routing the message to the trigger, once the trigger and it’s document types have been updated to work with Universal Messaging, the contents of the Filter field become a local filter only. If you want the filter to become a provider filter applied by Universal Messaging, you must specify a filter in the Provider Filter (UM) field.

UM_MIGRATE_NOT_MIGRATABLE_FILTER_INVALID_BOOLEAN_VALUE Filter cannot be completely migrated to Provider Filter (UM). Contains an invalid Boolean value:{0}.
Class W
Explanation

The contents of Filter could not be migrated to Provider Filter (UM) because the filter contains an invalid value for a field or type Boolean.

Action

No action is required. The contents of the Filter field will not change. The trigger will apply the filter to any messages that it receives. Note that while Broker might have applied portions of the filter to received messages before routing the message to the trigger, once the trigger and it’s document types have been updated to work with Universal Messaging, the contents of the Filter field become a local filter only. If you want the filter to become a provider filter applied by Universal Messaging, you must specify a filter in the Provider Filter (UM) field.

UM_MIGRATE_NOT_MIGRATABLE_FILTER_INVALID_OR Filter cannot be completely migrated to Provider Filter (UM). Contains an invalid OR condition:{0} - {1}.
Class W
Explanation

The contents of Filter could not be migrated to Provider Filter (UM) because the filter contains an OR condition that specifies a null value. Because a null value cannot be included in a protocol buffer message, a filter that checks for a null value is invalid. At run time, the {0} in the message is replaced the contents of the left side of the expression and {1} is replaced by the contents of the right side of the expression.

Action

No action is required. The contents of the Filter field will not change. The trigger will apply the filter to any messages that it receives. Note that while Broker might have applied portions of the filter to received messages before routing the message to the trigger, once the trigger and it’s document types have been updated to work with Universal Messaging, the contents of the Filter field become a local filter only. If you want the filter to become a provider filter applied by Universal Messaging, you must specify a filter in the Provider Filter (UM) field.

UM_MIGRATE_NOT_MIGRATABLE_FILTER_INVALID_NOT Filter cannot be completely migrated to Provider Filter (UM). Contains an invalid NOT condition:{0}.
Class W
Explanation

The contents of Filter could not be migrated to Provider Filter (UM) because the filter contains an invalid value in a NOT condition.

Action

No action is required. The contents of the Filter field will not change. The trigger will apply the filter to any messages that it receives. Note that while Broker might have applied portions of the filter to received messages before routing the message to the trigger, once the trigger and it’s document types have been updated to work with Universal Messaging, the contents of the Filter field become a local filter only. If you want the filter to become a provider filter applied by Universal Messaging, you must specify a filter in the Provider Filter (UM) field.

OPERATION_NOT_SUPPORTED_WITH_LOCAL_ALIAS {0} operation is not supported when connection alias type is Local.
Class E
Explanation

The documentTypeName input parameter specifies a publishable document type that uses the IS_LOCAL_CONNECTION alias. Instances of publishable document types that use the IS_LOCAL_CONNECTION messaging connection alias cannot be delivered.

Action

Change the documentTypeName input parameter value to be a publishable document type associated with a Universal Messaging connection alias or a Broker connection alias and then re-execute the service. If you want to publish a document locally, use the pub.publish:publish service or the pub.publish:publishAndWait service.

INVALID_UM_TRIGGER_FILTER_MISMATCH Cannot specify different provider filters for document type ''{0}'' within a single UM trigger
Class E
Explanation

If a webMethods messaging trigger that receives messages from Universal Messaging specifies the same publishable document type in more than one condition, the conditions must specify the same provider filter. That is, the contents of the Provide Filter (UM) column must be the same for each condition that subscribes to the same publishable document type.

Action

Revise the contents of the Provider Filter (UM) column to be the same for each condition that subscribes to the same publishable document type.

99.1 Broker Transport:{0} unable to subscribe to Broker Document {1}. Exception {2}
Class U
Explanation

The Integration Server failed to create the subscription for the trigger on the Broker. The Broker may be unavailable.
Action

In the Broker Administrator, check the status of the Broker and the network connection. If all are correct, then this is an internal error. Contact Software AG Global Support.

99.2 Broker Transport:{0} unable to unsubscribe to Broker Document {1}. Exception {2}
Class U
Explanation

The Integration Server failed to cancel the subscription for the trigger from the Broker after removing the trigger from the Integration Server. The Broker might be unavailable.

Action

In the Broker Administrator, check the status of the Broker and the network connection. If all are correct, then this is an internal error. Contact Software AG Global Support.

99.3 Unable to create Broker Transport {0}. Exception {1}
Class U
Explanation

The Integration Server failed to create the Broker transport for the Broker client because the client could not reconnect to the Broker. The Broker might be temporarily unavailable.

Action

In the Broker Administrator, check the status of the Broker and the network connection. If all are correct, then this is an internal error. Contact Software AG Global Support.

99.5 Creating subscription on Broker without invalid filter: {0}
Class E
Explanation

A trigger contains an invalid filter. The subscription was created on the Broker without the invalid filter.
Action

Change the filter in the trigger to a valid trigger.
99.6 Unable to disconnect Broker Transport. Exception: {0}
Class U
Explanation

Integration Server failed to disconnect from the Broker during shutdown. This indicates an internal error.
Action

Contact Software AG Global Support.
99.7 BrokerTransport:{0} got Exception: {1}
Class U
Explanation

The Integration Server encountered an internal error.
Action

Contact Software AG Global Support.
99.8 Insufficient memory while retrieving events for BrokerTransport:{0}
Class U
Explanation

The Integration Server does not have sufficient memory to retrieve even one document from the Broker.
Action

From the Broker, check the size of the document. Consider increasing the heap size of the JVM used by Integration Server.

99.9 Unable to retrieve events from the Broker for BrokerTransport:{0}. Insufficient JVM memory. Please check Heap size/ size of Documents on the Broker.
Class U
Explanation

The Integration Server does not have sufficient memory to retrieve documents from the Broker.
Action

From the Broker, check the size of the documents. Consider increasing the heap size of the JVM used by Integration Server.
99.10 Broker Transport:{0} failed to unsubscribe to all Broker Documents. Exception {1}
Class U
Explanation

The Integration Server failed to cancel the subscriptions from the Broker while removing the trigger from the Integration Server. The Broker might be unavailable.

Action

In the Broker Administrator, check the status of the Broker and the network connection. If all are correct, then this is an internal error. Contact Software AG Global Support.

99.11 Broker Transport Factory unable to retrieve password for handle {0}
Class E
Explanation

An internal error occurred.
Action

Contact Software AG Global Support.
99.12 {0} failed to retrieve password for handle {1}. Exception {2}
Class E
Explanation

An internal error occurred.
Action

Contact Software AG Global Support.
99.13 {0} failed to save password for handle {1}. Exception {2}
Class E
Explanation

An internal error occurred.
Action

Contact Software AG Global Support.
99.14 {0} failed to refresh broker settings. Exception type {1}, msg {2}
Class E
Explanation

An error occurred while saving broker settings to disk.
Action

Read through the details provided in the exception and take corrective steps. If you are not able to resolve the problem, contact Software AG Global Support.

99.15 BrokerTransport : Broker Timing out repetitively. New subscriptions won't get created and if subscriptions are already existing,this might lead to the client queue growing on the broker
Class E
Explanation

An attempt to create a new subscription has timed out multiple times.
Action

Contact Software AG Global Support.
100.36 {0} getReader() has already been called for this request
Class E
Explanation

A servlet or JSP called the ServletRequest.getInputStream() method after it had already called the ServletRequest.getReader() method. The servlet or JSP can call one method or the other, not both.

Action

Check the servlet or JSP and ensure that only one of these methods is called.
TAG_NOT_ENCLOSED The {0} action is not enclosed by a {1} action.
Class U
Explanation

Integration Server was not able to execute a Web application because there are syntax errors in the JSP file.
Action

Examine the error message to determine which tag name caused the exception to be thrown. Then check the JSP file that contains the tags and look for syntax errors. See the "Web Applications Developer’s Guide" for the correct usage. After you fix the problem, re-deploy the Web application on Integration Server.

TAG_NOT_ENCLOSED_PARENT The {0} action is not enclosed by a {1} action at {2}.
Class U
Explanation

Integration Server was not able to execute a web application because there was a syntax error in the <webm:ifvar> and <webm:else> tags in the JSP file.

Action

Examine the JSP file that contains the <webm:ifvar> and <webm:else> tags. See the "webMethods Applications Developer's Guide" for the correct usage of these tags. After you fix the problem, re-deploy the Web application on Integration Server.

105.3 Cannot get canonicalKey: {0}
Class E
Explanation

The pub.synchronization.xref:getCanonicalKey service failed to execute because an exception was thrown when Integration Server tried to retrieve the corresponding canonical key for the specified native ID from the repository.

Action

Examine the exception message and stack trace for details. Verify that you have provided correct input for the "appID", "nativeID", and "objectID" parameters. If you cannot find the cause for the problem, contact Software AG Global Support.

105.5 Cannot insert into database this record, appId="{0}", nativeId="{1}", canonicalKey="{2}", objId="{3}", error: {4}
Class E
Explanation

The pub.synchronization.xref:createXReference service or pub.synchronization.xref:insertXReference service failed to execute because an exception was thrown when Integration Server tried to insert or create the cross-reference record in the repository.

Action

Examine the error stack trace to determine which exception was thrown. If it was a SQLException, check the webMethods Integration Server documentation to make sure that you have set up your JDBC Pool configurations correctly. If you cannot determine the cause of the problem, contact Software AG Global Support.

105.6 Cannot close latch: {0}
Class E
Explanation

The "pub.synchronization.latch:closeLatch" service failed to execute because an exception was thrown when Integration Server tried to close the latch for a given application ID, canonical Key, and object ID.

Action

Examine the error stack trace to determine which exception was thrown. If it was a SQLException, check the webMethods Integration Server documentation to make sure you have set up your JDBC Pool configurations correctly. If you cannot determine the cause of the problem, contact Software AG Global Support.

105.7 Cannot open latch: {0}
Class E
Explanation

The "pub.synchronization.latch:closeLatch" service failed to execute because an exception was thrown when the Integration Server tried to open the latch for a given application ID, canonical Key, and object ID.

Action

Examine the error stack trace to determine which exception was thrown. If it was a SQLException, check "Installing webMethods Products" to make sure you have set up your JDBC Pool correctly.If you cannot determine the cause of the problem, contact Software AG Global Support.

105.8 Cannot get nativeId: {0}
Class E
Explanation

The "pub.synchronization.xref:getNativeId" service failed to execute because an exception was thrown when the Integration Server tried to retrieve the native ID for a given canonical key, application ID, and object ID.

Action

Examine the error stack trace to determine which exception was thrown. If it was a SQLException, check "Installing webMethods Products" to make sure you have set up your JDBC Pool configurations correctly. If you cannot determine the cause of the problem, contact Software AG Global Support.

105.9 Cannot obtain a JDBC connection: {0}
Class E
Explanation

The Integration Server was not able to obtain a connection to the JDBC database where cross-reference keys and echo suppression status are stored. A likely cause is that the pool alias for this database was specified incorrectly on the Settings>JDBC Pools page of the Server Administrator.

Action

From the Settings>JDBC Pools page of the Server Administrator, examine the pool alias properties for the Xref and make sure it specifies the correct Database URL, User Id, Password, and Database driver. Then, restart the Integration Server.

105.10 No JDBC connection available
Class E
Explanation

The Integration Server was not able to obtain a connection to the JDBC database where the cross-reference keys and echo suppression status are stored. A likely cause is that no JDBC pool connections are available.

Action

From the Settings > JDBC Pools page of the Integration Server Administrator, examine the pool alias properties for the Xref and consider increasing the number of connections. Then, restart Integration Server.

105.11 Release JDBC connection error: {0}
Class E
Explanation

Integration Server tried to perform a database operation, but the "pub.synchronization*" service failed to release its connection to the database. This indicates an internal error.

Action

Contact Software AG Global Support.
105.12 Get preparedStatement error: {0}
Class E
Explanation

While trying to perform a database operation, a "pub.synchronization*" service encountered an SQLException.
Action

Examine the error stack trace to determine which SQL exception was thrown. Make sure you followed the instructions in the "webMethods Integration Server documentation and set up the Database correctly. If you cannot determine the cause of the error, contact the database vendor.

105.13 Check isLatchClosed error: {0}
Class E
Explanation

The pub.synchronization.latch:isLatchClosed service threw an exception when it tried to check the latch status for a given canonical key, application ID, and object ID.

Action

Examine the error stack trace to determine which exception was thrown. If it was a SQLException, check "Installing webMethods Products" to make sure you have set up your JDBC Pool correctly. If you cannot determine the cause of the problem, contact Software AG Global Support.

105.14 Drop all records with objId="{0}", error: {1}
Class E
Explanation

The "pub.synchronization.xref:deleteByObjectId" service threw an exception when it tried to remove all cross-reference records associated with a particular process or synchronization.

Action

Examine the error stack trace to determine which exception was thrown. If it was a SQLException, check the webMethods Integration Server documentation to make sure that you have set up your JDBC Pool configurations correctly. If you cannot determine the cause of the problem, contact Software AG Global Support.

105.24 Delete xref record: appId="{0}", canonicalKey="{1}", objId="{2}", error: {3}
Class E
Explanation

The pub.synchronization.xref:deleteXReference service threw an exception when it tried to remove all cross-reference records associated with a particular process or synchronization.

Action

Examine the error stack trace to determine which exception was thrown. If it was a SQLException, check the webMethods Integration Server documentation to make sure that you have set up your JDBC Pool configurations correctly. If you cannot determine the cause of the problem, contact Software AG Global Support.

12.29 The certificate in the SAML assertion signature does not match the certificate on file for the issuer; Rejecting SAML assertion.
Class E
Explanation

The certificate in the SAML assertion signature does not match the certificate on file for the issuer.
Action

Check the issuer configuration on Security -> SAML screen and make sure that the identified truststore contains the correct certificate for the issuer.

125.15 The trigger input control parameters, watt.server.control.triggerInputControl.delaysIncrementInterval and watt.server.control.triggerInputControl.delays, were set to their default values because an exception occurred when parsing the supplied values.
Class W
Explanation

Integration Server could not set the trigger input control configuration parameter watt.server.control.triggerInputControl.delaysIncrementInterval and/or watt.server.control.triggerInputControl.delays to the new value because an exception occurred when parsing a new value for one of the parameters. Integration Server reset both configuration parameters to the default values.

Action

Use a valid value for the watt.server.control.triggerInputControl.delaysIncrementInterval or watt.server.control.triggerInputControl.delays parameter.

128.1 Unable to get JDBC connection. Exception:{0}
Class E
Explanation

Integration Server was unable to connect to the database defined by the DocumentHistory functional alias. This alias defines the database that the Integration Server uses to detect duplicate documents.

Action

From the Settings>JDBC Pools> page of the Integration Server Administrator, make sure that a Functional Alias called DocumentHistory exists and is associated with a valid Pool Alias. Click the Test button. If the alias exists, but there are errors when you hit the Test button, then there is a problem with the connection. Review the Journal log for messages about the operation being performed. If the problem persists, contact your Database Administrator.

128.2 Exception while {1}: {0}
Class E
Explanation

An exception occurred when Integration Server tried to perform a task using the In Doubt Resolver component.
Action

From the Settings>JDBC Pools> page of the Integration Server Administrator, make sure that a Functional Alias called DocumentHistory exists and is associated with a valid Pool Alias. Click the Test button. If the alias exists, but there are errors when you hit the Test button, then there is a problem with the connection. If the problem persists, contact your Database Administrator.

128.3 SQLException:{0} while {1}
Class E
Explanation

An exception occurred when Integration Server tried to perform a SQL operation using the JDBC connection pool for the functional alias DocumentHistory.

Action

From the Settings>JDBC Pools> page of the Integration Server Administrator, make sure that a Functional Alias called DocumentHistory exists and is associated with a valid Pool Alias. Click the Test button. If the alias exists, but there are errors when you hit the Test button, then there is a problem with the connection. Review the Journal log for messages about the operation being performed. If the problem persists, contact your Database Administrator.

128.4 Exception while loading the Decision Tree: {0}
Class E
Explanation

An exception occurred when Integration Server tried to create the decision tree for resolving duplicate documents. The decision is based on multiple criteria, but Integration Server was not able to load these criteria into memory.

Action

Contact webMethods Customer Care. Be prepared to provide logs and the version number and patch level for Integration Server and your operating system.

128.5 Exception:{0} while resolving Document of type: {1} and Id: {2} for trigger: {3}. Document is being deemed as In Doubt.
Class E
Explanation

An exception occurred when Integration Server tried to resolve a document it received. The exception might be due to a problem with the database connection for the alias DocumentHistory or with the Resolver Service associated with the trigger.

Action

Examine the Server log for error messages that indicate the cause of the problem. If the error was a database/SQL exception, check to see if the functional alias DocumentHistory is working properly. If a problem occurred with the Resolver Service, verify that the service is properly coded.

128.6 Trigger: {0} encountered exception while executing resolver service: {1}. Exception: {2}
Class E
Explanation

Integration Server received a document, but the document resolver service associated with the trigger encountered an exception.
Action

Check the Error log to see if the Document Resolver Service associated with the trigger has logged any error messages. If no messages have been logged, change the auditing properties for the service to enable the Log on Error property. In addition, because this is a user-written service, check it to make sure it has been coded properly.

128.7 In Doubt document of type:{0} with Id:{1} received for trigger:{2}. Document is being Audit Logged.
Class E
Explanation

Integration Server received a document, but the document resolver service associated with the rrigger could not resolve the document and therefore considers it to be "In Doubt".

Action

Check the document's id to see if it is a duplicate. If there is an document resolver service associated with the trigger, determine why the service was not able to resolve the document. Integration Server records occurrences of In Doubt Documents in the Audit log. You can view In Doubt documents through WmMonitor.

128.8 Unable to Audit Log document of type:{0} with id:{1} as it can't be decoded. Exception:{2}.
Class E
Explanation

An error occurred when Integration Server tried to resolve a document. As part of the resolution process, a document first goes to the In Doubt Resolver component. If that component successfully resolves the document, Integration Server decodes the document and sends it to the trigger. However, if the In Doubt Resolver cannot resolve the document, the Integration Server decodes the document and sends it to the In Doubt Resolver service associated with the trigger. This error is issued if there is an error when decoding the document before sending it to the In Doubt Resolver service associated with the trigger.

Action

Make sure the document type on Integration Server matches the associated Broker document type on the Broker. Re-sync the document types by pushing the IS document type to the Broker ("Push to Broker"). If all the document type fields and data types match and the problem still persists, contact webMethods Customer Care.

128.9 Unable to get JDBC Connection to the database.
Class E
Explanation

As part of storing history for the document being processed, the Integration Server's In Doubt Resolver component add/deletes rows to a database. While performing one of these actions, the connection to the database was lost.

Action

From the Settings>JDBC Pools> page of the Integration Server Administrator, make sure that a functional alias called DocumentHistory exists and is associated with a valid Pool Alias. Click the Test button. If the alias exists, but there are errors when you hit the Test button, then there is a problem with the connection. If the problem persists, contact your Database Administrator. Review the Journal log for messages about the operation being performed. If the problem persists, contact your Database Administrator.

128.10 Detected expired UUID:{0} for trigger:{1}. Deleting all expired UUIDs.
Class
128.11 Unable to resolve processing state for UUID:{0} for trigger:{1}. Exception:{2}
Class
128.12 Unable to mark UUID:{0} for trigger:{1} as complete in the database. A non-expired UUID already exists.
Class
128.14 Unable to insert UUID:{0}. Exception:{1}
Class E
Explanation

As part of storing history for the document or message being processed, Integration Server's In Doubt Resolver component stores the UUID (universally unique ID) of the document (message) in a database. An exception occurred during this process.

Action

From the Settings>JDBC Pools> page of the Integration Server Administrator, make sure that a Functional Alias called DocumentHistory exists and is associated with a valid Pool Alias. Click the Test button. If the alias exists, but there are errors when you hit the Test button, then there is a problem with the connection. If the problem persists, contact your Database Administrator.

128.15 Document history initialization failed. Please verify database connection is available.Exception {0}.
Class E
Explanation

No valid JDBC connection Pool is available for the In Doubt Resolver Alias "DocumentHistory". Detection of duplicate documents depends on the availability of a database where document history is defined.

Action

From the Settings>JDBC Pools> page of the Integration Server Administrator, make sure that a Functional Alias called DocumentHistory exists and is associated with a valid Pool Alias. Click the Test button. If the alias exists, but there are errors when you hit the Test button, then there is a problem with the connection. If the problem persists, contact your Database Administrator.

NO_CONNECTION Unable to get Connection
Class E
Explanation

No valid JDBC connection Pool is available for the In Doubt Resolver Alias "DocumentHistory".
Action

From the Settings>JDBC Pools> page of the Integration Server Administrator, make sure that a Functional Alias called DocumentHistory exists and is associated with a valid Pool Alias. Click the Test button. If the alias exists, but there are errors when you hit the test button, then there is a problem with the connection. Review the Journal log for messages about the operation being performed. If the problem persists, contact your Database Administrator.

INVALID_ARGUEMENT Invalid argument supplied for:{0}
Class E
Explanation

Integration Server stores document history information in a database so that it can detect when duplicate documents are received. This error occurs when a process tries to insert an entry that specifies an invalid argument into the database.

Action

Check to see if the name of the trigger and the UUID of the document satisfy the constraints specified on the columns of the Table WM_IDR_MSG_HST in your database. This error can occur if the Trigger Name or UUID exceeds the column length of the database column.

EXCEPTION_EXECUTING_SERVICE Exception while executing in doubt resolver service:{0}
Class E
Explanation

Integration Server received a document, but an exception occurred during execution of the document resolver service associated with the trigger.

Action

Check the Integration Serverse error log to see if the document resolver service has logged any error messages. If no errors were logged, configure the document resolver service's auditing properties to Log on Error. In addition, verify that the document resolver service has been coded properly.

NO_JDBC_POOL The DocumentHistory functional alias is not configured properly on the JDBC Pools page. Assign a valid database pool and restart the Integration Server.
Class E
Explanation

Integration Server stores document history information in a Document History database so that it can detect when duplicate documents are received. Integration Server throws this exception whenever it does not find a JDBC Pool for the Document History functional alias.

Action

Configure a JDBC Pool for Document History functional alias.
FAC_DOM+"."+INDEX_SIZE_ERR Index size error. Details:{0}
Class E
Explanation

Integration Server has detected that all threads allocated to the diagnostic thread pool are in use.
Action

Wait for one or more of these threads to finish. If this problem persists, contact Software AG Global Support.
FAC_DOM+"."+DOMSTRING_SIZE_ERR DOMString size error. Details:{0}
Class
FAC_DOM+"."+HIERARCHY_REQUEST_ERR Hierarchy request error. Details:{0}
Class
FAC_DOM+"."+WRONG_DOCUMENT_ERR Wrong document error. Details:{0}
Class
FAC_DOM+"."+INVALID_CHARACTER_ERR Invalid character error. Details:{0}
Class
FAC_DOM+"."+NO_DATA_ALLOWED_ERR No data allowed error. Details:{0}
Class
FAC_DOM+"."+NO_MODIFICATION_ALLOWED_ERR No modification allowed error. Details:{0}
Class
FAC_DOM+"."+NOT_FOUND_ERR Not found error. Details:{0}
Class
FAC_DOM+"."+NOT_SUPPORTED_ERR Not supported error. Details:{0}
Class
FAC_DOM+"."+INUSE_ATTRIBUTE_ERR Inuse attribute error. Details:{0}
Class
FAC_DOM+"."+INVALID_STATE_ERR Invalid state error. Details:{0}
Class
FAC_DOM+"."+INVALID_MODIFICATION_ERR Invalid modification error. Details:{0}
Class
FAC_DOM+"."+INVALID_ACCESS_ERR Invalid access error. Details:{0}
Class
FAC_DOM+"."+TYPE_MISMATCH_ERR Type mismatch error. Details:{0}
Class
FAC_DOM+"."+SETNULL Cannot set attribute name or value to null
Class
FAC_DOM+"."+GETNULL Cannot get null attribute
Class
FAC+"."+UNABLE_TO_SET_THREAD_MAX JMS Runtime Configuration Internal Error. Unable to set thread pool max: {0}
Class
FAC+"."+ERROR_LOADING_JMS_CONFIG An error occurred while loading JMS configuration file: {0}
Class
FAC+"."+ERROR_STARTING_CONNECTION_ALIAS Unable to start JMS connection alias {0}: {1}
Class
FAC+"."+ERROR_STARTING_CONNECTION_ALIAS_DISABLING Unable to start JMS connection alias {0}. The alias is now disabled: {1}
Class E
Explanation

The specified JMS connection alias could not be started because it is disabled. Only enabled JMS connection aliases can be started.

Action

Enable the JMS connection alias.
FAC+"."+JNDI_NOT_FOUND JNDI Propery "{0}" not found. Setting JMS connection alias {1} to disabled.
Class
FAC+"."+JMS_CONFIG_FILE_NOT_FOUND JMS configuration file not found: {0}
Class
FAC+"."+JMS_NOT_CONFIGURED JMS subsystem is not configured. The default JMS connection alias is being created.
Class
FAC+"."+UNABLE_TO_LOAD_JMS_CONFIG Unable to load JMS configuration file "{0}": {1}
Class
FAC+"."+UNABLE_TO_LOAD_JMS_CONFIG_FNF Unable to load JMS configuration file "{0}": File not found.
Class
FAC+"."+NO_DATA_IN_JMS_CONFIG "jms.cnf" file contains no configuration data.
Class
FAC+"."+UNABLE_TO_LOAD_ALIAS_CONFIG Unable to load configuration for JMS connection alias {0}: {1}
Class
FAC+"."+JMS_CONNECTION_ERROR JMS Connection Error on connection "{0}": {1}
Class
FAC+"."+UNABLE_TO_DESTROY_CSQ Unable to destroy CSQ for connection "{0}": {1}
Class
FAC+"."+UNABLE_TO_PING_JNDI Unable to ping JNDI provider "{0}": {1}
Class
FAC+"."+UNABLE_TO_START_CSQ_FACTORY Unable to start CSQ Factory. The CSQ feature will not be functional for any JMS connection aliases: {0}
Class
FAC+"."+ERROR_PINGING_JMS Exception occured while pinging JMS provider "{0}": {1}
Class
FAC+"."+ERROR_DELISTING_RESOURCE Error delisting resource from transaction: {0}
Class
FAC+"."+ERROR_CLOSING_JMS_SESSION Error closing JMSSession: {0}
Class
FAC+"."+ERROR_SHUTTING_DOWN_CSQ_FAC Error shutting down CSQ Factory: {0}
Class
FAC+"."+CSQ_UNABLE_TO_RETRIEVE_PRODUCER CSQ Dispatcher "{0}" unable to retrieve producer. CSQ Dispatcher is now stopping: {1}
Class
FAC+"."+CSQ_DISPATCHER_FAILURE CSQ Dispatcher "{0}" is stopping because of exception: {1}
Class
FAC+"."+CSQ_UNABLE_TO_SEND_AFTER_RETRY CSQ Dispatcher "{0}" was unable to send message to "{1}" after {2} retries: {3}
Class
FAC+"."+CSQ_UNABLE_TO_SEND CSQ Dispatcher "{0}" was unable to send message to "{1}": {2}
Class
FAC+"."+CSQ_OOM_DURING_ACK Out of memory error while acking message from CSQ "{0}". Attempting two retries
Class
FAC+"."+CSQ_UNABLE_TO_ACK CSQ Dispatcher "{0}" was unable to acknowledge message: {1}
Class
FAC+"."+CSQ_OOM_DURING_SEND Out of memory error while sending message from CSQ. Attempting two retries
Class
FAC+"."+METADATA_NOT_FOUND No metadata found for JMS connection alias {0}
Class
FAC+"."+METADATA_NOT_FOUND_EX No metadata found for JMS connection alias {0}: {1}
Class
FAC+"."+UNSUPPORTED_PROVIDER The JMS provider and version associated with JMS connection alias {0} is not officially supported.
Class
FAC+"."+CONSUMER_ILLEGAL_STATE_EX IllegalStateException occured in Consumer {0}: {1}
Class
FAC+"."+CONSUMER_OUT_OF_MEMORY OutOfMemoryError occured in Consumer {0}
Class
FAC+"."+PREPROCESSING_FAILURE JMS Trigger {0} failed preprocessing: {1}
Class
FAC+"."+PROCESSING_FAILURE JMS Trigger {0} failed: {1}
Class
FAC+"."+POSTPROCESSING_FAILURE JMS Trigger {0} failed post-processing: {1}
Class
FAC+"."+UNABLE_TO_SETUP_JMS_REPLYTO_CONTEXT JMS trigger {0} was unable to set JMS Reply To Context: {1}
Class
FAC+"."+ACKNOWLEDGED_MESSAGES JMS Trigger {0} has acknowledged the message(s).
Class I
Explanation

The specified JMS trigger has acknowledged the message(s) to the JMS provider.
Action

No action required.
FAC+"."+RECOVERED_MESSAGES JMS Trigger {0} has recovered the message(s).
Class
FAC+"."+CREATED_JMS_TRIGGER_THREAD_POOL Created JMS Trigger Thread Pool with a maximum of {0} threads.
Class
FAC+"."+UNABLE_TO_START_TRIGGER Unable to start JMS trigger {0}: {1}
Class
FAC+"."+ERROR_CLOSING_CONNECTION_HANDLE Error closing Connection Handle: {0}.
Class
FAC+"."+FORCING_TRIGGER_TO_STOP JMS trigger {0} did not shutdown in the allotted time ({1} seconds). It is now being forced to shutdown.
Class
FAC+"."+TRIGGER_STOPPING_BC_ERROR JMS trigger {0} is shutting down because of exception: {1}
Class
FAC+"."+ERROR_DESTROYING_CONSUMER_CONTEXT Error destroying Consumer Context: {0}.
Class
FAC+"."+UNABLE_TO_FILL_POOL_AFTER_RELEASE Unable to refill Shared Session Pool after release: {0}
Class
FAC+"."+CONTEXT_POOL_SHUTDOWN_TO Consumer Context Pool shutodwn timeout: Freeing up active entries.
Class
FAC+"."+CONTEXT_POOL_RETURNING_UNUSED_OBJ Internal Error: returning unused object to Consumer Context Pool!
Class
FAC+"."+REJECTING_FAILED_TRANSACTION JMS transaction failed with $errorType {0}.
Class
FAC+"."+UNABLE_TO_REGISTER_JMSTRIGGER Unable to register JMS trigger {0}: {1}
Class
FAC+"."+UNABLE_TO_UNREGISTER_JMSTRIGGER Unable to unregister JMS trigger {0}: {1}
Class
FAC+"."+JMS_TRIGGER_STARTED JMS trigger {0} has started
Class
FAC+"."+RESOURCE_MONITOR_SCHEDULED_NEW_TASK JMS Trigger Resource Monitor scheduled new system task.
Class
FAC+"."+RESOURCE_MONITOR_RESUMED_LAST_TRIGGER JMS Trigger Resource Monitor has resumed the last trigger. Its system task will now be canceled.
Class
FAC+"."+RESOURCE_MONITOR_MONITORING_TRIGGER JMS Trigger Resource Monitor is now monitoring the resource availability of trigger {0}.
Class
FAC+"."+RESOURCE_MONITOR_CHECKING_RESOURCE JMS Trigger Resource Monitor invoked service {0}. Status of resource is "{1}".
Class
FAC+"."+RESOURCE_MONITOR_CHECKING_RESOURCE_EXCEPTION JMS Trigger Resource Monitor received an exception while invoking service {0}: {1}
Class
FAC+"."+RESOURCE_MONITOR_RESUMED_TRIGGER JMSTrigger Resource Monitor has resumed trigger {0}.
Class
FAC+"."+RESOURCE_MONITOR_RESUMED_TRIGGER_EXCEPTION JMS Trigger Resource Monitor received an exception while attempting to resume trigger {0}: {1}
Class
FAC+"."+DECODING_NO_DATA No suitable data type was found in the message body so an empty Message is being created.
Class
FAC+"."+CLASS_LOADER_NOT_READY Not starting JMS connection alias {0} because package {1} is not loaded/enabled yet.
Class
FAC+"."+TX_AND_BATCH_MODE_NOT_SUPPORTED Trigger {0} cannot receive messages in a batch while using a transacted connection. The "max batch messages" size will be set to 1.
Class
FAC+"."+HISTORY_DB_UNABLE_TO_ACK Unable to acknowledge InDoubtResolver: {0}
Class
FAC+"."+HISTORY_DB_UNABLE_TO_DELETE Unable to remove InDoubtResolver entry: {0}
Class
FAC+"."+HISTORY_DB_NOT_CONFIGURED Trigger Preprocessing Failure occurred for trigger {0}: {1}. The DocumentHistory JDBC alias may not be configured correctly. The trigger will be automatically suspended. You must restart it manually.
Class
FAC+"."+HISTORY_DB_NOT_AVAILABLE Trigger Preprocessing Failure occurred for trigger {0}: {1}. The trigger will be automatically suspended and IS will monitor the DocumentHistory JDBC resource.
Class
FAC+"."+TRIGGER_EXCEEDED_DELIVERY_COUNT Rejecting incoming message for trigger: {0}, documentID: {1}. Delivery Count has exceeded {2} attempts.
Class
FAC+"."+DECODING_FAILURE JMS Trigger {0} failed decoding: {1}
Class
FAC+"."+CANT_RETRIEVE_PASS Unable to retrieve password from Password Manager with key {0}: {1}
Class
FAC+"."+CANT_SET_PASS Unable to set password in Password Manager with key {0}: {1}
Class
FAC+"."+ERROR_STARTING_CONNECTION_ALIAS_RETRY Unable to start JMS connection alias {0}. The server will attempt to reconnect every {1} seconds: {2}
Class
FAC+"."+CANT_CREATE_PING_DESTINATION Could not create Destination to Ping Connection Alias :{0}.
Class
FAC+"."+CONNECTION_ALIAS_UNABLE_TO_CHECK_FOR_UPDATES JMS connection alias {0} is unable to check the JNDI namespace for updates to the ConnectionFactory "{1}": {2}
Class
FAC+"."+CONNECTION_ALIAS_UPDATING JMS connection alias "{0}" is updating because of changes made to ConnectionFactory "{1}" in the JNDI namespace.
Class
FAC+"."+UNABLE_TO_START_CONNECTION_ALIAS_AFTER_UPDATE Unable to restart JMS connection alias {0} after updating ConnectionFactory {1}: {2}
Class
FAC+"."+UNABLE_TO_REGISTER_JNDI_LISTENER Unable to register event listener. Update functionality not available for this JNDI provider: {0}
Class
FAC+"."+JNDI_LISTENER_FAILED The JNDI event listener for JMS connection alias {0} has been disconnected. The system will try to reconnect.
Class
FAC+"."+POLLING_INTERVAL_RETRIEVED JMS connection alias {0} is dynamically setting polling interval to {1} milliseconds.
Class
FAC+"."+UNABLE_TO_RETRIEVE_POLLING_INTERVAL_ERROR JMS connection alias {0} is unable to retrieve polling interval, so the default value of {1} minutes will be used instead: {2}
Class
FAC+"."+STARTING_GUARANTEED_MULTISEND_POLICY Starting JMS connection alias with Guaranteed Multisend policy. Broker list = {0}; Multisend Broker count = {1}.
Class
FAC+"."+REFRESHED_CONSUMER_SESSION Refreshed Consumer Context: sessionId={0}, trigger={1}
Class D
Explanation

Integration Server refreshed the session for the specified message consumer.
Action

None.
FAC+"."+DEFAULT_SESSION_POOL_INIT_SUCCESS Initialized default Session pool for alias "{0}"; max size "{1}"
Class D
Explanation

Integration Server created a default Session Pool for the specified JMS connection alias.
Action

No action required.
FAC+"."+MESSAGE_PRODUCER_POOL_INIT_SUCCESS Initialized MessageProducer pool for alias "{0}"; destination "{1}"; max size "{2}"
Class D
Explanation

For the specified JMS connection alias, Integration Server created a MessageProducer Pool for the specified destination.
Action

No action required.
FAC+"."+MESSAGE_PRODUCER_POOL_INIT_FAIL Unable to initialize MessageProducer pool for alias "{0}"; destination "{1}": {2}
Class E
Explanation

An error occurred while initializing the MessageProducer Pool for the specified JMS connection alias and destination. The error most likely occurred because the destination does not exist or cannot be accessed.

Action

Verify that the specified destination exists and that you have sufficient privileges to access the destination. If the JMS connection alias uses a JNDI provider for administered objects, verify that the JNDI provider is available.

FAC+"."+LOG_UNEXPECTED_ERROR JMS subsystem unexpected error: {0}
Class
CANNOT_CREATE_TRIGGER_INVALID_NSNAME Unable to create trigger "{0}". Invalid or non-ascii characters in NSName.
Class E
Explanation

The WS endpoint trigger could not be created because the Web service endpoint alias name includes characters that are not valid for an element name.

Action

Change the name of the alias so that it does not include any characters that Integration Server considers to be reserved or invalid for element names. Refer to the Designer or webMethods Developer documentation for a list of reserved or invalid characters.

TEMP_QUEUE_UNSUPPORTED_WITH_CSQ The client side queue cannot be used with a send and wait request if the reply destination is a temporary queue.
Class E
Explanation

The useCSQ parameter is set to true and the replyToDestinationName is blank or specifies a temporary queue.
Action

If you want Integration Server to route messages to the client side queue when the JMS provider is not available leave useCSQ set to true and specify a queue that is not temporary. That is, specify values for the destinationNameReplyTo and destinationTypeReplyTo input parameters.

SEND_BATCH_NOT_SUPPORTED_BY_PROVIDER The pub.jms:sendBatch service is not supported with this provider.
Class E
Explanation

The connecationAliasName parameter specifies a JMS connection alias that uses a JMS provider that is not supported with the pub.jms:sendBatch service.

Action

Change the value of the connectionAliasName parameter to specify a JMS connection alias that uses a supported JMS provider.
SEND_BATCH_NOT_SUPPORTED_WITH_MULTISEND The pub.jms:sendBatch service is not supported with connection factories that use the multisend guaranteed or multisend best effort Broker cluster policies.
Class E
Explanation

The connectionAliasName parameter specifies a JMS connection alias that uses a connection factory to which the multisend guaranteed or multisend best effort Broker cluster policy is applied. The pub.jms:sendBatch service cannot be used with connection factories that have these policies.

Action

Change the value of the connectionAliasName parameter to specify a JMS connection alias that does not use a connection factory to which the multisend guaranteed or multisend best effort Broker cluster policy is applied.

NIRVANA_ADMIN_OP_FAILED UM admin operation failed [{0}]: {1}
Class E
Explanation

The specified admin operation could not be completed on Universal Messaging due to the listed error. Integration Server will perform admin operations on Universal Messaging when Designer is being used to manage destinations and durable subscribers on Universal Messaging.

Action

Use the provided error message to determine why the admin operation could not be completed.

NO_PROPERTIES_FOUND No properties found for JNDI alias {0}
Class E
Explanation

Integration Server could not find the JNDI properties file for the specified JNDI provider alias.

Action

Ensure that the properties file associated with the JNDI provider alias exists and is not empty. The JNDI properties file is stored in the following directory: IntegrationServer_directory\instances\instanceName\config\jndi

FAC+"."+UNABLE_TO_LOAD_PROPERTIES_FILE JNDIConfigurationManager was unable to load properties file "{0}": {1}
Class E
Explanation

Integration Server could not load the properties file for the JNDI provider alias.

Action

Ensure that the properties file associated with the JNDI provider alias exists in the following directory: IntegrationServer_directory\instances\instanceName\config\jndi
FILE_DOES_NOT_EXIST JNDI configuration file does not exist: {0}
Class E
Explanation

When deleting the JNDI provider alias, Integration Server encountered an error when attempting to dlete the assoiated properties file as the asssociated JNDI properties file does not exist.

Action

Ensure that the properties file associated with the JNDI provider alias exists in the following directory: IntegrationServer_directory\instances\instanceName\config\jndi

UNABLE_TO_DELETE_FILE Unable to delete JNDI configuration file: {0}
Class E
Explanation

When deleting the JNDI provider alias, Integration Server could not delete the associated JNDI properties file.

Action

Ensure that another user is not currently accessing the properties file for the JNDI provider alias that you are attempting to delete. The JNDI properties files are located in the following directory IntegrationServer_directory\instances\instanceName\config\jndi

FILE_NOT_FOUND Unable to load JNDI Properties. File not found: {0}
Class E
Explanation

Integratio Server cannot load the properties file associated with the JNDI provider alais.

Action

Ensure that a valid properties file exists for the JNDI provider alias in the following directory: IntegrationServer_directory\instances\instanceName\config\jndi
INVALID_PROPERTIES_FILE Unable to load JNDI Properties. Invalid properties file: {0}
Class E
Explanation

Integration Server could not load the properties file for the JNDI provider alias becaues the file is invalid.

Action

Ensure that the properties file associated with the JNDI provider alias exists and is not empty. The JNDI properties file is stored in the following directory: IntegrationServer_directory\instances\instanceName\config\jndi

JournalLogger.FAC_SCHED+"."+SCHED_DB_W_NOPOOL Scheduler: Unable to get pool for ISInternal
Class W
Explanation

Integration Server was unable to get the ISInternal JDBC connection pool.
Action

Configure the ISInternal functional alias (specified on the Settings > JDBC Pools screen in Integration Server Administrator) and assign a valid JDBC connection pool to it.

JournalLogger.FAC_SCHED+"."+SCHED_DB_C_INITFAIL Scheduler: Error initializing scheduler: {0}
Class E
Explanation

Integration Server encountered an error while initilizing the database in which information about scheduled jobs is stored.
Action

Read through the contents of the error logs and take corrective steps. If you are unable to resolve the issue, contact Software AG Global Support.

JournalLogger.FAC_SCHED+"."+SCHED_DB_E_NOCONN Scheduler: Unable to get a connection to the database.
Class E
Explanation

Integration Server was unable to get a connection from the JDBC connection pool.
Action

Use Integration Server Administrator to increase the maximum number of connections available in the JDBC connection pool that is assigned to the ISInternal functional alias.

JournalLogger.FAC_SCHED+"."+SCHED_DB_E_THREAD Scheduler: Resources unavailable: {0}
Class E
Explanation

Scheduler thread throttle, which is the percentage of server threads the scheduler function is permitted to use, is reached. Integration Server cannot execute a scheduled task because there are no threads available.

Action

Use Server Administrator to increase the maximum number of connections available in the JDBC pool that is assigned to the ISInternal functional alias.

JournalLogger.FAC_SCHED+"."+SCHED_DB_E_EXCEPTION Scheduler: Exception: {0}
Class E
Explanation

Integration Server encountered an error while retrieving a scheduled task from the database and executing it.
Action

Read through the contents of the error logs and take corrective steps. If you are unable to resolve the issue, contact Software AG Global Support.

JournalLogger.FAC_SCHED+"."+SCHED_DB_E_INSERT Scheduler: Error inserting task into database: {0}
Class E
Explanation

Integration Server encountered an error while adding a new scheduled task to the database.
Action

Read through the contents of the error logs and take corrective steps. If you are unable to resolve the issue, contact Software AG Global Support.

JournalLogger.FAC_SCHED+"."+SCHED_DB_E_UPDATE Scheduler: Error updating task in database: {0}
Class E
Explanation

Integration Server encountered an error while updating the information of a scheduled task in the database.
Action

Read through the contents of the error logs and take corrective steps. If you are unable to resolve the issue, contact Software AG Global Support.

JournalLogger.FAC_SCHED+"."+SCHED_DB_E_STATUS Scheduler: Error updating status in database: {0}
Class E
Explanation

Integration Server encountered an error while updating the status of a scheduled task in the database.
Action

Read through the contents of the error logs and take corrective steps. If you are unable to resolve the issue, contact Software AG Global Support.

JournalLogger.FAC_SCHED+"."+SCHED_DB_E_GETIDS Scheduler: Exception getting task IDs from database: {0}
Class E
Explanation

Integration Server encountered an error while retrieving the IDs of scheduled tasks associated with a user.
Action

Read through the contents of the error logs and take corrective steps. If you are unable to resolve the issue, contact Software AG Global Support.

JournalLogger.FAC_SCHED+"."+SCHED_DB_E_GETTASKS Scheduler: Exception getting tasks from database: {0}
Class E
Explanation

Integration Server encountered an unexcepted SQLException while retrieving the scheduled tasks from the database.
Action

Ensure that the database is available and configured to execute scheduled tasks.
JournalLogger.FAC_SCHED+"."+SCHED_DB_E_INVOKE Scheduler: Exception while invoking ''{0}'': {1}
Class E
Explanation

Integration Server encountered a runtime exception while invoking a scheduled task.
Action

Read through the contents of the error logs and take corrective steps. If you are unable to resolve the issue, contact Software AG Global Support.

JournalLogger.FAC_SCHED+"."+SCHED_DB_INVALID_DB_VENDOR_TYPE Invalid database vendor type: {0}
Class E
Explanation

The database driver for the ISInternal functional alias is not valid.
Action

Go to the Settings > JDBC Pools page in Integration Server Administrator and set ISInternal's pool alias to use one of the listed database drivers.

JournalLogger.FAC_SCHED+"."+SCHED_DB_NO_ISINTERNAL_POOL No ISInternal JDBC Pool
Class E
Explanation

The ISInternal functional alias is not configured.
Action

Configure the ISInternal functional alias (specified on the Settings > JDBC Pools screen in Integration Server Administrator) and assign a valid JDBC connection pool to it.

JournalLogger.FAC_SCHED+"."+SCHED_DB_NO_CONNECTION Could not get connection for pool {0}
Class E
Explanation

Integration Server attempted to acquire a JDBC connection, but no connections are available in the pool assigned to the ISInternal functional alias.

Action

Use Server Administrator to increase the maximum number of connections available in the JDBC pool that is assigned to the ISInternal functional alias.

JournalLogger.FAC_SCHED+"."+SCHED_DB_DISABLED_DEPENDENCY_MGR Namespace Dependency Manager is disabled
Class E
Explanation

Unable to determine if the service executed by a scheduled task refers to other services that are unavailable.
Action

Contact Software AG Global Support.
JournalLogger.FAC_SCHED+"."+SCHED_DB_FOUND_UNRESOLVED_DEPENDENT_SERVICES Found unresolved dependent services: {0}
Class E
Explanation

Integration Server was unable to create or run the scheduled task because the service scheduled to run contains a reference to a service that cannot be located.

Action

Update the scheduled task to specify a correct reference to the dependent service. Note: Integration Server performs reference validation for services only when the watt.server.scheduler.ignoreReferenceValidation configuration parameter is set to true. The default is false.

JournalLogger.FAC_SCHED+"."+SCHED_DB_DISABLED_USER User {0} is disabled
Class E
Explanation

The user a scheduled task is set to run as is disabled. The task will not run.
Action

Enable the user or modify the task to run as a different user.
JournalLogger.FAC_SCHED+"."+SCHED_DB_REMOVED_USER User {0} is removed
Class E
Explanation

The user associated with a scheduled task has been removed.
Action

Add the user or change the scheduled task to execute with an enabled user.
JournalLogger.FAC_SCHED+"."+SCHED_DB_COULD_NOT_COMPLETE_LAST_RUN Could not complete last run at node {0}
Class W
JournalLogger.FAC_SCHED+"."+SCHED_DB_THREAD_THROTTLE_REACHED Rolling back due to scheduler thread throttle reached: {0}
Class E
Explanation

A scheduled task attempted to use more threads than the maximum number allowed by the Scheduler thread throttle limit. Any scheduled tasks that attempt to execute under these circumstances will fail.

Action

Use Integration Server Administrator to increase the Scheduler thread throttle under Settings > Resources > Edit Resource Settings > Server Thread Pool.

JournalLogger.FAC_SCHED+"."+SCHED_DB_MSG_TRUNCATED ...<truncated>
Class E
Explanation

Integration Server encountered an error during the execution of a scheduled task.
Action

Read through the contents of the error logs and take corrective steps. If you are unable to resolve the issue, contact Software AG Global Support.

JournalLogger.FAC_SCHED+"."+SCHED_DB_INVALID_TARGET Invalid Target {0}
Class E
Explanation

A scheduled task is set to run on a host that is not currently a member of the Integration Server cluster.
Action

Modify the scheduled task to run on a member of the cluster.
JournalLogger.FAC_SCHED+"."+SCHED_DB_INVALID_TASK_ID Invalid task ID {0}
Class E
Explanation

Internal error.
Action

Contact Software AG Global Support.
JournalLogger.FAC_SCHED+"."+SCHEDULER_NOT_RUNNING Errors encountered while initializing Scheduler. Scheduled tasks will not run. Check the logs for more information.
Class E
Explanation

Integration Server encountered an error either while initializing the scheduler or while connecting to the database in which information about scheduled jobs is stored. As a result, scheduled tasks will not run.

Action

Read through the contents of the error logs and take corrective steps. After correcting the issue that caused the error, restart the Integration Server.

JournalLogger.FAC_SCHED+"."+SCHED_DB_UNKNOWN_SERVICE Unknown Service: {0}. Scheduled task will not run.
Class E
Explanation

The service configured to execute for a scheduler does not exist in the Integration Server.
Action

Ensure that the service is available in the Integration Server.
APLog.string(APLog.AP_CONNECTION_TEST_FAILED) Test of CentraSite connection failed.
Class E
Explanation

Integration Server encountered an exception while connecting to CentraSite.
Action

Ensure the parameters that Integration Server uses to connect to CentraSite are correct. Specifically, check the URL pointing to CentraSite (including the port), the user name, and password.

ISKeyStoreBundle.getKeyForJournalLogger(DEFAULT_KEYSTORE_CREATION_ERROR) Error: Default keystore alias "DEFAULT_IS_KEYSTORE" cannot be created. Details: {0}
Class W
Explanation

Error while creating DEFAULT_IS_KEYSTORE alias at the first startup of Integration Server.
Action

<p>The following lists the actions you can take:</p><p> 1. Ensure that the keystore file 'keystore.jks' is present in the Integration Server_directory\common\conf directory.</p><p>2. Ensure that the keystore has not expired.</p><p>3. Contact Software AG Global Support.</p>

ISKeyStoreBundle.getKeyForJournalLogger(DEFAULT_TRUSTSTORE_CREATION_ERROR) Error: Default truststore alias "DEFAULT_IS_TRUSTSTORE" cannot be created. Details: {0}
Class W
Explanation

Error while creating DEFAULT_IS_TRUSTSTORE alias at the first start up of Integration Server.
Action

<p>The following lists the actions you can take:</p><p>1. Ensure that the truststore file platform_truststore.jks is present in the Integration Server_directory\common\conf\ directory.</p><p>2. Ensure that the truststore has not expired.</p><p>3. Contact Software AG Global Support.</p>

KEYSTORE_INVALID_CONFIG_FILE Error: invalid keystore or truststore configuration file ''{0}''.
Class E
Explanation

Configuration file related to keystore is corrupted.
Action

Create a keystore alias.
KEY_STORE_CREATED Keystore alias ''{0}'' saved successfully.
Class I
KEY_STORE_CREATED_1 Keystore alias ''{0}'' saved successfully. Warning: before using the keystore, you must create a password for at least one of its key aliases. Please edit the keystore alias configuration and add one or more valid key alias passwords.
Class W
Explanation

The key aliases are not configured. Before using the keystore, you must create a password for at least one of its key aliases.
Action

Edit the keystore alias configuration and add at least one valid key alias passwords.
KEY_STORE_CREATED_2 Keystore alias ''{0}'' saved successfully. An error occurred while loading the keystore in memory, please edit the keystore alias configuration. Details: {1}
Class E
Explanation

An error occurred while loading the keystore in memory.
Action

Edit the keystore alias configuration. Make sure that the keystore location is correct and keystore exists on the file system. Then, make sure that the configuration file related to the keystore is valid.

KEY_STORE_CREATED_3 Keystore alias ''{0}'' saved successfully. Warning: the following key aliases ''{1}'' cannot be used because they do not have passwords. Please edit the keystore alias configuration and add password(s) for the appropriate key alias(es).
Class W
Explanation

Some key aliases are not configured.
Action

Edit the keystore alias configuration and add passwords for the corresponding key aliases.
KEY_STORE_CREATED_4 Keystore alias ''{0}'' saved successfully. Warning: the following key aliases ''{1}'' have been removed from the keystore alias configuration.
Class W
Explanation

Few key aliases were removed from the keystore alias configuration.
Action

Refresh the keystore alias.
KEY_STORE_SAVE_ERROR Error: cannot save the keystore alias ''{0}''.
Class E
Explanation

Either the keystore location is invalid, or the key aliases passwords do not consist of ASCII characters.
Action

Make sure that the keystore location is valid and the key aliases passwords consist of valid ASCII characters.
KEY_STORE_NOT_FOUND Error: keystore ''{0}'' not found.
Class E
Explanation

The configuration file related to keystore alias is unavailable.
Action

Make sure that the configuration file related to the keystore alias exists in the directory ../config/security/keystore.
KEY_STORE_NOT_FOUND_1 Error: keystore ''{0}'' not found. Details: {1}.
Class E
Explanation

Invalid keystore location.
Action

Make sure that the location of the keystore is correct; the key aliases passwords are valid; and the configuration file exists, and it is not corrupted.

KEY_STORE_REFRESHED_1 Keystore ''{0}'' was reloaded successfully. Warning: you must provide the password for at least one key alias in the keystore before using it. Please edit the keystore alias configuration and add at least one valid key alias password.
Class W
Explanation

Either the keystore does not contain any key aliases, or a key alias password is not provided. You must provide the password for at least one key alias in the keystore before using it.

Action

Check whether the keystore has any key aliases. If not, then add key alias in the keystore. If there are key aliases in the keystore, then edit the keystore alias configuration and add at least one valid key alias password.

KEY_STORE_REFRESHED_3 Keystore ''{0}'' reloaded successfully. Warning: the following key aliases ''{1}'' cannot be used because they do not have a password. Please edit the keystore alias configuration and add one or more valid key alias passwords.
Class W
Explanation

Key alias must be configured in advance.
Action

Edit the keystore alias configuration and add one or more valid key alias passwords.
KEY_STORE_REFRESHED_4 Keystore ''{0}'' reloaded successfully. Warning: the following key aliases ''{1}'' have been removed from the alias configuration.
Class W
Explanation

Key alias must be configured in advance.
Action

Edit the keystore alias configuration and add one or more valid key alias passwords.
KEY_STORE_REFRESH_ERROR Error: cannot reload keystore ''{0}''. Details: {1}.
Class E
Explanation

Keystore alias does not map to a valid keystore.
Action

Make sure that the keystore location is correct and keystore exists on the file system. Make sure that the configuration file related to the keystore is valid.

KEY_STORE_REFRESH_ERROR_1 Error: cannot reload keystore ''{0}''.
Class E
Explanation

Configuration file does not exist.
Action

Make sure that the configuration file, which corresponds to the truststore alias, exists in the directory ../config/security/keystore.
KEY_STORE_DELETE_ERROR Error: unable to delete the keystore alias ''{0}''.
Class E
Explanation

Keystore does not exist.
Action

Make sure that the keystore location is correct and the keystore exists on the file system.
INVALID_KEY_STORE Error: invalid keystore alias name ''{0}''.
Class E
Explanation

Keystore alias is null or empty.
Action

Make sure that the keystore alias is not null or empty.
KEY_STORE_INVALID_KEY_ALIAS_PASSWORD Error: cannot load the keystore pointed to by keystore alias ''{0}'', because of invalid password(s) for key alias(es) ''{1}''.
Class E
Explanation

Invalid key alias password.
Action

Make sure that the key aliases passwords are correct.
INVALID_KEY_ALIAS Error: invalid key alias ''{0}''.
Class E
Explanation

The key alias is invalid.
Action

Make sure that the key alias exists in the keystore.
KEY_STORE_PWD_LOOKUP_ERROR Error: unable to look up the password for the key alias ''{1}'' in the keystore '{0}''.
Class E
Explanation

Invalid key alias password.
Action

Make sure that the key alias password is correct.
TRUST_STORE_CREATED_2 Truststore alias ''{0}'' saved successfully. An error occurred while loading the truststore in memory, please edit the truststore alias configuration. Details: {1}.
Class E
Explanation

Configuration file is corrupted.
Action

Make sure that the configuration file, which corresponds to the truststore alias is valid.
TRUST_STORE_SAVE_ERROR Error: cannot save the truststore alias ''{0}''.
Class E
Explanation

Truststore location is invalid.
Action

Make sure that the truststore location is valid.
TRUST_STORE_NOT_FOUND Error: truststore ''{0}'' not found.
Class E
Explanation

The configuration file related to truststore alias is unavailable.
Action

Make sure that the configuration file related to the truststore alias exists in the directory ../config/security/keystore.
TRUST_STORE_NOT_FOUND_1 Error: truststore ''{0}'' not found. Error: {1}.
Class E
Explanation

Either the truststore location, or the configuration file is invalid.
Action

Make sure that the location of the truststore is correct; the truststore alias password is correct; and the configuration file exists, and it is not corrupted.

TRUST_STORE_REFRESH_ERROR Error: cannot reload truststore ''{0}''. Details: {1}.
Class E
Explanation

Either the keystore location is invalid, or the key aliases are modified.
Action

Make sure that the keystore location is valid and the key alias is not modified.
TRUST_STORE_REFRESH_ERROR_1 Error: cannot reload truststore ''{0}''.
Class E
Explanation

Configuration file does not exist.
Action

Make sure that the configuration file, which corresponds to the truststore alias, exists in the directory ../config/security/keystore.
TRUST_STORE_DELETE_ERROR Error: unable to delete the truststore alias ''{0}''.
Class E
Explanation

Configuration file does not exist.
Action

Make sure that the configuration file for the truststore alias exists in the directory ../config/security/keystore.
INVALID_TRUST_STORE Error: invalid truststore alias name ''{0}''.
Class E
Explanation

Invalid truststore name.
Action

Make sure that the truststore name is not null or empty.
STORE_DATA_RETRIEVAL_ERROR Error: cannot retrieve data for the truststore ''{0}''.
Class E
Explanation

Keystore is not loaded or initialized properly.
Action

Make sure that keystore is valid and the alias refers to the valid keystore location.
CERTS_RETRIEVAL_ERROR Error: cannot retrieve trusted certificates from the truststore pointed to by truststore alias ''{0}''. Details: {1}.
Class E
Explanation

Truststore is not initialized or loaded properly.
Action

Reload the truststore alias and then make sure that the configuration file exists for the truststore alias.
PRIVATE_KEY_RETRIEVAL_ERROR Error: cannot retrieve the key for alias ''{0}'' from the keystore pointed to by keystore alias ''{1}''. Details: {2}.
Class E
Explanation

Key alias entry in the keystore is not valid.
Action

Make sure that the key alias entry in the keystore is valid. For example, the certificate chain is available or the algorithm of the private key matches to the algorithm of the PublicKey in the end entity Certificate (at index 0).

USUPPORTED_CERTIFICATE_TYPE Error: cannot retrieve the certificate for alias ''{0}'' from the truststore pointed to by truststore alias ''{1}''. Unsupported certificate type ''{2}''.
Class E
Explanation

Invalid certificate type.
Action

Make sure that the certificate configured by the key alias is X509 Certificate.
STORE_ALIAS_MODIFIED_ERROR Error: the alias has been modified from ''{0}'' to ''{1}''.
Class E
Explanation

Keystore alias does not map to a valid keystore.
Action

Make sure that the keystore alias refers to a valid keystore.
STORE_ALIAS_OR_CONFIGFILE_MODIFIED_ERROR Error: either the alias name''{0}'' or the configuration file name ''{1}'' is incorrect.
Class E
Explanation

Configuration file does not exist.
Action

Make sure that the configuration file exists for the alias in the directory ../config/securoty/keystore.
INVALID_ASCII_KEYALIAS_PASSWD Password for following key aliases must be ASCII characters: {0}
Class E
Explanation

The key alias password consists of non-ASCII characters.
Action

Make sure that the key alias password consists of valid ASCII characters.
ISKeyStoreBundle.getKeyForJournalLogger(CANNOT_LOAD_KEYSTORE) Error: cannot load the keystore/truststore configuration file ''{0}''. Details:{1}.
Class E
Explanation

Failed to load the keystore file. Possible reasons:                      a. Corrupt keystore file                      b. Incorrect password                      c. No read permission for keystore file 

Action

Ensure that: a. The Keystore file is not corrupted. Try opening it using another keystore tool. b. Provide a correct password   c. Check file permissions 

ISKeyStoreBundle.getKeyForJournalLogger(INVALID_KEYSTORE_CONFIG_FILE) Error: invalid keystore/truststore configuration file ''{0}''.
Class E
Explanation

Configuration file does not exist.
Action

Make sure that the configuration file, which corresponds to the truststore alias, exists in the directory ../config/security/keystore.
ISKeyStoreBundle.getKeyForJournalLogger(KEYSTORE_INIT_FAILED) Error: ISKeyStoreManager initialization failed. Cannot create the keystore configuration directory ''{1}''.
Class E
Explanation

Keystore directory does not exist.
Action

Keystore location is invalid. Make sure that the keystore directory exists.
ISKeyStoreBundle.getKeyForJournalLogger(KEYSTORE_ALIAS_MODIFIED) Error: alias has been modified from ''{0}'' to ''{1}''.
Class E
Explanation

Keystore alias does not map to a valid keystore .
Action

Make sure that the keystore alias refers to a valid keystore.
ISKeyStoreBundle.getKeyForJournalLogger(INCORRECT_ALIAS_OR_CONFIG_FILE) Error: either the alias name ''{0}'' or the configuration file name ''{1}'' is incorrect.
Class E
Explanation

Configuration file is corrupted.
Action

Make sure that the configuration file, which corresponds to the truststore alias, exists in the directory ../config/security/keystore.
DEFAULT_KEYSTORE_DESCRIPTION Default keystore alias for Integration Server.
Class I
DEFAULT_TRUSTSTORE_DESCRIPTION Default truststore alias for Integration Server.
Class I
141.1 Unable to create JMS URI for WS Endpoint Alias "{0}": {1}
Class E
Explanation

The Web service endpoint alias does not contain the information needed to construct a JMS URI.
Action

Use the information in the exception to update the alias. For example, you may need to make changes to the provider Web service endpoint alias or edit the SOAP-JMS trigger used with the alias.

141.2 Unable to create WS Endpoint Trigger: {0}
Class E
Explanation

Integration Server could not create a WS endpoint trigger using the information in the provider Web service endpoint alias.
Action

In Integration Server Administrator, use the information provided in the exception to edit the provider Web service endpoint alias

141.101 WS-Policy file {0} with policy ID {1} is invalid. Details: {2}
Class W
Explanation

The WS-Policy file added to the policy repository is not valid. Integration Server has moved the policy file to the IntegrationServer/config/wss/policies/invalid folder.

Action

Correct the invalid WS-Policy file in the IntegrationServer/config/wss/policies/invalid folder to make it valid and move it back into the main policy repository directory.

141.103 Web service descriptor {0} is not available because the WS-Policy file {1} with policy ID {2} attached to the WSD is deleted.
Class W
Explanation

The Web service descriptor is not available because the WS-Policy file attached to the Web service descriptor is deleted or moved from the policy repository.

Action

The following lists the actions you can take:

1) Ensure that the WS-Policy that is attached to the Web service descriptor resides in the policy repository.

-OR-

2) Edit the Web service descriptor so that it no longer uses the deleted WS-Policy file.
141.107 Web service descriptor {0} is not available because the policy ID in WS-Policy file {1} is changed from {2} to {3}.
Class W
Explanation

The Web service descriptor is not available because the policy ID of the WS-Policy file attached to the Web service descriptor has changed.

Action

The following lists the actions you can take:

1) Change the policy id of the WS-Policy that is attached to the Web service descriptor to what it was previously.

2) Edit the Web service descriptor by re-attaching the WS-Policy file with the updated policy ID.
INVALID_HEADER_TYPE Transport header "{0}" is invalid and will not be added to the message. Transport headers must be Strings.
Class E
Explanation

In the name/value pair supplied as a transport header, the name and the value must be of type String. If a transport header has a name or value that is not of type String, the header will not be included in the message.

Action

Change the transport header so that the name and value are both of type String.
141.109 Could not deploy consumer Web service descriptor {0} for handling asynchronous responses. Connectors generated for this consumer Web service descriptor can only be used for handling responses synchronously. Cause: {1}.
Class W
Explanation

The consumer Web service descriptor specified in the message could not be deployed to handle asynchronous responses. See the error message for more details about the cause of the failure.

Action

If the error message indicates that the error can be resolved by changing the WSDL, change or correct the WSDL used for creating the consumer Web service descriptor and recreate the consumer. If the error still occurs, contact Software AG Global Support.

RESPONSE_CANNOT_BE_NULL Received a null response.
Class E
Explanation

An internal error occurred while processing the Web service request.
Action

Contact Software AG Global Support.
UNSUPPORTED_ENCODING Received unsupported content-encoding: {0}
Class E
Explanation

The Web service response used the specified content-encoding, which is not supported.
Action

Ensure that the Web service request specifies a supported content-encoding for the response.
TRANSPORT_ERROR An HTTP transport error occured. Error Code: {0}, Error Message: {1}
Class E
Explanation

An error occurred while sending a Web service response. The error code and message portions of the error contain details about the error.

Action

Contact Software AG Global Support.
ACCESS_DENIED Access Denied
Class E
Explanation

A Web service request has arrived over an HTTP or HTTPS port, but the port access check has failed for the Web service descriptor. This means that the provider Web service descriptor name is either missing from the Allow list or is present in the Deny List, depending on how access to the port is defined.

Action

If access to this Web service is to be allowed over this port, ensure that the provider Web service descriptor name is either removed from the port's deny list or added to the port's allow list.

COULD_NOT_DEPLOY_WSD Could not deploy the Web service descriptor {0}. Cause: {1}
Class E
Explanation

Integration Server could not deploy the Web service descriptor. Typical reasons are:

1) The WS-Policy that is attached to the provider Web service descriptor does not exist.

2) The module required to handle the attached WS-Policy does not exist.

3) The "rampartConfigProperties" parameter, which is in the axis2.xml file, is locked. If it is not one of these reasons, refer to the error message, which lists the cause.

Action

The following lists the actions you can take for one of the typical causes:

1) Ensure the WS-Policy that is attached to the Web service descriptor resides in the policy repository: (webMethods_directory)/IntegrationServer/config/wss

2) Ensure the module required to handle the attached WS-Policy resides in the (webMethods_directory)/IntegrationServer/config/wss/modules subdirectory.

3) Ensure the "rampartConfigProperties" parameter in the axis2.xml file is not locked. The axis2.xml file resides (webMethods_directory)/IntegrationServer/config/wss/modules subdirectory. For all other reasons, refer to the cause listed in the error message and respond accordingly.

SERVER_NON_SOAP_RESPONSE Received a plain text response: {0}
Class E
Explanation

A Web service call expected a SOAP Response but instead received a plain text response. The actual responseText is returned within a SOAP fault.

Action

Determine why the Web service provider did not return a SOAP response. It is possible that an incorrect endpoint address was used or an error occurred on the Web service provider.

WSRM_UNKNOWN_SEQUENCE Unknown web services reliable messaging sequence {0} specified for endpoint URI {1}.
Class E
Explanation

A reliable messaging sequence with the specified sequence key corresponding to the specified endpoint URI does not exist.
Action

Specify a valid sequence key for the specified endpoint URI.
WSRM_DUPLICATE_SEQUENCE A duplicate web services reliable messaging sequence {0} specified for endpoint URI {1}.
Class E
Explanation

A reliable messaging sequence with the specified sequence key and endpoint URI already exists.
Action

Specify a valid sequence key for the specified endpoint URI.
WSRM_CLOSED_SEQUENCE A closed web services reliable messaging sequence {0} specified for endpoint URI {1}.
Class E
Explanation

The reliable messaging sequence with the specified sequence key and endpoint URI is closed.
Action

Specify a valid sequence key for the specified endpoint URI.
WSRM_TERMINATED_SEQUENCE A terminated web services reliable messaging sequence {0} specified for endpoint URI {1}.
Class E
Explanation

The reliable messaging sequence with the specified key and endpoint URI is terminated.
Action

Specify a valid sequence key for the specified endpoint URI.
WSRM_POLICY_NOT_ENABLED Web services reliable messaging is not enabled for consumer web Services Descriptor {0}.
Class E
Explanation

Reliable messaging is not enabled for the specified consumer web service descriptor.
Action

Specify a valid consumer web service descriptor for which reliable messaging is enabled or enable reliable messaging for the specified consumer web service descriptor.

142.3 User {0} issued request to cancel the thread. Thread id - {1}
Class W
Explanation

Integration Server received a request to cancel an executing thread.
Action

No action is required.
142.4 User {0} issued request to kill the thread. Thread id - {1}
Class W
Explanation

Integration Server received a request to kill an executing thread.
Action

No action is required.
142.18 The watt.server.threadKill.timeout.enabled parameter is set to true; however, the property that enables the thread kill facility, watt.server.threadKill.enabled, is set to false.
Class E
Explanation

The ability to cancel or kill service threads is controlled by the watt.server.threadKill.enabled property. If you want to be able to cancel or kill threads, this property must be set to true, which is the default setting.

Action

Set watt.server.threadKill.enabled to true so that a flow step will not run beyond its specified timeout period.
FAC+"."+QMM_ERROR_START_UP Unable to start Integration Server in quiesce mode. No quiesce port was specified.
Class E
Explanation

Integration Server cannot be started from the command line with the -quiesce switch unless a quiesce port is specified.
Action

Start Integration Server using either the Start menu (on Windows) or the startup.sh script (on UNIX). Then, specify the quiesce port that Integration Server should use to enter and exit quiesce mode.

FAC+"."+QMM_ERROR_GO_QUIET Unable to quiesce this Integration Server. Exception: {0}
Class E
Explanation

An error occurred while switching this server to quiesce mode.
Action

Check the Integration Server server and error logs. Take appropriate corrective action for the reported asset type. Then, try switching to quiesce mode again.

FAC+"."+QMM_ERROR_HANDLER_GO_QUIET Handler "{0}" cannot disable asset type "{1}". Exception: {2}
Class W
Explanation

While entering quiesce mode, Integration Server encountered an error when attempting to disable the specified asset type.
Action

In the Integration Server Administrator, manually disable the assets of the reported asset type.
FAC+"."+QMM_ERROR_GO_ACTIVE Unable to return Integration Server to active mode. Exception: {0}
Class E
Explanation

An error occurred while switching this Integration Server to active mode.
Action

Check the Integration Server server and error logs. Then, take the appropriate corrective action.

FAC+"."+QMM_ERROR_HANDLER_GO_ACTIVE Handler "{0}" was unable to restore state of "{1}" asset type. Exception: {2}
Class W
Explanation

While exiting quiesce mode, Integration Server could not restore the state of the specified asset type.
Action

In the Integration Server Administrator, manually enable the assets of the reported asset type.
FAC+"."+QMM_ERROR_SHUTDOWN Unable to shut down the quiesce mode manager. Exception: {0}.
Class W
Explanation

Integration Server could not save the quiesce properties in the quiesce configuration file. The quiesce.cnf file either does not exist or is corrupt.

Action

Delete the quiesce.cnf file from the Integration Server_directory\config directory. Then, restart the server and specify the quiesce port again.

FAC+"."+QMM_ERROR_SET_QUIESCE_PORT Unable to save the configuration after setting quiesce port to {0}. Exception: {1}
Class E
Explanation

An error occurred when the quiesce port was changed and Integration Server attempted to save the changes.
Action

Set the quiesce port to a valid port. If the error recurs, contact Software AG Global Support.
FAC+"."+QMM_ERROR_QUIESCE_PORT_NULL Unable to validate quiesce port {0}. Port does not exist.
Class E
Explanation

The quiesce port has been deleted.
Action

Specify the port alias of an existing valid port.
FAC+"."+QMM_ERROR_QUIESCE_PORT_DISABLED Unable to validate quiesce port {0}. Port is not enabled.
Class E
Explanation

The quiesce port is disabled.
Action

Enable the quiesce port.
FAC+"."+QMM_ERROR_QUIESCE_PORT_PACKAGE Unable to validate quiesce port {0}. Port is not associated with WmRoot or WmPublic package.
Class E
Explanation

The quiesce port does not reside in either the WmRoot or the WmPublic package.
Action

Specify the port alias of a valid quiesce port that resides in either the WmRoot package or the WmPublic package.
FAC+"."+QMM_ERROR_QUIESCE_PORT_PROTOCOL Unable to validate quiesce port {0}. Port type is incorrect.
Class E
Explanation

The specified quiesce port does not belong to the HTTP or HTTPS protocol.
Action

Specify the port alias of a valid quiesce port of type HTTP or HTTPS.
FAC+"."+QMM_ERROR_QUIESCE_PORT_SUSPENDED Unable to validate quiesce port {0}. Port is suspended.
Class E
Explanation

The quiesce port is suspended.
Action

Resume the quiesce port.
FAC+"."+QMM_ERROR_QUIESCE_PORT_ACCESS Unable to validate quiesce port {0}. Port does not have the necessary access mode.
Class E
Explanation

The quiesce port's access mode is set to Deny+.
Action

Change the quiesce port's access mode to Allow.
FAC+"."+QUIESCE_CLUSTER_JOIN_FAILED Integration Server that is configured to be a member of a cluster did not join the cluster when exiting quiesce mode.
Class E
Explanation

When exiting quiesce mode, Integration Server did not join the cluster.
Action

Use the Integration Server server log and error log to determine why Integration Server did not join the cluster and take the necessary actions to correct the error. Then, do one of the following for Integration Server to join the cluster: either restart Integration Server or enter and exit quiesce mode.

FAC+"."+QUIESCE_CLUSTER_FAILED_EXCEPTION Integration Server is not configured for clustering. Errors occurred during initialization of cache managers. Exception: {0}
Class E
Explanation

When exiting quiesce mode, Integration Server failed to initialize cache managers.
Action

Check Integration Server Server and Error logs and take required actions to correct the clustering error. Once this is done, you can either restart Integration Server or Enter and Exit Quiesce Mode to enable the cluster.

FAC+"."+QUIESCE_CLUSTER_FAILED Integration Server is not configured for clustering. Errors occurred during initialization of cache managers.
Class E
Explanation

When exiting quiesce mode, Integration Server failed to initialize cache managers.
Action

Check Integration Server Server and Error logs and take required actions to correct the clustering error. Once this is done, you can either restart Integration Server or Enter and Exit Quiesce Mode.

FAC+"."+QM_SIR_WARN_TRIGGER_NOT_SUSPENDED Unable to suspend {0}. Reason: {1}
Class W
Explanation

While entering quiesce mode, Integration Server could not suspend the specified trigger.
Action

Check the server log for details and manually suspend the trigger.
FAC+"."+QM_SIR_WARN_TRIGGER_NOT_RESUMED Unable to resume {0}. Reason: {1}
Class W
Explanation

While entering quiesce mode, Integration Server could not resume the specified trigger, even though the package containing trigger is enabled.

Action

Check the server log for details and manually enable the trigger.
FAC+"."+QM_SIR_QUIESCE_TIMEOUT_EXPIRED Quiesce timeout limit of {0} minutes has expired. {1} services are running. Proceeding with disabling the packages.
Class W
Explanation

Integration Server is proceeding with disabling packages even though some long-running services are still running. One or more of these services might fail.

Action

In the Integration Server Administrator, check which services are still running and make sure those services have completed before attempting to quiesce this server again. Alternatively, increase the quiesce timeout limit.

FAC+"."+QUIESCE_PACKAGE_EXCEPTION_Q Cannot disable packages. Exception: {0}
Class E
Explanation

While entering quiesce mode, Integration Server could not disable packages.
Action

Check the Integration Server server log for details. Then, in the Integration Server Administrator, manually disable the packages.
FAC+"."+QUIESCE_PACKAGE_CORE_PACKAGE_NOT_LOADED Package "{0}" is not loaded.
Class E
Explanation

While starting in quiesce mode, Integration Server could not load the WmRoot or WmPublic package.
Action

Start the server in active mode, and then enter quiesce mode.
FAC+"."+QUIESCE_PACKAGE_EXCEPTION_R Unable to restore state of packages. Exception: {0}
Class E
Explanation

While exiting quiesce mode, Integration Server could not restore the state of packages.
Action

Check the Integration Server server log for details. Then, in the Integration Server Administrator, manually enable or disable the packages as necessary.

FAC+"."+QUIESCE_PACKAGE_RESUME_FAILED Cannot enable package "{0}".
Class E
Explanation

While exiting quiesce mode, Integration Server could not enable the specified package.
Action

In the Integration Server Administrator, manually enable the specified package.
FAC+"."+QUIESCE_LISTENER_ENABLE_EXCEPTION Cannot enable listener "{0}" in quiesce mode. Exception: {1}
Class E
Explanation

Integration Server could not start the quiesce listener.
Action

Ensure that the listener is enabled in the listener.cnf configuration file.
FAC+"."+QUIESCE_LISTENER_DISABLE_EXCEPTION Cannot disable listener "{0}" in quiesce mode. Exception: {1}
Class E
Explanation

Integration Server could not stop the quiesce listener.
Action

Ensure that the listener is disabled in the listener.cnf configuration file.
FAC+"."+QUIESCE_SCHEDULEDTASK_FATAL_ERROR Unable to process scheduled task. Exception: {0}
Class E
Explanation

Integration Server encountered a runtime error of unknown cause while attempting to quiesce a scheduled task.
Action

Check the server log for details and take the appropriate corrective steps.
FAC+"."+QUIESCE_SCHEDULEDTASK_SQL_ERROR Unable to retrieve scheduled task "{0}" from database. Exception: {1}
Class E
Explanation

Either the database server is down or Integration Server is no longer connected to the database.
Action

Make sure the connection between Integration Server and the database is active.
FAC+"."+QUIESCE_SCHEDULEDTASK_QUIESCEASSET_ERROR Unable to retrieve scheduled task from database. Exception: {0}
Class E
Explanation

Either the database server is down or Integration Server is no longer connected to the database.
Action

Make sure the connection between Integration Server and the database is active.
FAC+"."+QUIESCE_SCHEDULEDTASK_RESUME_ERROR Unable to resume scheduled task "{0}" in quiesce mode. Exception: {1}
Class E
Explanation

The state of the scheduled task may be inconsistent between the database and Integration Server. This can occur when changes are made to the database outside of Integration Server.

Action

Check the state of the task in the database. In the Integration Server Administrator, change the state of the task to match the state reported in the database.

FAC+"."+QUIESCE_SCHEDULEDTASK_NO_LOGICALHOST_NAME Unable to retrieve host name. Exception: {0}
Class E
Explanation

The Integration Server you are attempting to quiesce is part of a cluster, and there is an issue with the cluster's configuration.
Action

Verify your clustering environment and cache configuration according to the guidelines in the webMethods Integration Server documentation.

FAC+"."+QUIESCE_JMS_ALIAS_NOT_DISABLED Cannot disable JMS connection alias "{0}". Reason: {1}
Class W
Explanation

While entering quiesce mode, Integration Server could not disable the specified JMS connection alias.
Action

In the Integration Server Administrator, manually disable the JMS connection alias.
FAC+"."+QUIESCE_JMS_ALIAS_NOT_RESUMED Cannot enable JMS connection alias "{0}". Reason: {1}
Class W
Explanation

While exiting quiesce mode, Integration Server could not enable the specified JMS connection alias.
Action

In the Integration Server Administrator, manually enable the JMS connection alias.
FAC+"."+QUIESCE_GD_OUTBD_JOBMGR_SHUTDOWN_EXCEPTION Unable to shut down the guaranteed delivery outbound Job Manager. Exception: {0}
Class E
Explanation

While entering quiesce mode, Integration Server could not shut down the outbound Job Manager.
Action

In the Integration Server Administrator, manually disable the guaranteed delivery outbound Job Manager.
FAC+"."+QUIESCE_GD_INBD_JOBMGR_STARTUP_EXCEPTION Unable to initialize the guaranteed delivery inbound Job Manager. Exception: {0}
Class E
Explanation

While exiting quiesce mode, Integration Server could not initialize the guaranteed delivery inbound Job Manager.
Action

In the Integration Server Administrator, manually enable the guaranteed delivery inbound Job Manager.
FAC+"."+QUIESCE_GD_OUTBD_JOBMGR_STARTUP_EXCEPTION Unable to initialize the guaranteed delivery outbound Job Manager. Exception: {0}
Class E
Explanation

While exiting quiesce mode, Integration Server could not initialize the guaranteed delivery outbound Job Manager.
Action

In the Integration Server Administrator, manually enable the guaranteed delivery outbound Job Manager.
ERROR_KEY_NULL Key cannot be empty.
Class E
Explanation

The Key field must not be empty while adding a global variable.
Action

Provide a vaild Key for the global variable.
ERROR_VALUE_NULL Value cannot be empty.
Class E
Explanation

The Value field must not be empty while adding a global variable.
Action

Provide a valid value for global variable.
ERROR_GL_ALREADY_EXISTS Global variable {0} already exists.
Class E
Explanation

Global variable key must be unique.
Action

Provide a unique key for the global variable.
ERROR_GL_DOES_NOT_EXIST Global variable {0} does not exist.
Class E
Explanation

You attempted to delete or edit a global variable that does not exist.
Action

Ensure that the global variable exists before attempting to edit or delete it.
ERROR_INVALID_CHARS Global Variable key cannot contain any of these characters:{0}
Class
Explanation

The global variable key that you specified contains special characters other than period (.) or underscore(_).
Action

Ensure that the global variable key does not contain any special characters other than period or underscore(_).
ERROR_KEY_LENGTH Global variable key cannot exceed 255 characters.
Class E
Explanation

The global variable key that you specified contains more than 255 characters.
Action

Ensure that length of the global variable key is less than or equal to 255.
ERROR_VALUE_LENGTH Global variable value cannot exceed 255 characters.
Class E
Explanation

The global variable value that you specified contains more than 255 characters.
Action

Ensure that length of the global variable value is less than or equal to 255.
ERROR_SECURE_NOT_EDITABLE The value of the 'isSecure' field of a global variable cannot be edited.
Class E
Explanation

You attempted to edit the value of the ‘isSecure’ field of a global variable.
Action

Ensure that you do not edit the value of the ‘isSecure’ field of a global variable.
ERROR_SERVER_ALIAS_ALREADY_EXISTS SFTP server alias {0} already exists.
Class E
Explanation

The SFTP server alias name that you specified already exists in Integration Server.
Action

Specify an SFTP server alias name that does not exist in Integration Server.
ERROR_SERVER_ALIAS_DOES_NOT_EXIST SFTP server alias {0} does not exist.
Class E
Explanation

The specified SFTP server alias does not exist in Integration Server.
Action

Ensure that the SFTP server alias name you specified is correct and that this SFTP server alias exists in Integration Server.
ERROR_UNKNOWN_PUBLIC_KEY_FILE_FORMAT Cannot retrieve the host key from location {0}. Details: Corrupt or unknown public key file format.
Class E
Explanation

The specified host key file contains the public key of the SFTP server in an unsupported format.
Action

Ensure that the host key file contains the public key in the supported (openssh) format.
ERROR_PRIVATE_KEY_FILE_NOT_FOUND Cannot find the private key file {0}.
Class E
Explanation

Integration Server is unable to find the private key file at specified location.
Action

Ensure that the private key file exists at the specified location.
ERROR_PRIVATE_KEY_ALREADY_EXISTS Private key file {0} already exists in Integration Server.
Class E
Explanation

The specified private key file already exists in Integration Server.
Action

Specify a different private key file.
ERROR_USER_ALIAS_NOT_EXISTS User alias {0} does not exist.
Class E
Explanation

The specified SFTP user alias does not exist in Integration Server.
Action

Ensure that the SFTP user alias name you specified is correct and that this SFTP user alias exists in Integration Server.
ERROR_USER_ALIAS_ALREADY_EXIST User alias {0} already exists.
Class E
Explanation

The SFTP user alias name that you specified already exists in Integration Server.
Action

Specify an SFTP user alias name that does not exist in Integration Server.
ERROR_CANNOT_READ_PUBLIC_KEY_FILE Cannot read host key from location {0}.
Class E
Explanation

Integration Server is unable to read the host key file from the location you specified.
Action

Specify a valid host key file location to which Integration Server has the required permission for reading.
ERROR_CANNOT_WRITE_PUBLIC_KEY_FILE Cannot write the public key to file {0}.
Class E
Explanation

Integration Server is unable to write the host key file to the specified location.
Action

Ensure that Integration Server has the required permission and enough disk space to write the host key to the specified location.
ERROR_CANNOT_GET_HOST_KEY_FROM_SERVER Cannot get host key from server {0}. Details: {1}
Class E
Explanation

Integration Server is unable to retrieve the host key from the specified (arg0) SFTP server.
Action

Ensure that the SFTP server is configured and running on the specified host-port.
ERROR_TEST_CONN_FAIL Test of user alias {0} Fail. Details: {1}
Class E
Explanation

Testing of SFTP user alias (arg0) failed due to error (arg1).
Action

Ensure that the SFTP user alias information is correct and that the SFTP server is running on the specified host and port.
ERROR_SERVER_ALIAS_IN_USE Cannot delete SFTP server alias {0} because the following SFTP user alias(es) are using it : {1}.
Class E
Explanation

Integration Server cannot delete the SFTP server alias (arg0) because the SFTP user alias(es) [arg1] are using it.
Action

Ensure that the SFTP server alias that you want to delete is not included in any SFTP user alias definition.
ERROR_NOT_A_SHORT A valid short value must be specified for "{0}".
Class E
Explanation

The value of short data type that you entered for field {0} while calling the service is invalid.
Action

Ensure that the value specified for the field {0} is a valid short value.
ERROR_NOT_A_BOOLEAN A valid boolean value must be specified for "{0}".
Class E
Explanation

The value of boolean data type that you entered for field {0} while calling the service is invalid.
Action

Ensure that the value specified for the field {0} is a valid boolean value.
ERROR_NOT_A_DOUBLE A valid double value must be specified for "{0}".
Class E
Explanation

The value of double data type that you entered for field {0} while calling the service is invalid.
Action

Ensure that the value specified for the field {0} is a valid double value.
ERROR_NOT_A_FLOAT A valid float value must be specified for "{0}".
Class E
Explanation

The value of float data type that you entered for field {0} while calling the service is invalid.
Action

Ensure that the value specified for the field {0} is a valid float value.
ERROR_NOT_A_CHAR A valid character value must be specified for "{0}".
Class E
Explanation

The value of character data type that you entered for field {0} while calling the service is invalid.
Action

Ensure that the value specified for the field {0} is a valid charater value.
ERROR_NOT_A_BYTE A valid byte value must be specified for "{0}".
Class E
Explanation

The value of byte data type that you entered for field {0} while calling the service is invalid.
Action

Ensure that the value specified for the field {0} is a valid byte value.
ERROR_NOT_A_LONG A valid long value must be specified for "{0}".
Class E
Explanation

The value of long data type that you entered for field {0} while calling the service is invalid.
Action

Ensure that the value specified for the field {0} is a valid long value.
ERROR_PARAM_INVALID_VALID_VALUE {1} is not a valid value for {0}. Allowed values are {2}
Class E
Explanation

The value {1} specified for field {0} while calling a service is not available in the pick list {2}.
Action

Ensure that the value specified for the field {0} is in the pick list {2}.
JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+MESSAGE_SIZE_FILTER_FAILED Message size exceeded the limit of {0} MB.
Class E
Explanation

Enterprise Gateway Server could not process the request because the message associated with the request is larger than the size allowed in the Enterprise Gateway rule.

Action

Either reduce the message size of the request or increase the message size limit in the filter for the rule.
JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+DEBUG_RULE_SET_PROCESSING_START Enterprise Gateway rules processing has started on URL {0} and IP address {1} at time {2}.
Class D
Explanation

Enterprise Gateway Server has started processing rules.
Action

No action is needed.
JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+DEBUG_RULE_PROCESSING_START Processing Enterprise Gateway rule "{0}".
Class D
Explanation

Enterprise Gateway Server has started processing the specified rule.
Action

No action is needed.
JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+DEBUG_FILTER_PROCESSING_START Processing Enterprise Gateway rule filter "{0}".
Class D
Explanation

Enterprise Gateway Server has started processing the specified rule filter.
Action

No action is needed.

JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+ERROR_RULE_WITH_FILTER_FAILED A rule violation occurred for Enterprise Gateway rule "{0}" for filter "{1}": {2}.
Class E
Explanation

Enterprise Gateway Server could not process the request because the request met a filter condition defined in the Enterprise Gateway rule.

Action

Check the filter conditions for the specified rule and either change the conditions or modify the request so a rule violation does not occur.

JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+ERROR_RULE_WITHOUT_FILTER_FAILED A rule violation occurred for Enterprise Gateway rule "{0}".
Class E
Explanation

Enterprise Gateway Server could not process the request because its type did not match the request type configured in the Enterprise Gateway rule.

Action

Modify the request so it matches one of the configured request types.

JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+DOS_IP_FAILED Denial of Service by IP address limit was reached for IP address {0}.
Class E
Explanation

Enterprise Gateway Server could not process the request because an Enterprise Gateway Denial of Service limit was reached for this IP address.

Action

Delete the IP address from the Enterprise Gateway deny list.
JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+DOS_IP_UNBLOCK IP address {0} is unblocked.
Class W
Explanation

Enterprise Gateway Server is again accepting requests from this IP address because the Enterprise Gateway Denial of Service block interval has elapsed.

Action

No action is needed.

JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+DOS_IP_BLOCK IP address {0} is blocked for a duration of {1} minutes.
Class W
Explanation

Enterprise Gateway Server has blocked incoming requests from this IP address because the number of requests from this address has exceeded the specified Enterprise Gateway Denial of Service limits.

Action

Wait for the IP address to become unblocked when the block interval elapses. If an IP address is blocked too often, reevaluate the "maximum requests" and "maximum requests in progress" limits.

JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+DOS_IP_IN_PROGRESS_EXCEEDED Requests from IP address {0} have exceeded the maximum in-progress limit of {1}.
Class E
Explanation

Enterprise Gateway Server will deny or block incoming requests from this IP address because the number of requests from this address has exceeded the specified Enterprise Gateway Denial of Service limit for in-progress requests.

Action

Delete the IP address from the Enterprise Gateway deny list.

JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+DOS_CLEANUP Denial of Service clean-up task has executed.
Class D
Explanation

Periodically, Enterprise Gateway Server starts a task to clear old Denial of Service entries from the queue.
Action

No action is needed.
JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+DOS_GLOBAL_FAILED Global Denial of Service limits were reached: {0}.
Class E
Explanation

Enterprise Gateway Server will block incoming requests received from all IP addresses because the number of requests has exceeded the specified Enterprise Gateway global Denial of Service limits.

Action

Wait for the block interval to elapse.
JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+DOS_IP_REQUEST_LIMIT_EXCEEDED Requests from IP address {0} have exceeded the maximum request limit of {1} in {2} seconds.
Class E
Explanation

Enterprise Gateway Server will deny or block incoming requests from this IP address because the number of requests from this address has exceeded the specified Enterprise Gateway Denial of Service limit for requests allowed in a specified time period.

Action

Delete the IP address from the Enterprise Gateway deny list.

JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+DOS_GLOBAL_IP_BLOCK Requests from all IP addresses will be blocked for a duration of {0} minutes.
Class S
Explanation

Enterprise Gateway Server will block incoming requests received from all IP addresses for the indicated interval because the number of requests has exceeded the specified Enterprise Gateway global Denial of Service limits.

Action

Wait for the block interval to elapse.
JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+OAUTH_FILTER_FAILED OAuth token is not present in the request header.
Class E
Explanation

Enterprise Gateway Server could not process the request because the OAuth token is not present in the request header.
Action

Either disable the OAuth filter or ensure that the request contains the OAuth token.
JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+DOS_GLOBAL_IN_PROGRESS_EXCEEDED Maximum in-progress limit of {0} has been exceeded.
Class E
Explanation

Enterprise Gateway Server will block incoming requests received from all IP addresses because the number of requests has exceeded the specified Enterprise Gateway global Denial of Service limit for in-progress requests.

Action

Wait for the block interval to elapse.
JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+DOS_GLOBAL_REQUEST_LIMIT_EXCEEDED Maximum requests limit of {0} in {1} seconds has been exceeded.
Class E
Explanation

Enterprise Gateway Server will block incoming requests received from all IP addresses because the number of requests has exceeded the specified Enterprise Gateway global Denial of Service limit for requests allowed in a specified time period.

Action

Wait for the block interval to elapse.
JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+MOBILE_APP_HEADER_MISSING The header "{0}" is not present in the request header.
Class E
Explanation

Enterprise Gateway Server could not process the request because the indicated header is not present in the request header.
Action

Either disable the mobile application protection filter or ensure that the request has the required mobile device type, application name, and application version request headers.

JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+MOBILE_APP_FILTER_FAILED Mobile application version {0} is {1} {2} for application "{3}" and device type "{4}".
Class E
Explanation

Enterprise Gateway Server could not process the request because the request matches the indicated mobile application protection filter condition. As a result, the request is in violation of the Enterprise Gateway rule.

Action

Reevaluate the mobile application protection filter conditions if desired.
JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+ALERT_NOTIFIER_NOTIFICATION_ERROR Exception occurred while sending a notification for Enterprise Gateway rule "{0}": {1}.
Class S
Explanation

Enterprise Gateway Server could not send an alert notification indicating that a rule violation occurred for the reason indicated in the exception.

Action

Check the server error logs and take corrective steps.

JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+ALERT_NOTIFIER_INVOKE_ERROR Exception occurred while invoking "{0}": {1}.
Class S
Explanation

Enterprise Gateway Server could not invoke the flow service to notify users that a rule violation occurred for the reason indicated in the exception.

Action

Check the server error logs and take corrective steps.

JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+ALERT_NOTIFIER_NO_ALERT_OPTION_FOUND Alert notification for Enterprise Gateway rule "{0}" was not sent. No alert options were found for the rule.
Class W
Explanation

Enterprise Gateway Server could not send an alert notification indicating that a rule violation occurred because no alert options were specified for the rule to indicate how to handle the alert.

Action

Check the server error logs and take corrective steps.
JournalLogger.FAC_ENTERPRISE_GATEWAY_RULES+"."+ALERT_NOTIFIER_INVALID_SMTP_SERVER_CONFIGURATION Alert notification for Enterprise Gateway rule "{0}" was not sent. SMTP server configuration is not valid.
Class W
Explanation

Enterprise Gateway Server could not send an alert notification for the Enterprise Gateway rule because the server is not configured to send emails.

Action

Check the settings on the Settings > Resources screen under Email Notification. If your server is not configured to send emails, use Integration Server Administrator to configure an SMTP port.

DUPLICATE_RULE_NAME Enterprise Gateway rule "{0}" already exists.
Class E
Explanation

Enterprise Gateway Server could not create the rule because an Enterprise Gateway rule with this name already exists.
Action

Specify a unique name for the Enterprise Gateway rule.
RULE_NOT_FOUND Enterprise Gateway rule "{0}" was not found
Class E
Explanation

Enterprise Gateway Server could not find the specified Enterprise Gateway rule. Either the rule does not exist on this server or the specified rule name is incorrect.

Action

Ensure that the Enterprise Gateway rule exists on this Enterprise Gateway Server and that the name specified for the rule is correct.

MOBILE_APP_NO_DEVICE Mobile application protection filter conditions were not specified.
Class E
Explanation

Enterprise Gateway Server failed to create or update an Enterprise Gateway rule that has a mobile application protection filter enabled because no filter conditions were specified.

Action

Either specify one or more conditions or disable this filter.
MOBILE_APP_NOT_FOUND Mobile application "{0}" was not found.
Class E
Explanation

Enterprise Gateway Server did not recognize the application name provided in the mobile application protection filter because the application is not in the Mobile Applications list.

Action

Either specify a different mobile application or use the Mobile Application Protection Options screen in Integration Server Administrator to add the application.

MOBILE_DEVICE_NOT_FOUND Mobile device type "{0}" was not found.
Class E
Explanation

Enterprise Gateway Server did not recognize the device type provided in the mobile application protection filter because the device is not in the Device Types list.

Action

Specify a different device type or use the Mobile Application Protection Options screen in Integration Server Administrator to add the device type.

CONDITION_NOT_SUPPORTED Condition "{0}" is not supported.
Class E
Explanation

Enterprise Gateway Server failed to apply the condition to this Enterprise Gateway rule because the condition character specified in the mobile application protection filter is not valid.

Action

Ensure that the condition is one of the following characters: =,<,>,<=,>=,<>
MOBILE_APP_INVALID_VERSION Mobile application version "{0}" is not valid.
Class E
Explanation

Enterprise Gateway Server failed to apply the condition to this Enterprise Gateway rule because the application version specified in the mobile application protection filter is not formatted correctly.

Action

Ensure that the application version is in the following format: <major-version>.<minor-version>.<sub-minor-version>.<patch>

MOBILE_APP_UPDATE_FAILED Mobile applications list was not updated. The following applications are specified in one or more rules: {0}.
Class E
Explanation

Enterprise Gateway Server failed to remove mobile applications from the application list because the applications are specified in a filter condition for one or more rules.

Action

Before you attempt to remove a mobile application from the list, make sure the application is not specified in a filter condition in any rules.

MOBILE_DEVICE_UPDATE_FAILED Device types list was not updated. The following device types are specified in one or more rules: {0}.
Class E
Explanation

Enterprise Gateway Server failed to remove device types from the device types list because the device types are specified in a filter condition for one or more rules.

Action

Before you attempt to remove a device type from the list, make sure the device type is not specified in a filter condition in any rules.

ALERT_OPTION_INVALID_SERVICE_NAME Invalid service name {0}.
Class E
Explanation

The flow service name that you specified as the Mobile Gateway flow service alert option is invalid or does not exist.
Action

Ensure that the flow service you specify exists and is valid.
MISSING_REQUIRED_PARAMETER Missing required parameter: "{0}".
Class
Explanation

A required parameter was not supplied.
Action

Supply the specified required parameter.
UNABLE_TO_CREATE_PORT Unable to create port: "{0}".
Class
Explanation

Integration Server cannot create the port because an exception occurred.
Action

Use the specified exception to determine why the port could not be created.
UNABLE_TO_SET_PORT_IPACCESS_MODE Unable to set the IP access mode for the port: {0}
Class
Explanation

An error occurred during an attempt to set the IP access mode for the port.
Action

Use the exception returned by the error message to determine the cause of the error.
UNABLE_TO_SET_PORT_IPACCESS_LIST Unable to set the IP access list for the port: {0}
Class
Explanation

An error occurred while attempting to set the IP access list for the port.
Action

Use the exception returned by the error message to determine the cause of the error.
UNABLE_TO_SET_PORT_URLACCESS_MODE Unable to set the URL access mode for the port: {0}
Class
Explanation

An error occurred during an attempt to set the URL access mode for the port.
Action

Use the exception returned by the error message to determine the cause of the error.
UNABLE_TO_SET_PORT_URLACCESS_LIST Unable to set the URL access list for the port: {0}
Class
Explanation

An error occurred during an attempt to set the URL access list for the port.
Action

Use the exception returned by the error message to determine the cause of the error.
CANNOT_CHANGE_PRIMARY_PORT The primary port cannot be changed.
Class
Explanation

An update operation attempted to make changes to the primary port of the Integration Server. The primary port cannot be updated.
Action

To make changes to the port that is assigned to be the primary port, specify another port as the primary port. Then make changes to the port that was previously the primary port.

INVALID_PROTOCOL Invalid protocol. The webMethods Platform Manager subsystem does not support the protocol "{0}".
Class
Explanation

A create or update operation for port settings specified an protocol that is not supported by the webMethods Platform Manager subsystem in Integration Server.

Action

Specify a protocol supported by the webMethods Platform Manager subsystem in Integration Server.
CANNOT_CHANGE_PROTOCOL Cannot change port protocol [from {0} to {1}].
Class
Explanation

An update operation attempted to change the protocol for the port. Once a port is created, the protocol cannot be changed.
Action

To change the protocol used with a particular port, first delete the port. Then, recreate the port with the new protocol.
MUST_HAVE_VALID_PKG Package "{0}" is not loaded or is not enabled.
Class
Explanation

A create or update port operation attempted to create or change a port in a package that either does not exist or is not enabled.
Action

Make sure the package exists and is enabled before performing the create or update port operation.
UNABLE_TO_DISABLE_PORT Unable to disable port: {0}
Class
Explanation

An exception occurred during an attempt to disable the port
Action

Review the exception to determine why the port could not be disabled.
PORT_NOT_FOUND No port found with unique ID {0}.
Class
Explanation

A read, update, or delete port operation supplied a port ID that does not exist.
Action

Verify the instance ID that the Software AG Platform Manager associates with the port. To do this, refresh the port list on the Software AG Platform Manager.

CREATE_PARTIAL_ERR_ACCESS_MODE The port was created. However, the access configuration was not set: {0}
Class
Explanation

A create port operation was partially successful. The port was created and some configuration settings were established. However, establishing some or all of the access configuration settings failed. The port will be disabled if it is not already.

Action

Review the exception to determine why the access configuration could not be set.
UPDATE_PARTIAL_ERR_ACCESS_MODE The port was partially updated. However, the access configuration was not set: {0}
Class
Explanation

An update port operation was partially successful. Some settings were updated. However, updates to some or all of the access configuration settings failed. The port will be disabled if it is not already.

Action

Review the exception to determine why the access configuration settings could not be updated.
INVALID_PKG_FOR_DIAG The diagnostic port must be associated with the WmRoot package. Package {0} is invalid.
Class
Explanation

A create or update operation for the diagnostic port attempted to assign a package other than WmRoot to the diagnostic port. This is not allowed. The diagnostic port must be associated with the WmRoot package.

Action

Specify the WmRoot package when creating or updating the diagnostic port.
DIAG_PORT_ALREADY_REGISTERED Cannot create diagnostic port. A diagnostic port with port number {0} and ID {1} already exists. Each Integration Server can have one diagnostic port only.
Class
Explanation

An operation attempted to create a diagnostic port. However, the Integration Server already has a diagnostic port. Each Integration Server can have one diagnostic port only.

Action

To create a new diagnostic port, delete the existing diagnostic port first.
DIAG_PORT_CANNOT_CHANGED_TO_REGULAR_PORT Unable to update port. The diagnostic port cannot be changed to a standard port.
Class
Explanation

An operation attempted to change a diagnostic port to a standard port. A diagnostic port cannot be created in this way because the type of port may not be changed.

Action

To create a standard port on an assigned diagnostic port, first delete the existing diagnostic port and then create a standard port.

REGULAR_PORT_CANNOT_CHANGED_TO_DIAG_PORT Unable to update port. The standard port cannot be changed to a diagnostic port.
Class
Explanation

An operation attempted to change a standard port to a diagnostic port. A diagnostic port cannot be created in this way because the type of port may not be changed.

Action

To create a diagnostic port on an assigned port, first delete the existing port and then create a diagnostic port.
INVALID_KEYSTORE_ALIAS Invalid keystore alias {0}
Class
Explanation

A create or update port operation specified a keystore alias that does not exist.
Action

Make sure to specify the name of an existing keystore alias. Verify that the name of the keystore alias is spelled correctly.
INVALID_KEYSTORE_KEY_ALIAS Invalid key alias {0}
Class
Explanation

A create or update port operation specified a key alias that does not exist.
Action

Make sure to specify the name of an existing key alias. Verify that the name of the key alias is spelled correctly
INVALID_TRUSTSTORE_ALIAS Invalid truststore alias {0}
Class
Explanation

A create or update port operation specified a truststore alias that does not exist.
Action

Make sure to specify the name of an existing truststore alias. Verify that the name of the truststorealias is spelled correctly.
KEY_STORE_EMPTY_ENABLE_PORT_PARTIAL_ERR Cannot enable port. Keystore alias is empty. Specify a keystore alias for the port or a define a default SSL keystore alias for the Integration Server.
Class
Explanation

A create or update port operation did not specify a keystore alias and there is not a default SSL keystore alias for the Integration Server. An HTTPS port requires a keystore alias.

Action

Either define a keystore alias or specify a default SSL keystore alias for the Integration Server. The default SSL keystore alias is the keystore alias specified during configuration of the SSL authentication credentials for the Integration Server. To use a defined keystore alias with the HTTPS port, specify that keystore alias in the create or update operation. To use the Integration Server's default SSL keystore alias with the HTTPS port, do not supply keystore alias information for the create or update operations.

KEY_ALIAS_EMPTY_ENABLE_PORT_PARTIAL_ERR Cannot enable port. Keystore alias is empty. Specify a key alias for the port or a define a default SSL key alias for the Integration Server.
Class
Explanation

A create or update port operation did not specify a key alias and there is not a default SSL key alias for the Integration Server. An HTTPS port requires a key alias.

Action

Either define a key alias or specify a default SSL key alias for the Integration Server. The default SSL key alias is the keys alias specified during configuration of the SSL authentication credentials for the Integration Server. To use a defined key alias with the HTTPS port, specify that keystore alias in the create or update operation. To use the Integration Server's default SSL key alias with the HTTPS port, do not supply key alias information for the create or update operations.

UNABLE_TO_SET_PRIMARY Unable to assign primary port: "{0}".
Class
Explanation

An attempt to change the primary port failed because the selected port does not meet the primary port criteria mentioned in the wrapped exception.

Action

Select a port that meets the primary port requirements. Alternatively, change the chosen port to meet the primary port requirements mentioned in the wrapped exception.

UNABLE_TO_SET_QUIESCE Unable to assign quiesce port: "{0}".
Class E
Explanation

An attempt to change the quiesce port failed because the selected port does not meet the quiesce port criteria mentioned in the wrapped exception.

Action

Select a port that meets the quiesce port requirements. Alternatively, change the chosen port to meet the quiesce port requirements mentioned in the wrapped exception.

SPM_UNEXPECTED_ERROR The webMethods Platform Manager subsystem experienced an unexpected error: {0}
Class
Explanation

An error occurred in the webMethods Platform Manager subsystem that runs in Integration Server.
Action

Contact Software AG Global Support.
UNSUPPORTED_MODEL Unsupported MetaModelID: "{0}".
Class
Explanation

The specified MetaModelID is not supported.
Action

Check the Common Monitoring Provider (CMP) client that uses this API for additional information. It is also possible that the version of the CMP client using this API is not supported by this version of Integration Server

FAC+"."+DECODING_FAILURE Trigger {0} failed because of message decoding exception: {1}. Message has been acknowledged to messaging provider.
Class C
Explanation

The specified trigger could not decode a received document.

Action

Review the provided exception to determine why decoding failed.

FAC+"."+UM_BA_PWD_SAVE_EXCEP {0} failed to save password for handle {1}. Exception: {2}
Class E
Explanation

Integration Server was unable to save the password in the password store. This can occur if there is an issue with either the messaging.cnf file, which contains details about the connection alias, or the password store.

Action

Take appropriate action to resolve the problem described in the exception.
FAC+"."+UM_BA_PWD_RET_EXCEP {0} failed to retrieve password for handle {1}. Exception: {2}
Class E
Explanation

Integration Server was unable to retrieve the password from the password store. This can occur if there is an issue with either the messaging.cnf file, which contains details about the connection alias, or the password store.

Action

Take appropriate action to resolve the problem described in the exception.
FAC+"."+UM_AUTH_TYPE_RESET_TO_NONE Client authentication type for Universal Messaging connection alias {0} is not valid. Therefore, no authentication will be performed for this connection. Supported types: basic, none.
Class W
Explanation

The client authentication type provided for the specified Universal Messaging connection alias is not valid. As a result, Universal Messaging will use the default authentication type (“none”) and no authentication will be performed.

Action

Supply a valid authentication type (“none” or “basic”).
155.3 Unable to perform hot deployment of packages. Hot deployment timeout limit has expired while waiting for in-flight tasks to complete.
Class E
Explanation

Hot deployment of packages can happen only if the in-flight tasks are complete within the specified hot deployment timeout period.

Action

Increase the hot deployment timeout limit in the Settings > Hot Deployment page of the Integration Server Administrator. Alternatively, ensure that Integration Server is handling less load or requests.

155.5 Hot deployment of the system package {0} is not supported.
Class E
Explanation

You attempted to hot deploy a system package. Hot deployment can be performed only for custom packages.
Action

Ensure that the packages that you are attempting to hot deploy are not system packages.
155.8 Invalid input. Provide a valid positive integer as the hot deployment timeout value.
Class E
Explanation

The hot deployment timeout value must be a positive integer.

Action

Provide a valid positive integer as the hot deployment timeout value.
155.10 Cannot cancel the hot deployment operation. The installation of package has already started.
Class E
Explanation

You attempted to cancel the hot deployment operation after the installation of the package started. You can cancel the hot deployment operation only before the package installation starts.

Action

If you attempted to cancel the hot deployment because of the delay in the completion of in-flight tasks, this message indicates that the in-flight processes are now complete and Integration Server has started the hot deployment operation. No action required.<p>If the hot deployment operation is canceled because the new version of the package has issues, perform hot deployment of the previous version of the package from the salvage directory or perform hot deployment of a newer version of the package after correcting the issues.</p>

ISS.0157.0001 Package ''{0}'' is not loaded
Class E
Explanation

The specified package exists on Integration Server but is not enabled.
Action

Make sure the specified package is enabled. Then, re-execute the pub.assets:getChecksums service. Note that the service gets checksums only for assets that are loaded. If the specified package is partially loaded, the service gets checksums for the loaded assets only.

ISS.0157.0002 Package ''{0}'' does not exist
Class E
Explanation

The specified package does not exist on Integration Server .
Action

Make sure the specified package exists and is loaded. Then, re-execute the pub.assets:getChecksums service.

ISS.0157.0003 A value must be specified for either 'packages' or 'assets'
Class E
Explanation

A value was not specified for either the packages or assets input parameters. The pub.assets:getChecksums service requires a value for either packages or assets.

Action

Specify a value for the packages input parameter or the assets input parameter. Then, re-execute the pub.assets:getChecksums service.

MAX_THREADS_LT_CONNECTION_COUNT Maximum Execution Threads cannot be less than Connection Count.
Class E
Explanation

The value of the Maximum execution threads property is less than the value of the Connection count property. The Maximum execution threads value must be greater than or equal to the Connection count value.

Action

Change the value of the Maximum execution threads property to be greater than or equal to the Connection count property. Alternatively, change the value of the Connection count property to be less than or equal to the Maximum execution threads property.

CONNECTION_COUNT_NO_TOPICS The Multiple Connection feature is not supported when using non-durable Topics.
Class E
Explanation

Only JMS triggers that subscribe to queues and/or topics (durable subscribers) can use multiple connections to receive messages from the JMS provider. A JMS trigger that subscribes to a topic that is a non-durable subscriber cannot use multiple connections to receive messages from the JMS provider. That is, only a JMS trigger that subscribes to queues and/or topics that are durable subscribers can have a connection count greater than 1.

Action

Set Connection count to 1. Alternatively, remove any topics that are non-durable subscribers from the list of destinations to which the JMS trigger subscribes.

NO_TRANSPORT No transport info in MessageContext
Class E
Explanation

An internal error occurred while processing the Web service request.
Action

Contact Software AG Global Support.
NO_FORMATTER No MessageFormatter in MessageContext
Class E
Explanation

An internal error has occurred while processing the Web service request.
Action

Contact Software AG Global Support.
COULD_NOT_DEPLOY_WSD_AS_POLICY_NOT_FOUND Could not deploy the Web service descriptor {0} as policy with id {1} is not found.
Class E
Explanation

Integration Server was unable to execute the Web service connector because the WS-Policy attached to the Web service connector is either missing or invalid. Valid policies should be in the policy repository, that is, saved in the following directory: (webMethods_directory)/IntegrationServer/config/wss

Action

If you want to secure the Web service with the policy, locate the WS-Policy and add it to the policy repository. You can check the policy repository's invalid subdirectory to see whether the policy was moved because it is invalid. If the policy is in the invalid directory, correct it to make it valid, and move it back into the main policy repository directory.

If the WS-Policy does not exist, detach the WS-Policy from the Web service descriptor. If you still need to secure the Web service, create a WS-Policy that provides the security you want, add it to the policy repository, and attach it to the Web service descriptor.

PORT_ALIAS_CANNOT_BE_EDITED Port Alias cannot be edited.
Class E
Explanation

Once a port is created, the port alias cannot be changed.

Action

None. However, if you want an existing port to use a different port alias, you must delete the port and then recreate it using the new port alias.

UM_PROTOBUF_CODER_NO_DESCRIPTOR Protocol buffer coder cannot find descriptor in document type: {0}
Class E
Explanation

An error occurred while encoding or decoding an instance of the specified publishable document type. Integration Server cannot find the message descriptor for the publishable document type. Integration Server creates a message descriptor for a publishable document type with an encoding type set to protocol buffers.

Action

Make sure the publishable document type is synchronized with the messaging provider.

FAC+"."+SUBSCRIPTION_NOT_PRESENT Failed to unsubscribe because subscription does not exist for unique key "{0}".
Class E
Explanation

Subscription not found for the unique key \"{0}\".
FAC+"."+INVALID_CREATE_OPTION Provided options "{0}" are not valid.
Class E
Action

Provide valid options.
FAC+"."+EXCEPTION_WHILE_SERVICE_INVOKE Unable to invoke service "{0}" because of the exception: "{1}" .
Class E
Explanation

The exception message describes the cause.

Action

Check the exception message and take appropriate action.

FAC+"."+MISSING_SERVICE_NAME An error occured because the service name is not provided when the isAsync flag is set to true.
Class E
Explanation

An error occurs when service name is not provided and the isAsync flag is set to true.

Action

Provide a service name when isAsync flag is set to true.

FAC+"."+INVALID_USER An error occured because the user "{0}" is invalid or does not have the ACL permission to execute the service: "{1}".
Class E
Explanation

You have entered an invalid username or the user does not have necessary permissions to invoke the callback service.
Action

Enter a valid user name and check if the user has the necessary permissions to invoke the callback sevice.

FAC+"."+MISSING_ASYNC_FLAG An error occured because the service name is provided and the isAsync flag is set to false.
Class E
Explanation

An error occurs when service name is provided and the isAsync flag is set to false.

Action

Do not provide a service name when isAsync is set to false.

FAC+"."+EXCEPTION_WHILE_UNSUBSCRIBING Could not unsubscribe the subscription. The exception message is: "{0}".
Class E
Explanation

The exception message describes the cause.

Action

Check the exception message and take appropriate action.

FAC+"."+EVENT_ROUTING_SERVICE_UNAVAILABLE Event routing service is unavailable.
Class E
Explanation

An error occurred when initializing event routing service.
FAC+"."+INVALID_SUBSCRIBE_SERVICE Invalid Callback Service "{0}". Service should be invokable and should have reference to "{1}" document type as the only input.
Class E
Explanation

Callback service cannot be invoked and does not have reference to \"{1}\" document type.

Action

Ensure that the callback service can be invoked and has reference to \"{1}\" document type as the only input.

FAC+"."+DUPLICATE_SUBSCRIPTION Subscription failed because subscription already exists for unique key "{0}"
Class E
INVALID_RECORD The specified document type {0} does not exist.
Class E
Explanation

The document type that you supplied as input to the service does not exist.
Action

Check the name of the document type that you are attempting to use to ensure you have the correct name. Then, specify a document type name that exists and re-invoke the service.

IDATA_VALIDATION_FAILED The structure of the document instance does not match the specified document type, {0}; validation failed.
Class E
Explanation

The service validates a document instance using the IS document type you supplied. However, the document instance does not have the structure specified by the IS document type. Validation of the document instance failed.

Action

Check the IS document type you are attempting to use to ensure you specifying the correct one. Then, re-invoke the service specifying the correct IS document type for the document instance.

UNEXPECTED_EXCEPTION Unexpected exception occurred: {0}
Class E
Explanation

The Web services stack, which is Integration Server code that performs Web service functionality, encountered an unexpected error.

Action

Read through the contents of the messages, and take corrective steps. If you are unable to resolve the issue, contact Software AG Global Support.

SOAP_FAULT_NOT_CREATED_PROPER Unexpected exception occurred while creating a fault message.
Class E
Explanation

Integration Server encountered an unexpected error. It was attempting to add a child fault element to a non-existing parent fault element.

Action

Contact Software AG Global Support.
SOAP_FAULT_BLCK_NOT_PRESENT The query for the fault element failed because its corresponding parent element is absent from the SOAP message.
Class E
Explanation

You attempted to query a SOAP message for SOAPFault elements. However, there is no parent element in the SOAP message for the queried item. For example, Integration Server will issue this error if you attempt to query for a fault code when there is no SOAPFault in the SOAP message.

Action

Ensure the SOAP message that you are attempting to process is valid. If the SOAP message is valid, contact Software AG Global Support.

ATTRIBUTE_NAME_IMPROPER The structure of the SOAP fault detail Document is not valid, resulting in the invalid attribute name: {0}; validation failed.
Class E
Explanation

A document representing the SOAP fault detail was passed to a service that handles SOAP faults, for example, the pub.soap.handler:addFaultBlock. The fault detail Document that was passed to the service has an invalid structure. An example of an invalid structure would be if the name in the Document instance that corresponds to an attribute is "@ns1:", but there is no local name for the attribute. In this example, there should have been additional text after the ":" that corresponds to a valid local name.

Action

Ensure that IS document instance for the SOAP fault detail is a proper representation of valid XML structure. Correct the SOAP fault detail Document and execute the service again.

NO_ISDOCUMENT_FOR_VALIDATION Validation requested, but no IS document type specified; validation failed.
Class E
Explanation

You specified that you want an input Document to be validated. However, you have not provided the document type that the service should use for validation. As a result, the validation failed.

Action

Invoke the service again. This time pass the document type to use for validation in the appropriate input parameter.
INVALID_INPUT Service executed with invalid input parameter {0} : {1}
Class E
Explanation

Execution of the service failed because the specified input parameter was passed an invalid value. The invalid value is displayed in the message.

Action

Invoke the service again, this time specifying a valid value for the input parameter.
IS_RUNTIME_EXCEPTION runtime exception occured. see error log for details.
122.6 Package ''{0}'' has deploy directory contents, but does not have a dependency on 'WmJBoss'
Class
JNDI_CONTEXT_NOT_INITIALIZED Cannot perform JNDI operation: JNDI context is not initialized.
JSONCODER_INVALID_DECODE_FOR_REAL Both decodeRealAsString and decodeRealAsDouble cannot be set to true.
JSONCODER_UNSUPPORTED_TOKEN Invalid state. Unsupported token found in the JSON input stream.
Explanation

The input stream does not contain valid JSON content.
Action

Provide valid JSON content in the input stream.
JSONSCHEMA_DOCUMENT_NOT_CREATED Could not create JSON document type - "{0}"
JSON_INVALID_INPUTS_REAL_AS_STRING_AND_DOUBLE Both decodeRealAsString and decodeRealAsDouble cannot be set to true.
JSON_INVALID_INPUT_REAL_AS_STRING Field decodeRealAsString if set , can only be true or false.
JournalLogger.FAC_SCHED+"."+DATABASE_VERSION_CHECK_FAILED Check of internal database failed: the current version {0} should be at least {1}
JournalLogger.FAC_SCHED+"."+DATABASE_VERSION_NOT_FOUND Check of internal database failed: version could not be found
LDAP_URL_INVALID_CHAR Directory url contain invalid charactors. {0}
LVLCHNG_COMP_CODE_INVALID Supplied "componentCode" is not valid.
LVLCHNG_COMP_CODE_NULL Parameter "componentCode" is required and it cannot be null.
LVLCHNG_LISTENER_NULL Parameter "listener" is required and it cannot be null.
NESTED_TRANS_NOT_SUPPORTED another tran active. nested tran disabled in settings
NODE_NS_NAME_EXISTS node_nsName already exists
NODE_NS_NAME_IS_INVALID node_nsName "{0}" is invalid
NODE_NS_NAME_IS_REQUIRED node_nsName is required
NODE_PKG_IS_INVALID node_pkg "{0}" is invalid
NODE_PKG_IS_REQUIRED node_pkg is required
NODE_TYPE_IS_INVALID Node "{0}" is not of type 'webMethods/WebSocket'
NOT_NSWEBSOCKETENDPOINTCLIENT_TYPE Provided NSWebSocketEndpointDescriptor is not of type Client
NOT_NSWEBSOCKETENDPOINTDESC_TYPE Provided NSName "{0}" is not a type of NSWebSocketEndpointDescriptor. Please provide the NSWebSocketEndpointDescriptor' NSName
NOT_NS_WEBSOCKET_ENDPOINT_CLIENT_TYPE Provided NSWebSocketEndpoint is not of type Client
NOT_NS_WEBSOCKET_ENDPOINT_TYPE Provided NSName "{0}" is not a type of NSWebSocketEndpoint. Please provide the NSWebSocketEndpoint' NSName
NO_LOADERS_FOUND Loader is not configured for the cache {1} contained within the cache manager {0}.
NO_MORE_EVENTS_AVAILABLE No more xml events avaiable
NO_OUTPUT_SIGNATURE no output signature
NO_TRANS_FOR_THREAD current thread not with any transaction
NO_WRITERS_FOUND Writer is not configured for the cache {1} contained within the cache manager {0}.
NS_SAME_NODE_EXISTS Similarly-named node "{0}" already in use
OAUTH_ONE_PREVENTS_OTHER {0} may not be specified if {1} is "{2}".
Class E
Explanation

The service failed because the specified input variable contains an invalid value combination. The invalid combination is listed in the message text.

Action

Enter a valid value combination for the input variable.
ON_BINARY_IS_INVALID onBinary "{0}" is invalid
ON_CLOSE_IS_INVALID onClose "{0}" is invalid
ON_CONNECT_IS_INVALID onConnect "{0}" is invalid
ON_ERROR_IS_INVALID onError "{0}" is invalid
ON_TEXT_IS_INVALID onText "{0}" is invalid
OPERATION_NOT_SUPPORTED_WITH_ALIAS {1} operation is not supported when connection alias type is {0}.
OPERATION_NOT_SUPPORTED_WITH_DES_ALIAS {0} operation is not supported when connection alias type is DES.
OTHER_THAN_SPACE_CHARACTERS_ENCOUNTERED Other than space characters encountered
PACKAGE_HOTDEPLOY_ACTIVATION_FAILED_ON_RECOVERY Package recovered but not activated.
Class E
Explanation

Hot deployment of the specified package failed. Integration Server recovered the package from the salvage directory, but was unable to activate the package.

Action

Check the logs for hot deployment failure messages or contact Software AG Global Support.
PACKAGE_HOTDEPLOY_AUTORECOVER_ERROR Package cannot be recovered, check server logs for details.
Class E
Explanation

Hot deployment of the specified package failed.
Action

Check the logs for hot deployment failure messages or contact Software AG Global Support.
PACKAGE_HOTDEPLOY_AUTORECOVER_FAILED Error during hot deployment of package {0}. Package cannot be recovered.
Class E
Explanation

Hot deployment of the specified package failed. Integration Server attempted to recover the package from the salvage directory but was unable to do so.

Action

Check the logs for hot deployment failure messages or contact Software AG Global Support.
PACKAGE_HOTDEPLOY_AUTORECOVER_SUCCESS Package recovered and activated.
Class I
PACKAGE_HOTDEPLOY_IN_PROGRESS Cannot hot deploy package {0}. Hot deployment of package {1} is already in progress.
Class E
Explanation

You attempted to hot deploy multiple packages in parallel. Integration Server does not support parallel hot deployment of packages.

Action

Integration Server does not support parallel hot deployment of packages. Ensure that you perform hot deployment of packages sequentially.

PACKAGE_HOTDEPLOY_TIMEOUT Cannot hot deploy package {0} due to error: {1}
Class E
Explanation

Hot deployment of the package failed due to the listed error.

Action

Review the error details provided in the message to determine the cause of the failure and take appropriate action, and then retry hot deploying the packages.

PACKAGE_SIZE_LIMIT Package size exceeds limit set by watt.server.package.maxSizeMB
PARSER_MUST_BE_ON_START_ELEMENT_TO_READ_NEXT_TEXT parser must be on START_ELEMENT to read next text
PASSWORDBADOLDPASSWORD Invalid user name or password.
Class E
Explanation

The specified user credentials are not valid.
Action

Provide a valid user name and password.
PASSWORD_EMPTY Password is empty. User(s) {0} not added.
Explanation

The Password field requires a value.
Action

Enter a valid password.
PASSWORD_EXPIRED Password expired.
PASSWORD_HANDLE_TIMED_OUT Could not create keystore/truststore, please try again
PASSWORD_UPDT_EMPTY Password is empty. Password was not changed.
Explanation

The Password field requires a value.
Action

Enter a valid password.
PDT_OUT_OF_SYNC Document type ''{0}'' is out of sync with Provider
PIECMNE0000 Error initializing ISAttributeValues. ISMonitoringContext cannot be null.
Explanation

The ISAttributeValues cannot be initialized because ISMonitoringContext is null.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0001 Error retrieving AttributeValue. The metaModelTypeID cannot be null or empty.
Explanation

The AttributeValue cannot be retrieved because metaModelTypeID is null or empty.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0002 Error retrieving AttributeValue. The attributeID cannot be null or empty.
Explanation

The AttributeValue cannot be retrieved because metaModelTypeInstanceID is null or empty.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0003 Error retrieving AttributeValue. The attributeID cannot be null or empty.
Explanation

The AttributeValue cannot be retrieved because attributeID is null or empty.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0004 Error retrieving attribute values. The attributeQuery object cannot be null.
Explanation

The attribute values cannot be retrieved because the attributeQuery object is null.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0005 Error retrieving attribute values. The modelType is invalid.
Explanation

The attribute values cannot be retrieved because the modelType is invalid.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0006 Error while destroying ISMonitoringContext. The ISMonitoringContext cannot be null.
Explanation

The ISMonitoringContext could not be destroyed because it is null.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0007 Error destroying ISMonitoringContext. Invalid ISMonitoringContext provided.
Explanation

The ISMonitoringContext could not be destroyed because it is not a valid instance of ISMonitoringContext.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0008 Error getting meta model. The metaModelTypeId cannot be null.
Explanation

The meta model could not be retrieved because the metaModelTypeID is null or empty.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0009 Error validating ISMonitoringContext. ISMonitoringContext cannot be null.
Explanation

The ISMonitoringContext could not be validated because it is null.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0010 Error validating ISMonitoring Context. Invalid ISMonitoringContext provided.
Explanation

The ISMonitoringContext could not be validated because it is not an instance of MonitoringContext.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0011 Error validating ISMonitoringContext. ISInputContext object is null.
Explanation

The ISMonitoringContext cannot be validated because the supplied ISInputContext object is null.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0012 Error validating ISMonitoringContext. ISInputContext is invalid.
Explanation

The ISMonitoringContext cannot be validated because the supplied ISInputContext object is invalid.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0013 Error validating ISMonitoringContext. Context host attribute cannot be null or empty.
Explanation

The ISMonitoringContext cannot be validated because the context has a host attribute that is null or empty.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0014 Error validating ISMonitoringContext. Context port attribute is invalid.
Explanation

The ISMonitoringContext cannot be validated because the context has an invalid port attribute.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0015 Error initializing ISModelInstance. ISMonitoringContext is null.
Explanation

An ISModelInstance cannot be initialized because the ISMonitoringContext is null.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0016 Error getting model instances. The metaModelTypeName is null or empty.
Explanation

The model instances cannot be retrieved because a metaModelTypeName is null or empty.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0017 Error getting model instances. Invalid metaModelTypeName.
Explanation

The model instances cannot be retrieved because a valid metaModelTypeName was not supplied.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0018 Error while initializing ISServerModel. ISMonitoringContext is null.
Explanation

The ISServerModel cannot be initialized because ISMonitoringContext is null.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0019 Error getting attributes for Integration Server. The modelInstanceListToQuery cannot be null.
Explanation

Integration Server attributes cannot be retrieved because the modelInstanceListToQuery was null .
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0020 Error getting Integration Server attributes. The attributeListToQuery cannot be null.
Explanation

The Integration Server attributes cannot be retrieved because the attributeListToQuery was null.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0021 Error getting attributeID. The attributeID cannot be null.
Explanation

The Integration Server attribute cannot be retrieved because the attributeID was null.
Action

This is an internal error. Contact Software AG Global Support.
PIECMNE0022 Error while pinging Integration Server. Invalid ISMonitoringContext.
Explanation

The ping of Integration Server failed because the provided ISMonitoringContext is invalid.
Action

This is an internal error. Contact Software AG Global Support.
PIESIME0000 Unable to access Integration Server:{0}
Explanation

An error occurred while attempting to access Integration Server. The details of the error will replace the {0} in the message text.

Action

Use the details of the error to resolve the error preventing a connection to Integration Server.
PIESIME0001 Integration Server is unavailable:{0}
Explanation

An error occurred while attempting to access Integration Server. The details of the error will replace the {0} in the message text.

Action

Use the provided error information to correct the issue and try again.
PIESIME0002 An error occurred while invoking a service on Integration Server:{0}
Explanation

An error occurred while invoking a service on Integration Server. The details of the error will replace the {0} in the message text.

Action

Use the supplied error information to correct the condition causing the error. Then, reissue the service request.
PIESIME0004 Port object cannot be null.
Explanation

ISContext cannot be created because the Port object is null.
Action

Provide a valid Port object that is not null.
PIESIME0005 UserCredentials username/password cannot be null.
Explanation

ISContext cannot be created because the username/password is null.
Action

Make sure that the username/password has a valid value and is not null.
PIESIME0006 Missing required ClientAuthType for SSL.
Explanation

ISContext cannot be created because the ClientAuthType required for SSL is null.
Action

Make sure the ClientAuthType has a valid value and is not null.
PIESIME0007 Invalid protocol. The webMethods Platform Manager subsystem does not support the protocol "{0}".
Explanation

A create or update operation for port settings specified a protocol that is not supported by the webMethods Platform Manager subsystem in Integration Server.

Action

Specify a protocol supported by the webMethods Platform Manager subsystem in Integration Server.
PIESIME0008 Unable to connect Integration Server:{0}
Explanation

An error occurred while attempting to connect Integration Server. The details of the error will replace the {0} in the message text.

Action

Use the error details to resolve the error that is preventing a connection to Integration Server.
PIESIME0009 Port Validation Error :{0}
Class E
Explanation

The port configuration is not valid.
Action

Make sure the port configuration is valid.
PIESIME0010 Port Validation Error, Invalid URLAccess Service :{0}
Explanation

The port is not valid because the supplied URLAccess does not have a valid service name.

Action

Specify a valid service name for URLAccess.
PIESIME0011 Port Validation Error, Invalid IPAccess Hostname :{0}
Explanation

The port is not valid because the IPAccess Hostname is not valid.

Action

Specify a valid value for the IPAccess Hostname.

PIESIME0012 Port Validation Error, Port Alias already exists : {0}
Explanation

The port is not valid because the port alias is used by another port on Integration Server.
Action

Specify a port alias that is unique for the Integration Server.
PIESIME0013 Port Validation Error, Primary port may not be disabled in an update.
Explanation

A primary port cannot be disabled as part of an update.
Action

Do not attempt to disable the primary port as part of updating a port. If you want to disable the port acting as the primary port, you must first designate another port as the primary port. Then you can disable the port that was previously the primary port.

PIESIME0014 Port Validation Error, Primary port package name must be WmRoot. Invalid Package Name : {0}
Explanation

The primary port must be associated with the WmRoot package.
Action

Make sure the primary port is associated with the WmRoot package.
PIESIME0015 Invalid server configuration parameter names: {0}
Explanation

The server configuration parameter names must begin with “watt.”
Action

Rename the server configuration parameter names so that they begin with “watt.”
PIESIME0016 A required configuration parameter is missing: {0}
Explanation

A required configuration parameter is missing.
Action

Check the logs.
PIESIME0017 Configuration details for COMMON-JDBC cannot be null.
Explanation

While creating a JDBC pool alias, the configuration details for COMMON-JDBC cannot be null.
Action

Provide valid JDBC pool alias configuration details.
PIESIME0018 JDBC pool alias cannot be null or empty.
Explanation

While creating or updating a JDBC pool, the pool alias cannot be null or empty.
Action

Provide a valid value for the JDBC pool alias.
PIESIME0019 Invalid configuration type.
Explanation

The configuration type provided while creating the JDBC pool alias must be of type COMMON-JDBC.
Action

Provide a valid configuration of type COMMON-JDBC.
PIESIME0020 Invalid configuration type.
Explanation

The configuration type provided while updating the JDBC pool alias must be of type COMMON-JDBC.
Action

Provide a valid configuration of type COMMON-JDBC.
PIESIME0021 JDBC pool cannot be null.
Explanation

While creating a JDBC pool alias,the pool configuration details cannot be null.
Action

Provide valid configuration details while creating or updating a JDBC pool.
PIESIME0022 {0} cannot be null or empty.
Explanation

The specified value must not be null or empty
Action

Provide a valid value.
PIESIME0023 Enter a positive number for {0}
Explanation

The specified value must not be a negative number.
Action

Specify a positive number.
PIESIME0024 JDBC configuration instance id is missing.
Explanation

JDBC configuration instance id is required and must be specified.
Action

Provide a valid JDBC configuration instance id.
PIESIME0025 MaxSize must be greater than 0.
Explanation

The value provided for MaxSize must be greater than 0.
Action

Ensure that the value provided for MaxSize is greater than 0.
PIESIME0026 Configuration details for COMMON-JDBC cannot be null.
Explanation

While updating a JDBC pool alias, the configuration details for COMMON-JDBC cannot be null.
Action

Provide valid JDBC pool alias configuration details.
PIESIME0027 JDBC pool cannot be null.
Explanation

While updating a JDBC pool alias,the pool configuration details cannot be null.
Action

Provide valid configuration details while creating or updating a JDBC pool.
PIESIME0028 MinSize must be less than or equal to MaxSize.
Explanation

Minimum connections must be less than or equal to maximum connections.
Action

Ensure that the value provided for MinSize is less than or equal to MaxSize.
PIESIME0029 Invalid SMTP port.
Explanation

SMTP port should be greater than 0.
Action

Change the SMTP port to a valid value greater than 0.
PIESIME0030 Unable to retrieve truststores.
Explanation

Integration server is unable to retrieve the truststores.
Action

Ensure that there are truststores installed in Integration server.
PIESIME0031 SMTP settings are already defined.
Explanation

Unable to define new SMTP settings because the SMTP settings are already defined.

Action

To specify new SMTP settings, update the existing SMTP configuration.
PIESIME0032 The truststore {0} does not exist.
Explanation

The specified truststore alias cannot be found.
Action

Ensure that the specified truststore exists in Integration Server.
PIESIME0033 Configuration details for COMMON-DBFUNCTION cannot be null.
Explanation

While updating a functional alias, the configuration details for COMMON-DBFUNCTION cannot be null.
Action

Provide valid functional alias configuration details.
PIESIME0034 Invalid configuration type.
Explanation

The configuration type provided while updating the functional alias must be of type COMMON-DBFUNCTION.
Action

Provide a valid configuration of type COMMON-DBFUNCTION.
PIESIME0035 Functional alias cannot be null
Explanation

While updating a functional alias,the functional alias configuration details cannot be null.
Action

Provide valid configuration details while updating a functional alias.
PIESIME0037 Configuration details for COMMON-JNDI cannot be null.
Explanation

While configuring a JNDI provider alias, the configuration details for COMMON-JNDI cannot be null.
Action

Provide valid JNDI provider alias configuration details.
PIESIME0038 Invalid configuration type.
Explanation

The configuration type provided while configuring a JNDI provider alias must be of type COMMON-JNDI.
Action

Provide a valid configuration of type COMMON-JNDI.
PIESIME0039 SMTP server not configured.
Explanation

SMTP server is not configured in Integration Server.
Action

Configure SMTP server in Integration Server.
PIESIME0040 Functional alias specified is not valid.
Explanation

The functional alias specified in the input must be valid.
Action

Ensure that the functional alias specified in the input is valid.
PIESIME0041 Functional alias description cannot be modified.
Explanation

The functional alias description specified in the input cannot be modified.
Action

Ensure that the functional alias description specified in the input is not modified.
PIESIME0042 The functional alias {0} cannot be associated with the embedded database pool.
Explanation

The embedded database pool can only be used with IS Internal and Cross Reference database components.
Action

Associate the functional alias with any JDBC connection pool other than the embedded database pool.
PIESIME0043 Invalid configuration details for COMMON-JMS. Invalid value for {0}.
Explanation

The value specified for COMMON-JMS configuration {0} is not valid.
Action

Specify valid values for all the mandatory attributes in COMMON-JMS configuration.
PIESIME0045 Configuration details for COMMON-JMS cannot be null.
Explanation

The configuration details for COMMON-JMS cannot be null.

Action

Provide valid JMS configuration details.
PIESIME0046 Invalid configuration provided while updating the COMMON-JMS configuration.
Explanation

The JMS alias configuration provided while updating the COMMON-JMS configuration does not match the existing JMS alias configuration.
Action

Provide a valid JMS configuration that matches the JMS configuration to be updated.
PIESIME0047 An error occurred while invoking a service in Integration Server : {0}
Explanation

An error occurred while invoking a service in Integration Server. Error {0} occurred.
Action

Use the supplied error information to correct the condition causing the error. Then, reissue the service request.
PIESIME0048 JMS alias {0} should be disabled before {1} operation.
Explanation

The JMS alias {0} should be disabled before performing the {1} operation.
Action

Ensure that the JMS alias is disabled.
PIESIME0049 Messaging connection alias {0} should be disabled before {1} operation.
Explanation

The messaging connection alias {0} should be disabled before performing the {1} operation.
Action

Ensure that the messaging connection alias is disabled.
PIESIME0050 Messaging connection alias description cannot be null or empty.
Explanation

While creating a messaging connection alias, the description field cannot be null or empty.
Action

Provide a valid description for messaging connection alias.
PIESIME0051 Messaging connection alias name cannot be updated.
Explanation

You attempted to update the messaging connection alias. Messaging connection alias name is not editable.
Action

To change the name of a messaging connection alias, delete the existing messaging connection alias and create a new alias.
PIESIME0052 Default messaging connection alias cannot be deleted.
Explanation

The messaging connection alias that you attempted to delete is the default messaging connection alias, which cannot be deleted.
Action

To delete a default messaging connection alias, configure another messaging connection alias as the default.
PIESIME0053 Cannot create a new messaging connection alias for Broker.
Explanation

Only one messaging connection aliases for Broker can exist at a time in Integration Server.
Action

Delete the existing messaging connection aliases for Broker before creating a new messaging connection aliases for Broker.
PIESIME0057 Logger name for COMMON-LOGGERS configuration type is invalid.
Explanation

Valid values of logger name for COMMON-LOGGERS configuration type are {0}.
Action

Ensure that you specify a valid logger name when updating the COMMON-LOGGERS configuration type.
PIESIME0058 Server logger cannot be disabled.
Explanation

You attempted to disable the server logger. Server logger cannot be disabled.
Action

Ensure that the server logger is enabled.
PIESIME0059 Destination for server log entries must be a file.
Explanation

The destination for server log entries can only be a file.
Action

Ensure that you specify a file as the destination for server log entries.
PIESIME0060 Mode for writing server log entries must be synchronous.
Explanation

The server logger writes log entries synchronously to the specified destination file. Therefore, the mode for writing server log entries must be specified as synchronous.

Action

Ensure that the mode for writing server log entries is specified as synchronous.
PIESIME0062 The destination for writing Integration Server log entries must be database or file.
Explanation

Integration Server logger writes log entries to database or file only. You attempted to specify a destination other than database or file.

Action

Ensure that you specify database or file as the destination for writing Integration Server log entries.
PIESIME0063 Configuration details for COMMON-VARS cannot be null.
Explanation

While creating a global variable, the configuration details for COMMON-VARS cannot be null.
Action

Provide valid global variable configuration details.
PIESIME0064 Invalid configuration type.
Explanation

The configuration type provided while creating the global variable must be of type COMMON-VARS.
Action

Provide a valid configuration of type COMMON-VARS.
PIESIME0065 Global variable validation error: Variable Setting cannot be empty.
Explanation

The global variable configuration is not valid.
Action

Make sure that Variable Setting is not empty and that the global variable configuration is valid.
PIESIME0066 Global variable validation error: Integration Server accepts only Strings as global variable values.
Explanation

The global variable value specified is not of type String.
Action

Provide a valid value of type String for the global variable.
PIESIME0067 Global variable validation error: Global variable value cannot be empty.
Explanation

The global variable value must not be empty.
Action

Provide a valid value for the global variable.
PIESIME0068 Global variable validation error: Global variable value cannot exceed 255 characters.
Explanation

The global variable value that you specified contains more than 255 characters.

Action

Ensure that length of the global variable value is less than or equal to 255.
PIESIME0069 Global variable validation error: Global variable key cannot be empty.
Explanation

The global variable key must not be empty.
Action

Provide a valid key for the global variable.
PIESIME0070 Global variable validation error: Global variable key cannot exceed 255 characters.
Explanation

The global variable key that you specified contains more than 255 characters.

Action

Ensure that length of the global variable key is less than or equal to 255.
PIESIME0071 Global variable validation error: Global variable key contains special characters other than "." and "_".
Explanation

The global variable key that you specified contains special characters other than period (.) or underscore(_).
Action

Ensure that the global variable key does not contain any special characters other than period or underscore(_).
PIESIME0072 Invalid value for ServiceLogLevel in Service Logger.
Explanation

The value specified for ServiceLogLevel in Service Logger is not valid. Valid values for ServiceLogLevel are perSvc, brief, and verbose.

Action

Ensure that you specify a valid value for ServiceLogLevel in Service Logger.
PIESIME0073 Invalid value for GenerateAuditingDataOnStartup in Security Logger.
Explanation

The value specified for GenerateAuditingDataOnStartup in Security Logger is not valid. The GenerateAuditingDataOnStartup value must be a valid Boolean value (true/false).

Action

Ensure that you specify a valid value for GenerateAuditingDataOnStartup in Security Logger.
PIESIME0074 Invalid value for GenerateAuditingDataOnEvent in Security Logger.
Explanation

The value specified for GenerateAuditingDataOnEvent in Security Logger is not valid. Valid values for GenerateAuditingDataOnEvent are Success or Failure, Success, and Failure.

Action

Ensure that you specify a valid value for GenerateAuditingDataOnEvent in Security Logger.
PIESIME0075 Invalid value for SecurityAreasToAudit in Security Logger.
Explanation

The value specified for SecurityAreasToAudit in Security Logger is not valid. Valid values for SecurityAreasToAudit are {0}.
Action

Ensure that you specify a valid value for SecurityAreasToAudit in Security Logger.
PIESIME0076 Unable to disable messaging connection alias.
Explanation

An operation to disable messaging connection alias failed.
Action

Check the Integration Server logs for more information.
PIESIME0077 Configuration details for COMMON-CLUSTER cannot be null.
Explanation

When updating cluster settings, the configuration details for COMMON-CLUSTER cannot be null.
Action

Provide valid cluster configuration details.
PIESIME0078 Invalid configuration type.
Explanation

When updating the cluster settings, the provided configuration type must be COMMON-CLUSTER.
Action

Specify a configuration type of COMMON-CLUSTER when updating the cluster settings.
PIESIME0079 {0} is required.
Explanation

The required field value cannot be empty.
Action

Specify a value for the required field.
PIESIME0082 Session timeout must be a positive integer.
Explanation

The provided session timeout is not a positive integer.

Action

Specify a positive integer for session timeout.
PIESIME0083 Configuration details for {0} cannot be null.
Class E
Explanation

While creating a {0} web service endpoint alias, the configuration details for {1} cannot be null.
Action

Provide valid web service endpoint alias configuration details.
PIESIME0084 Invalid configuration type.
Explanation

The configuration type provided while creating {0} web service endpoint alias must be of type {1}.
Action

Provide a valid configuration type.
PIESIME0085 {0} Web service endpoint alias is not specified.
Explanation

{0} Web service endpoint alias is not specified.
Action

Specify a valid web service endpoint alias configured in Integration Server.
PIESIME0086 {0} Web service endpoint alias contains invalid characters.
Explanation

{0} Web service endpoint alias contains invalid characters.
Action

Specify a valid web service endpoint alias.
PIESIME0087 Host or port is not specified for {0} web service endpoint alias.
Explanation

Host or port is not specified for {0} web service endpoint alias.
Action

Specify a valid host and port for the web service endpoint alias.
PIESIME0088 Keystore alias or key alias is not valid.
Explanation

Keystore alias or key alias must be a valid alias configured in Integration Server.
Action

Specify a valid configured keystore alias or key alias.
PIESIME0089 Truststore alias is not valid.
Explanation

Truststore alias must be a valid alias configured in Integration Server.
Action

Specify a valid configured truststore alias.
PIESIME0090 {0} cannot be edited.
Explanation

You attempted to edit {0}, which cannot be edited.
Action

Ensure that the specified field is not edited.
PIESIME0092 Execute ACL is not valid.
Explanation

The specified Execute ACL does not exist.
Action

Specify a valid ACL.
PIESIME0093 Proxy server alias is not valid.
Explanation

Proxy server alias must be a valid alias configured in Integration Server.
Action

Specify a valid proxy server alias.
PIESIME0094 The proxy-bypass alias cannot be deleted.
Class E
Explanation

The default proxy alias, proxy-bypass, contains the proxy bypass addresses list and cannot be deleted.
Action

You cannot create or delete the proxy-bypass alias.
PIESIME0095 Invalid protocol specified. Protocol must be HTTP, HTTPS, FTP, or SOCKS.
Class E
Explanation

Protocol must be HTTP, HTTPS, FTP, or SOCKS.
Action

Specify HTTP, HTTPS, FTP, or SOCKS as the protocol.
PIESIME0096 Invalid FTP proxy type. The FTP proxy type must be an integer within the range of 0 and 7 (inclusive).
Class E
Explanation

FTP proxy type must be an integer within the range of 0 and 7 (inclusive).
Action

Specify an integer within the range of 0 and 7 (inclusive).
PIESIME0097 Only the NonProxyHosts field can be edited in the proxy-bypass alias.
Class E
Explanation

You attempted to edit the fields other than the NonProxyHosts field in the proxy-bypass alias.
Action

Ensure that you edit only the NonProxyHosts field in the proxy-bypass alias.
PIESIME0098 License key location cannot be updated.
Class E
Explanation

License key location cannot be updated.
Action

License key location cannot be updated.
PIESIME0099 The proxy server alias element for the existing configuration of type COMMON-PROXY cannot be updated.
Class E
Explanation

You attempted to update the alias element for the existing configuration of type COMMON-PROXY.
Action

The proxy server alias element is not editable.
PIESIME0102 File Access Permission configuration instance id cannot be null.
Explanation

File Access Permission configuration instance id is required and must be specified.
Action

Provide a valid File Access Permission configuration instance id.
PIESIME0103 Configuration details for IS-FILEPERMISSION cannot be null.
Explanation

While updating a file permission instance, the configuration details for IS-FILEPERMISSION cannot be null.
Action

Provide valid file permission configuration details.
PIESIME0104 Invalid configuration type.
Explanation

The configuration type provided while updating the file permission configuration must be of type IS-FILEPERMISSION.
Action

Provide a valid configuration of type IS-FILEPERMISSION.
PIESIME0105 Configuration details for IS-FILEPERMISSION cannot be null.
Explanation

While updating the file access control configuration, the configuration details for IS-FILEPERMISSION cannot be null.
Action

Provide valid file access control configuration details.
PIESIME0106 File permission type cannot be modified.
Explanation

While updating file access control configuration, the file permission type cannot be modified.
Action

Provide valid configuration details while updating the file access control configuration.
PIESIME0107 Logger Levels specified for Server Logger cannot be modified.
Explanation

You attempted to add or delete the Logger Levels specified for Server Logger.
Action

You cannot add or delete the Logger Levels specified for Server Logger.
PIESIME0108 Logger Level names and descriptions specified for Server Logger cannot be modified.
Explanation

You attempted to modify the Logger Level names or descriptions specified for Server Logger.
Action

You can modify only the Logger Level value for Server Logger.
PIESIME0109 Specify an {0} proxy server alias.
Class E
Explanation

Protocol of the proxy server alias that you specified and the transport type of the consumer web service endpoint alias must match.

Action

Specify an {0} proxy server alias.
PIESIME0110 Value of {0} must be a positive integer between 0 and {1} (inclusive).
Explanation

You specified an invalid value for {0}. Value of {1} must be a positive integer between 0 and {2} (inclusive).
Action

Ensure that you specify a positive integer between 0 and {1} (inclusive) as the value of {0}.
PIESIME0111 Alias of an Integration Server logger cannot be modified.
Explanation

You attempted to modify the alias of an Integration Server logger.
Action

You cannot modify the alias of an Integration Server logger.
PIESIME0112 Invalid timestamp format.
Explanation

The timestamp format must be supported by the Java class java.text.SimpleDateFormat.
Action

Specify any timestamp format that is supported by the Java class java.text.SimpleDateFormat.
PIESIME0113 Alias of a {0} cannot be modified.
Explanation

You attempted to modify the alias of a {0}.
Action

You cannot modify the alias of a {0}.

PIESIME0114 Remote server endpoint configuration details are not valid for {0}.
Class E
Explanation

The value specified for remote server endpoint {0} is missing or is not valid.
Action

Specify valid values for all mandatory remote server endpoint attributes.
PIESIME0115 Remote server endpoint configuration details cannot be null.
Class E
Explanation

Configuration details for a remote server endpoint cannot be null.
Action

Provide valid remote server endpoint details.
PIESIME0116 Remote server endpoint configuration could not be updated because the configuration details provided are not valid.
Class E
Explanation

The remote server endpoint configuration could not be updated because the provided configuration details are not valid.

Action

Specify valid values for all mandatory remote server endpoint attributes.
PIESIME0117 An error occurred while invoking a service in Integration Server: {0}
Class E
Explanation

Integration Server could not execute the service for the reason indicated.

Action

Check the reason detailed in the message, take appropriate corrective action, and reissue the service request.
PIESIME0118 Connection attempts to the remote server endpoint {0} failed.
Class E
Explanation

A connection error occurred while trying to connect to the remote Integration Server from the target server on which the remote server endpoint was created. Either the remote server is not available or the provided host name, port, or authentication credentials are not valid.

Action

Check the status of the remote server and restart the server if necessary. Ensure the configuration of the remote server endpoint is valid.

PIESIME0119 Invalid SOCKS protocol version.
Class E
Explanation

Supported SOCKS protocol versions are 4 and 5.
Action

Specify the SOCKS protocol version as either 4 or 5.
PIESIME0120 SOCKS protocol version 4 does not support authentication.
Class E
Explanation

You specified authentication credentials (i.e. username and password) for SOCKS protocol version 4.
Action

Do not specify authentication credentials (i.e. username and password) for SOCKS protocol version 4.
PIESIME0121 Messaging connection alias client prefix cannot be null or empty.
Explanation

While creating a messaging connection alias, the client prefix field cannot be null or empty.
Action

Provide a valid client prefix for messaging connection alias.
PIESIME0122 JAAS Context cannot be null or empty.
Explanation

You did not specify a valid JAAS login context for Kerberos authentication. The JAAS Context field must not be null or empty.
Action

Provide a valid JAAS login context for Kerberos authentication.
PIESIME0123 Service Principal Name Format cannot be null or empty.
Explanation

You did not specify a valid Service Principal Name Format. Service Principal Name Format must not be null or empty.
Action

Provide a valid Service Principal Name Format.
PIESIME0124 Proxy server alias contains invalid characters.
Explanation

The Proxy server alias name can contain only alphanumeric characters.
Action

Specify a proxy server alias name that contains only alphanumeric characters.
PIESIME0125 No LDAP server configuration is available in the target Integration Server or more than one LDAP servers are configured in the target Integration Server.
Explanation

Only one LDAP server must be configured in the target Integration Server.
Action

Add or remove LDAP server configurations to ensure that there is only one LDAP server configured in the target Integration Server.

PIESIME0126 An LDAP server is already configured in the target Integration Server.
Explanation

Only one LDAP server must be configured in the target Integration Server. There is already one or more than one LDAP servers configured in the target Integration Server.

Action

Ensure that there is only one LDAP server configured in the target Integration Server. Retain one LDAP server configuration and delete the rest.

PIESIME0127 The Maximum Connection Pool Size must be greater than the Minimum Connection Pool Size.
Explanation

The value specified for Maximum Connection Pool Size is lesser than the Minimum Connection Pool Size.
Action

Ensure that you provide a Maximum Connection Pool Size greater than the Minimum Connection Pool Size.
PIESIME0128 LDAP server configuration must contain either a default group or a group member attribute.
Explanation

While configuring the LDAP server, either a default group or a group member attribute must be specified.
Action

Ensure that you specify a default group or a group member attribute while configuring the LDAP server.
PIESIME0129 Invalid LDAP URL! Specify a LDAP URL that starts with ldap:// or ldaps:// and try again.
Explanation

Invalid LDAP URL specified in the Server configuration type for LDAP.
Action

Specify a valid URL in the Server configuration type for LDAP.
PIESIME0130 The Group Id attribute in the Server configuration type for LDAP cannot be null.
Explanation

The Group Id attribute is not provided in the Server configuration type for LDAP.
Action

Specify a Group Id attribute in the Server configuration type for LDAP.
PIESIME0131 Default JAAS Realm alias cannot be deleted.
Explanation

The JAAS Realm alias that you attempted to delete is the default Integartion server JAAS Realm, which cannot be deleted.
Action

Do not delete the default Integration Server JAAS Realm.
PIESIME0132 Specified JAAS Realm is already defined.
Explanation

Unable to define new JAAS Realm because the specified JAAS Realm is already defined.
Action

Specify new JAAS Realm.
PIESIME0133 Configuration details for COMMON-JAAS-Realm cannot be empty.
Explanation

The configuration details for COMMON-JAAS-Realm cannot be empty.
Action

Provide valid JAAS Realm details.
PIESIME0134 Provided JAAS Realm name is not same as the existing JAAS Realm name.
Explanation

Unable to update as provided JAAS Realm name does not match with the existing JAAS Realm name.
Action

To update a current JAAS Realm provide the same name as the existing one.
PIESIME0141 JMS Trigger State must be specified
Explanation

JMS Trigger State must be specified
Action

Provide the JMS Trigger state
PIESIME0142 JMS Trigger State must be Enabled or Disabled or Suspended
Explanation

JMS Trigger State must be Enabled or Disabled or Suspended
Action

Provide the JMS Trigger State
PIESIME0143 JMS Trigger Type must be specified
Explanation

JMS Trigger Type must be specified
Action

Provide the JMS Trigger Type
PIESIME0144 JMS Trigger Type must be All or Standard or SOAP
Explanation

Provided JMS Trigger Type must be All or Standard or SOAP
Action

Provide JMS Trigger Type
PIESIME0145 Thread Pool Throttle must be specified
Explanation

Thread Pool Throttle must be specified
Action

Provide value to the Thread Pool Throttle
PIESIME0146 Thread Pool Throttle must be an integer between 1 and 100
Explanation

Thread Pool Throttle must be an integer between 1 and 100
Action

Provide value to the Thread Pool Throttle between 1 and 100
PIESIME0147 Processing Throttle must be specified
Explanation

Processing Throttle must be specified
Action

Provide a value to the Processing Throttle
PIESIME0148 Processing Throttle must be an integer between 1 and 100
Explanation

Processing Throttle must be an integer between 1 and 100
Action

Provide a value to the Processing Throttle between 1 and 100
PIESIME0180 User {0} cannot be deleted.
Explanation

The predefined user {0} cannot be deleted.
Action

Provide a valid user name while deleting a User configuration.
PIESIME0181 User ID cannot be empty.
Explanation

User ID cannot be empty while adding, updating, and deleting a User configuration.
Action

Provide a valid user name while adding, updating, and deleting a User configuration.
PIESIME0182 User ID cannot be edited.
Explanation

You attempted to edit ID, which cannot be edited.
Action

Ensure that the specified field is not edited.
PIESIME0183 User {0} cannot be removed from the Group {1}.
Explanation

User {0} cannot be removed from the Group {1}.
Action

Provide a valid list of Groups while updating a User configuration.
PIESIME0184 User configuration instance ID cannot be null.
Explanation

User configuration instance ID is required and must be specified.
Action

Provide a valid User configuration instance ID.
PIESIME0185 Missing required configuration : User
Explanation

Missing required configuration : User
Action

Provide the required User configuration
PIESIME0186 Invalid property {0}.
Explanation

Invalid property {0}.
Action

Provide a valid property.
PIESIME0187 Invalid configuration type.
Explanation

The configuration type provided must be of type COMMON-LOCAL-USERS.
Action

Provide a valid configuration type.
PIESIME0188 Invalid configuration type.
Explanation

The configuration type provided must be of type IS-GROUPS.
Action

Provide a valid configuration type.
PIESIME0189 Group configuration instance ID cannot be null.
Explanation

Group configuration instance ID is required and must be specified.
Action

Provide a valid Group configuration instance ID.
PIESIME0190 Group name cannot be empty.
Explanation

Group name cannot be empty while adding, updating, and deleting a Group configuration.
Action

Provide a valid group name while adding, updating, and deleting a Group configuration.
PIESIME0191 Group {0} cannot be deleted.
Explanation

The predefined Group {0} cannot be deleted.
Action

Provide a valid Group name while deleting a Group configuration.
PIESIME0192 Group {0} cannot be edited
Explanation

The predefined Group {0} cannot be edited
Action

Provide a valid Group name while updating a Group configuration
PIESIME0193 Group name cannot be edited.
Explanation

You attempted to edit Group name, which cannot be edited.
Action

Ensure that the specified field is not edited.
PIESIME0194 User {0} cannot be added to Group {1}.
Explanation

User {0} cannot be added to Group {1}.
Action

Provide a valid list of Groups while updating a User configuration
PIESIME0195 Group {0} already exists.
Explanation

Group {0} already exists.
Action

Provide a valid Group name while creating a Group configuration.
PIESIME0196 Missing required configuration : Group
Explanation

Missing required configuration : Group
Action

Missing required configuration : Group
PIESIME0197 Group configuration instance ID cannot be null.
Explanation

Group configuration instance ID is required and must be specified.
Action

Provide a valid Group configuration instance ID.
PIESIME0198 The Group {0} does not exist.
Explanation

The specified Group cannot be found.
Action

Provide a valid name for Group configuration.
PIESIME0199 Missing required configuration : ACL
Explanation

Missing required configuration : ACL
Action

Missing required configuration : ACL
PIESIME0200 ACL configuration instance ID cannot be null.
Explanation

ACL configuration instance ID is required and must be specified.
Action

Provide a valid ACL configuration instance ID.
PIESIME0201 The ACL {0} does not exist.
Explanation

The specified ACL cannot be found.
Action

Provide a valid name for ACL configuration.
PIESIME0202 Invalid configuration type.
Explanation

The configuration type provided must be of type IS-ACLS.
Action

Provide a valid configuration type.
PIESIME0203 ACL name cannot be empty.
Explanation

ACL name cannot be empty while adding, updating, and deleting an ACL configuration.
Action

Provide a valid ACL name while adding, updating, and deleting an ACL configuration.
PIESIME0204 ACL {0} cannot be deleted.
Explanation

The predefined ACL {0} cannot be deleted.
Action

Provide a valid ACL name while deleting an ACL configuration.
PIESIME0205 ACL name cannot be edited.
Explanation

You attempted to edit ACL name, which cannot be edited.
Action

Ensure that the specified field is not edited.
PIESIME0206 ACL {0} already exists.
Explanation

ACL {0} already exists.
Action

Provide a valid ACL name while creating an ACL configuration.
PIESIME0207 Group {0} cannot be removed from {1} list of {2} ACL.
Explanation

Group {0} cannot be removed from {1} list of {2} ACL.
Action

Provide valid Group names for Allow and Deny list of an ACL configuration.
PIESIME0208 Group {0} cannot be added to {1} list of {2} ACL.
Explanation

Group {0} cannot be added to {1} list of {2} ACL.
Action

Provide valid Group names for Allow and Deny list of an ACL configuration.
PIESIME0209 Group created but User names are not valid.
Explanation

Group created but provided User names are not valid.
Action

Provide valid User names for the group.
PIESIME0210 Group name is not valid.
Explanation

Group name contains non-ASCII characters.
Action

Provide a valid group name.
PIESIME0211 User ID is not valid.
Explanation

User ID contains non-ASCII characters.
Action

Provide a valid user ID.
PIESIME0212 ACL name is not valid.
Explanation

ACL name contains non-ASCII characters.
Action

Provide a valid ACL name.
PIESIME0213 ACL created but Allow or Deny Group names are not valid.
Explanation

ACL created but provided Allow or Deny Group names are not valid.
Action

Provide valid Allow or Deny Group names for the ACL.
PIESIME0214 Allow or Deny Group names are not valid.
Explanation

Allow or Deny Group names provided are not valid.
Action

Provide valid Allow or Deny Group names while updating an ACL configuration.
PIESIME0215 User names are not valid.
Explanation

User names provided are not valid.
Action

Provide valid User names while updating a Group configuration.
PIESIME0216 LDAP or CDS groups cannot be deleted.
Explanation

LDAP or CDS groups cannot be deleted.
Action

Provide a valid Group name while deleting a Group configuration.
PIESIME0217 Provided value for ‘Action On Startup Error’ is not valid.
Explanation

Provided value for ‘Action On Startup Error’ is not valid. Supported values are ‘standalone’, ‘shutdown’, ‘quiesce’
Action

Provide a valid value for ‘Action On Startup Error’. Supported values are ‘standalone’, ‘shutdown’, ‘quiesce’
PIESIME0218 LDAP or CDS groups cannot be created or edited.
Explanation

LDAP or CDS groups cannot be created or edited.
Action

Provide a valid Group name while creating and updating a Group configuration.
PIESIME0219 Unable to create LDAP configuration as Central Directory Service is configured
Explanation

If Central Directory Service is configured, LDAP Configuration is not allowed
Action

Unconfigure Central Directory Service to add LDAP Configuration
PIESIMI0150 IS System Properties
Explanation

Java System Properties
PIESIMI0151 General Properties (alternative)
Explanation

General Properties (alternative)
PIESIMI0160 IS Groups
Explanation

IS Groups Configuration Type
PIESIMI0161 Groups
Explanation

Groups
PIESIMI0170 IS ACLs
Explanation

IS ACLs Configuration Type
PIESIMI0171 ACLs
Explanation

ACLs
PIESIMW0036 Unable to establish a connection using the specified JNDI provider alias.
Explanation

Integration Server is unable to establish a connection using the specified JNDI provider alias. For possible causes, check the server logs.

Action

Ensure that the JNDI provider is running and that the JNDI provider-specific libraries are used in Integration server.
PIESIMW0044 JMS alias {0} created successfully, but an error occurred while enabling the JMS alias.
Explanation

An error occurred while enabling JMS alias {0}. Check logs of integration server. Exception : {1}
Action

Check the Integration Server log to handle the exception manually.
PIESIMW0055 IS Resource settings updated successfully. If Broker is not configured, Broker-related settings will be ignored.
Explanation

IS Resource settings updated successfully. If Broker is not configured on Integration Server, all the Broker-related settings that you specified will be ignored.

Action

Ensure that Broker is configured if you want the Broker-related settings to be updated.
PIESIMW0056 Unable to read listeners.cnf file from package {0}.
Explanation

Unable to read the listeners.cnf configuration file while attempting to locate the port number for the specified port alias.
Action

No action is required. If the issue persists, contact Software AG Global Support.
PIPELINE_SAVE_ACCESSDENIED Save pipeline to file {0}, Access denied
POOL_NOT_EXIST Pool alias {0} does not exist.
Class I
PREFIX+String.valueOf(NEG_TIMEOUT_ERROR) Pool {0} cannot be initialized. The pool timeouts must not be negative.
PROPERTIES_CAN_NOT_BE_NULL properties can not be null
PROTOBUF_CODER_UNSUPPORTED_DATATYPE Protocol buffer coder cannot handle data type {0} for field {1} in document type: {2}. Error: {3}
PROXY_INVALID_SOCKS_AUTH SOCKS protocol version 4 does not support authentication.
PROXY_INVALID_SOCKS_VERSION Invalid SOCKS protocol version.
REMOTE_NO_ACTION Action missing, should be 'add' or 'edit'
REMOTE_NO_REGISTRY_TYPE No Registry type specifed
RESOURCE_CAN_NOT_BE_NULL resource can not be null
RESPONSE_ONE_OF_THREE_REQD "{0}" or "{1}" or "{2}" must be supplied
REVERSE_GATEWAY_NO_LICENSE Could not find a valid license for Enterprise Gateway.
Explanation

The Enterprise Gateway Server instance does not have a valid license for webMethods Enterprise Gateway.
Action

Check the terms of the license file.
ROLLBACK_FAILED_BAD_STATE Rollback failed due to status
RUN_AS_USER_IS_REQUIRED runAsUser is required
String.valueOf(TRAN_MSG)+"."+String.valueOf(ENLIST_FAILED) enlist failed: {0} xid = {1} rxid = {2}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(DELIST_FAILED) delist failed: {0} xid = {1} rxid = {2}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(COMMIT_FAILED) commit failed: {0} xid = {1} resource = {2}
Class E
Explanation

Integration Server transaction manager was unable to commit a two-phase commit (2PC) transaction to the backend XA resource.
Action

Check to see if the backend resource is connected to Integration Server. Then, if necessary, re-initiate the transaction.
String.valueOf(TRAN_MSG)+"."+String.valueOf(PREPARE_FAILED) prepare failed: {0} xid = {1} rxid = {2} vote = {3}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(ROLLBACK_FAILED) rollback failed: {0} xid = {1} resource = {2}
Class E
Explanation

The Integration Server transaction manager was unable to roll back a two-phase commit (2PC) transaction, most likely due to a resource issue.

Action

Check to see if the backend resource is connected to Integration Server. Then, if necessary, re-initiate the transaction.
String.valueOf(TRAN_MSG)+"."+String.valueOf(END_FAILED) end failed: {0} xid = {1} rxid = {2}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(DELIST_COMMIT_FAILED) delisted transaction commit failed: {0} xid = {1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(ONEPHASE_FAILED) one phase commit failed: {0} xid = {1} resource = {2}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(B4_COMPLETION_ERROR) sync beforeCompletion ran: {0} error: {1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(AFTER_COMPLETION_ERROR) sync afterCompletion ran: {0} error: {1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(MORE_THAN_1_LOCAL_TX) commit failed: more than 1 local trans enlisted. xid = {1} rxid = {2}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(DELISTED_WITH_TMFAIL) resource delisted with TMFAIL flag, transaction marked for rollback. xid = {0} rxid = {1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(TIMED_OUT) transaction timeout. xid = {0}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(UNABLE_TO_PERSIST) Unable to persist transaction status for xid = {0}: Exception: {1}
Class E
Explanation

The transaction recovery manager in Integration Server was unable to write the status of a two-phase commit (2PC) transaction to the disk-based XA recovery store.

Action

Investigate the following possible causes for the problem:

1) The operating system userid under which the Integration Server is running does not have write privileges to the XAStore directory.

2) There is not sufficient disk space for the directory.

3) The XA recovery store is corrupt. If this is the case, archive the files stored in the XA recovery store directory, mail them to Software AG Global Support, move the files in the XA recovery store to a backup directory, and restart Integration Server.

String.valueOf(TRAN_MSG)+"."+String.valueOf(UNABLE_TO_GET_TRANSACTIONS) Unable to get unrecovered transactions from persistent store. Exception:{0}
Class E
Explanation

The transaction recovery manager in Integration Server was unable to obtain a list of incomplete transactions from the XA recovery store. Integration Server uses this store to hold two-phase commit (2PC) transaction states for possible future recovery.

Action

Investigate the following possible causes for the problem:

1) The operating system userid under which Integration Server is running does not have write privileges to the XAStore directory.

2) There is not sufficient disk space for the directory.

3) The XA recovery store is corrupt. If this is the case, archive the files stored in the XA recovery store directory, mail them to Software AG Global Support, move the files in the XA recovery store to a backup directory, and restart the Integration Server.

String.valueOf(TRAN_MSG)+"."+String.valueOf(GOT_UNRECOVERD_TX) RecoveryManager found {0} unrecovered Transactions. Starting recovery.
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(TX_RECOVERY_STARTED) Recovery process started for Transaction Xid:{0}, Status: {1}.
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(TX_ROLLBACK_ERROR) Unable to rollback Xid:{0} during recovery for resource:{1}, transaction might been heuristically rolled back/commited by resource. Manual intervention might be required. Exception:{2}: Error Code:{3}.
Class E
Explanation

The transaction recovery manager in Integration Server detected a transaction whose status in Integration Server is different from the status stored in the back-end resource (for example, a database). This situation occurs when the transaction recovery manager tries to rollback a transaction that the back-end XA resource has already rolled back or committed.

Action

Check to see if the back-end resource administrator (for example a database administrator ) manually issued a rollback/commit for the incomplete transaction. If so, ensure that the other back-end XA resources do the same.

String.valueOf(TRAN_MSG)+"."+String.valueOf(TX_COMMIT_ERROR) Unable to commit Xid:{0} during recovery for resource:{1}, transaction might been heuristically rolled back/commited by resource. Manual intervention might be required. Exception:{2}.
Class E
Explanation

The transaction recovery manager of the Integration Server detected a transaction whose status in the Integration Server is different from the status stored in the back-end resource (for example, a database). This situation occurs when the transaction recovery manager tries to commit a transaction that the back-end XA resource has already rolled back or committed.

Action

Check to see if the back-end resource administrator (for example a database administrator) manually issued a rollback/commit for the incomplete transaction. If so, ensure that the other back-end XA resources do the same.

String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_CHECK_DATADEVICE) XARecoveryStore: Error during checkDataDevice. Db:{0} Error:{1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_RESIZED_RECOVER) XARecoveryStore: Resized Data file recovered. Db:{0}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_RESTORE_DATA) XARecoveryStore: Error restoring original data file. Db:{0} Error:{1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_RECOVER_ERR_SKIP) XARecoveryStore: Recoverable Error Skipped - warnonopen = continue. Db:{0} Error:{1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_RECOVER_ERR_FAIL) XARecoveryStore: Recoverable Error Encountered but warnonopen = fail. Db:{0} Error:{1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_DAMAGED_DATA) XARecoveryStore: Damaged data file detected. Db:{0} Error:{1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_REQUIRE_RESIZE) XARecoveryStore: Data file resize required. Db:{0}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_RESIZE_CLEAN_ERR) XARecoveryStore: Error cleaning up resized Data file. Db:{0} Error:{1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_RESIZE_CREATE_ERR) XARecoveryStore: Error creating resized Data file. Db:{0} Error:{1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_CLOSE_ORG_ERR) XARecoveryStore: Error closing original Data file. Db:{0} Error:{1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_CLOSE_RESIZE_ERR) XARecoveryStore: Error closing resized data file. Db:{0} Error:{1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_COPY_CLEAN_ERR) XARecoveryStore: Error cleaning up copied Data file. Db:{0} Error:{1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_RENAME_ORG_ERR) XARecoveryStore: Error renaming original data file. Db:{0} Error:{1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_FILE_RESIZE) XARecoveryStore: Data file resize completed. Db:{0}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_RENAME_RESIZE_ERR) XARecoveryStore: Error renaming resized data file. Db:{0} Error:{1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_COPY_RESIZE_ERR) XARecoveryStore: Error copying resized Data file. Db:{0}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_DAMAGE_RENAME) XARecoveryStore: Damaged data file renamed. Db:{0} renamed:{1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_DAMAGE_RENAME_ERR) XARecoveryStore: Error renaming damaged data file. Db:{0} Error:{1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_DAMAGE_DELETE) XARecoveryStore: Damaged data file deleted. Db:{0}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_DAMAGE_DELETE_ERR) XARecoveryStore: Error deleting damaged data file. Db:{0} Error:{1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_DAMAGE_RECREATE_ERR) XARecoveryStore: Error re-creating damaged data file. Db:{0} Error:{1}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(STORE_DAMAGE_RECREATE) XARecoveryStore: Damaged data file re-created. Db:{0}
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(INIT_XA_FAILURE) Unrecoverable Exception while initializing the XA Recovery Store: {0}
Class S
Explanation

Integration Server was unable to create a persistent XA recovery store on disk. Integration Server uses this store to hold two-phase commit (2PC) transaction states for possible future recovery.

Action

Investigate the following possible causes for the problem:

1) The operating system userid under which the Integration Server is running does not have write privileges to the XA recovery store directory.

2) There is not sufficient disk space for the directory.

3) The XA recovery store is corrupt. If this is the case, archive the files stored in the XAStore directory, mail them to Software AG Global Support, move the files in the XA recovery store to a backup directory, and restart the Integration Server.

String.valueOf(TRAN_MSG)+"."+String.valueOf(INIT_XA_STORE_NULL) XA Recovery Store could not be created.
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(UNABLE_TO_GET_RESOURCE) Unable to gain access to resource:{0} Error:{1}. Please verify that the Connection exists and is correctly configured.
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(UNABLE_TO_ROLLBACK) No transaction record found for Xid:{0} in resource:{1}. Transaction might have been commited or erased on resource:{1}. Unable to resolve as transaction might be in mixed state, requires manual intervention.
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(INVALID_GLBL_TX_STATUS) Invalid global transaction state for Xid:{0}. Unable to auto-resolve transaction, aborting recovery.
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(ABANDON_TIME_EXCEEDED) Transaction Xid:{0} exceeded abandon timeout setting, aborting recovery.
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(XA_SHUTDOWN_ERROR) Error while shutting down XA Recovery Store:{0}.
Class E
Explanation

The Integration Server XA recovery store did not shut down cleanly. Integration Server uses this store to hold two-phase commit (2PC) transaction states for possible future recovery.

Action

Restart Integration Server and examine the Server log for any error messages regarding the XARecovery Store. If the problem is a file permission or out of storage issue, correct the problem and restart the Integration Server. If the problem is not a file permission or out of storage issue, archive the contents of the XAStore directory and contact Software AG Global Support.

String.valueOf(TRAN_MSG)+"."+String.valueOf(XA_XARESOURCE_RECOVER_ERROR) Recover call on XAResource:{0} failed. Exception:{1}, Error Code:{2}
Class E
Explanation

The transaction recovery manager on Integration Server encountered an error when it tried to obtain a list of all incomplete XIDs known to the back-end resource. The error occurred because the back-end resource threw an exception.

Action

Check to see if the back-end resource is available and connected to Integration Server. The name of the resource will be the name of the connection defined in the adapter for the resource.

String.valueOf(TRAN_MSG)+"."+String.valueOf(TX_ACTIVE_NO_CLOSE) Active transaction detected while completing service {0}. Rolling back pending operations.
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(TX_ACTIVE_NO_CLOSE_CLEAN_TOPTRAN) Active resource detected while cleaning Top Transaction for service {0}. Rolling back pending operations.
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(TX_ACTIVE_AFTER_CLEANUP) Active transaction found with the thread after cleanup while completing service {0}. Check the cleanup process.
Class
String.valueOf(TRAN_MSG)+"."+String.valueOf(XA_LOGGING_MSG) XA Transaction Logging: {0}
Class
PREFIX+String.valueOf(TRAN_CLEANUP_ERROR) An error occurred while attempting to clean up transaction resources on connection {0}
Class
PREFIX+String.valueOf(CONN_RELEASE_ERROR) An error occurred while attempting to release connection {0}
Class
PREFIX+String.valueOf(POOL_CLOSE_ERROR) An error occurred while attempting to close connection pool {0}
Class
PREFIX+String.valueOf(POOL_OPEN_ASSERT_ERROR) Assertion error during creation of connection pool {0}
Class E
Explanation

An error occurred while allocating the managed connection because either the connection pool does not exist or the connection pool is empty for the managed connection factory.

Action

Ensure that the connection pool settings contain valid values. If the values are valid and if Integration Server is still unable create the connection pool, contact Software AG Global Support.

PREFIX+String.valueOf(POOL_RESET_ASSERT_ERROR) Assertion error during reset of connection pool {0}
Class
PREFIX+String.valueOf(CONN_REQ_ASSERT_ERROR) Assertion error during connection request from pool {0}
Class E
Explanation

An error occurred while allocating a connection to a request from the connection pool. This can happen if there are no available connections in the pool, if the managed connection factory does not exist, or if the conditions provided by the basic connection pool properties (such as pool size, minimum number of connections or maximum number of connections) are not met.

Action

Ensure the connection pool settings are valid. If the connection pool settings are valid and Integration Server is still unable to allocate a connection from the connection pool, contact Software AG Global Support.

PREFIX+String.valueOf(CONN_REQ_ERROR) An error occurred while attempting to retrieve a connection from {0}
Class
PREFIX+String.valueOf(NO_CONN_AVAILABLE) A connection was not available for request in pool {0}
Class
PREFIX+String.valueOf(CONN_HANDLE_FAIL) Failed to retrieve handle for connection {0}
Class
PREFIX+String.valueOf(DUPLICATE_CONNECTION) A duplicate connection returned from managed connection factory {0}
Class
PREFIX+String.valueOf(DATA_ASSERT_ERROR) A data level assertion occurred while managing connections for pool {0}
Class
PREFIX+String.valueOf(NEG_POOL_SIZE_ERROR) Pool {0} cannot be initialized. The pool sizes (min, max, increment) must not be negative.
Class
PREFIX+String.valueOf(MIN_POOL_SIZE_ERROR) Pool {0} cannot be initialized. The minimum pool size must be <= the maximum pool size.
Class E
Explanation

An error occurred while initializing the connection pool because the minimum number of connections is greater than the maximum number of connections allowed or the maximum number of connections is set to zero.

Action

Check the adapter connection pool settings to ensure the values for the minimum number of connections and maximum number of connections are valid. If the adapter connection pool settings are valid and the pool is still unable to initialize, contact Software AG Global Support.

PREFIX+String.valueOf(INVALID_FACTORY_ERROR) Pool {0} cannot be initialized. A valid ManagedConnectionFactory was not provided.
Class E
Explanation

An error occurred while checking basic properties for a connection pool because the managed connection factory for this pool is null.

Action

Check the connection pool settings to ensure that a valid connection factory is provided. If the settings are valid and the problem still exists, contact Software AG Global Support.

PREFIX+String.valueOf(CONN_DESTROY_ERROR) An error occurred while attempting to destroy connection {0}
Class E
Explanation

An error occurred while closing the database connection from the connection pool.
Action

This is an internal error. Contact Software AG Global Support.
PREFIX+String.valueOf(POOL_STATE_ERROR) Pool state error in {0}. Cannot process request.
Class E
Explanation

The next available connection cannot be obtained from the connection pool because the connection pool is disabled.
Action

Check the connection pool settings to ensure that the connection pool is enabled. If the connection pool is enabled and if Integration Server is still unable to obtain the next available connection from the connection pool, contact Software AG Global Support.

PREFIX+String.valueOf(CONN_CREATE_ERROR) An error occurred while attempting to create connections for {0}
Class E
Explanation

An error occurred while creating a new connection for the connection pool.
Action

Ensure that the resource database is running and the connection pool settings are valid. If the resource database is running and the connection pool settings are valid, contact Software AG Global Support.

PREFIX+String.valueOf(POOL_FlOODED_ALLOC_CONN_ERR) {0} Threads are already waiting to get connection. The pool {1} doesn't have a connection available for the request.
Class E
Explanation

This error occurs when a thread holds a connection and stops responding or is in an infinite loop. In either case, the connection pool management capabilities to grant, release, or close connections do not work. Meanwhile, if the pool is flooded with many connection requests, all of the requesting threads are held in a waiting state. Under a heavy load, Integration Server might stop responding. If there are a large number of threads already waiting for a connection, ResourceAllocationException will be thrown to the new threads.

Action

Check the adapter connection pool settings to ensure the values for the minimum number of connections and maximum number of connections are valid. If the adapter connection pool settings are valid and the pool is still unable to initialize, contact Software AG Global Support.

SCHEDU_ACL_DENIED User '{0}' doesn't have permission to execute the service '{1}'.
SESSION_EXPIRED Session has expired.
SERVICE_HANDLER_INIT_ERROR Error initializing service handler {0}. Error: {1}
Class E
Explanation

An error occurred while initializing the JAX-RPC header handler.
Action

The init() method of JAX-RPC handler threw an error. Correct the error in init() method.
STATUS_ACTIVE Transaction is active
STATUS_COMMITTED Transaction is committed
STATUS_COMMITTING Transaction is committing
STATUS_MARKED_ROLLBACK Transaction is marked for rollback
STATUS_NO_TRANSACTION No Transaction
STATUS_PREPARED Transaction is prepared
STATUS_PREPARING Transaction is preparing
STATUS_ROLLEDBACK Transaction is rolled back
STATUS_ROLLING_BACK Transaction is rolling back
STATUS_TWO_LOCAL_TX commit failed. more than one local transaction enlisted.
STATUS_UNKNOWN Transaction status is unknown
STRINGSET_NOSUCHELMENT StringSetEnumerator
SUSPENDED Suspended
TEST_INVALID_ALIAS Associated pool alias for the functional alias {0} does not exist.
Class E
Explanation

Integration Server cannot establish a connection to the pool. A connection pool alias is not associated with the specified functional alias.

Action

Make sure a connection pool is associated with the functional alias.
THREAD_ALREADY_WITH_THIS_TX thread already associated with this transaction
THREAD_WITH_ANOTHER_TX thread already associated with another transaction
TRAN_NOT_ACTIVE transaction is not active
TRAN_NOT_FOR_THREAD transaction is not with current thread
TRAN_NOT_WMTRAN transaction not a Tran instance
TRUST_STORE_EMPTY Truststore alias is empty. Specify a Truststore alias for the port or a global truststore alias on the Security > Certificates > Edit page.
UM_MIGRATE_CONNECTION_ALIAS_NOT_FOUND...0 conectionAlias was not found:{0}.
UM_MIGRATE_CONNECTION_ALIAS_NOT_UM...0 conectionAlias:{0} MUST be a Universal Messaging Connection Alias.
UM_MIGRATE_NOT_MIGRATABLE_FILTER Filter cannot be completely migrated to Provider Filter (UM). Contains an unsupported construct:{0} {1} {2}.
UNABLE_TO_INIT_XASTORE Unrecoverable Error while initializing XA Store: {0}
UNEXPECTED_END_OF_DOCUMENT_WHEN_READING_ELEMENT_TEXT_CONTENT unexpected end of document when reading element text content
UNEXPECTED_EVENT_TYPE Unexpected event type {0}
UNSUPPORTED_ACTION_DELETE_DEST_NULL Cannot delete durable subscriber {0} for alias {1}. The durable subscriber cannot be accessed. You may need to delete the durable subscriber from the JMS provider manually.
URI_IS_INVALID URI "{0}" is invalid
URI_IS_NOT_UNIQUE URI "{0}" is already being used
URI_IS_REQUIRED URI is required
URLALIAS_ALREADY_REGISTERED The HTTP URL alias could not be registered by the service {0}. "{1}" is already registered as an alias for the path: {2}
URLALIAS_ALREADY_REGISTERED2 HTTP URL alias "{0}" could not be registered. It is already registered as an alias for the path: {1}
URLALIAS_ALREADY_REGISTERED3 HTTP URL alias "{0}" could not be registered. It is already registered by package {1} as an alias for the path: {2}
URL_IS_INVALID URL "{0}" is invalid
URL_IS_NOT_UNIQUE URL "{0}" is already being used
URL_IS_REQUIRED URL is required
VCSLog.string(VCSLog.VCS_PKG_SHUTTING_DOWN) VCS package shutting down
Class
VCSLog.string(VCSLog.VCS_PKG_LOADING_CONFIG_FILE) loading configuration file: {0}
Class
VCSLog.string(VCSLog.VCS_PKG_ERROR_LOADING_CONFIG_FILE) error loading configuration file: {0}
Class
VCSLog.string(VCSLog.VCS_PKG_LOADING_USERS_FILE) loading users file: {0}
Class
VCSLog.string(VCSLog.VCS_PKG_ERROR_LOADING_USERS_FILE) error loading users file: {0}
Class
VCSLog.string(VCSLog.VCS_PKG_SAVING_USERS_FILE) saving users file: {0}
Class
VCSLog.string(VCSLog.VCS_PKG_ERROR_SAVING_USERS_FILE) error saving users file: {0}
Class
VCSLog.string(VCSLog.VCS_PKG_GETTING_INFO) retrieving information from VCS server
Class
VCSLog.string(VCSLog.VCS_PKG_NO_CONFIG_FILE_READ) no configuration file read for package: {0}; expecting: {1}
Class
VCSLog.string(VCSLog.VCS_PKG_OVERWRITING_EXISTING_PROPERTY) overwriting existing property: {0}; new value: {1}
Class
VCSLog.string(VCSLog.VCS_FILE_NOT_CHECKED_OUT) file not checked out: {0}
Class
VCSLog.string(VCSLog.VCS_FILE_CHECKED_OUT) file checked out: {0}
Class
VCSLog.string(VCSLog.VCS_FILE_OUT_OF_DATE) file out of date: {0}
Class
VCSLog.string(VCSLog.VCS_FILE_CHECKED_OUT_BY_OTHER_USER) file checked out by another user: {0}
Class
VCSLog.string(VCSLog.VCS_CLIENT_SETTING) setting VCS client as {0}
Class
VCSLog.string(VCSLog.VCS_CLIENT_NONE) no current VCS client
Class
VCSLog.string(VCSLog.VCS_CLIENT_INVALID) invalid VCS client: {0}
Class
VCSLog.string(VCSLog.VCS_CLIENT_TYPE_NOT_SET) no VCS client type set
Class
VCSLog.string(VCSLog.VCS_LOAD_FILES_TO_DELETE) files to delete: {0}
Class
VCSLog.string(VCSLog.VCS_DELETE_DEFAULT_COMMENT) Deleted by %value dev_user% on %value is_host% at %value is_time%
Class
VCSLog.string(VCSLog.VCS_DELETE_DEFAULT_METACOMMENT) %value usercomment%%nl%dev_user : %value dev_user%%nl%is_host : %value is_host%%nl%dev_host: %value dev_host%%nl%is_time : %value is_time%
Class
VCSLog.string(VCSLog.VCS_DELETE_FAILED_REVERTING) delete failed; attempting to revert from opened list
Class
VCSLog.string(VCSLog.VCS_CHECKOUT_IGNORING_BUILD_MODE) not locking in build mode (no package specified)
Class
VCSLog.string(VCSLog.VCS_CHECKOUT_IGNORING_DELETE_MODE) not locking in delete mode
Class
VCSLog.string(VCSLog.VCS_CHECKOUT_FROM_VCS) running checkout from VCS
Class
VCSLog.string(VCSLog.VCS_CHECKIN_DEFAULT_COMMENT) Checked in by %value dev_user% on %value is_host% at %value is_time%
Class
VCSLog.string(VCSLog.VCS_CHECKIN_DEFAULT_METACOMMENT) %value usercomment%%nl%dev_user : %value dev_user%%nl%is_host : %value is_host%%nl%dev_host: %value dev_host%%nl%is_time : %value is_time%
Class
VCSLog.string(VCSLog.VCS_CHECKIN_TO_VCS) running checkin to VCS
Class
VCSLog.string(VCSLog.VCS_PREDELETE_SKIPPING) not deleting files during preDelete
Class
VCSLog.string(VCSLog.VCS_SUBMIT_NO_ENTRIES) No entries to submit
Class
VCSLog.string(VCSLog.VCS_LOAD_DIRECTORIES) loading directories: {0}; version: {1}
Class
VCSLog.string(VCSLog.VCS_P4_CLIENT_NOT_FOUND) Perforce client not found
Class
VCSLog.string(VCSLog.VCS_P4_USER_NOT_FOUND) Perforce user not found
Class
VCSLog.string(VCSLog.VCS_EXEC_COMMAND) For {0}, command: {1}
Class
VCSLog.string(VCSLog.VCS_PARENT_NOT_EXISTS) Parent does not exist: {0}
Class
VCSLog.string(VCSLog.VCS_NO_SUCH_NODE) Node not found for version
Class
WEBSOCKET_NO_CALLBACK Values for callback is required
WEBSOCKET_NO_VALUE Callback "{0}" is required
WEBSOCKET_REQ_FIELD "{0}" is a required field.
WEBSOCKET_REQ_STR_OR_BYTE Message field should be either string or byte object
WEBSOCKET_RUASUSER runAsUser is a required field.
WEBSOCKET_RUN_AS_USER runAsUser is a required field.
WEBSOCKET_SESSION_NOTFOUND Could not find session with sessionId: "{0}"
WS_ALIAS_EXISTING_MESSAGE_ADDRESSING Could not add the Web service endpoint alias because the message addressing endpoint alias {0} for transport type {1} already exists. Provide a different alias name.
Class E
Explanation

The message addressing endpoint alias name you specified already exists for a transport type (HTTP, HTTPS, JMS).
Action

Specify a message addressing endpoint alias name that does not already exist.
WS_INVALID_ASC_CLIENT_KEYTAB_FILE Client Keytab Filename must be ASCII characters
WS_INVALID_ASC_CLIENT_PASSWORD Password for Client Principal must be ASCII characters
WS_INVALID_ASC_CLIENT_PRINCIPAL Client Prinicipal name must be ASCII characters
WS_INVALID_ASC_CLIENT_PWD_INPUT_MODE Client Password Input Mode must be ASCII characters
WS_INVALID_ASC_JAAS_CONTEXT JAAS Context name must be ASCII characters
WS_INVALID_ASC_SERVICE_PRINCIPAL Service Principal Name must be ASCII characters
WS_INVALID_ASC_SERVICE_PRINCIPAL_FORM Service Principal Name Form must be ASCII characters
WS_NO_MSG_KRB_JAAS_CONTEXT JAAS Context for WS Security not specified
WS_NO_MSG_KRB_SERVICE_PRINCIPAL Service Principal for WS Security not specified
WS_NO_MSG_KRB_SERVICE_PRINCIPAL_FORM Service Principal Name Form for WS Security not specified
XID_NOT_FOUND Failed attempt to store global status={0} for xid={1}. XID not found.
XML_NOT_WELLFORMED XML provided is not well-formed or external references encountered while parsing XML - {0}
XML_SOURCE_SHOULD_BE_OF_CORRECT_TYPE xmlSource should be of type 'java.io.InputStream', 'java.io.Reader', 'org.w3c.dom.Node', 'javax.xml.stream.XMLStreamReader' or 'java.lang.String'
XML_TARGET_SHOULD_BE_OF_CORRECT_TYPE xmlTarget should be of type 'java.io.OutputStream', 'java.io.Writer' or 'javax.xml.stream.XMLEventWriter'
String.valueOf(LogMsg.FAC_XSLT_JAXP) new Object[][]{{Integer.valueOf(1),Integer.valueOf(2),"JAXP: Error - {0}"},{Integer.valueOf(2),Integer.valueOf(3),"JAXP: Warning - {0}"},{Integer.valueOf(3),Integer.valueOf(5),"JAXP: Properties file is {0}."},{Integer.valueOf(4),Integer.valueOf(5),"JAXP: DocumentBuilderFactory = {0}"},{Integer.valueOf(5),Integer.valueOf(5),"JAXP: SAXParserFactory = {0}"},{Integer.valueOf(6),Integer.valueOf(5),"JAXP: TransformerFactory = {0}"},{Integer.valueOf(7),Integer.valueOf(5),"JAXP: Stylesheet template {0} cached."},{Integer.valueOf(8),Integer.valueOf(5),"JAXP: Stylesheet templates cache cleared."},{Integer.valueOf(9),Integer.valueOf(3),"JAXP: Required argument 'stylesheet' not specified; no value removed from stylesheet cache."},{Integer.valueOf(10),Integer.valueOf(5),"JAXP: Stylesheet template {0} removed from cache."},{Integer.valueOf(11),Integer.valueOf(3),"JAXP: Stylesheet template {0} was not found in cache."},{Integer.valueOf(12),Integer.valueOf(5),"JAXP: Stylesheet {0} was successfully compiled."},{Integer.valueOf(13),Integer.valueOf(5),"JAXP: Compiling TransformerFactory = {0}"},{Integer.valueOf(14),Integer.valueOf(2),"JAXP: Error - External entity attack detected. Entity name is {0}"},}
Class E
Explanation

An external entity was detected in the XML that the pub.xslt.Transformations:transformSerialXML service received or in the XSLT stylesheet the service used to transform the XML.

Action

Check the XML file or the XSLT stylesheet for external entities. If the external entity is a trusted entity, add the entity to the server parameter watt.core.xml.allowedExternalEntities.