TIBCO BusinessWorks Container Edition Error Codes · PDF fileAll other product and company...

TIBCO BusinessWorks™ Container Edition ErrorCodesSoftware Release 2.0May 2016

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 (ORPROVIDE 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, TIBCO BusinessWorks Container Edition, TIBCO BusinessWorks Studio ContainerEdition and Two-Second Advantage are either registered trademarks or trademarks of TIBCO SoftwareInc. 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, EITHER EXPRESSOR 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-2016 TIBCO Software Inc. All rights reserved.

TIBCO Software Inc. Confidential Information

2

TIBCO BusinessWorks™ Container Edition Error Codes

Contents

TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Message Codes Naming Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

SOAP Binding Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

REST Binding Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Engine Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Palettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

General Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

File Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

HTTP Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Java Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

JDBC Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

JMS Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Parse Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

XML Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Shared Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Shared Resource Framework Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Data Format Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

HTTP Client Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

HTTP Connector Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Java Global Instance Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

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

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

JNDI Configuration Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Proxy Configuration Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

3


TIBCO Documentation

Documentation for this and other TIBCO products is available on the TIBCO Documentation site. Thissite is updated more frequently than any documentation that might be included with the product. Toensure that you are accessing the latest available help topics, please visit:

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.

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

● Concepts

● Installation

● Getting Started

● Application Development

● Palettes Reference

● Samples

● Error Codes

● Conversion

How to Contact TIBCO Support

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

● 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 the following web address:

https://www.tibcommunity.com

4


https://docs.tibco.com

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

https://support.tibco.com

https://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 BusinessWorks Container Edition Engine Layer

PVM BusinessWorks Container Edition Engine Layer

TIBCO-BW-BINDING-REST BusinessWorks Container Edition REST Binding

TIBCO-BW-BINDING-SOAP BusinessWorks Container Edition SOAP Binding

TIBCO-BW-CORE BusinessWorks Container Edition Engine Layer

TIBCO-BW-FRWK BusinessWorks Container Edition Framework

TIBCO-BW-PALETTE BusinessWorks Container Edition Palette layer

TIBCO-BW-PALETTE-<Palette Name> BusinessWorks Container Edition Palette specificactivity

TIBCO-BW-SR BusinessWorks Container Edition SharedResource API layer

TIBCO-BW-SR-<UniqueName> BusinessWorks Container Edition specificShared Resource

TIBCO-BW-STATS BusinessWorks Container Edition 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.

Log Level Error Code

TRACE 100001 - 109999

DEBUG 200001 - 209999

5


Log Level Error Code

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.

6


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 Error Resolution

TIBCO-BW-BINDING-SOAP-001010

SOAP BindingFactory is initializedwith incorrect BindingConfigurationfor the SOAP Service Binding.

This is a internal resolution message.Resolution not required.


Failed to obtain HTTP Connectorresource for SoapServiceBinding [{0}],Application [{1}:{2}]

This is an internal product error.Contact TIBCO support.


Failed to obtain HTTP Connectorresource for SoapServiceBinding [{0}],Application [{1}:{2}]



SOAP BindingFactory is initializedwith incorrect BindingConfigurationfor the SOAP Reference Binding.



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

Ensure that the xml file contents arevalid and well formed.


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

Ensure that the 'name' attribute of theservice element contains a uniqueBinding Name.


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

Ensure that Binding Name of theSOAP Interceptor is unique and itdoes not match with any BindingName (service/reference) in theApplication Module


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

Ensure that the SOAP Interceptordeployed follows the Axis2 Moduleprotocol.


Failed to initialize SOAP Binding.Binding Name is not specified.

BW_SOAP_BINDING_NAME_MISSING_ERROR.resolution = Make sureall Bindings in the application Modulehave a Name.


Failed to initialize SOAP Binding.Binding Name is not specified for port[{0}].

Make sure the Binding in theapplication Module has a Name.

7




Failed to initialize SOAP Binding.Application Name is not available.



Failed to initialize SOAP Binding.Application Version is not available.



Failed to locate WSDL definition forport type [{0}].

Ensure that the a WSDL exist withport type [{0}] in the applicationmodule.


MEP [{0}] is not supported. Reviewthe WSDL definition for Port type[{1}].

Ensure that the MEP definition forPort type [{1}] is either IN-OUT ORIN-ONLY


Failed to recognize the MEP for Porttype [{0}].



Failed to find message receiver forMEP [{0}] for port type [{1}].



SOAP Binding [{1}] for portType [{0}]is missing Transport Configuration.

Ensure that the SOAP Binding [{1}] forport type [{0}] is configured with aTransport.


Operation Configuration forOperation [{0}], Port Type [{1}], SOAPBinding [{2}] is missing. Ensure thatSOAP Binding [{2}] is in sync withWSDL

Ensure that SOAP Binding [{2}] is insync with WSDL.


Failed to initialize SOAP ServiceBinding [{0}]. Promoted Name for theBinding is missing.



Failed to initialize SOAP ReferenceBinding [{0}]. Promoted Name for theBinding is missing.



Failed to load WSDL definition fornamespace [{0}].

Make sure the WSDL with namespace[{0}] exists in the application module.


Malformed MIME Message received.Failed to parse the attachments in thereceived message for Operation [{0}],SoapBinding [{1}], Application [{2}:{3}]. Ignoring the attachments fromthe SOAP Message.

Ensure that the MIME Message is wellformed with correct mimeboundaries.

8




Failed to create SoapServiceBinding[{0}], Application [{1}:{2}] due toexception [{3}]



Unable to parse model version of theSOAP Binding.

Ensure the SOAP Model versionin .bwm file is of format [0-9].[0-9].[0-9]


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

Ensure that the configuration andcontext mapping. if any, done onSoapServiceBinding [{0}] are correct.


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

Ensure that the SoapServiceBinding[{0}] is configured with a SharedTransport Resource.


Failed to initialize SoapServiceBinding[{0}]. A Service Endpoint URI [{1}] isalready registered

Ensure that each SOAP/HTTP servicehas unique URL.


Failed to initialize SoapServiceBinding[{0}]. The operation [{1}] withsoapaction [{2}] is already registeredfor destination [{3}] with MessageStyle [{4}].

Ensure that the combination of "SoapAction" and"MessageStyle:Destination" should beunique.


Failed to send SOAP Fault message tothe consumer of the service forOperation [{0}], SoapServiceBinding[{1}], Application [{2}:{3}] due toexception [{4}]. Root Exceptionmessage: {5}



Failed to process Reply message forOperation [{0}], SoapServiceBinding[{1}], Application [{2}:{3}] due toexception [{4}]. Sending UndeclaredFault message to the consumer of thisservice. Root Exception message: [{5}]

Ensure that the Binding configurationand Context Configuration, if any,done on SoapServiceBinding [{1}] arecorrect.


Error occurred while processingService Request messages ContextInformation for Operation [{0}],SoapServiceBinding [{1}], Application[{2}:{3}] due to exception [{4}]. RootException message: {5}

Ensure that the Context Mappingdone on SoapServiceBinding [{1}] arecorrect.


Error occurred while processingService Request message forOperation [{0}], SoapServiceBinding[{1}], Application [{2}]:{3}] due toexception [{4}]. Root Exceptionmessage: {5}

Ensure that the Message partconfiguration and headerconfiguration, if any, done onSoapServiceBinding [{1}] are correct.

9




Error occurred while processingService Request message forOperation [{0}], SoapServiceBinding[{1}], Application [{2}:{3}] due toexception [{4}]. Sending UndeclaredFault message to the consumer of thisservice. Root Exception message: {5}



Error occurred while processingService Request message forOperation [{0}], SoapServiceBinding[{1}], Application [{2}:{3}] due toexception [{4}].Root Exceptionmessage: {5}



Failed to process Declared FaultMessage for Operation [{0}],SoapServiceBinding [{1}], Application[{2}:{3}] due to exception [{4}]. SendingUndeclared Fault message to theconsumer of this service. RootException message: {5}.

Ensure that the Context Mapping andconfiguration done onSoapServiceBinding [{1}] are correct.


The BusinessWorks ProcessServiceimplementation failed to complete therequest for the Operation [{0}],SoapServiceBinding [{1}], Application[{2}:{3}] and returned exception [{4}].Sending Undeclared Fault message tothe consumer of this service. RootException message: {5}.

Ensure that the BW Process constructis correct.


Unable to populate SOAP BindingConfiguration due to exception [{1}]



An Error occurred while cleaning upthe SOAP Binding ConfigurationResources due to exception [{1}]



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



Failed to start SoapServiceBinding[{0}], Application [{1}:{2}] due toexception [{3}]

Ensure that the TransportConfiguration done onSoapServiceBinding [{0}] are correct.

10




Failed to stop SoapServiceBinding[{0}], Application [{1}:{2}] due toexception [{3}]



Error occurred while processingService Request messages Contextinformation for Operation [{0}],SoapServiceBinding [{1}], Application[{2}:{3}] due to exception [{4}]. SendingUndeclared Fault message to theconsumer of this service. RootException message: {5}

Ensure that the Context Mapping andconfiguration done onSoapServiceBinding [{1}] are correct.


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



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



Failed to Initialize JMS transportprimitive for SoapServiceBinding [{0}],Application [{1}:{2}] due to exception[{3}]

Ensure that the transportconfiguration done onSoapServiceBinding [{0}] are correct.


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



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

Ensure that the transportconfiguration done onSoapServiceBinding [{0}] are correct.


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

Ensure that the Service Provider issending a correct SOAP Envelope.


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



Failed to acknowledge ServiceRequest message for Operation [{0}],SoapServiceBinding [{1}], Application[{2}:{3}] due to exception [{4}]


11




Failed to authenticate Requestmessage for Operation [{0}],SoapServiceBinding [{1}], Application[{2}:{3}] due to exception [{4}].

Check if the identity resourcereferenced in Http Client resourcecontains username and password.


Failed to authenticate Requestmessage for Operation [{0}],SoapServiceBinding [{1}], Application[{2}:{3}]. Username and Password isnot set.



Failed to authenticate Requestmessage for Operation [{0}],SoapServiceBinding [{1}], Application[{2}:{3}] due to exception [{4}].



Malformed SOAP Request messagereceived for Operation [{0}],SoapServiceBinding [{1}], Application[{2}:{3}]. Root Exception message: [{5}]

Check if the SOAP Request Message iswell formed.


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



Failed to createSoapReferenceEndpoint [{0}] due toexception [{1}]

Ensure that configurations done onReference Binding [{0}] are correct.


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

Ensure that the Binding and Transportconfiguration onSoapReferenceBinding [{0}] arecorrect.


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



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



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


12




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



Unable to receive response from theservice provider for Operation [{0}],SoapReferenceBinding [{1}],Application [{2}:{3}] due to exception[{4}]



Received SOAP Fault from the serviceprovider of the Operation [{0}],SoapReferenceBinding [{1}],Application [{2}:{3}]. SOAP Faultreceived: [{4}]

This is an internal message sent to theframework. Resolution not required.


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

Ensure that the declared fault sendback by the Service Provider is validand well formed SOAP Fault.


Error occurred while processing replymessage from the service provider ofthe Operation [{0}],SoapReferenceBinding [{1}],Application [{2}:{3}] due to exception[{4}]

Ensure that Message Part and HeaderConfiguration done onSoapReferenceBinding [{1}] arecorrect.


SOAPEnvelope must contain a bodyelement which is either first or secondchild element of the SOAPEnvelope.

Ensure that Service Provider has senda valid SOAP Envelope.


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

Ensure that Context configuration andMapping for the attachment done onSoapReferenceBinding [{1}] is correct.


Failed to Initialize JMS transportprimitive for SoapReferenceBinding[{0}], Application [{1}:{2}] due toexception [{3}]

Ensure that the Transport Senderconfigurations are correct.

13




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

Ensure that the MessageConfiguration done onSoapReferenceBinding [{1}] arecorrect.


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

Ensure that the MessageConfiguration done onSoapReferenceBinding [{1}] are correct


Failed to update HTTP Transportconfigurations before sending theReference Request message forOperation [{0}],SoapReferenceBinding [{1}],Application [{2}:{3}] due to exception[{4}].

Ensure that the port numberconfiguration forSoapReferenceBinding [{1}] is valid


Failed to create the HTTP Clientrequired for sending the ReferenceRequest message for Operation [{0}],SoapReferenceBinding [{1}],Application [{2}:{3}] due to exception[{4}]

Ensure that the Endpoint URL is incorrect format.


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

Ensure that the configuration done onReference Binding are correct.


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

Ensure that the configuration done onReference Binding are correct.


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

Ensure that the Endpoint URIconfiguration onSOAPRefernceBinding [{1}] is correct.


Unable to receive response from theservice provider for Operation [{0}],SoapReferenceBinding [{1}],Application [{2}:{3}] due to exception[{4}]. Message Received: [{5}]

Ensure that the Service Provider isavailable.



Ensure that HTTP Clientconfigurations are configured as perservice provider requirements.

14







Unable to send request the serviceprovider for Operation [{0}],SoapReferenceBinding [{1}],Application [{2}:{3}] due to exception[{4}]. Message Received: [{5}]



Unable to send request the serviceprovider for Operation [{0}],SoapReferenceBinding [{1}],Application [{2}:{3}] due to exception[{4}]. Message Received: [{5}]

Ensure that the COOKIE format iscorrect.

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


TIBCO-BW-BINDING-REST-200001

Creating REST Resource with HTTPConnector Name [{0}] at ResourcePath: [{1}]

This is a debug message andresolution is not applicable.


Creating REST Resource forconflicting path spec



