TIB Bwce 2.6.2 Error Codes

TIBCO BusinessWorks™
Container Edition
Error Codes
Version 2.6.2
May 2021
Copyright © 2015-2021. TIBCO Software Inc. All Rights Reserved.

2 | Contents
Contents
Contents 2
Message Codes Naming Convention 4
Bindings 6
SOAP Binding Error Codes 6
REST Binding Error Codes 18
Core 23
Engine Error Codes 23
Design Time Error Codes 103
Palettes 106
File Palette Error Codes 106
FTP Palette Error Codes 109
General Palette Error Codes 111
HTTP Palette Error Codes 113
Java Palette Error Codes 117
JDBC Palette Error Codes 124
JMS Palette Error Codes 129
Mail Palette Error Codes 132
Parse Palette Error Codes 136
TCP Palette Error Codes 141
XML Palette Error Codes 143
Shared Resources 146

Shared Resource Framework Error Codes 146
Data Format Error Codes 148
FTP Connection Error Codes 148
HTTP Client Error Codes 149
TIBCO BusinessWorks™ Container Edition Error Codes

3 | Contents
HTTP Connector Error Codes 149

Java Global Instance Error Codes 152
JMS Connection Error Codes 154
JDBC Connection Error Codes 155
JNDI Configuration Error Codes 158
Proxy Configuration Error Codes 158
SMTP Resource Error Codes 159
TCP Connection 160
TIBCO Documentation and Support Services 161
Legal and Third-Party Notices 163

4 | Message Codes Naming Convention
Message Codes Naming Convention

Product execution errors, warnings, and information are reported through detailed log
messages that can help trace the cause of the issue. These messages follow a naming
convention that indicates the component and log level for each message. The log levels
allow you to capture different granularity of messages 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 a numerical 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 BusinessWorks Container Edition Palette specific

Name> activity
TIBCO-BW-SR BusinessWorks Container Edition Shared Resource

API layer
TIBCO-BW-SR-<UniqueName> BusinessWorks Container Edition specific Shared

Resource

5 | Message Codes Naming Convention
TIBCO-BW-STATS BusinessWorks Container Edition Stats Collector
TIBCO-THOR-FRWK Thor Framework
Note: 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.
The message describes the issue. Sometimes, the message can contain parameters
shown as ({N}), where N is an integer.

6 | Bindings
Bindings
This section describes the error messages that can be reported by the SOAP and REST
Binding types.
SOAP Binding Error Codes

This section describes the error messages that can be reported by the SOAP Binding.
Error Codes Error Message Error Resolution
TIBCO-BW- SOAP BindingFactory is initialized with This is a internal resolution

BINDING- incorrect BindingConfiguration for the message. Resolution not
SOAP- SOAP Service Binding. required.
001010
TIBCO-BW- Failed to obtain HTTP Connector resource This is an internal product

BINDING- for SoapServiceBinding [{0}], Application error. Contact TIBCO support.
SOAP- [{1}:{2}]
001020
TIBCO-BW- Failed to obtain HTTP Connector resource This is an internal product

BINDING- for SoapServiceBinding [{0}], Application error. Contact TIBCO support.
SOAP- [{1}:{2}]
001030
TIBCO-BW- SOAP BindingFactory is initialized with This is a internal resolution

BINDING- incorrect BindingConfiguration for the message. Resolution not
SOAP- SOAP Reference Binding. required.
001031
TIBCO-BW- Failed to parse binding meta data file [{0}] Ensure that the xml file
BINDING- in bundle [{1}] due to exception [{2}]. contents are valid and well
SOAP- formed.
001040

7 | Bindings
TIBCO-BW- Failed to process File [{0}] in bundle [{1}]. Ensure that the 'name'
BINDING- BindingName is not specified. attribute of the service
SOAP- element contains a unique
001050 Binding Name.
TIBCO-BW- Failed to process File [{0}] in bundle [{1}]. Ensure that Binding Name of
BINDING- A Binding with name [{2}] is already the SOAP Interceptor is
SOAP- registered. unique and it does not match
001060 with any Binding Name
(service/reference) in the
Application Module
TIBCO-BW- Failed to deploy the SOAP Interceptor Ensure that the SOAP
BINDING- Module [{0}], due to exception [{1}]. Root Interceptor deployed follows
SOAP- exception message is [{2}]. the Axis2 Module protocol.
001070
TIBCO-BW- Failed to initialize SOAP Binding. Binding BW_SOAP_BINDING_

BINDING- Name is not specified. NAME_MISSING_
SOAP- ERROR.resolution = Make
001080 sure all Bindings in the
application Module have a
Name.
TIBCO-BW- Failed to initialize SOAP Binding. Binding Make sure the Binding in the
BINDING- Name is not specified for port [{0}]. application Module has a
SOAP- Name.
001081
TIBCO-BW- Failed to initialize SOAP Binding. This is an internal product

BINDING- Application Name is not available. error. Contact TIBCO support.
SOAP-
001090
TIBCO-BW- Failed to initialize SOAP Binding. This is an internal product

BINDING- Application Version is not available. error. Contact TIBCO support.
SOAP-

8 | Bindings
001100
TIBCO-BW- Failed to locate WSDL definition for port Ensure that the a WSDL exist
BINDING- type [{0}]. with port type [{0}] in the
SOAP- application module.
001130
TIBCO-BW- MEP [{0}] is not supported. Review the Ensure that the MEP definition
BINDING- WSDL definition for Port type [{1}]. for Port type [{1}] is either IN-
SOAP- OUT OR IN-ONLY
001140
TIBCO-BW- Failed to recognize the MEP for Port type Ensure that the MEP definition
BINDING- [{0}]. for Port type [{0}] is either IN-
001150
TIBCO-BW- Failed to find message receiver for MEP Ensure that the MEP definition
BINDING- [{0}] for port type [{1}]. for Port type [{1}] is either IN-
001160
TIBCO-BW- SOAP Binding [{1}] for portType [{0}] is Ensure that the SOAP Binding
BINDING- missing Transport Configuration. [{1}] for port type [{0}] is
SOAP- configured with a Transport.
001170
TIBCO-BW- Operation Configuration for Operation Ensure that SOAP Binding

BINDING- [{0}], Port Type [{1}], SOAP Binding [{2}] is [{2}] is in sync with WSDL.
SOAP- missing. Ensure that SOAP Binding [{2}] is
001180 in sync with WSDL
TIBCO-BW- Failed to initialize SOAP Service Binding This is an internal product

BINDING- [{0}]. Promoted Name for the Binding is error. Contact TIBCO support.
SOAP- missing.
001110

9 | Bindings
TIBCO-BW- Failed to initialize SOAP Reference This is an internal product

BINDING- Binding [{0}]. Promoted Name for the error. Contact TIBCO support.
SOAP- Binding is missing.
001120
TIBCO-BW- Failed to load WSDL definition for Make sure the WSDL with
BINDING- namespace [{0}]. namespace [{0}] exists in the
SOAP- application module.
001130
TIBCO-BW- Malformed MIME Message received. Ensure that the MIME

BINDING- Failed to parse the attachments in the Message is well formed with
SOAP- received message for Operation [{0}], correct mime boundaries.
500009 SoapBinding [{1}], Application [{2}:{3}].
Ignoring the attachments from the SOAP
Message.
TIBCO-BW- Failed to create SoapServiceBinding [{0}], This is a internal resolution

BINDING- Application [{1}:{2}] due to exception [{3}] message. Resolution not
SOAP- required.
500010
TIBCO-BW- Unable to parse model version of the Ensure the SOAP Model
BINDING- SOAP Binding. version in .bwm file is of
SOAP- format [0-9].[0-9].[0-9]
500011
TIBCO-BW- Failed to initialize SoapServiceBinding Ensure that the configuration

BINDING- [{0}], Application [{1}:{2}] due to exception and context mapping. if any,
SOAP- [{3}] done on SoapServiceBinding
500020 [{0}] are correct.
TIBCO-BW- Failed to add transport dependency for Ensure that the

BINDING- SoapServiceBinding [{0}], Application [{1}: SoapServiceBinding [{0}] is
SOAP- {2}] configured with a Shared
500030 Transport Resource.

10 | Bindings
TIBCO-BW- Failed to initialize SoapServiceBinding Ensure that each SOAP/HTTP

BINDING- [{0}]. A Service Endpoint URI [{1}] is service has unique URL.
SOAP- already registered
500040
TIBCO-BW- Failed to initialize SoapServiceBinding Ensure that the combination of

BINDING- [{0}]. The operation [{1}] with soapaction "Soap Action" and
SOAP- [{2}] is already registered for destination "MessageStyle:Destination"
500050 [{3}] with Message Style [{4}]. should be unique.
TIBCO-BW- Failed to send SOAP Fault message to This is an internal product

BINDING- the consumer of the service for Operation error. Contact TIBCO support.
SOAP- [{0}], SoapServiceBinding [{1}], Application
500060 [{2}:{3}] due to exception [{4}]. Root
Exception message: {5}
TIBCO-BW- Failed to process Reply message for Ensure that the Binding
BINDING- Operation [{0}], SoapServiceBinding [{1}], configuration and Context
SOAP- Application [{2}:{3}] due to exception [{4}]. Configuration, if any, done on
500070 Sending Undeclared Fault message to the SoapServiceBinding [{1}] are
consumer of this service. Root Exception correct.
message: [{5}]
TIBCO-BW- Error occurred while processing Service Ensure that the Context
BINDING- Request messages Context Information Mapping done on
SOAP- for Operation [{0}], SoapServiceBinding SoapServiceBinding [{1}] are
500080 [{1}], Application [{2}:{3}] due to exception correct.
[{4}]. Root Exception message: {5}
TIBCO-BW- Error occurred while processing Service Ensure that the Message part
BINDING- Request message for Operation [{0}], configuration and header
SOAP- SoapServiceBinding [{1}], Application [{2}]: configuration, if any, done on
500090 {3}] due to exception [{4}]. Root Exception SoapServiceBinding [{1}] are
message: {5} correct.

11 | Bindings
SOAP- SoapServiceBinding [{1}], Application [{2}: configuration, if any, done on

500100 {3}] due to exception [{4}]. Sending SoapServiceBinding [{1}] are
Undeclared Fault message to the correct.
consumer of this service. Root Exception
message: {5}
SOAP- SoapServiceBinding [{1}], Application [{2}: configuration, if any, done on
500105 {3}] due to exception [{4}].Root Exception SoapServiceBinding [{1}] are
message: {5} correct.
TIBCO-BW- Failed to process Declared Fault Message Ensure that the Context
BINDING- for Operation [{0}], SoapServiceBinding Mapping and configuration
SOAP- [{1}], Application [{2}:{3}] due to exception done on SoapServiceBinding
500110 [{4}]. Sending Undeclared Fault message [{1}] are correct.
to the consumer of this service. Root
Exception message: {5}.
TIBCO-BW- The BusinessWorks ProcessService Ensure that the BW Process

BINDING- implementation failed to complete the construct is correct.
SOAP- request for the Operation [{0}],
500120 SoapServiceBinding [{1}], Application [{2}:
{3}] and returned exception [{4}]. Sending
Undeclared Fault message to the
message: {5}.
TIBCO-BW- Unable to populate SOAP Binding This is an internal product

BINDING- Configuration due to exception [{1}] error. Contact TIBCO support.
SOAP-
500130
TIBCO-BW- An Error occurred while cleaning up the This is an internal product

BINDING- SOAP Binding Configuration Resources error. Contact TIBCO support.
SOAP- due to exception [{1}]
500131

12 | Bindings
TIBCO-BW- An interrupted fault occurred while waiting This is an internal product

BINDING- for the Service Request message to be error. Contact TIBCO support.
SOAP- processed for Operation [{0}],
500140 SoapServiceBinding [{1}], Application [{2}:
{3}] due to exception [{4}]. Sending
Undeclared Fault message to the
message: {5}
TIBCO-BW- Failed to start SoapServiceBinding [{0}], Ensure that the Transport

BINDING- Application [{1}:{2}] due to exception [{3}] Configuration done on
SOAP- SoapServiceBinding [{0}] are
500150 correct.
TIBCO-BW- Failed to stop SoapServiceBinding [{0}], This is an internal product

BINDING- Application [{1}:{2}] due to exception [{3}] error. Contact TIBCO support.
SOAP-
500160
TIBCO-BW- Error occurred while processing Service Ensure that the Context
BINDING- Request messages Context information Mapping and configuration
SOAP- for Operation [{0}], SoapServiceBinding done on SoapServiceBinding
500170 [{1}], Application [{2}:{3}] due to exception [{1}] are correct.
[{4}]. Sending Undeclared Fault message
to the consumer of this service. Root
Exception message: {5}
TIBCO-BW- Failed to start JMS transport primitive for This is an internal product
BINDING- SoapServiceBinding [{0}], Application [{1}: error. Contact TIBCO support.
SOAP- {2}] due to exception [{3}]
500190
TIBCO-BW- Failed to stop JMS transport primitive for This is an internal product
BINDING- SoapServiceBinding [{0}], Application [{1}: error. Contact TIBCO support.
SOAP- {2}] due to exception [{3}]
500200

13 | Bindings
TIBCO-BW- Failed to Initialize JMS transport primitive Ensure that the transport
BINDING- for SoapServiceBinding [{0}], Application configuration done on
SOAP- [{1}:{2}] due to exception [{3}] SoapServiceBinding [{0}] are
500210 correct.
TIBCO-BW- Failed to read incoming JMS raw message This is an internal product
BINDING- due to exception [{0}]; error. Contact TIBCO support.
SOAP-
500230
TIBCO-BW- Failed to create JMS Reply Handler for Ensure that the transport
BINDING- SoapServiceBinding [{0}], Application [{1}: configuration done on
SOAP- {2}] due to exception [{3}] SoapServiceBinding [{0}] are
500240 correct.
TIBCO-BW- Failed to process service request Ensure that the Service

BINDING- message for SoapServiceBinding [{0}], Provider is sending a correct
SOAP- Application [{1}:{2}] due to exception [{3}] SOAP Envelope.
500250 .Root exception message : [{4}]
TIBCO-BW- Failed to send Service Reply message for This is an internal product
BINDING- Operation [{0}], SoapServiceeBinding error. Contact TIBCO support.
SOAP- [{1}], Application [{2}:{3}] due to exception
500260 [{4}]
TIBCO-BW- Failed to acknowledge Service Request This is an internal product

BINDING- message for Operation [{0}], error. Contact TIBCO support.
SOAP- SoapServiceBinding [{1}], Application [{2}:
500270 {3}] due to exception [{4}]
TIBCO-BW- Failed to authenticate Request message Check if the identity resource

BINDING- for Operation [{0}], SoapServiceBinding referenced in Http Client
SOAP- [{1}], Application [{2}:{3}] due to exception resource contains username
500280 [{4}]. and password.
TIBCO-BW- Failed to authenticate Request message Check if the identity resource

BINDING- for Operation [{0}], SoapServiceBinding referenced in Http Client

14 | Bindings
SOAP- [{1}], Application [{2}:{3}]. Username and resource contains username

500281 Password is not set. and password.
TIBCO-BW- Failed to authenticate Request message This is an internal product

BINDING- for Operation [{0}], SoapServiceBinding error. Contact TIBCO support.
500290 [{4}].
TIBCO-BW- Malformed SOAP Request message Check if the SOAP Request

BINDING- received for Operation [{0}], Message is well formed.
SOAP- SoapServiceBinding [{1}], Application [{2}:
500300 {3}]. Root Exception message: [{5}]
TIBCO-BW- Failed to create SoapReferenceBinding This is an internal product

BINDING- [{0}], Application [{1}:{2}] due to exception error. Contact TIBCO support.
SOAP- [{3}]
550010
TIBCO-BW- Failed to create SoapReferenceEndpoint Ensure that configurations

BINDING- [{0}] due to exception [{1}] done on Reference Binding
SOAP- [{0}] are correct.
550020
TIBCO-BW- Failed to initialize SoapReferenceBinding Ensure that the Binding and

BINDING- [{0}], Application [{1}:{2}] due to exception Transport configuration on
SOAP- [{3}] SoapReferenceBinding [{0}]
550030 are correct.
TIBCO-BW- Failed to add transport dependency for This is an internal product

BINDING- SoapReferenceBinding [{0}], Application error. Contact TIBCO support.
SOAP- [{1}:{2}]
550040
TIBCO-BW- Failed to destroy SoapReferenceBinding This is an internal product

BINDING- [{0}], Application [{1}:{2}] due to exception error. Contact TIBCO support.
SOAP- [{3}]
550050

15 | Bindings
TIBCO-BW- Failed to release transport resources for This is an internal product

BINDING- Operation [{0}], SoapReferenceBinding error. Contact TIBCO support.
550060 [{4}]
TIBCO-BW- Received Declared Fault. Failed to This is an internal product

BINDING- release transport resources for Operation error. Contact TIBCO support.
SOAP- [{0}], SoapReferenceBinding [{1}],
550070 Application [{2}:{3}] due to exception [{4}]
TIBCO-BW- Unable to receive response from the This is an internal product

BINDING- service provider for Operation [{0}], error. Contact TIBCO support.
SOAP- SoapReferenceBinding [{1}], Application
550090 [{2}:{3}] due to exception [{4}]
TIBCO-BW- Received SOAP Fault from the service This is an internal message
BINDING- provider of the Operation [{0}], sent to the framework for
SOAP- SoapReferenceBinding [{1}], Application server error. Resolution not
550100 [{2}:{3}]. SOAP Fault received: [{4}] required.
TIBCO-BW- Received SOAP Fault from the service This is an internal message
BINDING- provider of the Operation [{0}], sent to the framework for
SOAP- SoapReferenceBinding [{1}], Application client error. Resolution not
550101 [{2}:{3}]. SOAP Fault received: [{4}] required.
TIBCO-BW- Error occurred while processing the Ensure that the declared fault
BINDING- declared fault message from the service send back by the Service
SOAP- provider of the Operation [{0}], Provider is valid and well
550110 SoapReferenceBinding [{1}], Application formed SOAP Fault.
[{2}:{3}] due to exception [{4}]
TIBCO-BW- Error occurred while processing reply Ensure that Message Part and
BINDING- message from the service provider of the Header Configuration done on
SOAP- Operation [{0}], SoapReferenceBinding SoapReferenceBinding [{1}]
550120 [{1}], Application [{2}:{3}] due to exception are correct.
[{4}]

16 | Bindings
TIBCO-BW- SOAPEnvelope must contain a body Ensure that Service Provider

BINDING- element which is either first or second has send a valid SOAP
SOAP- child element of the SOAPEnvelope. Envelope.
550121
TIBCO-BW- Error occurred while processing reply Ensure that Context

BINDING- message attachments from the service configuration and Mapping for
SOAP- provider of the Operation [{0}], the attachment done on
550130 SoapReferenceBinding [{1}], Application SoapReferenceBinding [{1}] is
[{2}:{3}] due to exception [{4}] correct.
TIBCO-BW- Failed to Initialize JMS transport primitive Ensure that the Transport
BINDING- for SoapReferenceBinding [{0}], Sender configurations are
SOAP- Application [{1}:{2}] due to exception [{3}] correct.
550140
TIBCO-BW- Failed to send Reference Request Ensure that the Message

BINDING- message for Operation [{0}], Configuration done on
SOAP- SoapReferenceBinding [{1}], Application SoapReferenceBinding [{1}]
550170 [{2}:{3}] due to exception [{4}] are correct.
TIBCO-BW- Failed to process reply message from the Ensure that the Message
BINDING- service provider of the Operation [{0}], Configuration done on
SOAP- SoapReferenceBinding [{1}], Application SoapReferenceBinding [{1}]
550180 [{2}:{3}] due to exception [{4}] are correct
TIBCO-BW- Failed to update HTTP Transport Ensure that the port number
BINDING- configurations before sending the configuration for
SOAP- Reference Request message for SoapReferenceBinding [{1}] is
550190 Operation [{0}], SoapReferenceBinding valid
[{1}], Application [{2}:{3}] due to exception
[{4}].
TIBCO-BW- Failed to create the HTTP Client required Ensure that the Endpoint URL
BINDING- for sending the Reference Request is in correct format.
SOAP- message for Operation [{0}],
550210 SoapReferenceBinding [{1}], Application

17 | Bindings
[{2}:{3}] due to exception [{4}]
TIBCO-BW- Failed to serialize JMS transport message Ensure that the configuration
BINDING- due to exception [{1}]. done on Reference Binding
SOAP- are correct.
550220
TIBCO-BW- Failed to convert JMS message to string Ensure that the configuration
BINDING- due to exception [{1}]. done on Reference Binding
SOAP- are correct.
550230
TIBCO-BW- Failed to create Endpoint URL for Ensure that the Endpoint URI
BINDING- Operation [{0}], SoapReferenceBinding configuration on
SOAP- [{1}], Application [{2}:{3}] due to exception SOAPRefernceBinding [{1}] is
550240 [{4}] correct.
TIBCO-BW- Unable to receive response from the Ensure that the Service
BINDING- service provider for Operation [{0}], Provider is available.
555000 [{2}:{3}] due to exception [{4}]. Message
Received: [{5}]
TIBCO-BW- Unable to receive response from the Ensure that HTTP Client
BINDING- service provider for Operation [{0}], configurations are configured
SOAP- SoapReferenceBinding [{1}], Application as per service provider
555010 [{2}:{3}] due to exception [{4}]. Message requirements.
Received: [{5}]
TIBCO-BW- Unable to receive response from the Ensure that HTTP Client
BINDING- service provider for Operation [{0}], configurations are configured
Received: [{5}]
TIBCO-BW- Unable to send request the service Ensure that HTTP Client
BINDING- provider for Operation [{0}], configurations are configured

18 | Bindings

Received: [{5}]
TIBCO-BW- Unable to send request the service Ensure that the COOKIE
BINDING- provider for Operation [{0}], format is correct.
555040 [{2}:{3}] due to exception [{4}]. Message
Received: [{5}]
REST Binding Error Codes

This section lists the error messages that can be reported by the REST Binding.
TIBCO-BW- Creating REST Resource with HTTP This is a debug message and
BINDING- Connector Name [{0}] at Resource Path: resolution is not applicable.
REST- [{1}]
200001
TIBCO-BW- Creating REST Resource for conflicting This is a debug message and
BINDING- path spec resolution is not applicable.
REST-
200002
TIBCO-BW- Adding REST operation [{0}] with HTTP This is a debug message and
BINDING- Method[{1}] for [{2}] at resource path [{3}] resolution is not applicable.
REST-
200003
TIBCO-BW- Request Received for Operation [{0}] This is a debug message and
BINDING- resolution is not applicable.
REST-
200004

