TIBCO BusinessWorks™

Container Edition
Error Codes
Version 2.7.1
February 2022

Copyright © 2015-2022. 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 87

Palettes 89
File Palette Error Codes 89
FTP Palette Error Codes 92
General Palette Error Codes 94
HTTP Palette Error Codes 96
Java Palette Error Codes 100
JDBC Palette Error Codes 107
JMS Palette Error Codes 112
Mail Palette Error Codes 115
Parse Palette Error Codes 119
TCP Palette Error Codes 125
XML Palette Error Codes 127

Shared Resources 130

Shared Resource Framework Error Codes 130
Data Format Error Codes 132
FTP Connection Error Codes 132

TIBCO BusinessWorks™ Container Edition Error Codes

3 | Contents

HTTP Client Error Codes 133

HTTP Connector Error Codes 133
Java Global Instance Error Codes 136
JMS Connection Error Codes 138
JDBC Connection Error Codes 139
JNDI Configuration Error Codes 142
Proxy Configuration Error Codes 142
SMTP Resource Error Codes 143
TCP Connection 144

TIBCO Documentation and Support Services 145

Legal and Third-Party Notices 147

TIBCO BusinessWorks™ Container Edition Error Codes

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 activity

Name>

TIBCO-BW-SR BusinessWorks Container Edition Shared Resource API

layer

TIBCO BusinessWorks™ Container Edition Error Codes

5 | Message Codes Naming Convention

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

Resource

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 message describes the issue. Sometimes, the message can contain parameters shown
as ({N}), where N is an integer.

TIBCO BusinessWorks™ Container Edition Error Codes

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

Codes

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

BINDING- incorrect BindingConfiguration for the SOAP message. Resolution not
SOAP- Service Binding. required.
001010

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

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

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

BINDING- incorrect BindingConfiguration for the SOAP message. Resolution not
SOAP- Reference Binding. required.
001031

TIBCO-BW- Failed to parse binding meta data file [{0}] in Ensure that the xml file
BINDING- bundle [{1}] due to exception [{2}]. contents are valid and well

TIBCO BusinessWorks™ Container Edition Error Codes

7 | Bindings

Error Error Message Error Resolution

Codes

SOAP- formed.
001040

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}]. A Ensure that Binding Name of
BINDING- Binding with name [{2}] is already registered. the SOAP Interceptor is
SOAP- 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 Module Ensure that the SOAP
BINDING- [{0}], due to exception [{1}]. Root exception Interceptor deployed follows
SOAP- message is [{2}]. the Axis2 Module protocol.
001070

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

BINDING- Name is not specified. MISSING_ERROR.resolution =
SOAP- Make sure all Bindings in the
001080 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. Application This is an internal product

BINDING- Name is not available. error. Contact TIBCO support.
SOAP-
001090

TIBCO BusinessWorks™ Container Edition Error Codes

8 | Bindings

Error Error Message Error Resolution

Codes

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

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

TIBCO-BW- Failed to locate WSDL definition for port type Ensure that the a WSDL exist
BINDING- [{0}]. with port type [{0}] in the
SOAP- application module.
001130

TIBCO-BW- MEP [{0}] is not supported. Review the WSDL Ensure that the MEP
BINDING- definition for Port type [{1}]. definition for Port type [{1}] is
SOAP- either IN-OUT OR IN-ONLY
001140

TIBCO-BW- Failed to recognize the MEP for Port type [{0}]. Ensure that the MEP
BINDING- definition for Port type [{0}] is
SOAP- either IN-OUT OR IN-ONLY
001150

TIBCO-BW- Failed to find message receiver for MEP [{0}] Ensure that the MEP
BINDING- for port type [{1}]. definition for Port type [{1}] is
SOAP- either IN-OUT OR IN-ONLY
001160

TIBCO-BW- SOAP Binding [{1}] for portType [{0}] is missing Ensure that the SOAP Binding
BINDING- Transport Configuration. [{1}] for port type [{0}] is
SOAP- configured with a Transport.
001170

TIBCO-BW- Operation Configuration for Operation [{0}], Ensure that SOAP Binding
BINDING- Port Type [{1}], SOAP Binding [{2}] is missing. [{2}] is in sync with WSDL.
SOAP- Ensure that SOAP Binding [{2}] is in sync with
001180 WSDL

TIBCO-BW- Failed to initialize SOAP Service Binding [{0}]. This is an internal product

TIBCO BusinessWorks™ Container Edition Error Codes

9 | Bindings

Error Error Message Error Resolution

Codes

BINDING- Promoted Name for the Binding is missing. error. Contact TIBCO support.
SOAP-
001110

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

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

TIBCO-BW- Failed to load WSDL definition for namespace Make sure the WSDL with
BINDING- [{0}]. namespace [{0}] exists in the
SOAP- application module.
001130

TIBCO-BW- Malformed MIME Message received. Failed to Ensure that the MIME
BINDING- parse the attachments in the received message Message is well formed with
SOAP- for Operation [{0}], SoapBinding [{1}], correct mime boundaries.
500009 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 SOAP Ensure the SOAP Model
BINDING- Binding. version in .bwm file is of
SOAP- format [0-9].[0-9].[0-9]
500011

TIBCO-BW- Failed to initialize SoapServiceBinding [{0}], Ensure that the configuration

BINDING- Application [{1}:{2}] due to exception [{3}] and context mapping. if any,
SOAP- done on SoapServiceBinding
500020 [{0}] are correct.

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

TIBCO BusinessWorks™ Container Edition Error Codes

10 | Bindings

Error Error Message Error Resolution

Codes

BINDING- SoapServiceBinding [{0}], Application [{1}:{2}] SoapServiceBinding [{0}] is

SOAP- configured with a Shared
500030 Transport Resource.

TIBCO-BW- Failed to initialize SoapServiceBinding [{0}]. A Ensure that each SOAP/HTTP

BINDING- Service Endpoint URI [{1}] is already registered service has unique URL.
SOAP-
500040

TIBCO-BW- Failed to initialize SoapServiceBinding [{0}]. Ensure that the combination

BINDING- The operation [{1}] with soapaction [{2}] is of "Soap Action" and
SOAP- already registered for destination [{3}] with "MessageStyle:Destination"
500050 Message Style [{4}]. should be unique.

TIBCO-BW- Failed to send SOAP Fault message to the This is an internal product
BINDING- consumer of the service for Operation [{0}], error. Contact TIBCO support.
SOAP- SoapServiceBinding [{1}], Application [{2}:{3}]
500060 due to exception [{4}]. Root Exception
message: {5}

TIBCO-BW- Failed to process Reply message for Operation Ensure that the Binding
BINDING- [{0}], SoapServiceBinding [{1}], Application [{2}: configuration and Context
SOAP- {3}] due to exception [{4}]. Sending Undeclared Configuration, if any, done on
500070 Fault message to the consumer of this service. SoapServiceBinding [{1}] are
Root Exception message: [{5}] correct.

TIBCO-BW- Error occurred while processing Service Ensure that the Context
BINDING- Request messages Context Information for Mapping done on
SOAP- Operation [{0}], SoapServiceBinding [{1}], SoapServiceBinding [{1}] are
500080 Application [{2}:{3}] due to exception [{4}]. Root correct.
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}]:{3}] configuration, if any, done on
500090 due to exception [{4}]. Root Exception SoapServiceBinding [{1}] are

TIBCO BusinessWorks™ Container Edition Error Codes

11 | Bindings

Error Error Message Error Resolution

Codes

message: {5} correct.

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}:{3}] configuration, if any, done on
500100 due to exception [{4}]. Sending Undeclared SoapServiceBinding [{1}] are
Fault message to the consumer of this service. correct.
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}:{3}] configuration, if any, done on
500105 due to exception [{4}].Root Exception message: SoapServiceBinding [{1}] are
{5} correct.

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

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

BINDING- implementation failed to complete the request construct is correct.
SOAP- for the Operation [{0}], SoapServiceBinding
500120 [{1}], Application [{2}:{3}] and returned
exception [{4}]. Sending Undeclared Fault
message to the consumer of this service. Root
Exception 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 SOAP This is an internal product

TIBCO BusinessWorks™ Container Edition Error Codes

12 | Bindings

Error Error Message Error Resolution

Codes

BINDING- Binding Configuration Resources due to error. Contact TIBCO support.

SOAP- exception [{1}]
500131

TIBCO-BW- An interrupted fault occurred while waiting for This is an internal product
BINDING- the Service Request message to be processed error. Contact TIBCO support.
SOAP- for Operation [{0}], SoapServiceBinding [{1}],
500140 Application [{2}:{3}] due to exception [{4}].
Sending Undeclared Fault message to the
consumer of this service. Root Exception
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 for Mapping and configuration
SOAP- Operation [{0}], SoapServiceBinding [{1}], done on SoapServiceBinding
500170 Application [{2}:{3}] due to exception [{4}]. [{1}] are correct.
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}:{2}] error. Contact TIBCO support.
SOAP- due to exception [{3}]
500190

TIBCO-BW- Failed to stop JMS transport primitive for This is an internal product

TIBCO BusinessWorks™ Container Edition Error Codes

13 | Bindings

Error Error Message Error Resolution

Codes

BINDING- SoapServiceBinding [{0}], Application [{1}:{2}] error. Contact TIBCO support.

SOAP- due to exception [{3}]
500200

TIBCO-BW- Failed to Initialize JMS transport primitive for Ensure that the transport
BINDING- SoapServiceBinding [{0}], Application [{1}:{2}] configuration done on
SOAP- due to exception [{3}] SoapServiceBinding [{0}] are
500210 correct.

TIBCO-BW- Failed to read incoming JMS raw message due This is an internal product
BINDING- 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}:{2}] configuration done on
SOAP- due to exception [{3}] SoapServiceBinding [{0}] are
500240 correct.

TIBCO-BW- Failed to process service request message for Ensure that the Service
BINDING- SoapServiceBinding [{0}], Application [{1}:{2}] Provider is sending a correct
SOAP- due to exception [{3}] .Root exception message SOAP Envelope.
500250 : [{4}]

TIBCO-BW- Failed to send Service Reply message for This is an internal product
BINDING- Operation [{0}], SoapServiceeBinding [{1}], error. Contact TIBCO support.
SOAP- Application [{2}:{3}] due to exception [{4}]
500260

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}:{3}]
500270 due to exception [{4}]

TIBCO-BW- Failed to authenticate Request message for Check if the identity resource
BINDING- Operation [{0}], SoapServiceBinding [{1}], referenced in Http Client

TIBCO BusinessWorks™ Container Edition Error Codes

14 | Bindings

Error Error Message Error Resolution

Codes

SOAP- Application [{2}:{3}] due to exception [{4}]. resource contains username

500280 and password.

TIBCO-BW- Failed to authenticate Request message for Check if the identity resource
BINDING- Operation [{0}], SoapServiceBinding [{1}], referenced in Http Client
SOAP- Application [{2}:{3}]. Username and Password resource contains username
500281 is not set. and password.

TIBCO-BW- Failed to authenticate Request message for This is an internal product

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

TIBCO-BW- Malformed SOAP Request message received for Check if the SOAP Request
BINDING- Operation [{0}], SoapServiceBinding [{1}], Message is well formed.
SOAP- Application [{2}:{3}]. Root Exception message:
500300 [{5}]

TIBCO-BW- Failed to create SoapReferenceBinding [{0}], This is an internal product

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

TIBCO-BW- Failed to create SoapReferenceEndpoint [{0}] Ensure that configurations

BINDING- due to exception [{1}] done on Reference Binding
SOAP- [{0}] are correct.
550020

TIBCO-BW- Failed to initialize SoapReferenceBinding [{0}], Ensure that the Binding and
BINDING- Application [{1}:{2}] due to exception [{3}] Transport configuration on
SOAP- SoapReferenceBinding [{0}]
550030 are correct.

TIBCO-BW- Failed to add transport dependency for This is an internal product

BINDING- SoapReferenceBinding [{0}], Application [{1}: error. Contact TIBCO support.
SOAP- {2}]

TIBCO BusinessWorks™ Container Edition Error Codes

15 | Bindings

Error Error Message Error Resolution

Codes

550040

TIBCO-BW- Failed to destroy SoapReferenceBinding [{0}], This is an internal product

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

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

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

TIBCO-BW- Received Declared Fault. Failed to release This is an internal product

BINDING- transport resources for Operation [{0}], error. Contact TIBCO support.
SOAP- SoapReferenceBinding [{1}], Application [{2}:
550070 {3}] due to exception [{4}]

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

TIBCO-BW- Received SOAP Fault from the service provider This is an internal message
BINDING- of the Operation [{0}], SoapReferenceBinding sent to the framework for
SOAP- [{1}], Application [{2}:{3}]. SOAP Fault received: server error. Resolution not
550100 [{4}] required.

TIBCO-BW- Received SOAP Fault from the service provider This is an internal message
BINDING- of the Operation [{0}], SoapReferenceBinding sent to the framework for
SOAP- [{1}], Application [{2}:{3}]. SOAP Fault received: client error. Resolution not
550101 [{4}] required.

TIBCO-BW- Error occurred while processing the declared Ensure that the declared fault
BINDING- fault message from the service provider of the send back by the Service
SOAP- Operation [{0}], SoapReferenceBinding [{1}], Provider is valid and well
550110 Application [{2}:{3}] due to exception [{4}] formed SOAP Fault.

TIBCO BusinessWorks™ Container Edition Error Codes

16 | Bindings

Error Error Message Error Resolution

Codes

TIBCO-BW- Error occurred while processing reply message Ensure that Message Part and
BINDING- from the service provider of the Operation Header Configuration done
SOAP- [{0}], SoapReferenceBinding [{1}], Application on SoapReferenceBinding
550120 [{2}:{3}] due to exception [{4}] [{1}] are correct.

TIBCO-BW- SOAPEnvelope must contain a body element Ensure that Service Provider
BINDING- which is either first or second child element of has send a valid SOAP
SOAP- the SOAPEnvelope. Envelope.
550121

TIBCO-BW- Error occurred while processing reply message Ensure that Context
BINDING- attachments from the service provider of the configuration and Mapping
SOAP- Operation [{0}], SoapReferenceBinding [{1}], for the attachment done on
550130 Application [{2}:{3}] due to exception [{4}] SoapReferenceBinding [{1}] is
correct.

TIBCO-BW- Failed to Initialize JMS transport primitive for Ensure that the Transport
BINDING- SoapReferenceBinding [{0}], Application [{1}: Sender configurations are
SOAP- {2}] due to exception [{3}] correct.
550140

TIBCO-BW- Failed to send Reference Request message for Ensure that the Message
BINDING- Operation [{0}], SoapReferenceBinding [{1}], Configuration done on
SOAP- Application [{2}:{3}] due to exception [{4}] SoapReferenceBinding [{1}]
550170 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 [{2}: SoapReferenceBinding [{1}]
550180 {3}] due to exception [{4}] are correct

TIBCO-BW- Failed to update HTTP Transport Ensure that the port number
BINDING- configurations before sending the Reference configuration for
SOAP- Request message for Operation [{0}], SoapReferenceBinding [{1}] is
550190 SoapReferenceBinding [{1}], Application [{2}: valid
{3}] due to exception [{4}].

TIBCO BusinessWorks™ Container Edition Error Codes

17 | Bindings

Error Error Message Error Resolution

Codes

TIBCO-BW- Failed to create the HTTP Client required for Ensure that the Endpoint URL
BINDING- sending the Reference Request message for is in correct format.
SOAP- Operation [{0}], SoapReferenceBinding [{1}],
550210 Application [{2}:{3}] due to exception [{4}]

TIBCO-BW- Failed to serialize JMS transport message due Ensure that the configuration
BINDING- to exception [{1}]. done on Reference Binding
SOAP- are correct.
550220

TIBCO-BW- Failed to convert JMS message to string due to Ensure that the configuration
BINDING- exception [{1}]. done on Reference Binding
SOAP- are correct.
550230

TIBCO-BW- Failed to create Endpoint URL for Operation Ensure that the Endpoint URI
BINDING- [{0}], SoapReferenceBinding [{1}], Application configuration on
SOAP- [{2}:{3}] due to exception [{4}] SOAPRefernceBinding [{1}] is
550240 correct.

TIBCO-BW- Unable to receive response from the service Ensure that the Service
BINDING- provider for Operation [{0}], Provider is available.
SOAP- SoapReferenceBinding [{1}], Application [{2}:
555000 {3}] due to exception [{4}]. Message Received:
[{5}]

TIBCO-BW- Unable to receive response from the service Ensure that HTTP Client
BINDING- provider for Operation [{0}], configurations are configured
SOAP- SoapReferenceBinding [{1}], Application [{2}: as per service provider
555010 {3}] due to exception [{4}]. Message Received: requirements.
[{5}]

TIBCO-BW- Unable to receive response from the service Ensure that HTTP Client
BINDING- provider for Operation [{0}], configurations are configured
SOAP- SoapReferenceBinding [{1}], Application [{2}: as per service provider
555020 {3}] due to exception [{4}]. Message Received: requirements.

TIBCO BusinessWorks™ Container Edition Error Codes

18 | Bindings

Error Error Message Error Resolution

Codes

[{5}]

TIBCO-BW- Unable to send request the service provider Ensure that HTTP Client
BINDING- for Operation [{0}], SoapReferenceBinding [{1}], configurations are configured
SOAP- Application [{2}:{3}] due to exception [{4}]. as per service provider
555030 Message Received: [{5}] requirements.

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

REST Binding Error Codes

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

Error Error Message Error Resolution

Codes

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 BusinessWorks™ Container Edition Error Codes

19 | Bindings

Error Error Message Error Resolution

Codes

TIBCO-BW- Request Received for Operation [{0}] This is a debug message and
BINDING- resolution is not applicable.
REST-
200004

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