Adding REST operation [{0}] withHTTP Method[{1}] for [{2}] at resourcepath [{3}]



Request Received for Operation [{0}] This is a debug message andresolution is not applicable.


Invoking BW Endpoint [{0}] forOperation [{1}]



BW Endpoint [{0}] for Operation [{1}]has been invoked. Waiting for Replyto be generated



Response generated. Responding torequest


15




Payload for Request is [{0}] This is a debug message andresolution is not applicable.


Creating XML Message for JSONMessage. Element details -targetnamespace [{0}] and name is[{1}]



Destroying REST Binding withpathspec [{0}] and binding name [{1}]



JSON-> XML Conversion Result: \n{0}



REST Binding Authentication isenabled. Trying to authenticate usingthe Authorization Header of therequest


Expected JSON Content-Type. GotXML Instead. Replying with error toclient

The Client needs to be notified to usethe right Content-Type Header or thebinding configuration can be changedto allow multiple content-types


Expected XML Content-Type. GotJSON Instead. Replying with error toclient

The Client needs to be notified to usethe right Content-Type Header or thebinding configuration can be changedto allow multiple content-types


Binding Configuration is not for aREST Service Binding

Check configuration of the RESTbinding


NO_RESOURCE_URL_SPECIFIED =No relative resource url specified todeploy REST Resource

Check configuration of the RESTbinding for the value of the ResourceURL field.


Unable to create REST resource forbinding [{0}]. Reason - Unable to stopconflicting binding [{1}].

Check both binding configurationsspecified in the error message for theResource URL fields


Error Occurred while trying to createJersey REST Resource for binding [{1}]

Check configuration of the RESTbinding specified in the error message


Unable to start REST Binding withname [{0}]


16




Unable to stop REST Binding withname [{0}}



Error Occurred while parsing andcreating HTTP Headers. Respondingto client with error message.

Invalid values were sent by the clientin the HTTP headers.


Error Occurred while creatingParameters Part. Responding to clientwith error message.

Invalid values were passed for theParameters element. Check the clientrequest and the configuration of theREST Binding.


Error Occurred while creating UserPart. Responding to client with errormessage.

Invalid values were passed for theParameters element. Check the clientrequest and the configuration of theREST Binding.


The HTTP Connector failed to deploythe REST Service Binding. Check theexception thrown by the HTTPConnector for possible configurationissues

Check the HTTP Connector exceptionfor possible reasons of failure. Forexample, Some of them could berelated to overlapping context pathsor an address in use.


The HTTP Connector [{0}] sharedresource could not be retrieved. Pleasecheck the REST Binding configurationor the logs if the HTTP Connectorcould not be started.


The HTTP Connector [{0}] sharedresource could not be retrieved. Pleasecheck the REST Binding configurationor the logs if the HTTP Connectorcould not be started.


AUTHENTICATION_FAILED =Authentication failed for clientrequest. A 401 status code has beensent to the client with the realm as[{0}].


WSDL_CACHE_NOT_FOUND = Anerror occurred while trying to retrievethe WSDL/XSD's for the REST binding[{0}]. Please check the underlyingexception thrown by the WSDL/XSDCache for the root cause.


No WSDL Operation found. Please re-validate the application module andtry deploying again.

This is an internal product error.Contact TIBCO Support.

17


Core

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

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


TIBCO-BW-CORE-000001

{0} This is an internal product error.Contact TIBCO Support.


BWActivityManager RegistrationError. The BWActivityManagerargument provided to the BW Engineis null.



Failed to initialize BW Engine. TheBW Engine was initialized without alogger object.



Failed to initialize BW Engine. Whileregistering BWActivtyBridge the BWEngine encountered exception [{0}]



Failed to initialize BW Engine. TheBWActivityManager was notregistered correctly with the BWEngine.



Failed to initialize BW Engine. TheBW Crypto service was not registeredcorrectly with the BW Engine.



Failed to initialize BW Engine. TheBW Custom XPath Function Managerservice was not registered correctlywith the BW Engine.



Failed to enable BW Debugger. TheBW Engine has not been initialized.



The BW Debugger is already enabledstate and it can not be enabled again.



Unable to disable BW Debugger. TheBW Engine has not been initialized.



Attempt to disable the BW Debuggerencountered exception [{0}]


18




Unable to enable BW Event Publisher.The BW Engine has not beeninitialized.



BW Engine configuration data doesnot contain AppNode name.



BW Engine configuration data doesnot contain AppSpace name.



BW Engine configuration data doesnot contain Domain name.



The operation [{0}] is not supportedfor the BX Non-Executable Module.ModuleName={0}, ModuleVersion={1}



The operation [{0}] is not supportedfor the BX Executable Module.ModuleName={1}, ModuleVersion={2}



The operation [{0}] is not supportedfor the BW Job Shared Variable.



Unable to obtain EngineManagement.The BW Engine has not beeninitialized.



Unable to obtain EngineManagementdue to exception [{0}]



The BX operation [{0}] failed due toexception [{1}].



Invalid 'BWModuleHandle'. The BWmodule represented by this handlehas been already un-installed or thehandle has been already destroyed.



Unable to obtain process templatesreferenced by BW Module, the BWEngine encountered exception.ModuleName[{0}],ModuleVersion[{1}], Exception[{2}].



Unable to obtain GenXDMSchemaComponentCache for the BWModule [{0}]. The operation [{1}]returned "null".


19




Unable to obtain GenXDMSchemaComponentCache for the BWModule [{0}]. The operation [{1}]returned exception [{2}]



Unable to obtain GenXDMSchemaComponentCache for the BWModule [{0}:{1}] due to exception [{2}]



Unable to obtain "BundleContext" forBW module [{0}:{1}]. The operation[{2}] returned "null"



Unable to obtain "BundleContext" forBW module [{0}:{1}] due to exception[{2}]



Unable to obtain ServiceReference forthe cache service [{0}]. The operation"BundleContext.getServiceReference"for BW module [{1}:{2}] returned"null".



Unable to obtain ServiceReference forthe cache service [{0}]. The operation"BundleContext.getServiceReference"for BW module [{1}:{2}] returnedexception [{3}]



Unable to obtain XSD cache service[{0}] for the BW module [{1}:{2}]. Theoperation [{3}] returned "null".



Unable to obtain XSD cache service[{0}] for the BW module [{1}:{2}]. Theoperation [{3}] returned exception [{4}]



Unable to obtain WSDL cache service[{0}] for the BW module [{1}:{2}]. Theoperation [{3}] returned "null".



Unable to obtain WSDL cache service[{0}] for the BW module [{1}:{2}]. Theoperation [{3}] returned exception [{4}]



Unable to obtain WSDL ModuleCachefrom the WSDLCacheService for theWSDL namespace [{0}], locationURI[{1}] that is associated with the BWModule [{2}:{3}], DeploymentUnit [{4}:{5}]. The operation [{6}] returned"null".


20




Unable to obtain WSDL ModuleCachefrom the WSDLCacheService for theWSDL namespace [{0}], locationURI[{1}] that is associated with the BWModule [{2}:{3}], DeploymentUnit [{4}:{5}]. Encountered exception [{6}]



Unable to obtain BxWSDLResolver forthe WSDL namespace [{0}], Location[{1}] that is associated with the BWModule [{2}:{3}], DeploymentUnit [{4}:{5}] due to exception [{6}]



Unable to obtain GenXDM WSDLModule for the WSDL namespace[ {0} ] that is associated with the BWModule [{1}:{2}], DeploymentUnit [{3}:{4}]. The operation "{5}" returnedexception [{6}]



Unable to obtain GenXDM WSDLModule for the WSDL namespace[ {0} ] that is associated with the BWModule [{1}:{2}], DeploymentUnit [{3}:{4}]. The operation "{5}" returned"null". Ensure the BW Module [{6}] isdependent on a BW shared modulewhich contains the WSDL file for thisWSDL namespace or the BW Module[{7}] itself contains the required WSDLfile.



Unable to obtain WSDL Messagedetails from the GenXDM WSDLModule for the WSDL namespace[ {0} ] that is referenced in the BWModule [{1}:{2}] due to exception [{3}].



Unable to obtain WSDL Definitionnamespace details from the GenXDMWSDL Module for the WSDLnamespace [ {0} ] that is associatedwith the BW Module [{1}:{2}] due toexception [{3}].



Unable to obtain WSDL Targetnamespace from the GenXDM WSDLModule for the WSDL namespace[ {0} ] that is associated with the BWModule [{1}:{2}] due to exception [{3}].


21




Unable to obtain WSDL Interfacedetails from the GenXDM WSDLModule for the PortType [{0}], that isassociated with the BW Module [{1}:{2}]. The operation "{3}" returnedexception [{4}].



Unable to obtain WSDL Interfacedetails from the GenXDM WSDLModule for the PortType [{0}], that isassociated with the BW Module [{1}:{2}]. The operation "{3}" returned null.



Unable to construct PortType detailsfrom the GenXDM WSDL Interface forthe WSDL namespace [ {0} ] that isassociated with the BW Module [{1}:{2}] due to exception [{3}].



Invalid BWBxWSDLResolver. Theinstance of this BWBxWSDLResolverhas been already released.



The initial value mode [{0}] specifiedfor the {1} [{2}] in BW Module [{3}:{4}],DeploymentUnit[{5}:{6}] is invalid.



The QName value [{0}] specified forthe {1} [{2}] in BW Module [{3}] isinvalid or malformed.



Invalid 'BWComponentHandle'. TheBW Component represented by thishandle has been already un-installedor the handle has been alreadydestroyed.



Unable to createServiceEndpointRequestHandler forBW Component due to invalid BWProcess ServiceType [{0}].ComponentName={1},ComponentVersion={2}



Unable to createServiceEndpointRequestHandler forBW Component due to invalid BWProcess ServiceName [{0}].ComponentName={1},ComponentVersion={2}


22




Error occurred while creatingServiceEndpointRequestHandler forservice [{0}], BW Component [{1}],Application [{2}:{3}]. Exception[{4}].



Unable to createServiceEndpointRequestHandler forservice [{0}], BW Component [{1}]. Theoperation"BxSystem.getInterfaceProvider"returned "null".



Received unexpected exception [{0}]from the service binding associatedwith the component service [{1}],Application [{2}] on invocation ofmethod [{3}].



Unable to obtain "BundleContext".The operation "{0}" returned "null"



Unable to obtain "BundleContext" dueto exception [{0}]



Unable to obtain GenXDM WSDLModule for the WSDL namespace [{0}]that is associated with the BWComponent [{1}], Application[{2}:{3}].The operation "{4}" returned exception[{5}]



Unable to obtain GenXDM WSDLModule for the WSDL namespace [{0}]that is associated with the BWComponent [{1}], Application[{2}:{3}].The operation "{4}" returned "null".



Unable to obtain WSDL Interfacedetails from the GenXDM WSDLModule for the PortType [{0}], that isassociated with the BW Component[{1}], Application[{2}:{3}]. Theoperation "{4}" returned exception[{5}].


Unable to obtain WSDL Interfacedetails from the GenXDM WSDLModule for the PortType [{0}], that isassociated with the BW Component[{1}], Application[{2}:{3}]. Theoperation "{4}" returned null.


23




Unable to obtain ServiceReference forthe cache service [{0}]. The operation"{1}" returned "null".


Unable to obtain ServiceReference forthe cache service [{0}] due to exception[{1}]



Unable to obtain cache service [{0}].The operation "{1}" returned "null".



Unable to obtain cache service [{0}].The operation "{1}" returned exception[{2}].



Unable to construct PortType detailsfrom the GenXDM WSDL Interface forthe WSDL namespace [{0}] that isassociated with the BW Component[{1}] due to exception [{2}].



Unable to obtain ModuleCache for theBW Component [{0}]. The operation"{1}" returned "null".



Failed obtain value for the componentlevel property [{0}], BW Component[{1}], Application [{2}:{3}].Encountered exception [{4}]

BW framework layer encounterederrors when accessing the componentlevel property. Contact TIBCOSupport.


Invalid 'BWApplicationHandle'. TheBW Application represented by thishandle has been already un-installedor the handle has been alreadydestroyed.



Unable to create'BWApplicationHandle' due to invalidBWComponentHandle list. Theargument of type'List<BWComponentHandle>;' mustcontain at least oneBWComponentHandle.


24




Unable to create'BWApplicationHandle' due toinconsistent application names in theBWComponentHandle(s) contained inthe argument of type'List<BWComponentHandle>;'. Thehandle for the BW Component [{0}]has application name as [{1}] where asthe first handle in the list hasapplication name as [{2}].



Unable to create'BWApplicationHandle' for the BWApplication [{0}].



Error occurred when accessing theProcessStarter activity [{0}] in process[{1}], module [{2}] from theBWActivityManager. Error={3}.



Error occurred when configuring theProcessStarter activity [{0}] in process[{1}], module [{2}].



Unable to configure ProcessStarteractivity [{0}] in process [{1}], module[{2}] due to crypto service access error.



HotUpdate operation not supportedfor ProcessStarter activity [{0}] inprocess [{1}], module [{2}]. TheProcessStarter already exists foractivitId [{3}].

This error can occur if the BW processfile has been corrupted.


Failed to obtain activity [{0}] inprocess [{1}], module [{2}] from theBWActivityManager due to exception[{3}]. ActivityId [{4}].



Error occurred when configuring theactivity [{0}] in process [{1}], module[{2}]



Unable to configure activity [{0}] inprocess [{1}], module [{2}] due tocrypto service access error.



Unable to execute [{0}] operation foran activity. Failed to lookup activity[{1}] in process [{2}], module [{3}] fromthe BWActivityManager. ActivityId[{4}].