19 | Bindings
TIBCO-BW- Invoking BW Endpoint [{0}] for Operation This is a debug message and
BINDING- [{1}] resolution is not applicable.
REST-
200005
TIBCO-BW- BW Endpoint [{0}] for Operation [{1}] has This is a debug message and
BINDING- been invoked. Waiting for Reply to be resolution is not applicable.
REST- generated
200006
TIBCO-BW- Response generated. Responding to This is a debug message and

BINDING- request resolution is not applicable.
REST-
200007
TIBCO-BW- Payload for Request is [{0}] This is a debug message and

REST-
200008
TIBCO-BW- Creating XML Message for JSON This is a debug message and
BINDING- Message. Element details - resolution is not applicable.
REST- targetnamespace [{0}] and name is [{1}]
200009
TIBCO-BW- Destroying REST Binding with pathspec This is a debug message and
BINDING- [{0}] and binding name [{1}] resolution is not applicable.
REST-
200010
TIBCO-BW- JSON-> XML Conversion Result: \n {0} This is a debug message and
REST-
200011
TIBCO-BW- REST Binding Authentication is enabled.

BINDING- Trying to authenticate using the

20 | Bindings
REST- Authorization Header of the request

200012
TIBCO-BW- Expected JSON Content-Type. Got XML The Client needs to be notified
BINDING- Instead. Replying with error to client to use the right Content-Type
REST- Header or the binding
400001 configuration can be changed
to allow multiple content-types
TIBCO-BW- Expected XML Content-Type. Got JSON The Client needs to be notified
BINDING- Instead. Replying with error to client to use the right Content-Type
REST- Header or the binding
400002 configuration can be changed
to allow multiple content-types
TIBCO-BW- Binding Configuration is not for a REST Check configuration of the

BINDING- Service Binding REST binding
REST-
500001
TIBCO-BW- NO_RESOURCE_URL_SPECIFIED = Check configuration of the

BINDING- No relative resource url specified to REST binding for the value of
REST- deploy REST Resource the Resource URL field.
500002
TIBCO-BW- Unable to create REST resource for Check both binding

BINDING- binding [{0}]. Reason - Unable to stop configurations specified in the
REST- conflicting binding [{1}]. error message for the Resource
500003 URL fields
TIBCO-BW- Error Occurred while trying to create Check configuration of the

BINDING- Jersey REST Resource for binding [{1}] REST binding specified in the
REST- error message
500004
TIBCO-BW- Unable to start REST Binding with name Check configuration of the
BINDING- [{0}] REST binding specified in the

21 | Bindings
REST- error message

500004
TIBCO-BW- Unable to stop REST Binding with name Check configuration of the
BINDING- [{0}} REST binding specified in the
REST- error message
500005
TIBCO-BW- Error Occurred while parsing and Invalid values were sent by the
BINDING- creating HTTP Headers. Responding to client in the HTTP headers.
REST- client with error message.
500006
TIBCO-BW- Error Occurred while creating Invalid values were passed for
BINDING- Parameters Part. Responding to client the Parameters element. Check
REST- with error message. the client request and the
500007 configuration of the REST
Binding.
TIBCO-BW- Error Occurred while creating User Part. Invalid values were passed for
BINDING- Responding to client with error message. the Parameters element. Check
REST- the client request and the
500008 configuration of the REST
Binding.
TIBCO-BW- The HTTP Connector failed to deploy the Check the HTTP Connector
BINDING- REST Service Binding. Check the exception for possible reasons
REST- exception thrown by the HTTP Connector of failure. For example, Some
500009 for possible configuration issues of them could be related to
overlapping context paths or an
address in use.
TIBCO-BW- The HTTP Connector [{0}] shared

BINDING- resource could not be retrieved. Please
REST- check the REST Binding configuration or
500010 the logs if the HTTP Connector could not
be started.

22 | Bindings
TIBCO-BW- The HTTP Connector [{0}] shared

BINDING- resource could not be retrieved. Please
REST- check the REST Binding configuration or
500011 the logs if the HTTP Connector could not
be started.
TIBCO-BW- AUTHENTICATION_FAILED =
BINDING- Authentication failed for client request. A
REST- 401 status code has been sent to the
500012 client with the realm as [{0}].
TIBCO-BW- WSDL_CACHE_NOT_FOUND = An
BINDING- error occurred while trying to retrieve the
REST- WSDL/XSD's for the REST binding [{0}].
500013 Please check the underlying exception
thrown by the WSDL/XSD Cache for the
root cause.
TIBCO-BW- No WSDL Operation found. Please re- This is an internal product error.
BINDING- validate the application module and try Contact TIBCO Support.
REST- deploying again.
000001

23 | Core
Core
This section lists the error codes returned by the core components such as runtime.
Engine Error Codes

This section describes the error messages that can be reported by the Engine layers.
Error Error Message Error Resolution

Code
s
TIBC {0} This is an internal product error. Contact

O- TIBCO Support.
BW-
COR
E-
00000
1
TIBC BWActivityManager Registration This is an internal product error. Contact

O- Error. The BWActivityManager TIBCO Support.
BW- argument provided to the BW
COR Engine is null.
E-
00001
0
TIBC Failed to initialize BW Engine. This is an internal product error. Contact

O- The BW Engine was initialized TIBCO Support.
BW- without a logger object.
COR
E-
00001
2

24 | Core

Code
s

O- While registering TIBCO Support.
BW- BWActivtyBridge the BW Engine
COR encountered exception [{0}]
E-
00001
8

O- The BWActivityManager was not TIBCO Support.
BW- registered correctly with the BW
COR Engine.
E-
00002
0

O- The BW Crypto service was not TIBCO Support.
BW- registered correctly with the BW
COR Engine.
E-
00002
2

O- The BW Custom XPath Function TIBCO Support.
BW- Manager service was not
COR registered correctly with the BW
E- Engine.
00002
4
TIBC Failed to enable BW Debugger. This is an internal product error. Contact

O- The BW Engine has not been TIBCO Support.
BW- initialized.

25 | Core

Code
s
COR
E-
00002
6
TIBC The BW Debugger is already This is an internal product error. Contact

O- enabled state and it can not be TIBCO Support.
BW- enabled again.
COR
E-
00002
8
TIBC Unable to disable BW Debugger. This is an internal product error. Contact

O- The BW Engine has not been TIBCO Support.
BW- initialized.
COR
E-
00003
0
TIBC Attempt to disable the BW This is an internal product error. Contact

O- Debugger encountered exception TIBCO Support.
BW- [{0}]
COR
E-
00003
2
TIBC Unable to enable BW Event This is an internal product error. Contact

O- Publisher. The BW Engine has TIBCO Support.
BW- not been initialized.
COR
E-
00003

26 | Core

Code
s
TIBC BW Engine configuration data This is an internal product error. Contact

O- does not contain AppNode name. TIBCO Support.
BW-
COR
E-
00003
6

O- does not contain AppSpace TIBCO Support.
BW- name.
COR
E-
00003
8

O- does not contain Domain name. TIBCO Support.
BW-
COR
E-
00004
0
TIBC The operation [{0}] is not This is an internal product error. Contact
O- supported for the BX Non- TIBCO Support.
BW- Executable Module.
COR ModuleName={0},
E- ModuleVersion={1}
00005
2

27 | Core

Code
s
O- supported for the BX Executable TIBCO Support.

BW- Module. ModuleName={1},
COR ModuleVersion={2}
E-
00005
4
O- supported for the BW Job Shared TIBCO Support.
BW- Variable.
COR
E-
00005
6
TIBC Unable to obtain This is an internal product error. Contact

O- EngineManagement. The BW TIBCO Support.
BW- Engine has not been initialized.
COR
E-
00005
7

O- EngineManagement due to TIBCO Support.
BW- exception [{0}]
COR
E-
00005
8
TIBC The BX operation [{0}] failed due This is an internal product error. Contact
O- to exception [{1}]. TIBCO Support.
BW-
COR

28 | Core

Code
s
E-
00005
9
TIBC Invalid 'BWModuleHandle'. The This is an internal product error. Contact

O- BW module represented by this TIBCO Support.
BW- handle has been already un-
COR installed or the handle has been
E- already destroyed.
00010
2
TIBC Unable to obtain process This is an internal product error. Contact

O- templates referenced by BW TIBCO Support.
BW- Module, the BW Engine
COR encountered exception.
E- ModuleName[{0}], ModuleVersion
00010 [{1}], Exception[{2}].
4
TIBC Unable to obtain GenXDM This is an internal product error. Contact

O- SchemaComponentCache for the TIBCO Support.
BW- BW Module [{0}]. The operation
COR [{1}] returned "null".
E-
00011
6

BW- BW Module [{0}]. The operation
COR [{1}] returned exception [{2}]
E-
00011
8

29 | Core

Code
s

BW- BW Module [{0}:{1}] due to
COR exception [{2}]
E-
00012
0
TIBC Unable to obtain "BundleContext" This is an internal product error. Contact

O- for BW module [{0}:{1}]. The TIBCO Support.
BW- operation [{2}] returned "null"
COR
E-
00012
2

O- for BW module [{0}:{1}] due to TIBCO Support.
BW- exception [{2}]
COR
E-
00012
4

O- ServiceReference for the cache TIBCO Support.
BW- service [{0}]. The operation
COR "BundleContext.getServiceRefere
E- nce" for BW module [{1}:{2}]
00012 returned "null".
6

BW- service [{0}]. The operation

30 | Core

Code
s
COR "BundleContext.getServiceRefere
E- nce" for BW module [{1}:{2}]
00012 returned exception [{3}]
8
TIBC Unable to obtain XSD cache This is an internal product error. Contact
O- service [{0}] for the BW module TIBCO Support.
BW- [{1}:{2}]. The operation [{3}]
COR returned "null".
E-
00013
0
TIBC Unable to obtain XSD cache This is an internal product error. Contact
COR returned exception [{4}]
E-
00013
1
TIBC Unable to obtain WSDL cache This is an internal product error. Contact
E-
00013
2
TIBC Unable to obtain WSDL cache This is an internal product error. Contact
COR returned exception [{4}]
E-
00013

31 | Core

Code
s
TIBC Unable to obtain WSDL This is an internal product error. Contact

O- ModuleCache from the TIBCO Support.
BW- WSDLCacheService for the
COR WSDL namespace [{0}],
E- locationURI [{1}] that is
00013 associated with the BW Module
4 [{2}:{3}], DeploymentUnit [{4}:{5}].
The operation [{6}] returned "null".
TIBC Unable to obtain WSDL This is an internal product error. Contact

O- ModuleCache from the TIBCO Support.
BW- WSDLCacheService for the
COR WSDL namespace [{0}],
E- locationURI [{1}] that is
00013 associated with the BW Module
5 [{2}:{3}], DeploymentUnit [{4}:{5}].
Encountered exception [{6}]

O- BxWSDLResolver for the WSDL TIBCO Support.
BW- namespace [{0}], Location [{1}]
COR that is associated with the BW
E- Module [{2}:{3}], DeploymentUnit
00013 [{4}:{5}] due to exception [{6}]
6
TIBC Unable to obtain GenXDM WSDL This is an internal product error. Contact
O- Module for the WSDL namespace TIBCO Support.
BW- [ {0} ] that is associated with the
COR BW Module [{1}:{2}],
E- DeploymentUnit [{3}:{4}]. The
00013 operation "{5}" returned exception
7 [{6}]

32 | Core

Code
s
BW- [ {0} ] that is associated with the
COR BW Module [{1}:{2}],
E- DeploymentUnit [{3}:{4}]. The
00013 operation "{5}" returned "null".
8 Ensure the BW Module [{6}] is
dependent on a BW shared
module which contains the WSDL
file for this WSDL namespace or
the BW Module [{7}] itself
contains the required WSDL file.
TIBC Unable to obtain WSDL Message This is an internal product error. Contact
O- details from the GenXDM WSDL TIBCO Support.
BW- Module for the WSDL namespace
COR [ {0} ] that is referenced in the BW
E- Module [{1}:{2}] due to exception
00014 [{3}].
0
TIBC Unable to obtain WSDL Definition This is an internal product error. Contact
O- namespace details from the TIBCO Support.
BW- GenXDM WSDL Module for the
COR WSDL namespace [ {0} ] that is
E- associated with the BW Module
00014 [{1}:{2}] due to exception [{3}].
2
TIBC Unable to obtain WSDL Target This is an internal product error. Contact
O- namespace from the GenXDM TIBCO Support.
BW- WSDL Module for the WSDL
COR namespace [ {0} ] that is
00014 [{1}:{2}] due to exception [{3}].

33 | Core

Code
s
TIBC Unable to obtain WSDL Interface This is an internal product error. Contact
BW- Module for the PortType [{0}], that
COR is associated with the BW Module
E- [{1}:{2}]. The operation "{3}"
00014 returned exception [{4}].
6
COR is associated with the BW Module
E- [{1}:{2}]. The operation "{3}"
00014 returned null.
8
TIBC Unable to construct PortType This is an internal product error. Contact

BW- Interface for the WSDL
COR namespace [ {0} ] that is
00015 [{1}:{2}] due to exception [{3}].
0
TIBC Invalid BWBxWSDLResolver. The This is an internal product error. Contact

O- instance of this TIBCO Support.
BW- BWBxWSDLResolver has been
COR already released.
E-
00015
2
TIBC The initial value mode [{0}] This is an internal product error. Contact

34 | Core

Code
s
O- specified for the {1} [{2}] in BW TIBCO Support.

BW- Module [{3}:{4}], DeploymentUnit
COR [{5}:{6}] is invalid.
E-
00016
0
TIBC The QName value [{0}] specified This is an internal product error. Contact
O- for the {1} [{2}] in BW Module [{3}] TIBCO Support.
BW- is invalid or malformed.
COR
E-
00016
2
TIBC Invalid 'BWComponentHandle'. This is an internal product error. Contact

O- The BW Component represented TIBCO Support.
BW- by this handle has been already
COR un-installed or the handle has
E- been already destroyed.
00020
2
TIBC Unable to create This is an internal product error. Contact

O- ServiceEndpointRequestHandler TIBCO Support.
BW- for BW Component due to invalid
COR BW Process ServiceType [{0}].
E- ComponentName={1},
00020 ComponentVersion={2}
4

BW- for BW Component due to invalid
COR BW Process ServiceName [{0}].

35 | Core

Code
s
E- ComponentName={1},
00020 ComponentVersion={2}
6
TIBC Error occurred while creating This is an internal product error. Contact
BW- for service [{0}], BW Component
COR [{1}], Application [{2}:{3}].
E- Exception[{4}].
00020
8

BW- for service [{0}], BW Component
COR [{1}]. The operation
E- "BxSystem.getInterfaceProvider"
0
TIBC Received unexpected exception This is an internal product error. Contact

O- [{0}] from the service binding TIBCO Support.
BW- associated with the component
COR service [{1}], Application [{2}] on
E- invocation of method [{3}].
00021
2
TIBC Unable to obtain "BundleContext". This is an internal product error. Contact

O- The operation "{0}" returned "null" TIBCO Support.
BW-
COR
E-
00021
4

36 | Core

Code
s

O- due to exception [{0}] TIBCO Support.
BW-
COR
E-
00021
6
BW- [{0}] that is associated with the
COR BW Component [{1}], Application
E- [{2}:{3}]. The operation "{4}"
00022 returned exception [{5}]
0
BW- [{0}] that is associated with the
COR BW Component [{1}], Application
E- [{2}:{3}]. The operation "{4}"
2
TIBC Unable to obtain WSDL Interface

O- details from the GenXDM WSDL
COR is associated with the BW
E- Component [{1}], Application[{2}:
00022 {3}]. The operation "{4}" returned
4 exception [{5}].

37 | Core

Code
s
COR is associated with the BW

E- Component [{1}], Application[{2}:
00022 {3}]. The operation "{4}" returned
6 null.
TIBC Unable to obtain

O- ServiceReference for the cache
BW- service [{0}]. The operation "{1}"
E-
00022
8

BW- service [{0}] due to exception [{1}]
COR
E-
00023
0
TIBC Unable to obtain cache service This is an internal product error. Contact
O- [{0}]. The operation "{1}" returned TIBCO Support.
BW- "null".
COR
E-
00023
1
TIBC Unable to obtain cache service This is an internal product error. Contact
O- [{0}]. The operation "{1}" returned TIBCO Support.
BW- exception [{2}].
COR
E-
00013

38 | Core

Code
s
TIBC Unable to construct PortType This is an internal product error. Contact

BW- Interface for the WSDL
COR namespace [{0}] that is
E- associated with the BW
00023 Component [{1}] due to exception
2 [{2}].
TIBC Unable to obtain ModuleCache for This is an internal product error. Contact
O- the BW Component [{0}]. The TIBCO Support.
BW- operation "{1}" returned "null".
COR
E-
00023
4
TIBC Failed obtain value for the BW framework layer encountered errors
O- component level property [{0}], when accessing the component level
BW- BW Component [{1}], Application property. Contact TIBCO Support.
COR [{2}:{3}]. Encountered exception
E- [{4}]
00023
5
TIBC Invalid 'BWApplicationHandle'. This is an internal product error. Contact

O- The BW Application represented TIBCO Support.
BW- by this handle has been already
COR un-installed or the handle has
E- been already destroyed.
00030
2

39 | Core

Code
s
O- 'BWApplicationHandle' due to TIBCO Support.

BW- invalid BWComponentHandle list.
COR The argument of type
E- 'List<BWComponentHandle>;'
00030 must contain at least one
4 BWComponentHandle.

O- 'BWApplicationHandle' due to TIBCO Support.
BW- inconsistent application names in
COR the BWComponentHandle(s)
E- contained in the argument of type
00030 'List<BWComponentHandle>;'.
6 The handle for the BW
Component [{0}] has application
name as [{1}] where as the first
handle in the list has application
name as [{2}].

O- 'BWApplicationHandle' for the BW TIBCO Support.
BW- Application [{0}].
COR
E-
00030
8
TIBC Error occurred when accessing This is an internal product error. Contact
O- the ProcessStarter activity [{0}] in TIBCO Support.
BW- process [{1}], module [{2}] from
COR the BWActivityManager. Error=
E- {3}.
00040
2

40 | Core

Code
s
TIBC Error occurred when configuring This is an internal product error. Contact
O- the ProcessStarter activity [{0}] in TIBCO Support.
BW- process [{1}], module [{2}].
COR
E-
00040
4
TIBC Unable to configure This is an internal product error. Contact

O- ProcessStarter activity [{0}] in TIBCO Support.
BW- process [{1}], module [{2}] due to
COR crypto service access error.
E-
00040
6
TIBC HotUpdate operation not This error can occur if the BW process file
O- supported for ProcessStarter has been corrupted.
BW- activity [{0}] in process [{1}],
COR module [{2}]. The ProcessStarter
E- already exists for activitId [{3}].
00040
8
TIBC Failed to obtain activity [{0}] in This is an internal product error. Contact
O- process [{1}], module [{2}] from TIBCO Support.
BW- the BWActivityManager due to
COR exception [{3}]. ActivityId [{4}].
E-
00060
2
TIBC Error occurred when configuring This is an internal product error. Contact
O- the activity [{0}] in process [{1}], TIBCO Support.
BW- module [{2}]

41 | Core

Code
s
COR
E-
00060
4
TIBC Unable to configure activity [{0}] in This is an internal product error. Contact
O- process [{1}], module [{2}] due to TIBCO Support.
BW- crypto service access error.
COR
E-
00060
6
TIBC Unable to execute [{0}] operation This is an internal product error. Contact
O- for an activity. Failed to lookup TIBCO Support.
BW- activity [{1}] in process [{2}],
COR module [{3}] from the
E- BWActivityManager. ActivityId
00060 [{4}].
8
TIBC HotUpdate operation not This is an internal product error. Contact

O- supported for activity [{0}] in TIBCO Support.
BW- process [{1}], module [{2}]. The
COR activity already exists for activitId
E- [{3}].
00061
0
TIBC {0} This is a trace message and resolution is not

O- applicable.
BW-
COR
E-
10000

42 | Core

Code
s
TIBC Activated Application[{0}], This is a trace message and resolution is not

O- Component[{1}] in AppNode[{2}], applicable.
BW- ActivationAlias[{3}].
COR
E-
10000
2
TIBC Activated Application[{0}], Module This is a trace message and resolution is not
O- [{1}] in AppNode[{2}], applicable.
BW- ActivationAlias[{3}].
COR
E-
10000
3
TIBC {0} This is a debug message and resolution is

O- not applicable.
BW-
COR
E-
20000
1

O- not applicable.
BW-
COR
E-
20200
0
TIBC Initialized BW Engine successfully This is a debug message and it indicates the

43 | Core

Code
s
O- [{0}, {1}, {2}]. BW Engine was initialized successfully.

BW- Resolution is not applicable for this message.
COR
E-
20200
2
TIBC Stopped(Graceful) BW Engine This is a debug message and it indicates the

O- successfully. BW Engine was stopped gracefully.
COR
E-
20205
2
TIBC Stopped(Forceful) BW Engine This is a debug message and it indicates the

O- successfully. BW Engine was stopped forcefully before
BW- completing all application jobs. Resolution is
COR not applicable for this message.
E-
20205
3
TIBC BW Engine is already in stopped This is a debug message and resolution is

O- state. not applicable.
BW-
COR
E-
20205
4
TIBC Enabled BW Debugger in the BW This is a debug message and resolution is

O- Engine. not applicable.
BW-
COR

44 | Core

Code
s
E-
20205
5
TIBC Disabled BW Debugger in the BW This is a debug message and resolution is

O- Engine. not applicable.
BW-
COR
E-
20205
6

O- not applicable.
BW-
COR
E-
20210
0
TIBC INITIATE: install BW Module [{0}: This is a debug message and it indicates the
O- {1}], DeploymentUnit [{2}:{3}]. BW Engine is starting to create the BW
BW- Module. Resolution is not applicable for this
COR message.
E-
20210
1
TIBC Installed BW Module [{0}:{1}], This is a debug message and it indicates the
O- DeploymentUnit [{2}:{3}]. BW Engine has completed creating the BW
BW- Module. Resolution is not applicable for this
COR message.
E-
20210
2

