tibco activematrix businessworks error codes codes naming convention product execution errors,...

TIBCO ActiveMatrix BusinessWorks™ ErrorCodesSoftware Release 6.2November 2014

Two-Second Advantage®

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCHEMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY(OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THEEMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANYOTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS ANDCONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTEDSOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THECLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOADOR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE)OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USERLICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THESOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, ANDYOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BEBOUND BY THE SAME.

This document contains confidential information that is subject to U.S. and international copyright lawsand treaties. No part of this document may be reproduced in any form without the writtenauthorization of TIBCO Software Inc.

TIBCO, TIBCO ActiveMatrix BusinessWorks, TIBCO Rendezvous, TIBCO Enterprise Message Service,TIBCO Business Studio, TIBCO Enterprise Administrator, TIBCO ActiveSpaces, TIBCO Runtime Agent,TIBCO Designer, and Two-Second Advantage are either registered trademarks or trademarks of TIBCOSoftware Inc. in the United States and/or other countries.

Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform EnterpriseEdition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks ofOracle Corporation in the U.S. and other countries.

All other product and company names and marks mentioned in this document are the property of theirrespective owners and are mentioned for identification purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOTALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASEDAT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWAREVERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.

THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICALERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESECHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCOSOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S)AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.

THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY ORINDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE,INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

Copyright © 2001-2014 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

2

TIBCO ActiveMatrix BusinessWorks™ Error Codes

Contents

TIBCO Documentation and Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Message Codes Naming Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

SOAP Binding Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

REST Binding Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Admin Agent Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Admin Command Line Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Admin Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Engine Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Hawk Microagents Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

TEA Agent Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Palettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

File Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

FTP Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

General Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

HTTP Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Java Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

JDBC Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

JMS Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Mail Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Parse Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Rendezvous Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

TCP Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

XML Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Shared Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Shared Resource Framework Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Data Format Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

FTP Connection Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

HTTP Client Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

HTTP Connector Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Java Global Instance Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

JMS Connection Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

JDBC Connection Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

JNDI Configuration Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Proxy Configuration Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Rendezvous Transport Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

SMTP Resource Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

3


TCP Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86

4


TIBCO Documentation and Support Services

All TIBCO documentation is available on the TIBCO Documentation site, which can be found here:

https://docs.tibco.com

Product-Specific Documentation

Documentation for TIBCO products is not bundled with the software. Instead, it is available on theTIBCO Documentation site. To directly access documentation for this product, double-click thefollowing file:

TIBCO_HOME/release_notes/TIB_BW_version_docinfo.html

The following documents for this product can be found on the TIBCO Documentation site:

● Concepts● Installation● Getting Started● Application Development● Administration● Bindings and Palettes Reference● Samples● Error Codes● API Reference● Migration

How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, contact TIBCO Support asfollows:

● For an overview of TIBCO Support, and information about getting started with TIBCO Support,visit this site:

http://www.tibco.com/services/support

● If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a user name, you canrequest one.

How to Join TIBCOmmunity

TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is aplace to share and access the collective experience of the TIBCO community. TIBCOmmunity offersforums, blogs, and access to a variety of resources. To register, go to:

http://www.tibcommunity.com

5


https://docs.tibco.com

http://www.tibco.com/services/support

https://support.tibco.com

http://www.tibcommunity.com

Message Codes Naming Convention

Product execution errors, warnings, and information are reported through detailed log messages thatcan help trace the cause of the issue. These messages follow a naming convention that indicates thecomponent and log level for each message. The log levels allow you to capture different granularity ofmessages for different loggers.

Messages returned by the software consist of a code and an associated message.

The message code consists of two parts, a component ID and a 6-digit number, separated by a hyphen(-). The component ID indicates the component that reported the message and the 6-digit number is anumerical range that indicates the logger level.

The following table lists the component IDs and their descriptions.

Component Id Description

BX ActiveMatrix BusinessWorks Engine Layer

PVM ActiveMatrix BusinessWorks Engine Layer

TIBCO-BW-ADMIN ActiveMatrix BusinessWorks Administrator

TIBCO-BW-ADMIN-CLI ActiveMatrix BusinessWorks Administrator Command Line Interface

TIBCO-BW-BINDING-REST

ActiveMatrix BusinessWorks REST Binding

TIBCO-BW-BINDING-SOAP

ActiveMatrix BusinessWorks SOAP Binding

TIBCO-BW-CORE ActiveMatrix BusinessWorks Engine Layer

TIBCO-BW-FRWK ActiveMatrix BusinessWorks Framework

TIBCO-BW-PALETTE ActiveMatrix BusinessWorks Palette Layer

TIBCO-BW-PALETTE-<PaletteName>

ActiveMatrix BusinessWorks Palette specific activity implementation

TIBCO-BW-SR ActiveMatrix BusinessWorks Shared Resource API Layer

TIBCO-BW-SR-<UniqueName>

ActiveMatrix BusinessWorks specific Shared Resource implementation

TIBCO-BW-STATS ActiveMatrix BusinessWorks Stats Collector

TIBCO-THOR-FRWK Thor Framework

The Engine layers with component IDs BX and PVM do not follow this convention.

The following table lists the log levels used by the software and the corresponding message code range.

6


Log Level Error Code

TRACE 100001 - 109999

DEBUG 200001 - 209999

INFO 300001 - 309999

WARN 400001 - 409999

ERROR Errors can be indicated by one of the following error code ranges:

● 500001 - 509999● 600001 and higher● 0xxxxx

● Error codes 600001 and higher indicate exceptions in the executionand are always associated with a 5xxxxx error code, which can betraced in the log file.

● Error codes starting with 0xxxxx indicate internal errors. ContactTIBCO Support for possible resolution or a workaround.

The message describes the issue. Sometimes, the message can contain parameters shown as ({N}), whereN is an integer. For example, consider the message for error code TIBCO-BW-ADMIN-500300 : TheAppNode [{0}] does not exist in AppSpace [{1}] and Domain [{2}]. These parameters aresubstituted with appropriate values at runtime.

7


Bindings

This section describes the error messages that can be reported by the SOAP and REST Binding types.

SOAP Binding Error CodesThis section describes the error messages that can be reported by the SOAP Binding.

Error Codes Error Message

TIBCO-BW-BINDING-SOAP-001010

SOAP BindingFatory is initialized with incorrectBindingConfiguration for the SOAP Service Binding.


Failed to obtain HTTP Connector resource forSoapServiceBinding [{0}], Application [{1}:{2}]


Failed to obtain HTTP Connector resource forSoapServiceBinding [{0}], Application [{1}:{2}]


SOAP BindingFatory is initialized with incorrectBindingConfiguration for the SOAP Reference Binding.


Failed to parse binding meta data file [{0}] in bundle [{1}] due toexception [{2}].


Failed to process File [{0}] in bundle [{1}]. BindingName is notspecified.


Failed to process File [{0}] in bundle [{1}]. A Binding with name[{2}] is already registered.


Failed to deploy the SOAP Interceptor Module [{0}], due toexception [{1}]. Root exception message is [{2}].


Failed to create SoapServiceBinding [{0}], Application [{1}:{2}] dueto exception [{3}]


Failed to initialize SoapServiceBinding [{0}], Application [{1}:{2}]due to exception [{3}]


Failed to add transport dependency for SoapServiceBinding [{0}],Application [{1}:{2}]


Failed to initialize SoapServiceBinding [{0}]. A Service EndpointURI [{1}] is already registered


Failed to initialize SoapServiceBinding [{0}]. The operation [{1}]with soapaction [{2}] is already registered for destination [{3}]with Message Style [{4}].


Failed to send SOAP Fault message to the consumer of the servicefor Operation [{0}], SoapServiceBinding [{1}], Application [{2}:{3}]due to exception [{4}]. Root Exception message: {5}

8




Failed to process Reply message for Operation [{0}],SoapServiceBinding [{1}], Application [{2}:{3}] due to exception[{4}]. Sending Undeclared Fault message to the consumer of thisservice. Root Exception message: [{5}]


Error occurred while processing Service Request messagesContext Information for Operation [{0}], SoapServiceBinding [{1}],Application [{2}:{3}] due to exception [{4}]. Root Exceptionmessage: {5}


Error occurred while processing Service Request message forOperation [{0}], SoapServiceBinding [{1}], Application [{2}]:{3}]due to exception [{4}]. Root Exception message: {5}


Error occurred while processing Service Request message forOperation [{0}], SoapServiceBinding [{1}], Application [{2}:{3}]due to exception [{4}]. Sending Undeclared Fault message to theconsumer of this service. Root Exception message: {5}


Failed to process Declared Fault Message for Operation [{0}],SoapServiceBinding [{1}], Application [{2}:{3}] due to exception[{4}]. Sending Undeclared Fault message to the consumer of thisservice. Root Exception message: {5}.


Error occurred while processing service request message forOperation [{0}], SoapServiceBinding [{1}], Application [{2}:{3}]due to exception [{4}]. Sending Undeclared Fault message to theconsumer of this service. Root Exception message: {5}.


Unable to populate SOAP Binding Configuration due toexception [{1}]


An Error occurred while cleaning up the SOAP BindingConfiguration Resources due to exception [{1}]


An interrupted fault occurred while waiting for the ServiceRequest message to be processed for Operation [{0}],SoapServiceBinding [{1}], Application [{2}:{3}] due to exception[{4}]. Sending Undeclared Fault message to the consumer of thisservice. Root Exception message: {5}


Failed to start SoapServiceBinding [{0}], Application [{1}:{2}] dueto exception [{3}]


Failed to stop SoapServiceBinding [{0}], Application [{1}:{2}] dueto exception [{3}]


Error occurred while processing Service Request messagesContext information for Operation [{0}], SoapServiceBinding [{1}],Application [{2}:{3}] due to exception [{4}]. Sending UndeclaredFault message to the consumer of this service. Root Exceptionmessage: {5}

9




Failed to start JMS transport primitive for SoapServiceBinding[{0}], Application [{1}:{2}] due to exception [{3}]


Failed to stop JMS transport primitive for SoapServiceBinding[{0}], Application [{1}:{2}] due to exception [{3}]


Failed to Initialize JMS transport primitive forSoapServiceBinding [{0}], Application [{1}:{2}] due to exception[{3}]


Failed to read incoming JMS raw message due to exception [{0}];


Failed to create JMS Reply Handler for SoapServiceBinding [{0}],Application [{1}:{2}] due to exception [{3}]


Failed to process service request message for SoapServiceBinding[{0}], Application [{1}:{2}] due to exception [{3}] .Root exceptionmessage : [{4}]


Failed to send Service Reply message for Operation [{0}],SoapServiceeBinding [{1}], Application [{2}:{3}] due to exception[{4}]


Failed to acknowledge Service Request message for Operation[{0}], SoapServiceeBinding [{1}], Application [{2}:{3}] due toexception [{4}]


Failed to create SoapReferenceBinding [{0}], Application [{1}:{2}]due to exception [{3}]


Failed to create SoapReferenceEndpoint [{0}] due to exception[{1}]


Failed to initialize SoapReferenceBinding [{0}], Application [{1}:{2}] due to exception [{3}]


Failed to add transport dependency for SoapReferenceBinding[{0}], Application [{1}:{2}]


Failed to destroy SoapReferenceBinding [{0}], Application [{1}:{2}]due to exception [{3}]


Failed to release transport resources for Operation [{0}],SoapReferenceBinding [{1}], Application [{2}:{3}] due to exception[{4}]


Received Declared Fault. Failed to release transport resources forOperation [{0}], SoapReferenceBinding [{1}], Application [{2}:{3}]due to exception [{4}]

10




Ensure that the Service Provider is available.


Unable to connect to the service provider for Operation [{0}],SoapReferenceBinding [{1}], Application [{2}:{3}] due to exception[{4}]


Received SOAP Fault from the service provider of the Operation[{0}], SoapReferenceBinding [{1}], Application [{2}:{3}]. SOAPFault received: [{4}]


Error occurred while processing the declared fault message fromthe service provider of the Operation [{0}], SoapReferenceBinding[{1}], Application [{2}:{3}] due to exception [{4}]


Error occurred while processing reply message from the serviceprovider of the Operation [{0}], SoapReferenceBinding [{1}],Application [{2}:{3}] due to exception [{4}]


SOAPEnvelope must contain a body element which is either firstor second child element of the SOAPEnvelope.


Error occurred while processing reply message attachments fromthe service provider of the Operation [{0}], SoapReferenceBinding[{1}], Application [{2}:{3}] due to exception [{4}]


Failed to Initialize JMS transport primitive forSoapReferenceBinding [{0}], Application [{1}:{2}] due to exception[{3}]


Failed to send Reference Request message for Operation [{0}],SoapReferenceBinding [{1}], Application [{2}:{3}] due to exception[{4}]


Failed to process reply message from the service provider of theOperation [{0}], SoapReferenceBinding [{1}], Application [{2}:{3}]due to exception [{4}]


Failed to update HTTP Transport configurations before sendingthe Reference Request message for Operation [{0}],SoapReferenceBinding [{1}], Application [{2}:{3}] due to exception[{4}].


Failed to create the HTTP Client required for sending theReference Request message for Operation [{0}],SoapReferenceBinding [{1}], Application [{2}:{3}] due to exception[{4}].


Failed to serialize JMS transport message due to exception [{1}].

11




Failed to convert JMS message to string due to exception [{1}].


Failed to create Endpoint URL for Operation [{0}],SoapReferenceBinding [{1}], Application [{2}:{3}] due to exception[{4}].

REST Binding Error CodesThis section lists the error messages that can be reported by the REST Binding.


TIBCO-BW-BINDING-REST-500001

Binding Configuration is not for a REST Service Binding


No relative resource url specified to deploy REST Resource


Unable to create REST resource for binding [{0}]. Reason - Unableto stop conflicting binding [{1}].


Unable to start REST Binding with name [{0}]


Unable to stop REST Binding with name [{0}}


Error Occurred while parsing and creating HTTP Headers.Responding to client with error message.


Error Occurred while creating Parameters Part. Responding toclient with error message.


Error Occurred while creating User Part. Responding to clientwith error message.


No WSDL Operation found. Please re-validate the applicationmodule and try deploying again.

12


Core

This section lists the error codes returned by the core components such as runtime and administration.

Admin Agent Error CodesThis section lists the error messages that can be reported by the bwagent.


TIBCO-BW-ADMIN-PRSTNC-500001

Connection to BW Agent failed.


bwagent.ini configuration error.bw.agent.technology.as.dataStoreLocation=[{0}] does not exist.


bwagent.ini configuration error. read timeout is invalid


bwagent.ini configuration error. write timeout is invalid


Failed to execute query on Space [{0}] with given parameters


bwagent is not ready or the the existing connection to thebwagent is stale. Re-try the command, if the problem persists,restart the process and try again.


Invalid query. Mandatory argument(s) are missing. ContactTIBCO Support.

Admin Command Line Error CodesThis section describes the error messages that can be reported by the Administrator command line.


TIBCO-BW-ADMIN-CLI-500000

{0}


Failed to perform operation [{0}] on [{1}] in the Domain [{2}] dueto an error in initializing data manager, {3}


Error while checking if the Entity [{0}] is present in the Domain[{1}], {2}


The BW Agent [{0}] on the target Machine is not running


Error invoking {0} method on the remote agent [{1}], {2}

13




Error occurred while uploading the ear file into data store, {0}


Failed to initialize transport, {0}


Unsupported entity {0}


Failed to perform operation [{0}] due to an error in initializingdata manager, {1}


Failed to write to file [{0}]


Execution of this command is not supported in admin mode'local'.


Please provide the agent name.


No matching Agent found


Invalid value for mandatory entity argument. Valid argumentvalues are domain, appspace, appnode, and application.


The {0} command without any argument is only supported ininteractive console mode.


Invalid value for mandatory entity argument. Valid argumentvalues are appnode and agent.


Nothing to restore. Either agent [{0}] does not exist or the agent isnot part of the domain [{1}]


Failed to configure bwagent, <CausedBy> {0}


Domain [{0}] does not exist


Domain [{0}] already exists in the datastore


Failed to create Domain [{0}], {1}


Domain home folder [{0}] does not exist. Verify if the folder ispresent and use forward slash in the folder path

14




Failed to delete Domain [{0}], {1}


No matching Domain found


Failed to delete BW Agent [{0}], <CausedBy> {1}


Failed to unregister BW Agent [{0}] from the AppSpace [{1}].<CausedBy> {2}


AppSpace [{0}] not found in Domain [{1}]


AppSpace [{0}] already exists in Domain [{1}]