BINDING- resolution is not applicable.
REST-
200008

TIBCO-BW- Creating XML Message for JSON Message. This is a debug message and
BINDING- Element details - targetnamespace [{0}] resolution is not applicable.
REST- 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

TIBCO BusinessWorks™ Container Edition Error Codes

20 | Bindings

Error Error Message Error Resolution

Codes

BINDING- resolution is not applicable.

REST-
200011

TIBCO-BW- REST Binding Authentication is enabled.

BINDING- Trying to authenticate using the
REST- Authorization Header of the request
200012

TIBCO-BW- Expected JSON Content-Type. Got XML The Client needs to be notified to
BINDING- Instead. Replying with error to client 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 to
BINDING- Instead. Replying with error to client 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 REST
BINDING- Service Binding binding
REST-
500001

TIBCO-BW- NO_RESOURCE_URL_SPECIFIED = No Check configuration of the REST

BINDING- relative resource url specified to deploy binding for the value of the
REST- REST Resource 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 BusinessWorks™ Container Edition Error Codes

21 | Bindings

Error Error Message Error Resolution

Codes

TIBCO-BW- Error Occurred while trying to create Check configuration of the REST
BINDING- Jersey REST Resource for binding [{1}] binding specified in the error
REST- message
500004

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

TIBCO-BW- Unable to stop REST Binding with name Check configuration of the REST
BINDING- [{0}} binding specified in the error
REST- message
500005

TIBCO-BW- Error Occurred while parsing and creating Invalid values were sent by the
BINDING- HTTP Headers. Responding to client with client in the HTTP headers.
REST- error message.
500006

TIBCO-BW- Error Occurred while creating Parameters Invalid values were passed for the
BINDING- Part. Responding to client with error Parameters element. Check the
REST- message. client request and the
500007 configuration of the REST
Binding.

TIBCO-BW- Error Occurred while creating User Part. Invalid values were passed for the
BINDING- Responding to client with error message. Parameters element. Check the
REST- 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 exception for possible reasons of
REST- thrown by the HTTP Connector for failure. For example, Some of
500009 possible configuration issues them could be related to

TIBCO BusinessWorks™ Container Edition Error Codes

22 | Bindings

Error Error Message Error Resolution

Codes

overlapping context paths or an

address in use.

TIBCO-BW- The HTTP Connector [{0}] shared resource

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

TIBCO-BW- The HTTP Connector [{0}] shared resource

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

TIBCO-BW- AUTHENTICATION_FAILED = Authentication

BINDING- failed for client request. A 401 status code
REST- has been sent to the client with the realm
500012 as [{0}].

TIBCO-BW- WSDL_CACHE_NOT_FOUND = An error

BINDING- 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

TIBCO BusinessWorks™ Container Edition Error Codes

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

Codes

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

O-BW- TIBCO Support.
CORE-
00000
1

TIBC BWActivityManager Registration This is an internal product error. Contact

O-BW- Error. The BWActivityManager TIBCO Support.
CORE- argument provided to the BW
00001 Engine is null.
0

TIBC Failed to initialize BW Engine. The This is an internal product error. Contact
O-BW- BW Engine was initialized without TIBCO Support.
CORE- a logger object.
00001
2

TIBC Failed to initialize BW Engine. This is an internal product error. Contact

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

TIBCO BusinessWorks™ Container Edition Error Codes

24 | Core

Error Error Message Error Resolution

Codes

TIBC Failed to initialize BW Engine. The This is an internal product error. Contact
O-BW- BWActivityManager was not TIBCO Support.
CORE- registered correctly with the BW
00002 Engine.
0

TIBC Failed to initialize BW Engine. The This is an internal product error. Contact
O-BW- BW Crypto service was not TIBCO Support.
CORE- registered correctly with the BW
00002 Engine.
2

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

TIBC Failed to enable BW Debugger. The This is an internal product error. Contact
O-BW- BW Engine has not been initialized. TIBCO Support.
CORE-
00002
6

TIBC The BW Debugger is already This is an internal product error. Contact

O-BW- enabled state and it can not be TIBCO Support.
CORE- enabled again.
00002
8

TIBC Unable to disable BW Debugger. This is an internal product error. Contact

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

TIBCO BusinessWorks™ Container Edition Error Codes

25 | Core

Error Error Message Error Resolution

Codes

TIBC Attempt to disable the BW This is an internal product error. Contact

O-BW- Debugger encountered exception TIBCO Support.
CORE- [{0}]
00003
2

TIBC Unable to enable BW Event This is an internal product error. Contact

O-BW- Publisher. The BW Engine has not TIBCO Support.
CORE- been initialized.
00003
4

TIBC BW Engine configuration data does This is an internal product error. Contact
O-BW- not contain AppNode name. TIBCO Support.
CORE-
00003
6

TIBC BW Engine configuration data does This is an internal product error. Contact
O-BW- not contain AppSpace name. TIBCO Support.
CORE-
00003
8

TIBC BW Engine configuration data does This is an internal product error. Contact
O-BW- not contain Domain name. TIBCO Support.
CORE-
00004
0

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

TIBCO BusinessWorks™ Container Edition Error Codes

26 | Core

Error Error Message Error Resolution

Codes

TIBC The operation [{0}] is not This is an internal product error. Contact
O-BW- supported for the BX Executable TIBCO Support.
CORE- Module. ModuleName={1},
00005 ModuleVersion={2}
4

TIBC The operation [{0}] is not This is an internal product error. Contact
O-BW- supported for the BW Job Shared TIBCO Support.
CORE- Variable.
00005
6

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

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

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

O-BW- EngineManagement due to TIBCO Support.
CORE- exception [{0}]
00005
8

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

TIBC Invalid 'BWModuleHandle'. The BW This is an internal product error. Contact

O-BW- module represented by this handle TIBCO Support.
CORE- has been already un-installed or
00010 the handle has been already
2 destroyed.

TIBCO BusinessWorks™ Container Edition Error Codes

27 | Core

Error Error Message Error Resolution

Codes

TIBC Unable to obtain process This is an internal product error. Contact

O-BW- templates referenced by BW TIBCO Support.
CORE- Module, the BW Engine
00010 encountered exception.
4 ModuleName[{0}], ModuleVersion
[{1}], Exception[{2}].

TIBC Unable to obtain GenXDM This is an internal product error. Contact

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

TIBC Unable to obtain GenXDM This is an internal product error. Contact

O-BW- SchemaComponentCache for the TIBCO Support.
CORE- BW Module [{0}]. The operation
00011 [{1}] returned exception [{2}]
8

TIBC Unable to obtain GenXDM This is an internal product error. Contact

O-BW- SchemaComponentCache for the TIBCO Support.
CORE- BW Module [{0}:{1}] due to
00012 exception [{2}]
0

TIBC Unable to obtain "BundleContext" This is an internal product error. Contact

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

TIBC Unable to obtain "BundleContext" This is an internal product error. Contact

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

TIBCO BusinessWorks™ Container Edition Error Codes

28 | Core

Error Error Message Error Resolution

Codes

TIBC Unable to obtain ServiceReference This is an internal product error. Contact

O-BW- for the cache service [{0}]. The TIBCO Support.
CORE- operation
00012 "BundleContext.getServiceReferenc
6 e" for BW module [{1}:{2}] returned
"null".

TIBC Unable to obtain ServiceReference This is an internal product error. Contact

O-BW- for the cache service [{0}]. The TIBCO Support.
CORE- operation
00012 "BundleContext.getServiceReferenc
8 e" for BW module [{1}:{2}] returned
exception [{3}]

TIBC Unable to obtain XSD cache service This is an internal product error. Contact
O-BW- [{0}] for the BW module [{1}:{2}]. TIBCO Support.
CORE- The operation [{3}] returned "null".
00013
0

TIBC Unable to obtain XSD cache service This is an internal product error. Contact
O-BW- [{0}] for the BW module [{1}:{2}]. TIBCO Support.
CORE- The operation [{3}] returned
00013 exception [{4}]
1

TIBC Unable to obtain WSDL cache This is an internal product error. Contact
O-BW- service [{0}] for the BW module [{1}: TIBCO Support.
CORE- {2}]. The operation [{3}] returned
00013 "null".
2

TIBC Unable to obtain WSDL cache This is an internal product error. Contact
O-BW- service [{0}] for the BW module [{1}: TIBCO Support.
CORE- {2}]. The operation [{3}] returned
00013 exception [{4}]

TIBCO BusinessWorks™ Container Edition Error Codes

29 | Core

Error Error Message Error Resolution

Codes

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

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

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

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

TIBC Unable to obtain BxWSDLResolver This is an internal product error. Contact

O-BW- for the WSDL namespace [{0}], TIBCO Support.
CORE- Location [{1}] that is associated
00013 with the BW Module [{2}:{3}],
6 DeploymentUnit [{4}:{5}] due to
exception [{6}]

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

TIBC Unable to obtain GenXDM WSDL This is an internal product error. Contact
O-BW- Module for the WSDL namespace [  TIBCO Support.

TIBCO BusinessWorks™ Container Edition Error Codes

30 | Core

Error Error Message Error Resolution

Codes

CORE- {0} ] that is associated with the BW

00013 Module [{1}:{2}], DeploymentUnit
8 [{3}:{4}]. The operation "{5}"
returned "null". 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-BW- details from the GenXDM WSDL TIBCO Support.
CORE- Module for the WSDL namespace [ 
00014 {0} ] that is referenced in the BW
0 Module [{1}:{2}] due to exception
[{3}].

TIBC Unable to obtain WSDL Definition This is an internal product error. Contact
O-BW- namespace details from the TIBCO Support.
CORE- GenXDM WSDL Module for the
00014 WSDL namespace [ {0} ] that is
2 associated with the BW Module
[{1}:{2}] due to exception [{3}].

TIBC Unable to obtain WSDL Target This is an internal product error. Contact
O-BW- namespace from the GenXDM TIBCO Support.
CORE- WSDL Module for the WSDL
00014 namespace [ {0} ] that is associated
4 with the BW Module [{1}:{2}] due to
exception [{3}].

TIBC Unable to obtain WSDL Interface This is an internal product error. Contact
O-BW- details from the GenXDM WSDL TIBCO Support.
CORE- Module for the PortType [{0}], that
00014 is associated with the BW Module
6 [{1}:{2}]. The operation "{3}"

TIBCO BusinessWorks™ Container Edition Error Codes

31 | Core

Error Error Message Error Resolution

Codes

returned exception [{4}].

TIBC Unable to obtain WSDL Interface This is an internal product error. Contact
O-BW- details from the GenXDM WSDL TIBCO Support.
CORE- Module for the PortType [{0}], that
00014 is associated with the BW Module
8 [{1}:{2}]. The operation "{3}"
returned null.

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

O-BW- details from the GenXDM WSDL TIBCO Support.
CORE- Interface for the WSDL namespace
00015 [ {0} ] that is associated with the
0 BW Module [{1}:{2}] due to
exception [{3}].

TIBC Invalid BWBxWSDLResolver. The This is an internal product error. Contact

O-BW- instance of this TIBCO Support.
CORE- BWBxWSDLResolver has been
00015 already released.
2

TIBC The initial value mode [{0}] This is an internal product error. Contact
O-BW- specified for the {1} [{2}] in BW TIBCO Support.
CORE- Module [{3}:{4}], DeploymentUnit
00016 [{5}:{6}] is invalid.
0

TIBC The QName value [{0}] specified for This is an internal product error. Contact
O-BW- the {1} [{2}] in BW Module [{3}] is TIBCO Support.
CORE- invalid or malformed.
00016
2

TIBC Invalid 'BWComponentHandle'. The This is an internal product error. Contact

O-BW- BW Component represented by this TIBCO Support.

TIBCO BusinessWorks™ Container Edition Error Codes

32 | Core

Error Error Message Error Resolution

Codes

CORE- handle has been already un-

00020 installed or the handle has been
2 already destroyed.

TIBC Unable to create This is an internal product error. Contact

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

TIBC Unable to create This is an internal product error. Contact

O-BW- ServiceEndpointRequestHandler for TIBCO Support.
CORE- BW Component due to invalid BW
00020 Process ServiceName [{0}].
6 ComponentName={1},
ComponentVersion={2}

TIBC Error occurred while creating This is an internal product error. Contact
O-BW- ServiceEndpointRequestHandler for TIBCO Support.
CORE- service [{0}], BW Component [{1}],
00020 Application [{2}:{3}]. Exception[{4}].
8

TIBC Unable to create This is an internal product error. Contact

O-BW- ServiceEndpointRequestHandler for TIBCO Support.
CORE- service [{0}], BW Component [{1}].
00021 The operation
0 "BxSystem.getInterfaceProvider"
returned "null".

TIBC Received unexpected exception This is an internal product error. Contact

O-BW- [{0}] from the service binding TIBCO Support.
CORE- associated with the component
00021 service [{1}], Application [{2}] on
2 invocation of method [{3}].

TIBCO BusinessWorks™ Container Edition Error Codes

33 | Core

Error Error Message Error Resolution

Codes

TIBC Unable to obtain "BundleContext". This is an internal product error. Contact

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

TIBC Unable to obtain "BundleContext" This is an internal product error. Contact

O-BW- due to exception [{0}] TIBCO Support.
CORE-
00021
6

TIBC Unable to obtain GenXDM WSDL This is an internal product error. Contact
O-BW- Module for the WSDL namespace TIBCO Support.
CORE- [{0}] that is associated with the BW
00022 Component [{1}], Application[{2}:
0 {3}]. The operation "{4}" returned
exception [{5}]

TIBC Unable to obtain GenXDM WSDL This is an internal product error. Contact
O-BW- Module for the WSDL namespace TIBCO Support.
CORE- [{0}] that is associated with the BW
00022 Component [{1}], Application[{2}:
2 {3}]. The operation "{4}" returned
"null".

TIBC Unable to obtain WSDL Interface

O-BW- details from the GenXDM WSDL
CORE- Module for the PortType [{0}], that
00022 is associated with the BW
4 Component [{1}], Application[{2}:
{3}]. The operation "{4}" returned
exception [{5}].

TIBC Unable to obtain WSDL Interface This is an internal product error. Contact
O-BW- details from the GenXDM WSDL TIBCO Support.

TIBCO BusinessWorks™ Container Edition Error Codes

34 | Core

Error Error Message Error Resolution

Codes

CORE- Module for the PortType [{0}], that

00022 is associated with the BW
6 Component [{1}], Application[{2}:
{3}]. The operation "{4}" returned
null.

TIBC Unable to obtain ServiceReference

O-BW- for the cache service [{0}]. The
CORE- operation "{1}" returned "null".
00022
8

TIBC Unable to obtain ServiceReference This is an internal product error. Contact

O-BW- for the cache service [{0}] due to TIBCO Support.
CORE- exception [{1}]
00023
0

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

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

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

O-BW- details from the GenXDM WSDL TIBCO Support.
CORE- Interface for the WSDL namespace
00023 [{0}] that is associated with the BW
2 Component [{1}] due to exception
[{2}].

TIBCO BusinessWorks™ Container Edition Error Codes

35 | Core

Error Error Message Error Resolution

Codes

TIBC Unable to obtain ModuleCache for This is an internal product error. Contact
O-BW- the BW Component [{0}]. The TIBCO Support.
CORE- operation "{1}" returned "null".
00023
4

TIBC Failed obtain value for the BW framework layer encountered errors when
O-BW- component level property [{0}], BW accessing the component level property.
CORE- Component [{1}], Application [{2}: Contact TIBCO Support.
00023 {3}]. Encountered exception [{4}]
5

TIBC Invalid 'BWApplicationHandle'. The This is an internal product error. Contact

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

TIBC Unable to create This is an internal product error. Contact

O-BW- 'BWApplicationHandle' due to TIBCO Support.
CORE- invalid BWComponentHandle list.
00030 The argument of type
4 'List<BWComponentHandle>;' must
contain at least one
BWComponentHandle.

TIBC Unable to create This is an internal product error. Contact

O-BW- 'BWApplicationHandle' due to TIBCO Support.
CORE- inconsistent application names in
00030 the BWComponentHandle(s)
6 contained in the argument of type
'List<BWComponentHandle>;'. 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}].

TIBCO BusinessWorks™ Container Edition Error Codes

36 | Core

Error Error Message Error Resolution

Codes

TIBC Unable to create This is an internal product error. Contact

O-BW- 'BWApplicationHandle' for the BW TIBCO Support.
CORE- Application [{0}].
00030
8

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

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

TIBC Unable to configure ProcessStarter This is an internal product error. Contact

O-BW- activity [{0}] in process [{1}], TIBCO Support.
CORE- module [{2}] due to crypto service
00040 access error.
6

TIBC HotUpdate operation not This error can occur if the BW process file has
O-BW- supported for ProcessStarter been corrupted.
CORE- activity [{0}] in process [{1}],
00040 module [{2}]. The ProcessStarter
8 already exists for activitId [{3}].

TIBC Failed to obtain activity [{0}] in This is an internal product error. Contact
O-BW- process [{1}], module [{2}] from the TIBCO Support.
CORE- BWActivityManager due to
00060 exception [{3}]. ActivityId [{4}].
2

TIBCO BusinessWorks™ Container Edition Error Codes

37 | Core

Error Error Message Error Resolution

Codes

TIBC Error occurred when configuring This is an internal product error. Contact
O-BW- the activity [{0}] in process [{1}], TIBCO Support.
CORE- module [{2}]
00060
4

TIBC Unable to configure activity [{0}] in This is an internal product error. Contact
O-BW- process [{1}], module [{2}] due to TIBCO Support.
CORE- crypto service access error.
00060
6