45 | Core

Code
s
TIBC INITIATE: release-resources for This is a debug message and it indicates the
O- BW Module [{0}:{1}], BW Engine is starting to release the BW
BW- DeploymentUnit [{2}:{3}]. Module resources. Resolution is not
COR applicable for this message.
E-
20210
3
TIBC Released-resources for BW This is a debug message and it indicates the

O- Module [{0}:{1}], DeploymentUnit BW Engine has completed releasing the BW
BW- [{2}:{3}]. Module resources. Resolution is not
COR applicable for this message.
E-
20210
4
TIBC INITIATE: undeploy BW Module This is a debug message and it indicates the
O- [{0}:{1}], DeploymentUnit [{2}:{3}]. BW Engine is starting to un-deploying the
BW- BW Module. Resolution is not applicable for
COR this message.
E-
20210
5
TIBC Undeployed BW Module [{0}:{1}], This is a debug message and it indicates the
O- DeploymentUnit [{2}:{3}]. BW Engine has completed un-deploying the
BW- BW Module. Resolution is not applicable for
COR this message.
E-
20210
6

O- not applicable.
BW-

46 | Core

Code
s
COR
E-
20220
0
TIBC INITIATE: install BW Component This is a debug message and it indicates the
O- [{0}], Application[{1}:{2}]. BW Engine is starting to create the BW
BW- Component. Resolution is not applicable for
COR this message.
E-
20220
1
TIBC Installed BW Component [{0}], This is a debug message and it indicates the
O- Application[{1}:{2}]. BW Engine has completed creating the BW
COR this message.
E-
20220
2
TIBC INITIATE: initialize BW This is a debug message and it indicates the

O- Component [{0}], Application[{1}: BW Engine is starting to initialize the BW
BW- {2}]. Component. Resolution is not applicable for
COR this message.
E-
20220
3
TIBC Initialized BW Component [{0}], This is a debug message and it indicates the
O- Application[{1}:{2}]. BW Engine has completed initializing the BW
COR this message.
E-
20220

47 | Core

Code
s
TIBC INITIATE: start BW Component This is a debug message and it indicates the
O- [{0}]. BW Engine is starting the BW Component.
COR
E-
20220
5
TIBC Started BW Component [{0}]. This is a debug message and it indicates the
O- BW Engine has stated the BW Component.
COR
E-
20220
6
TIBC INITIATE: stop(Forceful) BW This is a debug message and resolution is

O- Component [{0}]. not applicable.
BW-
COR
E-
20220
7
TIBC Stopped(Forceful) BW This is a debug message and resolution is

BW-
COR
E-
20220
8
TIBC INITIATE: destroy BW This is a debug message and resolution is

48 | Core

Code
s

BW-
COR
E-
20220
9
TIBC Destroyed BW Component [{0}]. This is a debug message and resolution is

O- not applicable.
BW-
COR
E-
20221
0
TIBC INITIATE: release-resources for This is a debug message and resolution is

O- BW Component [{0}], Application not applicable.
BW- [{1}:{2}].
COR
E-
20221
1
TIBC Released-resources for BW This is a debug message and resolution is

O- Component [{0}], Application[{1}: not applicable.
BW- {2}].
COR
E-
20221
2
TIBC INITIATE: undeploy BW This is a debug message and resolution is

O- Component [{0}], Application[{1}: not applicable.
BW- {2}].
COR

49 | Core

Code
s
E-
20221
3
TIBC Undeployed BW Component [{0}], This is a debug message and resolution is

O- Application[{1}:{2}]. not applicable.
BW-
COR
E-
20221
4
TIBC INITIATE: start ServiceBinding(s) This is a debug message and resolution is

O- or ProcessStarter for BW not applicable.
BW- Component [{0}], Application[{1}:
COR {2}].
E-
20221
5
TIBC Started ServiceBinding(s) or This is a debug message and resolution is

O- ProcessStarter for BW not applicable.
COR {2}].
E-
20221
6
TIBC INITIATE: stop ServiceBinding(s) This is a debug message and resolution is

O- or ProcessStarter for BW not applicable.
COR {2}].
E-
20221
7

50 | Core

Code
s
TIBC Stopped ServiceBinding(s) or This is a debug message and resolution is

O- ProcessStarter for BW not applicable.
COR {2}].
E-
20221
8
TIBC INITIATE: start ServiceBinding This is a debug message and resolution is

O- [{0}] for BW Component [{1}], not applicable.
BW- Application [{2}:{3}].
COR
E-
20221
9
TIBC Started ServiceBinding [{0}] for This is a debug message and resolution is
BW- [{2}:{3}].
COR
E-
20222
0
TIBC INITIATE: stop ServiceBinding This is a debug message and resolution is

O- [{0}] for BW Component [{1}], not applicable.
COR
E-
20222
1
TIBC Stopped ServiceBinding [{0}] for This is a debug message and resolution is
BW- [{2}:{3}].

51 | Core

Code
s
COR
E-
20222
2
TIBC Ready to uninstall BW This is a debug message and resolution is

O- Component [{0}], Application [{1}]. not applicable.
BW-
COR
E-
20222
3
TIBC Created This is a debug message and resolution is

O- ServiceEndpointRequestHandler not applicable.
BW- for the ServiceBinding [{0}],
COR Service [{1}], BW Component
E- [{2}], Application [{3}:{4}].
20222
4

O- not applicable.
BW-
COR
E-
20230
0
TIBC INITIATE: create BW Application This is a debug message and resolution is

O- [{0}] handle. not applicable.
BW-
COR
E-
20230

52 | Core

Code
s
TIBC Created BW Application [{0}] This is a debug message and resolution is

O- handle. not applicable.
BW-
COR
E-
20230
2
TIBC INITIATE: start BW Application This is a debug message and resolution is

O- [{0}]. not applicable.
BW-
COR
E-
20230
3
TIBC Started BW Application [{0}]. This is a debug message and resolution is

O- not applicable.
BW-
COR
E-
20230
4
TIBC INITIATE: stop(Graceful) for BW This is a debug message and resolution is

O- Application [{0}]. not applicable.
BW-
COR
E-
20230
9
TIBC Stopped(Graceful) BW This is a debug message and resolution is

53 | Core

Code
s

BW-
COR
E-
20231
0
TIBC INITIATE: stop(Forceful) BW This is a debug message and resolution is

BW-
COR
E-
20231
1
TIBC Stopped(Forceful) BW Application This is a debug message and resolution is

BW-
COR
E-
20231
2
TIBC INITIATE: start all This is a debug message and resolution is

O- ProcessStarters and not applicable.
BW- ServiceBindings for BW
COR Application [{0}:{1}].
E-
20231
3
TIBC Started all ProcessStarters and This is a debug message and resolution is
O- ServiceBindings for BW not applicable.
COR

54 | Core

Code
s
E-
20231
4
TIBC INITIATE: stop all This is a debug message and resolution is

O- ProcessStarters and not applicable.
BW- ServiceBindings for BW
COR Application [{0}:{1}].
E-
20231
5
TIBC Stopped all ProcessStarters and This is a debug message and resolution is
O- ServiceBindings for BW not applicable.
COR
E-
20231
6
TIBC INITIATE: pause BW Application This is a debug message and resolution is

BW-
COR
E-
20231
7
TIBC Paused BW Application [{0}]. This is a debug message and resolution is

O- not applicable.
BW-
COR
E-
20231
8

55 | Core

Code
s
TIBC INITIATE: resume BW Application This is a debug message and resolution is

BW-
COR
E-
20231
9
TIBC Resumed BW Application [{0}]. This is a debug message and resolution is

O- not applicable.
BW-
COR
E-
20232
0
TIBC INITIATE: initialize ProcessStarter This is a debug message and resolution is

O- activity [{0}] in Process[{1}], not applicable.
BW- Module [{2}], DeploymentUnit [{3}:
COR {4}].
E-
20240
1
TIBC Initialized ProcessStarter activity This is a debug message and resolution is

O- [{0}] in Process[{1}], Module [{2}], not applicable.
BW- DeploymentUnit [{3}:{4}].
COR
E-
20240
2
TIBC INITIATE: start ProcessStarter This is a debug message and resolution is


56 | Core

Code
s
COR {4}].
E-
20240
3
TIBC Started ProcessStarter activity This is a debug message and resolution is

COR
E-
20240
4
TIBC INITIATE: stop ProcessStarter This is a debug message and resolution is

COR {4}].
E-
20240
5
TIBC Stopped ProcessStarter activity This is a debug message and resolution is

COR
E-
20240
6
TIBC INITIATE: destroy ProcessStarter This is a debug message and resolution is

COR {4}].
E-
20240

57 | Core

Code
s
TIBC Destroyed ProcessStarter activity This is a debug message and resolution is

COR
E-
20240
8
TIBC INITIATE: release ProcessStarter This is a debug message and resolution is

COR {4}].
E-
20240
9
TIBC Released ProcessStarter activity This is a debug message and resolution is

COR
E-
20241
0

O- not applicable.
BW-
COR
E-
20241
1
TIBC INITIATE: release ProcessStarter This is a debug message and resolution is

58 | Core

Code
s

COR {4}].
E-
20250
9
TIBC Released ProcessStarter activity This is a debug message and resolution is

COR
E-
20251
0

O- not applicable.
BW-
COR
E-
20251
1
TIBC INITIATE: initialize Activity [{0}] in This is a debug message and resolution is
O- Process[{1}], Module [{2}], not applicable.
COR
E-
20260
1
TIBC Initialized Activity [{0}] in Process This is a debug message and resolution is
O- [{1}], Module [{2}], not applicable.
COR

59 | Core

Code
s
E-
20260
2
TIBC INITIATE: destroy Activity [{0}] in This is a debug message and resolution is
O- Process[{1}], Module [{2}], not applicable.
COR
E-
20260
3
TIBC Destroyed Activity [{0}] in Process This is a debug message and resolution is
O- [{1}], Module [{2}], not applicable.
COR
E-
20260
4

O- not applicable.
BW-
COR
E-
20260
5

O- not applicable.
BW-
COR
E-
20611
0

60 | Core

Code
s

O- not applicable.
BW-
COR
E-
20611
1

O- not applicable.
BW-
COR
E-
20612
0

O- not applicable.
BW-
COR
E-
20612
1

O- not applicable.
BW-
COR
E-
20620
0

O- not applicable.
BW-

61 | Core

Code
s
COR
E-
20621
0

O- not applicable.
BW-
COR
E-
20631
0

O- not applicable.
BW-
COR
E-
20631
1

O- not applicable.
BW-
COR
E-
20640
0

O- not applicable.
BW-
COR
E-
20641

62 | Core

Code
s

O- not applicable.
BW-
COR
E-
20652
0

O- not applicable.
BW-
COR
E-
20652
1
TIBC Activity input data validation This is a debug message and resolution is
O- details. ActivityName={0}, not applicable.
BW- ProcessName={1}, Module={2}:
COR {3}, Schema={4}, Data={5}
E-
20661
1
TIBC Activity output data validation This is a debug message and resolution is
O- details. ActivityName={0}, not applicable.
BW- ProcessName={1}, Module={2}:
COR {3}, Schema={4}, Data={5}
E-
20661
2
TIBC The BusinessWorks Event This message indicates the BW Engine is

63 | Core

Code
s
O- Publisher is disabled. configured to disable the event publisher;

BW- therefore there will be no event published by
COR the BW Engine.
E-
30000
2
TIBC {0} This is a warning message and it highlights

O- situations that may affect the application
BW- execution.
COR
E-
40000
1
TIBC Activity resource release The activity resource release operation must
O- operation not raise an exception. This is considered to
BW- [com.tibco.bw.runtime.ActivityRes be an activity resource implementation error.
COR ource.release()] called at the end
E- of the execution of the BW group
40000 or BW Process instance
4 encountered error. The Activity
resource release operation
[{0}.release(boolean)] raised
exception: {1}
TIBC CatchAll fault details formating Received unexpected data when formating
O- issue. Expected [{0}], but received the CatchAll fault details.
BW- [{1}]
COR
E-
40000
6
TIBC The BW process [{0}] instance This message is generated when the

64 | Core

Code
s
O- cancelled, JobId [{1}], BusinessWorks Engine cancels a process

BW- ProcessInstanceId [{2}], instance execution. A process instance can
COR ParentProcessInstanceId [{3}], be canceled when one of the following
E- Module [{4}:{5}], Application [{6}: occurs: the invoke activity (in the parent
40001 {7}]. process) that called this process instance
0 timed out, the application is stopped non
gracefully or the process instance is explicitly
canceled through an internal management
interface.
TIBC Unable to close the file [{0}] The BW Engine was unable to close the file
O- configured for the initial value of that contains initial values for the Module or
BW- the {1} [{2}] in the BW Module [{3}: Job Shared variables. This error occurred
COR {4}], DeploymentUnit [{5}:{6}]; when attempting to close the file, but after
E- encountered exception [{7}]. reading the file contents.
40010
2
TIBC The BW Component [{0}:{1}] is The BW framework is attempting to destroy

O- already in destroyed state. the BW Component that is already in
BW- destroyed state. Resolution is not applicable.
COR
E-
40020
2
TIBC {0} This error code is used to log BW Engine

O- errors. For more details, refer to the
BW- additional exception message or the
COR "CausedBy" statements reported as part of
E- this error message.
50000
1
TIBC Failed to initialize BW Engine due The BW Engine did not successfully initialize,

65 | Core

Code
s
O- to exception [{0}] and this could be due to many reasons. For

BW- more details, refer to the additional exception
COR message or the "CausedBy" statements
E- reported as part of this error message.
50001
0
TIBC Failed to initialize BW Engine due The BW Engine was not able to establish
O- to database access error connection or access the engine database
BW- instance. Ensure the database driver,
COR connection, user name and password details
E- are correctly specified. Also ensure database
50001 instance has been started.
1
TIBC Failed to initialize BW Engine due The BW Engine failed to establish connection
O- to engine group connection with the engine group connection provider.
BW- provider error Ensure the group connection provider entity
COR (bw.engine.groupProvider.technology)
E- specified in the BW AppNode or BW
50001 AppSpace configuration file has been started
2 and accessible to the BW Engine.
TIBC Failed to initialize BW Engine due The BW Engine was not able to initialize due
O- to database schema configuration to the engine database schema configuration
BW- error. The BW Engine database error. Create a new engine database using
COR does not contain the required the database scripts provided in the TIBCO
E- tables. Ensure the BW Engine BusinessWorks product and this will
50001 database has been created with configure the database with the appropriate
3 the table schemas required by the schemas required by the engine.
engine
TIBC Failed to initialize BW Engine due The BW Engine is configured to execute in

O- to missing or incorrect engine persistence mode "datastore"; however the
BW- database configuration data. The required database configuration data was not

66 | Core

Code
s
COR BW Engine persistence mode specified. Ensure the BW Engine is

E- property [{0}] is set to [datastore] configured with the required database
50001 and this option requires valid connection details.
4 engine database configuration
data
TIBC Failed to initialize BW Engine due The BW Engine is configured to execute in

O- to missing or incorrect engine persistence mode "group"; however the
BW- database configuration data. The required database configuration data was not
COR BW Engine persistence mode specified. Ensure the BW Engine is
E- property [{0}] is set to [group] and configured with the required database
50001 this option requires valid engine connection details.
5 database configuration data
TIBC Failed to initialize BW Engine due This error can occur when the BW Engine is
O- to incompatible engine group configured to use a group name that does not
BW- name. The group name [{0}] match the group name in the engine
COR configured for the BW Engine database. To resolve these issues change
E- does not match the group name the engine group name to match the group
50001 value in the BW Engine database. name in the engine database, use a different
6 Try using a different engine engine database that contains the matching
database or change the engine engine group name or create a new engine
group name to match the value in database. Furthermore if the group name is
the database not specified then the BW Engine uses a
default group name. Refer to documentation
for more details on naming convention used
for the default engine group name.
TIBC Failed to initialize BW Engine due This error can occur if the engine database
O- to incompatible persistence mode was previously used by a BW Engine
BW- between the engine and the configured to execute in persistence mode
COR engine database. This error can 'datastore'
E- occur if the BW Engine is (bw.engine.persistenceMode=datastore).
50001 configured to execute in When a BW Engine uses the database for
7 persistence mode [group]; the first time, the database is updated with

67 | Core

Code
s
however the BW Engine database the engine execution persistence mode.

is configured for the persistence Subsequently the persistence mode value
mode [datastore]. Try using a stored in the database cannot be altered and
different database or use a the same database cannot be used for
database that is configured for the different engine persistence mode. To
persistence mode [group] resolve this issue ensure the engine and the
database persistence mode match or create
a new database using the database scripts
provided by the TIBCO BusinessWorks
product.
TIBC Failed to initialize BW Engine due This error can occur if the engine database
O- to incompatible persistence mode was previously used by a BW Engine
BW- between engine and the engine configured to execute in persistence mode
COR database. This error can occur if 'group' (bw.engine.persistenceMode=group).
E- the BW Engine is configured to When a BW Engine uses the database for
50001 execute in persistence mode the first time, the database is updated with
8 [datastore]; however the engine the engine execution persistence mode.
database is configured for the Subsequently the persistence mode value
persistence mode [group]. Try stored in the database cannot be altered and
using a database that is the same database cannot be used for
configured for the persistence different engine persistence mode. To
mode [datastore] or create a new resolve this issue ensure the engine and the
engine database database persistence mode match or create
a new database using the database scripts
provided by the TIBCO BusinessWorks
product.
TIBC Failed to initialize BW Engine due This error can occur if the BW Engine is
O- to missing or incorrect group configured to execute in persistence mode
BW- connection provider configuration [group] and the engine is not correctly
COR data. The BW Engine persistence configured with the group connection
E- mode property [{0}] is set to provider data. Ensure the BW Engine is
50001 [group] and this option requires configured with the required group
9 valid engine group connection connection provider details.

68 | Core

Code
s
provider configuration data.
TIBC Failed to initialize BW Engine due This error can occur if the BW Engine is
O- to incorrect engine group name. configured to execute in persistence mode
BW- The BW Engine persistence mode [group] and an empty or invalid engine group
COR property [{0}] is set to [group] and name is specified. Ensure the engine group
E- this option requires a valid engine name is not empty or contains a valid name.
50002 group name specified via property
0 [{1}].
TIBC Failed to initialize BW Engine. Ensure the BW Engine thread count is not
O- The BW Engine thread count configured to be empty or null. Furthermore
BW- value is configured incorrectly. the thread count value must be an integer
COR Ensure the thread count value is that is greater than zero.
E- set to an integer that is greater
50002 than zero
1
TIBC Failed to initialize BW Engine. Ensure the BW Engine step count is not
O- The BW Engine step count value configured to be empty or null. Furthermore
BW- is configured incorrectly. Ensure the step count value must be "-1" or an
COR the step count value is set to "-1" integer that is greater than zero.
E- or an integer that is greater than
50002 zero
2
TIBC Failed to initialize BW Engine. Ensure the specified BW Engine property is

O- The BW Engine property [{0}] not configured to be empty or null. The value
BW- contains incorrect value [{1}]. configured for this property must be an
COR Ensure the value is an integer that integer that is greater than zero.
E- is greater than one
50002
3
TIBC Failed to initialize BW Engine. Ensure the specified BW Engine property is

69 | Core

Code
s
O- The BW Engine property [{0}] not configured to be empty or null. The value
BW- contains incorrect value [{1}]. configured for this property must be an
COR Ensure the value is an integer that integer that is greater than zero.
E- is greater than one.
50002
4

O- While creating TIBCO Support.
BW- SpringApplicationContext the BW
COR Engine encountered exception:
E- {0}.
50002
5
TIBC The ProcessStarter has not been A ProcessStarter is attempting to perform an

O- initialized or it is in the destroyed operation when it has not been initialized or it
BW- state. The EventSourceContext is in the destroyed state. This is considered
COR associated with the to be a ProcessStarter implementation error.
E- ProcessStarter is invalid.
50002
6
TIBC Failed to initialize BW Engine due This error can be reported when multiple BW
O- to exception [{0}]. This error can Engines configured for 'datastore'
BW- occur if the BW Engine persistence mode is attempting to use the
COR persistence mode is set to [{1}] same database configuration. Ensure
E- and the same database different database configuration specified for
50002 configuration is used by multiple each BW Engine when the persistence option
7 BW Engines. When a BW Engine is 'datastore'. This is also applicable when
is configured for the persistence multiple BW Engines (BW AppNodes) are
mode [{2}], then each BW Engine part of the same BW AppSpace.
must have a unique database
configuration. This is applicable
even if the BW Engines (BW

70 | Core

Code
s
AppNodes) are part of the same

BW AppSpace
TIBC BW Engine stop operation An error was encountered when stopping the
O- encountered exception [{0}] BW Engine. For more details, refer to the
BW- additional exception message or the
50003
0
TIBC BW Engine graceful stop An error was encountered when attempting

O- operation encountered exception to gracefully stop the BW Engine. For more
BW- [{0}] details, refer to the additional exception
50003
1
TIBC Exception occurred when Error was encountered when attempting to

O- accessing custom XPATH access the custom XPath function associated
BW- function(s) associated with the with the BW Engine. Contact TIBCO Support.
COR BusinessWork Engine.
E- Exception={0}
50003
2
TIBC Failed to enable the BW Error was encountered when attempting to

O- Debugger entity in the BW Engine enable the BW Debugger entity in the BW
BW- due to exception [{0}] Engine. Contact TIBCO Support.
COR
E-
50003
3

71 | Core

Code
s
TIBC BW Debugger connection failed, Ensure valid BW Debugger connection is

O- encountered exception [{0}] provided when enabling the BW Debugger
BW- entity in the BW Engine.
COR
E-
50003
4
TIBC Unable to enable Event Publisher Error was encountered when attempting to
O- in the BW Engine, encountered enable the Event Publisher in the BW
BW- exception [{0}] Engine. Contact TIBCO Support.
COR
E-
50003
5
TIBC Attempt to disable the Event Error was encountered when attempting to
O- Publisher in the BW Engine, disable the Event Publisher in the BW
BW- encountered exception [{0}] Engine. Contact TIBCO Support.
COR
E-
50003
6
TIBC Unable to associate an activity An activity that is not inside a group is