Failed to create AppSpace [{0}] in Domain [{1}], {2}


AppSpace [{0}] already exists with BW Agent [{1}]


Failed to delete AppSpace [{0}] from Domain [{1}], {2}


AppSpace [{0}] in Domain [{1}] could not be started, {2}


AppSpace [{0}] in Domain [{1}] could not be stopped, {2}


AppSpace [{0}] in Domain [{1}] does not have any AppNodes.


Failed to export configuration from AppSpace [{0}] and Domain[{1}] , {2}


AppSpace [{0}] in Domain [{1}] does not have configuration.


Configured AppSpace [{0}] in Domain [{1}]. Restart AppSpace toapply changes.


Configuration of AppSpace [{0}] in Domain [{1}] failed, {2}


Exported configuration from AppSpace [{0}] and Domain [{1}] to[{2}]

15




The minNodes configuration value for an AppSpace has to be atleast 1.


The minNodes configuration argument is invalid. Validargument are Integer values greater than 0.


No matching AppSpace found


Failed to restore AppSpace [{0}].


Failed to restore AppSpace on [{0}] <CausedBy> {1}


Restore failed.


Nothing to restore. Either agent [{0}] does not exist or the agent isnot part of the AppSpace [{1}]


AppNode [{0}] not found in AppSpace [{1}] in Domain [{2}]


AppNode [{0}] already exists in the AppSpace [{1}] in Domain[{2}]


Failed to create AppNode [{0}] in AppSpace [{1}] in Domain [{2}],{3}


Start AppNode [{0}] in Domain [{1}] timed out


AppNode [{0}] in Domain [{1}] did not start, {2}


AppNode [{0}] in Domain [{1}] did not stop, {2}


Failed to delete AppNode [{0}] in AppSpace [{1}] in Domain [{2}],{3}


Stop AppNode [{0}] in Domain [{1}] timed out.


Failed to obtain thread dump, {0}


Failed to export configuration from AppNode [{0}] in AppSpace[{1}] in Domain [{2}], {3}

16




AppNode [{0}] in AppSpace [{1}] in Domain [{2}] configured.Restart AppNode to apply changes.


Configuration of AppNode [{0}] in AppSpace [{1}], Domain [{2}]failed, {3}


Exported configuration from AppNode [{0}] in AppSpace [{1}],Domain [{2}] to [{3}]


Failed to obtain Agent log file, {0}


Failed to enable console on AppNode [{0}] in AppSpace [{1}] inDomain [{2}], {3}


Failed to disable console on AppNode [{0}] in AppSpace [{1}] inDomain [{2}], {3}


Failed to obtain AppNode log file, {0}


Failed to disable debugger on AppNode [{0}] in AppSpace [{1}] inDomain [{2}], {3}


No matching AppNode found


The deployment artifact [{0}] supplied does not exist


Application [{0}] is not present in the Domain [{1}], {2}


Failed to deploy application from the archive [{0}], {1}


Failed to undeploy application [{0}:{1}], <CausedBy> {2}


The application [{0}] is in undeployed state


The deployment artifact [{0}] supplied is not valid


Failed to deploy hotfix to application [{0}:{1}]


Version [{0}] is not valid. Only <major>.<minor> version format issupported.

17




Delete ear file [{0}] failed.


Failed to undeploy hotfix to application [{0}:{1}].


Failed to start application [{0}:{1}]. <CausedBy> {2}


Failed to stop application [{0}:{1}]. <CausedBy> {2}


Failed to export Profile [{0}] from the Archive [{1}], {2}


Failed to export configuration from application [{0}:{1}] , {2}


Failed to obtain metrics. <CausedBy> {0}


Deployed application from the archive [{0}], however not allapplication instances started. <CausedBy> {1}


Failed to configure application [{0}:{1}], {2}


Failed to pause application [{0}:{1}]. <CausedBy> {2}


Failed to resume application [{0}:{1}]. <CausedBy> {2}


The directory [{0}] provided for option [-dir] does not exist,provide a valid directory.


Failed to start process starters of application [{0}:{1}], <CausedBy>{2}.


Failed to stop process starters of application [{0}:{1}], <CausedBy>{2}.


Profile file [{0}] does not exist


No matching Application found


Failed to upload the ear file [{0}].

18




Failed to upload ear file [{0}] to some machines in the domain.


Failed to upload archive [{0}], <CausedBy> {1}.


Failed to delete archive [{0}], <CausedBy> {1}.


Failed to delete ear file [{0}] from some machines in the domain.


Failed to restore application [{0}] on Agent [{1}], <CausedBy> {2}


Failed to restore application [{0}].


The application [{0}] from archive [{1}] has been deployed to theseAppSpaces: {2}


Applications are out of sync with the archive they were deployedfrom, They have to be re-deployed to keep them in sync.


Failed to enable debug port on AppNode[{0}] in AppSpace[{1}] inDomain[{2}], <CausedBy> {3}


Name contains invalid characters and does not comply withnaming conventions. Valid characters are upper and lower casecharacters of the alphabet as well as digits, '.' and '-'.


Name length exceeds 100 characters and it will be truncated tosatisfy the length limit


Name contains invalid characters that have been removed tocomply with naming conventions.\nAllowed characters areupper and lower case characters of the alphabet as well as digits," ", "." and "-".\nName has been changed to [{0}].


Failed to register TEA Agent [{0}] with TEA server, <CausedBy>{1}


Failed to disable auto registration with TEA server, <CausedBy>{0}


Successfully disabled auto registration with TEA server


Failed to enable auto registration with TEA server, <CausedBy>{0}

19




Successfully enabled auto registration with TEA server


No matching Archive found to restore


{0}

Admin Error CodesThis section describes the error messages that can be reported by the entities associated with theActiveMatrix BusinessWorks Administrator.


TIBCO-BW-ADMIN-500000 {0}

TIBCO-BW-ADMIN-500001 Failed to perform operation [{0}] on [{1}] in the Domain [{2}] dueto an error in initializing data manager, {3}

TIBCO-BW-ADMIN-500002 Error while checking if the entity [{0}] is present in the Domain[{1}], {2}.

TIBCO-BW-ADMIN-500004 Error invoking [{0}] method on the agent [{1}], {2}

TIBCO-BW-ADMIN-500005 Error while uploading the application archive file into data store,{0}

TIBCO-BW-ADMIN-500006 Failed to initialize transport, {0}

TIBCO-BW-ADMIN-500007 Unsupported value for bw.admin.mode [{0}]

TIBCO-BW-ADMIN-500008 Error in initializing data manager, {0}

TIBCO-BW-ADMIN-500009 Cannot find or read file [{0}].

TIBCO-BW-ADMIN-500010 Invalid configuration content or format in file [{0}].

TIBCO-BW-ADMIN-500011 Remote command execution failed: {0}

TIBCO-BW-ADMIN-500012 Configuration error in bwagent.ini file. Remote request timeoutinvalid.

TIBCO-BW-ADMIN-500013 Port [{0}] is already taken by AppNode [{1}] belonging toAppSpace [{2}] in the Domain [{3}]

TIBCO-BW-ADMIN-500014 Port [{0}] is in use already.

TIBCO-BW-ADMIN-500015 Conflicting HTTP and OSGi console ports. Port [{0}]

20



TIBCO-BW-ADMIN-500016 Configuration error in bwagent.ini file. Value given inbw.agent.technology.as.remote.status.requestTimeout is invalid.

TIBCO-BW-ADMIN-500017 BW Agent is running, Stop the remote agent, delete all the filesunder domains folder,and re-try.

TIBCO-BW-ADMIN-500100 Domain [{0}] not found, check this and re-try.

TIBCO-BW-ADMIN-500101 Domain [{0}] already exists, check this and re-try.

TIBCO-BW-ADMIN-500102 Failed to create domain [{0}]

TIBCO-BW-ADMIN-500103 Domain home folder [{0}] does not exist. Verify if the folder existsand use '/' character in the folder path.

TIBCO-BW-ADMIN-500104 Machine [{0}] is not present in the Domain [{1}].

TIBCO-BW-ADMIN-500105 Machine [{0}] could not be added to the Domain [{1}], {2}.

TIBCO-BW-ADMIN-500106 Failed to delete Domain [{0}], {1}.

TIBCO-BW-ADMIN-500107 Machine [{0}] could not be removed from the Domain [{1}], {2}.

TIBCO-BW-ADMIN-500108 Machine [{0}] is already part of Domain [{1}]

TIBCO-BW-ADMIN-500109 The Domain [{0}] has AppSpaces associated with it. Use -forceoption to override

TIBCO-BW-ADMIN-500108 Agent [{0}] is already part of domain [{1}]

TIBCO-BW-ADMIN-500109 Domain [{1}] could not be expanded to the Agent [{0}], {2}.

TIBCO-BW-ADMIN-500110 Domain [{1}] could not be removed from the Agent [{0}], {2}.

TIBCO-BW-ADMIN-500111 Agent [{0}] is not part of the Domain [{1}].

TIBCO-BW-ADMIN-500112 Domain [{0}] not found, check this and re-try.

TIBCO-BW-ADMIN-500113 Domain [{0}] is not a local domain.

TIBCO-BW-ADMIN-500201 AppSpace [{0}] in Domain [{1}] not found.

TIBCO-BW-ADMIN-500202 The AppSpace [{0}] is already present in the Domain [{1}].

TIBCO-BW-ADMIN-500204 AppSpace [{0}] already exists with agent [{1}].

TIBCO-BW-ADMIN-500205 AppSpace [{0}] in Domain [{1}] could not be deleted, {2}.

TIBCO-BW-ADMIN-500206 Failed to register Agent [{0}] to AppSpace [{1}], {2}.

TIBCO-BW-ADMIN-500207 Failed to unregister Agent [{0}] from AppSpace [{1}], {2}.

21



TIBCO-BW-ADMIN-500208 Adding Machine to an AppSpace is not supported in 'local'admin mode.

TIBCO-BW-ADMIN-500209 Removing Machine from an AppSpace is not supported in 'local'admin mode.

TIBCO-BW-ADMIN-500210 AppSpace [{0}] in Domain [{1}] did not start completely, {2}.

TIBCO-BW-ADMIN-500211 AppSpace [{0}] in Domain [{1}] could not be stopped, {2}.

TIBCO-BW-ADMIN-500212 AppSpace [{0}] in Domain [{1}] could not be deleted, {2}.

TIBCO-BW-ADMIN-500213 AppSpace [{0}] in Domain [{1}] does not have any AppNodes.

TIBCO-BW-ADMIN-500214 Failed to deploy the {0} [{1}] from URL {2} into AppSpace {3}

TIBCO-BW-ADMIN-500215 AppSpace handler [{0}] not found

TIBCO-BW-ADMIN-500216 AppSpace [{0}] has AppNodes associated with it. Delete theAppNodes first and re-try or use -force option to override

TIBCO-BW-ADMIN-500217 AppSpace [{0}] has Applications or Libraries associated with it.Undeploy them first and re-try or use -force option to override

TIBCO-BW-ADMIN-500218 AppSpace [{0}] is not expanded to BW Agent [{1}].

TIBCO-BW-ADMIN-500219 AppSpace [{0}] is not scaled across multiple installations. Usedelete command to delete it.

TIBCO-BW-ADMIN-500220 AppSpace [{0}] is scaled across multiple BW Agents. Cannot bedeleted. Use -force option to override.

TIBCO-BW-ADMIN-500221 AppSpace [{0}] could not be updated, {1}

TIBCO-BW-ADMIN-500222 Configuration of AppSpace [{0}] in Domain [{1}] failed, {2}

TIBCO-BW-ADMIN-500223 Configuration failed on one or more remote agents.

TIBCO-BW-ADMIN-500224 AppSpace [{0}] has already reached its limit of applications [{1}]

TIBCO-BW-ADMIN-500225 Only one version of Application [{0}] can be deployed in anAppSpace at the same time.

TIBCO-BW-ADMIN-500226 The registration of BW Agent to the domain [{0}] failed. Cannotcreate AppNodes in the AppSpace [{1}] on the remote BW Agent[{2}]

TIBCO-BW-ADMIN-500227 The registration of BW Agent to the AppSpace [{0}] failed. Cannotcreate AppNodes in the AppSpace [{0}] on the remote BW Agent[{1}]

22



TIBCO-BW-ADMIN-500228 Invalid value supplied as minNodes. minNodes must be anInteger greater than 0.

TIBCO-BW-ADMIN-500229 AppSpace [{0}] is expanded to the BW Agent [{1}] on the filesystem, However the agent failed to update the status in thedatastore. <CausedBy> {2}

TIBCO-BW-ADMIN-500230 AppSpace [{0}] is expanded to the BW Agent [{1}] on the filesystem, However one or multiple applications failed to deployinto this AppSpace on the remote machine, check the status of theapplications in this AppSpace for details. <CausedBy> {2}

TIBCO-BW-ADMIN-500231 AppSpace [{0}] is expanded to the BW Agent [{1}] on the filesystem, However one or multiple applications failed to deployinto this AppSpace on the remote machine, check the status of theapplications in this AppSpace for details.

TIBCO-BW-ADMIN-500232 Errors while deleting AppNodes and/or AppSpace instances onlocal and/or remote machines.

TIBCO-BW-ADMIN-500300 The AppNode [{0}] does not exist in AppSpace [{1}] and Domain[{2}].

TIBCO-BW-ADMIN-500301 The AppNode [{0}] already exists in the AppSpace [{1}] Domain[{2}].

TIBCO-BW-ADMIN-500302 Failed to create AppNode [{0}] in AppSpace [{1}] in Domain [{2}],{3}

TIBCO-BW-ADMIN-500303 Start of AppNode [{0}] in AppSpace [{1}] in Domain [{2}] timedout.

TIBCO-BW-ADMIN-500304 AppNode [{0}] in AppSpace [{1}] in Domain [{2}] did not start, {3}

TIBCO-BW-ADMIN-500305 AppNode [{0}] in Domain [{1}] did not stop, {2}

TIBCO-BW-ADMIN-500306 Failed to delete AppNode [{0}] in AppSpace [{1}] in Domain [{2}],{3}

TIBCO-BW-ADMIN-500307 Stop AppNode [{0}] in Domain [{1}] timed out.

TIBCO-BW-ADMIN-500308 Reached wrong AppNode [{0}] in AppSpace [{1}] in Domain [{2}].Expected was [{3}].

TIBCO-BW-ADMIN-500309 Failed to enable console on AppNode [{0}] in AppSpace [{1}] inDomain [{2}], {3}

TIBCO-BW-ADMIN-500310 Failed to disable console on AppNode [{0}] in AppSpace [{1}] inDomain [{2}], {3}

TIBCO-BW-ADMIN-500311 Failed to update AppNode [{0}] in data store, {1}

23



TIBCO-BW-ADMIN-500312 Failed to configure AppNode [{0}], {1}

TIBCO-BW-ADMIN-500313 AppNode [{0}] is not running or cannot be contacted

TIBCO-BW-ADMIN-500314 The AppNode [{0}] is still in [{1}] state. Please stop the AppNodefirst or use the -force option.

TIBCO-BW-ADMIN-500315 No AppNodes are present in the AppSpace [{0}] in the Domain[{0}].

TIBCO-BW-ADMIN-500316 AppNode [{0}] log file does not exist or could not be read

TIBCO-BW-ADMIN-500317 Agent log file does not exist or could not be read

TIBCO-BW-ADMIN-500318 The AppNode [{0}] is running. Stop the AppNode first and tryagain.

TIBCO-BW-ADMIN-500319 Port is taken, cause: {0}

TIBCO-BW-ADMIN-500320 AppNode [{0}] encountered an Internal Server Error. Please checkthe log file of the AppNode for details.

TIBCO-BW-ADMIN-500321 Failed to disable debugger on AppNode [{0}] in AppSpace [{1}] inDomain [{2}]. <CausedBy> {3}

TIBCO-BW-ADMIN-500322 Failed to obtain BW Engine information on AppNode [{0}] inAppSpace [{1}] in Domain [{2}]. <CausedBy> {3}. Please check thelog file of the AppNode for details.

TIBCO-BW-ADMIN-500400 The supplied deployment artifact [{0}] does not exist.

TIBCO-BW-ADMIN-500401 Application [{0}] not found in the Domain [{1}] {2}

TIBCO-BW-ADMIN-500402 Failed to deploy application [{0}:{1}], <CausedBy> {2}

TIBCO-BW-ADMIN-500403 Failed to undeploy application [{0}:{1}], <CausedBy> {2}

TIBCO-BW-ADMIN-500404 The Application [{0}] is in undeployed state.