TIBC Unable to execute [{0}] operation This is an internal product error. Contact
O-BW- for an activity. Failed to lookup TIBCO Support.
CORE- activity [{1}] in process [{2}],
00060 module [{3}] from the
8 BWActivityManager. ActivityId [{4}].

TIBC HotUpdate operation not This is an internal product error. Contact

O-BW- supported for activity [{0}] in TIBCO Support.
CORE- process [{1}], module [{2}]. The
00061 activity already exists for activitId
0 [{3}].

TIBC {0} This is a trace message and resolution is not

O-BW- applicable.
CORE-
10000
1

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

O-BW- Component[{1}] in AppNode[{2}], applicable.
CORE- ActivationAlias[{3}].
10000
2

TIBCO BusinessWorks™ Container Edition Error Codes

38 | Core

Error Error Message Error Resolution

Codes

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

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20000
1

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20200
0

TIBC Initialized BW Engine successfully This is a debug message and it indicates the
O-BW- [{0}, {1}, {2}]. BW Engine was initialized successfully.
CORE- Resolution is not applicable for this message.
20200
2

TIBC Stopped(Graceful) BW Engine This is a debug message and it indicates the

O-BW- successfully. BW Engine was stopped gracefully. Resolution
CORE- is not applicable for this message.
20205
2

TIBC Stopped(Forceful) BW Engine This is a debug message and it indicates the

O-BW- successfully. BW Engine was stopped forcefully before
CORE- completing all application jobs. Resolution is
20205 not applicable for this message.
3

TIBCO BusinessWorks™ Container Edition Error Codes

39 | Core

Error Error Message Error Resolution

Codes

TIBC BW Engine is already in stopped This is a debug message and resolution is not
O-BW- state. applicable.
CORE-
20205
4

TIBC Enabled BW Debugger in the BW This is a debug message and resolution is not
O-BW- Engine. applicable.
CORE-
20205
5

TIBC Disabled BW Debugger in the BW This is a debug message and resolution is not
O-BW- Engine. applicable.
CORE-
20205
6

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20210
0

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

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

TIBCO BusinessWorks™ Container Edition Error Codes

40 | Core

Error Error Message Error Resolution

Codes

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

TIBC Released-resources for BW Module This is a debug message and it indicates the
O-BW- [{0}:{1}], DeploymentUnit [{2}:{3}]. BW Engine has completed releasing the BW
CORE- Module resources. Resolution is not applicable
20210 for this message.
4

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

TIBC Undeployed BW Module [{0}:{1}], This is a debug message and it indicates the
O-BW- DeploymentUnit [{2}:{3}]. BW Engine has completed un-deploying the BW
CORE- Module. Resolution is not applicable for this
20210 message.
6

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20220
0

TIBC INITIATE: install BW Component This is a debug message and it indicates the
O-BW- [{0}], Application[{1}:{2}]. BW Engine is starting to create the BW
CORE- Component. Resolution is not applicable for
20220 this message.
1

TIBCO BusinessWorks™ Container Edition Error Codes

41 | Core

Error Error Message Error Resolution

Codes

TIBC Installed BW Component [{0}], This is a debug message and it indicates the
O-BW- Application[{1}:{2}]. BW Engine has completed creating the BW
CORE- Component. Resolution is not applicable for
20220 this message.
2

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

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

TIBC INITIATE: start BW Component This is a debug message and it indicates the
O-BW- [{0}]. BW Engine is starting the BW Component.
CORE- Resolution is not applicable for this message.
20220
5

TIBC Started BW Component [{0}]. This is a debug message and it indicates the
O-BW- BW Engine has stated the BW Component.
CORE- Resolution is not applicable for this message.
20220
6

TIBC INITIATE: stop(Forceful) BW This is a debug message and resolution is not

O-BW- Component [{0}]. applicable.
CORE-
20220
7

TIBCO BusinessWorks™ Container Edition Error Codes

42 | Core

Error Error Message Error Resolution

Codes

TIBC Stopped(Forceful) BW Component This is a debug message and resolution is not

O-BW- [{0}]. applicable.
CORE-
20220
8

TIBC INITIATE: destroy BW Component This is a debug message and resolution is not
O-BW- [{0}]. applicable.
CORE-
20220
9

TIBC Destroyed BW Component [{0}]. This is a debug message and resolution is not
O-BW- applicable.
CORE-
20221
0

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

TIBC Released-resources for BW This is a debug message and resolution is not

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

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

TIBCO BusinessWorks™ Container Edition Error Codes

43 | Core

Error Error Message Error Resolution

Codes

TIBC Undeployed BW Component [{0}], This is a debug message and resolution is not
O-BW- Application[{1}:{2}]. applicable.
CORE-
20221
4

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

TIBC Started ServiceBinding(s) or This is a debug message and resolution is not

O-BW- ProcessStarter for BW Component applicable.
CORE- [{0}], Application[{1}:{2}].
20221
6

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

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

O-BW- ProcessStarter for BW Component applicable.
CORE- [{0}], Application[{1}:{2}].
20221
8

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

TIBCO BusinessWorks™ Container Edition Error Codes

44 | Core

Error Error Message Error Resolution

Codes

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

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

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

TIBC Ready to uninstall BW Component This is a debug message and resolution is not
O-BW- [{0}], Application [{1}]. applicable.
CORE-
20222
3

TIBC Created This is a debug message and resolution is not

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

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20230
0

TIBCO BusinessWorks™ Container Edition Error Codes

45 | Core

Error Error Message Error Resolution

Codes

TIBC INITIATE: create BW Application This is a debug message and resolution is not
O-BW- [{0}] handle. applicable.
CORE-
20230
1

TIBC Created BW Application [{0}] This is a debug message and resolution is not
O-BW- handle. applicable.
CORE-
20230
2

TIBC INITIATE: start BW Application [{0}]. This is a debug message and resolution is not
O-BW- applicable.
CORE-
20230
3

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

TIBC INITIATE: stop(Graceful) for BW This is a debug message and resolution is not
O-BW- Application [{0}]. applicable.
CORE-
20230
9

TIBC Stopped(Graceful) BW Application This is a debug message and resolution is not

O-BW- [{0}]. applicable.
CORE-
20231
0

TIBCO BusinessWorks™ Container Edition Error Codes

46 | Core

Error Error Message Error Resolution

Codes

TIBC INITIATE: stop(Forceful) BW This is a debug message and resolution is not

O-BW- Application [{0}]. applicable.
CORE-
20231
1

TIBC Stopped(Forceful) BW Application This is a debug message and resolution is not

O-BW- [{0}]. applicable.
CORE-
20231
2

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

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

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

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

TIBCO BusinessWorks™ Container Edition Error Codes

47 | Core

Error Error Message Error Resolution

Codes

TIBC INITIATE: pause BW Application This is a debug message and resolution is not
O-BW- [{0}]. applicable.
CORE-
20231
7

TIBC Paused BW Application [{0}]. This is a debug message and resolution is not
O-BW- applicable.
CORE-
20231
8

TIBC INITIATE: resume BW Application This is a debug message and resolution is not
O-BW- [{0}]. applicable.
CORE-
20231
9

TIBC Resumed BW Application [{0}]. This is a debug message and resolution is not
O-BW- applicable.
CORE-
20232
0

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

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

TIBCO BusinessWorks™ Container Edition Error Codes

48 | Core

Error Error Message Error Resolution

Codes

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

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

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

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

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

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

TIBCO BusinessWorks™ Container Edition Error Codes

49 | Core

Error Error Message Error Resolution

Codes

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

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

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20241
1

TIBC INITIATE: release ProcessStarter This is a debug message and resolution is not
O-BW- activity [{0}] in Process[{1}], Module applicable.
CORE- [{2}], DeploymentUnit [{3}:{4}].
20250
9

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

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20251
1

TIBCO BusinessWorks™ Container Edition Error Codes

50 | Core

Error Error Message Error Resolution

Codes

TIBC INITIATE: initialize Activity [{0}] in This is a debug message and resolution is not
O-BW- Process[{1}], Module [{2}], applicable.
CORE- DeploymentUnit [{3}:{4}].
20260
1

TIBC Initialized Activity [{0}] in Process This is a debug message and resolution is not
O-BW- [{1}], Module [{2}], DeploymentUnit applicable.
CORE- [{3}:{4}].
20260
2

TIBC INITIATE: destroy Activity [{0}] in This is a debug message and resolution is not
O-BW- Process[{1}], Module [{2}], applicable.
CORE- DeploymentUnit [{3}:{4}].
20260
3

TIBC Destroyed Activity [{0}] in Process This is a debug message and resolution is not
O-BW- [{1}], Module [{2}], DeploymentUnit applicable.
CORE- [{3}:{4}].
20260
4

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20260
5

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20611
0

TIBCO BusinessWorks™ Container Edition Error Codes

51 | Core

Error Error Message Error Resolution

Codes

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20611
1

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20612
0

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20612
1

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20620
0

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20621
0

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20631
0

TIBCO BusinessWorks™ Container Edition Error Codes

52 | Core

Error Error Message Error Resolution

Codes

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20631
1

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20640
0

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20641
0

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20652
0

TIBC {0} This is a debug message and resolution is not

O-BW- applicable.
CORE-
20652
1

TIBC Activity input data validation This is a debug message and resolution is not
O-BW- details. ActivityName={0}, applicable.
CORE- ProcessName={1}, Module={2}:{3},
20661 Schema={4}, Data={5}
1

TIBCO BusinessWorks™ Container Edition Error Codes

53 | Core

Error Error Message Error Resolution

Codes

TIBC Activity output data validation This is a debug message and resolution is not
O-BW- details. ActivityName={0}, applicable.
CORE- ProcessName={1}, Module={2}:{3},
20661 Schema={4}, Data={5}
2

TIBC The BusinessWorks Event Publisher This message indicates the BW Engine is
O-BW- is disabled. configured to disable the event publisher;
CORE- therefore there will be no event published by
30000 the BW Engine.
2

TIBC {0} This is a warning message and it highlights

O-BW- situations that may affect the application
CORE- execution.
40000
1

TIBC Activity resource release operation The activity resource release operation must
O-BW- [com.tibco.bw.runtime.ActivityReso not raise an exception. This is considered to be
CORE- urce.release()] called at the end of an activity resource implementation error.
40000 the execution of the BW group or
4 BW Process instance encountered
error. The Activity resource release
operation [{0}.release(boolean)]
raised exception: {1}

TIBC CatchAll fault details formating Received unexpected data when formating the
O-BW- issue. Expected [{0}], but received CatchAll fault details.
CORE- [{1}]
40000
6

TIBC The BW process [{0}] instance This message is generated when the
O-BW- cancelled, JobId [{1}], BusinessWorks Engine cancels a process
CORE- ProcessInstanceId [{2}], instance execution. A process instance can be

TIBCO BusinessWorks™ Container Edition Error Codes

54 | Core

Error Error Message Error Resolution

Codes

40001 ParentProcessInstanceId [{3}], canceled when one of the following occurs: the
0 Module [{4}:{5}], Application [{6}: invoke activity (in the parent process) that
{7}]. called this process instance 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-BW- configured for the initial value of that contains initial values for the Module or
CORE- the {1} [{2}] in the BW Module [{3}: Job Shared variables. This error occurred when
40010 {4}], DeploymentUnit [{5}:{6}]; attempting to close the file, but after reading
2 encountered exception [{7}]. the file contents.

TIBC The BW Component [{0}:{1}] is The BW framework is attempting to destroy

O-BW- already in destroyed state. the BW Component that is already in destroyed
CORE- state. Resolution is not applicable.
40020
2

TIBC {0} This error code is used to log BW Engine

O-BW- errors. For more details, refer to the additional
CORE- exception message or the "CausedBy"
50000 statements reported as part of this error
1 message.

TIBC Failed to initialize BW Engine due The BW Engine did not successfully initialize,
O-BW- to exception [{0}] and this could be due to many reasons. For
CORE- more details, refer to the additional exception
50001 message or the "CausedBy" statements
0 reported as part of this error message.

TIBC Failed to initialize BW Engine due The BW Engine was not able to establish
O-BW- to database access error connection or access the engine database
CORE- instance. Ensure the database driver,
50001 connection, user name and password details
1 are correctly specified. Also ensure database

TIBCO BusinessWorks™ Container Edition Error Codes

55 | Core

Error Error Message Error Resolution

Codes

instance has been started.

TIBC Failed to initialize BW Engine due The BW Engine failed to establish connection
O-BW- to engine group connection with the engine group connection provider.
CORE- provider error Ensure the group connection provider entity
50001 (bw.engine.groupProvider.technology)
2 specified in the BW AppNode or BW AppSpace
configuration file has been started and
accessible to the BW Engine.

TIBC Failed to initialize BW Engine due The BW Engine was not able to initialize due to
O-BW- to database schema configuration the engine database schema configuration
CORE- error. The BW Engine database error. Create a new engine database using the
50001 does not contain the required database scripts provided in the TIBCO
3 tables. Ensure the BW Engine BusinessWorks product and this will configure
database has been created with the database with the appropriate schemas
the table schemas required by the required by the engine.
engine

TIBC Failed to initialize BW Engine due The BW Engine is configured to execute in

O-BW- to missing or incorrect engine persistence mode "datastore"; however the
CORE- database configuration data. The required database configuration data was not
50001 BW Engine persistence mode specified. Ensure the BW Engine is configured
4 property [{0}] is set to [datastore] with the required database connection details.
and this option requires valid
engine database configuration data

TIBC Failed to initialize BW Engine due The BW Engine is configured to execute in

O-BW- to missing or incorrect engine persistence mode "group"; however the
CORE- database configuration data. The required database configuration data was not
50001 BW Engine persistence mode specified. Ensure the BW Engine is configured
5 property [{0}] is set to [group] and with the required database connection details.
this option requires valid engine
database configuration data

TIBCO BusinessWorks™ Container Edition Error Codes

56 | Core

Error Error Message Error Resolution

Codes

TIBC Failed to initialize BW Engine due This error can occur when the BW Engine is
O-BW- to incompatible engine group configured to use a group name that does not
CORE- name. The group name [{0}] match the group name in the engine database.
50001 configured for the BW Engine does To resolve these issues change the engine
6 not match the group name value in group name to match the group name in the
the BW Engine database. Try using engine database, use a different engine
a different engine database or database that contains the matching engine
change the engine group name to group name or create a new engine database.
match the value in the database Furthermore if the group name is 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 was
O-BW- to incompatible persistence mode previously used by a BW Engine configured to
CORE- between the engine and the engine execute in persistence mode 'datastore'
50001 database. This error can occur if (bw.engine.persistenceMode=datastore). When
7 the BW Engine is configured to a BW Engine uses the database for the first
execute in persistence mode time, the database is updated with the engine
[group]; however the BW Engine execution persistence mode. Subsequently the
database is configured for the persistence mode value stored in the database
persistence mode [datastore]. Try cannot be altered and the same database
using a different database or use a cannot be used for different engine persistence
database that is configured for the mode. To resolve this issue ensure the engine
persistence mode [group] 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 was
O-BW- to incompatible persistence mode previously used by a BW Engine configured to
CORE- between engine and the engine execute in persistence mode 'group'
50001 database. This error can occur if (bw.engine.persistenceMode=group). When a
8 the BW Engine is configured to BW Engine uses the database for the first time,
execute in persistence mode the database is updated with the engine

TIBCO BusinessWorks™ Container Edition Error Codes

57 | Core

Error Error Message Error Resolution

Codes

[datastore]; however the engine execution persistence mode. Subsequently the

database is configured for the persistence mode value stored in the database
persistence mode [group]. Try cannot be altered and the same database
using a database that is configured cannot be used for different engine persistence
for the persistence mode mode. To resolve this issue ensure the engine
[datastore] or create a new engine and the database persistence mode match or
database 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-BW- to missing or incorrect group configured to execute in persistence mode
CORE- connection provider configuration [group] and the engine is not correctly
50001 data. The BW Engine persistence configured with the group connection provider
9 mode property [{0}] is set to data. Ensure the BW Engine is configured with
[group] and this option requires the required group connection provider details.
valid engine group connection
provider configuration data.

TIBC Failed to initialize BW Engine due This error can occur if the BW Engine is
O-BW- to incorrect engine group name. configured to execute in persistence mode
CORE- The BW Engine persistence mode [group] and an empty or invalid engine group
50002 property [{0}] is set to [group] and name is specified. Ensure the engine group
0 this option requires a valid engine name is not empty or contains a valid name.
group name specified via property
[{1}].

TIBC Failed to initialize BW Engine. The Ensure the BW Engine thread count is not
O-BW- BW Engine thread count value is configured to be empty or null. Furthermore
CORE- configured incorrectly. Ensure the the thread count value must be an integer that
50002 thread count value is set to an is greater than zero.
1 integer that is greater than zero

TIBC Failed to initialize BW Engine. The Ensure the BW Engine step count is not
O-BW- BW Engine step count value is configured to be empty or null. Furthermore
CORE- configured incorrectly. Ensure the the step count value must be "-1" or an integer

TIBCO BusinessWorks™ Container Edition Error Codes

58 | Core

Error Error Message Error Resolution

Codes

50002 step count value is set to "-1" or an that is greater than zero.
2 integer that is greater than zero

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

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

TIBC Failed to initialize BW Engine. This is an internal product error. Contact

O-BW- While creating TIBCO Support.
CORE- SpringApplicationContext the BW
50002 Engine encountered exception: {0}.
5

TIBC The ProcessStarter has not been A ProcessStarter is attempting to perform an

O-BW- initialized or it is in the destroyed operation when it has not been initialized or it
CORE- state. The EventSourceContext is in the destroyed state. This is considered to
50002 associated with the ProcessStarter be a ProcessStarter implementation error.
6 is invalid.