O- resource with a BW group. The attempting to associate a resource with a
BW- activity [{0}] in process [{1}] is not group. This error can occur due to an activity
COR contained within a group; however implementation error.
E- the activity is attempting to
50003 associate a resource with a
7 group. {2}
TIBC Unable to associate an activity An activity that is not inside a loop is

O- resource with a BW loop. The attempting to associate a resource with a
BW- activity [{0}] in process [{1}] is not loop. This error can occur due to an activity

72 | Core

Code
s
COR contained within a loop; however implementation error.

E- the activity is attempting to
50003 associate a resource with a loop.
8 {2}
TIBC Reference Binding configured for The Reference Binding configured for the
O- the process reference [{0}], in process provided an invalid message data
BW- process [{1}], module [{2}] model. This error can occur due to the
COR provided unsupported message Reference Binding implementation error.
E- data model [{3}].
50003
9
TIBC Invocation of the Process This error indicates the Reference Binding
O- Reference's operation [{0}] failed. configured for the process reference failed
BW- The BW Reference Binding [{1}] and returned a fault.
COR configured for the process
E- reference [{2}] in process [{3}],
50004 module [{4}] returned fault [{5}].
0
TIBC Invalid activity name. The activity The error indicates the specified activity
O- name [{0}] is not found in process name is not contained within the BW
BW- [{1}], module [{2}:{3}], process. Ensure a valid activity name is
COR DeploymentUnit [{4}:{5}]. specified for this operation.
E-
50004
1
TIBC The BW Debugger entity is The BW Debugger entity in the BW Engine

O- already enabled in the BW Engine can not be enabled again when it is already
BW- and it can not be enabled again. in enabled state. It is only possible to disable
COR the BW Debugger entity when it is in the
E- enabled state.
50004

73 | Core

Code
s
TIBC The BW process [{0}] instance This error message indicates the process
O- faulted, JobId [{1}], instance did not complete successfully;
BW- ProcessInstanceId [{2}], instead it terminated due to an error that
COR ParentProcessInstanceId [{3}], occurred during the execution of the process
E- Module [{4}:{5}], Application [{6}: instance. For more details on the process
50005 {7}]. {8} instance failure, refer to the additional
0 exception message or the "CausedBy"
statements reported as part of this error
message.
TIBC Activity [{0}] fault. {1} This message indicates the potential activity
O- that raised the fault and caused the process
BW- instance to fail.
COR
E-
50005
1
TIBC Invoke activity [{0}] fault. {1} This message indicates the potential invoke
O- activity that raised the fault and caused the
BW- process instance to fail.
COR
E-
50005
2
TIBC XSLT transformation error. {0} This message indicates the cause of the
O- failure could be due to a XSLT transformation
BW- error.
COR
E-
50005
3

74 | Core

Code
s
TIBC Activity [{0}] XSLT transformation This message indicates the cause of the
O- error. {1} failure could be due to an Activity XSLT
BW- transformation error.
COR
E-
50005
4
TIBC XPATH error. {0} This message indicates the cause of the
O- failure could be due to a XPATH error.
BW-
COR
E-
50005
5
TIBC Activity [{0}] XPATH error. {1} This message indicates the cause of the
O- failure could be due to an Activity XPATH
BW- error.
COR
E-
50005
6
TIBC XML related error. {0} This message indicates the cause of the
O- failure could be due to a XML error.
BW-
COR
E-
50005
7
TIBC Activity [{0}] XML related error. {1} This message indicates the cause of the
O- failure could be due to an Activity XML error.
BW-

75 | Core

Code
s
COR
E-
50005
8
TIBC Reply activity [{0}] error. The reply This error message is reported when a
O- activity cannot be associated with process is implemented to execute more than
BW- the ProcessService request one Reply activity for the same operation, the
COR message. This error can occur if caller of this process (Service Binding, Parent
E- the process is implemented to Process) has terminated before Reply activity
50005 send reply multiple times for the can be executed or on recovery from a
9 same request, the caller of this check-point the Reply activity is executed but
process is no longer available or the caller of this process did not recover
on recovery from a check-point because it was not part of the check-pointed
the caller did not recover because job. Ensure the process is not implemented
it was not part of the check- to reply to same request multiple times.
pointed job. {1}
TIBC The process instance terminated This message is reported when a process
O- without replying to the caller of instance terminates without replying to the
BW- this process. {0} request of a ProcessService operation. This
COR can occur if the process is implemented
E- incorrectly to end the process execution
50006 without performing a reply operation or when
0 the process instance is canceled. Ensure the
process in implemented correctly and there is
no validation errors.
TIBC Reply activity [{0}] error. The reply This error message can be reported for the
O- activity [{1}] encountered error on following reasons: the caller of this process
BW- sending the response to the caller (Service Binding, Parent Process) raised a
COR of this process. This error can fault when processing the reply message, the
E- occur if the caller of this process caller of this process is no longer available.
50006 raised a fault when processing the
1 reply message, the caller of this

76 | Core

Code
s
process is no longer available. {2}
TIBC {0} This message provides information for the

O- process instance failure.
BW-
COR
E-
50006
3
TIBC Activity [{0}] error. {1} This message indicates the potential activity
O- that raised the fault and caused the process
BW- instance to fail.
COR
E-
50006
4
TIBC Throw activity [{0}] fault. Fault: {1} This message indicates the name of the
O- Throw activity that raised the fault and
BW- caused the process instance to fail.
COR
E-
50006
5
TIBC Invoke activity faulted due an This message indicates the Invoke activity
O- error from the invoked failed due to an unexpected error received for
BW- subprocess. {0} the invoked subprocess. This error can occur
COR if the subprocess terminated without replying,
E- the subprocess faulted, the invoked
50006 subprocess does not exist, etc. Ensure the
6 invoked subprocess is implemented correctly
and confirms to the invoked operation
contract.

77 | Core

Code
s
TIBC Activity [{0}] faulted due to an This error can occur when the BW Engine is
O- object serialization error. This attempting to serialize a Java object to
BW- error can occur if an object that support the persistence feature and the
COR must be serialized as part of the object cannot be serialized. Ensure the Java
E- BusinessWorks process object is Serializable and the Java package
50006 execution is not Serializable or that contains the class is exported.
7 the Java package that contains
the class is not exported correctly.
{1}
TIBC Fault occurred due to an object This error can occur when the BW Engine is
O- serialization error. This error can attempting to serialize a Java object to
BW- occur if the Java class that must support the persistence feature; however the
COR be serialized as part of the Java object cannot be serialized. Ensure the
E- BusinessWorks process Java object is Serializable and the Java
50006 execution is not Serializable or package that contains the class is exported.
8 the Java package that contains
the class is not exported correctly.
{0}
TIBC Failed to confirm the request This error message can be reported for the
O- message from the receive activity following reasons: the process is
BW- [{0}], in process [{1}], module [{2}: implemented to execute more than one
COR {3}], application [{4}:{5}]. This confirm activity for the same request, the
E- error can occur if the process is caller of this process instance (Service
50008 implemented to confirm multiple Binding, Parent process) has terminated
9 times for the same request before the confirm activity can be executed or
message, the caller of this on recovery from a check-point the confirm
process is no longer available, on activity is executed; however the caller of this
recovery from a check-point the process did not recover because it was not
caller did not recover because it part of the check-pointed job. Ensure the
was not part of the check-pointed process is not implemented to confirm to
job or the specified receive same request for multiple times or the activity
activity name is incorrect. name configured in the confirm activity is
correct.

78 | Core

Code
s
TIBC The reply operation The operation

O- [com.tibco.bw.runtime.EventCont [com.tibco.bw.runtime.EventContext.reply(..)]
BW- ext.reply(..)] is not supported for is not allowed for the specified activity and
COR the activity [{0}], in process [{1}], this is an implementation error.
E- module [{2}:{3}], application [{4}:
50009 {5}].
0
TIBC Invalid argument value. The BW The BusinessWorks Application specified for
O- Application name cannot be null. this operation can not be null or empty.
BW- Ensure valid application name is specified for
COR this operation.
E-
50009
1
TIBC Unable to get BW Process Error occurred when obtaining the process
O- instances information for the BW instance details for the specified
BW- Application [{0}] due to exception BusinessWorks application.
COR [{1}].
E-
50009
2
O- instance information for the BW instance details for the specified
BW- ProcessIntanceId [{0}] due to BusinessWorks ProcessIntanceId.
COR exception [{1}].
E-
50009
3
O- instance summary information for instance details for the specified
BW- the BW ProcessIntanceId [{0}] BusinessWorks ProcessIntanceId.

79 | Core

Code
s
COR due to exception [{1}].

E-
50009
4
TIBC Failed to suspend the BW Error occurred when attempting to suspend

O- Process instance for the BW the process instance for the specified
E-
50009
5
TIBC Failed to resume the BW Process Error occurred when attempting to resume
O- instance for the BW the process instance for the specified
E-
50009
6
TIBC Failed to cancel the BW Process Error occurred when attempting to cancel the
O- instance for the BW process instance for the specified
E-
50009
7
TIBC BW AppNode name [{0}] exceeds BW AppNode name exceeds 250 characters
O- 250 characters and it is possible this is not possible create unique engine
BW- to create the internal engine alias name. Ensure AppNode name is less than
COR name. 250 characters.
E-
50009

80 | Core

Code
s
TIBC Failed to install BW Module [{0}: The BW Module did not get installed in the
O- {1}], DeploymentUnit [{2}:{3}] BW Engine, and this could be due to many
BW- reasons. For more details, refer to the
COR additional exception message or the
E- "CausedBy" statements reported as part of
50010 this error message.
2
TIBC Encountered error(s) on release- The BW Engine encountered error(s) when

O- resource operation for the BW releasing resources associated with the BW
BW- Module [{0}:{1}], DeploymentUnit Module and this could be due to many
COR [{2}:{3}] reasons. For more details, refer to the
E- additional exception message or the
50010 "CausedBy" statements reported as part of
TIBC Encountered error(s) when un- The BW Engine encountered error(s) when
O- deploying the BW Module [{0}: un-deploying the BW Module and this could
BW- {1}], DeploymentUnit [{2}:{3}] be due to many reasons. For more details,
COR refer to the additional exception message or
E- the "CausedBy" statements reported as part
50010 of this error message.
6
TIBC Failed to install BW Module [{0}: The BW Module or the process is using a
O- {1}], DeploymentUnit [{2}:{3}]. The persistence feature, module shared variable
BW- module or a process is configured with persistence option, etc..; however the
COR to utilize the BW Engine BW Engine persistence mode is not set
E- persistence feature; however the appropriately for this feature. Ensure the BW
50011 BW Engine is not configured with Engine persistence mode
0 a correct engine persistence (bw.engine.persistenceMode) is set to
mode. Ensure the BW Engine is "datastore" or "group" and the required
configured for the engine engine database configuration is specified.

81 | Core

Code
s
persistence mode [datastore] or

[group] before installing this
module.
TIBC Failed to start BW Module due to This error is reported when the BW Activity in
O- an activity start error. CausedBy the process fails to initialize and start. For
BW- more details, refer to the additional exception
50011
2
TIBC Unable to obtain Failed to obtain SchemaComponentCache

O- SchemaComponentCache for the schema required by the BW Module
BW- (Namespace={0}, Location={1}, and this could be due to many reasons. For
COR BaseURI={2}) for BW Module [{3}: more details, refer to the additional exception
E- {4}] due to exception [{5}] message or the "CausedBy" statements
50011 reported as part of this error message.
7
TIBC Unable to add schema to Failed to add schema required by the BW

O- SchemaComponentCache Module to SchemaComponentCache and
BW- (Namespace={0}, Location={1}) this could be due to many reasons. For more
COR due to exception [{2}] details, refer to the additional exception
E- message or the "CausedBy" statements
8
TIBC Unable to obtain WSDL Failed to get the WSDL ModuleCache

O- ModuleCache (Namespace={0}, required by the BW Module.
BW- Location={1}) for BW Module [{2}:
COR {3}]. The WSDLCacheService
E- operation [{4}] returned "null".
50011
9

82 | Core

Code
s
TIBC Unable to obtain WSDL Failed to get the WSDL ModuleCache for the
O- ModuleCache (Namespace={0}, WSDL required by the BW Module.
BW- Location={1}) for BW Module [{2}:
COR {3}]. The WSDLCacheService
E- operation [{4}] returned "null".
50012
1
TIBC Unable to obtain WSDL Failed to get the WSDL ModuleCache for the
O- ModuleCache (Namespace={0}, WSDL required by the BW Module and this
BW- Location={1}) for BW Module [{2}: could be due to many reasons. For more
COR {3}]. The WSDLCacheService details, refer to the additional exception
E- operation [{4}] returned exception message or the "CausedBy" statements
50012 [{5}] reported as part of this error message.
2
TIBC Unable to resolve Schema Failed to resolve the schema required by the
O- (Namespace={0}, Location={1}, BW Module. Ensure the schema is valid, the
BW- BaseURI={2}) for BW Module [{3}: schemas imported/referenced by this
COR {4}]. The SchemaCacheService schema are valid, the schemaLocation of the
E- operation [{5}] returned "null". schemas imported by this schema is valid,..
50012
3
TIBC Invalid or empty file name is The module shared variable or the job shared
O- specified for the initial value of the variable contains incorrect value or is empty.
BW- {0} [{1}] in BW Module [{2}:{3}], Ensure the module or the job shared variable
COR DeploymentUnit [{4}:{5}]. has been initialized or assigned with a correct
E- value.
50013
1
TIBC The file [{0}] configured for the The module shared variable or the job shared
O- initial value of the {1} [{2}] is not variable has been initialized with a file URL
BW- found in BW Module [{3}:{4}], that is not found in the BW Module. Ensure

83 | Core

Code
s
COR DeploymentUnit [{5}:{6}]. the specified file name is valid or the file is
E- contained within the BW Module.
50013
2
TIBC Unable to access the file [{0}] Failed to access the file specified in the
O- configured for the initial value of module or job shared variable and this could
BW- the {1} [{2}] in BW Module [{3}: be due to many reasons. For more details,
COR {4}], DeploymentUnit [{5}:{6}]; refer to the additional exception message or
E- encountered exception [{7}]. the "CausedBy" statements reported as part
3
TIBC Unable to open the file [{0}] Failed to open the file specified in the module
O- configured for the initial value of or job shared variable and this could be due
BW- the {1} [{2}] in BW Module [{3}: to many reasons. For more details, refer to
COR {4}], DeploymentUnit [{5}:{6}]; the additional exception message or the
E- encountered exception [{7}]. "CausedBy" statements reported as part of
4
TIBC Unable to read the file [{0}] Failed to read the file specified in the module
O- configured for the initial value of or job shared variable and this could be due
BW- the {1} [{2}] in BW Module [{3}: to many reasons. For more details, refer to
COR {4}], DeploymentUnit [{5}:{6}]; the additional exception message or the
E- encountered exception [{7}]. "CausedBy" statements reported as part of
5
TIBC The contents of the file [{0}] Ensure the file specified for the module or job
O- configured for the initial value of shared variable is not empty.
BW- the {1} [{2}] in BW Module [{3}:
COR {4}], DeploymentUnit [{5}:{6}] is
E- empty.
50013

84 | Core

Code
s
TIBC Invalid BW Module property. The Ensure the module property correctly defined
O- module property [{0}] is not in the BW Module.
BW- defined in the BW Module [{1}:
COR {2}], DeploymentUnit [{3}:{4}].
E- Therefore the XPath function
50014 "getModuleProperty({5})"
1 contained in the XSLT is not able
to resolve this module property.
TIBC Unable to resolve the BW Module Ensure the module property correctly defined
O- property [{0}] defined in the BW in the BW Module.
BW- Module [{1}:{2}], DeploymentUnit
COR [{3}:{4}] via the XPath function
E- "getModuleProperty({5})"
50014 contained in the XSLT.
2 Encountered exception [{6}].
TIBC Failed to create Binding Encountered errors when creating the

O- ReferenceEndpoint for the binding endpoint for the BW process
BW- process reference [{0}] in process reference and and this could be due to many
COR [{1}], module [{2}:{3}], reasons. For more details, refer to the
E- DeploymentUnit [{4}:{5}]; additional exception message or the
50014 encountered exception [{6}] "CausedBy" statements reported as part of
TIBC Failed to obtain module properties BW framework layer encountered errors

O- for the module [{0}:{1}], when accessing module properties for the
BW- DeploymentUnit [{2}:{3}]; specified BW Module. Contact TIBCO
COR encountered exception [{4}] Support.
E-
50014
4

85 | Core

Code
s
TIBC Unable to obtain WSDL Interface Error occurred when attempting to obtain
O- details for the PortType [{0}], that WSDL details for the specified PortType, and
BW- is associated with the BW Module this could be due to many reasons. For more
COR [{1}:{2}]. Encountered exception details, refer to the additional exception
E- [{3}] message or the "CausedBy" statements
5
TIBC Failed to install BW Component The BW Component did not get installed in
O- [{0}], Application [{1}:{2}] the BW Engine, and this could be due to
BW- many reasons. For more details, refer to the
2
TIBC Failed to install BW Component The BusinessWorks application or the

O- [{0}], Application [{1}:{2}]. The component in the application is configured to
BW- application is configured with Job use the Job PageThreshold property
COR PageThreshold property [bw.application.job.pageThreshold.*] and this
E- [bw.application.job.pageThreshol requires the BW Engine to be configured for
50020 d.*]; however the BW Engine is the "datastore" or "group" persistence mode.
3 not configured with a correct Stop the BusinessWorks AppSpace,
engine persistence mode. Ensure configure the BW Engine for the engine
the BW Engine is configured for persistence mode [datastore] or [group] and
the engine persistence mode restart the AppSpace before installing the
[datastore] or [group] before application.
installing this application.
TIBC Encountered error(s) on release- Error occurred when releasing the resources
O- resource operation for the BW associated with the BW Component, and this
BW- Component [{0}], Application [{1}: could be due to many reasons. For more
COR {2}] details, refer to the additional exception

86 | Core

Code
s
TIBC Encountered error(s) when un- Error occurred when un-deploying the BW
O- deploying the BW Component Component and this could be due to many
BW- [{0}], Application [{1}:{2}] reasons. For more details, refer to the
1
TIBC Failed to initialize BW Component Error occurred when initializing the BW

O- [{0}], Application [{1}:{2}] Component and this could be due to many
2
TIBC Failed to initialize BW Component Error occurred when creating an instance of

O- [{0}], Application [{1}:{2}] due to an activity that is associated with the BW
BW- activity creation error Component; therefore the BW Component
COR can not be initialized. For more details, refer
E- to the additional exception message or the
TIBC Failed to initialize BW Component There is a configuration error in the activity or

O- [{0}], Application [{1}:{2}] due to resource that is associated with the BW
BW- activity or resource configuration Component; therefore the BW Component
COR error can not be initialized. For more details, refer
TIBC Failed to initialize BW Component There are implementation errors in the

87 | Core

Code
s
O- [{0}], Application [{1}:{2}] due to activity that is associated with the BW

BW- activity implementation error Component; therefore the BW Component
COR can not be initialized. For more details, refer
TIBC Failed to initialize BW Component Error occurred when initializing an activity

O- [{0}], Application [{1}:{2}] due to that is associated with the BW Component;
BW- activity initialization error therefore the BW Component can not be
COR initialized. For more details, refer to the
TIBC Encountered error when Error occurred when destroying or deleting

O- destroying the BW Component the BW Component and this could be due to
BW- [{0}] many reasons. For more details, refer to the
8
TIBC Encountered errors when Error occurred when destroying or deleting

O- destroying the BW Component the BW Component and this could be due to
BW- [{0}] many reasons. For more details, refer to the
0
TIBC Failed to start BW Component Error occurred when starting the BW

O- [{0}], Application [{1}:{2}] Component and this could be due to many

88 | Core

Code
s

2
TIBC Encountered error(s) when Error occurred when stopping the BW

O- stopping the BW Component [{0}], Component and this could be due to many
BW- Application [{1}:{2}] reasons. For more details, refer to the
6
TIBC Encountered error(s) when Error occurred when starting the

O- starting the ProcessStarter ProcessStarter activity that is associated with
BW- associated with the BW the BW Component. For more details, refer
COR Component [{0}], Application [{1}: to the additional exception message or the
E- {2}] "CausedBy" statements reported as part of
8
TIBC Encountered error(s) when Error occurred when stopping the

O- stopping the ProcessStarter ProcessStarter activity that is associated with
BW- associated with the BW the BW Component. For more details, refer
COR Component [{0}], Application [{1}: to the additional exception message or the
E- {2}] "CausedBy" statements reported as part of
0
TIBC Failed to start ServiceBinding [{0}] Error occurred when starting the
O- for the BW Component [{1}], ServiceBinding that is associated with the
BW- Application [{2}:{3}] due to BW Component. For more details, refer to
COR ServiceBinding lifecycle error the additional exception message or the
2

89 | Core

Code
s
TIBC Unable to stop ServiceBinding Error occurred when stopping the

O- [{0}] for the BW Component [{1}], ServiceBinding that is associated with the
BW- Application [{2}:{3}] due to BW Component. For more details, refer to
COR ServiceBinding lifecycle error the additional exception message or the
4
TIBC The job flow limit property [{0}] for The BW application or component's job flow
O- the application or the component limit property is configured with an incorrect
BW- is configured incorrectly. Ensure value. The job flow limit property value must
COR the job flow limit property value is be an integer that is greater than zero.
E- set to an integer that is greater
50025 than zero.
6
TIBC The job priority property [{0}] for The BW application or component's job
O- the application or the component priority property is configured with an
BW- is configured incorrectly. Ensure incorrect value. The job priority property can
COR the job priority property value is only be configured with the string value "low",
E- set to "low", "normal" or "high". "normal" or "high".
50025
8
TIBC The property to enable activity The property that is used to determine the
O- input validation for the application enabling of the activity output validation for
BW- or the component is configured the application or the component is
COR incorrectly. Ensure properties that configured with an incorrect value. This
E- are prefixed with [{0}] are set with property can only be configured with the
50026 value "true" or "false". string value "true" or "false".
2
TIBC The property to enable activity

O- output validation for the
BW- application or the component is

90 | Core

Code
s
COR configured incorrectly. Ensure