25




HotUpdate operation not supportedfor activity [{0}] in process [{1}],module [{2}]. The activity alreadyexists for activitId [{3}].



{0} This is a trace message and resolutionis not applicable.


Activated Application[{0}],Component[{1}] in AppNode[{2}],ActivationAlias[{3}].

This is a trace message and resolutionis not applicable.


Activated Application[{0}],Module[{1}] in AppNode[{2}],ActivationAlias[{3}].

This is a trace message and resolutionis not applicable.


{0} This is a debug message andresolution is not applicable.




Initialized BW Engine successfully[{0}, {1}, {2}].

This is a debug message and itindicates the BW Engine wasinitialized successfully. Resolution isnot applicable for this message.


Stopped(Graceful) BW Enginesuccessfully.

This is a debug message and itindicates the BW Engine was stoppedgracefully. Resolution is notapplicable for this message.


Stopped(Forceful) BW Enginesuccessfully.

This is a debug message and itindicates the BW Engine was stoppedforcefully before completing allapplication jobs. Resolution is notapplicable for this message.


BW Engine is already in stopped state. This is a debug message andresolution is not applicable.


Enabled BW Debugger in the BWEngine.



Disabled BW Debugger in the BWEngine.




26




INITIATE: install BW Module [{0}:{1}],DeploymentUnit [{2}:{3}].

This is a debug message and itindicates the BW Engine is starting tocreate the BW Module. Resolution isnot applicable for this message.


Installed BW Module [{0}:{1}],DeploymentUnit [{2}:{3}].

This is a debug message and itindicates the BW Engine hascompleted creating the BW Module.Resolution is not applicable for thismessage.


INITIATE: release-resources for BWModule [{0}:{1}], DeploymentUnit [{2}:{3}].

This is a debug message and itindicates the BW Engine is starting torelease the BW Module resources.Resolution is not applicable for thismessage.


Released-resources for BW Module[{0}:{1}], DeploymentUnit [{2}:{3}].

This is a debug message and itindicates the BW Engine hascompleted releasing the BW Moduleresources. Resolution is not applicablefor this message.


INITIATE: undeploy BW Module [{0}:{1}], DeploymentUnit [{2}:{3}].

This is a debug message and itindicates the BW Engine is starting toun-deploying the BW Module.Resolution is not applicable for thismessage.


Undeployed BW Module [{0}:{1}],DeploymentUnit [{2}:{3}].

This is a debug message and itindicates the BW Engine hascompleted un-deploying the BWModule. Resolution is not applicablefor this message.




INITIATE: install BW Component[{0}], Application[{1}:{2}].

This is a debug message and itindicates the BW Engine is starting tocreate the BW Component. Resolutionis not applicable for this message.


Installed BW Component [{0}],Application[{1}:{2}].

This is a debug message and itindicates the BW Engine hascompleted creating the BWComponent. Resolution is notapplicable for this message.

27




INITIATE: initialize BW Component[{0}], Application[{1}:{2}].

This is a debug message and itindicates the BW Engine is starting toinitialize the BW Component.Resolution is not applicable for thismessage.


Initialized BW Component [{0}],Application[{1}:{2}].

This is a debug message and itindicates the BW Engine hascompleted initializing the BWComponent. Resolution is notapplicable for this message.


INITIATE: start BW Component [{0}]. This is a debug message and itindicates the BW Engine is starting theBW Component. Resolution is notapplicable for this message.


Started BW Component [{0}]. This is a debug message and itindicates the BW Engine has statedthe BW Component. Resolution is notapplicable for this message.


INITIATE: stop(Forceful) BWComponent [{0}].



Stopped(Forceful) BW Component[{0}].



INITIATE: destroy BW Component[{0}].



Destroyed BW Component [{0}]. This is a debug message andresolution is not applicable.


INITIATE: release-resources for BWComponent [{0}], Application[{1}:{2}].



Released-resources for BWComponent [{0}], Application[{1}:{2}].



INITIATE: undeploy BW Component[{0}], Application[{1}:{2}].



Undeployed BW Component [{0}],Application[{1}:{2}].



INITIATE: start ServiceBinding(s) orProcessStarter for BW Component[{0}], Application[{1}:{2}].


28




Started ServiceBinding(s) orProcessStarter for BW Component[{0}], Application[{1}:{2}].



INITIATE: stop ServiceBinding(s) orProcessStarter for BW Component[{0}], Application[{1}:{2}].



Stopped ServiceBinding(s) orProcessStarter for BW Component[{0}], Application[{1}:{2}].



INITIATE: start ServiceBinding [{0}]for BW Component [{1}], Application[{2}:{3}].



Started ServiceBinding [{0}] for BWComponent [{1}], Application [{2}:{3}].



INITIATE: stop ServiceBinding [{0}]for BW Component [{1}], Application[{2}:{3}].



Stopped ServiceBinding [{0}] for BWComponent [{1}], Application [{2}:{3}].



Ready to uninstall BW Component[{0}], Application [{1}].



CreatedServiceEndpointRequestHandler forthe ServiceBinding [{0}], Service [{1}],BW Component [{2}], Application [{3}:{4}].





INITIATE: create BW Application [{0}]handle.



Created BW Application [{0}] handle. This is a debug message andresolution is not applicable.


INITIATE: start BW Application [{0}]. This is a debug message andresolution is not applicable.


Started BW Application [{0}]. This is a debug message andresolution is not applicable.


INITIATE: stop(Graceful) for BWApplication [{0}].


29




Stopped(Graceful) BW Application[{0}].



INITIATE: stop(Forceful) BWApplication [{0}].



Stopped(Forceful) BW Application[{0}].



INITIATE: start all ProcessStarters andServiceBindings for BW Application[{0}:{1}].



Started all ProcessStarters andServiceBindings for BW Application[{0}:{1}].



INITIATE: stop all ProcessStarters andServiceBindings for BW Application[{0}:{1}].



Stopped all ProcessStarters andServiceBindings for BW Application[{0}:{1}].



INITIATE: pause BW Application[{0}].



Paused BW Application [{0}]. This is a debug message andresolution is not applicable.


INITIATE: resume BW Application[{0}].



Resumed BW Application [{0}]. This is a debug message andresolution is not applicable.


INITIATE: initialize ProcessStarteractivity [{0}] in Process[{1}], Module[{2}], DeploymentUnit [{3}:{4}].



Initialized ProcessStarter activity [{0}]in Process[{1}], Module [{2}],DeploymentUnit [{3}:{4}].



INITIATE: start ProcessStarter activity[{0}] in Process[{1}], Module [{2}],DeploymentUnit [{3}:{4}].



Started ProcessStarter activity [{0}] inProcess[{1}], Module [{2}],DeploymentUnit [{3}:{4}].


30




INITIATE: stop ProcessStarter activity[{0}] in Process[{1}], Module [{2}],DeploymentUnit [{3}:{4}].



Stopped ProcessStarter activity [{0}] inProcess[{1}], Module [{2}],DeploymentUnit [{3}:{4}].



INITIATE: destroy ProcessStarteractivity [{0}] in Process[{1}], Module[{2}], DeploymentUnit [{3}:{4}].



Destroyed ProcessStarter activity [{0}]in Process[{1}], Module [{2}],DeploymentUnit [{3}:{4}].



INITIATE: release ProcessStarteractivity [{0}] in Process[{1}], Module[{2}], DeploymentUnit [{3}:{4}].



Released ProcessStarter activity [{0}]in Process[{1}], Module [{2}],DeploymentUnit [{3}:{4}].





INITIATE: release ProcessStarteractivity [{0}] in Process[{1}], Module[{2}], DeploymentUnit [{3}:{4}].



Released ProcessStarter activity [{0}]in Process[{1}], Module [{2}],DeploymentUnit [{3}:{4}].





INITIATE: initialize Activity [{0}] inProcess[{1}], Module [{2}],DeploymentUnit [{3}:{4}].



Initialized Activity [{0}] inProcess[{1}], Module [{2}],DeploymentUnit [{3}:{4}].



INITIATE: destroy Activity [{0}] inProcess[{1}], Module [{2}],DeploymentUnit [{3}:{4}].


31




Destroyed Activity [{0}] inProcess[{1}], Module [{2}],DeploymentUnit [{3}:{4}].





























Activity input data validation details.ActivityName={0}, ProcessName={1},Module={2}:{3}, Schema={4}, Data={5}



Activity output data validationdetails. ActivityName={0},ProcessName={1}, Module={2}:{3},Schema={4}, Data={5}


32




The BusinessWorks Event Publisher isdisabled.

This message indicates the BW Engineis configured to disable the eventpublisher; therefore there will be noevent published by the BW Engine.


{0} This is a warning message and ithighlights situations that may affectthe application execution.


Activity resource release operation[com.tibco.bw.runtime.ActivityResource.release()] called at the end of theexecution of the BW group or BWProcess instance encountered error.The Activity resource releaseoperation [{0}.release(boolean)] raisedexception: {1}

The activity resource release operationmust not raise an exception. This isconsidered to be an activity resourceimplementation error.


CatchAll fault details formating issue.Expected [{0}], but received [{1}]

Received unexpected data whenformating the CatchAll fault details.


The BW process [{0}] instancecancelled, JobId [{1}],ProcessInstanceId [{2}],ParentProcessInstanceId [{3}], Module[{4}:{5}], Application [{6}:{7}].

This message is generated when theBusinessWorks Engine cancels aprocess instance execution. A processinstance can be canceled when one ofthe following occurs: the invokeactivity (in the parent process) thatcalled this process instance timed out,the application is stopped nongracefully or the process instance isexplicitly canceled through an internalmanagement interface.


Unable to close the file [{0}]configured for the initial value of the{1} [{2}] in the BW Module [{3}:{4}],DeploymentUnit [{5}:{6}]; encounteredexception [{7}].

The BW Engine was unable to closethe file that contains initial values forthe Module or Job Shared variables.This error occurred when attemptingto close the file, but after reading thefile contents.


The BW Component [{0}:{1}] is alreadyin destroyed state.

The BW framework is attempting todestroy the BW Component that isalready in destroyed state. Resolutionis not applicable.


{0} This error code is used to log BWEngine errors. For more details, referto the additional exception message orthe "CausedBy" statements reportedas part of this error message.

33




Failed to initialize BW Engine due toexception [{0}]

The BW Engine did not successfullyinitialize, and this could be due tomany reasons. For more details, referto the additional exception message orthe "CausedBy" statements reportedas part of this error message.


Failed to initialize BW Engine due todatabase access error

The BW Engine was not able toestablish connection or access theengine database instance. Ensure thedatabase driver, connection, username and password details arecorrectly specified. Also ensuredatabase instance has been started.


Failed to initialize BW Engine due toengine group connection providererror

The BW Engine failed to establishconnection with the engine groupconnection provider. Ensure thegroup connection provider entity(bw.engine.groupProvider.technology) specified in the BW AppNode or BWAppSpace configuration file has beenstarted and accessible to the BWEngine.


Failed to initialize BW Engine due todatabase schema configuration error.The BW Engine database does notcontain the required tables. Ensure theBW Engine database has been createdwith the table schemas required bythe engine

The BW Engine was not able toinitialize due to the engine databaseschema configuration error. Create anew engine database using thedatabase scripts provided in theTIBCO BusinessWorks product andthis will configure the database withthe appropriate schemas required bythe engine.


Failed to initialize BW Engine due tomissing or incorrect engine databaseconfiguration data. The BW Enginepersistence mode property [{0}] is setto [datastore] and this option requiresvalid engine database configurationdata

The BW Engine is configured toexecute in persistence mode"datastore"; however the requireddatabase configuration data was notspecified. Ensure the BW Engine isconfigured with the required databaseconnection details.


Failed to initialize BW Engine due tomissing or incorrect engine databaseconfiguration data. The BW Enginepersistence mode property [{0}] is setto [group] and this option requiresvalid engine database configurationdata

The BW Engine is configured toexecute in persistence mode "group";however the required databaseconfiguration data was not specified.Ensure the BW Engine is configuredwith the required database connectiondetails.

34




Failed to initialize BW Engine due toincompatible engine group name. Thegroup name [{0}] configured for theBW Engine does not match the groupname value in the BW Enginedatabase. Try using a different enginedatabase or change the engine groupname to match the value in thedatabase

This error can occur when the BWEngine is configured to use a groupname that does not match the groupname in the engine database. Toresolve these issues change the enginegroup name to match the group namein the engine database, use a differentengine database that contains thematching engine group name orcreate a new engine database.Furthermore if the group name is notspecified then the BW Engine uses adefault group name. Refer todocumentation for more details onnaming convention used for thedefault engine group name.


Failed to initialize BW Engine due toincompatible persistence modebetween the engine and the enginedatabase. This error can occur if theBW Engine is configured to execute inpersistence mode [group]; howeverthe BW Engine database is configuredfor the persistence mode [datastore].Try using a different database or use adatabase that is configured for thepersistence mode [group]

This error can occur if the enginedatabase was previously used by aBW Engine configured to execute inpersistence mode 'datastore'(bw.engine.persistenceMode=datastore). When a BW Engine uses thedatabase for the first time, thedatabase is updated with the engineexecution persistence mode.Subsequently the persistence modevalue stored in the database cannot bealtered and the same database cannotbe used for different enginepersistence mode. To resolve this issueensure the engine and the databasepersistence mode match or create anew database using the databasescripts provided by the TIBCOBusinessWorks product.

35