TIBC Failed to initialize BW Engine due This error can be reported when multiple BW
O-BW- to exception [{0}]. This error can Engines configured for 'datastore' persistence
CORE- occur if the BW Engine persistence mode is attempting to use the same database
50002 mode is set to [{1}] and the same configuration. Ensure different database
7 database configuration is used by configuration specified for each BW Engine
multiple BW Engines. When a BW when the persistence option is 'datastore'. This
Engine is configured for the is also applicable when multiple BW Engines
persistence mode [{2}], then each (BW AppNodes) are part of the same BW
BW Engine must have a unique AppSpace.

TIBCO BusinessWorks™ Container Edition Error Codes

59 | Core

Error Error Message Error Resolution

Codes

database configuration. This is

applicable even if the BW Engines
(BW AppNodes) are part of the
same BW AppSpace

TIBC BW Engine stop operation An error was encountered when stopping the
O-BW- encountered exception [{0}] BW Engine. For more details, refer to the
CORE- additional exception message or the
50003 "CausedBy" statements reported as part of this
0 error message.

TIBC BW Engine graceful stop operation An error was encountered when attempting to
O-BW- encountered exception [{0}] gracefully stop the BW Engine. For more
CORE- details, refer to the additional exception
50003 message or the "CausedBy" statements
1 reported as part of this error message.

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

TIBC Failed to enable the BW Debugger Error was encountered when attempting to
O-BW- entity in the BW Engine due to enable the BW Debugger entity in the BW
CORE- exception [{0}] Engine. Contact TIBCO Support.
50003
3

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

O-BW- encountered exception [{0}] provided when enabling the BW Debugger
CORE- entity in the BW Engine.
50003
4

TIBC Unable to enable Event Publisher Error was encountered when attempting to

TIBCO BusinessWorks™ Container Edition Error Codes

60 | Core

Error Error Message Error Resolution

Codes

O-BW- in the BW Engine, encountered enable the Event Publisher in the BW Engine.
CORE- exception [{0}] Contact TIBCO Support.
50003
5

TIBC Attempt to disable the Event Error was encountered when attempting to
O-BW- Publisher in the BW Engine, disable the Event Publisher in the BW Engine.
CORE- encountered exception [{0}] Contact TIBCO Support.
50003
6

TIBC Unable to associate an activity An activity that is not inside a group is

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

TIBC Unable to associate an activity An activity that is not inside a loop is

O-BW- resource with a BW loop. The attempting to associate a resource with a loop.
CORE- activity [{0}] in process [{1}] is not This error can occur due to an activity
50003 contained within a loop; however implementation error.
8 the activity is attempting to
associate a resource with a loop.
{2}

TIBC Reference Binding configured for The Reference Binding configured for the
O-BW- the process reference [{0}], in process provided an invalid message data
CORE- process [{1}], module [{2}] provided model. This error can occur due to the
50003 unsupported message data model Reference Binding implementation error.
9 [{3}].

TIBC Invocation of the Process This error indicates the Reference Binding
O-BW- Reference's operation [{0}] failed. configured for the process reference failed and
CORE- The BW Reference Binding [{1}] returned a fault.

TIBCO BusinessWorks™ Container Edition Error Codes

61 | Core

Error Error Message Error Resolution

Codes

50004 configured for the process

0 reference [{2}] in process [{3}],
module [{4}] returned fault [{5}].

TIBC Invalid activity name. The activity The error indicates the specified activity name
O-BW- name [{0}] is not found in process is not contained within the BW process. Ensure
CORE- [{1}], module [{2}:{3}], a valid activity name is specified for this
50004 DeploymentUnit [{4}:{5}]. operation.
1

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

TIBC The BW process [{0}] instance This error message indicates the process
O-BW- faulted, JobId [{1}], instance did not complete successfully; instead
CORE- ProcessInstanceId [{2}], it terminated due to an error that occurred
50005 ParentProcessInstanceId [{3}], during the execution of the process instance.
0 Module [{4}:{5}], Application [{6}: For more details on the process instance
{7}]. {8} failure, refer to the additional 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-BW- that raised the fault and caused the process
CORE- instance to fail.
50005
1

TIBC Invoke activity [{0}] fault. {1} This message indicates the potential invoke
O-BW- activity that raised the fault and caused the
CORE- process instance to fail.
50005
2

TIBCO BusinessWorks™ Container Edition Error Codes

62 | Core

Error Error Message Error Resolution

Codes

TIBC XSLT transformation error. {0} This message indicates the cause of the failure
O-BW- could be due to a XSLT transformation error.
CORE-
50005
3

TIBC Activity [{0}] XSLT transformation This message indicates the cause of the failure
O-BW- error. {1} could be due to an Activity XSLT
CORE- transformation error.
50005
4

TIBC XPATH error. {0} This message indicates the cause of the failure
O-BW- could be due to a XPATH error.
CORE-
50005
5

TIBC Activity [{0}] XPATH error. {1} This message indicates the cause of the failure
O-BW- could be due to an Activity XPATH error.
CORE-
50005
6

TIBC XML related error. {0} This message indicates the cause of the failure
O-BW- could be due to a XML error.
CORE-
50005
7

TIBC Activity [{0}] XML related error. {1} This message indicates the cause of the failure
O-BW- could be due to an Activity XML error.
CORE-
50005
8

TIBCO BusinessWorks™ Container Edition Error Codes

63 | Core

Error Error Message Error Resolution

Codes

TIBC Reply activity [{0}] error. The reply This error message is reported when a process
O-BW- activity cannot be associated with is implemented to execute more than one
CORE- the ProcessService request Reply activity for the same operation, the caller
50005 message. This error can occur if of this process (Service Binding, Parent
9 the process is implemented to Process) has terminated before Reply activity
send reply multiple times for the can be executed or on recovery from a check-
same request, the caller of this point the Reply activity is executed but the
process is no longer available or on caller of this process did not recover because it
recovery from a check-point the was not part of the check-pointed job. Ensure
caller did not recover because it the process is not implemented to reply to
was not part of the check-pointed same request multiple times.
job. {1}

TIBC The process instance terminated This message is reported when a process
O-BW- without replying to the caller of instance terminates without replying to the
CORE- this process. {0} request of a ProcessService operation. This can
50006 occur if the process is implemented incorrectly
0 to end the process execution without
performing a reply operation or when 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-BW- activity [{1}] encountered error on following reasons: the caller of this process
CORE- sending the response to the caller (Service Binding, Parent Process) raised a fault
50006 of this process. This error can when processing the reply message, the caller
1 occur if the caller of this process of this process is no longer available.
raised a fault when processing the
reply message, the caller of this
process is no longer available. {2}

TIBC {0} This message provides information for the

O-BW- process instance failure.
CORE-
50006

TIBCO BusinessWorks™ Container Edition Error Codes

64 | Core

Error Error Message Error Resolution

Codes

TIBC Activity [{0}] error. {1} This message indicates the potential activity
O-BW- that raised the fault and caused the process
CORE- instance to fail.
50006
4

TIBC Throw activity [{0}] fault. Fault: {1} This message indicates the name of the Throw
O-BW- activity that raised the fault and caused the
CORE- process instance to fail.
50006
5

TIBC Invoke activity faulted due an error This message indicates the Invoke activity
O-BW- from the invoked subprocess. {0} failed due to an unexpected error received for
CORE- the invoked subprocess. This error can occur if
50006 the subprocess terminated without replying,
6 the subprocess faulted, the invoked
subprocess does not exist, etc. Ensure the
invoked subprocess is implemented correctly
and confirms to the invoked operation
contract.

TIBC Activity [{0}] faulted due to an This error can occur when the BW Engine is
O-BW- object serialization error. This error attempting to serialize a Java object to
CORE- can occur if an object that must be support the persistence feature and the object
50006 serialized as part of the cannot be serialized. Ensure the Java object is
7 BusinessWorks process execution is Serializable and the Java package that
not Serializable or the Java contains the class is exported.
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-BW- serialization error. This error can attempting to serialize a Java object to
CORE- occur if the Java class that must be support the persistence feature; however the

TIBCO BusinessWorks™ Container Edition Error Codes

65 | Core

Error Error Message Error Resolution

Codes

50006 serialized as part of the Java object cannot be serialized. Ensure the
8 BusinessWorks process execution is Java object is Serializable and the Java
not Serializable or the Java package that contains the class is exported.
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-BW- message from the receive activity following reasons: the process is implemented
CORE- [{0}], in process [{1}], module [{2}: to execute more than one confirm activity for
50008 {3}], application [{4}:{5}]. This error the same request, the caller of this process
9 can occur if the process is instance (Service Binding, Parent process) has
implemented to confirm multiple terminated before the confirm activity can be
times for the same request executed or on recovery from a check-point
message, the caller of this process the confirm activity is executed; however the
is no longer available, on recovery caller of this process did not recover because it
from a check-point the caller did was not part of the check-pointed job. Ensure
not recover because it was not part the process is not implemented to confirm to
of the check-pointed job or the same request for multiple times or the activity
specified receive activity name is name configured in the confirm activity is
incorrect. correct.

TIBC The reply operation The operation

O-BW- [com.tibco.bw.runtime.EventConte [com.tibco.bw.runtime.EventContext.reply(..)]
CORE- xt.reply(..)] is not supported for the is not allowed for the specified activity and this
50009 activity [{0}], in process [{1}], is an implementation error.
0 module [{2}:{3}], application [{4}:
{5}].

TIBC Invalid argument value. The BW The BusinessWorks Application specified for
O-BW- Application name cannot be null. this operation can not be null or empty. Ensure
CORE- valid application name is specified for this
50009 operation.
1

TIBC Unable to get BW Process Error occurred when obtaining the process
O-BW- instances information for the BW instance details for the specified

TIBCO BusinessWorks™ Container Edition Error Codes

66 | Core

Error Error Message Error Resolution

Codes

CORE- Application [{0}] due to exception BusinessWorks application.

50009 [{1}].
2

TIBC Unable to get BW Process instance Error occurred when obtaining the process
O-BW- information for the BW instance details for the specified
CORE- ProcessIntanceId [{0}] due to BusinessWorks ProcessIntanceId.
50009 exception [{1}].
3

TIBC Unable to get BW Process instance Error occurred when obtaining the process
O-BW- summary information for the BW instance details for the specified
CORE- ProcessIntanceId [{0}] due to BusinessWorks ProcessIntanceId.
50009 exception [{1}].
4

TIBC Failed to suspend the BW Process Error occurred when attempting to suspend
O-BW- instance for the BW the process instance for the specified
CORE- ProcessIntanceId [{0}] due to BusinessWorks ProcessIntanceId.
50009 exception [{1}].
5

TIBC Failed to resume the BW Process Error occurred when attempting to resume the
O-BW- instance for the BW process instance for the specified
CORE- ProcessIntanceId [{0}] due to BusinessWorks ProcessIntanceId.
50009 exception [{1}].
6

TIBC Failed to cancel the BW Process Error occurred when attempting to cancel the
O-BW- instance for the BW process instance for the specified
CORE- ProcessIntanceId [{0}] due to BusinessWorks ProcessIntanceId.
50009 exception [{1}].
7

TIBC BW AppNode name [{0}] exceeds BW AppNode name exceeds 250 characters this
O-BW- 250 characters and it is possible to is not possible create unique engine name.

TIBCO BusinessWorks™ Container Edition Error Codes

67 | Core

Error Error Message Error Resolution

Codes

CORE- create the internal engine alias Ensure AppNode name is less than 250
50009 name. characters.
8

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

TIBC Encountered error(s) on release- The BW Engine encountered error(s) when

O-BW- resource operation for the BW releasing resources associated with the BW
CORE- Module [{0}:{1}], DeploymentUnit Module and this could be due to many
50010 [{2}:{3}] reasons. For more details, refer to the
4 additional exception message or the
"CausedBy" statements reported as part of this
error message.

TIBC Encountered error(s) when un- The BW Engine encountered error(s) when un-
O-BW- deploying the BW Module [{0}:{1}], deploying the BW Module and this could be
CORE- DeploymentUnit [{2}:{3}] due to many reasons. For more details, refer to
50010 the additional exception message or the
6 "CausedBy" statements reported as part of this
error message.

TIBC Failed to install BW Module [{0}: The BW Module or the process is using a
O-BW- {1}], DeploymentUnit [{2}:{3}]. The persistence feature, module shared variable
CORE- module or a process is configured with persistence option, etc..; however the BW
50011 to utilize the BW Engine Engine persistence mode is not set
0 persistence feature; however the appropriately for this feature. Ensure the BW
BW Engine is not configured with a Engine persistence mode
correct engine persistence mode. (bw.engine.persistenceMode) is set to
Ensure the BW Engine is configured "datastore" or "group" and the required engine
for the engine persistence mode database configuration is specified.
[datastore] or [group] before

TIBCO BusinessWorks™ Container Edition Error Codes

68 | Core

Error Error Message Error Resolution

Codes

installing this module.

TIBC Failed to start BW Module due to This error is reported when the BW Activity in
O-BW- an activity start error. CausedBy the process fails to initialize and start. For
CORE- more details, refer to the additional exception
50011 message or the "CausedBy" statements
2 reported as part of this error message.

TIBC Unable to obtain Failed to obtain SchemaComponentCache for

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

TIBC Unable to add schema to Failed to add schema required by the BW

O-BW- SchemaComponentCache Module to SchemaComponentCache and this
CORE- (Namespace={0}, Location={1}) due could be due to many reasons. For more
50011 to exception [{2}] details, refer to the additional exception
8 message or the "CausedBy" statements
reported as part of this error message.

TIBC Unable to obtain WSDL Failed to get the WSDL ModuleCache required
O-BW- ModuleCache (Namespace={0}, by the BW Module.
CORE- Location={1}) for BW Module [{2}:
50011 {3}]. The WSDLCacheService
9 operation [{4}] returned "null".

TIBC Unable to obtain WSDL Failed to get the WSDL ModuleCache for the
O-BW- ModuleCache (Namespace={0}, WSDL required by the BW Module.
CORE- Location={1}) for BW Module [{2}:
50012 {3}]. The WSDLCacheService
1 operation [{4}] returned "null".

TIBC Unable to obtain WSDL Failed to get the WSDL ModuleCache for the
O-BW- ModuleCache (Namespace={0}, WSDL required by the BW Module and this

TIBCO BusinessWorks™ Container Edition Error Codes

69 | Core

Error Error Message Error Resolution

Codes

CORE- Location={1}) for BW Module [{2}: could be due to many reasons. For more
50012 {3}]. The WSDLCacheService details, refer to the additional exception
2 operation [{4}] returned exception message or the "CausedBy" statements
[{5}] reported as part of this error message.

TIBC Unable to resolve Schema Failed to resolve the schema required by the
O-BW- (Namespace={0}, Location={1}, BW Module. Ensure the schema is valid, the
CORE- BaseURI={2}) for BW Module [{3}: schemas imported/referenced by this schema
50012 {4}]. The SchemaCacheService are valid, the schemaLocation of the schemas
3 operation [{5}] returned "null". imported by this schema is valid,..

TIBC Invalid or empty file name is The module shared variable or the job shared
O-BW- specified for the initial value of the variable contains incorrect value or is empty.
CORE- {0} [{1}] in BW Module [{2}:{3}], Ensure the module or the job shared variable
50013 DeploymentUnit [{4}:{5}]. has been initialized or assigned with a correct
1 value.

TIBC The file [{0}] configured for the The module shared variable or the job shared
O-BW- initial value of the {1} [{2}] is not variable has been initialized with a file URL
CORE- found in BW Module [{3}:{4}], that is not found in the BW Module. Ensure the
50013 DeploymentUnit [{5}:{6}]. specified file name is valid or the file is
2 contained within the BW Module.

TIBC Unable to access the file [{0}] Failed to access the file specified in the
O-BW- configured for the initial value of module or job shared variable and this could
CORE- the {1} [{2}] in BW Module [{3}:{4}], be due to many reasons. For more details,
50013 DeploymentUnit [{5}:{6}]; refer to the additional exception message or
3 encountered exception [{7}]. the "CausedBy" statements reported as part of
this error message.

TIBC Unable to open the file [{0}] Failed to open the file specified in the module
O-BW- configured for the initial value of or job shared variable and this could be due to
CORE- the {1} [{2}] in BW Module [{3}:{4}], many reasons. For more details, refer to the
50013 DeploymentUnit [{5}:{6}]; additional exception message or the
4 encountered exception [{7}]. "CausedBy" statements reported as part of this
error message.

TIBCO BusinessWorks™ Container Edition Error Codes

70 | Core

Error Error Message Error Resolution

Codes

TIBC Unable to read the file [{0}] Failed to read the file specified in the module
O-BW- configured for the initial value of or job shared variable and this could be due to
CORE- the {1} [{2}] in BW Module [{3}:{4}], many reasons. For more details, refer to the
50013 DeploymentUnit [{5}:{6}]; additional exception message or the
5 encountered exception [{7}]. "CausedBy" statements reported as part of this
error message.

TIBC The contents of the file [{0}] Ensure the file specified for the module or job
O-BW- configured for the initial value of shared variable is not empty.
CORE- the {1} [{2}] in BW Module [{3}:{4}],
50013 DeploymentUnit [{5}:{6}] is empty.
6

TIBC Invalid BW Module property. The Ensure the module property correctly defined
O-BW- module property [{0}] is not in the BW Module.
CORE- defined in the BW Module [{1}:{2}],
50014 DeploymentUnit [{3}:{4}]. Therefore
1 the XPath function
"getModuleProperty({5})"
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-BW- property [{0}] defined in the BW in the BW Module.
CORE- Module [{1}:{2}], DeploymentUnit
50014 [{3}:{4}] via the XPath function
2 "getModuleProperty({5})"
contained in the XSLT.
Encountered exception [{6}].

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

TIBCO BusinessWorks™ Container Edition Error Codes

71 | Core