E- properties that are prefixed with
50026 [{0}] are set with value "true" or
4 "false".
TIBC The property that specifies the The property that specifies the default wait
O- async activity default wait time is time (timeout) value for an asynchronous
BW- configured incorrectly. Ensure the activity is configured incorrectly. The value
COR property [{0}] or the properties for this property must be a zero or positive
E- prefixed with [{1}] are configured number. This property can be configured the
50026 with a zero or positive numeric AppSpace/AppNode configuration file
5 value 'config.ini'
TIBC Failed to start BW Application [{0}] The BW Application did not start and this
O- due to exception [{1}] could be due to many reasons. For more
BW- details, refer to the additional exception
50030
2
TIBC Failed to start BW Application [{0}: Error occurred in an activity that is associated
O- {1}] due to an activity error with the BW Application; therefore the BW
BW- Application did not start. For more details,
4
TIBC Encountered error when Error occurred when attempting to gracefully

O- attempting to gracefully stop BW stop the BW Application and this could be
BW- Application [{0}:{1}] due to many reasons. For more details, refer
COR to the additional exception message or the

91 | Core

Code
s
TIBC The BW Application [{0}:{1}] is The BW Application is already in stopped

O- already in stopping state. Unable state; therefore it can not be stopped again.
BW- to perform operation
COR "stopApplicationGraceful"
E-
50030
7
TIBC Encountered error when Error occurred when attempting to stop the
O- attempting to stop BW Application BW Application and this could be due to
BW- [{0}:{1}] many reasons. For more details, refer to the
8
TIBC Encountered errors when

O- attempting to stop BW Application
BW- [{0}:{1}]
COR
E-
50031
0
TIBC Unable to start ServiceBinding(s) Error occurred when attempting to start the
O- or ProcessStarter(s) associated ServiceBinding(s) or ProcessStarter(s)
BW- with the BW Application [{0}:{1}] activity that is associated with the BW
COR Application. For more details, refer to the
TIBC Unable to stop ServiceBinding(s) Error occurred when attempting to stop the

92 | Core

Code
s
O- or ProcessStarter(s) associated ServiceBinding(s) or ProcessStarter(s)

BW- with the BW Application [{0}:{1}] activity that is associated with the BW
COR Application. For more details, refer to the
TIBC Encountered error when Error occurred when attempting to resume

O- attempting to pause BW the BW Application. For more details, refer to
BW- Application [{0}:{1}] job(s) the additional exception message or the
50031
6
TIBC Encountered error when

O- attempting to resume BW
BW- Application [{0}:{1}] job(s)
COR
E-
50031
8
TIBC Failed to create the Error occurred when attempting to create an

O- ProcessStarter activity [{0}] in instance of the ProcessStarter activity in a
BW- process [{1}], module [{2}] due to process. For more details, refer to the
COR exception [{3}] additional exception message or the
2
TIBC Failed to create the Unexpected error occurred when attempting

O- ProcessStarter activity [{0}] in to create an instance of the ProcessStarter
BW- process [{1}], module [{2}] due to activity in a process. For more details, refer
COR unexpected exception [{3}] to the additional exception message or the

93 | Core

Code
s

4
TIBC Failed to initialize the Error occurred when attempting to initialize

O- ProcessStarter activity [{0}] in an instance of the ProcessStarter activity in a
BW- process [{1}], module [{2}] due to process. For more details, refer to the
COR activity lifecycle error additional exception message or the
6
TIBC Failed to initialize the Unexpected error occurred when attempting

O- ProcessStarter activity [{0}] in to initialize an instance of the ProcessStarter
BW- process [{1}], module [{2}] due to activity in a process. For more details, refer
COR unexpected activity lifecycle error to the additional exception message or the
8
TIBC Failed to start the ProcessStarter Error occurred when attempting to start the
O- activity [{0}] in process [{1}], ProcessStarter activity in a process. For
BW- module [{2}] due to activity more details, refer to the additional exception
COR lifecycle error message or the "CausedBy" statements
50041
0
TIBC Failed to start the ProcessStarter Unexpected error occurred when attempting
O- activity [{0}] in process [{1}], to start the ProcessStarter activity in a
BW- module [{2}] due to unexpected process. For more details, refer to the
COR activity lifecycle error additional exception message or the
2

94 | Core

Code
s
TIBC The stop operation for the Unexpected error occurred when attempting
O- ProcessStarter activity [{0}] in to stop the ProcessStarter activity in a
BW- process [{1}], module [{2}] failed process. The ProcessStarter activity stop
COR with unexpected exception [{3}] operation
E- "com.tibco.bw.runtime.EventSource.stop()"
50041 failed and returned unexpected exception.
4 The ProcessStarter stop operation must not
raise a fault and it is considered to be a
ProcessStarter activity implementation error.
TIBC The destroy operation for the Unexpected error occurred when attempting
O- ProcessStarter activity [{0}] in to destroy the ProcessStarter activity in a
BW- process [{1}], module [{2}] failed process. For more details, refer to the
COR with unexpected exception [{3}] additional exception message or the
6
TIBC The release operation for the Unexpected error occurred when attempting
O- ProcessStarter activity [{0}] in to release resources for the ProcessStarter
BW- process [{1}], module [{2}] failed activity in a process. For more details, refer
COR with unexpected exception [{3}] to the additional exception message or the
8
TIBC Failed to process the event from BWEngine failed to process the new events
O- the ProcessStarter activity [{0}] from the ProcessStarter activity. For more
BW- details, refer to the additional exception
50042
0
TIBC Failed to execute event from the This error message is reported when the

95 | Core

Code
s
O- ProcessStarter activity due to output data generated by the ProcessStarter

BW- activity output data validation activity does not comply with the output
COR error. The output data from schema of the ProcessStarter activity. This
E- ProcessStarter activity [{0}] does error can occur if ProcessStarter activity is
50042 not conform to the ProcessStarter not implemented correctly to generate the
2 activity output schema. Validation valid output data.
error details: {1}.
TIBC The BWEngine is unable accept The ProcessStarter generated new events
O- new events from the when it is in the stopped state. A
BW- ProcessStarter activity [{0}], in ProcessStarter must not generate new
COR process [{1}], module [{2}] since events during the stopped state and it will be
E- the ProcessStarter is in the considered as ProcessStarter activity
50042 stopped sate. When the implementation error. The ProcessStarter is
4 ProcessStarter is in the stopped in the stopped state once the BWEngine
state, the BWEngine will not invokes the ProcessStarter operation
accept new events. "com.tibco.bw.runtime.EventSource.stop" or
before the invocation of the ProcessStarter
operation
"com.tibco.bw.runtime.EventSource.start".
TIBC The model or the runtime class for This error message is generated if the BW
O- the activity [{0}] in process [{1}], activity is not implemented correctly. Ensure
BW- module [{2}] is implemented the BW activity model class contains the
COR incorrectly. The activity model required attribute or property.
E- class [{3}] does not contain the
50060 configuration property [{4}] as
2 defined in the annotation for the
member variable [{5}] declared in
the activity runtime class [{6}].
TIBC The model or the runtime class for

O- the activity [{0}] in process [{1}],
BW- module [{2}] is implemented
COR incorrectly. The activity model

96 | Core

Code
s
E- [{3}] does not contain the attribute

50060 [{4}] as defined in the annotation
3 for the member variable [{5}]
declared in the activity runtime
class [{6}]. The attribute must be
one of the following that is
specified in the activity model [{7}]
TIBC The model or runtime class for the This error message is generated if the BW
O- activity [{0}] in process [{1}], activity is not implemented correctly. Ensure
BW- module [{2}] is implemented the BW activity model class contains the
COR incorrectly. The activity model property of a supported data type.
E- class [{3}] associated with the
50060 activity runtime class [{4}] has a
4 configuration property which is of
unsupported data type. The
activity configuration property
data type [{5}] is not supported.
TIBC The model or runtime class for the This error message is generated if the BW
O- activity [{0}] in process [{1}], activity is not implemented correctly. Ensure
BW- module [{2}] is implemented the BW activity runtime class member
COR incorrectly. Unable to set member variable is defined correctly.
E- variable [{3}] declared in the
50060 activity runtime class [{4}].
5 Encountered exception [{5}].
TIBC The resource specified for the A resource assigned to the process property
O- process property [{0}] in process is not accessible or resolvable at runtime.
BW- [{1}], module [{2}] is not available Ensure the process property is configured
COR in the runtime environment. This correctly and the required resource is
E- process property is used by the resolvable at runtime.
50060 activity [{3}] in process [{4}].
6 Ensure the resource is configured
and installed correctly.

97 | Core

Code
s
TIBC The process property [{0}] in The process property is configured with a
O- process [{1}], module [{2}] has an incorrect value. Ensure the process property
BW- incorrect value [{3}]. This process is configured correctly, specially for a
COR property is used by the activity DateTime data type.
E- [{4}] in process [{5}]. For
50060 DateTime, ensure the value has
7 the format [{6}].
TIBC The resource obtained from the The value assigned to the process property
O- framework for the process did resolve to the data type excepted by the
BW- property [{0}] in process [{1}], process property . Ensure the process
COR module [{2}] is not compatible with property contains the correct value or the
E- the data type of the process module property assigned to the process
50060 property. Encountered exception property is contains the correct value.
8 [{3}].
TIBC One or more required fields of the The activity is not configured correctly.
O- activity [{0}] in process [{1}], Ensure the all required fields for the activity
BW- module [{2}] is not configured at design time are populated correctly.
COR correctly. Ensure the required
E- fields of the activity contains valid
50061 data.
0
TIBC Failed to create the activity [{0}] in Unexpected error occurred when attempting
O- process [{1}], module [{2}] due to to create an instance of an activity. For more
BW- exception [{3}] details, refer to the additional exception
50061
2
TIBC Failed to create the activity [{0}] in

O- process [{1}], module [{2}] due to
BW- unexpected exception [{3}]

98 | Core

Code
s
COR
E-
50061
4
TIBC Failed to initialize the activity [{0}] Error occurred when attempting to initialize
O- in process [{1}], module [{2}] due an instance of an activity. For more details,
BW- to activity lifecycle error refer to the additional exception message or
COR the "CausedBy" statements reported as part
E- of this error message.
50061
6
TIBC Failed to initialize the activity [{0}] Unexpected error occurred when attempting
O- in process [{1}], module [{2}] due to initialize an instance of an activity. For
BW- to unexpected activity lifecycle more details, refer to the additional exception
COR error message or the "CausedBy" statements
50061
8
TIBC The execute operation for the The activity execution failed and raised an
O- activity [{0}] in process [{1}] failed unexpected exception. For more details, refer
BW- with unexpected exception [{2}] to the additional exception message or the
50062
0
TIBC The post-execute operation for The post-execute operation for an

O- the asynchronous activity [{0}] in asynchronous activity failed and raised an
BW- process [{1}] failed with unexpected exception. For more details, refer
COR unexpected exception [{2}] to the additional exception message or the

99 | Core

Code
s
TIBC The cancel operation for the The cancel operation for an asynchronous
O- activity [{0}] in process [{1}], activity failed and raised an unexpected
BW- module [{2}] failed with exception. For more details, refer to the
COR unexpected exception [{3}] additional exception message or the
4
TIBC BWEngine was unable to execute BWEngine encountered error when

O- cancel operation for the activity attempting to execute cancel operation for
BW- [{1}] in process [{2}], module [{3}] the activity. For more details, refer to the
COR due to exception [{4}] additional exception message or the
6
TIBC The destroy operation for the The destroy operation for an activity failed
O- activity [{0}] in process [{1}], and raised an unexpected exception. For
BW- module [{2}] failed with more details, refer to the additional exception
COR unexpected exception [{3}] message or the "CausedBy" statements
50062
8
TIBC The process property [{0}] is not Unable to resolve the specified process
O- defined in the BW Process [{1}] property. Ensure this process property is
BW- correctly defined in the BW Process.
COR
E-
50063
0
TIBC The process property [{0}] has not The specified process property has not been

100 | Core

Code
s
O- been registered with the activity correctly registered with the activity context.
BW- context or the event source This error can occur if the BW activity is not
COR context. implemented correctly to register the process
E- property via method
50063 [com.tibco.bw.runtime.ActivityContext.registe
1 rProcessProperty].
TIBC Failed to resolve process property Failed to resolve the specified process
O- [{0}] from the BW Process [{1}] property. Ensure the specified process
BW- property is defined in the process. For more
COR details, refer to the additional exception
E- message in the cause.
50063
2
TIBC The module property [{0}] is not Unable to resolve the specified module
O- defined in the BW Module [{1}:{2}] property. Ensure this module property is
BW- correctly defined in the BW Module.
COR
E-
50063
3
TIBC The module property [{0}] has not The specified module property has not been
O- been registered with the activity correctly registered with the activity context.
BW- context or the event source This error can occur if the BW activity is not
COR context. implemented correctly to register the module
E- property via method
50063 [com.tibco.bw.runtime.ActivityContext.registe
4 rModuleProperty].
TIBC Failed to resolve module property Failed to resolve the specified module
O- [{0}] from the BW Module [{1}:{2}] property. Ensure the specified module
BW- property is defined in the module. For more
COR details, refer to the additional exception

101 | Core

Code
s

5
TIBC Activity [{0}] timed out. The activity wait or execution time has
O- exceeded the timeout value specified for the
BW- activity.
COR
E-
50063
6
TIBC Activity input data validation error. This error message is reported when the data
O- The input data for activity [{0}] in that is provided as an input to the activity
BW- process [{1}], module [{2}] does does not comply with the input schema of the
COR not conform to the activity input activity. This error can occur if the previous
E- schema. {3} {4} activity in the process generated incorrect
50063 data or the activity input XSLT transformation
8 generated data that does not comply with the
input schema of the activity.
TIBC Activity output data validation This error message is reported when the
O- error. The output data from output data generated by the activity does
BW- activity [{0}] in process [{1}], not comply with the output schema of the
COR module [{2}] does not conform to activity. Some activities can generate in-
E- the activity output schema. {3} {4} compliant output if it receives incorrect data
50064 from the external entity it is interacting. In
0 these scenarios, ensure the external entity
provides or returns the correct data excepted
by the activity.
TIBC Activity input/output data This error message is reported when the data
O- validation error. The input/output that is provided as an input to the activity or
BW- data for activity [{0}] in process the output data generated by the activity
COR [{1}], module [{2}] does not does not comply with the output schema of

102 | Core

Code
s
E- conform to the activity the activity.

50064 input/output schema. {3} {4}
1
TIBC Unable to obtain activity input This error message is reported when an
O- data. The BW Engine has not entity such as the event subscriber attempts
BW- been initialized or started. to obtain an activity input data before the BW
COR Engine has been initialized or started. Ensure
E- the BW Engine has started before performing
50064 this operation.
2
TIBC Unable to obtain activity input This error message is reported when an
O- data. The specified ActivityEvent entity such as the event subscriber attempts
BW- object is invalid, the ActivityEvent to obtain an activity input data; however the
COR can not be null. specified ActivityEvent
E- (com.tibco.bw.runtime.event.ActivityAuditEve
50064 nt) object is invalid or null. Ensure the
3 ActivityEvent object is valid.
TIBC Unable to obtain activity input Unexpected error occurred when an entity
O- data due to exception [{0}] such as the event subscriber is attempting to
BW- obtain activity input data. For more details,
4
TIBC Unable to obtain activity output This error message is reported when an
O- data. The BW Engine has not entity such as the event subscriber attempts
BW- been initialized or started. to obtain an activity output data before the
COR BW Engine has been initialized or started.
E- Ensure the BW Engine has started before
50064 performing this operation.
5

103 | Core

Code
s
TIBC Unable to obtain activity output This error message is reported when an
O- data. The specified ActivityEvent entity such as the event subscriber attempts
BW- object is invalid, the ActivityEvent to obtain an activity output data; however the
COR can not be null. specified ActivityEvent
E- (com.tibco.bw.runtime.event.ActivityAuditEve
50064 nt) object is invalid or null. Ensure the
6 ActivityEvent object is valid.
TIBC Unable to obtain activity output Unexpected error occurred when an entity
O- data due to exception [{0}] such as the event subscriber is attempting to
BW- obtain activity output data. For more details,
7
TIBC Unable to obtain XPath functions Error was encountered when attempting to
O- associated with the obtain the list of XPath functions associated
BW- BusinessWork Activity, with the BW Activity.
COR encountered exception [{0}]
E-
50064
8
TIBC Unable to find process BWEngine is not able to obtain process

O- information for process [{0}] in information for the specified BW process.
BW- module ModuleName={1}, Ensure the BW Module contains the required
COR ModuleVersion={2}. process.
E-
50070
5
Design Time Error Codes

This section describes the error messages that can be reported at design time.

104 | Core
TIBCO-BW-DT- Cyclic reference detected Inspect the reference binding on the

VALIDATION- in process {0}. Reference process. BWEngine does not support
500023 {1} points to {2}. This references that point to the same
might cause the process. This reference needs to be
application to reach removed. Point to another process/sub
impaired state at runtime. process to correct this.
TIBCO-BW-DT- One or more sources Delete existing links and create links
VALIDATION- mapped for activity {0} again before deploying to runtime.
500024 contain invalid references.
TIBCO-BW-DT- Process configuration Remove this variable or quick fix.

VALIDATION- error. The variable with
500025 name [ {0}] is no longer
being referenced in the
process [{1}] .
TIBCO-BW-DT- External Shared Module Not applicable.

VALIDATION- error. The Module [{0} ] is
500026 out of sync. It is not
present on the current
Target Definition.
TIBCO-BW-DT- Folder : '' {0} '' contains Replace the special characters with
VALIDATION- special characters. alphanumeric characters, ''-'', ''_'', or
500027 whitespaces.
BW_ The Bundle-Version of Not applicable.

VALIDATION_ BusinessWorks module
MODULE-_ [{0}] must end with
VERSION_ .qualifier in the manifest
CONFIG_ERROR- file [META-
500620 INF/MANIFEST.MF]
APPLICATION_ The Bundle-Version of Not aplicable.

MANIFEST_ Application [{0}] must end
VERSION_ with .qualifier in the

105 | Core
ERROR-501005 manifest file [META-

INF/MANIFEST.MF].

106 | Palettes
Palettes
This section describes the error messages that can be reported by the activities or
entities associated with palettes.
File Palette Error Codes

entities associated with the File palette.
TIBCO-BW- {0} This is an internal product error.

PALETTE- Contact TIBCO Support.
FILE-000001
TIBCO-BW- {0} This is a trace message and

PALETTE- resolution is not applicable.
FILE-100001
TIBCO-BW- {0} This is a debug message and

FILE-200001
TIBCO-BW- {0} This is an informational message

PALETTE- and it highlights the runtime
FILE-300001 progress of the activity.
Resolution is not applicable.
TIBCO-BW- {0} This is a warning message and it

PALETTE- highlights situations that may
FILE-400001 affect the activity execution.
TIBCO-BW- File name [{0}] is not valid. Ensure that file name must not be
PALETTE- empty or null string.

107 | Palettes
FILE-500000
TIBCO-BW- File [{0}] was not found. Ensure that File indicated by
PALETTE- fileName exists at the given
FILE-500001 location.
TIBCO-BW- File [{0}] already exists. Ensure the Overwrite checkBox

PALETTE- on general tab is checked or
FILE-500002 delete the already existing file.
TIBCO-BW- An exception [{0}] occurred when Ensure the file name is valid and
PALETTE- attempting to write to the file [{1}]. the access permissions are set
FILE-500003 appropriately.
TIBCO-BW- Unable to create file [{0}] due to file or Ensure the

PALETTE- directory denoted by the pathname createNonExistingDirectory option
FILE-500004 [{1}] does not exist. on general tab is checked.
TIBCO-BW- Cannot read the binary content from Ensure the file name is valid and
PALETTE- the file [{0}]. the access permissions are set
TIBCO-BW- Cannot read the string content from Ensure the file name is valid and
PALETTE- the file [{0}]. the access permissions are set
TIBCO-BW- The file encoding [{0}] is not valid. Ensure the encoding provided is
PALETTE- valid.
FILE-500007
TIBCO-BW- Unable to rename the file from [{0}] to Ensure the file or directory name
PALETTE- file [{1}]. is valid and the access
FILE-500009 permissions are set appropriately.
TIBCO-BW- Unable to rename the file from [{0}] to Ensure the source file and
PALETTE- file [{1}]. The destination file exists destination file both are of same
FILE-500010 and its type is different then the type type.

108 | Palettes
of the source file.
TIBCO-BW- The file activity [{0}] cannot be used to Ensure the directories can't be
PALETTE- move a directory. moved unless they have same
FILE-500011 parent Directory.
TIBCO-BW- Cannot remove the file [{0}]. Ensure the file or directory name
PALETTE- is valid and the access
TIBCO-BW- An exception [{0}] occurred when Ensure the file or directory name
PALETTE- attempting to create the file [{1}]. is valid and the access
TIBCO-BW- Cannot overwrite the file [{0}] to file Ensure the Overwrite checkBox
PALETTE- [{1}], when the overwrite flag is not on general tab is checked or
FILE-500014 selected in the activity configuration. delete the already existing file
explicitly.
TIBCO-BW- Cannot copy a directory [{0}] to an Ensure that source should not be
PALETTE- existing file [{1}]. a directory when destination
FILE-500015 exists and is a File.
TIBCO-BW- Cannot copy multiple files [{0}] to an Ensure that when using pattern in
PALETTE- existing file [{1}]. source it should not match with
FILE-500016 multiple files to copy into a single
destination file.
TIBCO-BW- Cannot create missing path [{0}]. Ensure the

PALETTE- createNonExistingDirectory on
FILE-500017 general tab is checked.
TIBCO-BW- Cannot copy from file [{0}] to file [{1}]. Ensure the file or directory name
PALETTE- is valid and the access
TIBCO-BW- The file name value provided for the Ensure that fileName must not be

109 | Palettes
PALETTE- activity input is empty or null. empty or null string.

FILE-500019
TIBCO-BW- File [{0}] was not found due to fault Ensure that File indicated by
PALETTE- [{1}]. fileName exists at the given
FILE-500020 location.
TIBCO-BW- The ProcessStarter activity [{0}] failed This is an internal product error.
PALETTE- to a generate a new event due to Contact TIBCO Support.
FILE-500502 exception [{1}].
TIBCO-BW- The File Poller ProcessStarter activity This is an internal product error.
PALETTE- [{0}] failed to a generate a new event Contact TIBCO Support.
FILE-500021 due to exception [{1}] since it is in the
stopped state.
FTP Palette Error Codes

entities associated with the FTP palette.
TIBCO-BW- Unable to establish FTP connection Ensure FTP Connection

