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.


1.9999 ""+EXCEPTION_MSG+""

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.


109.8 Unable to find service object for {0}. Therefore, no statistics will be captured

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.70 JWT Authentication was successful , skipping Basic Authentication.

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.

14.67 Transaction Metering configuration missing.

14.68 Transaction Metering configuration loading exception: {0}.

14.69 License Metering initialization exception: {0}.

14.70 Local JMX is not enable for Transaction Metering, no metrics for transactions will be produced.

14.71 Transaction Metering enabled.

14.72 Default outbound master password is in use.

14.73 Default Administrator password is in use.

14.74 An item is released to the pool: {0}. Statistics: Used count: {1}, Available: {2}, Allocatable: {3}

14.75 An item is returned to the pool: {0}. Statistics: Used count: {1}, Available: {2}, Allocatable: {3}

14.76 Waiting for all items to be released or returned to the pool: {0}.

14.77 An item is expired from the pool: {0}.

14.78 An excess item is released from the pool: {0}

14.79 Pool: {0} statistics: Used count: {1}, Available: {2}, Allocatable: {3}

14.9999 {0}

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_MSG+""

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.100 Signature was invalid

163.101 Not before claim verification failed

163.102 Expiration claim verification failed

163.103 Unable to parse JWT , threw exception: {0}

163.104 JWT verified with truststore {0} and keystore {1}

163.105 Successfully extracted claims : {0}. Claims not found in jwt : {1}

163.106 Failed to verify JWT : {0}

163.107 Unable to get private key entry for keystore {0} and key {1}

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.14 Not before time is after current time , trying to verify not before time with skew {0}.

163.15 Expiry time is before current time , trying to verify expiry time with skew {0}.

163.16 Issuer skew set to {0} , takes precedence over global skew {1}.

163.17 Signing JWT with key obtained from keystore alias "{0}" and key alias "{1}".

163.18 Failed to get certificate using truststore alias "{0}" and certificate alias "{1}".

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.9998 {0}

163.9999 ""+EXCEPTION_MSG+""

174.1 Start Time ''{0}'' is invalid, should be a positive number.

174.2 End Time ''{0}'' is invalid, should be a positive number.

174.3 Sort Order ''{0}'' is invalid, should be one of ['ASC', 'DESC'].

174.4 Sort By ''{0}'' is invalid, should be one of ['timestamp', 'channel', 'severity', 'subject'].

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 Tenant connection(s) 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 Cloud 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.8022 Test of the account {0} failed. Confirm that the related tenant connection is enabled.
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.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 server {1} for application {2}.
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 Tenant Connection settings are configured and enabled.
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.

24.62 Unable to locate Administrator password. Shutting down server.

24.63 Unable to locate Instance key.

24.64 Unable to locate Installer key.

25.27 Messaging sub-system {0} successfully shutdown.

25.28 Error shutting down CSQ Factory for {0} messaging sub-system: {1}

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

27.6 The values of the watt.server.http.header.sameSite and watt.server.http.header.useSecure parameters must be compatible. If the watt.server.http.header.sameSite is set to None, then watt.server.http.header.useSecure must be true.

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}

28.65 Failed to retrieve the Universal Messaging triggers of the package {0}. Integration Server might not remove the durables for deleted triggers: {1}

28.66 Failed to remove the durable for trigger {0} of the package {1}: {2}.

28.67 Removed trigger name (after deployment): {0}, package: {1}.

28.68 The Web service descriptor {0} cannot be loaded. {1}

28.69 The SOAP JMS trigger {0} cannot be loaded. {1}

3 Enabled

33.187 ClusterMembers Error getting TCDB Coordinator: {0}

34.1 Setting ACL for {0} to ACL group {1}

34.2 Setting Write ACL for {0} to ACL group {1}

34.3 Setting Read ACL for {0} to ACL group {1}

34.4 Setting Browse ACL for {0} to ACL group {1}

35.5 Number of lines to display must be a non negative number. {0}.

35.9998 ""+EXCEPTION_MSG+""

35.9999 {0}

4 Disabled

4.9998 Exception -> {0}