Failed to initialize BW Engine due toincompatible persistence modebetween engine and the enginedatabase. This error can occur if theBW Engine is configured to execute inpersistence mode [datastore]; howeverthe engine database is configured forthe persistence mode [group]. Tryusing a database that is configured forthe persistence mode [datastore] orcreate a new engine database

This error can occur if the enginedatabase was previously used by aBW Engine configured to execute inpersistence mode 'group'(bw.engine.persistenceMode=group).When a BW Engine uses the databasefor the first time, the database isupdated with the engine executionpersistence mode. Subsequently thepersistence mode value stored in thedatabase cannot be altered and thesame database cannot be used fordifferent engine persistence mode. Toresolve this issue ensure the engineand the database persistence modematch or create a new database usingthe database scripts provided by theTIBCO BusinessWorks product.


Failed to initialize BW Engine due tomissing or incorrect group connectionprovider configuration data. The BWEngine persistence mode property[{0}] is set to [group] and this optionrequires valid engine groupconnection provider configurationdata.

This error can occur if the BW Engineis configured to execute in persistencemode [group] and the engine is notcorrectly configured with the groupconnection provider data. Ensure theBW Engine is configured with therequired group connection providerdetails.


Failed to initialize BW Engine due toincorrect engine group name. The BWEngine persistence mode property[{0}] is set to [group] and this optionrequires a valid engine group namespecified via property [{1}].

This error can occur if the BW Engineis configured to execute in persistencemode [group] and an empty or invalidengine group name is specified.Ensure the engine group name is notempty or contains a valid name.


Failed to initialize BW Engine. TheBW Engine thread count value isconfigured incorrectly. Ensure thethread count value is set to an integerthat is greater than zero

Ensure the BW Engine thread count isnot configured to be empty or null.Furthermore the thread count valuemust be an integer that is greater thanzero.


Failed to initialize BW Engine. TheBW Engine step count value isconfigured incorrectly. Ensure the stepcount value is set to "-1" or an integerthat is greater than zero

Ensure the BW Engine step count isnot configured to be empty or null.Furthermore the step count valuemust be "-1" or an integer that isgreater than zero.


Failed to initialize BW Engine. TheBW Engine property [{0}] containsincorrect value [{1}]. Ensure the valueis an integer that is greater than one

Ensure the specified BW Engineproperty is not configured to beempty or null. The value configuredfor this property must be an integerthat is greater than zero.

36




Failed to initialize BW Engine. TheBW Engine property [{0}] containsincorrect value [{1}]. Ensure the valueis an integer that is greater than one.

Ensure the specified BW Engineproperty is not configured to beempty or null. The value configuredfor this property must be an integerthat is greater than zero.


Failed to initialize BW Engine. Whilecreating SpringApplicationContextthe BW Engine encounteredexception: {0}.



The ProcessStarter has not beeninitialized or it is in the destroyedstate. The EventSourceContextassociated with the ProcessStarter isinvalid.

A ProcessStarter is attempting toperform an operation when it has notbeen initialized or it is in thedestroyed state. This is considered tobe a ProcessStarter implementationerror.


Failed to initialize BW Engine due toexception [{0}]. This error can occur ifthe BW Engine persistence mode is setto [{1}] and the same databaseconfiguration is used by multiple BWEngines. When a BW Engine isconfigured for the persistence mode[{2}], then each BW Engine must havea unique database configuration. Thisis applicable even if the BW Engines(BW AppNodes) are part of the sameBW AppSpace

This error can be reported whenmultiple BW Engines configured for'datastore' persistence mode isattempting to use the same databaseconfiguration. Ensure differentdatabase configuration specified foreach BW Engine when the persistenceoption is 'datastore'. This is alsoapplicable when multiple BW Engines(BW AppNodes) are part of the sameBW AppSpace.


BW Engine stop operationencountered exception [{0}]

An error was encountered whenstopping the BW Engine. For moredetails, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.


BW Engine graceful stop operationencountered exception [{0}]

An error was encountered whenattempting to gracefully stop the BWEngine. For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.


Exception occurred when accessingcustom XPATH function(s) associatedwith the BusinessWork Engine.Exception={0}

Error was encountered whenattempting to access the custom XPathfunction associated with the BWEngine. Contact TIBCO Support.

37




Failed to enable the BW Debuggerentity in the BW Engine due toexception [{0}]

Error was encountered whenattempting to enable the BWDebugger entity in the BW Engine.Contact TIBCO Support.


BW Debugger connection failed,encountered exception [{0}]

Ensure valid BW Debuggerconnection is provided when enablingthe BW Debugger entity in the BWEngine.


Unable to enable Event Publisher inthe BW Engine, encounteredexception [{0}]

Error was encountered whenattempting to enable the EventPublisher in the BW Engine. ContactTIBCO Support.


Attempt to disable the EventPublisher in the BW Engine,encountered exception [{0}]

Error was encountered whenattempting to disable the EventPublisher in the BW Engine. ContactTIBCO Support.


Unable to associate an activityresource with a BW group. Theactivity [{0}] in process [{1}] is notcontained within a group; howeverthe activity is attempting to associate aresource with a group. {2}

An activity that is not inside a groupis attempting to associate a resourcewith a group. This error can occur dueto an activity implementation error.


Unable to associate an activityresource with a BW loop. The activity[{0}] in process [{1}] is not containedwithin a loop; however the activity isattempting to associate a resourcewith a loop. {2}

An activity that is not inside a loop isattempting to associate a resourcewith a loop. This error can occur dueto an activity implementation error.


Reference Binding configured for theprocess reference [{0}], in process [{1}],module [{2}] provided unsupportedmessage data model [{3}].

The Reference Binding configured forthe process provided an invalidmessage data model. This error canoccur due to the Reference Bindingimplementation error.


Invocation of the Process Reference'soperation [{0}] failed. The BWReference Binding [{1}] configured forthe process reference [{2}] in process[{3}], module [{4}] returned fault [{5}].

This error indicates the ReferenceBinding configured for the processreference failed and returned a fault.


Invalid activity name. The activityname [{0}] is not found in process[{1}], module [{2}:{3}],DeploymentUnit [{4}:{5}].

The error indicates the specifiedactivity name is not contained withinthe BW process. Ensure a validactivity name is specified for thisoperation.

38




The BW Debugger entity is alreadyenabled in the BW Engine and it cannot be enabled again.

The BW Debugger entity in the BWEngine can not be enabled again whenit is already in enabled state. It is onlypossible to disable the BW Debuggerentity when it is in the enabled state.


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

This error message indicates theprocess instance did not completesuccessfully; instead it terminated dueto an error that occurred during theexecution of the process instance. Formore details on the process instancefailure, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.


Activity [{0}] fault. {1} This message indicates the potentialactivity that raised the fault andcaused the process instance to fail.


Invoke activity [{0}] fault. {1} This message indicates the potentialinvoke activity that raised the faultand caused the process instance tofail.


XSLT transformation error. {0} This message indicates the cause ofthe failure could be due to a XSLTtransformation error.


Activity [{0}] XSLT transformationerror. {1}

This message indicates the cause ofthe failure could be due to an ActivityXSLT transformation error.


XPATH error. {0} This message indicates the cause ofthe failure could be due to a XPATHerror.


Activity [{0}] XPATH error. {1} This message indicates the cause ofthe failure could be due to an ActivityXPATH error.


XML related error. {0} This message indicates the cause ofthe failure could be due to a XMLerror.


Activity [{0}] XML related error. {1} This message indicates the cause ofthe failure could be due to an ActivityXML error.

39




Reply activity [{0}] error. The replyactivity cannot be associated with theProcessService request message. Thiserror can occur if the process isimplemented to send reply multipletimes for the same request, the callerof this process is no longer availableor on recovery from a check-point thecaller did not recover because it wasnot part of the check-pointed job. {1}

This error message is reported when aprocess is implemented to executemore than one Reply activity for thesame operation, the caller of thisprocess (Service Binding, ParentProcess) has terminated before Replyactivity can be executed or onrecovery from a check-point the Replyactivity is executed but the caller ofthis process did not recover because itwas not part of the check-pointed job.Ensure the process is notimplemented to reply to same requestmultiple times.


The process instance terminatedwithout replying to the caller of thisprocess. {0}

This message is reported when aprocess instance terminates withoutreplying to the request of aProcessService operation. This canoccur if the process is implementedincorrectly to end the processexecution without performing a replyoperation or when the processinstance is canceled. Ensure theprocess in implemented correctly andthere is no validation errors.


Reply activity [{0}] error. The replyactivity [{1}] encountered error onsending the response to the caller ofthis process. This error can occur if thecaller of this process raised a faultwhen processing the reply message,the caller of this process is no longeravailable. {2}

This error message can be reported forthe following reasons: the caller of thisprocess (Service Binding, ParentProcess) raised a fault whenprocessing the reply message, thecaller of this process is no longeravailable.


{0} This message provides informationfor the process instance failure.


Activity [{0}] error. {1} This message indicates the potentialactivity that raised the fault andcaused the process instance to fail.


Throw activity [{0}] fault. Fault: {1} This message indicates the name ofthe Throw activity that raised the faultand caused the process instance tofail.

40




Invoke activity faulted due an errorfrom the invoked subprocess. {0}

This message indicates the Invokeactivity failed due to an unexpectederror received for the invokedsubprocess. This error can occur if thesubprocess terminated withoutreplying, the subprocess faulted, theinvoked subprocess does not exist, etc.Ensure the invoked subprocess isimplemented correctly and confirmsto the invoked operation contract.


Activity [{0}] faulted due to an objectserialization error. This error canoccur if an object that must beserialized as part of theBusinessWorks process execution isnot Serializable or the Java packagethat contains the class is not exportedcorrectly. {1}

This error can occur when the BWEngine is attempting to serialize a Javaobject to support the persistencefeature and the object cannot beserialized. Ensure the Java object isSerializable and the Java package thatcontains the class is exported.


Fault occurred due to an objectserialization error. This error canoccur if the Java class that must beserialized as part of theBusinessWorks process execution isnot Serializable or the Java packagethat contains the class is not exportedcorrectly. {0}

This error can occur when the BWEngine is attempting to serialize a Javaobject to support the persistencefeature; however the Java objectcannot be serialized. Ensure the Javaobject is Serializable and the Javapackage that contains the class isexported.


Failed to confirm the request messagefrom the receive activity [{0}], inprocess [{1}], module [{2}:{3}],application [{4}:{5}]. This error canoccur if the process is implemented toconfirm multiple times for the samerequest message, the caller of thisprocess is no longer available, onrecovery from a check-point the callerdid not recover because it was notpart of the check-pointed job or thespecified receive activity name isincorrect.

This error message can be reported forthe following reasons: the process isimplemented to execute more thanone confirm activity for the samerequest, the caller of this processinstance (Service Binding, Parentprocess) has terminated before theconfirm activity can be executed or onrecovery from a check-point theconfirm activity is executed; howeverthe caller of this process did notrecover because it was not part of thecheck-pointed job. Ensure the processis not implemented to confirm tosame request for multiple times or theactivity name configured in theconfirm activity is correct.


The reply operation[com.tibco.bw.runtime.EventContext.reply(..)] is not supported for theactivity [{0}], in process [{1}], module[{2}:{3}], application [{4}:{5}].

The operation[com.tibco.bw.runtime.EventContext.reply(..)] is not allowed for thespecified activity and this is animplementation error.

41




Invalid argument value. The BWApplication name cannot be null.

The BusinessWorks Applicationspecified for this operation can not benull or empty. Ensure validapplication name is specified for thisoperation.


Unable to get BW Process instancesinformation for the BW Application[{0}] due to exception [{1}].

Error occurred when obtaining theprocess instance details for thespecified BusinessWorks application.


Unable to get BW Process instanceinformation for the BWProcessIntanceId [{0}] due toexception [{1}].

Error occurred when obtaining theprocess instance details for thespecified BusinessWorksProcessIntanceId.


Unable to get BW Process instancesummary information for the BWProcessIntanceId [{0}] due toexception [{1}].

Error occurred when obtaining theprocess instance details for thespecified BusinessWorksProcessIntanceId.


Failed to suspend the BW Processinstance for the BW ProcessIntanceId[{0}] due to exception [{1}].

Error occurred when attempting tosuspend the process instance for thespecified BusinessWorksProcessIntanceId.


Failed to resume the BW Processinstance for the BW ProcessIntanceId[{0}] due to exception [{1}].

Error occurred when attempting toresume the process instance for thespecified BusinessWorksProcessIntanceId.


Failed to cancel the BW Processinstance for the BW ProcessIntanceId[{0}] due to exception [{1}].

Error occurred when attempting tocancel the process instance for thespecified BusinessWorksProcessIntanceId.


BW AppNode name [{0}] exceeds 250characters and it is possible to createthe internal engine alias name.

BW AppNode name exceeds 250characters this is not possible createunique engine name. EnsureAppNode name is less than 250characters.


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

The BW Module did not get installedin the BW Engine, and this could bedue to many reasons. For moredetails, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.

42




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

The BW Engine encountered error(s)when releasing resources associatedwith the BW Module and this couldbe due to many reasons. For moredetails, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.


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

The BW Engine encountered error(s)when un-deploying the BW Moduleand this could be due to manyreasons. For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.


Failed to install BW Module [{0}:{1}],DeploymentUnit [{2}:{3}]. The moduleor a process is configured to utilize theBW Engine persistence feature;however the BW Engine is notconfigured with a correct enginepersistence mode. Ensure the BWEngine is configured for the enginepersistence mode [datastore] or[group] before installing this module.