PALETTE- for the FTP function [{0}]. parameters are set properly.
FTP-500003 Encountered error [{1}].
TIBCO-BW- File [{0}] already exists. Ensure Overwrite Existing File

PALETTE- check box is checked or delete
FTP-500004 the file on server.
TIBCO-BW- Error in PUT or MPUT command. Error in PUT or MPUT command.

PALETTE- See Fault Tab for details.
FTP-500005
TIBCO-BW- Error in GET or MGET command. Error in GET or MGET command.

110 | Palettes
PALETTE- See Fault Tab for details.

FTP-500006
TIBCO-BW- Client is not initialized [{0}]. Please Contact TIBCO Support

PALETTE-
FTP-500008
TIBCO-BW- Error in PUT or MPUT command. Ensure the local file is specified
PALETTE- Local file specified cannot be found for PUT or MPUT command.
FTP-500010 [{0}].
TIBCO-BW- Unexpected reply code. Returned Please Contact TIBCO Support.

PALETTE- Code [{0}]. Expected Code [{1}].
FTP-500012
TIBCO-BW- Invalid user name or password. Ensure user name or password is

PALETTE- valid.
FTP-500013
TIBCO-BW- Error in executing remote command Please Contact TIBCO Support.

PALETTE- [{0}].
FTP-500014
TIBCO-BW- FTP Connection Test Failed. Ensure user name or password is

PALETTE- Encountered error [{0}]. valid.
FTP-500019
TIBCO-BW- File [{0}] does not exist. Ensure File exist at given location.
PALETTE-
FTP-500020
TIBCO-BW- Error establishing active data socket. Please Contact TIBCO Support.
PALETTE- Reason [{0}].
FTP-500022
TIBCO-BW- Error performing mget. Reason: Please Contact TIBCO Support.

PALETTE- mget is not supported for FTP via

111 | Palettes
FTP-500024 Proxy
TIBCO-BW- Error in PUT or MPUT Error in PUT or MPUT command.

PALETTE- command.Error:[{0}]. See Fault Tab for details.
FTP-500025
TIBCO-BW- Error in GET or MGET Error in GET or MGET command.

PALETTE- command.Error:[{0}]. See Fault Tab for details.
FTP-500026
General Palette Error Codes

entities associated with the General Activities palette.
TIBCO-BW-PALETTE- Activity configuration error. The

GENERALACTIVITIES- end time must be greater than
VALIDATION-500001 start time for Timer activity [{0}]
in the process [{1}].
TIBCO-BW-PALETTE- The Timer ProcessStarter This is an internal product

GENERALACTIVITIES- activity [{0}] failed to generate a error. Contact TIBCO
000001 new event due to exception Support.
[{1}]
TIBCO-BW-PALETTE- {0} This is a trace message

GENERALACTIVITIES- and resolution is not
100001 applicable.
TIBCO-BW-PALETTE- {0} This is a debug message

GENERALACTIVITIES- and resolution is not
200001 applicable.
TIBCO-BW-PALETTE- {0} This is an informational

112 | Palettes
GENERALACTIVITIES- message and it highlights

300001 the runtime progress of the
activity. Resolution is not
applicable.
TIBCO-BW-PALETTE- {0} This is a warning message

GENERALACTIVITIES- and it highlights situations
400001 that may affect the activity
execution.
TIBCO-BW-PALETTE- Error executing external Ensure the activity is

GENERALACTIVITIES- command [{0}]: [{1}]. configured correctly.
500000
TIBCO-BW-PALETTE- Error accessing file or directory Ensure the file or directory

GENERALACTIVITIES- [{0}]: [{1}]. name is valid and the
500001 access permissions are set
appropriately.
TIBCO-BW-PALETTE- No command specified. Ensure the specified field in

GENERALACTIVITIES- the activity input is
500002 configured with the correct
data.
TIBCO-BW-PALETTE- Input data error in field [{0}]

GENERALACTIVITIES- expecting a valid [{1}]
500003
TIBCO-BW-PALETTE- Sleep interval value [{0}] is not Ensure the sleep interval is
GENERALACTIVITIES- valid. a positive long value.
500004
TIBCO-BW-PALETTE- Activity configuration error. The

GENERAL-ACTIVITIES- {2} Shared Variable must be
500001 configured for {3} Shared
Variable activity [{0}] in the
process [{1}].

113 | Palettes
HTTP Palette Error Codes

entities associated with the HTTP palette.
TIBCO-BW- {0} This is an internal product

PALETTE- error. Contact TIBCO
HTTP- Support.
000001
TIBCO-BW- {0} This is a trace message and

HTTP-
100001
TIBCO-BW- {0} This is a debug message

PALETTE- and resolution is not
HTTP- applicable.
200001
TIBCO-BW- {0} This is an informational

PALETTE- message and it highlights
HTTP- the runtime progress of the
300001 activity. Resolution is not
applicable.
TIBCO-BW- {0} This is a warning message

PALETTE- and it highlights situations
HTTP- that may affect the activity
400001 execution.
TIBCO-BW- The Http Server replied with a [{0}] status Check the status code to
PALETTE- code. know the reason for the
HTTP- error.
500001
TIBCO-BW- The Http Server replied with a [{0}] status Check the status code to
PALETTE- code know the reason for the

114 | Palettes
HTTP- error.
500002
TIBCO-BW- An exception was thrown while trying to Correct the configuration of

PALETTE- initialize the Http client Send Http Request activity.
HTTP-
500003
TIBCO-BW- An exception occurred while trying to Check the exception and

PALETTE- initialize the Http server: [{0}] correct the configuration of
HTTP- Http Connector resource or
500004 Http ProcessStarter.
TIBCO-BW- A POST Method cannot send parameters if Correct the input data of
PALETTE- the message body is specified Send Http Request
HTTP- activity.Make sure message
500005 body is not specified when
parameters are used.
TIBCO-BW- A GET Method doesn't have a message Correct the input data of
PALETTE- body Send Http Request activity.
HTTP- Make sure that the message
500006 body is not specified for a
GET request.
TIBCO-BW- Invalid endpoint URL Correct either the http client

PALETTE- configuration or the input
HTTP- data of Send Http Request
500007 activity.
TIBCO-BW- Invalid input data. The encoding is not Correct the input data. Make
PALETTE- supported sure the encoding is
HTTP- supported. See the
500008 documentation.
TIBCO-BW- The http method [{0}] is not valid Correct the input data of
PALETTE- Send Http Request activity.

115 | Palettes
HTTP- Make sure that the HTTP

500009 method is valid.
TIBCO-BW- An exception was thrown while trying to url- Correct the input data. See
PALETTE- encode the data the documentation.
HTTP-
500010
TIBCO-BW- Attachment not supported for HTTP method Check input of Send Http
PALETTE- [{0}]. Only HTTP 'POST' can send Request activity. Only
HTTP- attachments 'POST' method can send
500011 attachments.
TIBCO-BW- Error serializing attachment data, Cause: Check the exception and
PALETTE- [{0}] correct the attachment data.
HTTP-
500012
TIBCO-BW- An IOException was thrown while trying to System exception.

PALETTE- execute the Http method
HTTP-
500013
TIBCO-BW- An exception was thrown while trying to System exception.

PALETTE- execute the Http method. The Reason-code
HTTP- is [{0}]
500014

PALETTE- read the response
HTTP-
500015

PALETTE- send the response
HTTP-
500016

116 | Palettes
TIBCO-BW- An Exception was thrown while trying to System exception.

PALETTE- send the response
HTTP-
500017
TIBCO-BW- The header [{0}] is defined as non- Correct the input data.
PALETTE- Repeating Header in Input Headers. This
HTTP- header cannot have multiple occurrences in
500019 DynamicHeaders.
TIBCO-BW- The HTTP ProcessStarter [{0}] failed to Check the exception and
PALETTE- generate a new event due to exception [{1}] correct the configuration of
HTTP- Http connector or Http
500020 Receiver.
TIBCO-BW- Failed to reply to HTTP ProcessStarter Check point activity should

PALETTE- activity. This error can occur if the HTTP not be placed between Http
HTTP- Response activity is executed after ProcessStarter and Send
500021 recovering from a check-pointed Http Response activity.
BusinessWorks process instance.
TIBCO-BW- Failed to authenticate request. Username Check if the identity

PALETTE- and Password is not set. resource referenced in Http
HTTP- Client resource contains
500022 username and password.
TIBCO-BW- Failed to authenticate request. Check if the LDAP resource

PALETTE- is configuired on Http
HTTP- Connector resource.
500022
TIBCO-BW- Value not specified for the DynamicHeader Correct the input data.
PALETTE- [{0}].
HTTP-
500023
TIBCO-BW- Reply For field cannot be blank. Select a value for Reply For

117 | Palettes
PALETTE- field in Send HTTP

HTTP- Response activity.
500024
TIBCO-BW- The circuit-breaker is open now and will Check circuit-breaker

PALETTE- short-circuit all the requests. configuration and try again.
HTTP-
500025
Java Palette Error Codes

entities associated with the Java palette.
TIBCO-BW-PALETTE- [{0}]
JAVA-
PROCESSSTARTER-
000001
JAVA-
PROCESSSTARTER-
100001
JAVA-
PROCESSSTARTER-
200001
JAVA-
PROCESSSTARTER-
300001

118 | Palettes
JAVA-
PROCESSSTARTER-
400001
TIBCO-BW-PALETTE- The JAVA ProcessStarter Ensure that the correct

JAVA- activity [{0}] failed to a generate object passed to the
PROCESSSTARTER- a new event due to exception 'onEvent' method in the
500001 [{1}] specified Java class. Please
refer to the declared class
implementation for details.
TIBCO-BW-PALETTE- Illegal onEvent(Object Remove the onEvent(Object

JAVA- output)/onError(Throwable output) method call in the init
PROCESSSTARTER- throwable) method call. method.
500002 OnEvent/OnError method must
not be called in the init method
or during the initialization
phase.
TIBCO-BW-PALETTE- The JAVA ProcessStarter Ensure that the

JAVA- activity [{0}] failed to a generate ProcessStarter has been
PROCESSSTARTER- a new event due to exception stopped properly.
500003 [{1}] since it is in the stopped
state.
TIBCO-BW-PALETTE- [{0}] This is an internal product

JAVA-000001 error. Contact TIBCO
Support.
TIBCO-BW-PALETTE- [{0}] This is a trace message and

JAVA-100001 resolution is not applicable.
TIBCO-BW-PALETTE- [{0}] This is a debug message

JAVA-200001 and resolution is not
applicable.

119 | Palettes
TIBCO-BW-PALETTE- [{0}] This is an informational

JAVA-300001 message and it highlights the
runtime progress of the
activity. Resolution is not
applicable.
TIBCO-BW-PALETTE- [{0}] This is a warning message

JAVA-400001 and it highlights situations
that may affect the activity
execution.
TIBCO-BW-PALETTE- Internal error occurred. Class= Make sure the Java Global
JAVA-501005 [{0}], Method=[{1}], Cause=[{2}] Instance resource has
properly referenced.
TIBCO-BW-PALETTE- Input data error in field [{0}] Ensure that the correct
JAVA-500504 because [{1}]. values are provided for the
method parameter elements
that are in the activity input
tab.
TIBCO-BW-PALETTE- Output data error in field [{0}] Ensure that the getter
JAVA-500604 because [{1}]. methods are returning the
correct values to display the
activity output tab.
JAVA-500605 value cannot be null. methods are not returning
null to display the activity
output tab.
JAVA-500606 value is not serializable. method returns a serializable
Java class to display the
activity output tab.
TIBCO-BW-PALETTE- While executing method [{0}] Correct the error stated in

120 | Palettes
JAVA-500001 encountered exception [{1}] the exception message and

[{2}]. retry.
TIBCO-BW-PALETTE- Activity input data conversion Incorrect object reference

JAVA-500013 error. Exception [{0}] occurred was specified for the
while trying to render the declared Java class. Ensure
activity input data. [{1}] that the correct Java object
reference is provided for the
declared Java class element
shown in the input tab of this
activity.
TIBCO-BW-PALETTE- Activity output data conversion Ensure that the unsupported

JAVA-500014 error. Exception [{0}] occurred data types are not utilized or
while trying to create the referenced in your Java
activity output data. [{1}] class.
TIBCO-BW-PALETTE- The Java class [{0}] is not Ensure that that the specified
JAVA-500017 found in the classpath. class file is contained in the
Encountered classpath.
ClassNotFoundException [{1}].
TIBCO-BW-PALETTE- Activity input error. The activity Ensure that the correct
JAVA-500019 received an incorrect value for values are provided for the
the method parameters. constructor parameter
IllegalArgumentException elements that are in the
occurred while trying to activity input tab.
construct an instance of the
Java class [{0}]: [{1}]
TIBCO-BW-PALETTE- Unable to construct an instance Correct the error stated in

JAVA-500020 of the Java class [{0}]. the exception message and
Encountered exception [{1}] retry.
[{2}].
TIBCO-BW-PALETTE- The constructor for the Java The exception was raised by
JAVA-500021 class [{0}] raised exception the constructor of the

121 | Palettes
[{1}]. [{2}] declared Java class. Please

refer to the Java class
TIBCO-BW-PALETTE- Unable to obtain information for Reconfigure this activity or

JAVA-500026 the method [{0}] from the class verify that the declared Java
[{1}]. Encountered class has not changed since
NoSuchMethodException [{2}]. the last configuration.
TIBCO-BW-PALETTE- Unable to obtain information for Correct the error stated in

JAVA-500027 the method [{0}] from the class the exception message and
[{1}]. Encountered retry.
SecurityException [{2}].
TIBCO-BW-PALETTE- Activity input error. The activity Ensure that the correct
JAVA-500031 received an incorrect value for values are provided for the
the method parameters. When method parameter elements
attempting to invoke the that are in the activity input
method [{0}], encountered tab.
IllegalArgumentException [{1}].
TIBCO-BW-PALETTE- Activity input error. The activity Ensure that the correct Java
JAVA-500032 received an incorrect Java object reference is provided
object for the declared Java for the declared Java class
class [{0}]. The activity required element shown in the input
an instance of the Java class tab of this activity. Ensure
[{1}], but received an instance that the classpath refers to
of the Java class [{2}]: [{3}] the correct declared class.
JAVA-500033 received an incorrect Java object reference is provided
object for the declared Java for the declared Java class
class [{0}]. The Java object element shown in the input
received is not compatible with tab of this activity. Ensure
the Java object required by this that the classpath refers to
activity. The activity required an the correct declared class.
instance of the Java class [{1}]:

122 | Palettes
[{2}]
JAVA-500034 received 'null' value for the for object reference is provided
the declared Java class. The for the declared Java class
activity required an instance of element shown in the input
the class [{0}], but received a tab of this activity.The
'null'. preceding activity that
provides the input value for
this activity should not
produce a null for its output.
TIBCO-BW-PALETTE- Unable to invoke the method Correct the error stated in

JAVA-500035 [{0}]. Encountered exception the exception message and
[{1}] [{2}]. retry.
TIBCO-BW-PALETTE- Unable to invoke the cleanup Correct the error stated in

JAVA-500036 method [{0}]. Encountered the exception message and
exception [{1}] [{2}]. retry.
TIBCO-BW-PALETTE- The method [{0}] raised The exception was raised by

JAVA-500037 exception [{1}]. [{2}]. the method of the specified
Java class. Please refer to
the declared class
TIBCO-BW-PALETTE- The cleanup method [{0}] The exception was raised by

JAVA-500038 raised exception [{1}]. [{2}]. the method of the specified
Java class. Please refer to
the declared class
JAVA-500042 required instance of class [{0}], object reference is provided
but received a 'null' value for for the declared Java class
the declared Java class. element shown in the input
tab of this activity.The

123 | Palettes
preceding activity that

provides the input value for
this activity should not
produce a null for its output.
JAVA-500043 received incorrect Java object object reference is provided
for the declared Java class. for the declared Java class
The activity required an element shown in the input
instance of a class [{0}], but tab of this activity. Ensure
received instance of a class that the classpath refers to
[{1}]. the correct declared class.
TIBCO-BW-PALETTE- Data Conversion error. When Ensure that unsupported

JAVA-500046 attempting to convert Java data types are not utilized or
object to XML data referenced in your Java
encountered exception [{0}]. class.
TIBCO-BW-PALETTE- Data Conversion error. When Ensure that unsupported

JAVA-500047 attempting to convert XML data data types are not utilized or
to Java object encountered referenced in your Java
exception [{0}]. class.
TIBCO-BW-PALETTE- Runtime error. Illegal onEvent Remove the onEvent(Object

JAVA-500063 (Object output)/onError output) method call in the init
(Throwable error) method call. method.
OnEvent/OnError method must
not be called in the init method
or during the initialization
phase.
TIBCO-BW-PALETTE- Runtime error. The output type

JAVA-500065 defined by the
getOutputObjectType() does
not match with the type that is
passed in to onEvent(Object
object).

124 | Palettes
TIBCO-BW-PALETTE- The Java Process Starter The exception was raised by

JAVA-500064 onstop method [{0}] raised the 'onStop' method of the
exception [{1}]. [{2}]. specified Java class. Please
refer to the declared class
TIBCO-BW-PALETTE- The Java Process Starter The exception was raised by

JAVA-500066 onShutdown method [{0}] the 'onShutdown' method of
raised exception [{1}]. [{2}]. the specified Java class.
Please refer to the declared
class implementation for
details.
TIBCO-BW-PALETTE- Internal error occurred while

JAVA-501067 loading the Class=[{0}],
Cause=[{1}]
TIBCO-BW-PALETTE- Internal error occurred. Make sure the Class

JAVA-501069 Method=[{0}] references a referenced the method is
Class=[{1}] no longer exists. valid.
Cause=[{2}]
TIBCO-BW-PALETTE- Activity input error. The activity Ensure that the input content
JAVA-500070 does not receive proper input. is not empty.
TIBCO-BW-PALETTE- Unable to obtain information for Reconfigure this activity or

JAVA-500071 the method [{0}] from the class verify that the declared Java
[{1}]. class has not changed since
the last configuration.
JDBC Palette Error Codes

entities associated with the JDBC palette.

125 | Palettes
TIBCO-BW- The JDBC activity [{0}] is NOT part of a JDBC This is an internal product
PALETTE- Transaction Group. However the activity error. Contact TIBCO
JDBC- references the same shared resource as used Support.
000001 in the group
TIBCO-BW- The JDBC activity [{0}] is first activity in the This is a debug message
PALETTE- JDBC Transaction. and resolution is not
JDBC- applicable.
200001
TIBCO-BW- JDBC activity [{0}] initialized successfully. This is a debug message

JDBC- applicable.
200002
TIBCO-BW- JDBC activity [{0}] task submitted to This is a debug message

PALETTE- Threadpool for execution and resolution is not
JDBC- applicable.
200003
TIBCO-BW- Executing SQL Statement [{0}] for activity This is a debug message
PALETTE- [{1}]. and resolution is not
JDBC- applicable.
200004
TIBCO-BW- Connection received from Datasource for This is a debug message

PALETTE- activity [{0}]. and resolution is not
JDBC- applicable.
200005
TIBCO-BW- Parameters set for activity [{0}] with sql This is a debug message
PALETTE- statement [{1}]. and resolution is not
JDBC- applicable.
200006
TIBCO-BW- Output for activity [{0}] is [{1}]. This is a debug message


126 | Palettes
JDBC- applicable.
200007
TIBCO-BW- Executing SQL Statement for activity [{0}]. This is a debug message
JDBC- applicable.
200008
TIBCO-BW- Executing Prepared Statement for activity

PALETTE- [{0}].
JDBC-
200009
TIBCO-BW- Successfully executed sql statement [{0}] for This is a debug message
PALETTE- activity [{1}]. and resolution is not
JDBC- applicable.
200010
TIBCO-BW- Last subset reached for activity [{0}]. This is a debug message
JDBC- applicable.
200011
TIBCO-BW- Process in subset output for activity [{0}] with This is a debug message
PALETTE- noofRecords [{1}] is [{2}]. and resolution is not
JDBC- applicable.
200012
TIBCO-BW- All Parameters set successfully on Statement This is a debug message

PALETTE- for activity [{0}]. and resolution is not
JDBC- applicable.
200013
TIBCO-BW- Number of updates for JDBC Update activity This is a debug message
PALETTE- is [{0}]. and resolution is not
JDBC- applicable.
200014

127 | Palettes
TIBCO-BW- Number of updates for JDBC Update activity This is a debug message
PALETTE- is 0. Executing Insert Statement [{0}] since and resolution is not
JDBC- activity is in Upsert mode. applicable.
200015
TIBCO-BW- Batch updates failed on update number [{0}]. Check the activity
PALETTE- configuration and if the
JDBC- database is up.
500001
TIBCO-BW- Invalid procedure name specified. Procedure Check the activity

PALETTE- name can not be null. configuration Procedure
JDBC- name field.
500002
TIBCO-BW- {0} input parameters declared in the SQL Check the activity
PALETTE- statement but no input parameters provided. configuration Prepared
JDBC- Parameters table.
500003
TIBCO-BW- Duplicate field name [{0}] found. Modify the Modify the query and
PALETTE- query and create unique aliases for duplicate create unique aliases for
JDBC- fields. duplicate fields.
500004
TIBCO-BW- Improper SQL statement used. {0} Check the syntax of the
PALETTE- SQL Statement specified.
JDBC-
500005
TIBCO-BW- Exception occurred occurred when attempting Check the Shared

PALETTE- to create a JDBC Connection for JDBC Resource configuration
JDBC- Transaction. this activity is configure
500006 with and also that the
database is running.
TIBCO-BW- Missing Input Value for required Column [{0}]. Check the input tab of the

128 | Palettes
PALETTE- activity and set the

JDBC- column value
500007
TIBCO-BW- SQL Exception occurred (SQL STATE = {0}) - Check the activity
PALETTE- detailMessage - {1} configuration and the
JDBC- state of the database the
500009 activity is connected to.
TIBCO-BW- {0} is not a valid timezone. Check the activity

PALETTE- configuration input tab
JDBC- and enter a valid
500010 timezone
TIBCO-BW- Could not create Connection to server using Check the JDBC
PALETTE- Shared Resource [{0}]. Connection Shared
JDBC- Resource configuration
500011 which is configured on the
activity.
TIBCO-BW- INVALID_JDBC_ACTIVITY_ Check the activity