48.12 Error occurred while initializing SSL Session Logger. Error: {0}

48.13 Error occurred while adding SSL session log entry to log file. Error: {0}

48.14 SSL session log entry ''{0}'' not added to log file.

48.15 SSL Session Logger has stopped.

48.16 Invalid SSL session log file ''{0}''. Using the default log file ''{1}''.

48.17 Unable to write SSL session logs to log file ''{0}''. Logs will be written to console. Error: {1}

48.18 SSL session logs will be written to file ''{0}''.

48.19 Integration Server detected loss of its Log4j configuration. Integration Server has now restored its Log4j configuration.

48.20 Setting extended WATT property {0}={1}

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 Configuration for cluster "{0}" has been updated.

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.

6.37 SSL port {0} is configured to support protocols {1}.

6.38 Outbound SSL connection {0} is configured to support protocols {1}.

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}

64.37 SSRF check enabled: redirection protocol must be http or https. Redirection to URL {0} was denied.

64.38 SSRF check enabled: attempting to redirect to private IP address. Redirection to URL {0} was denied.

68.29 {0}

68.30 {0}

68.31 {0}

68.32 Could not delete the message with uid {0}: {1}

68.33 Authorization failed for email port with the alias {0} due to {1}

68.34 Authorization code is empty for email port with the alias {0}

68.35 Failed to generate access token for email port with the alias {0} due to {1}

68.36 Failed to generate access token for email port with alias {0} due to invalid Access Token URL {1}

68.37 Email Expiry time parse failed

7 Configuration for broker "{0}" has been updated.

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.36 Invalid value: {0}, {1} must be greater than or equal to {2} bytes and be a multiple of 1024. Resetting to the default value: {3}

76.37 Invalid value: {0}, {1} exceeds the string length limit. Resetting to this maximum value: {2}

76.9999 {0}

79.9999 {0}

85.9318 Could not retrieve prometheus statistics for product {0}, because its package, {1}, is disabled or deleted. All prometheus stat providers should be unregistered before their sources are made no longer available.

85.9319 Could not retrieve prometheus statistics for product {0} because its getPackage() method returned a null value.

88.9443 One or more required Headers "{0}" are not present in the SOAP response.

9.16 Unable to access IS X509 certificate mapping data in the database. No JDBC connection is available.

91.9997 [Admin API] {0}

91.9998 Exception --> {0}

91.9999 {0}

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.32 Database URL contains the Kerberos re-authentication property 'ReAuthenticateUser'. The original URL is : {0}.

96.33 Database URL contains the Kerberos re-authentication property 'ReAuthenticateUser'. The revised URL is : {0}.

96.34 Database URL contains the Kerberos re-authentication property 'ReAuthenticateUser'. The ReAuthenticateUser is : {0}.

96.35 Kerberos re-authentication property 'ReAuthenticateUser' found in database URL. Invoked ExtConnection.setCurrenUser using : {0}.

96.36 Kerberos re-authentication property 'ReAuthenticateUser' found in connection properties. Invoked OracleConnection.openProxySession using : {0}.

96.37 loginConfigName is not specified so ignoring watt.server.jdbc.datadirect.useJaasSubjectForKerberos and attempting normal connection.

96.38 loginConfigName is {0}; Connection object is {1}.

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.

ALERTS_AND_NOTIFICATIONS_DISABLED Failed to execute service {0}, Alerts and notifications are disabled while in quiesce mode

ALERT_CHANNEL_INVALID channelId ''{0}'' is invalid, should be referencing: ''{1}''

ALERT_CONTENT_TYPE_MAX_LENGTH contentType can have a maximum of 255 characters

ALERT_FETCH_CHANNELS_INVALID Channels ''{0}'' is invalid, should be comma-separated numbers.

ALERT_FETCH_SEVERITIES_INVALID Severities ''{0}'' is invalid, should be comma-separated numbers.

ALERT_ID_INVALID alertId ''{0}'' is invalid

ALERT_SEVERITY_INVALID severity ''{0}'' is invalid, should be referencing: ''{1}''

ALERT_SUBJECT_MAX_LENGTH subject can have a maximum of 255 characters

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.