Error Error Message Error Resolution

Codes

TIBC Failed to obtain module properties BW framework layer encountered errors when
O-BW- for the module [{0}:{1}], accessing module properties for the specified
CORE- DeploymentUnit [{2}:{3}]; BW Module. Contact TIBCO Support.
50014 encountered exception [{4}]
4

TIBC Unable to obtain WSDL Interface Error occurred when attempting to obtain
O-BW- details for the PortType [{0}], that WSDL details for the specified PortType, and
CORE- is associated with the BW Module this could be due to many reasons. For more
50014 [{1}:{2}]. Encountered exception details, refer to the additional exception
5 [{3}] message or the "CausedBy" statements
reported as part of this error message.

TIBC Failed to install BW Component The BW Component did not get installed in the
O-BW- [{0}], Application [{1}:{2}] BW Engine, and this could be due to many
CORE- reasons. For more details, refer to the
50020 additional exception message or the
2 "CausedBy" statements reported as part of this
error message.

TIBC Failed to install BW Component The BusinessWorks application or the

O-BW- [{0}], Application [{1}:{2}]. The component in the application is configured to
CORE- application is configured with Job use the Job PageThreshold property
50020 PageThreshold property [bw.application.job.pageThreshold.*] and this
3 [bw.application.job.pageThreshol requires the BW Engine to be configured for
d.*]; however the BW Engine is not the "datastore" or "group" persistence mode.
configured with a correct engine Stop the BusinessWorks AppSpace, configure
persistence mode. Ensure the BW the BW Engine for the engine persistence mode
Engine is configured for the engine [datastore] or [group] and restart the
persistence mode [datastore] or AppSpace before installing the application.
[group] before installing this
application.

TIBC Encountered error(s) on release- Error occurred when releasing the resources
O-BW- resource operation for the BW associated with the BW Component, and this
CORE- Component [{0}], Application [{1}: could be due to many reasons. For more

TIBCO BusinessWorks™ Container Edition Error Codes

72 | Core

Error Error Message Error Resolution

Codes

50021 {2}] details, refer to the additional exception

0 message or the "CausedBy" statements
reported as part of this error message.

TIBC Encountered error(s) when un- Error occurred when un-deploying the BW
O-BW- deploying the BW Component [{0}], Component and this could be due to many
CORE- Application [{1}:{2}] reasons. For more details, refer to the
50021 additional exception message or the
1 "CausedBy" statements reported as part of this
error message.

TIBC Failed to initialize BW Component Error occurred when initializing the BW

O-BW- [{0}], Application [{1}:{2}] Component and this could be due to many
CORE- reasons. For more details, refer to the
50021 additional exception message or the
2 "CausedBy" statements reported as part of this
error message.

TIBC Failed to initialize BW Component Error occurred when creating an instance of an

O-BW- [{0}], Application [{1}:{2}] due to activity that is associated with the BW
CORE- activity creation error Component; therefore the BW Component can
50021 not be initialized. For more details, refer to the
3 additional exception message or the
"CausedBy" statements reported as part of this
error message.

TIBC Failed to initialize BW Component There is a configuration error in the activity or

O-BW- [{0}], Application [{1}:{2}] due to resource that is associated with the BW
CORE- activity or resource configuration Component; therefore the BW Component can
50021 error not be initialized. For more details, refer to the
4 additional exception message or the
"CausedBy" statements reported as part of this
error message.

TIBC Failed to initialize BW Component There are implementation errors in the activity
O-BW- [{0}], Application [{1}:{2}] due to that is associated with the BW Component;

TIBCO BusinessWorks™ Container Edition Error Codes

73 | Core

Error Error Message Error Resolution

Codes

CORE- activity implementation error therefore the BW Component can not be

50023 initialized. For more details, refer to the
0 additional exception message or the
"CausedBy" statements reported as part of this
error message.

TIBC Failed to initialize BW Component Error occurred when initializing an activity that
O-BW- [{0}], Application [{1}:{2}] due to is associated with the BW Component;
CORE- activity initialization error therefore the BW Component can not be
50023 initialized. For more details, refer to the
2 additional exception message or the
"CausedBy" statements reported as part of this
error message.

TIBC Encountered error when destroying Error occurred when destroying or deleting the
O-BW- the BW Component [{0}] BW Component and this could be due to many
CORE- reasons. For more details, refer to the
50023 additional exception message or the
8 "CausedBy" statements reported as part of this
error message.

TIBC Encountered errors when Error occurred when destroying or deleting the
O-BW- destroying the BW Component [{0}] BW Component and this could be due to many
CORE- reasons. For more details, refer to the
50024 additional exception message or the
0 "CausedBy" statements reported as part of this
error message.

TIBC Failed to start BW Component [{0}], Error occurred when starting the BW
O-BW- Application [{1}:{2}] Component and this could be due to many
CORE- reasons. For more details, refer to the
50024 additional exception message or the
2 "CausedBy" statements reported as part of this
error message.

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

TIBCO BusinessWorks™ Container Edition Error Codes

74 | Core

Error Error Message Error Resolution

Codes

O-BW- stopping the BW Component [{0}], Component and this could be due to many
CORE- Application [{1}:{2}] reasons. For more details, refer to the
50024 additional exception message or the
6 "CausedBy" statements reported as part of this
error message.

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

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

O-BW- stopping the ProcessStarter ProcessStarter activity that is associated with
CORE- associated with the BW the BW Component. For more details, refer to
50025 Component [{0}], Application [{1}: the additional exception message or the
0 {2}] "CausedBy" statements reported as part of this
error message.

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

TIBC Unable to stop ServiceBinding [{0}] Error occurred when stopping the
O-BW- for the BW Component [{1}], ServiceBinding that is associated with the BW
CORE- Application [{2}:{3}] due to Component. For more details, refer to the
50025 ServiceBinding lifecycle error additional exception message or the
4 "CausedBy" statements reported as part of this
error message.

TIBC The job flow limit property [{0}] for The BW application or component's job flow
O-BW- the application or the component limit property is configured with an incorrect

TIBCO BusinessWorks™ Container Edition Error Codes

75 | Core

Error Error Message Error Resolution

Codes

CORE- is configured incorrectly. Ensure value. The job flow limit property value must
50025 the job flow limit property value is be an integer that is greater than zero.
6 set to an integer that is greater
than zero.

TIBC The job priority property [{0}] for The BW application or component's job priority
O-BW- the application or the component property is configured with an incorrect value.
CORE- is configured incorrectly. Ensure The job priority property can only be
50025 the job priority property value is configured with the string value "low",
8 set to "low", "normal" or "high". "normal" or "high".

TIBC The property to enable activity The property that is used to determine the
O-BW- input validation for the application enabling of the activity output validation for
CORE- or the component is configured the application or the component is configured
50026 incorrectly. Ensure properties that with an incorrect value. This property can only
2 are prefixed with [{0}] are set with be configured with the string value "true" or
value "true" or "false". "false".

TIBC The property to enable activity

O-BW- output validation for the
CORE- application or the component is
50026 configured incorrectly. Ensure
4 properties that are prefixed with
[{0}] are set with value "true" or
"false".

TIBC The property that specifies the The property that specifies the default wait
O-BW- async activity default wait time is time (timeout) value for an asynchronous
CORE- configured incorrectly. Ensure the activity is configured incorrectly. The value for
50026 property [{0}] or the properties this property must be a zero or positive
5 prefixed with [{1}] are configured number. This property can be configured the
with a zero or positive numeric AppSpace/AppNode configuration file
value 'config.ini'

TIBC Failed to start BW Application [{0}] The BW Application did not start and this could
O-BW- due to exception [{1}] be due to many reasons. For more details,

TIBCO BusinessWorks™ Container Edition Error Codes

76 | Core

Error Error Message Error Resolution

Codes

CORE- refer to the additional exception message or

50030 the "CausedBy" statements reported as part of
2 this error message.

TIBC Failed to start BW Application [{0}: Error occurred in an activity that is associated
O-BW- {1}] due to an activity error with the BW Application; therefore the BW
CORE- Application did not start. For more details,
50030 refer to the additional exception message or
4 the "CausedBy" statements reported as part of
this error message.

TIBC Encountered error when Error occurred when attempting to gracefully

O-BW- attempting to gracefully stop BW stop the BW Application and this could be due
CORE- Application [{0}:{1}] to many reasons. For more details, refer to the
50030 additional exception message or the
6 "CausedBy" statements reported as part of this
error message.

TIBC The BW Application [{0}:{1}] is The BW Application is already in stopped state;

O-BW- already in stopping state. Unable therefore it can not be stopped again.
CORE- to perform operation
50030 "stopApplicationGraceful"
7

TIBC Encountered error when Error occurred when attempting to stop the
O-BW- attempting to stop BW Application BW Application and this could be due to many
CORE- [{0}:{1}] reasons. For more details, refer to the
50030 additional exception message or the
8 "CausedBy" statements reported as part of this
error message.

TIBC Encountered errors when

O-BW- attempting to stop BW Application
CORE- [{0}:{1}]
50031
0

TIBCO BusinessWorks™ Container Edition Error Codes

77 | Core

Error Error Message Error Resolution

Codes

TIBC Unable to start ServiceBinding(s) or Error occurred when attempting to start the
O-BW- ProcessStarter(s) associated with ServiceBinding(s) or ProcessStarter(s) activity
CORE- the BW Application [{0}:{1}] that is associated with the BW Application. For
50031 more details, refer to the additional exception
2 message or the "CausedBy" statements
reported as part of this error message.

TIBC Unable to stop ServiceBinding(s) or Error occurred when attempting to stop the
O-BW- ProcessStarter(s) associated with ServiceBinding(s) or ProcessStarter(s) activity
CORE- the BW Application [{0}:{1}] that is associated with the BW Application. For
50031 more details, refer to the additional exception
4 message or the "CausedBy" statements
reported as part of this error message.

TIBC Encountered error when Error occurred when attempting to resume the
O-BW- attempting to pause BW BW Application. For more details, refer to the
CORE- Application [{0}:{1}] job(s) additional exception message or the
50031 "CausedBy" statements reported as part of this
6 error message.

TIBC Encountered error when

O-BW- attempting to resume BW
CORE- Application [{0}:{1}] job(s)
50031
8

TIBC Failed to create the ProcessStarter Error occurred when attempting to create an
O-BW- activity [{0}] in process [{1}], instance of the ProcessStarter activity in a
CORE- module [{2}] due to exception [{3}] process. For more details, refer to the
50040 additional exception message or the
2 "CausedBy" statements reported as part of this
error message.

TIBC Failed to create the ProcessStarter Unexpected error occurred when attempting to
O-BW- activity [{0}] in process [{1}], create an instance of the ProcessStarter
CORE- module [{2}] due to unexpected activity in a process. For more details, refer to

TIBCO BusinessWorks™ Container Edition Error Codes

78 | Core

Error Error Message Error Resolution

Codes

50040 exception [{3}] the additional exception message or the

4 "CausedBy" statements reported as part of this
error message.

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

O-BW- ProcessStarter activity [{0}] in instance of the ProcessStarter activity in a
CORE- process [{1}], module [{2}] due to process. For more details, refer to the
50040 activity lifecycle error additional exception message or the
6 "CausedBy" statements reported as part of this
error message.

TIBC Failed to initialize the Unexpected error occurred when attempting to

O-BW- ProcessStarter activity [{0}] in initialize an instance of the ProcessStarter
CORE- process [{1}], module [{2}] due to activity in a process. For more details, refer to
50040 unexpected activity lifecycle error the additional exception message or the
8 "CausedBy" statements reported as part of this
error message.

TIBC Failed to start the ProcessStarter Error occurred when attempting to start the
O-BW- activity [{0}] in process [{1}], ProcessStarter activity in a process. For more
CORE- module [{2}] due to activity details, refer to the additional exception
50041 lifecycle error message or the "CausedBy" statements
0 reported as part of this error message.

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

TIBC The stop operation for the Unexpected error occurred when attempting to
O-BW- ProcessStarter activity [{0}] in stop the ProcessStarter activity in a process.
CORE- process [{1}], module [{2}] failed The ProcessStarter activity stop operation
50041 with unexpected exception [{3}] "com.tibco.bw.runtime.EventSource.stop()"
4 failed and returned unexpected exception. The

TIBCO BusinessWorks™ Container Edition Error Codes

79 | Core

Error Error Message Error Resolution

Codes

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 to
O-BW- ProcessStarter activity [{0}] in destroy the ProcessStarter activity in a process.
CORE- process [{1}], module [{2}] failed For more details, refer to the additional
50041 with unexpected exception [{3}] exception message or the "CausedBy"
6 statements reported as part of this error
message.

TIBC The release operation for the Unexpected error occurred when attempting to
O-BW- ProcessStarter activity [{0}] in release resources for the ProcessStarter
CORE- process [{1}], module [{2}] failed activity in a process. For more details, refer to
50041 with unexpected exception [{3}] the additional exception message or the
8 "CausedBy" statements reported as part of this
error message.

TIBC Failed to process the event from BWEngine failed to process the new events
O-BW- the ProcessStarter activity [{0}] from the ProcessStarter activity. For more
CORE- details, refer to the additional exception
50042 message or the "CausedBy" statements
0 reported as part of this error message.

TIBC Failed to execute event from the This error message is reported when the
O-BW- ProcessStarter activity due to output data generated by the ProcessStarter
CORE- activity output data validation activity does not comply with the output
50042 error. The output data from schema of the ProcessStarter activity. This
2 ProcessStarter activity [{0}] does error can occur if ProcessStarter activity is not
not conform to the ProcessStarter implemented correctly to generate the valid
activity output schema. Validation output data.
error details: {1}.

TIBC The BWEngine is unable accept The ProcessStarter generated new events when
O-BW- new events from the it is in the stopped state. A ProcessStarter
CORE- ProcessStarter activity [{0}], in must not generate new events during the

TIBCO BusinessWorks™ Container Edition Error Codes

80 | Core

Error Error Message Error Resolution

Codes

50042 process [{1}], module [{2}] since the stopped state and it will be considered as
4 ProcessStarter is in the stopped ProcessStarter activity implementation error.
sate. When the ProcessStarter is in The ProcessStarter is in the stopped state once
the stopped state, the BWEngine the BWEngine invokes the ProcessStarter
will not accept new events. operation
"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-BW- the activity [{0}] in process [{1}], activity is not implemented correctly. Ensure
CORE- module [{2}] is implemented the BW activity model class contains the
50060 incorrectly. The activity model required attribute or property.
2 class [{3}] does not contain the
configuration property [{4}] as
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-BW- the activity [{0}] in process [{1}],
CORE- module [{2}] is implemented
50060 incorrectly. The activity model [{3}]
3 does not contain the attribute [{4}]
as defined in the annotation 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-BW- activity [{0}] in process [{1}], activity is not implemented correctly. Ensure
CORE- module [{2}] is implemented the BW activity model class contains the
50060 incorrectly. The activity model property of a supported data type.

TIBCO BusinessWorks™ Container Edition Error Codes

81 | Core

Error Error Message Error Resolution

Codes

4 class [{3}] associated with the

activity runtime class [{4}] has a
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-BW- activity [{0}] in process [{1}], activity is not implemented correctly. Ensure
CORE- module [{2}] is implemented the BW activity runtime class member variable
50060 incorrectly. Unable to set member is defined correctly.
5 variable [{3}] declared in the
activity runtime class [{4}].
Encountered exception [{5}].

TIBC The resource specified for the A resource assigned to the process property is
O-BW- process property [{0}] in process not accessible or resolvable at runtime. Ensure
CORE- [{1}], module [{2}] is not available the process property is configured correctly
50060 in the runtime environment. This and the required resource is resolvable at
6 process property is used by the runtime.
activity [{3}] in process [{4}]. Ensure
the resource is configured and
installed correctly.

TIBC The process property [{0}] in The process property is configured with a
O-BW- process [{1}], module [{2}] has an incorrect value. Ensure the process property is
CORE- incorrect value [{3}]. This process configured correctly, specially for a DateTime
50060 property is used by the activity data type.
7 [{4}] in process [{5}]. For DateTime,
ensure the value has the format
[{6}].

TIBC The resource obtained from the The value assigned to the process property did
O-BW- framework for the process property resolve to the data type excepted by the
CORE- [{0}] in process [{1}], module [{2}] is process property . Ensure the process property
50060 not compatible with the data type contains the correct value or the module

TIBCO BusinessWorks™ Container Edition Error Codes

82 | Core

Error Error Message Error Resolution

Codes

8 of the process property. property assigned to the process property is

Encountered exception [{3}]. contains the correct value.

TIBC One or more required fields of the The activity is not configured correctly. Ensure
O-BW- activity [{0}] in process [{1}], the all required fields for the activity at design
CORE- module [{2}] is not configured time are populated correctly.
50061 correctly. Ensure the required
0 fields of the activity contains valid
data.

TIBC Failed to create the activity [{0}] in Unexpected error occurred when attempting to
O-BW- process [{1}], module [{2}] due to create an instance of an activity. For more
CORE- exception [{3}] details, refer to the additional exception
50061 message or the "CausedBy" statements
2 reported as part of this error message.

TIBC Failed to create the activity [{0}] in

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

TIBC Failed to initialize the activity [{0}] Error occurred when attempting to initialize an
O-BW- in process [{1}], module [{2}] due to instance of an activity. For more details, refer
CORE- activity lifecycle error to the additional exception message or the
50061 "CausedBy" statements reported as part of this
6 error message.

TIBC Failed to initialize the activity [{0}] Unexpected error occurred when attempting to
O-BW- in process [{1}], module [{2}] due to initialize an instance of an activity. For more
CORE- unexpected activity lifecycle error details, refer to the additional exception
50061 message or the "CausedBy" statements
8 reported as part of this error message.