PALETTE- CONFIGURATION = Invalid Activity configuration and enter
JDBC- Configuration. Missing required configuration values for missing fields
500012 Field [{0}] in activity [{1}] specified in the message.
TIBCO-BW- INVALID_SQL_STATEMENT = Invalid Check the activity

PALETTE- Activity Configuration. Invalid SQL Statement configuration for the SQL
JDBC- [{0}] in activity [{1}] expected a statement with statement syntax.
500013 [{2}]
TIBCO-BW- PREPARED_PARAMETERS_MORE_THAN_ Check the activity

PALETTE- QUESTION_MARKS = Invalid Activity configuration for the
JDBC- Configuration. Number of Prepared Prepared Parameters
500014 Parameters in activity configuration exceed specified.
number of '?' in SQL Statement
TIBCO-BW- PREPARED_PARAMETERS_LESS_THAN_ Check the activity

129 | Palettes
PALETTE- QUESTION_MARKS = Invalid Activity configuration for the

JDBC- Configuration. Number of Prepared Prepared Parameters
500015 Parameters in activity configuration is less specified.
than number of '?' in SQL Statement
TIBCO-BW- BATCH_UPDATE_WITHOUT_PREPARED_ Check the SQL statement

PALETTE- PARAMS = Batch Update mode works only in the activity
JDBC- with Prepared Statements configuration to ensure
500016 that it is a SQL statement
with prepared
parameters.
TIBCO-BW- JDBC Connection login timed out. Check the configuration

PALETTE- details or increase the
JDBC- login timeout.
500019
JMS Palette Error Codes

entities associated with the JMS palette.
TIBCO-BW- {0}
PALETTE-
JMS-000001
TIBCO-BW- {0}
PALETTE-
JMS-100001
TIBCO-BW- {0}
PALETTE-
JMS-200001

130 | Palettes
TIBCO-BW- {0}
PALETTE-
JMS-300001
TIBCO-BW- {0}
PALETTE-
JMS-400001
TIBCO-BW- Invalid configuration data. JMS connection Check activity configuration

PALETTE- reference is not specified. for JMS Connection
JMS-500001 Reference.
TIBCO-BW- Invalid configuration data. Specified Check activity configuration

PALETTE- connection reference is not found in for JMS Connection
JMS-500002 repository. {0} Reference.
TIBCO-BW- Invalid configuration data. JMS destination Check activity configuration

PALETTE- is not specified. for the JMS Destination field.
JMS-500003
TIBCO-BW- Error occurred when attempting to create Check activity configuration

PALETTE- Durable Subscriber for the Durable Subscription
JMS-500004 name box and if JMS server
is running.
TIBCO-BW- Failed to create connection to the JMS Check JMS Connection

PALETTE- server. {0} shared resource configuration
JMS-500005 and if the JMS server is
running.
TIBCO-BW- Unable to create a session to receive Check JMS Connection

PALETTE- messages [{0}]. shared resource configuration
running.
TIBCO-BW- Unable to create a reply session/producer Check JMS Connection

PALETTE- [{0}] shared resource configuration

131 | Palettes

running.
TIBCO-BW- Unable to find destination [{0}] on JMS Check JMS Server if it the
PALETTE- server destination name specified in
JMS-500008 the error message exists.
TIBCO-BW- Error occurred when attempting to create Check JMS Connection

PALETTE- MessageConsumer shared resource configuration
running.
TIBCO-BW- Error occurred when attempting to resolve Check JMS Connection

PALETTE- destination [{0}] shared resource configuration
running.
TIBCO-BW- Invalid configuration data. JMS Reply To Check the activity

PALETTE- Destination Not Specified. configuration and specify a
JMS-500011 value in the JMS Reply To
field.
TIBCO-BW- Error occurred when attempting to send a Check the activity

PALETTE- JMS message configuration, input data, JMS
JMS-500012 Connection shared resource
configuration and if the JMS
server is running.
TIBCO-BW- Error occurred when attempting to receive Check the activity

PALETTE- a JMS message configuration, JMS
server is running.
TIBCO-BW- Error occurred when attempting to confirm Check the activity

PALETTE- a JMS message configuration, JMS

132 | Palettes

server is running.
TIBCO-BW- Failed to Reply for JMS ProcessStarter There is no resolution for this
PALETTE- [{0}]. This error can occur if the JMSReply error.
JMS-500015 activity is executed after recovering from a
check-pointed BusinessWorks process
instance.
Mail Palette Error Codes

entities associated with the Mail palette.
TIBCO-BW- [{0}] This is an internal product error.

PALETTE- Contact TIBCO Support.
MAIL-000001
TIBCO-BW- [{0}] This is a trace message and

MAIL-100001
TIBCO-BW- [{0}] This is a debug message and

MAIL-200001
TIBCO-BW- [{0}] This is an informational message

MAIL-300001 progress of the activity.
TIBCO-BW- [{0}] This is a warning message and it

PALETTE- highlights situations that may
MAIL-400001 affect the activity execution.

133 | Palettes
TIBCO-BW- Invalid input data. Reason: Error Ensure the destination addresses
PALETTE- parsing input data. given are valid.
MAIL-500005
TIBCO-BW- Invalid input data. Reason: Both the Ensure that both the comma and
PALETTE- comma and semicolon cannot be used semicolon cannot be used at
MAIL-500007 at same time to separate addresses: same time to separate
[{0}] addresses.
TIBCO-BW- Error connecting to the mail server. Ensure the host provided is valid.
PALETTE- Reason: unknown host - connection
MAIL-500020 parameters: [{0}].
TIBCO-BW- Error building mail message. Cause: Ensure the input message details
PALETTE- [{0}]. are properly given.
MAIL-500033
TIBCO-BW- From address [{0}] is not valid. Ensure the From address must
PALETTE- not be empty or null string
MAIL-500035
TIBCO-BW- Error sending mail message. Ensure the SMTP shared

PALETTE- resource configuration is
MAIL-500036 appropriately specified.
TIBCO-BW- The system cannot find the file Ensure the file exists at a given
PALETTE- specified: [{0}]. location.
MAIL-500037
TIBCO-BW- Invalid recipient address in To, CC or Ensure recipient addresses given

PALETTE- BCC [{0}, {1}, {2}]. must be valid.
MAIL-500038
TIBCO-BW- Host can not be null Ensure the host must not be null
PALETTE- value.
MAIL-500001

134 | Palettes
TIBCO-BW- Username can not be null when using Ensure the username value must
PALETTE- Authentication not be null when using
MAIL-500002 authentication.
TIBCO-BW- Password can not be null when using Ensure the password value must
PALETTE- Authentication not be null when using
MAIL-500003 authentication.
TIBCO-BW- Error closing mail server connection. Ensure the Mail receiver
PALETTE- Cause: [{0}]. configuration is appropriately
MAIL-500004 given.
TIBCO-BW- Mail provider for protocol [{0}] not Ensure that the mail provider jar
PALETTE- found. Make sure that the provider jar is in java classpath.
MAIL-500008 is in java classpath.
TIBCO-BW- Configuration error in field [{0}] the Ensure the host name for mail
PALETTE- value must be a valid Host Name. receiver must be valid.
MAIL-500009
TIBCO-BW- Error connecting to the mail server - Ensure the mail server is up or
PALETTE- connect exception; connection check whether the connection
MAIL-500010 parameters: [Host:{0}, Port:{1}, User: parameters are properly
{2}]. configured.
TIBCO-BW- Could not connect to mail server - Ensure the username and
PALETTE- invalid username in field [{0}] and/or password provided are valid.
MAIL-500011 invalid password.
TIBCO-BW- The default mail folder was not found Ensure the Mail receiver
PALETTE- on mail server. configuration is appropriately
MAIL-500012 given.
TIBCO-BW- The INBOX mail folder was not found Ensure the Mail receiver
PALETTE- on mail server. configuration is appropriately
MAIL-500013 given.

135 | Palettes
TIBCO-BW- Error getting folder on mail server. Ensure the Mail receiver
PALETTE- configuration is appropriately
MAIL-500014 given.
TIBCO-BW- Mail is already deleted, Receive Mail Ensure the delete mail option on
PALETTE- activity has 'Delete Mail' turned on. Receive Mail activity general tab
MAIL-500015 is unchecked or don't use explicit
confirm.
TIBCO-BW- Error connecting to the mail server Ensure the mail server is up or
PALETTE- using connection parameters: [{0}] verify connection parameters.
MAIL-500021
TIBCO-BW- Error while polling mail server: cannot Ensure the mail server is up or
PALETTE- open INBOX folder. verify connection parameters.
MAIL-500022
TIBCO-BW- Error parsing received mail. Ensure the Mail receiver

PALETTE- configuration is appropriately
MAIL-500023 given.
TIBCO-BW- Error while polling mail server: cannot Ensure the mail server is up or
PALETTE- close INBOX folder. verify connection parameters.
MAIL-500024
TIBCO-BW- Unexpected error while polling mail Ensure the mail server is up or
PALETTE- server. verify connection parameters.
MAIL-500025
TIBCO-BW- The Receive Mail ProcessStarter This is an internal product error.

PALETTE- activity [{0}] failed to a generate a new Contact TIBCO Support.
MAIL-500026 event due to exception [{1}] since it is
in the stopped state.
TIBCO-BW- Marking msg {0} for confirmation. This is an informational message

MAIL-300001 progress of the activity.

136 | Palettes
Parse Palette Error Codes

entities associated with the Parse palette.
TIBCO-BW- {0} This is an internal product error. Contact

PALETTE- TIBCO Support.
PARSE-
000001
TIBCO-BW- {0} This is a trace message and resolution is

PALETTE- not applicable.
PARSE-
100001
TIBCO-BW- {0} This is a debug message and resolution

PALETTE- is not applicable.
PARSE-
200001
TIBCO-BW- {0} This is an informational message and it

PALETTE- highlights the runtime progress of the
PARSE- activity. Resolution is not applicable.
300001
TIBCO-BW- {0} This is a warning message and it

PALETTE- highlights situations that may affect the
PARSE- activity execution.
400001
TIBCO-BW- Cannot find data format Check if Data format shared resource is
PALETTE- schema resource [{0}] configured.
PARSE-
500000
TIBCO-BW- Cannot create schema from Check if the schema is valid.

PALETTE- data format schema.
PARSE-

137 | Palettes
500001
TIBCO-BW- Exception in parse eval: [{0}] An error occurred while processing, refer
PALETTE- to the exception thrown and correct the
PARSE- activity configuration or input.
500002
TIBCO-BW- Line length must be > 0 Check if line length is greater than zero.
PALETTE-
PARSE-
500003
TIBCO-BW- Hit EOF on row [{0}] field [{1}] Check the configuration of number of
PALETTE- spanning columns [{2}] to [{3}] records in input of Parse Data activity. It
PARSE- .... last row contents was: [{4}] may be more than the records present in
500004 the file.
TIBCO-BW- Input type is not specified. Check configuration of Input type on

PALETTE- Parse Data activity. Ensure either File or
PARSE- String is configured.
500005
TIBCO-BW- Please specify the Input type Check configuration of Input type on
PALETTE- field. Parse Data activity. Ensure either File or
PARSE- String is configured.
500006
TIBCO-BW- Data format resource not Check if Data format shared resource is
PALETTE- specified. configured on the activity.
PARSE-
500007
TIBCO-BW- Specify the data format Check if Data format shared resource is
PALETTE- resource. configured on the activity.
PARSE-
500008

138 | Palettes
TIBCO-BW- File [{0}] cannot be opened Check the encoding configruation on

PALETTE- using encoding method [{1}] Parse Data activity. Ensure encoding
PARSE- supported by file is selected.
500009
TIBCO-BW- Format Type must be selected. Ensure that Format type is configured on
PALETTE- Data Format shared resource.
PARSE-
500011
TIBCO-BW- Line is too long. Specified Line Check field offsets configuration on Data
PALETTE- Delimiter may not match file Format shared resource.
PARSE- content.
500012
TIBCO-BW- There are not enough data for Check field offsets configuration on Data
PALETTE- the number of required fields in Format shared resource.
PARSE- a row.
500013
TIBCO-BW- Error while parsing headers in Ensure that the input message has
PALETTE- the mime message. MIME headers.
PARSE-
500014
TIBCO-BW- An I/O exception occurred Ensure that the SOAP payload is well
PALETTE- while parsing SOAP payload in formed and valid.
PARSE- the root part.
500015
TIBCO-BW- An Unexpected exception UNEXPECTED_EXCEPTION.resolution

PALETTE- occurred while parsing =This is an internal product error.
PARSE- Message. Root cause is [{0}] Contact TIBCO Support
5000016
TIBCO-BW- The SOAP Message doesn't Ensure that the input message has
PALETTE- exist in the Root part. SOAP payload in it.

139 | Palettes
PARSE-
500017
TIBCO-BW- Soap Envelope has invalid Ensure that the SOAP payload is valid
PALETTE- XML content. and well formed.
PARSE-
500018
TIBCO-BW- One or more mime parts have Ensure that in input message does not
PALETTE- same Content-Id value in the have same content id for different mime
PARSE- Mime Message. parts.
500019
TIBCO-BW- The xop:Include element must Ensure that in the SOAP payload, the
PALETTE- have an 'href' attribute. xop:Include element has href attribute.
PARSE-
500020
TIBCO-BW- Content_Id header is not found Ensure that the each mime part has
PALETTE- in mime part of the Mime content-id header and corresponding
PARSE- Message. value.
500021
TIBCO-BW- Invalid Content Type Field in Ensure that media type starts with
PALETTE- the Mime Message. 'multipart'.
PARSE-
500022
TIBCO-BW- Boundary attribute not found in Ensure that the 'boundary' attribute is not
PALETTE- the Mime Message. missing in the mime header.
PARSE-
500023
TIBCO-BW- startinfo parameter is missing Ensure that 'startinfo' attribute is present

PALETTE- in the Mime Message. in the mime header.
PARSE-
500024

140 | Palettes
TIBCO-BW- startinfo parameter is not Ensure that startinfo attribute has

PALETTE- starting with 'application/soap+xml' as value.
PARSE- 'application/soap+xml' in the
500025 Mime Message.
TIBCO-BW- Content Type header is not Ensure that the mime message has
PALETTE- found in the Mime Message. 'content-type' header.
PARSE-
500026
TIBCO-BW- Media type of root part is not Ensure that the root part's media type is
PALETTE- 'application/xop+xml' in the 'application/xop+xml'
PARSE- Mime Message.
500027
TIBCO-BW- 'type' parameter is not present Ensure that the root part has 'type'
PALETTE- in root part of the Mime parameter.
PARSE- Message.
500028
TIBCO-BW- startInfo parameter and type Ensure that the value of startInfo
PALETTE- parameter, of root part, does parameter and type parameter is same
PARSE- not match in the Mime in the root part of the Mime Message.
500029 Message.
TIBCO-BW- ERROR_LINE_LESS_THAN_ Ensure that Line length is not less than

PALETTE- MAX_ max Field Offset.
PARSE-
LENGTH=Line length [{0}]
500030
is less than max Field Offset
[{1}]
ERROR_LINE_LESS_THAN_
MAX_
LENGTH.errorCode=500030
ERROR_LINE_LESS_THAN_
MAX_

141 | Palettes
LENGTH.resolution
TCP Palette Error Codes

entities associated with the TIBCO ActiveMatrix BusinessWorks™ TCP palette.
TIBCO-BW- {0} This is a debug message and resolution is not

PALETTE- applicable.
TCP-200001
TIBCO-BW- Cannot start TCP Please correct Host and Port and retry.
PALETTE- Receiver on Host [{0}],
TCP-500001 Port [{1}]. Reason: [{2}].
TIBCO-BW- Invalid Port; port must be The Port must be numeric.

PALETTE- numeric. Error: [{0}]
TCP-500003
TIBCO-BW- No value specified for the Please specify value in the 'data' input field.
PALETTE- 'data' input field.
TCP-500004
TIBCO-BW- Error reading TCP data. This is an internal product error. Contact
PALETTE- Reason: [{0}]. TIBCO Support..
TCP-500006
TIBCO-BW- Error opening TCP This is an internal product error. Contact

PALETTE- Connection. Reason: TIBCO Support..
TCP-500008 [{0}].
TIBCO-BW- Error opening TCP Invalid Host, Please correct the error and retry.
PALETTE- Connection. Reason:
TCP-500009 Host [{0}] unknown.

142 | Palettes
TIBCO-BW- Exception closing TCP This is an internal product error. Contact

PALETTE- Connection. Reason: TIBCO Support..
TCP-500013 [{0}].
TIBCO-BW- Could not read from TCP The input connection is either invalid or closed.
PALETTE- connection. The input Please correct the error and retry.
TCP-500014 connection is either
invalid or closed.
TIBCO-BW- Could not write to TCP The input connection is either invalid or closed.
PALETTE- connection. The input Please correct the error and retry.
TCP-500015 connection is either
invalid or closed.
TIBCO-BW- Cannot start TCP Check Host and Port and retry.
PALETTE- Receiver on Host=[{0}],
TCP-500016 Port=[{1}]. Another TCP
Receiver is already
running with the same
configuration.
TIBCO-BW- Error closing TCP Match the input connection key while closing
PALETTE- connection. Reason: No connection.
TCP-500017 connection is available
which matches the input
connection key.
TIBCO-BW- Error writing data. This is an internal product error. Contact

PALETTE- Reason: [{0}]. TIBCO Support...
TCP-500018
TIBCO-BW- Timeout while reading Possible causes for this error are:(1)The data
PALETTE- TCP data is being read before it is written.(2)If the data
TCP-500021 that is written is text/binary and it is being read
as binary/text.(3)If the data is written
with/without separator and is being read
without/with separator.

143 | Palettes
TIBCO-BW- IOException occurred This is an internal product error. Contact

PALETTE- while retrieving XML TIBCO Support..
TCP-500022 Output for activity [{0}].
TIBCO-BW- The TCP Receiver This is an internal product error. Contact

PALETTE- Process Starter activity TIBCO Support.
TCP-500023 [{0}] failed to a generate
a new event due to
exception [{1}] since it is
TIBCO-BW- The Wait For TCP This is an internal product error. Contact
PALETTE- Request activity [{0}] TIBCO Support.
TCP-500024 failed to a generate a
new event due to
exception [{1}] since it is
TIBCO-BW- Invalid SSL There is error with the SSL Configurations.

PALETTE- Configurations. Reason: Correct the SSL Configurations and then retry.
TCP-500025 [\{0}].
TIBCO-BW- Cannot start TCP Correct Port and retry.

PALETTE- Receiver on Port [\{0}].
TCP-500026 Reason: [\{1}].
XML Palette Error Codes

entities associated with the XML palette.
TIBCO-BW- [{0}] This is an internal product error. Contact

PALETTE- TIBCO Support.
XML-000001

144 | Palettes
TIBCO-BW- [{0}] This is a trace message and resolution is

XML-100001
TIBCO-BW- [{0}] This is a debug message and resolution is

XML-200001
TIBCO-BW- [{0}] This is an informational message and it

PALETTE- highlights the runtime progress of the
XML-300001 activity. Resolution is not applicable.
TIBCO-BW- [{0}] This is a warning message and it

PALETTE- highlights situations that may affect the
XML-400001 activity execution.
TIBCO-BW- Internal error occurred Class= Please Contact TIBCO Support

PALETTE- [{0}], Method=[{1}], Reason=
XML-500000 [{2}].
TIBCO-BW- Unable to serialize the XML Ensure the input XML node is properly
PALETTE- due to exception [{0}]. given.
XML-500001
TIBCO-BW- Unable to parse the XML due Ensure the provided input XML is well
PALETTE- to exception [{0}]. formed and valid.
XML-500002
TIBCO-BW- Exception [{0}] occurred Ensure the provided input XML and input
PALETTE- during XSLT transformation. XSLT is properly given.
XML-500003 Exception detail [{1}].
TIBCO-BW- The XSLT transformation Ensure to provide the XSLT either in the
PALETTE- Stylesheet provided for the configuration or in the activity input.
XML-500004 activity input is empty or null.
TIBCO-BW- The selected encoding [{0}] is Ensure the provided encoding is valid.

145 | Palettes
PALETTE- not valid.

XML-500005
TIBCO-BW- Encountered encoding error Ensure the provided encoding is correct.

PALETTE- [{0}].
XML-500006
TIBCO-BW- The encoded bytes content is Ensure that the input content is not empty.
PALETTE- empty.
XML-500007
TIBCO-BW- Encountered error [{0}] while Ensure the provided input byte content is
PALETTE- trying to detect the encoding correct.
XML-500008 from the XML.
TIBCO-BW- Activity input error. The Ensure that the input content is not empty.
PALETTE- activity does not receive
XML-500009 proper input.

146 | Shared Resources
Shared Resources
This section describes the error codes that can be reported by various shared resources.
Shared Resource Framework Error Codes

The Shared Resource Framework is responsible for the creating and managing the
shared resources required by the product applications. This section describes the error
messages that can be reported by the Shared Resource Framework.
Error Codes Error Message
TIBCO-BW-SR- Shared Resource Creation Error. The ResourceDependencyHandler