TIBCO-BW-ADMIN-500405 The deployment artifact [{0}] supplied is not valid

TIBCO-BW-ADMIN-500406 Failed to deploy hotfix to application [{0}:{1}].

TIBCO-BW-ADMIN-500407 Version [{0}] is not valid. Only <major>.<minor> version format issupported.

TIBCO-BW-ADMIN-500408 Failed to undeploy hotfix to application [{0}:{1}].

TIBCO-BW-ADMIN-500409 Failed to start application [{0}:{1}], <CausedBy> {2}

TIBCO-BW-ADMIN-500410 Failed to stop application [{0}], <CausedBy> {1}

24



TIBCO-BW-ADMIN-500411 Deployment of [{0}] completed. The installation into runningAppNodes failed for some AppNodes. Please check log files formore details.

TIBCO-BW-ADMIN-500412 Deployment of [{0}] completed. The start of the application orlibrary in the running AppNodes failed for some AppNodes.Please check log files for more details.

TIBCO-BW-ADMIN-500413 Failed to update the application [{0}] in the data store,<CausedBy> {1}

TIBCO-BW-ADMIN-500415 Failed to upload to one or multiple remote machines.

TIBCO-BW-ADMIN-500416 Error encountered installing {0} [{1}] [{2}] on AppNode [{3}]

TIBCO-BW-ADMIN-500417 Error encountered starting {0} on AppNode [{1}]

TIBCO-BW-ADMIN-500418 Application archive file [{0}] not found in the domain [{1}]

TIBCO-BW-ADMIN-500419 Application archive file [{0}] could not be deleted from data store.

TIBCO-BW-ADMIN-500420 Name includes only invalid characters and does not comply withnaming conventions. Allowed characters are upper and lowercase characters of the alphabet as well as digits, '.' and '-'.

TIBCO-BW-ADMIN-500421 Configuration of Application [{0}] failed, <CausedBy> {1}

TIBCO-BW-ADMIN-500422 Failed to delete Application archive file on one or multipleremote machines.

TIBCO-BW-ADMIN-500423 Application [{0}] already exists in the domain [{1}] and it isdeployed from the archive file [{2}]

TIBCO-BW-ADMIN-500424 Failed to read profile from [{0}]

TIBCO-BW-ADMIN-500425 Profile [{0}] is not present in the Archive [{1}]

TIBCO-BW-ADMIN-500426 Failed to export Profile [{0}] from the Archive {1}.

TIBCO-BW-ADMIN-500427 Failed to export configuration of Application [{0}] Version [{1}]AppSpace [{2}] Domain [{3}].

TIBCO-BW-ADMIN-500428 Failed to get configuration of Application [{0}] Version [{1}]AppSpace [{2}] Domain [{3}] from the remote agent.

TIBCO-BW-ADMIN-500429 Failed to export configuration of Application Instance [{0}]Version [{1}] AppNode [{2}] AppSpace [{3}] Domain [{4}].

TIBCO-BW-ADMIN-500430 Application Instance [{0}] Version [{1}] on AppNode [{2}]AppSpace [{3}] Domain [{4}] is not found.

TIBCO-BW-ADMIN-500431 Error encountered pausing {0} [{1}] on AppNode [{2}]

25



TIBCO-BW-ADMIN-500432 Error encountered resuming {0} [{1}] on AppNode [{2}]

TIBCO-BW-ADMIN-500433 Pausing of [{0}] completed. Please check log files for more details.

TIBCO-BW-ADMIN-500434 Pausing of [{0}] completed. Please check log files for more details.

TIBCO-BW-ADMIN-500435 Failed to pause Application [{0}], <CausedBy> {1}

TIBCO-BW-ADMIN-500436 Failed to resume Application [{0}], <CausedBy> {1}

TIBCO-BW-ADMIN-500437 Failed to start in one or more AppNodes.

TIBCO-BW-ADMIN-500438 Failed to restore AppInstance configuration, <CausedBy> {0}

TIBCO-BW-ADMIN-500457 Error encountered starting process starters of {0} [{1}] [{2}] onAppNode [{3}]

TIBCO-BW-ADMIN-500439 Error encountered stopping process starters of {0} [{1}] [{2}] onAppNode [{3}]

TIBCO-BW-ADMIN-500440 Starting process starters of [{0}] completed. Please check log filesfor more details.

TIBCO-BW-ADMIN-500441 Stopping process starters of [{0}] completed. Please check log filesfor more details.

TIBCO-BW-ADMIN-500442 Failed to start process starters of Application [{0}], <CausedBy>{1}

TIBCO-BW-ADMIN-500443 Failed to stop process starters of Application [{0}], <CausedBy>{1}

TIBCO-BW-ADMIN-500444 Failed to start Application in AppNode [{0}]. Check the AppNodelog files for messages starting with TIBCO-THOR-FRWK, TIBCO-BW-FRWK, or TIBCO-BW-SR-FRWK for details. ApplicationState [{1}], reason : {2}

TIBCO-BW-ADMIN-500445 AppSpace [{0}] is not found. Create the AppSpace first and re-try.

TIBCO-BW-ADMIN-500446 The application [{0}] from archive [{1}] has been deployed to theseAppSpaces: {2}

TIBCO-BW-ADMIN-500447 Archive [{0}] is already present in the domain, use -replace optionto replace the existing archive.

TIBCO-BW-ADMIN-500448 Applications are out of sync with the archive they were deployedfrom, They have to be re-deployed to keep them in sync.

TIBCO-BW-ADMIN-500449 The archive [{0}] in the domain is replaced, Deploy theapplication again to apply the latest version.

TIBCO-BW-ADMIN-500450 Archive [{0}] has been deployed to the AppSpaces: {1}

26



TIBCO-BW-ADMIN-500451 Port is taken by AppNode[{0}] in AppSpace[{1}] in Domain[{2}]

TIBCO-BW-ADMIN-500452 Failed to obtain bwagents of the machine [{0}].

TIBCO-BW-ADMIN-500453 http interface and port of bwagent [{0}] conflicted with thesupplied interface and port

TIBCO-BW-ADMIN-500454 TEA interface and port of the bwagent [{0}] conflicted with thesupplied interface and port

TIBCO-BW-ADMIN-500455 Interface and the port of listen URL of the BW Agent [{0}] conflictwith the supplied interface and port

TIBCO-BW-ADMIN-500456 Interface and the port of listen URL of the BW Agent [{0}] conflictwith the supplied interface and port

TIBCO-BW-ADMIN-500460 Archive was created with a newer version of the product [{0}] andcannot be installed into the current version [{1}]. Upgrade theproduct and try again

TIBCO-BW-ADMIN-500461 Invalid archive for this product version. Only archives with singlemodules are supported.

TIBCO-BW-ADMIN-500462 Archive was created with different BusinessWorks Edition andcannot be installed in current product. Upgrade the product andtry again.

TIBCO-BW-ADMIN-500504 Failed to register TEA Agent [{0}] with TEA server [{1}], {2}

TIBCO-BW-ADMIN-500505 Failed to enable port on the AppNodec[{0}] in AppSpace [{1}] inDomain [{2}], <CausedBy> {3}

TIBCO-BW-ADMIN-000001 {0}

TIBCO-BW-ADMIN-000100 Failed to create the application [{0}] in the data store

TIBCO-BW-ADMIN-000101 Failed to read archive file for [{0}] from data store

TIBCO-BW-ADMIN-000200 Internal error: {0}

Engine Error CodesThis section describes the error messages that can be reported by the Engine layers.


TIBCO-BW-CORE-000001 {0}

TIBCO-BW-CORE-000010 BWActivityManager Registration Error. The BWActivityManagerargument provided to the BW Engine is null.

27



TIBCO-BW-CORE-000012 Failed to initialize BW Engine. The BW Engine was initializedwithout a logger object.

TIBCO-BW-CORE-000018 Failed to initialize BW Engine. While registeringBWActivtyBridge the BW Engine encountered exception [{0}]

TIBCO-BW-CORE-000020 Failed to initialize BW Engine. The BWActivityManager was notregistered correctly with the BW Engine.

TIBCO-BW-CORE-000022 Failed to initialize BW Engine. The BW Crypto service was notregistered correctly with the BW Engine.

TIBCO-BW-CORE-000024 Failed to initialize BW Engine. The BW Custom XPath FunctionManager service was not registered correctly with the BW Engine.

TIBCO-BW-CORE-000026 Failed to enable BW Debugger. The BW Engine has not beeninitialized.

TIBCO-BW-CORE-000028 The BW Debugger is already enabled state and it can not beenabled again.

TIBCO-BW-CORE-000030 Unable to disable BW Debugger. The BW Engine has not beeninitialized.

TIBCO-BW-CORE-000032 Attempt to disable the BW Debugger encountered exception [{0}]

TIBCO-BW-CORE-000034 Unable to enable BW Event Publisher. The BW Engine has notbeen initialized.

TIBCO-BW-CORE-000036 BW Engine configuration data does not contain AppNode name.

TIBCO-BW-CORE-000038 BW Engine configuration data does not contain AppSpace name.

TIBCO-BW-CORE-000040 BW Engine configuration data does not contain Domain name.

TIBCO-BW-CORE-000052 The operation [{0}] is not supported for the BX Non-ExecutableModule. ModuleName={0}, ModuleVersion={1}

TIBCO-BW-CORE-000054 The operation [{0}] is not supported for the BX ExecutableModule. ModuleName={1}, ModuleVersion={2}

TIBCO-BW-CORE-000056 The operation [{0}] is not supported for the BW Job SharedVariable.

TIBCO-BW-CORE-000057 Unable to obtain EngineManagement. The BW Engine has notbeen initialized.

TIBCO-BW-CORE-000058 Unable to obtain EngineManagement due to exception [{0}]

TIBCO-BW-CORE-000059 The BX operation [{0}] failed due to exception [{1}].

28



TIBCO-BW-CORE-000102 Invalid 'BWModuleHandle'. The BW module represented by thishandle has been already un-installed or the handle has beenalready destroyed.

TIBCO-BW-CORE-000104 Unable to obtain process templates referenced by BW Module,the BW Engine encountered exception. ModuleName[{0}],ModuleVersion[{1}], Exception[{2}].

TIBCO-BW-CORE-000116 Unable to obtain GenXDM SchemaComponentCache for the BWModule [{0}]. The operation [{1}] returned "null".

TIBCO-BW-CORE-000118 Unable to obtain GenXDM SchemaComponentCache for the BWModule [{0}]. The operation [{1}] returned exception [{2}]

TIBCO-BW-CORE-000120 Unable to obtain GenXDM SchemaComponentCache for the BWModule [{0}:{1}] due to exception [{2}]

TIBCO-BW-CORE-000122 Unable to obtain "BundleContext" for BW module [{0}:{1}]. Theoperation [{2}] returned "null"

TIBCO-BW-CORE-000124 Unable to obtain "BundleContext" for BW module [{0}:{1}] due toexception [{2}]

TIBCO-BW-CORE-000126 Unable to obtain ServiceReference for the cache service [{0}]. Theoperation "BundleContext.getServiceReference" for BW module[{1}:{2}] returned "null".

TIBCO-BW-CORE-000128 Unable to obtain ServiceReference for the cache service [{0}]. Theoperation "BundleContext.getServiceReference" for BW module[{1}:{2}] returned exception [{3}]

TIBCO-BW-CORE-000130 Unable to obtain XSD cache service [{0}] for the BW module [{1}:{2}]. The operation [{3}] returned "null".

TIBCO-BW-CORE-000131 Unable to obtain XSD cache service [{0}] for the BW module [{1}:{2}]. The operation [{3}] returned exception [{4}]

TIBCO-BW-CORE-000132 Unable to obtain WSDL cache service [{0}] for the BW module[{1}:{2}]. The operation [{3}] returned "null".

TIBCO-BW-CORE-000133 Unable to obtain WSDL cache service [{0}] for the BW module[{1}:{2}]. The operation [{3}] returned exception [{4}]

TIBCO-BW-CORE-000134 Unable to obtain WSDL ModuleCache from theWSDLCacheService for the WSDL namespace [{0}], locationURI[{1}] that is associated with the BW Module [{2}:{3}],DeploymentUnit [{4}:{5}]. The operation [{6}] returned "null".

TIBCO-BW-CORE-000135 Unable to obtain WSDL ModuleCache from theWSDLCacheService for the WSDL namespace [{0}], locationURI[{1}] that is associated with the BW Module [{2}:{3}],DeploymentUnit [{4}:{5}]. Encountered exception [{6}]

29



TIBCO-BW-CORE-000136 Unable to obtain BxWSDLResolver for the WSDL namespace[{0}], Location [{1}] that is associated with the BW Module [{2}:{3}], DeploymentUnit [{4}:{5}] due to exception [{6}]

TIBCO-BW-CORE-000137 Unable to obtain GenXDM WSDL Module for the WSDLnamespace [ {0} ] that is associated with the BW Module [{1}:{2}],DeploymentUnit [{3}:{4}]. The operation "{5}" returned exception[{6}]

TIBCO-BW-CORE-000138 Unable to obtain GenXDM WSDL Module for the WSDLnamespace [ {0} ] that is associated with the BW Module [{1}:{2}],DeploymentUnit [{3}:{4}]. The operation "{5}" returned "null".Ensure the BW Module [{6}] is dependent on a BW sharedmodule which contains the WSDL file for this WSDL namespaceor the BW Module [{7}] itself contains the required WSDL file.

TIBCO-BW-CORE-000140 Unable to obtain WSDL Message details from the GenXDMWSDL Module for the WSDL namespace [ {0} ] that is referencedin the BW Module [{1}:{2}] due to exception [{3}].

TIBCO-BW-CORE-000142 Unable to obtain WSDL Definition namespace details from theGenXDM WSDL Module for the WSDL namespace [ {0} ] that isassociated with the BW Module [{1}:{2}] due to exception [{3}].

TIBCO-BW-CORE-000144 Unable to obtain WSDL Target namespace from the GenXDMWSDL Module for the WSDL namespace [ {0} ] that is associatedwith the BW Module [{1}:{2}] due to exception [{3}].

TIBCO-BW-CORE-000146 Unable to obtain WSDL Interface details from the GenXDMWSDL Module for the PortType [{0}], that is associated with theBW Module [{1}:{2}]. The operation "{3}" returned exception [{4}].

TIBCO-BW-CORE-000148 Unable to obtain WSDL Interface details from the GenXDMWSDL Module for the PortType [{0}], that is associated with theBW Module [{1}:{2}]. The operation "{3}" returned null.

TIBCO-BW-CORE-000150 Unable to construct PortType details from the GenXDM WSDLInterface for the WSDL namespace [ {0} ] that is associated withthe BW Module [{1}:{2}] due to exception [{3}].

TIBCO-BW-CORE-000152 Invalid BWBxWSDLResolver. The instance of thisBWBxWSDLResolver has been already released.

TIBCO-BW-CORE-000160 The initial value mode [{0}] specified for the {1} [{2}] in BWModule [{3}:{4}], DeploymentUnit[{5}:{6}] is invalid.

TIBCO-BW-CORE-000162 The QName value [{0}] specified for the {1} [{2}] in BW Module[{3}] is invalid or malformed.

TIBCO-BW-CORE-000202 Invalid 'BWComponentHandle'. The BW Component representedby this handle has been already un-installed or the handle hasbeen already destroyed.

30



TIBCO-BW-CORE-000204 Unable to create ServiceEndpointRequestHandler for BWComponent due to invalid BW Process ServiceType [{0}].ComponentName={1}, ComponentVersion={2}

TIBCO-BW-CORE-000206 Unable to create ServiceEndpointRequestHandler for BWComponent due to invalid BW Process ServiceName [{0}].ComponentName={1}, ComponentVersion={2}

TIBCO-BW-CORE-000208 Error occurred while creating ServiceEndpointRequestHandlerfor service [{0}], BW Component [{1}], Application [{2}:{3}].Exception[{4}].

TIBCO-BW-CORE-000210 Unable to create ServiceEndpointRequestHandler for service [{0}],BW Component [{1}]. The operation"BxSystem.getInterfaceProvider" returned "null".

TIBCO-BW-CORE-000212 Received unexpected exception [{0}] from the service bindingassociated with the component service [{1}], Application [{2}] oninvocation of method [{3}].

TIBCO-BW-CORE-000214 Unable to obtain "BundleContext". The operation "{0}" returned"null"

TIBCO-BW-CORE-000216 Unable to obtain "BundleContext" due to exception [{0}]