TIBC The execute operation for the The activity execution failed and raised an
O-BW- activity [{0}] in process [{1}] failed unexpected exception. For more details, refer

TIBCO BusinessWorks™ Container Edition Error Codes

83 | Core

Error Error Message Error Resolution

Codes

CORE- with unexpected exception [{2}] to the additional exception message or the
50062 "CausedBy" statements reported as part of this
0 error message.

TIBC The post-execute operation for the The post-execute operation for an
O-BW- asynchronous activity [{0}] in asynchronous activity failed and raised an
CORE- process [{1}] failed with unexpected exception. For more details, refer
50062 unexpected exception [{2}] to the additional exception message or the
2 "CausedBy" statements reported as part of this
error message.

TIBC The cancel operation for the The cancel operation for an asynchronous
O-BW- activity [{0}] in process [{1}], activity failed and raised an unexpected
CORE- module [{2}] failed with exception. For more details, refer to the
50062 unexpected exception [{3}] additional exception message or the
4 "CausedBy" statements reported as part of this
error message.

TIBC BWEngine was unable to execute BWEngine encountered error when attempting
O-BW- cancel operation for the activity to execute cancel operation for the activity. For
CORE- [{1}] in process [{2}], module [{3}] more details, refer to the additional exception
50062 due to exception [{4}] message or the "CausedBy" statements
6 reported as part of this error message.

TIBC The destroy operation for the The destroy operation for an activity failed and
O-BW- activity [{0}] in process [{1}], raised an unexpected exception. For more
CORE- module [{2}] failed with details, refer to the additional exception
50062 unexpected exception [{3}] message or the "CausedBy" statements
8 reported as part of this error message.

TIBC The process property [{0}] is not Unable to resolve the specified process
O-BW- defined in the BW Process [{1}] property. Ensure this process property is
CORE- correctly defined in the BW Process.
50063
0

TIBCO BusinessWorks™ Container Edition Error Codes

84 | Core

Error Error Message Error Resolution

Codes

TIBC The process property [{0}] has not The specified process property has not been
O-BW- been registered with the activity correctly registered with the activity context.
CORE- context or the event source This error can occur if the BW activity is not
50063 context. implemented correctly to register the process
1 property via method
[com.tibco.bw.runtime.ActivityContext.register
ProcessProperty].

TIBC Failed to resolve process property Failed to resolve the specified process
O-BW- [{0}] from the BW Process [{1}] property. Ensure the specified process property
CORE- is defined in the process. For more details,
50063 refer to the additional exception message in
2 the cause.

TIBC The module property [{0}] is not Unable to resolve the specified module
O-BW- defined in the BW Module [{1}:{2}] property. Ensure this module property is
CORE- correctly defined in the BW Module.
50063
3

TIBC The module property [{0}] has not The specified module property has not been
O-BW- been registered with the activity correctly registered with the activity context.
CORE- context or the event source This error can occur if the BW activity is not
50063 context. implemented correctly to register the module
4 property via method
[com.tibco.bw.runtime.ActivityContext.register
ModuleProperty].

TIBC Failed to resolve module property Failed to resolve the specified module
O-BW- [{0}] from the BW Module [{1}:{2}] property. Ensure the specified module property
CORE- is defined in the module. For more details,
50063 refer to the additional exception message or
5 the "CausedBy" statements reported as part of
this error message.

TIBC Activity [{0}] timed out. The activity wait or execution time has

TIBCO BusinessWorks™ Container Edition Error Codes

85 | Core

Error Error Message Error Resolution

Codes

O-BW- exceeded the timeout value specified for the

CORE- activity.
50063
6

TIBC Activity input data validation error. This error message is reported when the data
O-BW- The input data for activity [{0}] in that is provided as an input to the activity does
CORE- process [{1}], module [{2}] does not not comply with the input schema of the
50063 conform to the activity input activity. This error can occur if the previous
8 schema. {3} {4} activity in the process generated incorrect data
or the activity input XSLT transformation
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-BW- error. The output data from output data generated by the activity does not
CORE- activity [{0}] in process [{1}], comply with the output schema of the activity.
50064 module [{2}] does not conform to Some activities can generate in-compliant
0 the activity output schema. {3} {4} output if it receives incorrect data from the
external entity it is interacting. In 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-BW- validation error. The input/output that is provided as an input to the activity or
CORE- data for activity [{0}] in process the output data generated by the activity does
50064 [{1}], module [{2}] does not not comply with the output schema of the
1 conform to the activity activity.
input/output schema. {3} {4}

TIBC Unable to obtain activity input This error message is reported when an entity
O-BW- data. The BW Engine has not been such as the event subscriber attempts to
CORE- initialized or started. obtain an activity input data before the BW
50064 Engine has been initialized or started. Ensure
2 the BW Engine has started before performing

TIBCO BusinessWorks™ Container Edition Error Codes

86 | Core

Error Error Message Error Resolution

Codes

this operation.

TIBC Unable to obtain activity input This error message is reported when an entity
O-BW- data. The specified ActivityEvent such as the event subscriber attempts to
CORE- object is invalid, the ActivityEvent obtain an activity input data; however the
50064 can not be null. specified ActivityEvent
3 (com.tibco.bw.runtime.event.ActivityAuditEven
t) object is invalid or null. Ensure the
ActivityEvent object is valid.

TIBC Unable to obtain activity input Unexpected error occurred when an entity
O-BW- data due to exception [{0}] such as the event subscriber is attempting to
CORE- obtain activity input data. For more details,
50064 refer to the additional exception message or
4 the "CausedBy" statements reported as part of
this error message.

TIBC Unable to obtain activity output This error message is reported when an entity
O-BW- data. The BW Engine has not been such as the event subscriber attempts to
CORE- initialized or started. obtain an activity output data before the BW
50064 Engine has been initialized or started. Ensure
5 the BW Engine has started before performing
this operation.

TIBC Unable to obtain activity output This error message is reported when an entity
O-BW- data. The specified ActivityEvent such as the event subscriber attempts to
CORE- object is invalid, the ActivityEvent obtain an activity output data; however the
50064 can not be null. specified ActivityEvent
6 (com.tibco.bw.runtime.event.ActivityAuditEven
t) object is invalid or null. Ensure the
ActivityEvent object is valid.

TIBC Unable to obtain activity output Unexpected error occurred when an entity
O-BW- data due to exception [{0}] such as the event subscriber is attempting to
CORE- obtain activity output data. For more details,
50064 refer to the additional exception message or

TIBCO BusinessWorks™ Container Edition Error Codes

87 | Core

Error Error Message Error Resolution

Codes

7 the "CausedBy" statements reported as part of

this error message.

TIBC Unable to obtain XPath functions Error was encountered when attempting to
O-BW- associated with the BusinessWork obtain the list of XPath functions associated
CORE- Activity, encountered exception with the BW Activity.
50064 [{0}]
8

TIBC Unable to find process information BWEngine is not able to obtain process
O-BW- for process [{0}] in module information for the specified BW process.
CORE- ModuleName={1}, ModuleVersion= Ensure the BW Module contains the required
50070 {2}. process.
5

Design Time Error Codes

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

Error Codes Error Message Error Resolution

TIBCO-BW-DT- Cyclic reference detected in Inspect the reference binding on the

VALIDATION- process {0}. Reference {1} process. BWEngine does not support
500023 points to {2}. This might references that point to the same process.
cause the application to This reference needs to be removed. Point
reach impaired state at to another process/sub process to correct
runtime. this.

TIBCO-BW-DT- One or more sources Delete existing links and create links again
VALIDATION- mapped for activity {0} before deploying to runtime.
500024 contain invalid references.

TIBCO-BW-DT- Process configuration error. Remove this variable or quick fix.