FRWK-000010 object returned by [{0}#create()] is null.
TIBCO-BW-SR- {0}
FRWK-500001
TIBCO-BW-SR- Failed to {0} SharedResource [{1}] for Module [{2}:{3}],

FRWK-502000 DeploymentUnit [{4}:{5}]{6}
TIBCO-BW-SR- Unable to start SharedResource [{0}] {1}. <Reason>: {2}

FRWK-503000
TIBCO-BW-SR- Unable to get IdentitySubject from Trinity for {0}.

COMMON-001101
TIBCO-BW-SR- Object is not of type IdentitySubject for {0}.

COMMON-001102
TIBCO-BW-SR- Unable to get IdentityTrust from Trinity for {0}.

COMMON-001103

TIBCO-BW-SR- Object is not of type IdentityTrust for {0}.

COMMON-001104
TIBCO-BW-SR- Unsupported PrivateKey.

COMMON-001105
TIBCO-BW-SR- Key not found.

COMMON-001105
TIBCO-BW-SR- Problem extracting Key.

COMMON-001105
TIBCO-BW-SR- Failed to {0} Thread Pool resource [{1}]

THREADPOOL-
502000
TIBCO-BW-SR- Failure during execution of pending task {0} in work queue on

THREADPOOL- ThreadPool shutdown.
500001
TIBCO-BW-SR- Could not submit task {0} for execution.

THREADPOOL-
500002
TIBCO-BW-SR- No matching time unit found for {0}, possible values are
THREADPOOL- {NANOSECONDS, MICROSECONDS, MILLISECONDS, SECONDS,
500003 MINUTES, HOURS, DAYS}.
TIBCO-BW-SR- No matching rejection policy found for {0}, possible values are
THREADPOOL- {BLOCKING, CALLER_RUNS, ABORT}.
500004
TIBCO-BW-SR- Keep Alive Time should be greater then or equal to zero.

THREADPOOL-
500005
TIBCO-BW-SR- Maximum Pool Size should be greater then zero and less then or
THREADPOOL- equal Core pool size.
500006
TIBCO-BW-SR- Core Pool Size should be greater then or equal to zero.

THREADPOOL-
500007
TIBCO-BW-SR- Minimum Pool Size should be greater then or equal to zero.

THREADPOOL-
500008
Data Format Error Codes

This section describes the error messages that can be reported by the Data Format
shared resource.
TIBCO-BW-SR- {0} This is a debug message and

DATAFORMAT-200001 resolution is not applicable.
TIBCO-BW-SR- Failed to {0} Data Check the configuration of Data

DATAFORMAT-500000 Format resource [{1}] Format shared resource.
FTP Connection Error Codes

This section describes the error messages that can be reported by the FTP Connection
shared resource.

TIBCO-BW-SR- Failed to {0} FTP Please correct the error and retry.
FTP-500004 Connection resource [{1}]

FTP-200001 resolution is not applicable.
HTTP Client Error Codes

This section describes the error messages that can be reported by the HTTP Client
shared resource.

HTTP-CLIENT- resolution is not applicable.
200001
TIBCO-BW-SR- Failed to {0} HTTP Client resource Check the configuration of Http
HTTP-CLIENT- [{1}] Client resource.
500000
TIBCO-BW-SR- User name or Password is not Specify user name and

HTTP-CLIENT- specified in Identity password in Identity shared
500001 resource.
TIBCO-BW-SR- User name or Password is not set in Check if user name and
HTTP-CLIENT- identity resource for basic Http password is specified in Identity
500002 authentication shared resource.
HTTP Connector Error Codes

This section describes the error messages that can be reported by the HTTP Connector
shared resource.

TIBCO-BW-SR- {0} This is a trace message and

HTTP- resolution is not applicable.
CONNECTOR-
100001

HTTP- resolution is not applicable.
CONNECTOR-
200001
TIBCO-BW-SR- Error while stopping HTTP This is an informational message

HTTP- endpoint [{0}] and it highlights the runtime
CONNECTOR- progress of the shared resource.
300003 Resolution is not applicable.
TIBCO-BW-SR- Error while stopping HTTP This is an informational message

HTTP- context [{0}] and it highlights the runtime
CONNECTOR- progress of the shared resource.
300004 Resolution is not applicable.
TIBCO-BW-SR- Failed to {0} HTTP Connector Check the configuration of Http

HTTP- resource [{1}] Connector resource.
CONNECTOR-
500000
TIBCO-BW-SR- Failed to create HTTP Check the configuration of Http

HTTP- Connector resource [{0}] with Connector resource.
CONNECTOR- the specified configuration.
500003 Check the configuration
settings.
TIBCO-BW-SR- Unable to start HTTP Server Check the configuration of Http

HTTP- instance for resource [{0}] Connector resource.
CONNECTOR-
500004
TIBCO-BW-SR- Failed to activate HTTP Check the exception and correct

HTTP- endpoint [{0}] because of the configuration of Http Connector

CONNECTOR- exception [{1}] resource or Http Event source.
500005
TIBCO-BW-SR- The HTTP server instance Check the configuration of Http

HTTP- cannot be started, because it is Connector resource or Http Event
CONNECTOR- not configured source.
500006
TIBCO-BW-SR- The HTTP server instance [{0}] System exception.

HTTP- occurred an error when stopped
CONNECTOR-
500007
TIBCO-BW-SR- Failed to deactivate HTTP System exception.

HTTP- endpoint [{0}]
CONNECTOR-
500008
TIBCO-BW-SR- Failed to get URL for HTTP Check the host and port
HTTP- endpoint [{0}] configuration on Http Connector
CONNECTOR- resource.
500009
TIBCO-BW-SR- Unable to find Application System exception.

HTTP- bundle [{0}]
CONNECTOR-
500010
TIBCO-BW-SR- Failed to create HTTP Check the port configured on Http

HTTP- Connector resource [{0}] Connector resource is not in use.
CONNECTOR- configured with port [{1}]
500012
TIBCO-BW-SR- LDAP resource is not Please check if LDAP resource is

HTTP- configured on HTTP Connector configured on Http Connector.
CONNECTOR- resource [{0}].
500013

Java Global Instance Error Codes

This section describes the error messages that can be reported by the Java Global
Instance shared resource.

Codes
TIBCO- BW6_EXCP_NAME_EXISTS = A connector This is an internal product

BW-SR- configuration with the name "[{0}" already error. Contact TIBCO Support.
JAVA- exists with pid [{1}]
500001
TIBCO- Unable to find Application bundle [{0}] This is an internal product

BW-SR- error. Contact TIBCO Support.
JAVA-
500002
TIBCO- Unable to construct an instance of the Java Correct the error stated in the
BW-SR- class [{0}]. Encountered exception [{1}] [{2}]. exception message and retry.
JAVA-
500003
TIBCO- Activity input error. The activity received an Ensure that the correct values
BW-SR- incorrect value for the method parameters. are provided for the
JAVA- IllegalArgumentException occurred while constructor parameter
500004 trying to construct an instance of the Java elements that are in the
class [{0}]: [{1}] activity input tab.
TIBCO- The constructor for the Java class [{0}] The exception was raised by
BW-SR- raised exception [{1}]. [{2}] the constructor of the declared
JAVA- Java class. Please refer to the
500005 Java class implementation for
details.
TIBCO- The Java class [{0}] is not found in the Ensure that the specified class
BW-SR- classpath. Encountered file is contained in the
JAVA- ClassNotFoundException [{1}]. classpath.
500006


Codes
TIBCO- Unable to obtain information for the method Reconfigure this activity or
BW-SR- [{0}] from the class [{1}]. Encountered verify that the declared Java
JAVA- NoSuchMethodException [{2}]. class has not changed since
500007 the last configuration.
TIBCO- Unable to obtain information for the cleanup Reconfigure this activity or
BW-SR- method [{0}] from the class [{1}]. verify that the declared Java
JAVA- NoSuchMethodException occurred. [{2}] class has not changed since
500008 the last configuration.
TIBCO- The cleanup method [{0}] raised exception The exception was raised by
BW-SR- [{1}]. [{2}] the method of the specified
500009 declared class implementation
for details.
TIBCO- Unable to invoke the cleanup method [{0}]. Correct the error stated in the
BW-SR- Exception [{1}] occurred. [{2}] exception message and retry.
JAVA-
500010
TIBCO- Unable to invoke the cleanup method [{0}]. The exception was raised by
BW-SR- Encountered exception [{1}] [{2}]. the method of the specified
500012 declared class implementation
for details.
TIBCO- Received an incorrect value for the method Ensure that the correct values
BW-SR- [{0}] parameter to get access the BW Module are provided for the method
JAVA- properties. Exception occurred: [{1}] parameter to get access the
500014 BW Module properties.
TIBCO- {0} This is a debug message and

BW-SR- resolution is not applicable.
JAVA-
200001


Codes
TIBCO- Failed to {0} Java Global Instance resource

BW-SR- [{1}]
JAVA-
200002
TIBCO- Delete Called on configuration that does not

BW-SR- exist with pid [{0}]
JAVA-
000001
JMS Connection Error Codes

This section describes the error messages that can be reported by the JMS Connection
shared resource.
TIBCO-BW-SR- {0}
JMS-100001
TIBCO-BW-SR- {0}
JMS-200001
TIBCO-BW-SR- {0}
JMS-300001
TIBCO-BW-SR- {0}
JMS-400001
TIBCO-BW-SR- Failed to {0} JMS Connection Check JMS Connection Shared

JMS-502000 resource [{1}] resource configuration

JDBC Connection Error Codes

This section describes the error messages that can be reported by the JDBC Connection
shared resource.

Codes
TIBCO- Received an update This is an informational message and it

BW-SR- request for existing highlights the runtime progress of the shared
JDBC- configuration with PID=[{0}] resource. Resolution is not applicable.
300001 and Shared resource name
[{1}]
TIBCO- Updating Password for This is an informational message and it

BW-SR- Shared Resource with PID highlights the runtime progress of the shared
JDBC- [{0}] and name[{1}] resource. Resolution is not applicable.
300002
TIBCO- Updating Username for This is an informational message and it

BW-SR- Shared Resource with PID highlights the runtime progress of the shared
JDBC- [{0}] and name[{1}] resource. Resolution is not applicable.
300003
TIBCO- Updating Database URL This is an informational message and it

BW-SR- [{0}] for Shared Resource highlights the runtime progress of the shared
JDBC- with PID[{1}] and name[{2}] resource. Resolution is not applicable.
300004
TIBCO- Ignoring Hot Update for This is an informational message and it

BW-SR- configuration with PID=[{0}] highlights the runtime progress of the shared
JDBC- and name[{1}]. resource. Resolution is not applicable.
300005 Unsupported parameters
updated. Only Username,
Password and URL is
supported
TIBCO- Adding new configuration This is an informational message and it

BW-SR- for Shared Resource with highlights the runtime progress of the shared
JDBC- name [{0}] resource. Resolution is not applicable.


Codes
300006
TIBCO- Deleting Configuration for This is an informational message and it

BW-SR- Shared Resource with highlights the runtime progress of the shared
JDBC- name[{0}] resource. Resolution is not applicable.
300007
TIBCO- Following Drivers have This is an informational message and it

BW-SR- been loaded in the highlights the runtime progress of the shared
JDBC- framework[{0}]. Following resource. Resolution is not applicable.
300008 Shared Resource
Configurations have been
deployed before these
drivers were loaded [{1}].
TIBCO- Exception occurred while This is a warning message and does not a. A
BW-SR- closing a bad connection JDBC connection was marked invalid by the
JDBC- with [Vendor ErrorCode:{0}] driver and was removed from the pool. This
400001 and SQL STATE[{1}] connection could not be closed successfully.
TIBCO- Maximum permitted This is a warning message. The JDBC

BW-SR- Connections reached. Connection Pool has reached is maximum limit
JDBC- Cannot create new specified by the user. Jobs created will wait for
400002 connection. Waiting for a a connection to be available before proceeding.
connection to be available. Increasing the max connections to a suitable
value for the application will solve this issue.
TIBCO- No suitable This is a warning message. This message

BW-SR- DataSourcefactory found prints out information about a driver not being
JDBC- for driver [{0}]. The shared loaded at the current time. Since the framework
400003 resource {1} might NOT has not finished loading, there is a chance of
resolve. The configuration the driver being loaded later. It is safe to ignore
will wait for a driver to be this message.
available.
TIBCO- Failed to {0} JDBC A JDBC Connection lifecycle error has


Codes
BW-SR- Connection resource [{1}]. occurred. Check the connection configuration

JDBC- and restart the application if necessary.
502000
TIBCO- Exception occurred while Check the connection configuration and if the
BW-SR- trying to retrieve a database is up and running.
JDBC- connection from the JDBC
500001 Connection pool
TIBCO- Failed to create a new Check the connection configuration and if the
BW-SR- connection to database database is up and running.
JDBC- server. Database URL [{0}],
500002 UserName [{1}],
SQLSTATE [{2}]
TIBCO- The database driver [{0}] is Run the appropriate script using bwinstall from
BW-SR- not found. Ensure that the bin folder to add the JDBC driver to the
JDBC- DataSourceFactory bundle runtime environment
500003 providing this driver is
available in the
environment.
TIBCO- Destroying all Unused This is a debug message and resolution is not
BW-SR- connections. applicable.
JDBC-
200001
TIBCO- Published Event to Event This is a debug message and resolution is not
BW-SR- Admin on topic {0} applicable.
JDBC-
200002
TIBCO- Delete Called on This is an internal product error. Contact TIBCO

BW-SR- configuration that does not Support.
JDBC- exist with pid [{0}]
000001

JNDI Configuration Error Codes

This section describes the error messages that can be reported by the JNDI
Configuration shared resource.
TIBCO-BW-SR- {0}
JNDI-100001
TIBCO-BW-SR- {0}
JNDI-200001
TIBCO-BW-SR- {0}
JNDI-300001
TIBCO-BW-SR- {0}
JNDI-400001
TIBCO-BW-SR- Failed to {0} JNDI Check JNDI Configuration shared

JNDI-502000 Configuration resource [{1}] resource configuration.
Proxy Configuration Error Codes

This section describes the error messages that can be reported by the Proxy
Configuration shared resource.
TIBCO-BW-SR-HTTP- {0} This is a debug message and

PROXY-200001 resolution is not applicable.
TIBCO-BW-SR-HTTP- Failed to {0} Proxy Check the configuration of Proxy

PROXY-500000 Configuration resource [{1}] shared resource.

SMTP Resource Error Codes

This section describes the error messages that can be reported by the SMTP shared
resource.

Codes
TIBCO- {0} This is a debug message and resolution is

BW-SR- not applicable.
MAIL-
200001
TIBCO- Adding new configuration This is an informational message and it

BW-SR- [{0}]. highlights the runtime progress of the activity.
MAIL- Resolution is not applicable.
300001
TIBCO- Deleting configuration [{0}]. This is an informational message and it

BW-SR- highlights the runtime progress of the activity.
300002
TIBCO- Mail Session created This is an informational message and it

BW-SR- successfully. highlights the runtime progress of the activity.
300004
TIBCO- Called update on an existing This is a warning message and it highlights

BW-SR- configuration [{0}]. Resource situations that may affect the activity
MAIL- will be recreated. execution.
400001
TIBCO- Problem extracting mail SSL Ensure the SSL shared resource is
BW-SR- information from Trinity for appropriately configured.
MAIL- JNDI [{0}].
500001
TIBCO- Mail Session creation failed. Ensure the smtp shared resource is
BW-SR- appropriately configured.


Codes
MAIL-
500002
TIBCO- Handler for MimeType [{0}] Ensure the MimeType is valid.

BW-SR- not found.
MAIL-
500005
TIBCO- Failed to start SMTP Ensure the smtp shared resource is

BW-SR- Connection Shared Resource appropriately configured.
MAIL- [{0}].
500006
TCP Connection
This section describes the error messages that can be reported by the TCP Connection
shared resource.
TIBCO-BW-SR- Failed to {0} TCP Please correct the error and retry.
TCP-500004 Connection resource [{1}]

TCP-200001 resolution is not applicable.

161 | TIBCO Documentation and Support Services
TIBCO Documentation and Support Services

For information about this product, you can read the documentation, contact TIBCO
Support, and join TIBCO Community.
How to Access TIBCO Documentation

Documentation for TIBCO products is available on the TIBCO Product Documentation
website, mainly in HTML and PDF formats.
The TIBCO Product Documentation website is updated frequently and is more current
than any other documentation included with the product. To access the latest
documentation, visit https://docs.tibco.com.
Product-Specific Documentation
Documentation for TIBCO BusinessWorks™ Container Edition is available on the TIBCO
BusinessWorks™ Container Edition Product Documentation page.
To directly access documentation for this product, double-click the following file:
TIBCO_HOME/release_notes/TIB_bwce_2.6.2_docinfo.html where TIBCO_HOME is the top-level
directory in which TIBCO products are installed. On Windows, the default TIBCO_HOME
is C:\tibco. On UNIX systems, the default TIBCO_HOME is /opt/tibco.
The following documents for this product can be found in the TIBCO Documentation site:
l TIBCO BusinessWorks™ Container Edition Release Notes
l TIBCO BusinessWorks™ Container Edition Application Development
l TIBCO BusinessWorks™ Container Edition Application Monitoring and
Troubleshooting
l TIBCO BusinessWorks™ Container Edition Bindings and Palettes Reference
l TIBCO BusinessWorks™ Container Edition Concepts
l TIBCO BusinessWorks™ Container Edition Error Codes
l TIBCO BusinessWorks™ Container Edition Getting Started
l TIBCO BusinessWorks™ Container Edition Migration
l TIBCO BusinessWorks™ Container Edition Performance Benchmarking and

162 | TIBCO Documentation and Support Services
Tuning
l TIBCO BusinessWorks™ Container Edition REST Implementation
l TIBCO BusinessWorks™ Container Edition Refactoring Best Practices
l TIBCO BusinessWorks™ Container Edition Samples
How to Join TIBCO Community

TIBCO Community is the official channel for TIBCO customers, partners, and employee
subject matter experts to share and access their collective experience. TIBCO
Community offers access to Q&A forums, product wikis, and best practices. It also offers
access to extensions, adapters, solution accelerators, and tools that extend and enable
customers to gain full value from TIBCO products. In addition, users can submit and vote
on feature requests from within the TIBCO Ideas Portal. For a free registration, go to
https://community.tibco.com.

163 | Legal and Third-Party Notices
Legal and Third-Party Notices

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF
SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE
FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED
TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE
USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND
CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED
SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT,
THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING
DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE
LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR
CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE
“LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE
TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE
OF AND AN AGREEMENT TO BE BOUND BY THE SAME.
This document is subject to U.S. and international copyright laws and treaties. No part of this
document may be reproduced in any form without the written authorization of TIBCO Software Inc.
TIBCO, the TIBCO logo, the TIBCO O logo, TIBCO ActiveMatrix BusinessWorks, TIBCO
ActiveSpaces, TIBCO Business Studio for BusinessWorks, TIBCO Designer, TIBCO Enterprise
Message Service, TIBCO Hawk, TIBCO Rendezvous, and TIBCO Runtime Agent are either
registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other
countries.
Java and all Java based trademarks and logos are trademarks or registered trademarks of Oracle
Corporation and/or its affiliates.
This document includes fonts that are licensed under the SIL Open Font License, Version 1.1,
which is available at: https://scripts.sil.org/OFL
Copyright (c) Paul D. Hunt, with Reserved Font Name Source Sans Pro and Source Code Pro.
All other product and company names and marks mentioned in this document are the property of
their respective owners and are mentioned for identification purposes only.
This software may be available on multiple operating systems. However, not all operating system
platforms for a specific software version are released at the same time. See the readme file for the
availability of this software version on a specific operating system platform.

164 | Legal and Third-Party Notices
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL

ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE
CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO
SOFTWARE 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

OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE,
INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.
This and other products of TIBCO Software Inc. may be covered by registered patents. Please
refer to TIBCO's Virtual Patent Marking document (https://www.tibco.com/patents) for details.
Copyright © 2015-2021. TIBCO Software Inc. All Rights Reserved.

TIB Bwce 2.6.2 Error Codes

Uploaded by

Copyright:

Available Formats

TIB Bwce 2.6.2 Error Codes

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TIB Bwce 2.6.2 Error Codes

Uploaded by

Copyright:

Available Formats

TIBCO BusinessWorks™

Copyright © 2015-2021. TIBCO Software Inc. All Rights Reserved.

Message Codes Naming Convention 4

Shared Resources 146

TIBCO BusinessWorks™ Container Edition Error Codes

HTTP Connector Error Codes 149

TIBCO Documentation and Support Services 161

Legal and Third-Party Notices 163

TIBCO BusinessWorks™ Container Edition Error Codes

Message Codes Naming Convention

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 BusinessWorks Container Edition Palette specific

TIBCO-BW-SR BusinessWorks Container Edition Shared Resource

TIBCO-BW-SR-<UniqueName> BusinessWorks Container Edition specific Shared

TIBCO BusinessWorks™ Container Edition Error Codes

TIBCO-BW-STATS BusinessWorks Container Edition Stats Collector

TIBCO-THOR-FRWK Thor Framework

TIBCO BusinessWorks™ Container Edition Error Codes

SOAP Binding Error Codes

Error Codes Error Message Error Resolution

TIBCO-BW- SOAP BindingFactory is initialized with This is a internal resolution

TIBCO-BW- Failed to obtain HTTP Connector resource This is an internal product

TIBCO-BW- Failed to obtain HTTP Connector resource This is an internal product

TIBCO-BW- SOAP BindingFactory is initialized with This is a internal resolution

TIBCO BusinessWorks™ Container Edition Error Codes

Error Codes Error Message Error Resolution

TIBCO-BW- Failed to initialize SOAP Binding. Binding BW_SOAP_BINDING_

TIBCO-BW- Failed to initialize SOAP Binding. This is an internal product

TIBCO-BW- Failed to initialize SOAP Binding. This is an internal product

TIBCO BusinessWorks™ Container Edition Error Codes

Error Codes Error Message Error Resolution

TIBCO-BW- Operation Configuration for Operation Ensure that SOAP Binding

TIBCO-BW- Failed to initialize SOAP Service Binding This is an internal product

TIBCO BusinessWorks™ Container Edition Error Codes

Error Codes Error Message Error Resolution

TIBCO-BW- Failed to initialize SOAP Reference This is an internal product

TIBCO-BW- Malformed MIME Message received. Ensure that the MIME

TIBCO-BW- Failed to create SoapServiceBinding [{0}], This is a internal resolution

TIBCO-BW- Failed to initialize SoapServiceBinding Ensure that the configuration

TIBCO-BW- Failed to add transport dependency for Ensure that the

TIBCO BusinessWorks™ Container Edition Error Codes

Error Codes Error Message Error Resolution

TIBCO-BW- Failed to initialize SoapServiceBinding Ensure that each SOAP/HTTP

TIBCO-BW- Failed to initialize SoapServiceBinding Ensure that the combination of

TIBCO-BW- Failed to send SOAP Fault message to This is an internal product

TIBCO BusinessWorks™ Container Edition Error Codes

Error Codes Error Message Error Resolution

SOAP- SoapServiceBinding [{1}], Application [{2}: configuration, if any, done on

TIBCO-BW- The BusinessWorks ProcessService Ensure that the BW Process

TIBCO-BW- Unable to populate SOAP Binding This is an internal product

TIBCO-BW- An Error occurred while cleaning up the This is an internal product

TIBCO BusinessWorks™ Container Edition Error Codes

Error Codes Error Message Error Resolution

TIBCO-BW- An interrupted fault occurred while waiting This is an internal product