TIBCO-BW-CORE-000220 Unable to obtain GenXDM WSDL Module for the WSDLnamespace [{0}] that is associated with the BW Component [{1}],Application[{2}:{3}]. The operation "{4}" returned exception [{5}]

TIBCO-BW-CORE-000222 Unable to obtain GenXDM WSDL Module for the WSDLnamespace [{0}] that is associated with the BW Component [{1}],Application[{2}:{3}]. The operation "{4}" returned "null".

TIBCO-BW-CORE-000224 Unable to obtain WSDL Interface details from the GenXDMWSDL Module for the PortType [{0}], that is associated with theBW Component [{1}], Application[{2}:{3}]. The operation "{4}"returned exception [{5}].

TIBCO-BW-CORE-000226 Unable to obtain WSDL Interface details from the GenXDMWSDL Module for the PortType [{0}], that is associated with theBW Component [{1}], Application[{2}:{3}]. The operation "{4}"returned null.

TIBCO-BW-CORE-000228 Unable to obtain ServiceReference for the cache service [{0}]. Theoperation "{1}" returned "null".

TIBCO-BW-CORE-000230 Unable to obtain ServiceReference for the cache service [{0}] dueto exception [{1}]

TIBCO-BW-CORE-000231 Unable to obtain cache service [{0}]. The operation "{1}" returned"null".

31



TIBCO-BW-CORE-000132 Unable to obtain cache service [{0}]. The operation "{1}" returnedexception [{2}].

TIBCO-BW-CORE-000232 Unable to construct PortType details from the GenXDM WSDLInterface for the WSDL namespace [{0}] that is associated with theBW Component [{1}] due to exception [{2}].

TIBCO-BW-CORE-000234 Unable to obtain ModuleCache for the BW Component [{0}]. Theoperation "{1}" returned "null".

TIBCO-BW-CORE-000235 Failed obtain value for the component level property [{0}], BWComponent [{1}], Application [{2}:{3}]. Encountered exception[{4}]

TIBCO-BW-CORE-000302 Invalid 'BWApplicationHandle'. The BW Application representedby this handle has been already un-installed or the handle hasbeen already destroyed.

TIBCO-BW-CORE-000304 Unable to create 'BWApplicationHandle' due to invalidBWComponentHandle list. The argument of type'List<BWComponentHandle>' must contain at least oneBWComponentHandle.

TIBCO-BW-CORE-000306 Unable to create 'BWApplicationHandle' due to inconsistentapplication names in the BWComponentHandle(s) contained inthe argument of type 'List<BWComponentHandle>'. The handlefor the BW Component [{0}] has application name as [{1}] whereas the first handle in the list has application name as [{2}].

TIBCO-BW-CORE-000308 Unable to create 'BWApplicationHandle' for the BW Application[{0}].

TIBCO-BW-CORE-000402 Error occurred when accessing the ProcessStarter activity [{0}] inprocess [{1}], module [{2}] from the BWActivityManager.Error={3}.

TIBCO-BW-CORE-000404 Error occurred when configuring the ProcessStarter activity [{0}]in process [{1}], module [{2}].

TIBCO-BW-CORE-000406 Unable to configure ProcessStarter activity [{0}] in process [{1}],module [{2}] due to crypto service access error.

TIBCO-BW-CORE-000408 HotUpdate operation not supported for ProcessStarter activity[{0}] in process [{1}], module [{2}]. The ProcessStarter alreadyexists for activitId [{3}].

TIBCO-BW-CORE-000502 Error occurred when accessing the SignalIn activity [{0}] inprocess [{1}], module [{2}] from the BWActivityManager.Error={3}.

TIBCO-BW-CORE-000504 Error occurred when configuring the SignalIn activity [{0}] inprocess [{1}], module [{2}].

32



TIBCO-BW-CORE-000506 Unable to configure SignalIn activity [{0}] in process [{1}], module[{2}] due to crypto service access error.

TIBCO-BW-CORE-000508 HotUpdate operation not supported for SignalIn activity [{0}] inprocess [{1}], module [{2}]. The SignalIn already exists foractivitId [{3}].

TIBCO-BW-CORE-000602 Failed to obtain activity [{0}] in process [{1}], module [{2}] fromthe BWActivityManager due to exception [{3}]. ActivityId [{4}].

TIBCO-BW-CORE-000604 Error occurred when configuring the activity [{0}] in process [{1}],module [{2}]

TIBCO-BW-CORE-000606 Unable to configure activity [{0}] in process [{1}], module [{2}] dueto crypto service access error.

TIBCO-BW-CORE-000608 Unable to execute [{0}] operation for an activity. Failed to lookupactivity [{1}] in process [{2}], module [{3}] from theBWActivityManager. ActivityId [{4}].

TIBCO-BW-CORE-000610 HotUpdate operation not supported for activity [{0}] in process[{1}], module [{2}]. The activity already exists for activitId [{3}].


TIBCO-BW-CORE-500010 Failed to initialize BW Engine due to exception [{0}]

TIBCO-BW-CORE-500011 Failed to initialize BW Engine due to database access error

TIBCO-BW-CORE-500012 Failed to initialize BW Engine due to engine group connectionprovider error

TIBCO-BW-CORE-500013 Failed to initialize BW Engine due to database schemaconfiguration error. The BW Engine database does not contain therequired tables. Ensure the BW Engine database has been createdwith the table schemas required by the engine

TIBCO-BW-CORE-500014 Failed to initialize BW Engine due to missing or incorrect enginedatabase configuration data. The BW Engine persistence modeproperty [{0}] is set to option [datastore] and this option requiresvalid engine database configuration data

TIBCO-BW-CORE-500015 Failed to initialize BW Engine due to missing or incorrect enginedatabase configuration data. The BW Engine persistence modeproperty [{0}] is set to option [group] and this option requiresvalid engine database configuration data

33



TIBCO-BW-CORE-500016 Failed to initialize BW Engine due to group name in-use error.The BW Engine database is configured for use by a differentgroup name and this database cannot be used for the specifiedengine group name [{0}]. Try using a different engine database orchange the specified engine group name to match the value in thedatabase

TIBCO-BW-CORE-500017 Failed to initialize BW Engine due to the incompatible persistencemode option configured between engine and in the enginedatabase. The BW Engine is configured to execute in persistencemode [group]; however the engine database is configured for thepersistence mode [datastore]. Try using a different database oruse a database that is configured for the persistence mode [group]

TIBCO-BW-CORE-500018 Failed to initialize BW Engine due to the incompatible persistencemode option configured between engine and in the enginedatabase. The BW Engine is configured to execute in persistencemode [datastore]; however the engine database is configured forthe persistence mode [group]. Try using a database that isconfigured for the persistence mode [datastore] or create a newengine database

TIBCO-BW-CORE-500019 Failed to initialize BW Engine due to missing or incorrect groupconnection provider configuration data. The BW Enginepersistence mode property [{0}] is set to option [group] and thisoption requires valid engine group connection providerconfiguration data.

TIBCO-BW-CORE-500020 Failed to initialize BW Engine due to incorrect engine groupname. The BW Engine persistence mode property [{0}] isconfigured with option [group] and this option requires a validengine group name specified via property [{1}].

TIBCO-BW-CORE-500021 Failed to initialize BW Engine. The BW Engine thread count valueis configured incorrectly. Ensure the thread count value is set toan integer that is greater than zero

TIBCO-BW-CORE-500022 Failed to initialize BW Engine. The BW Engine step count value isconfigured incorrectly. Ensure the step count value is set to "-1" oran integer that is greater than zero

TIBCO-BW-CORE-500023 Failed to initialize BW Engine. The BW Engine property [{0}]contains incorrect value [{1}]. Ensure the value is an integer that isgreater than one

TIBCO-BW-CORE-500024 Failed to initialize BW Engine. The BW Engine property [{0}]contains incorrect value [{1}]. Ensure the value is an integer that isgreater than one.

TIBCO-BW-CORE-500025 Failed to initialize BW Engine. While creatingSpringApplicationContext the BW Engine encountered exception:{0}.

34



TIBCO-BW-CORE-500026 The ProcessStarter or the SignalIn activity has not been initializedor it is in the destroyed state. The EventSourceContext associatedwith the ProcessStarter or the SignalIn activity is invalid.

TIBCO-BW-CORE-500030 BW Engine stop operation encountered exception [{0}]

TIBCO-BW-CORE-500031 BW Engine graceful stop operation encountered exception [{0}]

TIBCO-BW-CORE-500032 Exception occurred when accessing custom XPATH function(s)associated with the BusinessWork Engine. Exception={0}

TIBCO-BW-CORE-500033 Failed to enable the BW Debugger entity in the BW Engine due toexception [{0}]

TIBCO-BW-CORE-500034 BW Debugger connection failed, encountered exception [{0}]

TIBCO-BW-CORE-500035 Unable to enable Event Publisher in the BW Engine, encounteredexception [{0}]

TIBCO-BW-CORE-500036 Attempt to disable the Event Publisher in the BW Engine,encountered exception [{0}]

TIBCO-BW-CORE-500037 Unable to associate an activity resource with a BW group. Theactivity [{0}] in process [{1}] is not contained within a group;however the activity is attempting to associate a resource with agroup. {2}

TIBCO-BW-CORE-500038 Unable to associate an activity resource with a BW loop. Theactivity [{0}] in process [{1}] is not contained within a loop;however the activity is attempting to associate a resource with aloop. {2}

TIBCO-BW-CORE-500039 Reference Binding configured for the process reference [{0}], inprocess [{1}], module [{2}] provided unsupported message datamodel [{3}].

TIBCO-BW-CORE-500040 Invocation of the Process Reference's operation [{0}] failed. TheBW Reference Binding [{1}] configured for the process reference[{2}] in process [{3}], module [{4}] returned fault [{5}].

TIBCO-BW-CORE-500041 Invalid activity name. The activity name [{0}] is not found inprocess [{1}], module [{2}:{3}], DeploymentUnit [{4}:{5}].

TIBCO-BW-CORE-500042 The BW Debugger entity is already enabled in the BW Engineand it can not be enabled again.

TIBCO-BW-CORE-500050 The BW process [{0}] instance faulted, JobId [{1}],ProcessInstanceId [{2}], ParentProcessInstanceId [{3}], Module[{4}:{5}], Application [{6}:{7}]. {8}

TIBCO-BW-CORE-500051 Activity [{0}] fault. {1}

35



TIBCO-BW-CORE-500052 Invoke activity [{0}] fault. {1}

TIBCO-BW-CORE-500053 XSLT transformation error. {0}

TIBCO-BW-CORE-500054 Activity [{0}] XSLT transformation error. {1}

TIBCO-BW-CORE-500055 XPATH error. {0}

TIBCO-BW-CORE-500056 Activity [{0}] XPATH error. {1}

TIBCO-BW-CORE-500057 XML related error. {0}

TIBCO-BW-CORE-500058 Activity [{0}] XML related error. {1}

TIBCO-BW-CORE-500059 Reply activity [{0}] error. The reply activity cannot be associatedwith the ProcessService request message. This error can occur ifthe process is implemented to send reply multiple times for thesame request, the caller of this process is no longer available or onrecovery from a check-point the caller did not recover because itwas not part of the check-pointed job. {1}

TIBCO-BW-CORE-500060 The process instance terminated without replying to the caller ofthis process. {0}

TIBCO-BW-CORE-500061 Reply activity [{0}] error. The reply activity [{1}] is unable to sendthe response to the caller of this process. This error can occur ifthe caller of this process is no longer available or on recoveryfrom a check-point, the caller did not recover because it was notpart of the check-pointed job. {2}

TIBCO-BW-CORE-500062 ProcessStarter or SignalIn activity [{0}] fault. {1}


TIBCO-BW-CORE-500064 Activity [{0}] error. {1}

TIBCO-BW-CORE-500065 Throw activity [{0}] fault. Fault: {1}

TIBCO-BW-CORE-500066 Invoke activity faulted due an error from the invoked subprocess.{0}

TIBCO-BW-CORE-500067 Activity [{0}] faulted due to an object serialization error. Thiserror can occur if an object that must be serialized as part of theBusinessWorks process execution is not Serializable or the Javapackage that contains the class is not exported correctly. {1}

TIBCO-BW-CORE-500068 Fault occurred due to an object serialization error. This error canoccur if the Java class that must be serialized as part of theBusinessWorks process execution is not Serializable or the Javapackage that contains the class is not exported correctly. {0}

36



TIBCO-BW-CORE-500089 Failed to confirm the request message from the receive activity[{0}], in process [{1}], module [{2}:{3}], application [{4}:{5}]. Thiserror can occur if the process is implemented to confirm multipletimes for the same request message, the caller of this process is nolonger available, on recovery from a check-point the caller did notrecover because it was not part of the check-pointed job or thespecified receive activity name is incorrect.

TIBCO-BW-CORE-500090 The reply operation[com.tibco.bw.runtime.EventContext.reply(..)] is not supportedfor the activity [{0}], in process [{1}], module [{2}:{3}], application[{4}:{5}].

TIBCO-BW-CORE-500091 Invalid argument value. The BW Application name cannot benull.

TIBCO-BW-CORE-500092 Unable to get BW Process instances information for the BWApplication [{0}] due to exception [{1}].

TIBCO-BW-CORE-500093 Unable to get BW Process instance information for the BWProcessIntanceId [{0}] due to exception [{1}].

TIBCO-BW-CORE-500094 Unable to get BW Process instance summary information for theBW ProcessIntanceId [{0}] due to exception [{1}].

TIBCO-BW-CORE-500095 Failed to suspend the BW Process instance for the BWProcessIntanceId [{0}] due to exception [{1}].

TIBCO-BW-CORE-500096 Failed to resume the BW Process instance for the BWProcessIntanceId [{0}] due to exception [{1}].

TIBCO-BW-CORE-500097 Failed to cancel the BW Process instance for the BWProcessIntanceId [{0}] due to exception [{1}].

TIBCO-BW-CORE-500102 Failed to install BW Module [{0}:{1}], DeploymentUnit [{2}:{3}]

TIBCO-BW-CORE-500104 Encountered error(s) on release-resource operation for the BWModule [{0}:{1}], DeploymentUnit [{2}:{3}]

TIBCO-BW-CORE-500106 Encountered error(s) when un-deploying the BW Module [{0}:{1}],DeploymentUnit [{2}:{3}]

TIBCO-BW-CORE-500110 Failed to install BW Module [{0}:{1}], DeploymentUnit [{2}:{3}].The module or a process is configured to utilize the BW Enginepersistence feature; however the BW Engine is not configuredwith a correct engine persistence mode. Ensure the BW Engine isconfigured for the engine persistence mode [datastore] or [group]before installing this module.

TIBCO-BW-CORE-500112 Failed to start BW Module due to an activity start error.CausedBy

37



TIBCO-BW-CORE-500117 Unable to resolve SchemaComponentCache (BaseURI={0},Namespace={1}, Location={2}) for BW Module [{3}:{4}] due toexception [{5}]

TIBCO-BW-CORE-500118 Unable to add schema to SchemaComponentCache(Namespace={0}, Location={1}) due to exception [{2}]

TIBCO-BW-CORE-500119 Unable to obtain WSDL ModuleCache from the WSDLCacheService (WSDLAbsoluteLocation={0}, Namespace={1}) forBW Module [{2}:{3}]. The operation "{4}" returned "null".

TIBCO-BW-CORE-500120 Unable to obtain WSDL ModuleCache from the WSDLCacheService (WSDLAbsoluteLocation={0}, Namespace={1}) forBW Module [{2}:{3}]. The operation "{4}" returned exception [{5}]

TIBCO-BW-CORE-500121 Unable to obtain WSDL ModuleCache from the WSDLCacheService for the WSDL namespace [{0}], locationURI [{1}]that is referred in the BW Module [{2}:{3}], DeploymentUnit [{4}:{5}]. The operation [{6}] returned exception [{7}]

TIBCO-BW-CORE-500131 Invalid or empty file name is specified for the initial value of the{0} [{1}] in BW Module [{2}:{3}], DeploymentUnit [{4}:{5}].

TIBCO-BW-CORE-500132 The file [{0}] configured for the initial value of the {1} [{2}] is notfound in BW Module [{3}:{4}], DeploymentUnit [{5}:{6}].

TIBCO-BW-CORE-500133 Unable to access the file [{0}] configured for the initial value of the{1} [{2}] in BW Module [{3}:{4}], DeploymentUnit [{5}:{6}];encountered exception [{7}].