The BW Module or the process isusing a persistence feature, moduleshared variable with persistenceoption, etc..; however the BW Enginepersistence mode is not setappropriately for this feature. Ensurethe BW Engine persistence mode(bw.engine.persistenceMode) is set to"datastore" or "group" and therequired engine databaseconfiguration is specified.


Failed to start BW Module due to anactivity start error. CausedBy

This error is reported when the BWActivity in the process fails toinitialize and start. For more details,refer to the additional exceptionmessage or the "CausedBy"statements reported as part of thiserror message.


Unable to obtainSchemaComponentCache(Namespace={0}, Location={1},BaseURI={2}) for BW Module [{3}:{4}]due to exception [{5}]

Failed to obtainSchemaComponentCache for theschema required by the BW Moduleand this could be due to manyreasons. For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.

43




Unable to add schema toSchemaComponentCache(Namespace={0}, Location={1}) due toexception [{2}]

Failed to add schema required by theBW Module toSchemaComponentCache and thiscould be due to many reasons. Formore details, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.


Unable to obtain WSDL ModuleCache(Namespace={0}, Location={1}) for BWModule [{2}:{3}]. TheWSDLCacheService operation [{4}]returned "null".

Failed to get the WSDL ModuleCacherequired by the BW Module.


Unable to obtain WSDL ModuleCache(Namespace={0}, Location={1}) for BWModule [{2}:{3}]. TheWSDLCacheService operation [{4}]returned "null".

Failed to get the WSDL ModuleCachefor the WSDL required by the BWModule.


Unable to obtain WSDL ModuleCache(Namespace={0}, Location={1}) for BWModule [{2}:{3}]. TheWSDLCacheService operation [{4}]returned exception [{5}]

Failed to get the WSDL ModuleCachefor the WSDL required by the BWModule and this could be due tomany reasons. For more details, referto the additional exception message orthe "CausedBy" statements reportedas part of this error message.


Unable to resolve Schema(Namespace={0}, Location={1},BaseURI={2}) for BW Module [{3}:{4}].The SchemaCacheService operation[{5}] returned "null".

Failed to resolve the schema requiredby the BW Module. Ensure theschema is valid, the schemasimported/referenced by this schemaare valid, the schemaLocation of theschemas imported by this schema isvalid,..


Invalid or empty file name is specifiedfor the initial value of the {0} [{1}] inBW Module [{2}:{3}], DeploymentUnit[{4}:{5}].

The module shared variable or the jobshared variable contains incorrectvalue or is empty. Ensure the moduleor the job shared variable has beeninitialized or assigned with a correctvalue.


The file [{0}] configured for the initialvalue of the {1} [{2}] is not found inBW Module [{3}:{4}], DeploymentUnit[{5}:{6}].

The module shared variable or the jobshared variable has been initializedwith a file URL that is not found in theBW Module. Ensure the specified filename is valid or the file is containedwithin the BW Module.

44




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

Failed to access the file specified in themodule or job shared variable and thiscould be due to many reasons. Formore details, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.


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

Failed to open the file specified in themodule or job shared variable and thiscould be due to many reasons. Formore details, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.


Unable to read the file [{0}] configuredfor the initial value of the {1} [{2}] inBW Module [{3}:{4}], DeploymentUnit[{5}:{6}]; encountered exception [{7}].

Failed to read the file specified in themodule or job shared variable and thiscould be due to many reasons. Formore details, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.


The contents of the file [{0}]configured for the initial value of the{1} [{2}] in BW Module [{3}:{4}],DeploymentUnit [{5}:{6}] is empty.

Ensure the file specified for themodule or job shared variable is notempty.


Invalid BW Module property. Themodule property [{0}] is not defined inthe BW Module [{1}:{2}],DeploymentUnit [{3}:{4}]. Thereforethe XPath function"getModuleProperty({5})" contained inthe XSLT is not able to resolve thismodule property.

Ensure the module property correctlydefined in the BW Module.


Unable to resolve the BW Moduleproperty [{0}] defined in the BWModule [{1}:{2}], DeploymentUnit [{3}:{4}] via the XPath function"getModuleProperty({5})" contained inthe XSLT. Encountered exception [{6}].

Ensure the module property correctlydefined in the BW Module.


Failed to create BindingReferenceEndpoint for the processreference [{0}] in process [{1}], module[{2}:{3}], DeploymentUnit [{4}:{5}];encountered exception [{6}]

Encountered errors when creating thebinding endpoint for the BW processreference and and this could be due tomany reasons. For more details, referto the additional exception message orthe "CausedBy" statements reportedas part of this error message.

45




Failed to obtain module properties forthe module [{0}:{1}], DeploymentUnit[{2}:{3}]; encountered exception [{4}]

BW framework layer encounterederrors when accessing moduleproperties for the specified BWModule. Contact TIBCO Support.


Unable to obtain WSDL Interfacedetails for the PortType [{0}], that isassociated with the BW Module [{1}:{2}]. Encountered exception [{3}]

Error occurred when attempting toobtain WSDL details for the specifiedPortType, and this could be due tomany reasons. For more details, referto the additional exception message orthe "CausedBy" statements reportedas part of this error message.


Failed to install BW Component [{0}],Application [{1}:{2}]

The BW Component did not getinstalled in the BW Engine, and thiscould be due to many reasons. Formore details, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.


Failed to install BW Component [{0}],Application [{1}:{2}]. The applicationis configured with Job PageThresholdproperty[bw.application.job.pageThreshold.*];however the BW Engine is notconfigured with a correct enginepersistence mode. Ensure the BWEngine is configured for the enginepersistence mode [datastore] or[group] before installing thisapplication.

The BusinessWorks application or thecomponent in the application isconfigured to use the JobPageThreshold property[bw.application.job.pageThreshold.*]and this requires the BW Engine to beconfigured for the "datastore" or"group" persistence mode. Stop theBusinessWorks AppSpace, configurethe BW Engine for the enginepersistence mode [datastore] or[group] and restart the AppSpacebefore installing the application.


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

Error occurred when releasing theresources associated with the BWComponent, and this could be due tomany reasons. For more details, referto the additional exception message orthe "CausedBy" statements reportedas part of this error message.


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

Error occurred when un-deployingthe BW Component and this could bedue to many reasons. For moredetails, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.

46




Failed to initialize BW Component[{0}], Application [{1}:{2}]

Error occurred when initializing theBW Component and this could be dueto many reasons. For more details,refer to the additional exceptionmessage or the "CausedBy"statements reported as part of thiserror message.


Failed to initialize BW Component[{0}], Application [{1}:{2}] due toactivity creation error

Error occurred when creating aninstance of an activity that isassociated with the BW Component;therefore the BW Component can notbe initialized. For more details, referto the additional exception message orthe "CausedBy" statements reportedas part of this error message.


Failed to initialize BW Component[{0}], Application [{1}:{2}] due toactivity or resource configurationerror

There is a configuration error in theactivity or resource that is associatedwith the BW Component; thereforethe BW Component can not beinitialized. For more details, refer tothe additional exception message orthe "CausedBy" statements reportedas part of this error message.


Failed to initialize BW Component[{0}], Application [{1}:{2}] due toactivity implementation error

There are implementation errors inthe activity that is associated with theBW Component; therefore the BWComponent can not be initialized. Formore details, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.


Failed to initialize BW Component[{0}], Application [{1}:{2}] due toactivity initialization error

Error occurred when initializing anactivity that is associated with the BWComponent; therefore the BWComponent can not be initialized. Formore details, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.


Encountered error when destroyingthe BW Component [{0}]

Error occurred when destroying ordeleting the BW Component and thiscould be due to many reasons. Formore details, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.

47




Encountered errors when destroyingthe BW Component [{0}]

Error occurred when destroying ordeleting the BW Component and thiscould be due to many reasons. Formore details, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.


Failed to start BW Component [{0}],Application [{1}:{2}]

Error occurred when starting the BWComponent and this could be due tomany reasons. For more details, referto the additional exception message orthe "CausedBy" statements reportedas part of this error message.


Encountered error(s) when stoppingthe BW Component [{0}], Application[{1}:{2}]

Error occurred when stopping the BWComponent and this could be due tomany reasons. For more details, referto the additional exception message orthe "CausedBy" statements reportedas part of this error message.


Encountered error(s) when startingthe ProcessStarter associated with theBW Component [{0}], Application [{1}:{2}]

Error occurred when starting theProcessStarter activity that isassociated with the BW Component.For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.


Encountered error(s) when stoppingthe ProcessStarter associated with theBW Component [{0}], Application [{1}:{2}]

Error occurred when stopping theProcessStarter activity that isassociated with the BW Component.For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.


Failed to start ServiceBinding [{0}] forthe BW Component [{1}], Application[{2}:{3}] due to ServiceBindinglifecycle error

Error occurred when starting theServiceBinding that is associated withthe BW Component. For more details,refer to the additional exceptionmessage or the "CausedBy"statements reported as part of thiserror message.


Unable to stop ServiceBinding [{0}] forthe BW Component [{1}], Application[{2}:{3}] due to ServiceBindinglifecycle error

Error occurred when stopping theServiceBinding that is associated withthe BW Component. For more details,refer to the additional exceptionmessage or the "CausedBy"statements reported as part of thiserror message.

48




The job flow limit property [{0}] forthe application or the component isconfigured incorrectly. Ensure the jobflow limit property value is set to aninteger that is greater than zero.

The BW application or component'sjob flow limit property is configuredwith an incorrect value. The job flowlimit property value must be aninteger that is greater than zero.


The job priority property [{0}] for theapplication or the component isconfigured incorrectly. Ensure the jobpriority property value is set to "low","normal" or "high".

The BW application or component'sjob priority property is configuredwith an incorrect value. The jobpriority property can only beconfigured with the string value"low", "normal" or "high".


The property to enable activity inputvalidation for the application or thecomponent is configured incorrectly.Ensure properties that are prefixedwith [{0}] are set with value "true" or"false".

The property that is used to determinethe enabling of the activity outputvalidation for the application or thecomponent is configured with anincorrect value. This property canonly be configured with the stringvalue "true" or "false".


The property to enable activity outputvalidation for the application or thecomponent is configured incorrectly.Ensure properties that are prefixedwith [{0}] are set with value "true" or"false".


The property that specifies the asyncactivity default wait time isconfigured incorrectly. Ensure theproperty [{0}] or the propertiesprefixed with [{1}] are configured witha zero or positive numeric value

The property that specifies the defaultwait time (timeout) value for anasynchronous activity is configuredincorrectly. The value for this propertymust be a zero or positive number.This property can be configured theAppSpace/AppNode configurationfile 'config.ini'


Failed to start BW Application [{0}]due to exception [{1}]

The BW Application did not start andthis could be due to many reasons.For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.


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

Error occurred in an activity that isassociated with the BW Application;therefore the BW Application did notstart. For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.

49




Encountered error when attempting togracefully stop BW Application [{0}:{1}]

Error occurred when attempting togracefully stop the BW Applicationand this could be due to manyreasons. For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.


The BW Application [{0}:{1}] is alreadyin stopping state. Unable to performoperation "stopApplicationGraceful"

The BW Application is already instopped state; therefore it can not bestopped again.


Encountered error when attempting tostop BW Application [{0}:{1}]

Error occurred when attempting tostop the BW Application and thiscould be due to many reasons. Formore details, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.


Encountered errors when attemptingto stop BW Application [{0}:{1}]


Unable to start ServiceBinding(s) orProcessStarter(s) associated with theBW Application [{0}:{1}]

Error occurred when attempting tostart the ServiceBinding(s) orProcessStarter(s) activity that isassociated with the BW Application.For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.


Unable to stop ServiceBinding(s) orProcessStarter(s) associated with theBW Application [{0}:{1}]

Error occurred when attempting tostop the ServiceBinding(s) orProcessStarter(s) activity that isassociated with the BW Application.For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.


Encountered error when attempting topause BW Application [{0}:{1}] job(s)

Error occurred when attempting toresume the BW Application. For moredetails, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.


Encountered error when attempting toresume BW Application [{0}:{1}] job(s)

50




Failed to create the ProcessStarteractivity [{0}] in process [{1}], module[{2}] due to exception [{3}]

Error occurred when attempting tocreate an instance of theProcessStarter activity in a process.For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.


Failed to create the ProcessStarteractivity [{0}] in process [{1}], module[{2}] due to unexpected exception [{3}]

Unexpected error occurred whenattempting to create an instance of theProcessStarter activity in a process.For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.


Failed to initialize the ProcessStarteractivity [{0}] in process [{1}], module[{2}] due to activity lifecycle error

Error occurred when attempting toinitialize an instance of theProcessStarter activity in a process.For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.


Failed to initialize the ProcessStarteractivity [{0}] in process [{1}], module[{2}] due to unexpected activitylifecycle error

Unexpected error occurred whenattempting to initialize an instance ofthe ProcessStarter activity in aprocess. For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.


Failed to start the ProcessStarteractivity [{0}] in process [{1}], module[{2}] due to activity lifecycle error

Error occurred when attempting tostart the ProcessStarter activity in aprocess. For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.


Failed to start the ProcessStarteractivity [{0}] in process [{1}], module[{2}] due to unexpected activitylifecycle error

Unexpected error occurred whenattempting to start the ProcessStarteractivity in a process. For more details,refer to the additional exceptionmessage or the "CausedBy"statements reported as part of thiserror message.

51




The stop operation for theProcessStarter activity [{0}] in process[{1}], module [{2}] failed withunexpected exception [{3}]

Unexpected error occurred whenattempting to stop the ProcessStarteractivity in a process. TheProcessStarter activity stop operation"com.tibco.bw.runtime.EventSource.stop()" failed and returned unexpectedexception. The ProcessStarter stopoperation must not raise a fault and itis considered to be a ProcessStarteractivity implementation error.