VALIDATION- The variable with name [ 

TIBCO BusinessWorks™ Container Edition Error Codes

88 | Core

Error Codes Error Message Error Resolution

500025 {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 [{0}]
MODULE-_ must end with .qualifier in
VERSION_ the manifest file [META-
CONFIG_ERROR- INF/MANIFEST.MF]
500620

APPLICATION_ The Bundle-Version of Not aplicable.

MANIFEST_ Application [{0}] must end
VERSION_ with .qualifier in the
ERROR-501005 manifest file [META-
INF/MANIFEST.MF].

TIBCO BusinessWorks™ Container Edition Error Codes

89 | Palettes

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

File Palette Error Codes

This section describes the error messages that can be reported by the activities or entities
associated with the File palette.

Error Error Message Error Resolution

Codes

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

PALETTE- resolution is not applicable.
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 affect
FILE-400001 the activity execution.

TIBCO BusinessWorks™ Container Edition Error Codes

90 | Palettes

Error Error Message Error Resolution

Codes

TIBCO-BW- File name [{0}] is not valid. Ensure that file name must not be
PALETTE- empty or null string.
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 on

PALETTE- general tab is checked or delete the
FILE-500002 already existing file.

TIBCO-BW- An exception [{0}] occurred when Ensure the file name is valid and the
PALETTE- attempting to write to the file [{1}]. 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 [{1}] createNonExistingDirectory option
FILE-500004 does not exist. on general tab is checked.

TIBCO-BW- Cannot read the binary content from Ensure the file name is valid and the
PALETTE- the file [{0}]. access permissions are set
FILE-500005 appropriately.

TIBCO-BW- Cannot read the string content from the Ensure the file name is valid and the
PALETTE- file [{0}]. access permissions are set
FILE-500006 appropriately.

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 is
PALETTE- file [{1}]. valid and the access permissions are
FILE-500009 set appropriately.

TIBCO BusinessWorks™ Container Edition Error Codes

91 | Palettes

Error Error Message Error Resolution

Codes

TIBCO-BW- Unable to rename the file from [{0}] to Ensure the source file and
PALETTE- file [{1}]. The destination file exists and destination file both are of same
FILE-500010 its type is different then the type of the type.
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 is
PALETTE- valid and the access permissions are
FILE-500012 set appropriately.

TIBCO-BW- An exception [{0}] occurred when Ensure the file or directory name is
PALETTE- attempting to create the file [{1}]. valid and the access permissions are
FILE-500013 set appropriately.

TIBCO-BW- Cannot overwrite the file [{0}] to file Ensure the Overwrite checkBox on
PALETTE- [{1}], when the overwrite flag is not general tab is checked or delete the
FILE-500014 selected in the activity configuration. already existing file explicitly.

TIBCO-BW- Cannot copy a directory [{0}] to an Ensure that source should not be a
PALETTE- existing file [{1}]. directory when destination exists
FILE-500015 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 is
PALETTE- valid and the access permissions are

TIBCO BusinessWorks™ Container Edition Error Codes

92 | Palettes

Error Error Message Error Resolution

Codes

FILE-500018 set appropriately.

TIBCO-BW- The file name value provided for the Ensure that fileName must not be
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 to This is an internal product error.
PALETTE- 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

This section describes the error messages that can be reported by the activities or entities
associated with the FTP palette.

Error Codes Error Message Error Resolution

TIBCO-BW- Unable to establish FTP connection for Ensure FTP Connection parameters
PALETTE- the FTP function [{0}]. Encountered are set properly.
FTP-500003 error [{1}].

TIBCO-BW- File [{0}] already exists. Ensure Overwrite Existing File check
PALETTE- box is checked or delete the file on
FTP-500004 server.

TIBCO BusinessWorks™ Container Edition Error Codes

93 | Palettes

Error Codes Error Message Error Resolution

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.

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. Local Ensure the local file is specified for
PALETTE- file specified cannot be found [{0}]. PUT or MPUT command.
FTP-500010

TIBCO-BW- Unexpected reply code. Returned Code Please Contact TIBCO Support.
PALETTE- [{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.

TIBCO BusinessWorks™ Container Edition Error Codes

94 | Palettes

Error Codes Error Message Error Resolution

PALETTE- Reason [{0}].

FTP-500022

TIBCO-BW- Error performing mget. Reason: mget Please Contact TIBCO Support.
PALETTE- is not supported for FTP via Proxy
FTP-500024

TIBCO-BW- Error in PUT or MPUT command.Error: Error in PUT or MPUT command.

PALETTE- [{0}]. See Fault Tab for details.
FTP-500025

TIBCO-BW- Error in GET or MGET command.Error: Error in GET or MGET command.

PALETTE- [{0}]. See Fault Tab for details.
FTP-500026

General Palette Error Codes

This section describes the error messages that can be reported by the activities or entities
associated with the General Activities palette.

Error Codes Error Message Error Resolution

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 activity This is an internal product

GENERALACTIVITIES- [{0}] failed to generate a new error. Contact TIBCO Support.
000001 event due to exception [{1}]

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

GENERALACTIVITIES- resolution is not applicable.
100001

TIBCO BusinessWorks™ Container Edition Error Codes

95 | Palettes

Error Codes Error Message Error Resolution

TIBCO-BW-PALETTE- {0} This is a debug message and

GENERALACTIVITIES- resolution is not applicable.
200001

TIBCO-BW-PALETTE- {0} This is an informational

GENERALACTIVITIES- message and it highlights the
300001 runtime progress of the
activity. Resolution is not
applicable.

TIBCO-BW-PALETTE- {0} This is a warning message and

GENERALACTIVITIES- it highlights situations that
400001 may affect the activity
execution.

TIBCO-BW-PALETTE- Error executing external command Ensure the activity is

GENERALACTIVITIES- [{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 access
500001 permissions are set
appropriately.

TIBCO-BW-PALETTE- No command specified. Ensure the specified field in

GENERALACTIVITIES- the activity input is configured
500002 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 a
GENERALACTIVITIES- valid. positive long value.
500004

TIBCO-BW-PALETTE- Activity configuration error. The

TIBCO BusinessWorks™ Container Edition Error Codes

96 | Palettes

Error Codes Error Message Error Resolution

GENERAL-ACTIVITIES- {2} Shared Variable must be

500001 configured for {3} Shared Variable
activity [{0}] in the process [{1}].

HTTP Palette Error Codes

This section describes the error messages that can be reported by the activities or entities
associated with the HTTP palette.

Error Error Message Error Resolution

Codes

TIBCO-BW- {0} This is an internal product

PALETTE- error. Contact TIBCO Support.
HTTP-
000001

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

PALETTE- resolution is not applicable.
HTTP-
100001

TIBCO-BW- {0} This is a debug message and

PALETTE- resolution is not applicable.
HTTP-
200001

TIBCO-BW- {0} This is an informational

PALETTE- message and it highlights the
HTTP- runtime progress of the
300001 activity. Resolution is not
applicable.

TIBCO-BW- {0} This is a warning message and

PALETTE- it highlights situations that

TIBCO BusinessWorks™ Container Edition Error Codes

97 | Palettes

Error Error Message Error Resolution

Codes

HTTP- 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 error.
HTTP-
500001

TIBCO-BW- The Http Server replied with a [{0}] status Check the status code to
PALETTE- code know the reason for the error.
HTTP-
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 initialize Check the exception and
PALETTE- 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 the Correct the input data of Send
PALETTE- message body is specified Http Request activity.Make
HTTP- sure message body is not
500005 specified when parameters
are used.

TIBCO-BW- A GET Method doesn't have a message body Correct the input data of Send
PALETTE- Http Request activity. Make
HTTP- sure that the message body is
500006 not specified for a GET
request.

TIBCO-BW- Invalid endpoint URL Correct either the http client

TIBCO BusinessWorks™ Container Edition Error Codes

98 | Palettes

Error Error Message Error Resolution

Codes

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 Send
PALETTE- Http Request activity. Make
HTTP- sure that the HTTP method is
500009 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 attachments Request activity. Only 'POST'
HTTP- method can send
500011 attachments.

TIBCO-BW- Error serializing attachment data, Cause: [{0}] Check the exception and
PALETTE- 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 is

TIBCO BusinessWorks™ Container Edition Error Codes

99 | Palettes

Error Error Message Error Resolution

Codes

HTTP- [{0}]
500014

TIBCO-BW- An IOException was thrown while trying to System exception.

PALETTE- read the response
HTTP-
500015

TIBCO-BW- An IOException was thrown while trying to System exception.

PALETTE- send the response
HTTP-
500016

TIBCO-BW- An Exception was thrown while trying to send System exception.

PALETTE- the response
HTTP-
500017

TIBCO-BW- The header [{0}] is defined as non-Repeating Correct the input data.
PALETTE- Header in Input Headers. This header cannot
HTTP- 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 recovering ProcessStarter and Send Http
500021 from a check-pointed BusinessWorks process Response activity.
instance.

TIBCO-BW- Failed to authenticate request. Username and Check if the identity resource
PALETTE- Password is not set. referenced in Http Client

TIBCO BusinessWorks™ Container Edition Error Codes

100 | Palettes

Error Error Message Error Resolution

Codes

HTTP- resource contains username

500022 and password.

TIBCO-BW- Failed to authenticate request. Check if the LDAP resource is

PALETTE- configuired on Http Connector
HTTP- 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
PALETTE- field in Send HTTP Response
HTTP- 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

This section describes the error messages that can be reported by the activities or entities
associated with the Java palette.

Error Codes Error Message Error Resolution

TIBCO-BW-PALETTE- [{0}]
JAVA-
PROCESSSTARTER-
000001

TIBCO BusinessWorks™ Container Edition Error Codes

101 | Palettes

Error Codes Error Message Error Resolution

TIBCO-BW-PALETTE- [{0}]
JAVA-
PROCESSSTARTER-
100001

TIBCO-BW-PALETTE- [{0}]
JAVA-
PROCESSSTARTER-
200001

TIBCO-BW-PALETTE- [{0}]
JAVA-
PROCESSSTARTER-
300001

TIBCO-BW-PALETTE- [{0}]
JAVA-
PROCESSSTARTER-
400001

TIBCO-BW-PALETTE- The JAVA ProcessStarter activity Ensure that the correct object
JAVA- [{0}] failed to a generate a new passed to the 'onEvent' method
PROCESSSTARTER- event due to exception [{1}] in the specified Java class.
500001 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 activity Ensure that the ProcessStarter

JAVA- [{0}] failed to a generate a new has been stopped properly.
PROCESSSTARTER- event due to exception [{1}] since
500003 it is in the stopped state.

TIBCO BusinessWorks™ Container Edition Error Codes

102 | Palettes

Error Codes Error Message Error Resolution

TIBCO-BW-PALETTE- [{0}] This is an internal product error.

JAVA-000001 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 and

JAVA-200001 resolution is not applicable.

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

JAVA-300001 and it highlights the runtime
progress of the activity.
Resolution is not applicable.

TIBCO-BW-PALETTE- [{0}] This is a warning message and it

JAVA-400001 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 values
JAVA-500504 because [{1}]. 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 methods
JAVA-500604 because [{1}]. are returning the correct values
to display the activity output
tab.

TIBCO-BW-PALETTE- Output data error in field [{0}] Ensure that the getter methods
JAVA-500605 value cannot be null. are not returning null to display
the activity output tab.

TIBCO-BW-PALETTE- Output data error in field [{0}] Ensure that the getter method

TIBCO BusinessWorks™ Container Edition Error Codes

103 | Palettes

Error Codes Error Message Error Resolution

JAVA-500606 value is not serializable. returns a serializable Java class

to display the activity output
tab.

TIBCO-BW-PALETTE- While executing method [{0}] Correct the error stated in the
JAVA-500001 encountered exception [{1}] [{2}]. exception message and retry.

TIBCO-BW-PALETTE- Activity input data conversion Incorrect object reference was

JAVA-500013 error. Exception [{0}] occurred specified for the declared Java
while trying to render the activity class. Ensure that the correct
input data. [{1}] 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 activity referenced in your Java class.
output data. [{1}]

TIBCO-BW-PALETTE- The Java class [{0}] is not found in Ensure that that the specified
JAVA-500017 the classpath. Encountered class file is contained in the
ClassNotFoundException [{1}]. classpath.

TIBCO-BW-PALETTE- Activity input error. The activity Ensure that the correct values
JAVA-500019 received an incorrect value for the are provided for the constructor
method parameters. parameter elements that are in
IllegalArgumentException the activity input tab.
occurred while trying to construct
an instance of the Java class [{0}]:
[{1}]

TIBCO-BW-PALETTE- Unable to construct an instance of Correct the error stated in the

JAVA-500020 the Java class [{0}]. Encountered exception message and retry.
exception [{1}] [{2}].

TIBCO-BW-PALETTE- The constructor for the Java class The exception was raised by the

TIBCO BusinessWorks™ Container Edition Error Codes

104 | Palettes

Error Codes Error Message Error Resolution

JAVA-500021 [{0}] raised exception [{1}]. [{2}] constructor of the declared Java
class. Please refer to the Java
class implementation for details.

TIBCO-BW-PALETTE- Unable to obtain information for Reconfigure this activity or verify

JAVA-500026 the method [{0}] from the class that the declared Java class has
[{1}]. Encountered not changed since the last
NoSuchMethodException [{2}]. configuration.

TIBCO-BW-PALETTE- Unable to obtain information for Correct the error stated in the
JAVA-500027 the method [{0}] from the class exception message and retry.
[{1}]. Encountered
SecurityException [{2}].

TIBCO-BW-PALETTE- Activity input error. The activity Ensure that the correct values
JAVA-500031 received an incorrect value for the are provided for the method
method parameters. When parameter elements that are in
attempting to invoke the method the activity input tab.
[{0}], encountered
IllegalArgumentException [{1}].

TIBCO-BW-PALETTE- Activity input error. The activity Ensure that the correct Java
JAVA-500032 received an incorrect Java object object reference is provided for
for the declared Java class [{0}]. the declared Java class element
The activity required an instance shown in the input tab of this
of the Java class [{1}], but activity. Ensure that the
received an instance of the Java classpath refers to the correct
class [{2}]: [{3}] declared class.

TIBCO-BW-PALETTE- Activity input error. The activity Ensure that the correct Java
JAVA-500033 received an incorrect Java object object reference is provided for
for the declared Java class [{0}]. the declared Java class element
The Java object received is not shown in the input tab of this
compatible with the Java object activity. Ensure that the
required by this activity. The classpath refers to the correct
activity required an instance of declared class.
the Java class [{1}]: [{2}]

TIBCO BusinessWorks™ Container Edition Error Codes

105 | Palettes

Error Codes Error Message Error Resolution

TIBCO-BW-PALETTE- Activity input error. The activity Ensure that the correct Java
JAVA-500034 received 'null' value for the for the object reference is provided for
declared Java class. The activity the declared Java class element
required an instance of the class shown in the input tab of this
[{0}], but received a 'null'. activity.The 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 [{0}]. Correct the error stated in the
JAVA-500035 Encountered exception [{1}] [{2}]. exception message and retry.

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

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

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

TIBCO-BW-PALETTE- Activity input error. The activity Ensure that the correct Java
JAVA-500042 required instance of class [{0}], object reference is provided for
but received a 'null' value for the the declared Java class element
declared Java class. shown in the input tab of this
activity.The preceding activity
that provides the input value for
this activity should not produce
a null for its output.

TIBCO BusinessWorks™ Container Edition Error Codes

106 | Palettes

Error Codes Error Message Error Resolution

TIBCO-BW-PALETTE- Activity input error. The activity Ensure that the correct Java
JAVA-500043 received incorrect Java object for object reference is provided for
the declared Java class. The the declared Java class element
activity required an instance of a shown in the input tab of this
class [{0}], but received instance activity. Ensure that the
of a class [{1}]. classpath refers to the correct
declared class.

TIBCO-BW-PALETTE- Data Conversion error. When Ensure that unsupported data

JAVA-500046 attempting to convert Java object types are not utilized or
to XML data encountered referenced in your Java class.
exception [{0}].

TIBCO-BW-PALETTE- Data Conversion error. When Ensure that unsupported data

JAVA-500047 attempting to convert XML data to types are not utilized or
Java object encountered referenced in your Java class.
exception [{0}].

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).

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

TIBCO BusinessWorks™ Container Edition Error Codes

107 | Palettes

Error Codes Error Message Error Resolution

TIBCO-BW-PALETTE- The Java Process Starter The exception was raised by the
JAVA-500066 onShutdown method [{0}] raised 'onShutdown' method of the
exception [{1}]. [{2}]. 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. Method= Make sure the Class referenced
JAVA-501069 [{0}] references a Class=[{1}] no the method is valid.
longer exists. Cause=[{2}]

TIBCO-BW-PALETTE- Activity input error. The activity Ensure that the input content is
JAVA-500070 does not receive proper input. not empty.

TIBCO-BW-PALETTE- Unable to obtain information for Reconfigure this activity or verify

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

JDBC Palette Error Codes

This section describes the error messages that can be reported by the activities or entities
associated with the JDBC palette.

Error Error Message Error Resolution

Codes

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 in Support.
000001 the group

TIBCO-BW- The JDBC activity [{0}] is first activity in the This is a debug message and

TIBCO BusinessWorks™ Container Edition Error Codes

108 | Palettes

Error Error Message Error Resolution

Codes

PALETTE- JDBC Transaction. resolution is not applicable.

JDBC-
200001

TIBCO-BW- JDBC activity [{0}] initialized successfully. This is a debug message and
PALETTE- resolution is not applicable.
JDBC-
200002

TIBCO-BW- JDBC activity [{0}] task submitted to This is a debug message and
PALETTE- Threadpool for execution resolution is not applicable.
JDBC-
200003

TIBCO-BW- Executing SQL Statement [{0}] for activity [{1}]. This is a debug message and
PALETTE- resolution is not applicable.
JDBC-
200004

TIBCO-BW- Connection received from Datasource for This is a debug message and
PALETTE- activity [{0}]. resolution is not applicable.
JDBC-
200005

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

TIBCO-BW- Output for activity [{0}] is [{1}]. This is a debug message and
PALETTE- resolution is not applicable.
JDBC-
200007

TIBCO-BW- Executing SQL Statement for activity [{0}]. This is a debug message and
PALETTE- resolution is not applicable.

TIBCO BusinessWorks™ Container Edition Error Codes

109 | Palettes

Error Error Message Error Resolution

Codes

JDBC-
200008

TIBCO-BW- Executing Prepared Statement for activity [{0}].

PALETTE-
JDBC-
200009

TIBCO-BW- Successfully executed sql statement [{0}] for This is a debug message and
PALETTE- activity [{1}]. resolution is not applicable.
JDBC-
200010

TIBCO-BW- Last subset reached for activity [{0}]. This is a debug message and
PALETTE- resolution is not applicable.
JDBC-
200011

TIBCO-BW- Process in subset output for activity [{0}] with This is a debug message and
PALETTE- noofRecords [{1}] is [{2}]. resolution is not applicable.
JDBC-
200012

TIBCO-BW- All Parameters set successfully on Statement This is a debug message and
PALETTE- for activity [{0}]. resolution is not applicable.
JDBC-
200013

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

TIBCO-BW- Number of updates for JDBC Update activity is This is a debug message and
PALETTE- 0. Executing Insert Statement [{0}] since activity resolution is not applicable.
JDBC- is in Upsert mode.

TIBCO BusinessWorks™ Container Edition Error Codes

110 | Palettes

Error Error Message Error Resolution

Codes

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 create
PALETTE- query and create unique aliases for duplicate unique aliases for duplicate
JDBC- fields. fields.
500004

TIBCO-BW- Improper SQL statement used. {0} Check the syntax of the SQL
PALETTE- Statement specified.
JDBC-
500005

TIBCO-BW- Exception occurred occurred when attempting Check the Shared Resource
PALETTE- to create a JDBC Connection for JDBC configuration this activity is
JDBC- Transaction. configure with and also that
500006 the database is running.

TIBCO-BW- Missing Input Value for required Column [{0}]. Check the input tab of the
PALETTE- activity and set the column
JDBC- value
500007

TIBCO BusinessWorks™ Container Edition Error Codes

111 | Palettes

Error Error Message Error Resolution

Codes

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

TIBCO-BW- {0} is not a valid timezone. Check the activity

PALETTE- configuration input tab and
JDBC- enter a valid timezone
500010

TIBCO-BW- Could not create Connection to server using Check the JDBC Connection
PALETTE- Shared Resource [{0}]. Shared Resource
JDBC- configuration which is
500011 configured on the activity.

TIBCO-BW- INVALID_JDBC_ACTIVITY_CONFIGURATION = Check the activity

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

TIBCO-BW- INVALID_SQL_STATEMENT = Invalid Activity Check the activity

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

TIBCO-BW- PREPARED_PARAMETERS_MORE_THAN_ Check the activity

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

TIBCO-BW- PREPARED_PARAMETERS_LESS_THAN_ Check the activity

PALETTE- QUESTION_MARKS = Invalid Activity configuration for the
JDBC- Configuration. Number of Prepared Parameters Prepared Parameters
500015 in activity configuration is less than number of specified.
'?' in SQL Statement

TIBCO BusinessWorks™ Container Edition Error Codes

112 | Palettes

Error Error Message Error Resolution

Codes

TIBCO-BW- BATCH_UPDATE_WITHOUT_PREPARED_PARAMS Check the SQL statement in

PALETTE- = Batch Update mode works only with Prepared the activity configuration to
JDBC- Statements ensure that it is a SQL
500016 statement with prepared
parameters.

TIBCO-BW- JDBC Connection login timed out. Check the configuration

PALETTE- details or increase the login
JDBC- timeout.
500019

JMS Palette Error Codes

This section describes the error messages that can be reported by the activities or entities
associated with the JMS palette.

Error Error Message Error Resolution

Codes

TIBCO-BW- {0}
PALETTE-
JMS-000001

TIBCO-BW- {0}
PALETTE-
JMS-100001

TIBCO-BW- {0}
PALETTE-
JMS-200001

TIBCO-BW- {0}
PALETTE-
JMS-300001

TIBCO BusinessWorks™ Container Edition Error Codes

113 | Palettes

Error Error Message Error Resolution

Codes

TIBCO-BW- {0}
PALETTE-
JMS-400001

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

TIBCO-BW- Invalid configuration data. Specified Check activity configuration for

PALETTE- connection reference is not found in JMS Connection Reference.
JMS-500002 repository. {0}

TIBCO-BW- Invalid configuration data. JMS destination Check activity configuration for
PALETTE- is not specified. the JMS Destination field.
JMS-500003

TIBCO-BW- Error occurred when attempting to create Check activity configuration for
PALETTE- Durable Subscriber the Durable Subscription name
JMS-500004 box and if JMS server is
running.

TIBCO-BW- Failed to create connection to the JMS Check JMS Connection shared
PALETTE- server. {0} resource configuration and if
JMS-500005 the JMS server is running.

TIBCO-BW- Unable to create a session to receive Check JMS Connection shared

PALETTE- messages [{0}]. resource configuration and if
JMS-500006 the JMS server is running.

TIBCO-BW- Unable to create a reply session/producer Check JMS Connection shared

PALETTE- [{0}] resource configuration and if
JMS-500007 the JMS server is 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 BusinessWorks™ Container Edition Error Codes

114 | Palettes

Error Error Message Error Resolution

Codes

TIBCO-BW- Error occurred when attempting to create Check JMS Connection shared
PALETTE- MessageConsumer resource configuration and if
JMS-500009 the JMS server is running.

TIBCO-BW- Error occurred when attempting to resolve Check JMS Connection shared
PALETTE- destination [{0}] resource configuration and if
JMS-500010 the JMS server is running.

TIBCO-BW- Invalid configuration data. JMS Reply To Check the activity configuration
PALETTE- Destination Not Specified. and specify a value in the JMS
JMS-500011 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 a Check the activity

PALETTE- JMS message configuration, JMS Connection
JMS-500013 shared resource configuration
and if the JMS server is
running.

TIBCO-BW- Error occurred when attempting to confirm Check the activity

PALETTE- a JMS message configuration, JMS Connection
JMS-500014 shared resource configuration
and if the JMS server is
running.

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

TIBCO BusinessWorks™ Container Edition Error Codes

115 | Palettes

Mail Palette Error Codes

This section describes the error messages that can be reported by the activities or entities
associated with the Mail palette.

Error Error Message Error Resolution

Codes

TIBCO-BW- [{0}] This is an internal product error.

PALETTE- Contact TIBCO Support.
MAIL-
000001

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

PALETTE- resolution is not applicable.
MAIL-
100001

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

PALETTE- resolution is not applicable.
MAIL-
200001

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

PALETTE- and it highlights the runtime
MAIL- progress of the activity. Resolution
300001 is not applicable.

TIBCO-BW- [{0}] This is a warning message and it

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

TIBCO-BW- Invalid input data. Reason: Error parsing Ensure the destination addresses
PALETTE- input data. given are valid.
MAIL-
500005

TIBCO-BW- Invalid input data. Reason: Both the Ensure that both the comma and

TIBCO BusinessWorks™ Container Edition Error Codes

116 | Palettes

Error Error Message Error Resolution

Codes

PALETTE- comma and semicolon cannot be used semicolon cannot be used at same
MAIL- at same time to separate addresses: [{0}] time to separate addresses.
500007

TIBCO-BW- Error connecting to the mail server. Ensure the host provided is valid.
PALETTE- Reason: unknown host - connection
MAIL- parameters: [{0}].
500020

TIBCO-BW- Error building mail message. Cause: [{0}]. Ensure the input message details
PALETTE- are properly given.
MAIL-
500033

TIBCO-BW- From address [{0}] is not valid. Ensure the From address must not
PALETTE- be empty or null string
MAIL-
500035

TIBCO-BW- Error sending mail message. Ensure the SMTP shared resource
PALETTE- configuration is appropriately
MAIL- specified.
500036

TIBCO-BW- The system cannot find the file specified: Ensure the file exists at a given
PALETTE- [{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.

TIBCO BusinessWorks™ Container Edition Error Codes

117 | Palettes

Error Error Message Error Resolution

Codes

MAIL-
500001

TIBCO-BW- Username can not be null when using Ensure the username value must
PALETTE- Authentication not be null when using
MAIL- authentication.
500002

TIBCO-BW- Password can not be null when using Ensure the password value must
PALETTE- Authentication not be null when using
MAIL- authentication.
500003

TIBCO-BW- Error closing mail server connection. Ensure the Mail receiver
PALETTE- Cause: [{0}]. configuration is appropriately
MAIL- given.
500004

TIBCO-BW- Mail provider for protocol [{0}] not Ensure that the mail provider jar is
PALETTE- found. Make sure that the provider jar is in java classpath.
MAIL- in java classpath.
500008

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- parameters: [Host:{0}, Port:{1}, User:{2}]. parameters are properly
500010 configured.

TIBCO-BW- Could not connect to mail server - Ensure the username and password
PALETTE- invalid username in field [{0}] and/or provided are valid.
MAIL- invalid password.

TIBCO BusinessWorks™ Container Edition Error Codes

118 | Palettes

Error Error Message Error Resolution

Codes

500011

TIBCO-BW- The default mail folder was not found Ensure the Mail receiver
PALETTE- on mail server. configuration is appropriately
MAIL- given.
500012

TIBCO-BW- The INBOX mail folder was not found on Ensure the Mail receiver
PALETTE- mail server. configuration is appropriately
MAIL- given.
500013

TIBCO-BW- Error getting folder on mail server. Ensure the Mail receiver
PALETTE- configuration is appropriately
MAIL- given.
500014

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 is
MAIL- unchecked or don't use explicit
500015 confirm.

TIBCO-BW- Error connecting to the mail server using Ensure the mail server is up or
PALETTE- 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- given.
500023

TIBCO BusinessWorks™ Container Edition Error Codes

119 | Palettes

Error Error Message Error Resolution

Codes

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 activity This is an internal product error.
PALETTE- [{0}] failed to a generate a new event Contact TIBCO Support.
MAIL- due to exception [{1}] since it is in the
500026 stopped state.

TIBCO-BW- Marking msg {0} for confirmation. This is an informational message

PALETTE- and it highlights the runtime
MAIL- progress of the activity. Resolution
300001 is not applicable.

Parse Palette Error Codes

This section describes the error messages that can be reported by the activities or entities
associated with the Parse palette.

Error Error Message Error Resolution

Codes

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 not

TIBCO BusinessWorks™ Container Edition Error Codes

120 | Palettes

Error Error Message Error Resolution

Codes

PALETTE- applicable.
PARSE-
100001

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

PALETTE- 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 highlights

PALETTE- situations that may affect the activity
PARSE- 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-
500001

TIBCO-BW- Exception in parse eval: [{0}] An error occurred while processing, refer to
PALETTE- the exception thrown and correct the activity
PARSE- configuration or input.
500002

TIBCO-BW- Line length must be > 0 Check if line length is greater than zero.
PALETTE-

TIBCO BusinessWorks™ Container Edition Error Codes

121 | Palettes

Error Error Message Error Resolution

Codes

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 may
PARSE- .... last row contents was: [{4}] be more than the records present in the file.
500004

TIBCO-BW- Input type is not specified. Check configuration of Input type on Parse
PALETTE- Data activity. Ensure either File or String is
PARSE- configured.
500005

TIBCO-BW- Please specify the Input type Check configuration of Input type on Parse
PALETTE- field. Data activity. Ensure either File or String is
PARSE- 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

TIBCO-BW- File [{0}] cannot be opened Check the encoding configruation on Parse
PALETTE- using encoding method [{1}] Data activity. Ensure encoding supported by
PARSE- file is selected.
500009

TIBCO-BW- Format Type must be selected. Ensure that Format type is configured on
PALETTE- Data Format shared resource.
PARSE-

TIBCO BusinessWorks™ Container Edition Error Codes

122 | Palettes

Error Error Message Error Resolution

Codes

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 Format shared resource.
PARSE- in a row.
500013

TIBCO-BW- Error while parsing headers in Ensure that the input message has MIME
PALETTE- the mime message. headers.
PARSE-
500014

TIBCO-BW- An I/O exception occurred Ensure that the SOAP payload is well formed
PALETTE- while parsing SOAP payload in and valid.
PARSE- the root part.
500015

TIBCO-BW- An Unexpected exception UNEXPECTED_EXCEPTION.resolution =This is

PALETTE- occurred while parsing an internal product error. Contact TIBCO
PARSE- Message. Root cause is [{0}] Support
5000016

TIBCO-BW- The SOAP Message doesn't Ensure that the input message has SOAP
PALETTE- exist in the Root part. payload in it.
PARSE-
500017

TIBCO-BW- Soap Envelope has invalid XML Ensure that the SOAP payload is valid and
PALETTE- content. well formed.
PARSE-
500018

TIBCO BusinessWorks™ Container Edition Error Codes

123 | Palettes

Error Error Message Error Resolution

Codes

TIBCO-BW- One or more mime parts have Ensure that in input message does not have
PALETTE- same Content-Id value in the same content id for different mime parts.
PARSE- Mime Message.
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 content-
PALETTE- in mime part of the Mime id header and corresponding value.
PARSE- Message.
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 Ensure that the 'boundary' attribute is not
PALETTE- in the Mime Message. missing in the mime header.
PARSE-
500023

TIBCO-BW- startinfo parameter is missing Ensure that 'startinfo' attribute is present in

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

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 'content-

TIBCO BusinessWorks™ Container Edition Error Codes

124 | Palettes

Error Error Message Error Resolution

Codes

PALETTE- found in the Mime Message. 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 parameter
PALETTE- parameter, of root part, does and type parameter is same in the root part
PARSE- not match in the Mime of the Mime Message.
500029 Message.

TIBCO-BW- ERROR_LINE_LESS_THAN_ Ensure that Line length is not less than max
PALETTE- 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_

LENGTH.resolution

TIBCO BusinessWorks™ Container Edition Error Codes

125 | Palettes

TCP Palette Error Codes

This section describes the error messages that can be reported by the activities or entities
associated with the TIBCO ActiveMatrix BusinessWorks™ TCP palette.

Error Error Message Error Resolution

Codes

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

PALETTE- applicable.
TCP-200001

TIBCO-BW- Cannot start TCP Receiver Please correct Host and Port and retry.
PALETTE- on Host [{0}], Port [{1}].
TCP-500001 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 TIBCO
PALETTE- Reason: [{0}]. Support..
TCP-500006

TIBCO-BW- Error opening TCP This is an internal product error. Contact TIBCO
PALETTE- Connection. Reason: [{0}]. Support..
TCP-500008

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

TIBCO-BW- Exception closing TCP This is an internal product error. Contact TIBCO
PALETTE- Connection. Reason: [{0}]. Support..
TCP-500013

TIBCO BusinessWorks™ Container Edition Error Codes

126 | Palettes

Error Error Message Error Resolution

Codes

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 Receiver Check Host and Port and retry.
PALETTE- on Host=[{0}], Port=[{1}].
TCP-500016 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. Reason: This is an internal product error. Contact TIBCO
PALETTE- [{0}]. Support...
TCP-500018

TIBCO-BW- Timeout while reading Possible causes for this error are:(1)The data is
PALETTE- TCP data being read before it is written.(2)If the data that is
TCP-500021 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.

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

PALETTE- while retrieving XML Support..
TCP-500022 Output for activity [{0}].

TIBCO BusinessWorks™ Container Edition Error Codes

127 | Palettes

Error Error Message Error Resolution

Codes

TIBCO-BW- The TCP Receiver Process This is an internal product error. Contact TIBCO
PALETTE- Starter activity [{0}] failed Support.
TCP-500023 to a generate a new event
due to exception [{1}]
since it is in the stopped
state.

TIBCO-BW- The Wait For TCP Request This is an internal product error. Contact TIBCO
PALETTE- activity [{0}] failed to a Support.
TCP-500024 generate a new event due
to exception [{1}] since it
is in the stopped state.

TIBCO-BW- Invalid SSL There is error with the SSL Configurations. Correct
PALETTE- Configurations. Reason: [\ the SSL Configurations and then retry.
TCP-500025 {0}].

TIBCO-BW- Cannot start TCP Receiver Correct Port and retry.

PALETTE- on Port [\{0}]. Reason: [\
TCP-500026 {1}].

XML Palette Error Codes

This section describes the error messages that can be reported by the activities or entities
associated with the XML palette.

Error Error Message Error Resolution

Codes

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

PALETTE- TIBCO Support.
XML-000001

TIBCO-BW- [{0}] This is a trace message and resolution is not

TIBCO BusinessWorks™ Container Edition Error Codes

128 | Palettes

Error Error Message Error Resolution

Codes

PALETTE- applicable.
XML-100001

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

PALETTE- not applicable.
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 highlights

PALETTE- situations that may affect the activity
XML-400001 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 due Ensure the input XML node is properly given.
PALETTE- to exception [{0}].
XML-500001

TIBCO-BW- Unable to parse the XML due to Ensure the provided input XML is well
PALETTE- exception [{0}]. formed and valid.
XML-500002

TIBCO-BW- Exception [{0}] occurred during Ensure the provided input XML and input
PALETTE- XSLT transformation. Exception XSLT is properly given.
XML-500003 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.

TIBCO BusinessWorks™ Container Edition Error Codes

129 | Palettes

Error Error Message Error Resolution

Codes

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 activity Ensure that the input content is not empty.
PALETTE- does not receive proper input.
XML-500009

TIBCO BusinessWorks™ Container Edition Error Codes

130 | 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 object

FRWK-000010 returned by [{0}#create()] is null.

TIBCO-BW-SR- {0}
FRWK-500001

TIBCO-BW-SR- Failed to {0} SharedResource [{1}] for Module [{2}:{3}], DeploymentUnit

FRWK-502000 [{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 BusinessWorks™ Container Edition Error Codes

131 | Shared Resources

Error Codes Error Message

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 {NANOSECONDS,
THREADPOOL- MICROSECONDS, MILLISECONDS, SECONDS, MINUTES, HOURS, DAYS}.
500003

TIBCO-BW-SR- No matching rejection policy found for {0}, possible values are {BLOCKING,
THREADPOOL- CALLER_RUNS, ABORT}.
500004

TIBCO BusinessWorks™ Container Edition Error Codes

132 | Shared Resources

Error Codes Error Message

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 equal
THREADPOOL- 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.

Error Codes Error Message Error Resolution

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

DATAFORMAT-200001 resolution is not applicable.

TIBCO-BW-SR- Failed to {0} Data Format Check the configuration of Data

DATAFORMAT-500000 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 BusinessWorks™ Container Edition Error Codes

133 | Shared Resources

Error Codes Error Message Error Resolution

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

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

FTP-200001 is not applicable.

HTTP Client Error Codes

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

Error Codes Error Message Error Resolution

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

HTTP-CLIENT- resolution is not applicable.
200001

TIBCO-BW-SR- Failed to {0} HTTP Client resource [{1}] Check the configuration of Http
HTTP-CLIENT- Client resource.
500000

TIBCO-BW-SR- User name or Password is not Specify user name and password
HTTP-CLIENT- specified in Identity in Identity shared resource.
500001

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

HTTP Connector Error Codes

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

TIBCO BusinessWorks™ Container Edition Error Codes

134 | Shared Resources

Error Codes Error Message Error Resolution

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

HTTP- is not applicable.
CONNECTOR-
100001

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

HTTP- resolution is not applicable.
CONNECTOR-
200001

TIBCO-BW-SR- Error while stopping HTTP This is an informational message and

HTTP- endpoint [{0}] it highlights the runtime progress of
CONNECTOR- the shared resource. Resolution is not
300003 applicable.

TIBCO-BW-SR- Error while stopping HTTP context This is an informational message and
HTTP- [{0}] it highlights the runtime progress of
CONNECTOR- the shared resource. Resolution is not
300004 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 Connector Check the configuration of Http

HTTP- resource [{0}] with the specified Connector resource.
CONNECTOR- configuration. Check the
500003 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 endpoint Check the exception and correct the
HTTP- [{0}] because of exception [{1}] configuration of Http Connector

TIBCO BusinessWorks™ Container Edition Error Codes

135 | Shared Resources

Error Codes Error Message Error Resolution

CONNECTOR- resource or Http Event source.

500005

TIBCO-BW-SR- The HTTP server instance cannot Check the configuration of Http
HTTP- be started, because it is not Connector resource or Http Event
CONNECTOR- 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 configuration
HTTP- endpoint [{0}] on Http Connector resource.
CONNECTOR-
500009

TIBCO-BW-SR- Unable to find Application bundle System exception.

HTTP- [{0}]
CONNECTOR-
500010

TIBCO-BW-SR- Failed to create HTTP Connector Check the port configured on Http
HTTP- resource [{0}] configured with port Connector resource is not in use.
CONNECTOR- [{1}]
500012

TIBCO-BW-SR- LDAP resource is not configured Please check if LDAP resource is

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

TIBCO BusinessWorks™ Container Edition Error Codes

136 | Shared Resources

Java Global Instance Error Codes

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

Error Error Message Error Resolution

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 constructor
JAVA- IllegalArgumentException occurred while trying parameter elements that are in
500004 to construct an instance of the Java class [{0}]: the activity input tab.
[{1}]

TIBCO- The constructor for the Java class [{0}] raised The exception was raised by the
BW-SR- exception [{1}]. [{2}] 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

TIBCO BusinessWorks™ Container Edition Error Codes

137 | Shared Resources

Error Error Message Error Resolution

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 the
500007 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 the
500008 last configuration.

TIBCO- The cleanup method [{0}] raised exception The exception was raised by the
BW-SR- [{1}]. [{2}] method of the specified Java
JAVA- class. Please refer to the
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 the
BW-SR- Encountered exception [{1}] [{2}]. method of the specified Java
JAVA- class. Please refer to the
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 BW
500014 Module properties.

TIBCO- {0} This is a debug message and

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

TIBCO BusinessWorks™ Container Edition Error Codes

138 | Shared Resources

Error Error Message Error Resolution

Codes

TIBCO- Failed to {0} Java Global Instance resource [{1}]

BW-SR-
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.

Error Codes Error Message Error Resolution

TIBCO-BW-SR-JMS- {0}
100001

TIBCO-BW-SR-JMS- {0}
200001

TIBCO-BW-SR-JMS- {0}
300001

TIBCO-BW-SR-JMS- {0}
400001

TIBCO-BW-SR-JMS- Failed to {0} JMS Connection Check JMS Connection Shared

502000 resource [{1}] resource configuration

TIBCO BusinessWorks™ Container Edition Error Codes

139 | Shared Resources

JDBC Connection Error Codes

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

Error Error Message Error Resolution

Codes

TIBCO- Received an update request This is an informational message and it highlights

BW-SR- for existing configuration the runtime progress of the shared resource.
JDBC- with PID=[{0}] and Shared Resolution is not applicable.
300001 resource name [{1}]

TIBCO- Updating Password for This is an informational message and it highlights

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

TIBCO- Updating Username for This is an informational message and it highlights

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

TIBCO- Updating Database URL[{0}] This is an informational message and it highlights

BW-SR- for Shared Resource with the runtime progress of the shared resource.
JDBC- PID[{1}] and name[{2}] Resolution is not applicable.
300004

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

TIBCO- Adding new configuration for This is an informational message and it highlights
BW-SR- Shared Resource with name the runtime progress of the shared resource.
JDBC- [{0}] Resolution is not applicable.
300006

TIBCO BusinessWorks™ Container Edition Error Codes

140 | Shared Resources

Error Error Message Error Resolution

Codes

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

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

TIBCO- Following Drivers have been This is an informational message and it highlights
BW-SR- loaded in the framework the runtime progress of the shared resource.
JDBC- [{0}]. Following Shared Resolution is not applicable.
300008 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 JDBC
BW-SR- closing a bad connection connection was marked invalid by the driver and
JDBC- with [Vendor ErrorCode:{0}] was removed from the pool. This connection
400001 and SQL STATE[{1}] could not be closed successfully.

TIBCO- Maximum permitted This is a warning message. The JDBC Connection

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

TIBCO- No suitable This is a warning message. This message prints

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

TIBCO- Failed to {0} JDBC A JDBC Connection lifecycle error has occurred.
BW-SR- Connection resource [{1}]. Check the connection configuration and restart
JDBC- the application if necessary.

TIBCO BusinessWorks™ Container Edition Error Codes

141 | Shared Resources

Error Error Message Error Resolution

Codes

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

TIBCO BusinessWorks™ Container Edition Error Codes

142 | Shared Resources

JNDI Configuration Error Codes

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

Error Codes Error Message Error Resolution

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 Configuration Check JNDI Configuration shared

JNDI-502000 resource [{1}] resource configuration.

Proxy Configuration Error Codes

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

Error Codes Error Message Error Resolution

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.

TIBCO BusinessWorks™ Container Edition Error Codes

143 | Shared Resources

SMTP Resource Error Codes

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

Error Error Message Error Resolution

Codes

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

BW-SR- applicable.
MAIL-
200001

TIBCO- Adding new configuration [{0}]. This is an informational message and it

BW-SR- 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.
MAIL- Resolution is not applicable.
300002

TIBCO- Mail Session created This is an informational message and it

BW-SR- successfully. highlights the runtime progress of the activity.
MAIL- Resolution is not applicable.
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 appropriately
BW-SR- information from Trinity for configured.
MAIL- JNDI [{0}].
500001

TIBCO- Mail Session creation failed. Ensure the smtp shared resource is

TIBCO BusinessWorks™ Container Edition Error Codes

144 | Shared Resources

Error Error Message Error Resolution

Codes

BW-SR- appropriately configured.

MAIL-
500002

TIBCO- Handler for MimeType [{0}] not Ensure the MimeType is valid.
BW-SR- 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.

Error Codes Error Message Error Resolution

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

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

TCP-200001 is not applicable.

TIBCO BusinessWorks™ Container Edition Error Codes

145 | 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
The following documentation for this product is available on the TIBCO BusinessWorks™
Container Edition page:
l TIBCO BusinessWorks™ Container Edition Release Notes
l TIBCO BusinessWorks™ Container Edition Installation
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 Tuning
l TIBCO BusinessWorks™ Container Edition REST Implementation
l TIBCO BusinessWorks™ Container Edition Refactoring Best Practices

TIBCO BusinessWorks™ Container Edition Error Codes

146 | TIBCO Documentation and Support Services

l TIBCO BusinessWorks™ Container Edition Samples

How to Contact TIBCO Support

You can contact TIBCO Support in the following ways:
l For an overview of TIBCO Support, visit http://www.tibco.com/services/support.
l For accessing the Support Knowledge Base and getting personalized content about
products you are interested in, visit the TIBCO Support portal at
https://support.tibco.com.
l For creating a Support case, you must have a valid maintenance or support contract
with TIBCO. You also need a user name and password to log in to
https://support.tibco.com. If you do not have a user name, you can request one by
clicking Register on the website.

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.

TIBCO BusinessWorks™ Container Edition Error Codes

147 | 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, ActiveMatrix BusinessWorks, ActiveSpaces, Business Studio,
TIBCO Business Studio, TIBCO Designer, Enterprise Message Service, Hawk, 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
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.

TIBCO BusinessWorks™ Container Edition Error Codes

148 | 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-2022. TIBCO Software Inc. All Rights Reserved.

TIBCO BusinessWorks™ Container Edition Error Codes