TIBCO-BW-CORE-500134 Unable to open the file [{0}] configured for the initial value of the{1} [{2}] in BW Module [{3}:{4}], DeploymentUnit [{5}:{6}];encountered exception [{7}].

TIBCO-BW-CORE-500135 Unable to read the file [{0}] configured for the initial value of the{1} [{2}] in BW Module [{3}:{4}], DeploymentUnit [{5}:{6}];encountered exception [{7}].

TIBCO-BW-CORE-500136 The contents of the file [{0}] configured for the initial value of the{1} [{2}] in BW Module [{3}:{4}], DeploymentUnit [{5}:{6}] isempty.

TIBCO-BW-CORE-500141 Invalid BW Module property. The module property [{0}] is notdefined in the BW Module [{1}:{2}], DeploymentUnit [{3}:{4}].Therefore the XPath function "getModuleProperty({5})" containedin the XSLT is not able to resolve this module property.

TIBCO-BW-CORE-500142 Unable to resolve the BW Module property [{0}] defined in theBW Module [{1}:{2}], DeploymentUnit [{3}:{4}] via the XPathfunction "getModuleProperty({5})" contained in the XSLT.Encountered exception [{6}].

38



TIBCO-BW-CORE-500143 Failed to create Binding ReferenceEndpoint for the processreference [{0}] in process [{1}], module [{2}:{3}], DeploymentUnit[{4}:{5}]; encountered exception [{6}]

TIBCO-BW-CORE-500144 Failed to obtain module properties for the module [{0}:{1}],DeploymentUnit [{2}:{3}]; encountered exception [{4}]

TIBCO-BW-CORE-500202 Failed to install BW Component [{0}], Application [{1}:{2}]

TIBCO-BW-CORE-500203 Failed to install BW Component [{0}], Application [{1}:{2}]. Theapplication is configured with Job PageThreshold property[bw.application.job.pageThreshold.*]; however the BW Engine isnot configured with a correct engine persistence mode. Ensurethe BW Engine is configured for the engine persistence mode[datastore] or [group] before installing this application.

TIBCO-BW-CORE-500210 Encountered error(s) on release-resource operation for the BWComponent [{0}], Application [{1}:{2}]

TIBCO-BW-CORE-500211 Encountered error(s) when un-deploying the BW Component[{0}], Application [{1}:{2}]

TIBCO-BW-CORE-500212 Failed to initialize BW Component [{0}], Application [{1}:{2}]

TIBCO-BW-CORE-500213 Failed to initialize BW Component [{0}], Application [{1}:{2}] dueto activity creation error

TIBCO-BW-CORE-500214 Failed to initialize BW Component [{0}], Application [{1}:{2}] dueto activity or resource configuration error

TIBCO-BW-CORE-500230 Failed to initialize BW Component [{0}], Application [{1}:{2}] dueto activity implementation error

TIBCO-BW-CORE-500232 Failed to initialize BW Component [{0}], Application [{1}:{2}] dueto activity initialization error

TIBCO-BW-CORE-500238 Encountered error when destroying the BW Component [{0}]

TIBCO-BW-CORE-500240 Encountered errors when destroying the BW Component [{0}]

TIBCO-BW-CORE-500242 Failed to start BW Component [{0}], Application [{1}:{2}]

TIBCO-BW-CORE-500246 Encountered error(s) when stopping the BW Component [{0}],Application [{1}:{2}]

TIBCO-BW-CORE-500248 Encountered error(s) when starting the ProcessStarter associatedwith the BW Component [{0}], Application [{1}:{2}]

TIBCO-BW-CORE-500250 Encountered error(s) when stopping the ProcessStarter associatedwith the BW Component [{0}], Application [{1}:{2}]

39



TIBCO-BW-CORE-500252 Failed to start ServiceBinding [{0}] for the BW Component [{1}],Application [{2}:{3}] due to ServiceBinding lifecycle error

TIBCO-BW-CORE-500254 Unable to stop ServiceBinding [{0}] for the BW Component [{1}],Application [{2}:{3}] due to ServiceBinding lifecycle error

TIBCO-BW-CORE-500256 The job flow limit property [{0}] for the application or thecomponent is configured incorrectly. Ensure the job flow limitproperty value is set to an integer that is greater than zero.

TIBCO-BW-CORE-500258 The job priority property [{0}] for the application or thecomponent is configured incorrectly. Ensure the job priorityproperty value is set to "low", "normal" or "high".

TIBCO-BW-CORE-500262 The property to enable activity input validation for theapplication or the component is configured incorrectly. Ensureproperties prefixed with [{0}] are set with value "true" or "false".

TIBCO-BW-CORE-500264 The property to enable activity output validation for theapplication or the component is configured incorrectly. Ensureproperties prefixed with [{0}] are set with value "true" or "false".

TIBCO-BW-CORE-500302 Failed to start BW Application [{0}] due to exception [{1}]

TIBCO-BW-CORE-500304 Failed to start BW Application [{0}:{1}] due to an activity error

TIBCO-BW-CORE-500306 Encountered error when attempting to gracefully stop BWApplication [{0}:{1}]

TIBCO-BW-CORE-500307 The BW Application [{0}:{1}] is already in stopping state. Unableto perform operation "stopApplicationGraceful"

TIBCO-BW-CORE-500308 Encountered error when attempting to stop BW Application [{0}:{1}]

TIBCO-BW-CORE-500310 Encountered errors when attempting to stop BW Application [{0}:{1}]

TIBCO-BW-CORE-500312 Unable to start ServiceBinding(s) or ProcessStarter(s) associatedwith the BW Application [{0}:{1}]

TIBCO-BW-CORE-500314 Unable to stop ServiceBinding(s) or ProcessStarter(s) associatedwith the BW Application [{0}:{1}]

TIBCO-BW-CORE-500316 Encountered error when attempting to pause BW Application[{0}:{1}] job(s)

TIBCO-BW-CORE-500318 Encountered error when attempting to resume BW Application[{0}:{1}] job(s)

TIBCO-BW-CORE-500402 Failed to create the ProcessStarter activity [{0}] in process [{1}],module [{2}] due to exception [{3}]

40



TIBCO-BW-CORE-500404 Failed to create the ProcessStarter activity [{0}] in process [{1}],module [{2}] due to unexpected exception [{3}]

TIBCO-BW-CORE-500406 Failed to initialize the ProcessStarter activity [{0}] in process [{1}],module [{2}] due to activity lifecycle error

TIBCO-BW-CORE-500408 Failed to initialize the ProcessStarter activity [{0}] in process [{1}],module [{2}] due to unexpected activity lifecycle error

TIBCO-BW-CORE-500410 Failed to start the ProcessStarter activity [{0}] in process [{1}],module [{2}] due to activity lifecycle error

TIBCO-BW-CORE-500412 Failed to start the ProcessStarter activity [{0}] in process [{1}],module [{2}] due to unexpected activity lifecycle error

TIBCO-BW-CORE-500414 The stop operation for the ProcessStarter activity [{0}] in process[{1}], module [{2}] failed with unexpected exception [{3}]

TIBCO-BW-CORE-500416 The destroy operation for the ProcessStarter activity [{0}] inprocess [{1}], module [{2}] failed with unexpected exception [{3}]

TIBCO-BW-CORE-500418 The release operation for the ProcessStarter activity [{0}] inprocess [{1}], module [{2}] failed with unexpected exception [{3}]

TIBCO-BW-CORE-500420 Failed to process the event from the ProcessStarter activity [{0}]

TIBCO-BW-CORE-500422 Failed to execute event from the ProcessStarter activity due toactivity output data validation error. The output data fromProcessStarter activity [{0}] does not conform to the ProcessStarteractivity output schema. Validation error details: {1}.

TIBCO-BW-CORE-500424 The BWEngine is unable accept new events from theProcessStarter activity [{0}], in process [{1}], module [{2}] sincethis ProcessStarter is in the stopped sate. The ProcessStarter isconsidered to be in the stopped state after the BW Engine hasinvoked of the operation"com.tibco.bw.runtime.EventSource.stop" or before theinvocation of the operation"com.tibco.bw.runtime.EventSource.start". When theProcessStarter is in stopped state, the BW Engine will not acceptnew events

TIBCO-BW-CORE-500502 Failed to create the SignalIn activity [{0}] in process [{1}], module[{2}] due to exception [{3}]

TIBCO-BW-CORE-500504 Failed to create the SignalIn activity [{0}] in process [{1}], module[{2}] due to unexpected exception [{3}]

TIBCO-BW-CORE-500506 Failed to initialize the SignalIn activity [{0}] in process [{1}],module [{2}] due to activity lifecycle error

41



TIBCO-BW-CORE-500508 Failed to initialize the SignalIn activity [{0}] in process [{1}],module [{2}] due to unexpected activity lifecycle error

TIBCO-BW-CORE-500510 Failed to start the SignalIn activity [{0}] in process [{1}], module[{2}] due to activity lifecycle error

TIBCO-BW-CORE-500512 Failed to start the SignalIn activity [{0}] in process [{1}], module[{2}] due to unexpected activity lifecycle error

TIBCO-BW-CORE-500514 The stop operation for the SignalIn activity [{0}] in process [{1}],module [{2}] failed with unexpected exception [{3}]

TIBCO-BW-CORE-500516 The destroy operation for the SignalIn activity [{0}] in process[{1}], module [{2}] failed with unexpected exception [{3}]

TIBCO-BW-CORE-500518 The release operation for the SignalIn activity [{0}] in process[{1}], module [{2}] failed with unexpected exception [{3}]

TIBCO-BW-CORE-500520 Failed to process the event from the SignalIn activity [{0}]

TIBCO-BW-CORE-500522 Failed to execute event from the SignalIn activity due to activityoutput data validation error. The output data from SignalInactivity [{0}] does not conform to the SignalIn activity outputschema. Validation error details: {1}

TIBCO-BW-CORE-500524 SignalIn activity event error. The method [{0}] is not supportedfor the BW SignalIn activity. SignalInActivityName={1},ProcessName={2}

TIBCO-BW-CORE-500526 The SignalIn activity [{0}] in process [{1}], module [{2}:{3}],application [{4}:{5}] generated fault [{6}]. {7}

TIBCO-BW-CORE-500528 While stopping the engine or application, the SignalIn activity[{0}] in process [{1}], module [{2}:{3}], application [{4}:{5}]generated fault [{6}]. {7}

TIBCO-BW-CORE-500530 The BWEngine is unable accept new events from SignalIn activity[{0}], in process [{1}], module [{2}] since this SignalIn is in thestopped sate. The SignalIn is considered to be in stopped stateafter the BW Engine has invoked of the operation"com.tibco.bw.runtime.EventSource.stop" or before theinvocation of the operation"com.tibco.bw.runtime.EventSource.start". When the SignalIn isin stopped state, the BW Engine will not accept new events

TIBCO-BW-CORE-500602 The model or the runtime class for the activity [{0}] in process[{1}], module [{2}] is implemented incorrectly. The activity modelclass [{3}] does not contain the configuration property [{4}] asdefined in the annotation for the member variable [{5}] declaredin the activity runtime class [{6}].

42



TIBCO-BW-CORE-500603 The model or the runtime class for the activity [{0}] in process[{1}], module [{2}] is implemented incorrectly. The activity model[{3}] does not contain the attribute [{4}] as defined in theannotation for the member variable [{5}] declared in the activityruntime class [{6}]. The attribute must be one of the following thatis specified in the activity model [{7}]

TIBCO-BW-CORE-500604 The model or runtime class for the activity [{0}] in process [{1}],module [{2}] is implemented incorrectly. The activity model class[{3}] associated with the activity runtime class [{4}] has aconfiguration property which is of unsupported data type. Theactivity configuration property data type [{5}] is not supported.

TIBCO-BW-CORE-500605 The model or runtime class for the activity [{0}] in process [{1}],module [{2}] is implemented incorrectly. Unable to set membervariable [{3}] declared in the activity runtime class [{4}].Encountered exception [{5}].

TIBCO-BW-CORE-500606 The resource specified for the process property [{0}] in process[{1}], module [{2}] is not available in the runtime environment.This process property is used by the activity [{3}] in process [{4}].Ensure the resource is configured and installed correctly.

TIBCO-BW-CORE-500607 The process property [{0}] in process [{1}], module [{2}] has anincorrect value [{3}]. This process property is used by the activity[{4}] in process [{5}]. Ensure the DateTime value has the format[{6}].

TIBCO-BW-CORE-500608 The resource obtained from the framework for the processproperty [{0}] in process [{1}], module [{2}] is not compatible withthe data type of the process property. Encountered exception[{3}].

TIBCO-BW-CORE-500610 One or more required fields of the activity [{0}] in process [{1}],module [{2}] is not configured correctly. Ensure the requiredfields of the activity contains valid data.

TIBCO-BW-CORE-500612 Failed to create the activity [{0}] in process [{1}], module [{2}] dueto exception [{3}]

TIBCO-BW-CORE-500614 Failed to create the activity [{0}] in process [{1}], module [{2}] dueto unexpected exception [{3}]

TIBCO-BW-CORE-500616 Failed to initialize the activity [{0}] in process [{1}], module [{2}]due to activity lifecycle error

TIBCO-BW-CORE-500618 Failed to initialize the activity [{0}] in process [{1}], module [{2}]due to unexpected activity lifecycle error

TIBCO-BW-CORE-500620 The execute operation for the activity [{0}] in process [{1}] failedwith unexpected exception [{2}]

43



TIBCO-BW-CORE-500622 The post-execute operation for the activity [{0}] in process [{1}]failed with unexpected exception [{2}]

TIBCO-BW-CORE-500624 The cancel operation for the activity [{0}] in process [{1}], module[{2}] failed with unexpected exception [{3}]

TIBCO-BW-CORE-500626 Unable to execute cancel operation for the activity [{1}] in process[{2}], module [{3}] due to exception [{4}]

TIBCO-BW-CORE-500628 The destroy operation for the activity [{0}] in process [{1}],module [{2}] failed with unexpected exception [{3}]

TIBCO-BW-CORE-500630 The module property [{0}] is not defined in the BW Module [{1}:{2}]

TIBCO-BW-CORE-500632 The module property [{0}] has not been registered with theactivity context or the event source context.

TIBCO-BW-CORE-500634 Failed to resolve module property [{0}] from the BW Module [{1}:{2}]

TIBCO-BW-CORE-500636 Activity [{0}] timed out.

TIBCO-BW-CORE-500637 Checkpoint activity [{0}] detected duplicate key.

TIBCO-BW-CORE-500638 Activity input data validation error. The input data for activity[{0}] in process [{1}], module [{2}] does not conform to the activityinput schema. {3} {4}

TIBCO-BW-CORE-500640 Activity output data validation error. The output data fromactivity [{0}] in process [{1}], module [{2}] does not conform to theactivity output schema. {3} {4}

TIBCO-BW-CORE-500641 Activity input/output data validation error. The input/outputdata for activity [{0}] in process [{1}], module [{2}] does notconform to the activity input/output schema. {3} {4}

TIBCO-BW-CORE-500642 Unable to obtain activity input data. The BW Engine has not beeninitialized or started.

TIBCO-BW-CORE-500643 Unable to obtain activity input data. The specified ActivityEventobject is invalid, the ActivityEvent can not be null.

TIBCO-BW-CORE-500644 Unable to obtain activity input data due to exception [{0}]

TIBCO-BW-CORE-500645 Unable to obtain activity output data. The BW Engine has notbeen initialized or started.

TIBCO-BW-CORE-500646 Unable to obtain activity output data. The specified ActivityEventobject is invalid, the ActivityEvent can not be null.

TIBCO-BW-CORE-500647 Unable to obtain activity output data due to exception [{0}]

44



TIBCO-BW-CORE-500702 Unable to process the request message for the component service[{0}], Application [{2}] due to specified invalid operation name[{2}].

TIBCO-BW-CORE-500703 Unable to process the request message for the operation [{0}] ofthe component service [{1}], Application [{2}] due to exception[{3}]

TIBCO-BW-CORE-500704 Unable to process the request message for the operation [{0}] ofthe component service [{1}], Application [{2}] due to invalidResponseContext. The operation [{3}] returned "null".

TIBCO-BW-CORE-500705 Unable to process the request message for the operation [{0}] ofthe component service [{1}], Application [{2}] due to invalidResponseContext. The operation [{3}] returned "null".

BX-100001 Branches are greater than number of iterations

BX-100002 Invalid expression value: [{0}] [{1}]

BX-100003 Invalid variables: [{0}]

BX-500001 Conflicting receive

BX-500002 Activity [{0}] timed out

BX-500003 Duplicate key detected [{0}]