The destroy operation for theProcessStarter activity [{0}] in process[{1}], module [{2}] failed withunexpected exception [{3}]

Unexpected error occurred whenattempting to destroy theProcessStarter activity in a process.For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.


The release operation for theProcessStarter activity [{0}] in process[{1}], module [{2}] failed withunexpected exception [{3}]

Unexpected error occurred whenattempting to release resources for theProcessStarter activity in a process.For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.


Failed to process the event from theProcessStarter activity [{0}]

BWEngine failed to process the newevents from the ProcessStarteractivity. For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.


Failed to execute event from theProcessStarter activity due to activityoutput data validation error. Theoutput data from ProcessStarteractivity [{0}] does not conform to theProcessStarter activity output schema.Validation error details: {1}.

This error message is reported whenthe output data generated by theProcessStarter activity does notcomply with the output schema of theProcessStarter activity. This error canoccur if ProcessStarter activity is notimplemented correctly to generate thevalid output data.

52




The BWEngine is unable accept newevents from the ProcessStarter activity[{0}], in process [{1}], module [{2}]since the ProcessStarter is in thestopped sate. When the ProcessStarteris in the stopped state, the BWEnginewill not accept new events.

The ProcessStarter generated newevents when it is in the stopped state.A ProcessStarter must not generatenew events during the stopped stateand it will be considered asProcessStarter activityimplementation error. TheProcessStarter is in the stopped stateonce the BWEngine invokes theProcessStarter operation"com.tibco.bw.runtime.EventSource.stop" or before the invocation of theProcessStarter operation"com.tibco.bw.runtime.EventSource.start".


The model or the runtime class for theactivity [{0}] in process [{1}], module[{2}] is implemented incorrectly. Theactivity model class [{3}] does notcontain the configuration property[{4}] as defined in the annotation forthe member variable [{5}] declared inthe activity runtime class [{6}].

This error message is generated if theBW activity is not implementedcorrectly. Ensure the BW activitymodel class contains the requiredattribute or property.


The model or the runtime class for theactivity [{0}] in process [{1}], module[{2}] is implemented incorrectly. Theactivity model [{3}] does not containthe attribute [{4}] as defined in theannotation for the member variable[{5}] declared in the activity runtimeclass [{6}]. The attribute must be oneof the following that is specified in theactivity model [{7}]


The model or runtime class for theactivity [{0}] in process [{1}], module[{2}] is implemented incorrectly. Theactivity model class [{3}] associatedwith the activity runtime class [{4}]has a configuration property which isof unsupported data type. The activityconfiguration property data type [{5}]is not supported.

This error message is generated if theBW activity is not implementedcorrectly. Ensure the BW activitymodel class contains the property of asupported data type.


The model or runtime class for theactivity [{0}] in process [{1}], module[{2}] is implemented incorrectly.Unable to set member variable [{3}]declared in the activity runtime class[{4}]. Encountered exception [{5}].

This error message is generated if theBW activity is not implementedcorrectly. Ensure the BW activityruntime class member variable isdefined correctly.

53




The resource specified for the processproperty [{0}] in process [{1}], module[{2}] is not available in the runtimeenvironment. This process property isused by the activity [{3}] in process[{4}]. Ensure the resource isconfigured and installed correctly.

A resource assigned to the processproperty is not accessible orresolvable at runtime. Ensure theprocess property is configuredcorrectly and the required resource isresolvable at runtime.


The process property [{0}] in process[{1}], module [{2}] has an incorrectvalue [{3}]. This process property isused by the activity [{4}] in process[{5}]. For DateTime, ensure the valuehas the format [{6}].

The process property is configuredwith a incorrect value. Ensure theprocess property is configuredcorrectly, specially for a DateTimedata type.


The resource obtained from theframework for the process property[{0}] in process [{1}], module [{2}] isnot compatible with the data type ofthe process property. Encounteredexception [{3}].

The value assigned to the processproperty did resolve to the data typeexcepted by the process property .Ensure the process property containsthe correct value or the moduleproperty assigned to the processproperty is contains the correct value.


One or more required fields of theactivity [{0}] in process [{1}], module[{2}] is not configured correctly.Ensure the required fields of theactivity contains valid data.

The activity is not configuredcorrectly. Ensure the all required fieldsfor the activity at design time arepopulated correctly.


Failed to create the activity [{0}] inprocess [{1}], module [{2}] due toexception [{3}]

Unexpected error occurred whenattempting to create an instance of anactivity. For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.


Failed to create the activity [{0}] inprocess [{1}], module [{2}] due tounexpected exception [{3}]


Failed to initialize the activity [{0}] inprocess [{1}], module [{2}] due toactivity lifecycle error

Error occurred when attempting toinitialize an instance of an activity. Formore details, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.


Failed to initialize the activity [{0}] inprocess [{1}], module [{2}] due tounexpected activity lifecycle error

Unexpected error occurred whenattempting to initialize an instance ofan activity. For more details, refer tothe additional exception message orthe "CausedBy" statements reportedas part of this error message.

54




The execute operation for the activity[{0}] in process [{1}] failed withunexpected exception [{2}]

The activity execution failed andraised an unexpected exception. Formore details, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.


The post-execute operation for theasynchronous activity [{0}] in process[{1}] failed with unexpected exception[{2}]

The post-execute operation for anasynchronous activity failed andraised an unexpected exception. Formore details, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.


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

The cancel operation for anasynchronous activity failed andraised an unexpected exception. Formore details, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.


BWEngine was unable to executecancel operation for the activity [{1}]in process [{2}], module [{3}] due toexception [{4}]

BWEngine encountered error whenattempting to execute cancel operationfor the activity. For more details, referto the additional exception message orthe "CausedBy" statements reportedas part of this error message.


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

The destroy operation for an activityfailed and raised an unexpectedexception. For more details, refer tothe additional exception message orthe "CausedBy" statements reportedas part of this error message.


The process property [{0}] is notdefined in the BW Process [{1}]

Unable to resolve the specifiedprocess property. Ensure this processproperty is correctly defined in theBW Process.


The process property [{0}] has notbeen registered with the activitycontext or the event source context.

The specified process property has notbeen correctly registered with theactivity context. This error can occur ifthe BW activity is not implementedcorrectly to register the processproperty via method[com.tibco.bw.runtime.ActivityContext.registerProcessProperty].

55




Failed to resolve process property [{0}]from the BW Process [{1}]

Failed to resolve the specified processproperty. Ensure the specified processproperty is defined in the process. Formore details, refer to the additionalexception message in the cause.


The module property [{0}] is notdefined in the BW Module [{1}:{2}]

Unable to resolve the specifiedmodule property. Ensure this moduleproperty is correctly defined in theBW Module.


The module property [{0}] has notbeen registered with the activitycontext or the event source context.

The specified module property hasnot been correctly registered with theactivity context. This error can occur ifthe BW activity is not implementedcorrectly to register the moduleproperty via method[com.tibco.bw.runtime.ActivityContext.registerModuleProperty].


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

Failed to resolve the specified moduleproperty. Ensure the specified moduleproperty is defined in the module. Formore details, refer to the additionalexception message or the "CausedBy"statements reported as part of thiserror message.


Activity [{0}] timed out. The activity wait or execution timehas exceeded the timeout valuespecified for the activity.


Activity input data validation error.The input data for activity [{0}] inprocess [{1}], module [{2}] does notconform to the activity input schema.{3} {4}

This error message is reported whenthe data that is provided as an inputto the activity does not comply withthe input schema of the activity. Thiserror can occur if the previous activityin the process generated incorrectdata or the activity input XSLTtransformation generated data thatdoes not comply with the inputschema of the activity.

56




Activity output data validation error.The output data from activity [{0}] inprocess [{1}], module [{2}] does notconform to the activity output schema.{3} {4}

This error message is reported whenthe output data generated by theactivity does not comply with theoutput schema of the activity. Someactivities can generate in-compliantoutput if it receives incorrect datafrom the external entity it isinteracting. In these scenarios, ensurethe external entity provides or returnsthe correct data excepted by theactivity.


Activity input/output data validationerror. The input/output data foractivity [{0}] in process [{1}], module[{2}] does not conform to the activityinput/output schema. {3} {4}

This error message is reported whenthe data that is provided as an inputto the activity or the output datagenerated by the activity does notcomply with the output schema of theactivity.


Unable to obtain activity input data.The BW Engine has not beeninitialized or started.

This error message is reported whenan entity such as the event subscriberattempts to obtain an activity inputdata before the BW Engine has beeninitialized or started. Ensure the BWEngine has started before performingthis operation.


Unable to obtain activity input data.The specified ActivityEvent object isinvalid, the ActivityEvent can not benull.

This error message is reported whenan entity such as the event subscriberattempts to obtain an activity inputdata; however the specifiedActivityEvent(com.tibco.bw.runtime.event.ActivityAuditEvent) object is invalid or null.Ensure the ActivityEvent object isvalid.


Unable to obtain activity input datadue to exception [{0}]

Unexpected error occurred when anentity such as the event subscriber isattempting to obtain activity inputdata. For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.


Unable to obtain activity output data.The BW Engine has not beeninitialized or started.

This error message is reported whenan entity such as the event subscriberattempts to obtain an activity outputdata before the BW Engine has beeninitialized or started. Ensure the BWEngine has started before performingthis operation.

57




Unable to obtain activity output data.The specified ActivityEvent object isinvalid, the ActivityEvent can not benull.

This error message is reported whenan entity such as the event subscriberattempts to obtain an activity outputdata; however the specifiedActivityEvent(com.tibco.bw.runtime.event.ActivityAuditEvent) object is invalid or null.Ensure the ActivityEvent object isvalid.


Unable to obtain activity output datadue to exception [{0}]

Unexpected error occurred when anentity such as the event subscriber isattempting to obtain activity outputdata. For more details, refer to theadditional exception message or the"CausedBy" statements reported aspart of this error message.


Unable to obtain XPath functionsassociated with the BusinessWorkActivity, encountered exception [{0}]

Error was encountered whenattempting to obtain the list of XPathfunctions associated with the BWActivity.


Unable to find process information forprocess [{0}] in moduleModuleName={1}, ModuleVersion={2}.

BWEngine is not able to obtainprocess information for the specifiedBW process. Ensure the BW Modulecontains the required process.

58


Palettes

This section describes the error messages that can be reported by the activities or entities associatedwith palettes.

General Palette Error CodesThis section describes the error messages that can be reported by the activities or entities associatedwith the BusinessWorks Container Edition General Activities palette.


TIBCO-BW-PALETTE-GENERALACTIVITIES-VALIDATION-500001

Activity configuration error. The endtime must be greater than start timefor Timer activity [{0}] in the process[{1}].

TIBCO-BW-PALETTE-GENERALACTIVITIES-000001

The Timer ProcessStarter activity [{0}]failed to generate a new event due toexception [{1}]







{0} This is an informational message andit highlights the runtime progress ofthe activity. Resolution is notapplicable.


{0} This is a warning message and ithighlights situations that may affectthe activity execution.


Error executing external command[{0}]: [{1}].

Ensure the activity is configuredcorrectly.


Error accessing file or directory [{0}]:[{1}].

Ensure the file or directory name isvalid and the access permissions areset appropriately.

59




No command specified. Ensure the specified field in theactivity input is configured with thecorrect data.


Input data error in field [{0}] expectinga valid [{1}]


Sleep interval value [{0}] is not valid. Ensure the sleep interval is a positivelong value.

TIBCO-BW-PALETTE-GENERAL-ACTIVITIES-500001

Activity configuration error. The {2}Shared Variable must be configuredfor {3} Shared Variable activity [{0}] inthe process [{1}].

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











File name [{0}] is not valid. Ensure that file name must not beempty or null string.

60




File [{0}] was not found. Ensure that File indicated by fileNameexists at the given location.


File [{0}] already exists. Ensure the Overwrite checkBox ongeneral tab is checked or delete thealready existing file.


An exception [{0}] occurred whenattempting to write to the file [{1}].

Ensure the file name is valid and theaccess permissions are setappropriately.


Unable to create file [{0}] due to file ordirectory denoted by the pathname[{1}] does not exist.

Ensure thecreateNonExistingDirectory option ongeneral tab is checked.


Cannot read the binary content fromthe file [{0}].



Cannot read the string content fromthe file [{0}].



The file encoding [{0}] is not valid. Ensure the encoding provided isvalid.


Unable to rename the file from [{0}] tofile [{1}].



Unable to rename the file from [{0}] tofile [{1}]. The destination file existsand its type is different then the typeof the source file.

Ensure the source file and destinationfile both are of same type.


The file activity [{0}] cannot be used tomove a directory.

Ensure the directories can't be movedunless they have same parentDirectory.


Cannot remove the file [{0}]. Ensure the file or directory name isvalid and the access permissions areset appropriately.


An exception [{0}] occurred whenattempting to create the file [{1}].



Cannot overwrite the file [{0}] to file[{1}], when the overwrite flag is notselected in the activity configuration.

Ensure the Overwrite checkBox ongeneral tab is checked or delete thealready existing file explicitly.

61




Cannot copy a directory [{0}] to anexisting file [{1}].

Ensure that source should not be adirectory when destination exists andis a File.


Cannot copy multiple files [{0}] to anexisting file [{1}].

Ensure that when using pattern insource it should not match withmultiple files to copy into a singledestination file.


Cannot create missing path [{0}]. Ensure thecreateNonExistingDirectory ongeneral tab is checked.