BX-500004 Unsafe to delete case [{0}]

BX-500005 Error evaluating precondition for Adhoc activity

BX-200001 Unexpected State: [{0}]

BX-200002 Parsing Error: [{0}]

BX-200003 Variable [{0}] not found

BX-200004 unexpected predecessor state: [{0}]

BX-200005 Not supported

BX-200006 Assertion error @{0}

BX-200007 Exception handling exception.

BX-200008 [{0}]

BX-300001 SQL Exception: ErrorCode = [{0}], SQLState = [{1}], Message =[{2}].

45



BX-400001 Correlation Violation. Correlation set, [{0}] does not match theinbound/outbound message.

BX-400002 Correlation Violation. Correlation set, [{0}] is already initiated.

BX-400003 Correlation Violation. Correlation set, [{0}] has not beenpreviously initiated.

BX-600000 Reply activity, [{0}] cannot be associated receive activity.

BX-600001 Reply activity [{0}], variable and fromPart are missing.

BX-600002 Reply activity, [{0}] was unable to send reply using partner link[{1}], operation [{2}] and message exchange [{3}]. Cause: [{4}]

BX-600003 Partner link [{0}] is missing.

BX-600004 Receive activity [{0}], variable and fromPart are missing.

BX-600005 Missing reply. The process [{0}] ended without replying tooperation [{1}].

BX-600006 Invoke activity, [{0}] was unable to send a message using partnerlink [{1}], operation [{2}]. Cause: {3}

BX-600007 Invoke activity [{0}], inputVariable and toPart are missing.

BX-600008 Invoke activity [{0}], outputVariable and fromPart are missing.

BX-600009 Reference provider not found for partner link [{0}]

BX-600010 Operation [{0}] for service [{1}] not found.QUERY_OPERATION_NOT_FOUND = Process [{0}] operation[{1}] not found.

BX-600011 Activity, [{0}] in module [{1}], module version [{2}] cannot findexpected message.

BX-600012 Unable to process message for operation [{0}] in process [{1}],module [{2}], module version [{3}].

BX-600013 Message, [{0}] does not match message definition.

BX-600014 Message definition not found for [{0}]

BX-600015 Value is not specified for [{0}].

BX-600016 Process identifier field missing process name.

BX-600017 Package [{0}] version [{1}] not found.

BX-600018 Process [{0}] not found.

46



BX-600019 Process [{0}] implements different interface.

BX-600020 Sub-process cancelled

BX-600021 Error thrown with error code [{0}].

BX-600022 Missing port type for service [{0}]. One possible reason could be amissing WSDL file.

BX-600023 Interface [{0}] with this port type [{1}] is already defined in service[{2}].

BX-600024 Operation [{0}] with partner link [{1}] not found.

BX-600025 Create module failed for module [{0}] version [{1}] application[{2}]

BX-600026 Problem encountered during system initialization

BX-600027 Problem encountered during system stop

BX-600028 Adding definition failed for process [{0}]

BX-600029 Invalid process priority value [{0}]

BX-600030 ResourceManager release operation failed for [{0}]

BX-600031 Cannot perform operation on Module [{0}] with version [{1}]application [{2}] as it is in prepared for undeploy state and notavailable to do more work.

BX-600032 Cannot perform operation on Module [{0}] with version [{1}]application [{2}] as it is in marked for deletion state and notavailable to do more work.

BX-600033 Create module encountered a duplicate for module [{0}] version[{1}] application [{2}]

BX-600035 Process template instance with id [{0}] cannot be found.

BX-600036 Interface provider not found for partner link [{0}]

BX-600037 Init module failed for module [{0}] version [{1}] application [{2}]

BX-600038 Create template instance failed for module [{0}] version [{1}]application [{2}], process name [{3}]

BX-600039 Cycle detected while creating a template instance for template[{0}]

BX-600040 Start module failed for module [{0}] version [{1}] application [{2}]

47



BX-600041 Destroy module failed for module [{0}] version [{1}] application[{2}]

BX-600042 Stop module failed for module [{0}] version [{1}] application [{2}]

BX-600043 Process instance [{0}] already joined

BX-600045 Undeploy module failed for module [{0}] version [{1}] application[{2}]

BX-600046 Incoming message has more than one part, while expecting anelement for task [{0}] element name [{1}]

BX-600048 Update module failed for module [{0}] version [{1}] application[{2}]

BX-600050 Stop failed for application [{0}]

BX-600051 Start failed for application [{0}]

BX-600052 Singleton template instance for module [{0}] version [{1}]application [{2}] process name [{3}] cannot be found.

BX-600053 New exception event.

BX-600054 Interface provider not found for port type [{0}]

BX-600055 Partner role was not initialized

BX-600056 Mandatory parameter [{0}] not set.

BX-600057 Unexpected parameter [{0}] passed.

BX-600058 Problem encountered during system start, cause [{0}]

BX-600059 Exception processing activity [{0}], path [{1}]

BX-600060 Module [{0}] with name [{1}] already exists in application [{2}]

BX-700001 ExitOnStandardFault

BX-701001 An error encountered while setting up data.

BX-701002 The query is invalid. The expected query format is similar to aSQL select statement. Possible cause is [{0}].

BX-701003 The query cannot be empty.

BX-701004 The datetime value [{0}] is incorrect.

BX-701005 Process instance with id [{0}] cannot be found.

48



BX-701006 The specified query/paging id [{0}] is invalid. Please enter a validid of integer type.

BX-701007 Activity [{0}] is not found in the process template.

BX-701008 Activity [{0}] has not yet started for this process instance.

BX-701009 Priority [{0}] is invalid. Please enter a priority between 100(LOW)and 400 (EXCEPTIONAL) inclusive.

BX-701010 Parameter [{0}] not defined.

BX-701011 The specified activity id [{0}] is invalid. Please enter a valid stringi.e. pvm:010A.2.1c

BX-701012 Deadline not in use for activity [{0}].

BX-701013 Module [{0}] with version [{1}] in application [{2}] not found.

BX-701014 No wild card (*) selection is allowed in paginated queries.

BX-701015 An invalid status value has been selected.

BX-701016 User is not authorized to perform this operation on this instance.

BX-701017 Process [{0}] operation [{1}] not found.

BX-701018 Process [{0}] is not in the valid state.

BX-701019 Module [{0}] version [{1}] application [{2}] with process name [{3}]not found.

BX-701020 User is not privileged to perform this operation on this instance.

BX-701101 We cannot perform the operation [{0}] for [{1}] instances. Thisnumber surpasses the default limit of [{2}]. You may specify anew limit by using the java propertycom.tibco.bx.bulkoperation.maxsize

BX-701130 Operation failed: [{0}]. See log for details

Debugger operation [{0}] failed

BX-702001 An error occurred while initializing the debug. Cause: [{0}]

BX-702002 Debugger not available

BX-702003 Debugger operation [{0}] failed

BX-703001 Authorization failed.

BX-703002 Subject has no principal.

49



BX-703003 Too many organization ids: [{0}]

BX-800001 Process terminated

BX-800002 Process failed: [{0}] [{1}] Sub-process failed, reason: [{0}]

BX-800004 Generated fault reply failed

BX-800005 Action [{0}] failed to complete

BX-800006 Process suspended on error: [{0}]

BX-800007 ParameterName can not be null.

BX-800008 Task update from [{0}] failed.

BX-800009 Task reported an error

BX-905007 Dynamic service [{0}] not found, cause [{1}]

BX-905008 Service [{0}] for module [{1}] version [{2}] application [{3}] notfound.

BX-905009 Sub-process failed, reason: [{0}]

BX-905015 Invalid memory mode : [{0}]

BX-905016 Failed to confirm message, reason: [{0}]

BX-905017 Found more than one process [{0}] in [{1}].

BX-905018 Exception [{0}] occurred when initializing process manager.

BX-905019 Invalid selection, reason [{0}]

PVM-BMSG-110000 Pending Message already exists!

PVM-BMSG-110001 Waiting Receiver already exists!

PVM-BMSG-110002 Waiting Receiver Task does not exist!

PVM-BPEL-127000 Bpel failure: ''{0}''. .

PVM-BPEL-127001 BpelSelectionFailure: ''{0}''. .

PVM-BPEL-127002 BpelSelection: ''{0}''. .

PVM-BPEL-127003 Got an invalid node kind: ''{0}''. .

PVM-BPEL-127004 Bpel property registry not found.

50



PVM-BPEL-127005 Type converter not found: ''{0}''.

PVM-RUNNER-105001 Module ''{0}'' not deployed

PVM-CHK-100299 Not a valid value for this datatype

PVM-SYS-100000 Error with the System Forge, unable to create a PvmSystem

PVM-SYS-100101 Exception occurred loading configuration resource for {0}

PVM-SYS-100102 Exception validating configuration resource for {0}

PVM-SYS-100103 Class validation Error

PVM-SYS-100104 Class mismatch, {0} is not an instance of {1}

PVM-SYS-100105 Error Creating Attr: ''{0}'', Type: ''{1}'', Value: ''{2}'', Traits: ''{3}''

PVM-SYS-100106 Unsupported Environment Context

PVM-SYS-100107 Error starting service

PVM-SYS-100108 Error starting engine

PVM-SYS-100109 Engine not bound to group

PVM-SYS-100110 Cannot rebind active engine

PVM-SYS-100111 Error resuming engine

PVM-SYS-100120 Error connecting to DB resource

PVM-SYS-100121 Error accessing GroupConnectionProvider

PVM-SYS-100130 Required PVM DB tables do not exists

PVM-SYS-100131 Unable to determine schema version, make sure db user hascorrect privileges

PVM-SYS-100132 Incompatible storage schema, current version: {0} not incompatible range {1}

PVM-SYS-100140 Distributed System configured on Group[{0}] cannot start anengine for Group[{1}]

PVM-SYS-100141 Singleton System cannot start a distributed engine on Group[{0}]

PVM-SYS-100142 Distributed System configured on Group[{0}] cannot start aSingleton Engine

PVM-SYS-100201 Type is already registered: {0}

51



PVM-SYS-100202 Type {0} not registered in the {1} type system.

PVM-SYS-100203 Serializer not registered for type: {0}

PVM-SYS-100299 Factory is already registered: {0}

PVM-SYS-100301 Module ''{1}'' not deployed to Group ''{0}''

PVM-SYS-100302 Definition ''{1}''s Module not deployed

PVM-SYS-100303 The specified Module ''{1}'' has already been deployed to Group''{0}''

PVM-SYS-100304 Cannot delete active Module

PVM-SYS-100305 Cannot undeploy Module ''{0}'' because it has Process Instances

PVM-SYS-100306 Object ''{0}'' is deployed (or previously deployed) and cannot bemodified

PVM-SYS-100307 Module ''{0}'' does not exist

PVM-SYS-100308 Instance may not be created from disabled Definition ''{1}''

PVM-SYS-100309 Cannot delete a Group ''{0}'' with deployed Modules

PVM-SYS-100310 Cannot delete the Singleton Group

PVM-SYS-100311 Group already exists: {0}

PVM-SYS-100312 Compiled Definition (id

PVM-SYS-100313 Compiled Module (id

PVM-SYS-100314 Only one Singleton Group is allowed per domain

PVM-SYS-100350 Error occurred when serializing the object

PVM-SYS-100351 Error occurred when deserializing the object

PVM-SYS-100501 Service ''{0}'' not found

PVM-SYS-100502 Service Error

PVM-MODEL-102001 Invalid Object: {0}

PVM-MODEL-102002 The Object was not found: {0}

PVM-MODEL-102003 Module names and Process Definition names within Modulesmust be unique: ''{0}''

52



PVM-MODEL-102004 A child-parent concurrency exception: {0} invoked event {1} on itsancestor {2}

PVM-MODEL-102005 System is not setup to handle the specified ExecMode: {0}

PVM-MODEL-102006 Behavior does not handle 'uncaught exceptions'

PVM-MODEL-102007 Wrong Object Type: {0}

PVM-MODEL-102008 Application names must be unique: ''{0}''

PVM-MODEL-102101 Unable to find attribute ''{0}'' for object ''{1}''

PVM-MODEL-102102 Attribute ''{0}'' already defined

PVM-MODEL-102103 Set Value ''{0}'' failed: value

PVM-MODEL-102104 Get Value ''{0}'' failed.

PVM-MODEL-102105 System Attribute ''{0}'' is not updateable

PVM-MODEL-102106 System Attribute names are reserved: ''{0}''

PVM-MODEL-102107 System Attributes are not deletable: {0}

PVM-MODEL-102108 Cannot set traits on System Attributes: {0}

PVM-MODEL-102109 Serialization of Attribute ''{0}'' failed.

PVM-MODEL-102110 Deserialization of Attribute ''{0}'' failed.

PVM-MODEL-102111 Read-only Attribute ''{0}'' can''t be updated

PVM-MODEL-102112 Error getting raw value.

PVM-MODEL-102113 Attribute ''{0}'' string value exceeded size limit''{1}'' string size''{2}''.

PVM-MODEL-102114 Attribute has been paged-out and is currently inaccessible.

PVM-MODEL-102301 Operation not allowed on Definition

PVM-MODEL-102302 Cannot create a Process Definition from a running instance: {0}

PVM-MODEL-102303 Root Task Type is missing for process ''{0}''

PVM-MODEL-102304 A Definition has Instances and can't be deleted.

PVM-MODEL-102305 An InMemory Process Instance cannot spawn a Persisted ProcessInstance.

53



PVM-MODEL-102306 Root Task not set for Process

PVM-MODEL-102307 Cannot create child using as source this task or one of itsancestors in this process definition

PVM-MODEL-102398 Cannot create a Process Definition from an Instance

PVM-MODEL-102399 Structural Modification of instances not supported

PVM-MODEL-102401 Extender key ''{1}'' already registered for this task {0}

PVM-MODEL-102402 A Control Flow link''s parent must be the same as it To and Fromtasks'' parent

PVM-MODEL-102403 Link''s parent must be an ancestor to its task endpoints

PVM-MODEL-102450 Virtuals being instantiated may not have a multi-instanceancestor: {0}

PVM-MODEL-102451 Tasks may only instantiate its direct children

PVM-MODEL-102452 Model Event sources must be instantiated workunits or null,indicating an external source

PVM-MODEL-102453 A Path Starter's instantiated parent could not be found.

PVM-MODEL-102454 Operation may only be performed on an instantiated workunit.

PVM-MODEL-102455 Could not find Multi-Instance Master Task

PVM-MODEL-102456 Path Starter Links does not have a Entered-By Task

PVM-MODEL-102457 Instantiated Link does not have an instantiated predecessor task

PVM-MODEL-102458 Tokenized Link has no instantiated predecessor

PVM-MODEL-102459 External objects may not send Enter Events

PVM-MODEL-102460 Processes may only send Enter Events to the Root Task

PVM-MODEL-102501 Life Cycle command ''{0}'' is not allowed from ''{1}'' status

PVM-MODEL-102502 Life Cycle ''{0}'' cannot overide other final statuses: ''{1}''

PVM-MODEL-102503 LifeCycle event was rejected: {0}

PVM-MODEL-102601 The direct successor of this task must be a sibling: {0}

PVM-MODEL-102602 Task already has a direct successor

PVM-MODEL-102603 Task already has a direct predecessor

54



PVM-MODEL-102604 A From or To Task may not be the Root Task or an Extender Task

PVM-MODEL-102605 Root and Extender Tasks must be Base Tasks, not Multi-InstanceTasks: {0}

PVM-MODEL-102606 Root and Extender Tasks cannot be Path Starter or Stoppers

PVM-MODEL-102607 Only the first task in a Direct Sequence may be a Path Starter.

PVM-MODEL-102608 Only the last task in a Direct Sequence may be a Path Stopper.

PVM-MODEL-102609 A non-sibling link may not be a Path Starter or Stopper.

PVM-MODEL-102901 One or more set-values failed: (0)

PVM-DATA-104005 Serialization Error: Type

PVM-DATA-104006 Deserialization error: {0}

PVM-DATA-104007 Validation Error

PVM-DATA-104008 Pvm ObjectInputStream required to deserialize this object: {0}

PVM-DATA-104009 Can't find serializer for the datatype: {0}

PVM-DATA-104010 Conversion Error

PVM-TX-109001 A transaction is already in progress

PVM-TX-109002 No transaction is in progress

PVM-TX-109003 Unexpected Transaction Rollback

PVM-CHKPT-100101 Process {0} already associated with DupKey {1}

PVM-AQL-117000 AQL Query parsing error: ''{0}''. Check the syntax.

PVM-AQL-117001 Invalid system property passed in the query: ''{0}''. Check thequery string passed.

PVM-AQL-117002 Data type not specified: ''{0}''.

PVM-AQL-117003 Indexed attribute not supported on this type object: ''{0}''. Checkthe query string passed.

PVM-AQL-117004 Paged list not indexed.

PVM-AQL-117005 Page number ''{0}'' is higher than the number of pages in the list:''{1}''.

PVM-AQL-117006 Exception ''{0}'' occurred during execution of the query ''{1}''

55



PVM-AQL-117007 Serializer not found for the data type ''{0}''

PVM-AQL-117008 Exception while converting values ''{0}''

PVM-AQL-117009 Database field type not specified for the data type serializer ''{0}''

PVM-XML-106000 Unable to locate XML schema with namespace ''{0}'' and location''{1}''

PVM-XML-106001 XML Validation failed for data ''{0}''

PVM-XML-106002 XML serialization failed for data ''{0}''

PVM-XML-106003 XML deserialization failed for data ''{0}''

PVM-XML-106004 Compilation failed for Xpath expression ''{0}''

PVM-XML-106005 Evaluation failed for Xpath expression ''{0}''

PVM-XML-106006 XML Schema validation failed for namespace ''{0}''

PVM-XML-106007 Data Env already defined: ''{0}''

PVM-XML-106008 Schema not registered: ''{0}''

PVM-XML-106009 Namespace context not provided: ''{0}''

PVM-XML-106010 Data Env not found for: ''{0}''

PVM-XML-106011 Metabridge schema ''{0}'' load exception"

PVM-XML-106012 Unsupported Value for this datatype: {0}

PVM-XML-106013 Date Error

PVM-XML-106014 Negative minutes in date

PVM-XML-106015 Number greater than 100 in a 2-digit converter

PVM-XML-106016 Data Retrieval Error: ''{0}''

PVM-XML-106017 Expression Evaluation Error: ''{0}''

PVM-XML-106018 Expression Creation Error: ''{0}''

PVM-XML-106019 Expression Unsupported Error: ''{0}''

PVM-XML-106020 Exception loading schema into MetaBridge: {0}

PVM-XML-106021 Schema could not be registered: {0}

56



PVM-XML-106022 Application already registered for the system: {0}

PVM-XML-106023 Cannot register schema in a locked Data Env: {0}

PVM-XML-106024 Cannot find XML data type: {0}

PVM-XML-106025 Null or empty namespace used during schema registration: {0}

PVM-XML-106026 Transformation preparation failed for XSLT input ''{0}''

PVM-XML-106027 Transformation failed for XSLT input ''{0}''

PVM-XML-106028 Different types defined for the same name ''{0}''

PVM-XML-106029 Restrictions in type ''{0}'' do not match: ''{1}''

PVM-XML-106030 Different type names within the same element: ''{0}'' and ''{1}''

PVM-XML-106031 Not the same type: ''{0}''

PVM-XML-106032 Cannot find XML element: {0}

PVM-PERSIST-100001 Database Query Error: {0}

PVM-PERSIST-100002 Found more than 1 Object matching id: {0}

PVM-PERSIST-100003 Sequence {0} not found.

Hawk Microagents Error CodesThis section describes the error messages that can be reported by the Hawk microagents.


TIBCO-BW-HAWK-HMA-500002

Unable to enable HAWK HMA on the AppNode [{0}]. {1}

TIBCO-BW-HAWK-HMA-500003

Unable to stop HAWK HMA on the AppNode [{0}]. {1}

TEA Agent Error CodesThis section describes the error messages that can be reported by the TEA agent.


TIBCO-BW-TEAAGENT-500000

{0}


Failed to start TEA Agent, {0}

57




Error encountered during shutdown of TEA Agent


Please provide entity name to be created


Please provide entity name to be stopped


Please provide domain name


Please provide AppSpace name


Please provide AppNode name


Please provide AppNode HTTP port


Please provide application name


Please provide library name


Please provide object key


TEA Operation {0} is not available.


Failed to extract TEA Agent web application into [{0}]


Domain [{0}] is not present.


More than one Domain [{0}] is found.


AppSpace [{0}] in Domain [{1}] does not exist.


More than one AppSpace {0} in Domain [{1}] is found.


Machine {0} is not present.

58




More than one Machine {0} is found.


Please provide agent name.


Agent {0} is not present.


More than one Agent {0} is found.


Please provide EAR File Name.


Ear File {0} in Domain {1} is not present.


More than one Ear File {0} in Domain {1} is found.


Please use "show --help" to see available type of entities.


Entity [{0}] not found. Please use "show --help" to see availableentity types.


Application version is not present.


Application {0} in Domain {1} AppSpace{2} not found.


More than one application {0} in Domain {1} AppSpace{2} isfound.


Please provide installation Name.


Please provide machine name.


AppNode [{0}] in AppSpace [{1}] in Domain [{2}] not found.


Failed to register BW TEA agent [{0}] with TEA server,<CausedBy> {1}


Failed to update data store with current TEA Agent details

59




Failed to upload ear file into Domain [{0}]


Invalid pagination boundaries


Name contains invalid characters and does not comply withnaming conventions. Valid characters are upper and lower casecharacters of the alphabet as well as digits, '.' and '-'.


Name length exceeds 100 characters and it will be truncated tosatisfy the length limit


Name contains invalid characters.\nAllowed characters areupper and lower case characters of the alphabet as well as digits," ", "." and "-".\n.


Configuration of AppSpace [{0}] in Domain [{1}] failed, {2}


Library version missing.


Failed to create Domain [{0}]


Failed to delete Domain [{0}]


Failed to delete AppSpace [{0}] in Domain [{1}]


Failed to create AppSpace [{0}] in Domain [{1}]


Failed to create AppNode [{0}] in AppSpace [{1}] in Domain [{2}]


Failed to delete AppNode [{0}] in AppSpace [{1}] in Domain [{2}]


Failed to deploy Application from archive [{0}]


Profile file [{0}] does not exist.


Failed to upload Archive [{1}] in Domain [{0}]


Failed to delete Archive [{0}]

60




profileFile and profileName are mutually exclusive arguments.


Failed to undeploy Application [{2}] in AppSpace [{1}] of Domain[{0}]


Failed to create entity of type [{0}] with name [{1}] reason : {2}


Failed to delete Agent [{0}]


Failed to configure AppNode [{0}] in AppSpace [{1}] of Domain[{2}] <Cause> : {3}


Failed to get bwagents.


Failed to obtain machine records.


Failed to obtain installation records.


Failed to obtain bwagent log.


Failed to obtain AppNode records.


Failed to obtain bwagent configuration


Failed to obtain Application configuration


Failed to obtain Application metrics


Failed to stop process starters


Failed to start process starters


Failed to resume Application instance


Failed to resume Application

61




Failed to pause Application instance


Failed to pause Application instance


Failed to stop Application


Failed to stop Application instance


Failed to start Application instance


Failed to start Application


Failed to obtain AppNode log.


Failed to obtain AppNode thread dump.


Failed to start AppNode


Failed to stop AppNode


Failed to obtain AppNode names.


Failed to stop AppSpace


Failed to start AppSpace


Failed to obtain machines of an AppSpace


Failed to obtain softwares of an installation.


Failed to obtain machine states


Please provide port number

62




Please provide interface


Port is unavailable


bwagent [{0}] is using [{1}]:[{2}] as the {3} interface and port


AppSpace [{0}] already exists in domain [{1}]


Failed to configure Appliaction [{0}]


Invalid port number. Valid port range is (0, 65535).


Please provide destination for the backup file.


Destination argument is a folder where a file argument wasexpected.


Failed to backup domain [{0}]


Failed to configure Domain [{0}]


Failed to obtain Profile configuration


Invalid request.


AppInst not found


Failed to obtain application instance configuration.


No AppNodes available.


Failed to obtain agent system information


Failed to enable engine debug port

63




Failed to enable engine debug port


Failed to get BW Engine info


Failed to get Applications of Archive [{0}] in Domain [{1}]


Failed to start TEA Agent. Network name property not specified.Check configuration and restart.


{0}

64


Palettes

This section describes the error messages that can be reported by the activities or entities associatedwith palettes.

File Palette Error CodesThis section describes the error messages that can be reported by the activities or entities associatedwith the File palette.


TIBCO-BW-PALETTE-FILE-000001

{0}


File name [{0}] is not valid.


File [{0}] was not found.


File [{0}] already exists.


An exception [{0}] occurred when attempting to write to the file[{1}].


Unable to create file [{0}] due to file or directory denoted by thepathname [{1}] does not exist.


Cannot read the binary content from the file [{0}].


Cannot read the string content from the file [{0}].


The file encoding [{0}] is not valid.


Unable to rename the file from [{0}] to file [{1}].


Unable to rename the file from [{0}] to file [{1}]. The destinationfile exists and its type is different then the type of the source file.


The file activity [{0}] cannot be used to move a directory.


Cannot remove the file [{0}].


An exception [{0}] occurred when attempting to create the file[{1}].

65




Cannot overwrite the file [{0}] to file [{1}], when the overwrite flagis not selected in the activity configuration.


Cannot copy a directory [{0}] to an existing file [{1}].


Cannot copy multiple files [{0}] to an existing file [{1}].


Cannot create missing path [{0}].


Cannot copy from file [{0}] to file [{1}].


The file name value provided for the activity input is empty ornull.


File [{0}] was not found due to fault [{1}].


The ProcessStarter activity [{0}] failed to a generate a new eventdue to exception [{1}].


The Signal-In activity activity [{0}] failed to a generate a newevent due to exception [{1}].


The File Poller ProcessStarter activity [{0}] failed to a generate anew event due to exception [{1}] since it is in the stopped state.


The Waitforfilechange Signal-In activity [{0}] failed to a generate anew event due to exception [{1}] since it is in the stopped state.

FTP Palette Error CodesThis section describes the error messages that can be reported by the activities or entities associatedwith the FTP palette.


TIBCO-BW-PALETTE-FTP-500003

Unable to establish FTP connection for the FTP function [{0}].Encountered error [{1}].


File [{0}] already exists.


Error in PUT or MPUT command.


Error in GET or MGET command.

66




Client is not initialized [{0}].


Error in PUT or MPUT command. Local file specified cannot befound [{0}].


Unexpected reply code. Returned Code [{0}]. Expected Code [{1}].


Invalid user name or password.


Error in executing remote command [{0}].


FTP Connection Test Failed. Encountered error [{0}].


File [{0}] does not exist.


Error establishing active data socket. Reason [{0}].


Error performing mget. Reason: mget is not supported for FTPvia Proxy


Error in GET or MGET command.Error:[{0}].


Error in PUT or MPUT command.Error:[{0}].

General Palette Error CodesThis section describes the error messages that can be reported by the activities or entities associatedwith the BusinessWorks General Activities palette.


TIBCO-BW-PALETTE-GENERALACTIVITIES-000001

The Timer ProcessStarter activity [{0}] failed to generate a newevent due to exception [{1}]


Error executing external command [{0}]: [{1}].


Error accessing file or directory [{0}]: [{1}].


No command specified.

67




Input data error in field [{0}] expecting a valid [{1}]


Sleep interval value [{0}] is not valid.

TIBCO-BW-PALETTE-GENERAL-ACTIVITIES-500001

Activity configuration error. The {2} Shared Variable must beconfigured for {3} Shared Variable activity [{0}] in the process[{1}].


Activity configuration error. A Timeout expression configured forthe CheckPoint Activity [{0}] in the process [{1}] must be a validinteger expression.


Activity configuration error. A DuplicateKey expressionconfigured for the CheckPoint Activity [{0}] in the process [{1}]must be cast to a string. The expression should be configured as[string({2})].

HTTP Palette Error CodesThis section describes the error messages that can be reported by the activities or entities associatedwith the BusinessWorks HTTP palette.


TIBCO-BW-PALETTE-HTTP-000001

{0}


The Http Server replied with a [{0}] status code


The Http Server replied with a [{0}] status code


An exception was thrown while trying to initialize the Http client


An exception occurred while trying to initialize the Http server:[{0}]


A POST Method cannot send parameters if the message body isspecified


A GET Method doesn't have a message body


Invalid endpoint URL


Invalid input data. The encoding is not supported

68




The http method [{0}] is not valid


An exception was thrown while trying to url-encode the data


Attachment not supported for HTTP method [{0}]. Only HTTP'POST' can send attachments


Error serializing attachment data, Cause: [{0}]


An IOException was thrown while trying to execute the Httpmethod


An exception was thrown while trying to execute the Httpmethod. The Reason-code is [{0}]


An IOException was thrown while trying to read the response


An IOException was thrown while trying to send the response


An Exception was thrown while trying to send the response


The header [{0}] is defined as non-Repeating Header in InputHeaders. This header cannot have multiple occurrences inDynamicHeaders.


The HTTP ProcessStarter [{0}] failed to generate a new event dueto exception [{1}]


Failed to reply to HTTP ProcessStarter activity. This error canoccur if the HTTP Response activity is executed after recoveringfrom a check-pointed BusinessWorks process instance.


Failed to authenticate request. Username and Password is not set.

Java Palette Error CodesThis section describes the error messages that can be reported by the activities or entities associatedwith the BusinessWorks Java palette.


TIBCO-BW-PALETTE-JAVA-PROCESSSTARTER-000001

[{0}]

69




The JAVA ProcessStarter activity [{0}] failed to a generate a newevent due to exception [{1}]


Illegal onEvent(Object output)/onError(Throwable throwable)method call. OnEvent/OnError method must not be called in theinit method or during the initialization phase.


The JAVA ProcessStarter activity [{0}] failed to a generate a newevent due to exception [{1}] since it is in the stopped state.

TIBCO-BW-PALETTE-JAVA-000001

[{0}]

TIBCO-BW-PALETTE-JAVA-501005reference

Internal error occurred. Class=[{0}], Method=[{1}], Cause=[{2}]


Input data error in field [{0}] because [{1}].


Output data error in field [{0}] because [{1}].


Output data error in field [{0}] value cannot be null.


Output data error in field [{0}] value is not serializable.


While executing method [{0}] encountered exception [{1}] [{2}].


Activity input data conversion error. Exception [{0}] occurredwhile trying to render the activity input data. [{1}]


Activity output data conversion error. Exception [{0}] occurredwhile trying to create the activity output data. [{1}]


The Java class [{0}] is not found in the classpath. EncounteredClassNotFoundException [{1}].


Activity input error. The activity received an incorrect value forthe method parameters. IllegalArgumentException occurredwhile trying to construct an instance of the Java class [{0}]: [{1}]


Unable to construct an instance of the Java class [{0}].Encountered exception [{1}] [{2}].


The constructor for the Java class [{0}] raised exception [{1}]. [{2}]


Unable to obtain information for the method [{0}] from the class[{1}]. Encountered NoSuchMethodException [{2}].

70




Unable to obtain information for the method [{0}] from the class[{1}]. Encountered SecurityException [{2}].


Activity input error. The activity received an incorrect value forthe method parameters. When attempting to invoke the method[{0}], encountered IllegalArgumentException [{1}].


Activity input error. The activity received an incorrect Java objectfor the declared Java class [{0}]. The activity required an instanceof the Java class [{1}], but received an instance of the Java class[{2}]: [{3}]


Activity input error. The activity received an incorrect Java objectfor the declared Java class [{0}]. The Java object received is notcompatible with the Java object required by this activity. Theactivity required an instance of the Java class [{1}]: [{2}]


Activity input error. The activity received 'null' value for the forthe declared Java class. The activity required an instance of theclass [{0}], but received a 'null'.


Unable to invoke the method [{0}]. Encountered exception [{1}][{2}].


Unable to invoke the cleanup method [{0}]. Encounteredexception [{1}] [{2}].


The method [{0}] raised exception [{1}]. [{2}].


The cleanup method [{0}] raised exception [{1}]. [{2}].


Activity input error. The activity required instance of class [{0}],but received a 'null' value for the declared Java class.


Activity input error. The activity received incorrect Java object forthe declared Java class. The activity required an instance of a class[{0}], but received instance of a class [{1}].


Data Conversion error. When attempting to convert Java object toXML data encountered exception [{0}].


Data Conversion error. When attempting to convert XML data toJava object encountered exception [{0}].


Runtime error. Illegal onEvent(Object output)/onError(Throwableerror) method call. OnEvent/OnError method must not be calledin the init method or during the initialization phase.

71




Runtime error. The output type defined by thegetOutputObjectType() does not match with the type that ispassed in to onEvent(Object object).


The Java Process Starter onstop method [{0}] raised exception[{1}]. [{2}].


The Java Process Starter onShutdown method [{0}] raisedexception [{1}]. [{2}].

JDBC Palette Error CodesThis section describes the error messages that can be reported by the activities or entities associatedwith the JDBC palette.


TIBCO-BW-PALETTE-JDBC-000001

The JDBC activity [{0}] is NOT part of a JDBC Transaction Group.However the activity references the same shared resource as usedin the group


Batch updates failed on update number [{0}].


Invalid procedure name specified. Procedure name can not benull.


{0} input parameters declared in the SQL statement but no inputparameters provided.


Duplicate field name [{0}] found. Modify the query and createunique aliases for duplicate fields.


Improper SQL statement used. {0}


Exception occurred when attempting to create a JDBC Connectionfor JDBC Transaction.


Missing Input Value for required Column [{0}].


SQL Exception occurred (SQL STATE = {0}) - detailMessage - {1}


{0} is not a valid timezone.


Could not create Connection to server using Shared Resource[{0}].

72




Invalid Activity Configuration. Missing required configurationField [{0}] in activity [{1}]


Invalid Activity Configuration. Invalid SQL Statement [{0}] inactivity [{1}] expected a statement with [{2}]


Invalid Activity Configuration. Number of Prepared Parametersin activity configuration exceed number of '?' in SQL Statement


Invalid Activity Configuration. Number of Prepared Parametersin activity configuration is less than number of '?' in SQLStatement


Batch Update mode works only with Prepared Statements

JMS Palette Error CodesThis section describes the error messages that can be reported by the activities or entities associatedwith the BusinessWorks JMS palette.


TIBCO-BW-PALETTE-JMS-000001

{0}


Invalid configuration data. JMS connection reference is notspecified.


Invalid configuration data. Specified connection reference is notfound in repository. {0}


Invalid configuration data. JMS destination is not specified.


Error occurred when attempting to create Durable Subscriber


Failed to create connection to the JMS server. {0}


Unable to create a session to receive messages [{0}].


Unable to create a reply session/producer [{0}]


Unable to find destination [{0}] on JMS server


Error occurred when attempting to create MessageConsumer

73




Error occurred when attempting to resolve destination [{0}]


Invalid configuration data. JMS Reply To Destination NotSpecified.


Error occurred when attempting to send a JMS message


Error occurred when attempting to receive a JMS message


Error occurred when attempting to confirm a JMS message


Failed to Reply for JMS ProcessStarter[{0}]. This error can occur ifthe JMSReply activity is executed after recovering from a check-pointed BusinessWorks process instance.

Mail Palette Error CodesThis section describes the error messages that can be reported by the activities or entities associatedwith the BusinessWorks Mail palette.


TIBCO-BW-PALETTE-MAIL-000001

[{0}]


Invalid input data. Reason: Error parsing input data.


Invalid input data. Reason: Both the comma and semicoloncannot be used at same time to separate addresses: [{0}]


Error connecting to the mail server. Reason: unknown host -connection parameters: [{0}].


Error building mail message. Cause: [{0}].


From address [{0}] is not valid.


Error sending mail message.


The system cannot find the file specified: [{0}].


Invalid recipient address in To, CC or BCC [{0}, {1}, {2}].

74




Host can not be null


Username can not be null when using Authentication


Password can not be null when using Authentication


Error closing mail server connection. Cause: [{0}].


Mail provider for protocol [{0}] not found. Make sure that theprovider jar is in java classpath.


Configuration error in field [{0}] the value must be a valid HostName.


Error connecting to the mail server - connect exception;connection parameters: [Host:{0}, Port:{1}, User:{2}].


Could not connect to mail server - invalid username in field [{0}]and/or invalid password.


The default mail folder was not found on mail server.


The INBOX mail folder was not found on mail server.


Error getting folder on mail server.


Mail is already deleted, Receive Mail activity has 'Delete Mail'turned on.


Error connecting to the mail server using connection parameters:[{0}]


Error while polling mail server: cannot open INBOX folder.


Error parsing received mail.


Error while polling mail server: cannot close INBOX folder.


Unexpected error while polling mail server.

75




The Receive Mail ProcessStarter activity [{0}] failed to a generate anew event due to exception [{1}] since it is in the stopped state.

Parse Palette Error CodesThis section describes the error messages that can be reported by the activities or entities associatedwith the BusinessWorks Parse palette.


TIBCO-BW-PALETTE-PARSE-000001

{0}


Cannot find data format schema resource [{0}]


Cannot create schema from data format schema.


Exception in parse eval: [{0}]


Line length must be > 0


Hit EOF on row [{0}] field [{1}] spanning columns [{2}] to [{3}] ....last row contents was: [{4}]


Input type is not specified.


Please specify the Input type field.


Data format resource not specified.


Specify the data format resource.


File [{0}] cannot be opened using encoding method [{1}]


[{0}] must be specified if [{1}] is selected.


Format Type must be selected.


Line is too long. Specified Line Delimiter may not match filecontent.

76




There are not enough data for the number of required fields in arow.


Error while parsing headers in the mime message.


An I/O exception occurred while parsing SOAP payload in theroot part.


An Unexpected exception occurred while parsing Message. Rootcause is [{0}]


The SOAP Message doesn't exist in the Root part.


Soap Envelope has invalid XML content.


One or more mime parts have same Content-Id value in the MimeMessage.


The xop:Include element must have an 'href' attribute.


Content_Id header is not found in mime part of the MimeMessage.


Invalid Content Type Field in the Mime Message.


Boundary attribute not found in the Mime Message.


startinfo parameter is missing in the Mime Message.


startinfo parameter is not starting with 'application/soap+xml' inthe Mime Message.


Content Type header is not found in the Mime Message.


Media type of root part is not 'application/xop+xml' in the MimeMessage.


'type' parameter is not present in root part of the Mime Message.


startInfo parameter and type parameter,of root part, does notmatch in the Mime Message.

77


Rendezvous Palette Error CodesThis section describes the error messages that can be reported by the activities or entities associatedwith the BusinessWorks Rendezvous palette.


TIBCO-BW-PALETTE-RV-000001

{0}


Error in sending message


Error serializing the message


Error in processing event: [{0}]


Cannot create TibrvQueue: [{0}]


Cannot create reply listener for subject: [{0}]


Cannot activate TIBRV listener for subject: [{0}] : Exception: [{1}]


Error in sending reply


Error Occurred while receiving a RV Message so the RVEventSource activity [{0}] failed to a generate a new event due toexception [{1}]


Advisory listening queue caught exception: [{0}]


The RV Subscriber ProcessStarter activity [{0}] failed to a generatea new event due to exception [{1}] since it is in the stopped state.


The WaitforRVMessage Signal In activity [{0}] failed to a generatea new event due to exception [{1}] since it is in the stopped state.


Failed to Reply for [{0}]. This error can occur if the RV reply torequest activity is executed after recovering from a check-pointedBusinessWorks process instance.

78


TCP Palette Error CodesThis section describes the error messages that can be reported by the activities or entities associatedwith the BusinessWorks TCP palette.


TIBCO-BW-PALETTE-TCP-500001

Cannot start TCP Receiver on Host [{0}], Port [{1}]. Reason: [{2}].


Invalid Port; port must be numeric. Error: [{0}]


No value specified for the 'data' input field.


Error reading TCP data. Reason: [{0}].


Error opening TCP Connection. Reason: [{0}].


Error opening TCP Connection. Reason: Host [{0}] unknown.


Exception closing TCP Connection. Reason: [{0}].


Could not read from TCP connection. The input connection iseither invalid or closed.


Could not write to TCP connection. The input connection is eitherinvalid or closed.


Can not start TCP Receiver on Host=[{0}], Port=[{1}]. Another TCPReceiver is already running with the same configuration.


Error closing TCP connection. Reason: No connection is availablewhich matches the input connection key.


Error writing data. Reason: [{0}].


Timeout while reading TCP data


IOException occurred while retrieving XML Output for activity[{0}].


The TCPReceiver Process Starter activity [{0}] failed to a generatea new event due to exception [{1}] since it is in the stopped state.


The Wait For TCP Request activity [{0}] failed to a generate a newevent due to exception [{1}] since it is in the stopped state.

79


XML Palette Error CodesThis section describes the error messages that can be reported by the activities or entities associatedwith the BusinessWorks XML palette.


TIBCO-BW-PALETTE-XML-000001

[{0}]


Internal error occurred Class=[{0}], Method=[{1}], Reason=[{2}].


Unable to serialize the XML due to exception [{0}].


Unable to parse the XML due to exception [{0}].


Exception [{0}] occurred during XSLT transformation. Exceptiondetail [{1}].


The XSLT transformation Stylesheet provided for the activityinput is empty or null.


The selected encoding [{0}] is not valid.


Encountered encoding error [{0}].


The encoded bytes content is empty.


Encountered error [{0}] while trying to detect the encoding fromthe XML.

80


Shared Resources

This section describes the error codes that can be reported by various shared resources.

Shared Resource Framework Error CodesThe Shared Resource Framework is responsible for the creating and managing the shared resourcesrequired by the product applications. This section describes the error messages that can be reported bythe Shared Resource Framework.


TIBCO-BW-SR-FRWK-000010 Shared Resource Creation Error. TheResourceDependencyHandler object returned by [{0}#create()] isnull.

TIBCO-BW-SR-FRWK-500001 {0}

TIBCO-BW-SR-FRWK-502000 Failed to {0} SharedResource [{1}] for Module [{2}:{3}],DeploymentUnit [{4}:{5}]{6}

TIBCO-BW-SR-FRWK-503000 Unable to start SharedResource [{0}] {1}. <Reason>: {2}

TIBCO-BW-SR-COMMON-001101

Unable to get IdentitySubject from Trinity for {0}.


Object is not of type IdentitySubject for {0}.


Unable to get IdentityTrust from Trinity for {0}.


Object is not of type IdentityTrust for {0}.


Unsupported PrivateKey.


Key not found.


Problem extracting Key.

TIBCO-BW-SR-THREADPOOL-502000

Failed to {0} Thread Pool resource [{1}]


Failure during execution of pending task {0} in work queue onThreadPool shutdown.


Could not submit task {0} for execution.

81




No matching time unit found for {0}, possible values are{NANOSECONDS, MICROSECONDS, MILLISECONDS,SECONDS, MINUTES, HOURS, DAYS}.


No matching rejection policy found for {0}, possible values are{BLOCKING, CALLER_RUNS, ABORT}.


Keep Alive Time should be greater then or equal to zero.


Maximum Pool Size should be greater then zero and less then orequal Core pool size.


Core Pool Size should be greater then or equal to zero.


Minimum Pool Size should be greater then or equal to zero.

Data Format Error CodesThis section describes the error messages that can be reported by the Data Format shared resource.


TIBCO-BW-SR-DATAFORMAT-500000

Failed to {0} Data Format resource [{1}]

FTP Connection Error CodesThis section describes the error messages that can be reported by the FTP Connection shared resource.


TIBCO-BW-SR-FTP-500004 Failed to {0} FTP Connection resource [{1}]

HTTP Client Error CodesThis section describes the error messages that can be reported by the HTTP Client shared resource.


TIBCO-BW-SR-HTTP-CLIENT-500000

Failed to {0} HTTP Client resource [{1}]


User name or Password is not specified in Identity


User name or Password is not set in identity resource for basicHttp authentication

82


HTTP Connector Error CodesThis section describes the error messages that can be reported by the HTTP Connector shared resource.


TIBCO-BW-SR-HTTP-CONNECTOR-500000

Failed to {0} HTTP Connector resource [{1}]


Failed to create HTTP Connector resource [{0}] with the specifiedconfiguration. Check the configuration settings.


Unable to start HTTP Server instance for resource [{0}]


Failed to activate HTTP endpoint [{0}] because of exception [{1}]


The HTTP server instance cannot be started, because it is notconfigured


The HTTP server instance [{0}] occurred an error when stopped


Failed to deactivate HTTP endpoint [{0}]


Failed to get URL for HTTP endpoint [{0}]


Unable to find Application bundle [{0}]


Failed to create HTTP Connector resource [{0}] configured withport [{1}]

Java Global Instance Error CodesThis section describes the error messages that can be reported by the Java Global Instance sharedresource.


TIBCO-BW-SR-JAVA-500001 A connector configuration with the name "[{0}" already existswith pid [{1}]

TIBCO-BW-SR-JAVA-500002 Unable to find Application bundle [{0}]

TIBCO-BW-SR-JAVA-500003 Unable to construct an instance of the Java class [{0}].Encountered exception [{1}] [{2}].

83



TIBCO-BW-SR-JAVA-500004 Activity input error. The activity received an incorrect value forthe method parameters. IllegalArgumentException occurredwhile trying to construct an instance of the Java class [{0}]: [{1}]

TIBCO-BW-SR-JAVA-500005 The constructor for the Java class [{0}] raised exception [{1}]. [{2}]

TIBCO-BW-SR-JAVA-500006 The Java class [{0}] is not found in the classpath. EncounteredClassNotFoundException [{1}].

TIBCO-BW-SR-JAVA-500007 Unable to obtain information for the method [{0}] from the class[{1}]. Encountered NoSuchMethodException [{2}].

TIBCO-BW-SR-JAVA-500008 Unable to obtain information for the cleanup method [{0}] fromthe class [{1}]. NoSuchMethodException occurred. [{2}]

TIBCO-BW-SR-JAVA-500009 The cleanup method [{0}] raised exception [{1}]. [{2}]

TIBCO-BW-SR-JAVA-500010 Unable to invoke the cleanup method [{0}]. Exception [{1}]occurred. [{2}]

TIBCO-BW-SR-JAVA-500012 Unable to invoke the cleanup method [{0}]. Encounteredexception [{1}] [{2}].

TIBCO-BW-SR-JAVA-500014 Received an incorrect value for the method [{0}] parameter to getaccess the BW Module properties. Exception occurred: [{1}]

TIBCO-BW-SR-JAVA-000001 Delete Called on configuration that does not exist with pid [{0}]

JMS Connection Error CodesThis section describes the error messages that can be reported by the JMS Connection shared resource.


TIBCO-BW-SR-JMS-502000 Failed to {0} JMS Connection resource [{1}]

JDBC Connection Error CodesThis section describes the error messages that can be reported by the JDBC Connection shared resource.


TIBCO-BW-SR-JDBC-502000 Failed to {0} JDBC Connection resource [{1}].

TIBCO-BW-SR-JDBC-500001 Exception occurred while trying to retrieve a connection from theJDBC Connection pool

TIBCO-BW-SR-JDBC-500002 Failed to create a new connection to database server. DatabaseURL [{0}], UserName [{1}], SQLSTATE [{2}]

84



TIBCO-BW-SR-JDBC-500003 The database driver [{0}] is not found. Ensure thatDataSourceFactory bundle providing this driver is available inthe environment.

TIBCO-BW-SR-JDBC-000001 Delete Called on configuration that does not exist with pid [{0}]

JNDI Configuration Error CodesThis section describes the error messages that can be reported by the JNDI Configuration sharedresource.


TIBCO-BW-SR-JNDI-502000 Failed to {0} JNDI Configuration resource [{1}]

Proxy Configuration Error CodesThis section describes the error messages that can be reported by the Proxy Configuration sharedresource.


TIBCO-BW-SR-HTTP-PROXY-500000

Failed to {0} Proxy Configuration resource [{1}]

Rendezvous Transport Error CodesThis section describes the error messages that can be reported by the Rendezvous transport sharedresource.


TIBCO-BW-SR-RV-000001 {0}

TIBCO-BW-SR-RV-500000 Failed to create RV Transport due to exception [{0}]

TIBCO-BW-SR-RV-500006 Failed to {0} RV Transport resource [{1}]

SMTP Resource Error CodesThis section describes the error messages that can be reported by the SMTP shared resource.


TIBCO-BW-SR-MAIL-500001 Problem extracting mail SSL information from Trinity for JNDI[{0}].

TIBCO-BW-SR-MAIL-500002 Mail Session creation failed.

TIBCO-BW-SR-MAIL-500005 Handler for MimeType [{0}] not found.

85



TIBCO-BW-SR-MAIL-500006 Failed to start SMTP Connection Shared Resource [{0}].

TCP ConnectionThis section describes the error messages that can be reported by the TCP Connection shared resource.


TIBCO-BW-SR-TCP-500004 Failed to {0} TCP Connection resource [{1}]

86


tibco activematrix businessworks error codes codes naming convention product execution errors,...

Documents