Cannot copy from file [{0}] to file [{1}]. Ensure the file or directory name isvalid and the access permissions areset appropriately.


The file name value provided for theactivity input is empty or null.

Ensure that fileName must not beempty or null string.


File [{0}] was not found due to fault[{1}].

Ensure that File indicated by fileNameexists at the given location.


The ProcessStarter activity [{0}] failedto a generate a new event due toexception [{1}].



The File Poller ProcessStarter activity[{0}] failed to a generate a new eventdue to exception [{1}] since it is in thestopped state.


HTTP Palette Error CodesThis section describes the error messages that can be reported by the activities or entities associatedwith the BusinessWorks Container Edition HTTP palette.


TIBCO-BW-PALETTE-HTTP-000001






62








The Http Server replied with a [{0}]status code.

Check the status code to know thereason for the error.


The Http Server replied with a [{0}]status code

Check the status code to know thereason for the error.


An exception was thrown while tryingto initialize the Http client

Correct the configuration of Send HttpRequest activity.


An exception occurred while trying toinitialize the Http server: [{0}]

Check the exception and correct theconfiguration of Http Connectorresource or Http ProcessStarter.


A POST Method cannot sendparameters if the message body isspecified

Correct the input data of Send HttpRequest activity.Make sure messagebody is not specified whenparameters are used.


A GET Method doesn't have amessage body

Correct the input data of Send HttpRequest activity. Make sure that themessage body is not specified for aGET request.


Invalid endpoint URL Correct either the http clientconfiguration or the input data ofSend Http Request activity.


Invalid input data. The encoding isnot supported

Correct the input data. Make sure theencoding is supported. See thedocumentation.


The http method [{0}] is not valid Correct the input data of Send HttpRequest activity. Make sure that theHTTP method is valid.


An exception was thrown while tryingto url-encode the data

Correct the input data. See thedocumentation.

63




Attachment not supported for HTTPmethod [{0}]. Only HTTP 'POST' cansend attachments

Check input of Send Http Requestactivity. Only 'POST' method can sendattachments.


Error serializing attachment data,Cause: [{0}]

Check the exception and correct theattachment data.


An IOException was thrown whiletrying to execute the Http method

System exception.


An exception was thrown while tryingto execute the Http method. TheReason-code is [{0}]

System exception.


An IOException was thrown whiletrying to read the response

System exception.


An IOException was thrown whiletrying to send the response

System exception.


An Exception was thrown whiletrying to send the response

System exception.


The header [{0}] is defined as non-Repeating Header in Input Headers.This header cannot have multipleoccurrences in DynamicHeaders.

Correct the input data.


The HTTP ProcessStarter [{0}] failed togenerate a new event due to exception[{1}]

Check the exception and correct theconfiguration of Http connector orHttp Receiver.


Failed to reply to HTTP ProcessStarteractivity. This error can occur if theHTTP Response activity is executedafter recovering from a check-pointedBusinessWorks process instance.

Check point activity should not beplaced between Http ProcessStarterand Send Http Response activity.


Failed to authenticate request.Username and Password is not set.



Failed to authenticate request. Check if the LDAP resource isconfiguired on Http Connectorresource.

64


Java Palette Error CodesThis section describes the error messages that can be reported by the activities or entities associatedwith the BusinessWorks Container Edition Java palette.


TIBCO-BW-PALETTE-JAVA-PROCESSSTARTER-000001

[{0}]


[{0}]


[{0}]


[{0}]


[{0}]


The JAVA ProcessStarter activity [{0}]failed to a generate a new event due toexception [{1}]

Ensure that the correct object passedto the 'onEvent' method in thespecified Java class. Please refer to thedeclared class implementation fordetails.


Illegal onEvent(Object output)/onError(Throwable throwable)method call. OnEvent/OnErrormethod must not be called in the initmethod or during the initializationphase.

Remove the onEvent(Object output)method call in the init method.


The JAVA ProcessStarter activity [{0}]failed to a generate a new event due toexception [{1}] since it is in thestopped state.

Ensure that the ProcessStarter hasbeen stopped properly.

TIBCO-BW-PALETTE-JAVA-000001

[{0}] This is an internal product error.Contact TIBCO Support.

65




[{0}] This is a trace message and resolutionis not applicable.


[{0}] This is a debug message andresolution is not applicable.


[{0}] This is an informational message andit highlights the runtime progress ofthe activity. Resolution is notapplicable.


[{0}] This is a warning message and ithighlights situations that may affectthe activity execution.


Internal error occurred. Class=[{0}],Method=[{1}], Cause=[{2}]

Make sure the Java Global Instanceresource has properly referenced.


Input data error in field [{0}] because[{1}].

Ensure that the correct values areprovided for the method parameterelements that are in the activity inputtab.


Output data error in field [{0}] because[{1}].

Ensure that the getter methods arereturning the correct values to displaythe activity output tab.


Output data error in field [{0}] valuecannot be null.

Ensure that the getter methods are notreturning null to display the activityoutput tab.


Output data error in field [{0}] value isnot serializable.

Ensure that the getter method returnsa serializable Java class to display theactivity output tab.


While executing method [{0}]encountered exception [{1}] [{2}].

Correct the error stated in theexception message and retry.


Activity input data conversion error.Exception [{0}] occurred while tryingto render the activity input data. [{1}]

Incorrect object reference wasspecified for the declared Java class.Ensure that the correct Java objectreference is provided for the declaredJava class element shown in the inputtab of this activity.


Activity output data conversion error.Exception [{0}] occurred while tryingto create the activity output data. [{1}]

Ensure that the unsupported datatypes are not utilized or referenced inyour Java class.

66




The Java class [{0}] is not found in theclasspath. EncounteredClassNotFoundException [{1}].

Ensure that that the specified class fileis contained in the classpath.


Activity input error. The activityreceived an incorrect value for themethod parameters.IllegalArgumentException occurredwhile trying to construct an instanceof the Java class [{0}]: [{1}]

Ensure that the correct values areprovided for the constructorparameter elements that are in theactivity input tab.


Unable to construct an instance of theJava class [{0}]. Encountered exception[{1}] [{2}].



The constructor for the Java class [{0}]raised exception [{1}]. [{2}]

The exception was raised by theconstructor of the declared Java class.Please refer to the Java classimplementation for details.


Unable to obtain information for themethod [{0}] from the class [{1}].EncounteredNoSuchMethodException [{2}].

Reconfigure this activity or verify thatthe declared Java class has notchanged since the last configuration.


Unable to obtain information for themethod [{0}] from the class [{1}].Encountered SecurityException [{2}].



Activity input error. The activityreceived an incorrect value for themethod parameters. When attemptingto invoke the method [{0}],encounteredIllegalArgumentException [{1}].

Ensure that the correct values areprovided for the method parameterelements that are in the activity inputtab.


Activity input error. The activityreceived an incorrect Java object forthe declared Java class [{0}]. Theactivity required an instance of theJava class [{1}], but received aninstance of the Java class [{2}]: [{3}]

Ensure that the correct Java objectreference is provided for the declaredJava class element shown in the inputtab of this activity. Ensure that theclasspath refers to the correct declaredclass.


Activity input error. The activityreceived an incorrect Java object forthe declared Java class [{0}]. The Javaobject received is not compatible withthe Java object required by thisactivity. The activity required aninstance of the Java class [{1}]: [{2}]


67




Activity input error. The activityreceived 'null' value for the for thedeclared Java class. The activityrequired an instance of the class [{0}],but received a 'null'.

Ensure that the correct Java objectreference is provided for the declaredJava class element shown in the inputtab of this activity.The precedingactivity that provides the input valuefor this activity should not produce anull for its output.


Unable to invoke the method [{0}].Encountered exception [{1}] [{2}].



Unable to invoke the cleanup method[{0}]. Encountered exception [{1}] [{2}].



The method [{0}] raised exception[{1}]. [{2}].

The exception was raised by themethod of the specified Java class.Please refer to the declared classimplementation for details.


The cleanup method [{0}] raisedexception [{1}]. [{2}].



Activity input error. The activityrequired instance of class [{0}], butreceived a 'null' value for the declaredJava class.

Ensure that the correct Java objectreference is provided for the declaredJava class element shown in the inputtab of this activity.The precedingactivity that provides the input valuefor this activity should not produce anull for its output.


Activity input error. The activityreceived incorrect Java object for thedeclared Java class. The activityrequired an instance of a class [{0}],but received instance of a class [{1}].



Data Conversion error. Whenattempting to convert Java object toXML data encountered exception [{0}].

Ensure that unsupported data typesare not utilized or referenced in yourJava class.


Data Conversion error. Whenattempting to convert XML data toJava object encountered exception[{0}].

Ensure that unsupported data typesare not utilized or referenced in yourJava class.

68




Runtime error. Illegal onEvent(Objectoutput)/onError(Throwable error)method call. OnEvent/OnErrormethod must not be called in the initmethod or during the initializationphase.

Remove the onEvent(Object output)method call in the init method.


Runtime error. The output typedefined by the getOutputObjectType()does not match with the type that ispassed in to onEvent(Object object).


The Java Process Starter onstopmethod [{0}] raised exception [{1}].[{2}].

The exception was raised by the'onStop' method of the specified Javaclass. Please refer to the declared classimplementation for details.


The Java Process Starter onShutdownmethod [{0}] raised exception [{1}].[{2}].

The exception was raised by the'onShutdown' method of the specifiedJava class. Please refer to the declaredclass implementation for details.


Internal error occurred while loadingthe Class=[{0}], Cause=[{1}]


Internal error occurred. Method=[{0}]references a Class=[{1}] no longerexists. Cause=[{2}]

Make sure the Class referenced themethod is valid.


Activity input error. The activity doesnot receive proper input.

Ensure that the input content is notempty.


Unable to obtain information for themethod [{0}] from the class [{1}].


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 ofa JDBC Transaction Group. Howeverthe activity references the same sharedresource as used in the group


69




The JDBC activity [{0}] is first activityin the JDBC Transaction.



JDBC activity [{0}] initializedsuccessfully.



JDBC activity [{0}] task submitted toThreadpool for execution



Executing SQL Statement [{0}] foractivity [{1}].



Connection received from Datasourcefor activity [{0}].



Parameters set for activity [{0}] withsql statement [{1}].



Output for activity [{0}] is [{1}]. This is a debug message andresolution is not applicable.


Executing SQL Statement for activity[{0}].



Executing Prepared Statement foractivity [{0}].


Successfully executed sql statement[{0}] for activity [{1}].



Last subset reached for activity [{0}]. This is a debug message andresolution is not applicable.


Process in subset output for activity[{0}] with noofRecords [{1}] is [{2}].



All Parameters set successfully onStatement for activity [{0}].


70




Number of updates for JDBC Updateactivity is [{0}].



Number of updates for JDBC Updateactivity is 0. Executing InsertStatement [{0}] since activity is inUpsert mode.



Batch updates failed on updatenumber [{0}].

Check the activity configuration and ifthe database is up.


Invalid procedure name specified.Procedure name can not be null.

Check the activity configurationProcedure name field.


{0} input parameters declared in theSQL statement but no inputparameters provided.

Check the activity configurationPrepared Parameters table.


Duplicate field name [{0}] found.Modify the query and create uniquealiases for duplicate fields.

Modify the query and create uniquealiases for duplicate fields.


Improper SQL statement used. {0} Check the syntax of the SQLStatement specified.


Exception occurred occurred whenattempting to create a JDBCConnection for JDBC Transaction.

Check the Shared Resourceconfiguration this activity is configurewith and also that the database isrunning.


Missing Input Value for requiredColumn [{0}].

Check the input tab of the activity andset the column value


SQL Exception occurred (SQL STATE= {0}) - detailMessage - {1}

Check the activity configuration andthe state of the database the activity isconnected to.


{0} is not a valid timezone. Check the activity configuration inputtab and enter a valid timezone


Could not create Connection to serverusing Shared Resource [{0}].

Check the JDBC Connection SharedResource configuration which isconfigured on the activity.

71




INVALID_JDBC_ACTIVITY_CONFIGURATION = Invalid ActivityConfiguration. Missing requiredconfiguration Field [{0}] in activity[{1}]

Check the activity configuration andenter values for missing fieldsspecified in the message.


INVALID_SQL_STATEMENT =Invalid Activity Configuration.Invalid SQL Statement [{0}] in activity[{1}] expected a statement with [{2}]

Check the activity configuration forthe SQL statement syntax.


PREPARED_PARAMETERS_MORE_THAN_QUESTION_MARKS =Invalid Activity Configuration.Number of Prepared Parameters inactivity configuration exceed numberof '?' in SQL Statement

Check the activity configuration forthe Prepared Parameters specified.


PREPARED_PARAMETERS_LESS_THAN_QUESTION_MARKS = InvalidActivity Configuration. Number ofPrepared Parameters in activityconfiguration is less than number of '?'in SQL Statement

Check the activity configuration forthe Prepared Parameters specified.


BATCH_UPDATE_WITHOUT_PREPARED_PARAMS = Batch Updatemode works only with PreparedStatements

Check the SQL statement in theactivity configuration to ensure that itis a SQL statement with preparedparameters.


JDBC Connection login timed out. Check the configuration details orincrease the login timeout.

JMS Palette Error CodesThis section describes the error messages that can be reported by the activities or entities associatedwith the BusinessWorks Container Edition JMS palette.


TIBCO-BW-PALETTE-JMS-000001

{0}


{0}


{0}

72




{0}


{0}


Invalid configuration data. JMSconnection reference is not specified.

Check activity configuration for JMSConnection Reference.


Invalid configuration data. Specifiedconnection reference is not found inrepository. {0}

Check activity configuration for JMSConnection Reference.


Invalid configuration data. JMSdestination is not specified.

Check activity configuration for theJMS Destination field.


Error occurred when attempting tocreate Durable Subscriber

Check activity configuration for theDurable Subscription name box and ifJMS server is running.


Failed to create connection to the JMSserver. {0}

Check JMS Connection sharedresource configuration and if the JMSserver is running.


Unable to create a session to receivemessages [{0}].



Unable to create a reply session/producer [{0}]



Unable to find destination [{0}] on JMSserver

Check JMS Server if it the destinationname specified in the error messageexists.


Error occurred when attempting tocreate MessageConsumer



Error occurred when attempting toresolve destination [{0}]



Invalid configuration data. JMS ReplyTo Destination Not Specified.

Check the activity configuration andspecify a value in the JMS Reply Tofield.

73




Error occurred when attempting tosend a JMS message

Check the activity configuration,input data, JMS Connection sharedresource configuration and if the JMSserver is running.


Error occurred when attempting toreceive a JMS message

Check the activity configuration, JMSConnection shared resourceconfiguration and if the JMS server isrunning.


Error occurred when attempting toconfirm a JMS message

Check the activity configuration, JMSConnection shared resourceconfiguration and if the JMS server isrunning.


Failed to Reply for JMSProcessStarter[{0}]. This error canoccur if the JMSReply activity isexecuted after recovering from acheck-pointed BusinessWorks processinstance.

There is no resolution for this error.

Parse Palette Error CodesThis section describes the error messages that can be reported by the activities or entities associatedwith the ActiveMatrix BusinessWorks Parse palette.


TIBCO-BW-PALETTE-PARSE-000001










74




Cannot find data format schemaresource [{0}]

Check if Data format shared resourceis configured.


Cannot create schema from dataformat schema.

Check if the schema is valid.


Exception in parse eval: [{0}] An error occurred while processing,refer to the exception thrown andcorrect the activity configuration orinput.


Line length must be > 0 Check if line length is greater thanzero.


Hit EOF on row [{0}] field [{1}]spanning columns [{2}] to [{3}] .... lastrow contents was: [{4}]

Check the configuration of number ofrecords in input of Parse Data activity.It may be more than the recordspresent in the file.


Input type is not specified. Check configuration of Input type onParse Data activity. Ensure either Fileor String is configured.


Please specify the Input type field. Check configuration of Input type onParse Data activity. Ensure either Fileor String is configured.


Data format resource not specified. Check if Data format shared resourceis configured on the activity.


Specify the data format resource. Check if Data format shared resourceis configured on the activity.


File [{0}] cannot be opened usingencoding method [{1}]

Check the encoding configruation onParse Data activity. Ensure encodingsupported by file is selected.


[{0}] must be specified if [{1}] isselected.

Check the error and ensure that DataFormat shared resource configurationis correct.


Format Type must be selected. Ensure that Format type is configuredon Data Format shared resource.

75




Line is too long. Specified LineDelimiter may not match file content.

Check field offsets configuration onData Format shared resource.


There are not enough data for thenumber of required fields in a row.

Check field offsets configuration onData Format shared resource.


Error while parsing headers in themime message.

Ensure that the input message hasMIME headers.


An I/O exception occurred whileparsing SOAP payload in the rootpart.

Ensure that the SOAP payload is wellformed and valid.


An Unexpected exception occurredwhile parsing Message. Root cause is[{0}]

UNEXPECTED_EXCEPTION.resolution =This is an internal product error.Contact TIBCO Support


The SOAP Message doesn't exist inthe Root part.

Ensure that the input message hasSOAP payload in it.


Soap Envelope has invalid XMLcontent.

Ensure that the SOAP payload is validand well formed.


One or more mime parts have sameContent-Id value in the MimeMessage.

Ensure that in input message does nothave same content id for differentmime parts.


The xop:Include element must havean 'href' attribute.

Ensure that in the SOAP payload, thexop:Include element has hrefattribute.


Content_Id header is not found inmime part of the Mime Message.

Ensure that the each mime part hascontent-id header and correspondingvalue.


Invalid Content Type Field in theMime Message.

Ensure that media type starts with'multipart'.


Boundary attribute not found in theMime Message.

Ensure that the 'boundary' attribute isnot missing in the mime header.


startinfo parameter is missing in theMime Message.

Ensure that 'startinfo' attribute ispresent in the mime header.

76




startinfo parameter is not startingwith 'application/soap+xml' in theMime Message.

Ensure that startinfo attribute has'application/soap+xml' as value.


Content Type header is not found inthe Mime Message.

Ensure that the mime message has'content-type' header.


Media type of root part is not'application/xop+xml' in the MimeMessage.

Ensure that the root part's media typeis 'application/xop+xml'


'type' parameter is not present in rootpart of the Mime Message.

Ensure that the root part has 'type'parameter.


startInfo parameter and typeparameter,of root part, does not matchin the Mime Message.

Ensure that the value of startInfoparameter and type parameter is samein the root part of the Mime Message.

XML Palette Error CodesThis section describes the error messages that can be reported by the activities or entities associatedwith the BusinessWorks Container Edition XML palette.


TIBCO-BW-PALETTE-XML-000001

[{0}] This is an internal product error.Contact TIBCO Support.


[{0}] This is a trace message and resolutionis not applicable.


[{0}] This is a debug message andresolution is not applicable.


[{0}] This is an informational message andit highlights the runtime progress ofthe activity. Resolution is notapplicable.


[{0}] This is a warning message and ithighlights situations that may affectthe activity execution.


Internal error occurred Class=[{0}],Method=[{1}], Reason=[{2}].

Please Contact TIBCO Support

77




Unable to serialize the XML due toexception [{0}].

Ensure the input XML node isproperly given.


Unable to parse the XML due toexception [{0}].

Ensure the provided input XML iswell formed and valid.


Exception [{0}] occurred during XSLTtransformation. Exception detail [{1}].

Ensure the provided input XML andinput XSLT is properly given.


The XSLT transformation Stylesheetprovided for the activity input isempty or null.

Ensure to provide the XSLT either inthe configuration or in the activityinput.


The selected encoding [{0}] is notvalid.

Ensure the provided encoding isvalid.


Encountered encoding error [{0}]. Ensure the provided encoding iscorrect.


The encoded bytes content is empty. Ensure that the input content is notempty.


Encountered error [{0}] while trying todetect the encoding from the XML.

Ensure the provided input bytecontent is correct.


Activity input error. The activity doesnot receive proper input.

Ensure that the input content is notempty.

78


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.

Error Codes Error Message

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.

79


Error Codes Error Message


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-200001


TIBCO-BW-SR-DATAFORMAT-500000

Failed to {0} Data Format resource[{1}]

Check the configuration of DataFormat shared resource.

HTTP Client Error CodesThis section describes the error messages that can be reported by the HTTP Client shared resource.


TIBCO-BW-SR-HTTP-CLIENT-200001



Failed to {0} HTTP Client resource[{1}]

Check the configuration of Http Clientresource.


User name or Password is notspecified in Identity

Specify user name and password inIdentity shared resource.

80




User name or Password is not set inidentity resource for basic Httpauthentication

Check if user name and password isspecified in Identity shared resource.

HTTP Connector Error CodesThis section describes the error messages that can be reported by the HTTP Connector shared resource.


TIBCO-BW-SR-HTTP-CONNECTOR-100001





Error while stopping HTTP endpoint[{0}]

This is an informational message andit highlights the runtime progress ofthe shared resource. Resolution is notapplicable.


Error while stopping HTTP context[{0}]



Failed to {0} HTTP Connector resource[{1}]

Check the configuration of HttpConnector resource.


Failed to create HTTP Connectorresource [{0}] with the specifiedconfiguration. Check theconfiguration settings.



Unable to start HTTP Server instancefor resource [{0}]



Failed to activate HTTP endpoint [{0}]because of exception [{1}]

Check the exception and correct theconfiguration of Http Connectorresource or Http Event source.

81




The HTTP server instance cannot bestarted, because it is not configured

Check the configuration of HttpConnector resource or Http Eventsource.


The HTTP server instance [{0}]occurred an error when stopped

System exception.


Failed to deactivate HTTP endpoint[{0}]

System exception.


Failed to get URL for HTTP endpoint[{0}]

Check the host and port configurationon Http Connector resource.


Unable to find Application bundle[{0}]

System exception.


Failed to create HTTP Connectorresource [{0}] configured with port[{1}]

Check the port configured on HttpConnector resource is not in use.


LDAP resource is not configured onHTTP Connector resource [{0}].

Please check if LDAP resource isconfigured on Http Connector.

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

BW6_EXCP_NAME_EXISTS = Aconnector configuration with thename "[{0}" already exists with pid[{1}]



Unable to find Application bundle[{0}]


82




Unable to construct an instance of theJava class [{0}]. Encountered exception[{1}] [{2}].



Activity input error. The activityreceived an incorrect value for themethod parameters.IllegalArgumentException occurredwhile trying to construct an instanceof the Java class [{0}]: [{1}]

Ensure that the correct values areprovided for the constructorparameter elements that are in theactivity input tab.


The constructor for the Java class [{0}]raised exception [{1}]. [{2}]

The exception was raised by theconstructor of the declared Java class.Please refer to the Java classimplementation for details.


The Java class [{0}] is not found in theclasspath. EncounteredClassNotFoundException [{1}].

Ensure that the specified class file iscontained in the classpath.


Unable to obtain information for themethod [{0}] from the class [{1}].EncounteredNoSuchMethodException [{2}].



Unable to obtain information for thecleanup method [{0}] from the class[{1}]. NoSuchMethodExceptionoccurred. [{2}]



The cleanup method [{0}] raisedexception [{1}]. [{2}]



Unable to invoke the cleanup method[{0}]. Exception [{1}] occurred. [{2}]



Unable to invoke the cleanup method[{0}]. Encountered exception [{1}] [{2}].



Received an incorrect value for themethod [{0}] parameter to get accessthe BW Module properties. Exceptionoccurred: [{1}]

Ensure that the correct values areprovided for the method parameter toget access the BW Module properties.



83




Failed to {0} Java Global Instanceresource [{1}]


Delete Called on configuration thatdoes 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-100001

{0}


{0}


{0}


{0}


Failed to {0} JMS Connection resource[{1}]

Check JMS Connection Sharedresource configuration

JDBC Connection Error CodesThis section describes the error messages that can be reported by the JDBC Connection shared resource.


TIBCO-BW-SR-JDBC-300001

Received an update request forexisting configuration with PID=[{0}]and Shared resource name [{1}]



Updating Password for SharedResource with PID[{0}] and name[{1}]



Updating Username for SharedResource with PID[{0}] and name[{1}]


84




Updating Database URL[{0}] forShared Resource with PID[{1}] andname[{2}]



Ignoring Hot Update for configurationwith PID=[{0}] and name[{1}].Unsupported parameters updated.Only Username, Password and URL issupported



Adding new configuration for SharedResource with name [{0}]



Deleting Configuration for SharedResource with name[{0}]



Following Drivers have been loadedin the framework[{0}]. FollowingShared Resource Configurations havebeen deployed before these driverswere loaded [{1}].



Exception occurred while closing abad connection with [VendorErrorCode:{0}] and SQL STATE[{1}]

This is a warning message and doesnot a. A JDBC connection was markedinvalid by the driver and wasremoved from the pool. Thisconnection could not be closedsuccessfully.


Maximum permitted Connectionsreached. Cannot create newconnection. Waiting for a connectionto be available.

This is a warning message. The JDBCConnection Pool has reached ismaximum limit specified by the user.Jobs created will wait for a connectionto be available before proceeding.Increasing the max connections to asuitable value for the application willsolve this issue.


No suitable DataSourcefactory foundfor driver [{0}]. The shared resource{1} might NOT resolve. Theconfiguration will wait for a driver tobe available.

This is a warning message. Thismessage prints out information abouta driver not being loaded at thecurrent time. Since the framework hasnot finished loading, there is a chanceof the driver being loaded later. It issafe to ignore this message.

85




Failed to {0} JDBC Connectionresource [{1}].

A JDBC Connection lifecycle error hasoccurred. Check the connectionconfiguration and restart theapplication if necessary.


Exception occurred while trying toretrieve a connection from the JDBCConnection pool

Check the connection configurationand if the database is up and running.


Failed to create a new connection todatabase server. Database URL [{0}],UserName [{1}], SQLSTATE [{2}]

Check the connection configurationand if the database is up and running.


The database driver [{0}] is not found.Ensure that DataSourceFactorybundle providing this driver isavailable in the environment.

Run the appropriate script usingbwinstall from the bin folder to addthe JDBC driver to the runtimeenvironment


Destroying all Unused connections. This is a debug message andresolution is not applicable.


Published Event to Event Admin ontopic {0}



Delete Called on configuration thatdoes 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-100001

{0}


{0}


{0}


{0}


Failed to {0} JNDI Configurationresource [{1}]

Check JNDI Configuration sharedresource configuration.

86


Proxy Configuration Error CodesThis section describes the error messages that can be reported by the Proxy Configuration sharedresource.


TIBCO-BW-SR-HTTP-PROXY-200001


TIBCO-BW-SR-HTTP-PROXY-500000

Failed to {0} Proxy Configurationresource [{1}]

Check the configuration of Proxyshared resource.

87


Date post:	29-Mar-2018
Category:	Documents
Upload:	ngothien
View:	564 times
Download:	13 times

TIBCO BusinessWorks Container Edition Error Codes · PDF fileAll other product and company...

Documents