Tibco Activematrix Businessworks™ Error Codes: November 2020

TIBCO ActiveMatrix
BusinessWorks™
Error Codes
Version 6.7
November 2020
Copyright © 2001-2020. TIBCO Software Inc. All Rights Reserved.

2
Contents
TIBCO Documentation and Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Message Codes Naming Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
SOAP Binding Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
REST Binding Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Admin Agent Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Admin Command Line Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Admin Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Engine Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
List of Process Engine Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
TEA Agent Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Design Time Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Palettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
File Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
FTP Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
General Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
HTTP Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Java Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
JDBC Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
JMS Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Mail Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Parse Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Rendezvous Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
REST and JSON Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
TCP Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
XML Palette Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Shared Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Shared Resource Framework Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Data Format Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
FTP Connection Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
HTTP Client Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
HTTP Connector Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Java Global Instance Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
JMS Connection Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
JDBC Connection Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
TIBCO ActiveMatrix BusinessWorks™ Error Codes

3
JNDI Configuration Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Proxy Configuration Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Rendezvous Transport Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
SMTP Resource Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
TCP Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Legal and Third-Party Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

4
TIBCO Documentation and Support Services
How to Access TIBCO Documentation
Documentation for TIBCO products is available on the TIBCO Product Documentation website, mainly in
HTML and PDF formats.
The TIBCO Product Documentation website is updated frequently and is more current than any other
documentation included with the product. To access the latest documentation, visit https://docs.tibco.com.
Product-Specific Documentation
Documentation for TIBCO products is not bundled with the software. Instead, it is available on the TIBCO
Documentation site.
Access the following TIBCO ActiveMatrix BusinessWorks™ guides on the TIBCO Documentation site:
● Concepts
● Installation
● Getting Started
● Application Development
● Administration
● Bindings and Palettes Reference
● Samples
● Error Codes
● Migration
● Performance Benchmarking and Tuning
● REST Reference Guide
● Refactoring Best Practices
How to Contact TIBCO Support
You can contact TIBCO Support in the following ways:
● For an overview of TIBCO Support, visit http://www.tibco.com/services/support.

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

5
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 ActiveMatrix BusinessWorks™ Engine Layer
PVM ActiveMatrix BusinessWorks Engine Layer
TIBCO-BW-ADMIN ActiveMatrix BusinessWorks Administrator
TIBCO-BW-ADMIN-CLI ActiveMatrix BusinessWorks Administrator Command Line Interface
TIBCO-BW-BINDING- ActiveMatrix BusinessWorks REST Binding

REST
TIBCO-BW-BINDING- ActiveMatrix BusinessWorks SOAP Binding

SOAP
TIBCO-BW-CORE ActiveMatrix BusinessWorks Engine Layer
TIBCO-BW-FRWK ActiveMatrix BusinessWorks Framework
TIBCO-BW-PALETTE ActiveMatrix BusinessWorks Palette Layer
TIBCO-BW-PALETTE- ActiveMatrix BusinessWorks Palette specific activity implementation

<PaletteName>
TIBCO-BW-SR ActiveMatrix BusinessWorks Shared Resource API Layer
TIBCO-BW-SR- ActiveMatrix BusinessWorks specific Shared Resource implementation

<UniqueName>
TIBCO-BW-STATS ActiveMatrix BusinessWorks Stats Collector
TIBCO-THOR-FRWK Thor Framework
The Engine layers with component IDs BX and PVM do not follow this convention.
The following table lists the log levels used by the software and the corresponding message code range.

6
Log Level Error Code
TRACE 100001 - 109999
DEBUG 200001 - 209999
INFO 300001 - 309999
WARN 400001 - 409999
ERROR Errors can be indicated by one of the following error code ranges:
● 500001 - 509999
● 600001 and higher
● 0xxxxx
● Error codes 600001 and higher indicate exceptions in the execution and
are always associated with a 5xxxxx error code, which can be traced in
the log file.
● Error codes starting with 0xxxxx indicate internal errors. Contact
TIBCO Support for possible resolution or a workaround.
The message describes the issue. Sometimes, the message can contain parameters shown as ({N}), where N
is an integer. For example, consider the message for error code TIBCO-BW-ADMIN-500300 : The AppNode
[{0}] does not exist in AppSpace [{1}] and Domain [{2}]. These parameters are substituted with
appropriate values at runtime.

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

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

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

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

BINDING- resource for SoapServiceBinding [{0}], Contact TIBCO support.
TIBCO-BW- SOAP BindingFactory is initialized with This is a internal resolution message.

BINDING- incorrect BindingConfiguration for the Resolution not required.
SOAP-001031 SOAP Reference Binding.
TIBCO-BW- Failed to parse binding meta data file Ensure that the xml file contents are
BINDING- [{0}] in bundle [{1}] due to exception valid and well formed.
SOAP-001040 [{2}].
TIBCO-BW- Failed to process File [{0}] in bundle Ensure that the 'name' attribute of the
BINDING- [{1}]. BindingName is not specified. service element contains a unique
SOAP-001050 Binding Name.
TIBCO-BW- Failed to process File [{0}] in bundle Ensure that Binding Name of the SOAP
BINDING- [{1}]. A Binding with name [{2}] is Interceptor is unique and it does not
SOAP-001060 already registered. match with any Binding Name (service/
reference) in the Application Module
TIBCO-BW- Failed to deploy the SOAP Interceptor Ensure that the SOAP Interceptor
BINDING- Module [{0}], due to exception [{1}]. deployed follows the Axis2 Module
SOAP-001070 Root exception message is [{2}]. protocol.
TIBCO-BW- Failed to initialize SOAP Binding. BW_SOAP_BINDING_NAME_MISSIN

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

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

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

BINDING- Application Version is not available. Contact TIBCO support.
SOAP-001100
TIBCO-BW- Failed to locate WSDL definition for Ensure that the a WSDL exist with port
BINDING- port type [{0}]. type [{0}] in the application module.
SOAP-001130
TIBCO-BW- MEP [{0}] is not supported. Review the Ensure that the MEP definition for Port
BINDING- WSDL definition for Port type [{1}]. type [{1}] is either IN-OUT OR IN-
SOAP-001140 ONLY
TIBCO-BW- Failed to recognize the MEP for Port Ensure that the MEP definition for Port
BINDING- type [{0}]. type [{0}] is either IN-OUT OR IN-
SOAP-001150 ONLY
TIBCO-BW- Failed to find message receiver for MEP Ensure that the MEP definition for Port
BINDING- [{0}] for port type [{1}]. type [{1}] is either IN-OUT OR IN-
SOAP-001160 ONLY
TIBCO-BW- SOAP Binding [{1}] for portType [{0}] is Ensure that the SOAP Binding [{1}] for
BINDING- missing Transport Configuration. port type [{0}] is configured with a
SOAP-001170 Transport.
TIBCO-BW- Operation Configuration for Operation Ensure that SOAP Binding [{2}] is in
BINDING- [{0}], Port Type [{1}], SOAP Binding [{2}] sync with WSDL.
SOAP-001180 is missing. Ensure that SOAP Binding
[{2}] is in sync with WSDL
TIBCO-BW- Failed to initialize SOAP Service This is an internal product error.

BINDING- Binding [{0}]. Promoted Name for the Contact TIBCO support.
SOAP-001110 Binding is missing.
TIBCO-BW- Failed to initialize SOAP Reference This is an internal product error.

BINDING- Binding [{0}]. Promoted Name for the Contact TIBCO support.
SOAP-001120 Binding is missing.
TIBCO-BW- Failed to load WSDL definition for Make sure the WSDL with namespace
BINDING- namespace [{0}]. [{0}] exists in the application module.
SOAP-001130
TIBCO-BW- Malformed MIME Message received. Ensure that the MIME Message is well
BINDING- Failed to parse the attachments in the formed with correct mime boundaries.
SOAP-500009 received message for Operation [{0}],
SoapBinding [{1}], Application [{2}:{3}].
Ignoring the attachments from the
SOAP Message.

9
TIBCO-BW- Failed to create SoapServiceBinding This is a internal resolution message.

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

BINDING- [{0}], Application [{1}:{2}] due to context mapping. if any, done on
SOAP-500020 exception [{3}] SoapServiceBinding [{0}] are correct.
TIBCO-BW- Failed to add transport dependency for Ensure that the SoapServiceBinding
BINDING- SoapServiceBinding [{0}], Application [{0}] is configured with a Shared
SOAP-500030 [{1}:{2}] Transport Resource.
TIBCO-BW- Failed to initialize SoapServiceBinding Ensure that each SOAP/HTTP service

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

BINDING- [{0}]. The operation [{1}] with Action" and "MessageStyle:Destination"
SOAP-500050 soapaction [{2}] is already registered for should be unique.
destination [{3}] with Message Style
[{4}].
TIBCO-BW- Failed to send SOAP Fault message to This is an internal product error.
BINDING- the consumer of the service for Contact TIBCO support.
SOAP-500060 Operation [{0}], SoapServiceBinding
[{1}], Application [{2}:{3}] due to
exception [{4}]. Root Exception
message: {5}
TIBCO-BW- Failed to process Reply message for Ensure that the Binding configuration
BINDING- Operation [{0}], SoapServiceBinding and Context Configuration, if any, done
SOAP-500070 [{1}], Application [{2}:{3}] due to on SoapServiceBinding [{1}] are correct.
exception [{4}]. Sending Undeclared
Fault message to the consumer of this
service. Root Exception message: [{5}]
TIBCO-BW- Error occurred while processing Service Ensure that the Context Mapping done
BINDING- Request messages Context Information on SoapServiceBinding [{1}] are correct.
SOAP-500080 for Operation [{0}], SoapServiceBinding
exception [{4}]. Root Exception
message: {5}
TIBCO-BW- Error occurred while processing Service Ensure that the Message part
BINDING- Request message for Operation [{0}], configuration and header configuration,
SOAP-500090 SoapServiceBinding [{1}], Application if any, done on SoapServiceBinding [{1}]
[{2}]:{3}] due to exception [{4}]. Root are correct.
Exception message: {5}

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

BINDING- implementation failed to complete the correct.
SOAP-500120 request for the Operation [{0}],
SoapServiceBinding [{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 error.

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

BINDING- the SOAP Binding Configuration Contact TIBCO support.
SOAP-500131 Resources due to exception [{1}]
TIBCO-BW- An interrupted fault occurred while This is an internal product error.

BINDING- waiting for the Service Request message Contact TIBCO support.
SOAP-500140 to be processed for Operation [{0}],
SoapServiceBinding [{1}], Application
[{2}:{3}] due to exception [{4}]. Sending
TIBCO-BW- Failed to start SoapServiceBinding [{0}], Ensure that the Transport Configuration
BINDING- Application [{1}:{2}] due to exception done on SoapServiceBinding [{0}] are
SOAP-500150 [{3}] correct.

11
TIBCO-BW- Failed to stop SoapServiceBinding [{0}], This is an internal product error.

BINDING- Application [{1}:{2}] due to exception Contact TIBCO support.
SOAP-500160 [{3}]
TIBCO-BW- Error occurred while processing Service Ensure that the Context Mapping and
BINDING- Request messages Context information configuration done on
SOAP-500170 for Operation [{0}], SoapServiceBinding SoapServiceBinding [{1}] are correct.
exception [{4}]. Sending Undeclared
Fault message to the consumer of this
service. Root Exception message: {5}
TIBCO-BW- Failed to start JMS transport primitive This is an internal product error.
BINDING- for SoapServiceBinding [{0}], Contact TIBCO support.
SOAP-500190 Application [{1}:{2}] due to exception
[{3}]
TIBCO-BW- Failed to stop JMS transport primitive This is an internal product error.
BINDING- for SoapServiceBinding [{0}], Contact TIBCO support.
[{3}]
TIBCO-BW- Failed to Initialize JMS transport Ensure that the transport configuration
BINDING- primitive for SoapServiceBinding [{0}], done on SoapServiceBinding [{0}] are
SOAP-500210 Application [{1}:{2}] due to exception correct.
[{3}]
TIBCO-BW- Failed to read incoming JMS raw This is an internal product error.
BINDING- message due to exception [{0}]; Contact TIBCO support.
SOAP-500230
TIBCO-BW- Failed to create JMS Reply Handler for Ensure that the transport configuration
BINDING- SoapServiceBinding [{0}], Application done on SoapServiceBinding [{0}] are
SOAP-500240 [{1}:{2}] due to exception [{3}] correct.
TIBCO-BW- Failed to process service request Ensure that the Service Provider is
BINDING- message for SoapServiceBinding [{0}], sending a correct SOAP Envelope.
[{3}] .Root exception message : [{4}]
TIBCO-BW- Failed to send Service Reply message This is an internal product error.
BINDING- for Operation [{0}], Contact TIBCO support.
SOAP-500260 SoapServiceeBinding [{1}], Application
[{2}:{3}] due to exception [{4}]
TIBCO-BW- Failed to acknowledge Service Request This is an internal product error.

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

12
TIBCO-BW- Failed to authenticate Request message Check if the identity resource

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

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

BINDING- for Operation [{0}], SoapServiceBinding Contact TIBCO support.
SOAP-500290 [{1}], Application [{2}:{3}] due to
exception [{4}].
TIBCO-BW- Malformed SOAP Request message Check if the SOAP Request Message is
BINDING- received for Operation [{0}], well formed.
SOAP-500300 SoapServiceBinding [{1}], Application
[{2}:{3}]. Root Exception message: [{5}]
TIBCO-BW- Failed to create SoapReferenceBinding This is an internal product error.

BINDING- [{0}], Application [{1}:{2}] due to Contact TIBCO support.
TIBCO-BW- Failed to create SoapReferenceEndpoint Ensure that configurations done on

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

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

BINDING- [{0}], Application [{1}:{2}] due to Contact TIBCO support.
TIBCO-BW- Failed to release transport resources for This is an internal product error.
BINDING- Operation [{0}], SoapReferenceBinding Contact TIBCO support.
exception [{4}]
TIBCO-BW- Received Declared Fault. Failed to This is an internal product error.

BINDING- release transport resources for Contact TIBCO support.
SOAP-550070 Operation [{0}], SoapReferenceBinding
exception [{4}]

13
TIBCO-BW- Unable to receive response from the This is an internal product error.
BINDING- service provider for Operation [{0}], Contact TIBCO support.
SOAP-550090 SoapReferenceBinding [{1}],
Application [{2}:{3}] due to exception
[{4}]
TIBCO-BW- Received SOAP Fault from the service This is an internal message sent to the
BINDING- provider of the Operation [{0}], framework for server error. Resolution
SOAP-550100 SoapReferenceBinding [{1}], not required.
Application [{2}:{3}]. SOAP Fault
received: [{4}]
TIBCO-BW- Received SOAP Fault from the service This is an internal message sent to the
BINDING- provider of the Operation [{0}], framework for client error. Resolution
SOAP-550101 SoapReferenceBinding [{1}], not required.
Application [{2}:{3}]. SOAP Fault
received: [{4}]
TIBCO-BW- Error occurred while processing the Ensure that the declared fault send back
BINDING- declared fault message from the service by the Service Provider is valid and
SOAP-550110 provider of the Operation [{0}], well formed SOAP Fault.
SoapReferenceBinding [{1}],
[{4}]
TIBCO-BW- Error occurred while processing reply Ensure that Message Part and Header
BINDING- message from the service provider of Configuration done on
SOAP-550120 the Operation [{0}], SoapReferenceBinding [{1}] are correct.
[{4}]
TIBCO-BW- SOAPEnvelope must contain a body Ensure that Service Provider has send a
BINDING- element which is either first or second valid SOAP Envelope.
SOAP-550121 child element of the SOAPEnvelope.
TIBCO-BW- Error occurred while processing reply Ensure that Context configuration and
BINDING- message attachments from the service Mapping for the attachment done on
SOAP-550130 provider of the Operation [{0}], SoapReferenceBinding [{1}] is correct.
[{4}]
TIBCO-BW- Failed to Initialize JMS transport Ensure that the Transport Sender
BINDING- primitive for SoapReferenceBinding configurations are correct.
exception [{3}]
TIBCO-BW- Failed to send Reference Request Ensure that the Message Configuration
BINDING- message for Operation [{0}], done on SoapReferenceBinding [{1}] are
SOAP-550170 SoapReferenceBinding [{1}], correct.
[{4}]

14
TIBCO-BW- Failed to process reply message from Ensure that the Message Configuration
BINDING- the service provider of the Operation done on SoapReferenceBinding [{1}] are
SOAP-550180 [{0}], SoapReferenceBinding [{1}], correct
[{4}]
TIBCO-BW- Failed to update HTTP Transport Ensure that the port number
BINDING- configurations before sending the configuration for
SOAP-550190 Reference Request message for SoapReferenceBinding [{1}] is valid
Operation [{0}], SoapReferenceBinding
exception [{4}].
TIBCO-BW- Failed to create the HTTP Client Ensure that the Endpoint URL is in
BINDING- required for sending the Reference correct format.
SOAP-550210 Request message for Operation [{0}],
[{4}]
TIBCO-BW- Failed to serialize JMS transport Ensure that the configuration done on
BINDING- message due to exception [{1}]. Reference Binding are correct.
SOAP-550220
TIBCO-BW- Failed to convert JMS message to string Ensure that the configuration done on
BINDING- due to exception [{1}]. Reference Binding are correct.
SOAP-550230
TIBCO-BW- Failed to create Endpoint URL for Ensure that the Endpoint URI
BINDING- Operation [{0}], SoapReferenceBinding configuration on SOAPRefernceBinding
SOAP-550240 [{1}], Application [{2}:{3}] due to [{1}] is correct.
exception [{4}]
TIBCO-BW- Unable to receive response from the Ensure that the Service Provider is
BINDING- service provider for Operation [{0}], available.
[{4}]. Message Received: [{5}]
TIBCO-BW- Unable to receive response from the Ensure that HTTP Client configurations
BINDING- service provider for Operation [{0}], are configured as per service provider
SOAP-555010 SoapReferenceBinding [{1}], requirements.
TIBCO-BW- Unable to receive response from the Ensure that HTTP Client configurations
BINDING- service provider for Operation [{0}], are configured as per service provider

15
TIBCO-BW- Unable to send request the service Ensure that HTTP Client configurations
BINDING- provider for Operation [{0}], are configured as per service provider
TIBCO-BW- Unable to send request the service Ensure that the COOKIE format is
BINDING- provider for Operation [{0}], correct.
REST Binding Error Codes

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

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

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

BINDING- enabled. Trying to authenticate using
REST-200012 the Authorization Header of the request
TIBCO-BW- Expected JSON Content-Type. Got XML The Client needs to be notified to use
BINDING- Instead. Replying with error to client the right Content-Type Header or the
REST-400001 binding configuration can be changed
to allow multiple content-types
TIBCO-BW- Expected XML Content-Type. Got JSON The Client needs to be notified to use
BINDING- Instead. Replying with error to client the right Content-Type Header or the
REST-400002 binding 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 = Check configuration of the REST

BINDING- No relative resource url specified to binding for the value of the Resource
REST-500002 deploy REST Resource URL field.
TIBCO-BW- Unable to create REST resource for Check both binding configurations
BINDING- binding [{0}]. Reason - Unable to stop specified in the error message for the
REST-500003 conflicting binding [{1}]. Resource URL fields
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 message
REST-500004
TIBCO-BW- Unable to start REST Binding with Check configuration of the REST
BINDING- name [{0}] binding specified in the error message
REST-500004
TIBCO-BW- Unable to stop REST Binding with Check configuration of the REST
BINDING- name [{0}} binding specified in the error message
REST-500005

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

BINDING- resource could not be retrieved. Please
REST-500010 check the REST Binding configuration
or the logs if the HTTP Connector could
not be started.
TIBCO-BW- The HTTP Connector [{0}] shared

BINDING- resource could not be retrieved. Please
REST-500011 check the REST Binding configuration
or the logs if the HTTP Connector could
not be started.
TIBCO-BW- AUTHENTICATION_FAILED =
BINDING- Authentication failed for client request.
REST-500012 A 401 status code has been sent to the
client with the realm as [{0}].
TIBCO-BW- WSDL_CACHE_NOT_FOUND = An
BINDING- error occurred while trying to retrieve
REST-500013 the WSDL/XSD's for the REST binding
[{0}]. 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-000001 deploying again.

18
Core
This section lists the error codes returned by the core components such as runtime and administration.
Admin Agent Error Codes

This section lists the error messages that can be reported by the bwagent.
TIBCO-BW- BW6_ADMIN_AGENT_CONNECTIO
ADMIN- N_FAILED = Connection to BW Agent
PRSTNC-500001 failed.
TIBCO-BW- BW6_ADMIN_AGENT_DATA_STORE
ADMIN- _LOCATION_INVALID = bwagent.ini
PRSTNC-500002 configuration error.
bw.agent.technology.as.dataStoreLocati
on=[{0}] does not exist.
TIBCO-BW- BW6_ADMIN_AGENT_READ_TIMEO
ADMIN- UT = bwagent.ini configuration error.
PRSTNC-500003 read timeout is invalid
TIBCO-BW- BW6_ADMIN_AGENT_WRITE_TIME
ADMIN- OUT = bwagent.ini configuration error.
PRSTNC-500004 write timeout is invalid
TIBCO-BW- Failed to execute query on Space [{0}]

ADMIN- with given parameters
PRSTNC-500005
TIBCO-BW- BW6_ADMIN_AGENT_NOT_READY
ADMIN- = bwagent is not ready or the the
PRSTNC-500006 existing connection to the bwagent is
stale. Re-try the command, if the
problem persists, restart the process
and try again.
TIBCO-BW- BW6_ADMIN_AGENT_DATABASE_D Please change the

ADMIN- RIVER_INVALID = bwagent.ini bw.agent.technology.dbems.db.driver
PRSTNC-500007 configuration error. field in BW_HOME/config/bwagent.ini
bw.agent.technology.dbems.db.driver=[{ file. Example: com.mysql.jdbc.Driver
0}] is invalid.
TIBCO-BW- BW6_ADMIN_AGENT_DATABASE_C BW6_ADMIN_AGENT_DATABASE_C

ADMIN- ONNECTION_INVALID = bwagent.ini ONNECTION_INVALID.resolution =
PRSTNC-500008 configuration error. Please change the
bw.agent.technology.dbems.db.connecti bw.agent.technology.dbems.db.connecti
onURL=[{0}] is invalid. onURL field in BW_HOME/config/
bwagent.ini. Example: jdbc:mysql://
<HOST>:<PORT>/<DB>

19
TIBCO-BW- BW6_ADMIN_AGENT_DATABASE_D The PostgreSQL driver is available by

ADMIN- RIVER_MISSING = The [{0}] database default. To use MySQL, download the
PRSTNC-500009 driver is missing. JDBC driver to the BW_HOME/
system/lib folder.
TIBCO-BW- BW6_ADMIN_AGENT_DATABASE_S Please search online for database

ADMIN- QL_EXECUTION_FAILED = Failed to connection problems.
PRSTNC-500010 execute query on database with given
parameters. [{0}]
TIBCO-BW- BW6_ADMIN_AGENT_DATABASE_S Contact TIBCO Support.

ADMIN- QL_FILE_INVALID =SQL script file is
PRSTNC-500011 not found or invalid for creating
database structure.
TIBCO-BW- BW6_ADMIN_AGENT_CONFIGURAT Please check docs.tibco.com about

ADMIN- ION_MISSING = bwagent.ini "configuring bwagent for Database/
PRSTNC-500012 configuration error. [{0}] is missing. EMS".
TIBCO-BW- Invalid query. Mandatory argument(s)

ADMIN- are missing. Contact TIBCO Support.
PRSTNC-000100
Admin Command Line Error Codes

This section describes the error messages that can be reported by the Administrator command line.
TIBCO-BW- {0}
ADMIN-
CLI-100001
TIBCO-BW- {0}
ADMIN-
CLI-200001
TIBCO-BW- BusinessWorks is already running.

ADMIN-
CLI-300001
TIBCO-BW- No match found for [{0}].

ADMIN-
CLI-300005
TIBCO-BW- Found matches:

ADMIN-
CLI-300006
TIBCO-BW- Restore completed.

ADMIN-
CLI-300007

20
TIBCO-BW- Backup completed.

ADMIN-
CLI-300008
TIBCO-BW- Backup failed, <CausedBy> {0}

ADMIN-
CLI-300009
TIBCO-BW- Registered TEA Agent [{0}] with TEA

ADMIN- Server.
CLI-300010
TIBCO-BW- Restored Agent [{0}]

ADMIN-
CLI-300030
TIBCO-BW- Backed up Agent [{0}]

ADMIN-
CLI-300031
TIBCO-BW- Domain [{0}] created.

ADMIN-
CLI-300100
TIBCO-BW- BWAgent [{0}] registered in Domain

ADMIN- [{1}].
CLI-300101
TIBCO-BW- Domain [{0}] was deleted.

ADMIN-
CLI-300102
TIBCO-BW- Restored Domain [{0}]

ADMIN-
CLI-300130
TIBCO-BW- Backed up Domain [{0}]

ADMIN-
CLI-300131
TIBCO-BW- BWAgent [{0}] unregistered from the

ADMIN- AppSpace [{1}]. The AppSpace is
CLI-300132 removed from remote machine.
TIBCO-BW- AppSpace [{0}] in Domain [{1}] created.

ADMIN-
CLI-300200
TIBCO-BW- AppSpace [{0}] in Domain [{1}]

ADMIN- removed.
CLI-300201

21
TIBCO-BW- Machine [{0}] added to AppSpace [{1}],

ADMIN- Domain [{2}].
CLI-300202
TIBCO-BW- AppSpace [{0}] in Domain [{1}] started.

ADMIN-
CLI-300203
TIBCO-BW- AppSpace [{0}] in Domain [{1}] stopped.

ADMIN-
CLI-300204
TIBCO-BW- AppSpace [{0}] expanded to BWAgent

ADMIN- [{1}] in Domain [{2}].
CLI-300205
TIBCO-BW- AppSpace [{0}] in Domain [{1}] deleted.

ADMIN-
CLI-300206
TIBCO-BW- Restored AppSpace [{0}]

ADMIN-
CLI-300230
TIBCO-BW- Backed up AppSpace [{0}]

ADMIN-
CLI-300231
TIBCO-BW- AppNode [{0}] in AppSpace [{1}],

ADMIN- Domain [{2}] created.
CLI-300300
TIBCO-BW- AppNode [{0}] in Domain [{1}] deleted.

ADMIN-
CLI-300301
TIBCO-BW- AppNode [{0}] in AppSpace [{1}],

ADMIN- Domain [{2}] started.
CLI-300302
TIBCO-BW- AppNode [{0}] in Domain [{1}] stopped.

ADMIN-
CLI-300303
TIBCO-BW- Console enabled for AppNode [{0}] in

CLI-300304
TIBCO-BW- Console disabled for AppNode [{0}] in

CLI-300305

22
TIBCO-BW- Debugger disabled for AppNode [{0}]

ADMIN- in AppSpace [{1}] in Domain [{2}]
CLI-300306
TIBCO-BW- Restored AppNode [{0}]

ADMIN-
CLI-300330
TIBCO-BW- Backed up AppNode [{0}]

ADMIN-
CLI-300331
TIBCO-BW- Stats enabled for AppNode [{0}] in

CLI-300304
TIBCO-BW- The application [{0}:{1}] created

ADMIN- successfully.
CLI-300400
TIBCO-BW- The application [{0}:{1}] deleted

CLI-300401
TIBCO-BW- The application [{0}:{1}] updated

CLI-300402
TIBCO-BW- Deployed application [{0}:{1}].

ADMIN-
CLI-300403
TIBCO-BW- Undeployed application [{0}:{1}].

ADMIN-
CLI-300404
TIBCO-BW- The application [{0}:{1}] started.

ADMIN-
CLI-300405
TIBCO-BW- The application [{0}:{1}] stopped.

ADMIN-
CLI-300406
TIBCO-BW- Hotfix for application [{0}:{1}] deployed.

ADMIN-
CLI-300407
TIBCO-BW- Hotfix for application [{0}:{1}]

ADMIN- undeployed.
CLI-300408

23
TIBCO-BW- Deleted archive [{0}].

ADMIN-
CLI-300409
TIBCO-BW- Uploaded archive [{0}].

ADMIN-
CLI-300410
TIBCO-BW- Configured Application [{0}:{1}]

ADMIN-
CLI-300411
TIBCO-BW- Exported profile [{0}] from the Archive

ADMIN- [{1}].
CLI-300412
TIBCO-BW- Exported configuration from

ADMIN- Application [{0}:{1}].
CLI-300413
TIBCO-BW- Thread dump obtained.

ADMIN-
CLI-300414
TIBCO-BW- The application [{0}:{1}] paused.

ADMIN-
CLI-300415
TIBCO-BW- The application [{0}:{1}] resumed.

ADMIN-
CLI-300416
TIBCO-BW- The application [{0}:{1}] deployed and

ADMIN- started.
CLI-300417
TIBCO-BW- Stopped process starters of Application

ADMIN- [{0}:{1}]
CLI-300418
TIBCO-BW- Started process starters of Application

ADMIN- [{0}:{1}]
CLI-300419
TIBCO-BW- Agent log file obtained.

ADMIN-
CLI-300420
TIBCO-BW- AppNode log file obtained.

ADMIN-
CLI-300421

24
TIBCO-BW- Restored Application [{0}].

ADMIN-
CLI-300420
TIBCO-BW- Restored Application [{0}] on Agent

ADMIN- [{1}]
CLI-300430
TIBCO-BW- Backed up Application [{0}]

ADMIN-
CLI-300431
TIBCO-BW- Deployed application [{0}:{1}], The

ADMIN- AppSpace [{2}] does not have any
CLI-300432 AppNodes.
TIBCO-BW- An application is already deployed with

ADMIN- archive [{0}].
CLI-300433
TIBCO-BW- Deleted BWAgent [{0}].

ADMIN-
CLI-300434
TIBCO-BW- Enabled debug port [{0}] on AppNode

ADMIN- [{1}] in AppSpace [{2}] in Domain [{3}]
CLI-300631
TIBCO-BW- Restored Archive [{0}]

ADMIN-
CLI-300630
TIBCO-BW- BW6_INFR_WARN_FORMAT = {0}

ADMIN-
CLI-400000
TIBCO-BW- Make sure to change the {0} setting in Adjust the setting in the indicated file to
ADMIN- the {1} file. The newer version of the the current installation.
CLI-400010 product does not work with the data of
an installation from a previous version.
TIBCO-BW- BW6_INFR_ERROR_FORMAT = {0}

ADMIN-
CLI-500000
TIBCO-BW- Failed to perform operation [{0}] on [{1}]

ADMIN- in the Domain [{2}] due to an error in
CLI-500001 initializing data manager, {3}
TIBCO-BW- Error while checking if the Entity [{0}] is

ADMIN- present in the Domain [{1}], {2}
CLI-500002

25
TIBCO-BW- The BW Agent [{0}] on the target

ADMIN- Machine is not running
CLI-500003
TIBCO-BW- Error invoking {0} method on the

ADMIN- remote agent [{1}], {2}
CLI-500004
TIBCO-BW- Error occurred while uploading the ear

ADMIN- file into data store, {0}
CLI-500005
TIBCO-BW- Failed to initialize transport, {0}

ADMIN-
CLI-500006
TIBCO-BW- Unsupported entity {0}

ADMIN-
CLI-500007
TIBCO-BW- Failed to perform operation [{0}] due to

ADMIN- an error in initializing data manager, {1}
CLI-500008
TIBCO-BW- Failed to write to file [{0}]

ADMIN-
CLI-500009
TIBCO-BW- Execution of this command is not

ADMIN- supported in admin mode 'local'.
CLI-500010
TIBCO-BW- Please provide the agent name.

ADMIN-
CLI-500011
TIBCO-BW- No matching Agent found

ADMIN-
CLI-500030
TIBCO-BW- Invalid value for mandatory entity

ADMIN- argument. Valid argument values are
CLI-500031 domain, appspace, appnode, and
application.
TIBCO-BW- The {0} command without any

ADMIN- argument is only supported in
CLI-500040 interactive console mode.
TIBCO-BW- Invalid value for mandatory entity

ADMIN- argument. Valid argument values are
CLI-500041 appnode and agent.

26
TIBCO-BW- Nothing to restore. Either agent [{0}]

ADMIN- does not exist or the agent is not part of
CLI-500042 the domain [{1}]
TIBCO-BW- Failed to configure bwagent, Check with the Administration Guide

ADMIN- <CausedBy> {0} for the supported configuration
CLI-500043 properties for bwagent and bwadmin.
TIBCO-BW- Domain [{0}] does not exist

ADMIN-
CLI-500100
TIBCO-BW- Domain [{0}] already exists in the

ADMIN- datastore
CLI-500101
TIBCO-BW- Failed to create Domain [{0}], {1}

ADMIN-
CLI-500102
TIBCO-BW- Domain home folder [{0}] does not

ADMIN- exist. Verify if the folder is present and
CLI-500103 use forward slash in the folder path
TIBCO-BW- Failed to delete Domain [{0}], {1}

ADMIN-
CLI-500104
TIBCO-BW- No matching Domain found

ADMIN-
CLI-500130
TIBCO-BW- Failed to delete BW Agent [{0}],

ADMIN- <CausedBy> {1}
CLI-500131
TIBCO-BW- Failed to unregister BW Agent [{0}]

ADMIN- from the AppSpace [{1}]. <CausedBy>
CLI-500132 {2}
TIBCO-BW- AppSpace [{0}] not found in Domain

ADMIN- [{1}]
CLI-500201
TIBCO-BW- AppSpace [{0}] already exists in

ADMIN- Domain [{1}]
CLI-500202
TIBCO-BW- Failed to create AppSpace [{0}] in

ADMIN- Domain [{1}], {2}
CLI-500203

27
TIBCO-BW- AppSpace [{0}] already exists with BW

ADMIN- Agent [{1}]
CLI-500204
TIBCO-BW- Failed to delete AppSpace [{0}] from

CLI-500205
TIBCO-BW- AppSpace [{0}] in Domain [{1}] could

ADMIN- not be started, {2}
CLI-500210

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

ADMIN- have any AppNodes.
CLI-500212
TIBCO-BW- Failed to export configuration from

ADMIN- AppSpace [{0}] and Domain [{1}] , {2}
CLI-500213

ADMIN- have configuration.
CLI-500214
TIBCO-BW- Configured AppSpace [{0}] in Domain

ADMIN- [{1}]. Restart AppSpace to apply
CLI-500215 changes.
TIBCO-BW- Configuration of AppSpace [{0}] in

ADMIN- Domain [{1}] failed, {2}
CLI-500216
TIBCO-BW- Exported configuration from AppSpace

ADMIN- [{0}] and Domain [{1}] to [{2}]
CLI-500217
TIBCO-BW- The minNodes configuration value for

ADMIN- an AppSpace has to be at least 1.
CLI-500218
TIBCO-BW- The minNodes configuration argument

ADMIN- is invalid. Valid argument are Integer
CLI-500219 values greater than 0.
TIBCO-BW- No matching AppSpace found

ADMIN-
CLI-500230

28
TIBCO-BW- Failed to restore AppSpace [{0}].

ADMIN-
CLI-500231
TIBCO-BW- Failed to restore AppSpace on [{0}]

CLI-500232
TIBCO-BW- Restore failed.

ADMIN-
CLI-500233
TIBCO-BW- Nothing to restore. Either agent [{0}]

ADMIN- does not exist or the agent is not part of
CLI-500244 the AppSpace [{1}]
TIBCO-BW- AppNode [{0}] not found in AppSpace

ADMIN- [{1}] in Domain [{2}]
CLI-500300
TIBCO-BW- AppNode [{0}] already exists in the

ADMIN- AppSpace [{1}] in Domain [{2}]
CLI-500301
TIBCO-BW- Failed to create AppNode [{0}] in

ADMIN- AppSpace [{1}] in Domain [{2}], {3}
CLI-500302
TIBCO-BW- Start AppNode [{0}] in Domain [{1}]

ADMIN- timed out
CLI-500303
TIBCO-BW- AppNode [{0}] in Domain [{1}] did not

ADMIN- start, {2}
CLI-500304

ADMIN- stop, {2}
CLI-500305
TIBCO-BW- Failed to delete AppNode [{0}] in

ADMIN- AppSpace [{1}] in Domain [{2}], {3}
CLI-500306
TIBCO-BW- Stop AppNode [{0}] in Domain [{1}]

ADMIN- timed out.
CLI-500307
TIBCO-BW- Failed to obtain thread dump, {0}

ADMIN-
CLI-500308

29

ADMIN- AppNode [{0}] in AppSpace [{1}] in
CLI-500309 Domain [{2}], {3}
TIBCO-BW- AppNode [{0}] in AppSpace [{1}] in

ADMIN- Domain [{2}] configured. Restart
CLI-500310 AppNode to apply changes.
TIBCO-BW- Configuration of AppNode [{0}] in

ADMIN- AppSpace [{1}], Domain [{2}] failed, {3}
CLI-500311
TIBCO-BW- Exported configuration from AppNode

ADMIN- [{0}] in AppSpace [{1}], Domain [{2}] to
CLI-500312 [{3}]
TIBCO-BW- Failed to obtain Agent log file, {0}

ADMIN-
CLI-500313
TIBCO-BW- Failed to enable console on AppNode

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

CLI-500315 {3}
TIBCO-BW- Failed to obtain AppNode log file, {0}

ADMIN-
CLI-500316
TIBCO-BW- Failed to disable debugger on AppNode

CLI-500317 {3}
TIBCO-BW- The value of the {0} argument has to be

ADMIN- a valid port number, valid range is
CLI-500331 [0-65335]
TIBCO-BW- No matching AppNode found

ADMIN-
CLI-500330
TIBCO-BW- The deployment artifact [{0}] supplied

ADMIN- does not exist
CLI-500400
TIBCO-BW- Application [{0}] is not present in the

CLI-500401

30
TIBCO-BW- Failed to deploy application from the

ADMIN- archive [{0}], {1}
CLI-500402
TIBCO-BW- Failed to undeploy application [{0}:{1}],

CLI-500403
TIBCO-BW- The application [{0}] is in undeployed

ADMIN- state
CLI-500404

ADMIN- is not valid
CLI-500405
TIBCO-BW- Failed to deploy hotfix to application

ADMIN- [{0}:{1}]
CLI-500406
TIBCO-BW- Version [{0}] is not valid. Only

ADMIN- <major>.<minor> version format is
CLI-500407 supported.
TIBCO-BW- Delete ear file [{0}] failed.

ADMIN-
CLI-500408
TIBCO-BW- Failed to undeploy hotfix to application

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

CLI-500409
TIBCO-BW- Failed to stop application [{0}:{1}].

CLI-500410
TIBCO-BW- Failed to export Profile [{0}] from the

ADMIN- Archive [{1}], {2}
CLI-500411

ADMIN- application [{0}:{1}] , {2}
CLI-500412
TIBCO-BW- Failed to obtain metrics. <CausedBy> {0}

ADMIN-
CLI-500413

31
TIBCO-BW- Deployed application from the archive

ADMIN- [{0}], however not all application
CLI-500414 instances started. <CausedBy> {1}
TIBCO-BW- Failed to configure application [{0}:{1}],

ADMIN- {2}
CLI-500415
TIBCO-BW- Failed to pause application [{0}:{1}].

ADMIN- <CauseBy> {2}
CLI-500416
TIBCO-BW- Failed to resume application [{0}:{1}].

ADMIN- <CauseBy> {2}
CLI-500417
TIBCO-BW- The directory [{0}] provided for option

ADMIN- [-dir] does not exist, provide a valid
CLI-500418 directory.
TIBCO-BW- Failed to start process starters of

ADMIN- application [{0}:{1}], <CausedBy> {2}.
CLI-500419
TIBCO-BW- Failed to stop process starters of

ADMIN- application [{0}:{1}], <CausedBy> {2}.
CLI-500420
TIBCO-BW- Profile file [{0}] does not exist

ADMIN-
CLI-500421
TIBCO-BW- No matching Application found

ADMIN-
CLI-500430
TIBCO-BW- Failed to upload the ear file [{0}].

ADMIN-
CLI-500431
TIBCO-BW- Failed to upload ear file [{0}] to some

ADMIN- machines in the domain.
CLI-500432
TIBCO-BW- Failed to upload archive [{0}],

ADMIN- <CausedBy> {1}.
CLI-500433
TIBCO-BW- Failed to delete archive [{0}],

ADMIN- <CausedBy> {1}.
CLI-500434

32
TIBCO-BW- Failed to delete ear file [{0}] from some

ADMIN- machines in the domain.
CLI-500435
TIBCO-BW- Failed to restore application [{0}] on

ADMIN- Agent [{1}], <CausedBy> {2}
CLI-500436
TIBCO-BW- Failed to restore application [{0}].

ADMIN-
CLI-500437
TIBCO-BW- The application [{0}] from archive [{1}]

ADMIN- has been deployed to these AppSpaces:
CLI-500438 {2}
TIBCO-BW- Applications are out of sync with the

ADMIN- archive they were deployed from, They
CLI-500439 have to be re-deployed to keep them in
sync.
TIBCO-BW- Failed to enable debug port on

ADMIN- AppNode[{0}] in AppSpace[{1}] in
CLI-500440 Domain[{2}], <CausedBy> {3}
TIBCO-BW- Name contains invalid characters and Use only valid characters in a name.
ADMIN- does not comply with naming
CLI-500501 conventions. Valid characters are upper
and lower case characters of the
alphabet as well as digits, '.' and '-'.
TIBCO-BW- Name length exceeds 100 characters Use less than 100 character for the
ADMIN- and it will be truncated to satisfy the name.
CLI-500502 length limit
TIBCO-BW- Name contains invalid characters that Use only valid characters for the name.
ADMIN- have been removed to comply with
CLI-500503 naming conventions.\nAllowed
characters are upper and lower case
characters of the alphabet as well as
digits, " ", "." and "-".\nName has been
changed to [{0}].
TIBCO-BW- Failed to register TEA Agent [{0}] with

ADMIN- TEA server, <CausedBy> {1}
CLI-500504
TIBCO-BW- Failed to disable auto registration with

CLI-500505

33
TIBCO-BW- Successfully disabled auto registration

ADMIN- with TEA server
CLI-500506
TIBCO-BW- Failed to enable auto registration with

CLI-500507
TIBCO-BW- Successfully enabled auto registration

ADMIN- with TEA server
CLI-500508
TIBCO-BW- No matching Archive found to restore

ADMIN-
CLI-500630
TIBCO-BW- BW6_INFR_UNEXP_EXCP_FORMAT = Internal product defect. Contact TIBCO

ADMIN- {0} support.
CLI-000001
Admin Error Codes

This section describes the error messages that can be reported by the entities associated with the
ActiveMatrix BusinessWorks Administrator.
TIBCO-BW- {0}
ADMIN-100001
TIBCO-BW- {0}
ADMIN-200001
TIBCO-BW- Registered TEA Agent [{0}] with TEA

ADMIN-300010 Server [{1}].
TIBCO-BW- Created the domain [{0}].

ADMIN-300100
TIBCO-BW- Added Machine [{0}] to Domain [{1}]

ADMIN-300101
TIBCO-BW- Removed Machine [{0}] from Domain

ADMIN-300102 [{1}]
TIBCO-BW- Deleted the Domain [{0}].

ADMIN-300103
TIBCO-BW- Registered BW Agent [{0}] to Domain

ADMIN-300104 [{1}]

34
TIBCO-BW- Unregistered BW Agent [{0}] from

ADMIN-300105 AppSpace [{1}] in Domain [{2}]
TIBCO-BW- Created AppSpace [{0}] in Domain [{1}].

ADMIN-300200
TIBCO-BW- Deleted AppSpace [{0}] in Domain [{1}].

ADMIN-300201
TIBCO-BW- Added Machine [{0}] to AppSpace [{1}]

ADMIN-300202 in Domain [{2}].
TIBCO-BW- Removed AppSpace [{0}] from BW

ADMIN-300203 Agent [{1}].
TIBCO-BW- Started AppSpace [{0}] in Domain [{1}].

ADMIN-300204
TIBCO-BW- Stopped AppSpace [{0}] in Domain

ADMIN-300205 [{1}].
TIBCO-BW- Expanded AppSpace [{0}] to BW Agent

ADMIN-300206 [{1}] in Domain [{2}].
TIBCO-BW- Deleted AppSpace [{0}] in Domain [{1}].

ADMIN-300207
TIBCO-BW- Updated connfiguration of AppSpace

ADMIN-300208 [{0}] in Domain [{1}].
TIBCO-BW- Created AppNode [{0}] in AppSpace

ADMIN-300300 [{1}] in Domain [{2}].
TIBCO-BW- Deleted AppNode [{0}] in AppSpace

ADMIN-300301 [{1}] in Domain [{2}].
TIBCO-BW- Started AppNode [{0}] in AppSpace

ADMIN-300302 [{1}] in Domain [{2}].
TIBCO-BW- Stopped AppNode [{0}] in Domain [{1}].

ADMIN-300303
TIBCO-BW- Enabled console on AppNode [{0}] in

TIBCO-BW- Disabled console on AppNode [{0}] in

TIBCO-BW- Disabled debugger on AppNode [{0}] in


35
TIBCO-BW- Retrieved BW Engine information from

ADMIN-300307 AppNode [{0}] in AppSpace [{1}] in
Domain [{2}]
TIBCO-BW- Deployed Application [{0}:{1}]

ADMIN-300400
TIBCO-BW- Undeployed Application [{0}:{1}]

ADMIN-300401
TIBCO-BW- Updated Application[{0}:{1}]

ADMIN-300402
TIBCO-BW- Deployed Application [{0}:{1}]

ADMIN-300403
TIBCO-BW- Undeployed Application [{0}:{1}]

ADMIN-300404
TIBCO-BW- Started Application [{0}:{1}]

ADMIN-300405
TIBCO-BW- Stopped Application [{0}:{1}]

ADMIN-300406
TIBCO-BW- Hotfix to application [{0}:{1}] is

ADMIN-300407 deployed.
TIBCO-BW- Hotfix to application [{0}:{1}] is

ADMIN-300408 undeployed.
TIBCO-BW- Configured application [{0}:{1}].

ADMIN-300409
TIBCO-BW- Paused Application [{0}:{1}]

ADMIN-300410
TIBCO-BW- Resumed Application [{0}:{1}]

ADMIN-300411
TIBCO-BW- Application [{0}:{1}] is already

ADMIN-300412 deployed. Use config command to make
any changes to the configuration.
TIBCO-BW- Enabled statistics collection for

ADMIN-300413 Application [{0}:{1}].
TIBCO-BW- Disabled statistics collection for

ADMIN-300414 Application [{0}:{1}].
TIBCO-BW- Uploaded Archive [{0}]

ADMIN-300500

36
TIBCO-BW- Removed Archive [{0}]

ADMIN-300501
TIBCO-BW- Archive [{0}] was created with

ADMIN-300510 BusinessStudio version: {1}
TIBCO-BW- Debug port enabled on AppNode[{0}]

ADMIN-300511 in AppSpace[{1}] in Domain [{2}]
TIBCO-BW- BW6_INFR_WARN_FORMAT = {0}

ADMIN-400000
TIBCO-BW- Name is longer than 100 characters.

ADMIN-400501 Truncating to meet length limit.
TIBCO-BW- Name includes invalid characters that

ADMIN-400502 have been removed to comply with
naming conventions.\nAllowed
characters are upper and lower case
characters of the alphabet as well as
digits, " ", "." and "-".\nName has been
changed to [{0}].
TIBCO-BW- BW6_INFR_ERROR_FORMAT = {0}

ADMIN-500000
TIBCO-BW- Failed to perform operation [{0}] on [{1}]

ADMIN-500001 in the Domain [{2}] due to an error in
initializing data manager, <CausedBy>
{3}
TIBCO-BW- Error while checking if the entity [{0}] is

ADMIN-500002 present in the Domain [{1}],
<CausedBy> {2}.
TIBCO-BW- Error invoking [{0}] method on the

ADMIN-500004 agent [{1}], <CausedBy> {2}
TIBCO-BW- Error while uploading the application

ADMIN-500005 archive file into data store, <CausedBy>
{0}
TIBCO-BW- Failed to initialize transport,

ADMIN-500006 <CausedBy> {0}
TIBCO-BW- Unsupported value for bw.admin.mode

ADMIN-500007 [{0}]
TIBCO-BW- Error in initializing data manager,


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

ADMIN-500009
TIBCO-BW- Invalid configuration content or format

ADMIN-500010 in file [{0}].
TIBCO-BW- Remote command execution failed,

TIBCO-BW- Configuration error in bwagent.ini file.

ADMIN-500012 Remote request timeout invalid.
TIBCO-BW- Port [{0}] is already taken by AppNode

ADMIN-500013 [{1}] belonging to AppSpace [{2}] in the
Domain [{3}]
TIBCO-BW- Port [{0}] is in use already.

ADMIN-500014
TIBCO-BW- Conflicting HTTP and OSGi console

ADMIN-500015 ports. Port [{0}]
TIBCO-BW- Configuration error in bwagent.ini file.

ADMIN-500016 Value given in
bw.agent.technology.as.remote.status.re
questTimeout is invalid.
TIBCO-BW- BW Agent is running, Stop the remote

ADMIN-500017 agent, delete all the files under domains
folder, and re-try.
TIBCO-BW- Domain [{0}] not found, check this and

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

ADMIN-500101 and re-try.
TIBCO-BW- Failed to create domain [{0}]

ADMIN-500102
TIBCO-BW- Domain home folder [{0}] does not

ADMIN-500103 exist. Verify if the folder exists and use
'/' character in the folder path.
TIBCO-BW- Machine [{0}] is not present in the

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

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

ADMIN-500106

38
TIBCO-BW- Machine [{0}] could not be removed

ADMIN-500107 from the Domain [{1}], {2}.
TIBCO-BW- Machine [{0}] is already part of Domain

ADMIN-500108 [{1}]
TIBCO-BW- The Domain [{0}] has AppSpaces

ADMIN-500109 associated with it. Use -force option to
override
TIBCO-BW- Agent [{0}] is already part of domain

ADMIN-500108 [{1}]
TIBCO-BW- Domain [{1}] could not be expanded to

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

ADMIN-500110 from the Agent [{0}], {2}.
TIBCO-BW- Agent [{0}] is not part of the Domain

ADMIN-500111 [{1}].
TIBCO-BW- Domain [{0}] not found, check this and

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

ADMIN-500113
TIBCO-BW- AppSpace [{0}] in Domain [{1}] not

ADMIN-500201 found.
TIBCO-BW- The AppSpace [{0}] is already present in

ADMIN-500202 the Domain [{1}].
TIBCO-BW- AppSpace [{0}] already exists with

ADMIN-500204 agent [{1}].

ADMIN-500205 not be deleted, {2}.
TIBCO-BW- Failed to register Agent [{0}] to

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

ADMIN-500207 AppSpace [{1}], {2}.
TIBCO-BW- Adding Machine to an AppSpace is not

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

ADMIN-500209 is not supported in 'local' admin mode.

39
TIBCO-BW- AppSpace [{0}] in Domain [{1}] did not

ADMIN-500210 start completely, {2}.

ADMIN-500211 not be stopped, {2}.

ADMIN-500212 not be deleted, {2}.

ADMIN-500213 have any AppNodes.
TIBCO-BW- Failed to deploy the {0} [{1}] from URL

ADMIN-500214 {2} into AppSpace {3}
TIBCO-BW- AppSpace handler [{0}] not found

ADMIN-500215
TIBCO-BW- AppSpace [{0}] has AppNodes

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

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

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

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

ADMIN-500220 BW Agents. Cannot be deleted. Use -
force option to override.
TIBCO-BW- AppSpace [{0}] could not be updated,

ADMIN-500221 {1}

ADMIN-500222 Domain [{1}] failed, {2}
TIBCO-BW- Configuration failed on one or more

ADMIN-500223 remote agents.
TIBCO-BW- AppSpace [{0}] has already reached its

ADMIN-500224 limit of applications [{1}]

40
TIBCO-BW- Only one version of Application [{0}]

ADMIN-500225 can be deployed in an AppSpace at the
same time.
TIBCO-BW- The registration of BW Agent to the

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

ADMIN-500227 AppSpace [{0}] failed. Cannot create
AppNodes in the AppSpace [{0}] on the
remote BW Agent [{1}]
TIBCO-BW- Invalid value supplied as minNodes.

ADMIN-500228 minNodes must be an Integer greater
than 0.
TIBCO-BW- AppSpace [{0}] is expanded to the BW

ADMIN-500229 Agent [{1}] on the file system, However
the agent failed to update the status in
the datastore. <CausedBy> {2}

one or multiple applications failed to
deploy into this AppSpace on the
remote machine, check the status of the
applications in this AppSpace for
details. <CausedBy> {2}

one or multiple applications failed to
deploy into this AppSpace on the
remote machine, check the status of the
applications in this AppSpace for
details.
TIBCO-BW- Errors while deleting AppNodes and/or

ADMIN-500232 AppSpace instances on local and/or
remote machines.
TIBCO-BW- Cannot find AppSpace specific TRA file Make sure the file is at the expected
ADMIN-500233 at [{0}] location and the bwagent/bwadmin
programs have read access to it
TIBCO-BW- Failed to obtain AppSpace TRA file

ADMIN-500234 from [{0}], <CausedBy> [{1}]
TIBCO-BW- Failed to write AppSpace TRA file [{0}],

ADMIN-500235 <CausedBy> [{1}]

41
TIBCO-BW- The AppNode [{0}] does not exist in

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

ADMIN-500301 AppSpace [{1}] Domain [{2}].

ADMIN-500302 AppSpace [{1}] in Domain [{2}], {3}
TIBCO-BW- Start of AppNode [{0}] in AppSpace

ADMIN-500303 [{1}] in Domain [{2}] timed out.

ADMIN-500304 Domain [{2}] did not start, <CausedBy>
{3}

ADMIN-500305 stop, <CausedBy> {2}

ADMIN-500306 AppSpace [{1}] in Domain [{2}],
<CausedBy> {3}
TIBCO-BW- Stop AppNode [{0}] in Domain [{1}]

ADMIN-500307 timed out.
TIBCO-BW- Reached wrong AppNode [{0}] in

ADMIN-500308 AppSpace [{1}] in Domain [{2}].
Expected was [{3}].
TIBCO-BW- Failed to enable console on AppNode

ADMIN-500309 [{0}] in AppSpace [{1}] in Domain [{2}],
<CausedBy> {3}
TIBCO-BW- Failed to disable console on AppNode

<CausedBy> {3}
TIBCO-BW- Failed to update AppNode [{0}] in data

ADMIN-500311 store, <CausedBy> {1}
TIBCO-BW- Failed to configure AppNode [{0}],

TIBCO-BW- AppNode [{0}] is not running or cannot

ADMIN-500313 be contacted
TIBCO-BW- The AppNode [{0}] is still in [{1}] state.

ADMIN-500314 Please stop the AppNode first or use
the -force option.

42
TIBCO-BW- No AppNodes are present in the

ADMIN-500315 AppSpace [{0}] in the Domain [{0}].
TIBCO-BW- AppNode [{0}] log file does not exist or

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

ADMIN-500317 not be read
TIBCO-BW- The AppNode [{0}] is running. Stop the

ADMIN-500318 AppNode first and try again.
TIBCO-BW- Port is taken, <CausedBy> {0}

ADMIN-500319
TIBCO-BW- AppNode [{0}] encountered an Internal Please check AppNode log file for
ADMIN-500320 Server Error. Please check the log file of details.
the AppNode for details.
TIBCO-BW- Failed to disable debugger on AppNode

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

<CausedBy> {3}
TIBCO-BW- Cannot find AppNode specific TRA file Make sure the file is at the expected
ADMIN-500323 at [{0}] location and the bwagent/bwadmin
programs have read access to it
TIBCO-BW- Failed to obtain AppNode TRA file

ADMIN-500324 from [{0}], <CausedBy> [{1}]
TIBCO-BW- Failed to write AppNode TRA file [{0}],

ADMIN-500325 <CausedBy> [{1}]
TIBCO-BW- The supplied deployment artifact [{0}]

ADMIN-500400 does not exist.
TIBCO-BW- Application [{0}] not found in the

ADMIN-500401 Domain [{1}] {2}
TIBCO-BW- Failed to deploy application [{0}:{1}],


43
TIBCO-BW- BW6_ADMIN_APP_UNDEPLOYMEN
ADMIN-500403 T_FAILED = Failed to undeploy
application [{0}:{1}], <CausedBy> {2}
TIBCO-BW- The Application [{0}] is in undeployed

ADMIN-500404 state.

ADMIN-500405 is not valid
TIBCO-BW- Failed to deploy hotfix to application

ADMIN-500406 [{0}:{1}].
TIBCO-BW- Version [{0}] is not valid. Only

ADMIN-500407 <major>.<minor> version format is
supported.
TIBCO-BW- Failed to undeploy hotfix to application

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

TIBCO-BW- Failed to stop application [{0}],

TIBCO-BW- Deployment of [{0}] completed. The

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

ADMIN-500412 start of the application or library in the
running AppNodes failed for some
AppNodes. Please check log files for
more details.
TIBCO-BW- Failed to update the application [{0}] in

ADMIN-500413 the data store, <CausedBy> {1}
TIBCO-BW- Failed to upload to one or multiple

ADMIN-500415 remote machines.
TIBCO-BW- Error encountered installing {0} [{1}]

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

ADMIN-500417 AppNode [{1}]
TIBCO-BW- Application archive file [{0}] not found

ADMIN-500418 in the domain [{1}]

44
TIBCO-BW- Application archive file [{0}] could not

ADMIN-500419 be deleted from data store.
TIBCO-BW- Name includes only invalid characters

ADMIN-500420 and does not comply with naming
conventions. Allowed characters are
upper and lower case characters of the
TIBCO-BW- Configuration of Application [{0}]

ADMIN-500421 failed, <CausedBy> {1}
TIBCO-BW- Failed to delete Application archive file

ADMIN-500422 on one or multiple remote machines.
TIBCO-BW- BW6_ADMIN_APP_ALRDY_PRSNT
ADMIN-500423 =Application [{0}] already exists in the
domain [{1}] and it is deployed from the
archive file [{2}]
TIBCO-BW- Failed to read profile from [{0}]

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

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

ADMIN-500426 Archive {1}.
TIBCO-BW- Failed to export configuration of

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

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

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

ADMIN-500430 on AppNode [{2}] AppSpace [{3}]
Domain [{4}] is not found.
TIBCO-BW- Error encountered pausing {0} [{1}] on

TIBCO-BW- Error encountered resuming {0} [{1}] on


45
TIBCO-BW- Pausing of [{0}] completed. Please check

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

ADMIN-500434 log files for more details.
TIBCO-BW- Failed to pause Application [{0}],

TIBCO-BW- Failed to resume Application [{0}],

TIBCO-BW- Failed to start in one or more

ADMIN-500437 AppNodes.
TIBCO-BW- Failed to restore AppInstance

ADMIN-500438 configuration, <CausedBy> {0}
TIBCO-BW- Error encountered starting process

ADMIN-500457 starters of {0} [{1}] [{2}] on AppNode
[{3}]
TIBCO-BW- Error encountered stopping process

ADMIN-500439 starters of {0} [{1}] [{2}] on AppNode
[{3}]
TIBCO-BW- Starting process starters of [{0}]

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

ADMIN-500441 completed. Please check log files for
more details.
TIBCO-BW- Failed to start process starters of

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

ADMIN-500443 Application [{0}], <CausedBy> {1}
TIBCO-BW- Failed to start Application in AppNode

ADMIN-500444 [{0}]. Check the AppNode log files for
messages starting with TIBCO-THOR-
FRWK, TIBCO-BW-FRWK, or TIBCO-
BW-SR-FRWK for details. Application
State [{1}], reason : {2}
TIBCO-BW- AppSpace [{0}] is not found. Create the

ADMIN-500445 AppSpace first and re-try.

46
TIBCO-BW- The application [{0}] from archive [{1}]

ADMIN-500446 has been deployed to these AppSpaces:
{2}
TIBCO-BW- Archive [{0}] is already present in the

ADMIN-500447 domain, use -replace option to replace
the existing archive.
TIBCO-BW- Applications are out of sync with the

ADMIN-500448 archive they were deployed from, They
have to be re-deployed to keep them in
sync.
TIBCO-BW- The archive [{0}] in the domain is

ADMIN-500449 replaced, Deploy the application again
to apply the latest version.
TIBCO-BW- Archive [{0}] has been deployed to the

ADMIN-500450 AppSpaces: {1}
TIBCO-BW- Port is taken by AppNode[{0}] in

ADMIN-500451 AppSpace[{1}] in Domain[{2}]
TIBCO-BW- Failed to obtain bwagents of the

ADMIN-500452 machine [{0}].
TIBCO-BW- http interface and port of bwagent [{0}]

ADMIN-500453 conflicted with the supplied interface
and port
TIBCO-BW- TEA interface and port of the bwagent

ADMIN-500454 [{0}] conflicted with the supplied
interface and port
TIBCO-BW- Interface and the port of listen URL of

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

ADMIN-500456 the BW Agent [{0}] conflict with the
supplied interface and port
TIBCO-BW- Archive was created with a newer

ADMIN-500460 version of the product [{0}] and cannot
be installed into the current version
[{1}]. Upgrade the product and try again
TIBCO-BW- Invalid archive for this product version.

ADMIN-500461 Only archives with single modules are
supported.

47
TIBCO-BW- Archive was created with different

ADMIN-500462 BusinessWorks Edition and cannot be
installed in current product. Upgrade
the product and try again.
TIBCO-BW- Host and port combination [{0}:{1}] is

ADMIN-500463 already in use.
TIBCO-BW- Invalid interface name. No IP address

ADMIN-500464 was found for host [{0}]
TIBCO-BW- Failed to enable statistics collection for Please check AppNode log file for
ADMIN-500465 Application [{0}:{1}], {2} details.
TIBCO-BW- Failed to disable statistics collection for Please check AppNode log file for
ADMIN-500466 Application [{0}:{1}], {2} details.
TIBCO-BW- Invalid profile file from [{0}]. Please check profile file. Make sure
ADMIN-500467 profile properties match the application
properties.
TIBCO-BW- Invalid property [{0}] is unset. Please check the properties in

ADMIN-500469 configuration file to connect Mashery.
TIBCO-BW- Unable to connect to Mashery[{0}] Please make sure your mashery

ADMIN-500470 configuration file is in the bin folder.
TIBCO-BW- Mashery configuration file does not Please make sure your mashery
ADMIN-500471 exist. configuration file is in the bin folder.
TIBCO-BW- Failed to register TEA Agent [{0}] with

ADMIN-500504 TEA server [{1}], {2}
TIBCO-BW- BW6_INFR_UNEXP_EXCP_FORMAT =
ADMIN-000001 {0}
TIBCO-BW- Failed to create the application [{0}] in

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

ADMIN-000101 data store
TIBCO-BW- Internal error: {0}

ADMIN-000200

48
Engine Error Codes

This section describes the error messages that can be reported by the Engine layers.
TIBCO-BW- {0} This is an internal product error.

CORE-000001 Contact TIBCO Support.
TIBCO-BW- BWActivityManager Registration Error. This is an internal product error.

CORE-000010 The BWActivityManager argument Contact TIBCO Support.
provided to the BW Engine is null.
TIBCO-BW- Failed to initialize BW Engine. The BW This is an internal product error.

CORE-000012 Engine was initialized without a logger Contact TIBCO Support.
object.
TIBCO-BW- Failed to initialize BW Engine. While This is an internal product error.

CORE-000018 registering BWActivtyBridge the BW Contact TIBCO Support.
Engine encountered exception [{0}]
TIBCO-BW- Failed to initialize BW Engine. The This is an internal product error.

CORE-000020 BWActivityManager was not registered Contact TIBCO Support.
correctly with the BW Engine.

CORE-000022 Crypto service was not registered Contact TIBCO Support.
correctly with the BW Engine.

CORE-000024 Custom XPath Function Manager Contact TIBCO Support.
service was not registered correctly
with the BW Engine.
TIBCO-BW- Failed to enable BW Debugger. The BW This is an internal product error.

CORE-000026 Engine has not been initialized. Contact TIBCO Support.
TIBCO-BW- The BW Debugger is already enabled This is an internal product error.

CORE-000028 state and it can not be enabled again. Contact TIBCO Support.
TIBCO-BW- Unable to disable BW Debugger. The This is an internal product error.

CORE-000030 BW Engine has not been initialized. Contact TIBCO Support.
TIBCO-BW- Attempt to disable the BW Debugger This is an internal product error.

CORE-000032 encountered exception [{0}] Contact TIBCO Support.
TIBCO-BW- Unable to enable BW Event Publisher. This is an internal product error.

CORE-000034 The BW Engine has not been initialized. Contact TIBCO Support.
TIBCO-BW- BW Engine configuration data does not This is an internal product error.
CORE-000036 contain AppNode name. Contact TIBCO Support.
CORE-000038 contain AppSpace name. Contact TIBCO Support.

49
CORE-000040 contain Domain name. Contact TIBCO Support.
TIBCO-BW- The operation [{0}] is not supported for This is an internal product error.
CORE-000052 the BX Non-Executable Module. Contact TIBCO Support.
ModuleName={0}, ModuleVersion={1}
CORE-000054 the BX Executable Module. Contact TIBCO Support.
ModuleName={1}, ModuleVersion={2}
CORE-000056 the BW Job Shared Variable. Contact TIBCO Support.
TIBCO-BW- Unable to obtain EngineManagement. This is an internal product error.

CORE-000057 The BW Engine has not been initialized. Contact TIBCO Support.
TIBCO-BW- Unable to obtain EngineManagement This is an internal product error.

CORE-000058 due to exception [{0}] Contact TIBCO Support.
TIBCO-BW- The BX operation [{0}] failed due to This is an internal product error.
CORE-000059 exception [{1}]. Contact TIBCO Support.
TIBCO-BW- Invalid 'BWModuleHandle'. The BW This is an internal product error.

CORE-000102 module represented by this handle has Contact TIBCO Support.
been already un-installed or the handle
has been already destroyed.
TIBCO-BW- Unable to obtain process templates This is an internal product error.

CORE-000104 referenced by BW Module, the BW Contact TIBCO Support.
Engine encountered exception.
ModuleName[{0}], ModuleVersion[{1}],
Exception[{2}].
TIBCO-BW- Unable to obtain GenXDM This is an internal product error.

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

Module [{0}]. The operation [{1}]
returned exception [{2}]

Module [{0}:{1}] due to exception [{2}]
TIBCO-BW- Unable to obtain "BundleContext" for This is an internal product error.

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

50
TIBCO-BW- Unable to obtain "BundleContext" for This is an internal product error.

CORE-000124 BW module [{0}:{1}] due to exception Contact TIBCO Support.
[{2}]
TIBCO-BW- Unable to obtain ServiceReference for This is an internal product error.

CORE-000126 the cache service [{0}]. The operation Contact TIBCO Support.
"BundleContext.getServiceReference"
for BW module [{1}:{2}] returned "null".

CORE-000128 the cache service [{0}]. The operation Contact TIBCO Support.
"BundleContext.getServiceReference"
for BW module [{1}:{2}] returned
exception [{3}]
TIBCO-BW- Unable to obtain XSD cache service [{0}] This is an internal product error.
CORE-000130 for the BW module [{1}:{2}]. The Contact TIBCO Support.
operation [{3}] returned "null".
TIBCO-BW- Unable to obtain XSD cache service [{0}] This is an internal product error.
CORE-000131 for the BW module [{1}:{2}]. The Contact TIBCO Support.
operation [{3}] returned exception [{4}]
TIBCO-BW- Unable to obtain WSDL cache service This is an internal product error.
CORE-000132 [{0}] for the BW module [{1}:{2}]. The Contact TIBCO Support.
operation [{3}] returned "null".
TIBCO-BW- Unable to obtain WSDL cache service This is an internal product error.
CORE-000133 [{0}] for the BW module [{1}:{2}]. The Contact TIBCO Support.
operation [{3}] returned exception [{4}]
TIBCO-BW- Unable to obtain WSDL ModuleCache This is an internal product error.

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

CORE-000135 from the WSDLCacheService for the Contact TIBCO Support.
WSDL namespace [{0}], locationURI
{5}]. Encountered exception [{6}]
TIBCO-BW- Unable to obtain BxWSDLResolver for This is an internal product error.

CORE-000136 the WSDL namespace [{0}], Location Contact TIBCO Support.
{5}] due to exception [{6}]

51
TIBCO-BW- Unable to obtain GenXDM WSDL This is an internal product error.

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

CORE-000138 Module for the WSDL namespace [ {0} ] Contact TIBCO Support.
[{1}:{2}], DeploymentUnit [{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.
TIBCO-BW- Unable to obtain WSDL Message details This is an internal product error.
CORE-000140 from the GenXDM WSDL Module for Contact TIBCO Support.
the WSDL namespace [ {0} ] that is
referenced in the BW Module [{1}:{2}]
due to exception [{3}].
TIBCO-BW- Unable to obtain WSDL Definition This is an internal product error.

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

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

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

52
TIBCO-BW- Invalid BWBxWSDLResolver. The This is an internal product error.

CORE-000152 instance of this BWBxWSDLResolver Contact TIBCO Support.
has been already released.
TIBCO-BW- The initial value mode [{0}] specified for This is an internal product error.
CORE-000160 the {1} [{2}] in BW Module [{3}:{4}], Contact TIBCO Support.
DeploymentUnit[{5}:{6}] is invalid.
TIBCO-BW- The QName value [{0}] specified for the This is an internal product error.
CORE-000162 {1} [{2}] in BW Module [{3}] is invalid or Contact TIBCO Support.
malformed.
TIBCO-BW- Invalid 'BWComponentHandle'. The This is an internal product error.

CORE-000202 BW Component represented by this Contact TIBCO Support.
handle has been already un-installed or
the handle has been already destroyed.
TIBCO-BW- Unable to create This is an internal product error.

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

BW Component due to invalid BW
Process ServiceName [{0}].
ComponentName={1},
ComponentVersion={2}
TIBCO-BW- Error occurred while creating This is an internal product error.

service [{0}], BW Component [{1}],
Application [{2}:{3}]. Exception[{4}].

service [{0}], BW Component [{1}]. The
operation
"BxSystem.getInterfaceProvider"
returned "null".
TIBCO-BW- Received unexpected exception [{0}] This is an internal product error.

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

CORE-000214 operation "{0}" returned "null" Contact TIBCO Support.

53
TIBCO-BW- Unable to obtain "BundleContext" due This is an internal product error.

CORE-000216 to exception [{0}] Contact TIBCO Support.

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

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

CORE-000224 from the GenXDM WSDL Module for
with the BW Component [{1}],
Application[{2}:{3}]. The operation "{4}"
returned exception [{5}].
with the BW Component [{1}],
Application[{2}:{3}]. The operation "{4}"
returned null.
TIBCO-BW- Unable to obtain ServiceReference for

CORE-000228 the cache service [{0}]. The operation
"{1}" returned "null".

CORE-000230 the cache service [{0}] due to exception Contact TIBCO Support.
[{1}]
TIBCO-BW- Unable to obtain cache service [{0}]. The This is an internal product error.
CORE-000231 operation "{1}" returned "null". Contact TIBCO Support.
TIBCO-BW- Unable to obtain cache service [{0}]. The This is an internal product error.
CORE-000132 operation "{1}" returned exception [{2}]. Contact TIBCO Support.
TIBCO-BW- Unable to construct PortType details This is an internal product error.

CORE-000232 from the GenXDM WSDL Interface for Contact TIBCO Support.
the WSDL namespace [{0}] that is
associated with the BW Component
[{1}] due to exception [{2}].
TIBCO-BW- Unable to obtain ModuleCache for the This is an internal product error.
CORE-000234 BW Component [{0}]. The operation Contact TIBCO Support.
"{1}" returned "null".

54
TIBCO-BW- Failed obtain value for the component BW framework layer encountered
CORE-000235 level property [{0}], BW Component errors when accessing the component
[{1}], Application [{2}:{3}]. Encountered level property. Contact TIBCO Support.
exception [{4}]
TIBCO-BW- Invalid 'BWApplicationHandle'. The This is an internal product error.

CORE-000302 BW Application represented by this Contact TIBCO Support.
handle has been already un-installed or
the handle has been already destroyed.

CORE-000304 'BWApplicationHandle' due to invalid Contact TIBCO Support.
BWComponentHandle list. The
argument of type
'List<BWComponentHandle$gt;' must
contain at least one
BWComponentHandle.

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

CORE-000308 'BWApplicationHandle' for the BW Contact TIBCO Support.
Application [{0}].
TIBCO-BW- Error occurred when accessing the This is an internal product error.
CORE-000402 ProcessStarter activity [{0}] in process Contact TIBCO Support.
[{1}], module [{2}] from the
BWActivityManager. Error={3}.
TIBCO-BW- Error occurred when configuring the This is an internal product error.
CORE-000404 ProcessStarter activity [{0}] in process Contact TIBCO Support.
[{1}], module [{2}].
TIBCO-BW- Unable to configure ProcessStarter This is an internal product error.

CORE-000406 activity [{0}] in process [{1}], module Contact TIBCO Support.
[{2}] due to crypto service access error.
TIBCO-BW- HotUpdate operation not supported for This error can occur if the BW process
CORE-000408 ProcessStarter activity [{0}] in process file has been corrupted.
[{1}], module [{2}]. The ProcessStarter
already exists for activitId [{3}].

55
TIBCO-BW- Error occurred when accessing the This is an internal product error.
CORE-000502 SignalIn activity [{0}] in process [{1}], Contact TIBCO Support.
module [{2}] from the
BWActivityManager. Error={3}.
CORE-000504 SignalIn activity [{0}] in process [{1}], Contact TIBCO Support.
module [{2}].
TIBCO-BW- Unable to configure SignalIn activity This is an internal product error.

CORE-000506 [{0}] in process [{1}], module [{2}] due to Contact TIBCO Support.
crypto service access error.
TIBCO-BW- HotUpdate operation not supported for This error can occur if the BW process
CORE-000508 SignalIn activity [{0}] in process [{1}], file has been corrupted.
module [{2}]. The SignalIn already
exists for activitId [{3}].
TIBCO-BW- Failed to obtain activity [{0}] in process This is an internal product error.
CORE-000602 [{1}], module [{2}] from the Contact TIBCO Support.
BWActivityManager due to exception
[{3}]. ActivityId [{4}].
[{2}]
TIBCO-BW- Unable to configure activity [{0}] in This is an internal product error.

CORE-000606 process [{1}], module [{2}] due to crypto Contact TIBCO Support.
service access error.
TIBCO-BW- Unable to execute [{0}] operation for an This is an internal product error.
CORE-000608 activity. Failed to lookup activity [{1}] in Contact TIBCO Support.
process [{2}], module [{3}] from the
BWActivityManager. ActivityId [{4}].
TIBCO-BW- HotUpdate operation not supported for This is an internal product error.
[{2}]. The activity already exists for
activitId [{3}].
TIBCO-BW- {0} This is a trace message and resolution is

CORE-100001 not applicable.
TIBCO-BW- Activated Application[{0}], This is a trace message and resolution is

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

CORE-100003 in AppNode[{2}], ActivationAlias[{3}]. not applicable.

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

CORE-200001 is not applicable.

TIBCO-BW- Initialized BW Engine successfully [{0}, This is a debug message and it indicates
CORE-202002 {1}, {2}]. the BW Engine was initialized
successfully. Resolution is not
applicable for this message.
TIBCO-BW- Stopped(Graceful) BW Engine This is a debug message and it indicates

CORE-202052 successfully. the BW Engine was stopped gracefully.
Resolution is not applicable for this
message.
TIBCO-BW- Stopped(Forceful) BW Engine This is a debug message and it indicates

CORE-202053 successfully. the BW Engine was stopped forcefully
before completing all application jobs.
message.
TIBCO-BW- BW Engine is already in stopped state. This is a debug message and resolution
TIBCO-BW- Enabled BW Debugger in the BW This is a debug message and resolution

CORE-202055 Engine. is not applicable.
TIBCO-BW- Disabled BW Debugger in the BW This is a debug message and resolution

CORE-202056 Engine. is not applicable.

TIBCO-BW- INITIATE: install BW Module [{0}:{1}], This is a debug message and it indicates
CORE-202101 DeploymentUnit [{2}:{3}]. the BW Engine is starting to create the
BW Module. Resolution is not
TIBCO-BW- Installed BW Module [{0}:{1}], This is a debug message and it indicates

CORE-202102 DeploymentUnit [{2}:{3}]. the BW Engine has completed creating
the BW Module. Resolution is not
TIBCO-BW- INITIATE: release-resources for BW This is a debug message and it indicates

CORE-202103 Module [{0}:{1}], DeploymentUnit [{2}: the BW Engine is starting to release the
{3}]. BW Module resources. Resolution is not

57
TIBCO-BW- Released-resources for BW Module [{0}: This is a debug message and it indicates
CORE-202104 {1}], DeploymentUnit [{2}:{3}]. the BW Engine has completed releasing
the BW Module resources. Resolution is
not applicable for this message.
TIBCO-BW- INITIATE: undeploy BW Module [{0}: This is a debug message and it indicates
CORE-202105 {1}], DeploymentUnit [{2}:{3}]. the BW Engine is starting to un-
deploying the BW Module. Resolution
is not applicable for this message.
TIBCO-BW- Undeployed BW Module [{0}:{1}], This is a debug message and it indicates

CORE-202106 DeploymentUnit [{2}:{3}]. the BW Engine has completed un-
deploying the BW Module. Resolution
is not applicable for this message.

TIBCO-BW- INITIATE: install BW Component [{0}], This is a debug message and it indicates
CORE-202201 Application[{1}:{2}]. the BW Engine is starting to create the
BW Component. Resolution is not
TIBCO-BW- Installed BW Component [{0}], This is a debug message and it indicates

CORE-202202 Application[{1}:{2}]. the BW Engine has completed creating
the BW Component. Resolution is not
TIBCO-BW- INITIATE: initialize BW Component This is a debug message and it indicates

CORE-202203 [{0}], Application[{1}:{2}]. the BW Engine is starting to initialize
the BW Component. Resolution is not
TIBCO-BW- Initialized BW Component [{0}], This is a debug message and it indicates

CORE-202204 Application[{1}:{2}]. the BW Engine has completed
initializing the BW Component.
message.
TIBCO-BW- INITIATE: start BW Component [{0}]. This is a debug message and it indicates
CORE-202205 the BW Engine is starting the BW
Component. Resolution is not
TIBCO-BW- Started BW Component [{0}]. This is a debug message and it indicates

CORE-202206 the BW Engine has stated the BW
Component. Resolution is not
TIBCO-BW- INITIATE: stop(Forceful) BW This is a debug message and resolution

CORE-202207 Component [{0}]. is not applicable.

58
TIBCO-BW- Stopped(Forceful) BW Component [{0}]. This is a debug message and resolution

TIBCO-BW- INITIATE: destroy BW Component This is a debug message and resolution

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

TIBCO-BW- INITIATE: release-resources for BW This is a debug message and resolution

CORE-202211 Component [{0}], Application[{1}:{2}]. is not applicable.
TIBCO-BW- Released-resources for BW Component This is a debug message and resolution

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

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

CORE-202214 Application[{1}:{2}]. is not applicable.
TIBCO-BW- INITIATE: start ServiceBinding(s) or This is a debug message and resolution

CORE-202215 ProcessStarter for BW Component [{0}], is not applicable.
Application[{1}:{2}].
TIBCO-BW- Started ServiceBinding(s) or This is a debug message and resolution

TIBCO-BW- INITIATE: stop ServiceBinding(s) or This is a debug message and resolution

TIBCO-BW- Stopped ServiceBinding(s) or This is a debug message and resolution

TIBCO-BW- INITIATE: start ServiceBinding [{0}] for This is a debug message and resolution
CORE-202219 BW Component [{1}], Application [{2}: is not applicable.
{3}].
TIBCO-BW- Started ServiceBinding [{0}] for BW This is a debug message and resolution
CORE-202220 Component [{1}], Application [{2}:{3}]. is not applicable.
TIBCO-BW- INITIATE: stop ServiceBinding [{0}] for This is a debug message and resolution
CORE-202221 BW Component [{1}], Application [{2}: is not applicable.
{3}].
TIBCO-BW- Stopped ServiceBinding [{0}] for BW This is a debug message and resolution
CORE-202222 Component [{1}], Application [{2}:{3}]. is not applicable.

59
TIBCO-BW- Ready to uninstall BW Component [{0}], This is a debug message and resolution
CORE-202223 Application [{1}]. is not applicable.
TIBCO-BW- Created This is a debug message and resolution

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

TIBCO-BW- INITIATE: create BW Application [{0}] This is a debug message and resolution
CORE-202301 handle. is not applicable.
TIBCO-BW- Created BW Application [{0}] handle. This is a debug message and resolution
TIBCO-BW- INITIATE: start BW Application [{0}]. This is a debug message and resolution
TIBCO-BW- Started BW Application [{0}]. This is a debug message and resolution

TIBCO-BW- INITIATE: stop(Graceful) for BW This is a debug message and resolution

TIBCO-BW- Stopped(Graceful) BW Application This is a debug message and resolution

TIBCO-BW- INITIATE: stop(Forceful) BW This is a debug message and resolution

TIBCO-BW- Stopped(Forceful) BW Application [{0}]. This is a debug message and resolution

TIBCO-BW- INITIATE: start all ProcessStarters and This is a debug message and resolution
CORE-202313 ServiceBindings for BW Application is not applicable.
[{0}:{1}].
TIBCO-BW- Started all ProcessStarters and This is a debug message and resolution
[{0}:{1}].
TIBCO-BW- INITIATE: stop all ProcessStarters and This is a debug message and resolution
[{0}:{1}].
TIBCO-BW- Stopped all ProcessStarters and This is a debug message and resolution
[{0}:{1}].

60
TIBCO-BW- INITIATE: pause BW Application [{0}]. This is a debug message and resolution
TIBCO-BW- Paused BW Application [{0}]. This is a debug message and resolution

TIBCO-BW- INITIATE: resume BW Application This is a debug message and resolution

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

TIBCO-BW- INITIATE: initialize ProcessStarter This is a debug message and resolution

CORE-202401 activity [{0}] in Process[{1}], Module is not applicable.
[{2}], DeploymentUnit [{3}:{4}].
TIBCO-BW- Initialized ProcessStarter activity [{0}] in This is a debug message and resolution
CORE-202402 Process[{1}], Module [{2}], is not applicable.
DeploymentUnit [{3}:{4}].
TIBCO-BW- INITIATE: start ProcessStarter activity This is a debug message and resolution
CORE-202403 [{0}] in Process[{1}], Module [{2}], is not applicable.
TIBCO-BW- Started ProcessStarter activity [{0}] in This is a debug message and resolution
TIBCO-BW- INITIATE: stop ProcessStarter activity This is a debug message and resolution
TIBCO-BW- Stopped ProcessStarter activity [{0}] in This is a debug message and resolution
TIBCO-BW- INITIATE: destroy ProcessStarter This is a debug message and resolution

TIBCO-BW- Destroyed ProcessStarter activity [{0}] This is a debug message and resolution
CORE-202408 in Process[{1}], Module [{2}], is not applicable.
TIBCO-BW- INITIATE: release ProcessStarter This is a debug message and resolution

TIBCO-BW- Released ProcessStarter activity [{0}] in This is a debug message and resolution

61

TIBCO-BW- INITIATE: initialize SignalIn activity This is a debug message and resolution
TIBCO-BW- Initialized SignalIn activity [{0}] in This is a debug message and resolution
TIBCO-BW- INITIATE: start SignalIn [{0}] activity in This is a debug message and resolution
TIBCO-BW- Started SignalIn [{0}] activity in This is a debug message and resolution
TIBCO-BW- INITIATE: stop SignalIn activity [{0}] in This is a debug message and resolution
TIBCO-BW- Stopped SignalIn activity [{0}] in This is a debug message and resolution
TIBCO-BW- INITIATE: destroy SignalIn activity [{0}] This is a debug message and resolution
CORE-202507 in Process[{1}], Module [{2}], is not applicable.
TIBCO-BW- Destroyed SignalIn activity [{0}] in This is a debug message and resolution
TIBCO-BW- INITIATE: release ProcessStarter This is a debug message and resolution

TIBCO-BW- Released ProcessStarter activity [{0}] in This is a debug message and resolution

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

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













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

63
TIBCO-BW- Activity output data validation details. This is a debug message and resolution
CORE-206612 ActivityName={0}, ProcessName={1}, is not applicable.
Module={2}:{3}, Schema={4}, Data={5}
TIBCO-BW- The BusinessWorks Event Publisher is This message indicates the BW Engine
CORE-300002 disabled. is configured to disable the event
publisher; therefore there will be no
event published by the BW Engine.
TIBCO-BW- {0} This is a warning message and it

CORE-400001 highlights situations that may affect the
application execution.
TIBCO-BW- Activity resource release operation The activity resource release operation
CORE-400004 [com.tibco.bw.runtime.ActivityResourc must not raise an exception. This is
e.release()] called at the end of the considered to be an activity resource
execution of the BW group or BW implementation error.
Process instance encountered error. The
Activity resource release operation
[{0}.release(boolean)] raised exception:
{1}
TIBCO-BW- CatchAll fault details formating issue. Received unexpected data when
CORE-400006 Expected [{0}], but received [{1}] formating the CatchAll fault details.
TIBCO-BW- The BW process [{0}] instance cancelled, This message is generated when the
CORE-400010 JobId [{1}], ProcessInstanceId [{2}], BusinessWorks Engine cancels a process
ParentProcessInstanceId [{3}], Module instance execution. A process instance
[{4}:{5}], Application [{6}:{7}]. can be canceled when one of the
following occurs: the invoke activity (in
the parent process) that called this
process instance timed out, the
application is stopped non gracefully or
the process instance is explicitly
canceled through an internal
management interface.
TIBCO-BW- Unable to close the file [{0}] configured The BW Engine was unable to close the
CORE-400102 for the initial value of the {1} [{2}] in the file that contains initial values for the
BW Module [{3}:{4}], DeploymentUnit Module or Job Shared variables. This
[{5}:{6}]; encountered exception [{7}]. error occurred when attempting to close
the file, but after reading the file
contents.
TIBCO-BW- The BW Component [{0}:{1}] is already The BW framework is attempting to

CORE-400202 in destroyed state. destroy the BW Component that is
already in destroyed state. Resolution is
not applicable.

64
TIBCO-BW- {0} This error code is used to log BW

CORE-500001 Engine errors. For more details, refer to
the additional exception message or the
"CausedBy" statements reported as part
of this error message.
TIBCO-BW- Failed to initialize BW Engine due to The BW Engine did not successfully
CORE-500010 exception [{0}] initialize, and this could be due to many
reasons. For more details, refer to the
additional exception message or the
TIBCO-BW- Failed to initialize BW Engine due to The BW Engine was not able to
CORE-500011 database access error establish connection or access the
engine database instance. Ensure the
database driver, connection, user name
and password details are correctly
specified. Also ensure database instance
has been started.
TIBCO-BW- Failed to initialize BW Engine due to The BW Engine failed to establish

CORE-500012 engine group connection provider error connection with the engine group
connection provider. Ensure the group
connection provider entity
(bw.engine.groupProvider.technology)
specified in the BW AppNode or BW
AppSpace configuration file has been
started and accessible to the BW
Engine.
TIBCO-BW- Failed to initialize BW Engine due to The BW Engine was not able to
CORE-500013 database schema configuration error. initialize due to the engine database
The BW Engine database does not schema configuration error. Create a
contain the required tables. Ensure the new engine database using the database
BW Engine database has been created scripts provided in the TIBCO
with the table schemas required by the BusinessWorks product and this will
engine configure the database with the
appropriate schemas required by the
engine.
TIBCO-BW- Failed to initialize BW Engine due to The BW Engine is configured to execute

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

65
TIBCO-BW- Failed to initialize BW Engine due to The BW Engine is configured to execute

CORE-500015 missing or incorrect engine database in persistence mode "group"; however
configuration data. The BW Engine the required database configuration
persistence mode property [{0}] is set to data was not specified. Ensure the BW
[group] and this option requires valid Engine is configured with the required
engine database configuration data database connection details.
TIBCO-BW- Failed to initialize BW Engine due to This error can occur when the BW
CORE-500016 incompatible engine group name. The Engine is configured to use a group
group name [{0}] configured for the BW name that does not match the group
Engine does not match the group name name in the engine database. To resolve
value in the BW Engine database. Try these issues change the engine group
using a different engine database or name to match the group name in the
change the engine group name to match engine database, use a different engine
the value in the database database that contains the matching
engine group name or create a new
engine 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.
TIBCO-BW- Failed to initialize BW Engine due to This error can occur if the engine
CORE-500017 incompatible persistence mode between database was previously used by a BW
the engine and the engine database. Engine configured to execute in
This error can occur if the BW Engine is persistence mode 'datastore'
configured to execute in persistence (bw.engine.persistenceMode=datastore)
mode [group]; however the BW Engine . When a BW Engine uses the database
database is configured for the for the first time, the database is
persistence mode [datastore]. Try using updated with the engine execution
a different database or use a database persistence mode. Subsequently the
that is configured for the persistence persistence mode value stored in the
mode [group] database cannot be altered and the
same database cannot be used for
different engine persistence mode. To
resolve this issue ensure the engine and
the database persistence mode match or
create a new database using the
database scripts provided by the TIBCO
BusinessWorks product.

66
TIBCO-BW- Failed to initialize BW Engine due to This error can occur if the engine
CORE-500018 incompatible persistence mode between database was previously used by a BW
engine and the engine database. This Engine configured to execute in
error can occur if the BW Engine is persistence mode 'group'
configured to execute in persistence (bw.engine.persistenceMode=group).
mode [datastore]; however the engine When a BW Engine uses the database
database is configured for the for the first time, the database is
persistence mode [group]. Try using a updated with the engine execution
database that is configured for the persistence mode. Subsequently the
persistence mode [datastore] or create a persistence mode value stored in the
new engine database database cannot be altered and the
same database cannot be used for
different engine persistence mode. To
resolve this issue ensure the engine and
the database persistence mode match or
create a new database using the
database scripts provided by the TIBCO
BusinessWorks product.
TIBCO-BW- Failed to initialize BW Engine due to This error can occur if the BW Engine is
CORE-500019 missing or incorrect group connection configured to execute in persistence
provider configuration data. The BW mode [group] and the engine is not
Engine persistence mode property [{0}] correctly configured with the group
is set to [group] and this option requires connection provider data. Ensure the
valid engine group connection provider BW Engine is configured with the
configuration data. required group connection provider
details.
TIBCO-BW- Failed to initialize BW Engine due to This error can occur if the BW Engine is
CORE-500020 incorrect engine group name. The BW configured to execute in persistence
Engine persistence mode property [{0}] mode [group] and an empty or invalid
is set to [group] and this option requires engine group name is specified. Ensure
a valid engine group name specified via the engine group name is not empty or
property [{1}]. contains a valid name.
TIBCO-BW- Failed to initialize BW Engine. The BW Ensure the BW Engine thread count is
CORE-500021 Engine thread count value is configured not configured to be empty or null.
incorrectly. Ensure the thread count Furthermore the thread count value
value is set to an integer that is greater must be an integer that is greater than
than zero zero.
TIBCO-BW- Failed to initialize BW Engine. The BW Ensure the BW Engine step count is not
CORE-500022 Engine step count value is configured configured to be empty or null.
incorrectly. Ensure the step count value Furthermore the step count value must
is set to "-1" or an integer that is greater be "-1" or an integer that is greater than
than zero zero.
TIBCO-BW- Failed to initialize BW Engine. The BW Ensure the specified BW Engine

CORE-500023 Engine property [{0}] contains incorrect property is not configured to be empty
value [{1}]. Ensure the value is an or null. The value configured for this
integer that is greater than one property must be an integer that is
greater than zero.

67
TIBCO-BW- Failed to initialize BW Engine. The BW Ensure the specified BW Engine

CORE-500024 Engine property [{0}] contains incorrect property is not configured to be empty
value [{1}]. Ensure the value is an or null. The value configured for this
integer that is greater than one. property must be an integer that is
greater than zero.
TIBCO-BW- Failed to initialize BW Engine. While This is an internal product error.

CORE-500025 creating SpringApplicationContext the Contact TIBCO Support.
BW Engine encountered exception: {0}.
TIBCO-BW- The ProcessStarter or the SignalIn A ProcessStarter or SignalIn activity is

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

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

CORE-500031 encountered exception [{0}] attempting to gracefully stop the BW
Engine. For more details, refer to the
TIBCO-BW- Exception occurred when accessing Error was encountered when

CORE-500032 custom XPATH function(s) associated attempting to access the custom XPath
with the BusinessWork Engine. function associated with the BW
Exception={0} Engine. Contact TIBCO Support.
TIBCO-BW- Failed to enable the BW Debugger Error was encountered when

CORE-500033 entity in the BW Engine due to attempting to enable the BW Debugger
exception [{0}] entity in the BW Engine. Contact TIBCO
Support.

68
TIBCO-BW- BW Debugger connection failed, Ensure valid BW Debugger connection

CORE-500034 encountered exception [{0}] is provided when enabling the BW
Debugger entity in the BW Engine.
TIBCO-BW- Unable to enable Event Publisher in the Error was encountered when
CORE-500035 BW Engine, encountered exception [{0}] attempting to enable the Event
Publisher in the BW Engine. Contact
TIBCO Support.
TIBCO-BW- Attempt to disable the Event Publisher Error was encountered when
CORE-500036 in the BW Engine, encountered attempting to disable the Event
exception [{0}] Publisher in the BW Engine. Contact
TIBCO Support.
TIBCO-BW- Unable to associate an activity resource An activity that is not inside a group is
CORE-500037 with a BW group. The activity [{0}] in attempting to associate a resource with
process [{1}] is not contained within a a group. This error can occur due to an
group; however the activity is activity implementation error.
attempting to associate a resource with
a group. {2}
TIBCO-BW- Unable to associate an activity resource An activity that is not inside a loop is
CORE-500038 with a BW loop. The activity [{0}] in attempting to associate a resource with
process [{1}] is not contained within a a loop. This error can occur due to an
loop; however the activity is attempting activity implementation error.
to associate a resource with a loop. {2}
TIBCO-BW- Reference Binding configured for the The Reference Binding configured for
CORE-500039 process reference [{0}], in process [{1}], the process provided an invalid
module [{2}] provided unsupported message data model. This error can
message data model [{3}]. occur due to the Reference Binding
implementation error.
TIBCO-BW- Invocation of the Process Reference's This error indicates the Reference
CORE-500040 operation [{0}] failed. The BW Reference Binding configured for the process
Binding [{1}] configured for the process reference failed and returned a fault.
reference [{2}] in process [{3}], module
[{4}] returned fault [{5}].
TIBCO-BW- Invalid activity name. The activity name The error indicates the specified activity
CORE-500041 [{0}] is not found in process [{1}], name is not contained within the BW
module [{2}:{3}], DeploymentUnit [{4}: process. Ensure a valid activity name is
{5}]. specified for this operation.
TIBCO-BW- The BW Debugger entity is already The BW Debugger entity in the BW

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

69
TIBCO-BW- The BW process [{0}] instance faulted, This error message indicates the process
CORE-500050 JobId [{1}], ProcessInstanceId [{2}], instance did not complete successfully;
ParentProcessInstanceId [{3}], Module instead it terminated due to an error
[{4}:{5}], Application [{6}:{7}]. {8} that occurred during the execution of
the process instance. For more details
on the process instance failure, refer to
TIBCO-BW- Activity [{0}] fault. {1} This message indicates the potential
CORE-500051 activity that raised the fault and caused
the process instance to fail.
TIBCO-BW- Invoke activity [{0}] fault. {1} This message indicates the potential
CORE-500052 invoke activity that raised the fault and
caused the process instance to fail.
TIBCO-BW- XSLT transformation error. {0} This message indicates the cause of the
CORE-500053 failure could be due to a XSLT
transformation error.
TIBCO-BW- Activity [{0}] XSLT transformation error. This message indicates the cause of the
CORE-500054 {1} failure could be due to an Activity XSLT
transformation error.
TIBCO-BW- XPATH error. {0} This message indicates the cause of the
CORE-500055 failure could be due to a XPATH error.
TIBCO-BW- Activity [{0}] XPATH error. {1} This message indicates the cause of the
CORE-500056 failure could be due to an Activity
XPATH error.
TIBCO-BW- XML related error. {0} This message indicates the cause of the
CORE-500057 failure could be due to a XML error.
TIBCO-BW- Activity [{0}] XML related error. {1} This message indicates the cause of the
CORE-500058 failure could be due to an Activity XML
error.
TIBCO-BW- Reply activity [{0}] error. The reply This error message is reported when a
CORE-500059 activity cannot be associated with the process is implemented to execute more
ProcessService request message. This than one Reply activity for the same
error can occur if the process is operation, the caller of this process
implemented to send reply multiple (Service Binding, Parent Process) has
times for the same request, the caller of terminated before Reply activity can be
this process is no longer available or on executed or on recovery from a check-
recovery from a check-point the caller point the Reply activity is executed but
did not recover because it was not part the caller of this process did not recover
of the check-pointed job. {1} because it was not part of the check-
pointed job. Ensure the process is not
implemented to reply to same request
multiple times.

70
TIBCO-BW- The process instance terminated This message is reported when a

CORE-500060 without replying to the caller of this process instance terminates without
process. {0} replying to the request of a
ProcessService operation. This can
occur if the process is implemented
incorrectly 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.
TIBCO-BW- Reply activity [{0}] error. The reply This error message can be reported for
CORE-500061 activity [{1}] encountered error on the following reasons: the caller of this
sending the response to the caller of this process (Service Binding, Parent
process. This error can occur if the caller Process) raised a fault when processing
of this process raised a fault when the reply message, the caller of this
processing the reply message, the caller process is no longer available or on
of this process is no longer available or recovery from a check-point the caller
on recovery from a check-point the of this process did not recover because
caller did not recover because it was not it was not part of the check-pointed job.
part of the check-pointed job. {2}
TIBCO-BW- ProcessStarter or SignalIn activity [{0}] This message indicates the

CORE-500062 fault. {1} ProcessStarter or SignalIn activity that
generated the fault and caused the
process instance to fail.
TIBCO-BW- {0} This message provides information for

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

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

CORE-500090 [com.tibco.bw.runtime.EventContext.re [com.tibco.bw.runtime.EventContext.re
ply(..)] is not supported for the activity ply(..)] is not allowed for the specified
[{0}], in process [{1}], module [{2}:{3}], activity and this is an implementation
application [{4}:{5}]. error.
TIBCO-BW- Invalid argument value. The BW The BusinessWorks Application

CORE-500091 Application name cannot be null. specified for this operation can not be
null or empty. Ensure valid application
name is specified for this operation.
TIBCO-BW- Unable to get BW Process instances Error occurred when obtaining the
CORE-500092 information for the BW Application process instance details for the specified
[{0}] due to exception [{1}]. BusinessWorks application.

72
TIBCO-BW- Unable to get BW Process instance Error occurred when obtaining the
CORE-500093 information for the BW process instance details for the specified
ProcessIntanceId [{0}] due to exception BusinessWorks ProcessIntanceId.
[{1}].
TIBCO-BW- Unable to get BW Process instance Error occurred when obtaining the
CORE-500094 summary information for the BW process instance details for the specified
ProcessIntanceId [{0}] due to exception BusinessWorks ProcessIntanceId.
[{1}].
TIBCO-BW- Failed to suspend the BW Process Error occurred when attempting to

CORE-500095 instance for the BW ProcessIntanceId suspend the process instance for the
[{0}] due to exception [{1}]. specified BusinessWorks
ProcessIntanceId.
TIBCO-BW- Failed to resume the BW Process Error occurred when attempting to

CORE-500096 instance for the BW ProcessIntanceId resume the process instance for the
[{0}] due to exception [{1}]. specified BusinessWorks
ProcessIntanceId.
TIBCO-BW- Failed to cancel the BW Process instance Error occurred when attempting to
CORE-500097 for the BW ProcessIntanceId [{0}] due to cancel the process instance for the
exception [{1}]. specified BusinessWorks
ProcessIntanceId.
TIBCO-BW- BW AppNode name [{0}] exceeds 250 BW AppNode name exceeds 250
CORE-500098 characters and it is possible to create the characters this is not possible create
internal engine alias name. unique engine name. Ensure AppNode
name is less than 250 characters.
TIBCO-BW- Failed to install BW Module [{0}:{1}], The BW Module did not get installed in
CORE-500102 DeploymentUnit [{2}:{3}] the BW Engine, and this could be due to
many reasons. For more details, refer to
TIBCO-BW- Encountered error(s) on release- The BW Engine encountered error(s)

CORE-500104 resource operation for the BW Module when releasing resources associated
[{0}:{1}], DeploymentUnit [{2}:{3}] with the BW Module and this could be
due to many reasons. For more details,
refer to the additional exception
TIBCO-BW- Encountered error(s) when un- The BW Engine encountered error(s)

CORE-500106 deploying the BW Module [{0}:{1}], when un-deploying the BW Module
DeploymentUnit [{2}:{3}] and this could be due to many reasons.
For more details, refer to the additional
exception message or the "CausedBy"
statements reported as part of this error
message.

73
TIBCO-BW- Failed to install BW Module [{0}:{1}], The BW Module or the process is using
CORE-500110 DeploymentUnit [{2}:{3}]. The module a persistence feature such as the
or a process is configured to utilize the checkpoint activity, module shared
BW Engine persistence feature; variable with persistence option, etc..;
however the BW Engine is not however the BW Engine persistence
configured with a correct engine mode is not set appropriately for this
persistence mode. Ensure the BW feature. Ensure the BW Engine
Engine is configured for the engine persistence mode
persistence mode [datastore] or [group] (bw.engine.persistenceMode) is set to
before installing this module. "datastore" or "group" and the required
engine database configuration is
specified.
TIBCO-BW- Failed to start BW Module due to an This error is reported when the BW
CORE-500112 activity start error. CausedBy Activity in the process fails to initialize
and start. For more details, refer to the
TIBCO-BW- Unable to obtain Failed to obtain

CORE-500117 SchemaComponentCache SchemaComponentCache for the
(Namespace={0}, Location={1}, schema required by the BW Module
BaseURI={2}) for BW Module [{3}:{4}] and this could be due to many reasons.
due to exception [{5}] For more details, refer to the additional
message.
TIBCO-BW- Unable to add schema to Failed to add schema required by the

CORE-500118 SchemaComponentCache BW Module to
(Namespace={0}, Location={1}) due to SchemaComponentCache and this
exception [{2}] could be due to many reasons. For more
TIBCO-BW- Unable to obtain WSDL ModuleCache Failed to get the WSDL ModuleCache
CORE-500119 (Namespace={0}, Location={1}) for BW required by the BW Module.
Module [{2}:{3}]. The
WSDLCacheService operation [{4}]
returned "null".
CORE-500121 (Namespace={0}, Location={1}) for BW for the WSDL required by the BW
Module [{2}:{3}]. The Module.
WSDLCacheService operation [{4}]
returned "null".

74
CORE-500122 (Namespace={0}, Location={1}) for BW for the WSDL required by the BW
Module [{2}:{3}]. The Module and this could be due to many
WSDLCacheService operation [{4}] reasons. For more details, refer to the
returned exception [{5}] additional exception message or the
TIBCO-BW- Unable to resolve Schema Failed to resolve the schema required

CORE-500123 (Namespace={0}, Location={1}, by the BW Module. Ensure the schema
BaseURI={2}) for BW Module [{3}:{4}]. is valid, the schemas imported/
The SchemaCacheService operation referenced by this schema are valid, the
[{5}] returned "null". schemaLocation of the schemas
imported by this schema is valid,..
TIBCO-BW- Invalid or empty file name is specified The module shared variable or the job
CORE-500131 for the initial value of the {0} [{1}] in BW shared variable contains incorrect value
Module [{2}:{3}], DeploymentUnit [{4}: or is empty. Ensure the module or the
{5}]. job shared variable has been initialized
or assigned with a correct value.
TIBCO-BW- The file [{0}] configured for the initial The module shared variable or the job
CORE-500132 value of the {1} [{2}] is not found in BW shared variable has been initialized
Module [{3}:{4}], DeploymentUnit [{5}: with a file URL that is not found in the
{6}]. BW Module. Ensure the specified file
name is valid or the file is contained
within the BW Module.
TIBCO-BW- Unable to access the file [{0}] configured Failed to access the file specified in the
CORE-500133 for the initial value of the {1} [{2}] in BW module or job shared variable and this
Module [{3}:{4}], DeploymentUnit [{5}: could be due to many reasons. For more
{6}]; encountered exception [{7}]. details, refer to the additional exception
TIBCO-BW- Unable to open the file [{0}] configured Failed to open the file specified in the
TIBCO-BW- Unable to read the file [{0}] configured Failed to read the file specified in the
TIBCO-BW- The contents of the file [{0}] configured Ensure the file specified for the module
CORE-500136 for the initial value of the {1} [{2}] in BW or job shared variable is not empty.
{6}] is empty.

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

CORE-500143 ReferenceEndpoint for the process binding endpoint for the BW process
reference [{0}] in process [{1}], module reference and and this could be due to
[{2}:{3}], DeploymentUnit [{4}:{5}]; many reasons. For more details, refer to
encountered exception [{6}] the additional exception message or the
TIBCO-BW- Failed to obtain module properties for BW framework layer encountered

CORE-500144 the module [{0}:{1}], DeploymentUnit errors when accessing module
[{2}:{3}]; encountered exception [{4}] properties for the specified BW Module.
Contact TIBCO Support.
TIBCO-BW- Unable to obtain WSDL Interface details Error occurred when attempting to
CORE-500145 for the PortType [{0}], that is associated obtain WSDL details for the specified
with the BW Module [{1}:{2}]. PortType, and this could be due to
Encountered exception [{3}] many reasons. For more details, refer to
TIBCO-BW- Failed to install BW Component [{0}], The BW Component did not get
CORE-500202 Application [{1}:{2}] installed in the BW Engine, and this
could be due to many reasons. For more

76
TIBCO-BW- Failed to install BW Component [{0}], The BusinessWorks application or the

CORE-500203 Application [{1}:{2}]. The application is component in the application is
configured with Job PageThreshold configured to use the Job
property PageThreshold property
[bw.application.job.pageThreshold.*]; [bw.application.job.pageThreshold.*]
however the BW Engine is not and this requires the BW Engine to be
configured with a correct engine configured for the "datastore" or
persistence mode. Ensure the BW "group" persistence mode. Stop the
Engine is configured for the engine BusinessWorks AppSpace, configure
persistence mode [datastore] or [group] the BW Engine for the engine
before installing this application. persistence mode [datastore] or [group]
and restart the AppSpace before
installing the application.
TIBCO-BW- Encountered error(s) on release- Error occurred when releasing the

CORE-500210 resource operation for the BW resources associated with the BW
Component [{0}], Application [{1}:{2}] Component, and this could be due to
TIBCO-BW- Encountered error(s) when un- Error occurred when un-deploying the
CORE-500211 deploying the BW Component [{0}], BW Component and this could be due
Application [{1}:{2}] to many reasons. For more details, refer
to the additional exception message or
the "CausedBy" statements reported as
part of this error message.
TIBCO-BW- Failed to initialize BW Component [{0}], Error occurred when initializing the
CORE-500212 Application [{1}:{2}] BW Component and this could be due
to many reasons. For more details, refer
TIBCO-BW- Failed to initialize BW Component [{0}], Error occurred when creating an

CORE-500213 Application [{1}:{2}] due to activity instance of an activity that is associated
creation error with the BW Component; therefore the
BW Component can not be initialized.
message.
TIBCO-BW- Failed to initialize BW Component [{0}], There is a configuration error in the

CORE-500214 Application [{1}:{2}] due to activity or activity or resource that is associated
resource configuration error with the BW Component; therefore the
BW Component can not be initialized.
message.

77
TIBCO-BW- Failed to initialize BW Component [{0}], There are implementation errors in the
CORE-500230 Application [{1}:{2}] due to activity activity that is associated with the BW
implementation error Component; therefore the BW
Component can not be initialized. For
more details, refer to the additional
message.
TIBCO-BW- Failed to initialize BW Component [{0}], Error occurred when initializing an

CORE-500232 Application [{1}:{2}] due to activity activity that is associated with the BW
initialization error Component; therefore the BW
Component can not be initialized. For
message.
TIBCO-BW- Encountered error when destroying the Error occurred when destroying or
CORE-500238 BW Component [{0}] deleting the BW Component and this
TIBCO-BW- Encountered errors when destroying Error occurred when destroying or

CORE-500240 the BW Component [{0}] deleting the BW Component and this
TIBCO-BW- Failed to start BW Component [{0}], Error occurred when starting the BW
CORE-500242 Application [{1}:{2}] Component and this could be due to
TIBCO-BW- Encountered error(s) when stopping the Error occurred when stopping the BW
CORE-500246 BW Component [{0}], Application [{1}: Component and this could be due to
{2}] many reasons. For more details, refer to
TIBCO-BW- Encountered error(s) when starting the Error occurred when starting the
CORE-500248 ProcessStarter associated with the BW ProcessStarter activity that is associated
Component [{0}], Application [{1}:{2}] with the BW Component. For more

78
TIBCO-BW- Encountered error(s) when stopping the Error occurred when stopping the
CORE-500250 ProcessStarter associated with the BW ProcessStarter activity that is associated
Component [{0}], Application [{1}:{2}] with the BW Component. For more
TIBCO-BW- Failed to start ServiceBinding [{0}] for Error occurred when starting the
CORE-500252 the BW Component [{1}], Application ServiceBinding that is associated with
[{2}:{3}] due to ServiceBinding lifecycle the BW Component. For more details,
error refer to the additional exception
TIBCO-BW- Unable to stop ServiceBinding [{0}] for Error occurred when stopping the
CORE-500254 the BW Component [{1}], Application ServiceBinding that is associated with
[{2}:{3}] due to ServiceBinding lifecycle the BW Component. For more details,
error refer to the additional exception
TIBCO-BW- The job flow limit property [{0}] for the The BW application or component's job
CORE-500256 application or the component is flow limit property is configured with
configured incorrectly. Ensure the job an incorrect value. The job flow limit
flow limit property value is set to an property value must be an integer that
integer that is greater than zero. is greater than zero.
TIBCO-BW- The job priority property [{0}] for the The BW application or component's job
CORE-500258 application or the component is priority property is configured with an
configured incorrectly. Ensure the job incorrect value. The job priority
priority property value is set to "low", property can only be configured with
"normal" or "high". the string value "low", "normal" or
"high".
TIBCO-BW- The property to enable activity input The property that is used to determine
CORE-500262 validation for the application or the the enabling of the activity output
component is configured incorrectly. validation for the application or the
Ensure properties that are prefixed with component is configured with an
[{0}] are set with value "true" or "false". incorrect value. This property can only
be configured with the string value
"true" or "false".
TIBCO-BW- The property to enable activity output

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

79
TIBCO-BW- The property that specifies the async The property that specifies the default
CORE-500265 activity default wait time is configured wait time (timeout) value for an
incorrectly. Ensure the property [{0}] or asynchronous activity is configured
the properties prefixed with [{1}] are incorrectly. The value for this property
configured with a zero or positive must be a zero or positive number. This
numeric value property can be configured through the
Administrator or through the
AppSpace/AppNode configuration file
'config.ini'
TIBCO-BW- Failed to start BW Application [{0}] due The BW Application did not start and
CORE-500302 to exception [{1}] this could be due to many reasons. For
message.
TIBCO-BW- Failed to start BW Application [{0}:{1}] Error occurred in an activity that is

CORE-500304 due to an activity error associated with the BW Application;
therefore the BW Application did not
start. For more details, refer to the
TIBCO-BW- Encountered error when attempting to Error occurred when attempting to

CORE-500306 gracefully stop BW Application [{0}:{1}] gracefully stop the BW Application and
this could be due to many reasons. For
message.
TIBCO-BW- The BW Application [{0}:{1}] is already The BW Application is already in

CORE-500307 in stopping state. Unable to perform stopped state; therefore it can not be
operation "stopApplicationGraceful" stopped again.
TIBCO-BW- Encountered error when attempting to Error occurred when attempting to stop
CORE-500308 stop BW Application [{0}:{1}] the BW Application and this could be
due to many reasons. For more details,
TIBCO-BW- Encountered errors when attempting to

CORE-500310 stop BW Application [{0}:{1}]

80
TIBCO-BW- Unable to start ServiceBinding(s) or Error occurred when attempting to start

CORE-500312 ProcessStarter(s) associated with the the ServiceBinding(s) or
BW Application [{0}:{1}] ProcessStarter(s) activity that is
associated with the BW Application.
message.
TIBCO-BW- Unable to stop ServiceBinding(s) or Error occurred when attempting to stop

CORE-500314 ProcessStarter(s) associated with the the ServiceBinding(s) or
BW Application [{0}:{1}] ProcessStarter(s) activity that is
associated with the BW Application.
message.
TIBCO-BW- Encountered error when attempting to Error occurred when attempting to

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

CORE-500318 resume BW Application [{0}:{1}] job(s)
TIBCO-BW- Failed to create the ProcessStarter Error occurred when attempting to

CORE-500402 activity [{0}] in process [{1}], module create an instance of the ProcessStarter
[{2}] due to exception [{3}] activity in a process. For more details,
TIBCO-BW- Failed to create the ProcessStarter Unexpected error occurred when

CORE-500404 activity [{0}] in process [{1}], module attempting to create an instance of the
[{2}] due to unexpected exception [{3}] ProcessStarter activity in a process. For
message.
TIBCO-BW- Failed to initialize the ProcessStarter Error occurred when attempting to

CORE-500406 activity [{0}] in process [{1}], module initialize an instance of the
[{2}] due to activity lifecycle error ProcessStarter activity in a process. For
message.

81
TIBCO-BW- Failed to initialize the ProcessStarter Unexpected error occurred when

CORE-500408 activity [{0}] in process [{1}], module attempting to initialize an instance of
[{2}] due to unexpected activity lifecycle the ProcessStarter activity in a process.
error For more details, refer to the additional
message.
TIBCO-BW- Failed to start the ProcessStarter activity Error occurred when attempting to start
CORE-500410 [{0}] in process [{1}], module [{2}] due to the ProcessStarter activity in a process.
activity lifecycle error For more details, refer to the additional
message.
TIBCO-BW- Failed to start the ProcessStarter activity Unexpected error occurred when
CORE-500412 [{0}] in process [{1}], module [{2}] due to attempting to start the ProcessStarter
unexpected activity lifecycle error activity in a process. For more details,
TIBCO-BW- The stop operation for the Unexpected error occurred when
CORE-500414 ProcessStarter activity [{0}] in process attempting to stop the ProcessStarter
[{1}], module [{2}] failed with activity in a process. The ProcessStarter
unexpected exception [{3}] activity stop operation
"com.tibco.bw.runtime.EventSource.sto
p()" failed and returned unexpected
exception. The ProcessStarter stop
operation must not raise a fault and it is
considered to be a ProcessStarter
activity implementation error.
TIBCO-BW- The destroy operation for the Unexpected error occurred when
CORE-500416 ProcessStarter activity [{0}] in process attempting to destroy the ProcessStarter
[{1}], module [{2}] failed with activity in a process. For more details,
unexpected exception [{3}] refer to the additional exception
TIBCO-BW- The release operation for the Unexpected error occurred when
CORE-500418 ProcessStarter activity [{0}] in process attempting to release resources for the
[{1}], module [{2}] failed with ProcessStarter activity in a process. For
unexpected exception [{3}] more details, refer to the additional
message.

82
TIBCO-BW- Failed to process the event from the BWEngine failed to process the new
CORE-500420 ProcessStarter activity [{0}] events from the ProcessStarter activity.
message.
TIBCO-BW- Failed to execute event from the This error message is reported when
CORE-500422 ProcessStarter activity due to activity the output data generated by the
output data validation error. The output ProcessStarter activity does not comply
data from ProcessStarter activity [{0}] with the output schema of the
does not conform to the ProcessStarter ProcessStarter activity. This error can
activity output schema. Validation error occur if ProcessStarter activity is not
details: {1}. implemented correctly to generate the
valid output data.
TIBCO-BW- The BWEngine is unable accept new The ProcessStarter generated new
CORE-500424 events from the ProcessStarter activity events when it is in the stopped state. A
[{0}], in process [{1}], module [{2}] since ProcessStarter must not generate new
the ProcessStarter is in the stopped sate. events during the stopped state and it
When the ProcessStarter is in the will be considered as ProcessStarter
stopped state, the BWEngine will not activity implementation error. The
accept new events. ProcessStarter is in the stopped state
once the BWEngine invokes the
ProcessStarter operation
p" or before the invocation of the
ProcessStarter operation
"com.tibco.bw.runtime.EventSource.star
t".
TIBCO-BW- Failed to create the SignalIn activity Error occurred when attempting to
CORE-500502 [{0}] in process [{1}], module [{2}] due to create an instance of the SignalIn
exception [{3}] activity in a process. For more details,
TIBCO-BW- Failed to create the SignalIn activity Unexpected error occurred when
CORE-500504 [{0}] in process [{1}], module [{2}] due to attempting to create an instance of the
unexpected exception [{3}] SignalIn activity in a process. For more
TIBCO-BW- Failed to initialize the SignalIn activity Error occurred when attempting to
CORE-500506 [{0}] in process [{1}], module [{2}] due to initialize an instance of the SignalIn
activity lifecycle error activity in a process. For more details,

83
TIBCO-BW- Failed to initialize the SignalIn activity Unexpected error occurred when
CORE-500508 [{0}] in process [{1}], module [{2}] due to attempting to initialize an instance of
unexpected activity lifecycle error the SignalIn activity in a process. For
message.
TIBCO-BW- Failed to start the SignalIn activity [{0}] Error occurred when attempting to start
CORE-500510 in process [{1}], module [{2}] due to the SignalIn activity in a process. For
activity lifecycle error more details, refer to the additional
message.
TIBCO-BW- Failed to start the SignalIn activity [{0}] Unexpected error occurred when
CORE-500512 in process [{1}], module [{2}] due to attempting to start the SignalIn activity
unexpected activity lifecycle error in a process. For more details, refer to
TIBCO-BW- The stop operation for the SignalIn Unexpected error occurred when
CORE-500514 activity [{0}] in process [{1}], module attempting to stop the SignalIn activity
[{2}] failed with unexpected exception in a process. The SignalIn activity stop
[{3}] operation
p()" failed and returned unexpected
exception. The SignalIn stop operation
must not raise a fault and it is
considered to be a SignalIn activity
implementation error.
TIBCO-BW- The destroy operation for the SignalIn Unexpected error occurred when
CORE-500516 activity [{0}] in process [{1}], module attempting to destroy the SignalIn
[{2}] failed with unexpected exception activity in a process. For more details,
[{3}] refer to the additional exception
TIBCO-BW- The release operation for the SignalIn Unexpected error occurred when
CORE-500518 activity [{0}] in process [{1}], module attempting to release resource for the
[{2}] failed with unexpected exception SignalIn activity in a process. For more
[{3}] details, refer to the additional exception
TIBCO-BW- Failed to process the event from the BWEngine failed to process the new
CORE-500520 SignalIn activity [{0}] events from the SignalIn activity. For
message.

84
TIBCO-BW- Failed to execute event from the This error message is reported when
CORE-500522 SignalIn activity due to activity output the output data generated by the
data validation error. The output data SignalIn activity does not comply with
from SignalIn activity [{0}] does not the output schema of the ProcessStarter
conform to the SignalIn activity output activity. This error can occur if SignalIn
schema. Validation error details: {1} activity is not implemented correctly to
generate the valid output data.
TIBCO-BW- SignalIn activity event error. The The SignalIn activity invoked the
CORE-500524 method [{0}] is not supported for the method that is not supported for the
BW SignalIn activity. SignalIn activity and it is considered to
SignalInActivityName={1}, be SignalIn activity implementation
ProcessName={2} error.
TIBCO-BW- The SignalIn activity [{0}] in process The SignalIn activity in a process
CORE-500526 [{1}], module [{2}:{3}], application [{4}: generated fault event. For more details,
{5}] generated fault [{6}]. {7} refer to the additional exception
TIBCO-BW- While stopping the BWEngine or When the BWEngine or the application
CORE-500528 application, the SignalIn activity [{0}] in is in the process of being stopped, the
process [{1}], module [{2}:{3}], SignalIn activity generated a fault
application [{4}:{5}] generated fault [{6}]. event.
{7}
TIBCO-BW- The BWEngine is unable accept new A SignalIn activity must not generate
CORE-500530 events from SignalIn activity [{0}], in new events when it is in a stopped state
process [{1}], module [{2}] since this and it is considered to be SignalIn
SignalIn is in the stopped sate. The activity implementation error.
SignalIn is considered to be in stopped
state after the BW Engine has invoked
of the operation
p" or before the invocation of the
operation
"com.tibco.bw.runtime.EventSource.star
t". When the SignalIn is in stopped
state, the BW Engine will not accept
new events
TIBCO-BW- The model or the runtime class for the This error message is generated if the
CORE-500602 activity [{0}] in process [{1}], module BW activity is not implemented
[{2}] is implemented incorrectly. The correctly. Ensure the BW activity model
activity model class [{3}] does not class contains the required attribute or
contain the configuration property [{4}] property.
as defined in the annotation for the
member variable [{5}] declared in the
activity runtime class [{6}].

85
TIBCO-BW- The model or the runtime class for the

CORE-500603 activity [{0}] in process [{1}], module
[{2}] is implemented incorrectly. The
activity model [{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}]
TIBCO-BW- The model or runtime class for the This error message is generated if the
[{2}] is implemented incorrectly. The correctly. Ensure the BW activity model
activity model class [{3}] associated class contains the property of a
with the activity runtime class [{4}] has supported data type.
a configuration property which is of
unsupported data type. The activity
configuration property data type [{5}] is
not supported.
TIBCO-BW- The model or runtime class for the This error message is generated if the
[{2}] is implemented incorrectly. Unable correctly. Ensure the BW activity
to set member variable [{3}] declared in runtime class member variable is
the activity runtime class [{4}]. defined correctly.
Encountered exception [{5}].
TIBCO-BW- The resource specified for the process A resource assigned to the process
CORE-500606 property [{0}] in process [{1}], module property is not accessible or resolvable
[{2}] is not available in the runtime at runtime. Ensure the process property
environment. This process property is is configured correctly and the required
used by the activity [{3}] in process [{4}]. resource is resolvable at runtime.
Ensure the resource is configured and
installed correctly.
TIBCO-BW- The process property [{0}] in process The process property is configured with
CORE-500607 [{1}], module [{2}] has an incorrect value a incorrect value. Ensure the process
[{3}]. This process property is used by property is configured correctly,
the activity [{4}] in process [{5}]. For specially for a DateTime data type.
DateTime, ensure the value has the
format [{6}].
TIBCO-BW- The resource obtained from the The value assigned to the process
CORE-500608 framework for the process property property did resolve to the data type
[{0}] in process [{1}], module [{2}] is not excepted by the process property .
compatible with the data type of the Ensure the process property contains
process property. Encountered the correct value or the module
exception [{3}]. property assigned to the process
property is contains the correct value.

86
TIBCO-BW- One or more required fields of the The activity is not configured correctly.
CORE-500610 activity [{0}] in process [{1}], module Ensure the all required fields for the
[{2}] is not configured correctly. Ensure activity at design time are populated
the required fields of the activity correctly.
contains valid data.
TIBCO-BW- Failed to create the activity [{0}] in Unexpected error occurred when
CORE-500612 process [{1}], module [{2}] due to attempting to create an instance of an
exception [{3}] activity. For more details, refer to the
TIBCO-BW- Failed to create the activity [{0}] in

CORE-500614 process [{1}], module [{2}] due to
unexpected exception [{3}]
TIBCO-BW- Failed to initialize the activity [{0}] in Error occurred when attempting to
CORE-500616 process [{1}], module [{2}] due to initialize an instance of an activity. For
activity lifecycle error more details, refer to the additional
message.
TIBCO-BW- Failed to initialize the activity [{0}] in Unexpected error occurred when
CORE-500618 process [{1}], module [{2}] due to attempting to initialize an instance of an
unexpected activity lifecycle error activity. For more details, refer to the
TIBCO-BW- The execute operation for the activity The activity execution failed and raised
CORE-500620 [{0}] in process [{1}] failed with an unexpected exception. For more
unexpected exception [{2}] details, refer to the additional exception
TIBCO-BW- The post-execute operation for the The post-execute operation for an
CORE-500622 asynchronous activity [{0}] in process asynchronous activity failed and raised
[{1}] failed with unexpected exception an unexpected exception. For more
[{2}] details, refer to the additional exception
TIBCO-BW- The cancel operation for the activity The cancel operation for an
CORE-500624 [{0}] in process [{1}], module [{2}] failed asynchronous activity failed and raised
with unexpected exception [{3}] an unexpected exception. For more

87
TIBCO-BW- BWEngine was unable to execute cancel BWEngine encountered error when
CORE-500626 operation for the activity [{1}] in process attempting to execute cancel operation
[{2}], module [{3}] due to exception [{4}] for the activity. For more details, refer
TIBCO-BW- The destroy operation for the activity The destroy operation for an activity
CORE-500628 [{0}] in process [{1}], module [{2}] failed failed and raised an unexpected
with unexpected exception [{3}] exception. For more details, refer to the
TIBCO-BW- The process property [{0}] is not defined Unable to resolve the specified process
CORE-500630 in the BW Process [{1}] property. Ensure this process property
is correctly defined in the BW Process.
TIBCO-BW- The process property [{0}] has not been The specified process property has not
CORE-500631 registered with the activity context or been correctly registered with the
the event source context. activity context. This error can occur if
the BW activity is not implemented
correctly to register the process
property via method
[com.tibco.bw.runtime.ActivityContext.
registerProcessProperty].
TIBCO-BW- Failed to resolve process property [{0}] Failed to resolve the specified process
CORE-500632 from the BW Process [{1}] property. Ensure the specified process
property is defined in the process. For
exception message in the cause.
TIBCO-BW- The module property [{0}] is not Unable to resolve the specified module
CORE-500633 defined in the BW Module [{1}:{2}] property. Ensure this module property
is correctly defined in the BW Module.
TIBCO-BW- The module property [{0}] has not been The specified module property has not
CORE-500634 registered with the activity context or been correctly registered with the
the event source context. activity context. This error can occur if
the BW activity is not implemented
correctly to register the module
property via method
[com.tibco.bw.runtime.ActivityContext.
registerModuleProperty].
TIBCO-BW- Failed to resolve module property [{0}] Failed to resolve the specified module
CORE-500635 from the BW Module [{1}:{2}] property. Ensure the specified module
property is defined in the module. For
message.

88
TIBCO-BW- Activity [{0}] timed out. The activity wait or execution time has
CORE-500636 exceeded the timeout value specified
for the activity.
TIBCO-BW- Checkpoint activity [{0}] detected

CORE-500637 duplicate key.
TIBCO-BW- Activity input data validation error. The This error message is reported when
CORE-500638 input data for activity [{0}] in process the data that is provided as an input to
[{1}], module [{2}] does not conform to the activity does not comply with the
the activity input schema. {3} {4} input schema of the activity. This error
can occur if the previous 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.
TIBCO-BW- Activity output data validation error. This error message is reported when
CORE-500640 The output data from activity [{0}] in the output data generated by the
process [{1}], module [{2}] does not activity does not comply with the
conform to the activity output schema. output schema of the activity. Some
{3} {4} activities can generate in-compliant
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.
TIBCO-BW- Activity input/output data validation This error message is reported when
CORE-500641 error. The input/output data for activity the data that is provided as an input to
[{0}] in process [{1}], module [{2}] does the activity or the output data
not conform to the activity input/output generated by the activity does not
schema. {3} {4} comply with the output schema of the
activity.
TIBCO-BW- Unable to obtain activity input data. This error message is reported when an
CORE-500642 The BW Engine has not been initialized entity such as the event subscriber
or started. attempts to obtain an activity input data
before the BW Engine has been
initialized or started. Ensure the BW
Engine has started before performing
this operation.
TIBCO-BW- Unable to obtain activity input data. This error message is reported when an
CORE-500643 The specified ActivityEvent object is entity such as the event subscriber
invalid, the ActivityEvent can not be attempts to obtain an activity input
null. data; however the specified
ActivityEvent
(com.tibco.bw.runtime.event.ActivityA
uditEvent) object is invalid or null.
Ensure the ActivityEvent object is valid.

89
TIBCO-BW- Unable to obtain activity input data due Unexpected error occurred when an
CORE-500644 to exception [{0}] entity such as the event subscriber is
attempting to obtain activity input data.
message.
TIBCO-BW- Unable to obtain activity output data. This error message is reported when an
CORE-500645 The BW Engine has not been initialized entity such as the event subscriber
or started. attempts to obtain an activity output
data before the BW Engine has been
initialized or started. Ensure the BW
Engine has started before performing
this operation.
TIBCO-BW- Unable to obtain activity output data. This error message is reported when an
CORE-500646 The specified ActivityEvent object is entity such as the event subscriber
invalid, the ActivityEvent can not be attempts to obtain an activity output
null. data; however the specified
ActivityEvent
(com.tibco.bw.runtime.event.ActivityA
uditEvent) object is invalid or null.
Ensure the ActivityEvent object is valid.
TIBCO-BW- Unable to obtain activity output data Unexpected error occurred when an
CORE-500647 due to exception [{0}] entity such as the event subscriber is
attempting to obtain activity output
data. For more details, refer to the
TIBCO-BW- Unable to obtain XPath functions Error was encountered when

CORE-500648 associated with the BusinessWork attempting to obtain the list of XPath
Activity, encountered exception [{0}] functions associated with the BW
Activity.
TIBCO-BW- Unable to find process information for BWEngine is not able to obtain process
CORE-500705 process [{0}] in module information for the specified BW
ModuleName={1}, ModuleVersion={2}. process. Ensure the BW Module
contains the required process.

90
List of Process Engine Error Codes

This topic lists the error codes generated by the ActiveMatrix BPM Process Engine and details of the
corresponding errors.
Process Engine Error Codes
Error
Code Message Name Description Comments
BX- MISSING_REPLY_VARI Reply activity Possible BPEL generator error. Either

600001 ABLE_AND_PARTS {replyActivity }, variable or fromPart has to be defined
variable and fromPart on the reply activity.
are missing.
BX- SEND_REPLY_FAILURE Reply activity, Send message failed. Might be a wire

600002 {replyActivity } was configuration issue.
unable to send reply
using partner link
{partnerLink}, operation
{operation} and
message exchange
{messageExchange}.
Cause: {cause}
BX- MISSING_PARTNER_LI Partner link is missing Possible BPEL generator error. Cannot
600003 NK find a partner link scope.
BX- OPERATION_NOT_FO Operation, {operation} Operation could not be found. Possibly

600010 UND not found. missing from the service.
BX- EXIT_ON_STANDARD_ ExitOnStandardFault Exit on standard fault.

700001 FAULT
BX- PROCESS_EXIT_WITH_ Process ended with Process faulted due to a specific cause.
800003 FAULT fault Please see cause for details.
BX-100 INVALID_BRANCH_C Branches are greater In a multiple instance loop a number

001 ONDITION_EXCEPTIO than number of of branches is greater than number of
N iterations iterations.
BX-100 INVALID_EXPRESSION Invalid expression Expression returned an invalid value.

002 _VALUE_EXCEPTION value: {0} {1} See message for details.
BX-100 INVALID_VARIABLES_ Invalid variables: The "validate" part of the <assign>

003 EXCEPTION {variables} activity fails, that is, one of the
variables is invalid against its
corresponding XML definition.
BX-120 ACTIVITY_JAVA_BUND Bundle [{bundle}] not Java bundle not found.

001 LE_NOT_FOUND found
BX-200 UNEXPECTED_STATE Unexpected State: Unexpected process state. Refer to the

001 {state} message for more information.

91
Error
BX-200 PARSE_EXCEPTION Parsing Error: {error} Parsing error occurred. Refer to the
002 error for more information.
BX-200 VARIABLE_NOT_FOUN Variable {variableName} Unable to find the variable.

003 D_EXCEPTION not found
BX-200 UNEXPECTED_PREDE unexpected predecessor The predecessor task is in an

004 CESSOR_STATE state: {state} unexpected state.
BX-200 ASSERTION_ERROR Assertion error Assertion error (debugger)

006 @{linkName}
BX-200 EXCEPTION_HANDLI Exception handling Task encountered an exception when

007 NG_EXCEPTION exception. handling a fault or an unhandled
exception. Please see cause for details.
BX-200 NON_SERIALIZABLE_E {exception} This is not thrown but rather included

008 XCEPTION in the exception if the cause could not
be serialized.
BX-300 SQL_EXCEPTION SQL Exception: SQL exception occurred. Refer the

001 ErrorCode = error code, SQL state and message for
{errorCode}, SQLState = more information.
{sqlState}, Message =
{message}.
BX-400 CORRELATION_NOT_ Correlation Violation. Correlation violation occurred due to

001 MATCHED Correlation set, mismatch between correlation set
{correlationSet} does not values and inbound/outbound
match the inbound/ message.
outbound message.
BX-400 CORRELATION_INITIA Correlation Violation. Correlation violation occurred due to

002 TED Correlation set, correlation set already being initiated.
{correlationSet} is
already initiated.
BX-400 CORRELATION_NOT_I Correlation Violation. Correlation violation occurred due to

003 NITIATED Correlation set, correlation set not being previously
{correlationSet} has not initiated.
been previously
initiated.
BX-500 CONFLICTING_RECEI Conflicting receive A business process instance MUST

001 VE_EXCEPTION NOT simultaneously enable two or
more receive activities for the
same partnerLink, portType,
operation and correlationSet(s)
(including WS-BPEL processor-specific
correlation).

92
Error
BX-500 ACTIVITY_TIMEOUT_E Activity timed out Activity timed out (cancelling timer
002 XCEPTION event was triggered)
BX-600 MISSING_REQUEST Reply activity, Reply activity cannot be associated to

000 {replyActivity} cannot the receive activity
be associated receive
activity.
BX-600 MISSING_RECEIVE_VA Receive activity Possible BPEL generator error. Either

004 RIABLE_AND_PARTS {receiveActivity}, variable or fromPart has to be defined
variable and fromPart on the receive activity.
are missing.
BX-600 MISSING_REPLY Missing reply for The primary activity and the event
005 operation {operation}. handlers of a scope completed (or a
process instance completed) but there
is an orphaned Web service interaction
using a partner link or message
exchange declared in a
completed scope or process instance.
BX-600 INVOKE_FAILURE Invoke activity, Send message failed. Might be a wire

006 {invokeActivity} was configuration issue.
unable to send a
message using partner
link {partnerLink},
operation {operation}.
Cause: {cause}
BX-600 MISSING_INVOKE_IN_ Invoke activity Possible BPEL generator error. Either

007 VARIABLE_AND_TO_P {invokeActivity}, inputVariable or toPart has to be
ARTS inputVariable and defined on the invoke activity.
toPart are missing.
BX-600 MISSING_INVOKE_OU Invoke activity Possible BPEL generator error. Either

008 T_VARIABLE_AND_FR {invokeActivity}, outputVariable or fromPart has to be
OM_PARTS outputVariable and defined on the invoke activity.
fromPart are missing.
BX-600 MISSING_REFERENCE_ Reference provider not Could not find a reference provider,
009 PROVIDER found for partner link please check that component has a
{partnerLink} reference with this name configured.
BX-600 UNABLE_TO_PROCESS Unable to process Could not process incoming message.

012 _MESSAGE message for operation See error for details.
{operation} in process
{process}, module
{module}, module
version
{moduleVersion}.

93
Error
BX-600 MESSAGE_NOT_MATC Message, {message} Message definition in this module’s

013 HING_DEFINTION does not match message registry does not match the incoming
definition. message. Possible upgrade problem or
incorrectly constructed WSDL
message.
BX-600 MESSAGE_DEFINTION Message definition not Cannot find a message definition for a
014 _NOT_FOUND found for {0} given QName. Possibly missing a
WSDL import in the process or an
upgrade problem.
BX-600 PROCESS_IDENTIFIER_ Process identifier field Reusable Sub-Process task does not
016 FIELD_VALUE_NOT_SP missing process name. have a proper runtime identifier field
ECIFIED supplied.
BX-600 PACKAGE_NOT_FOUN Package [{package}] not Reusable Sub-Process task could not
017 D found. find a module with the specified name.
Either the module has not been
deployed or a dynamically supplied
value is incorrect.
BX-600 PROCESS_NOT_FOUN Process [{process}] not Reusable Sub-Process task could not
018 D found. find a process with the specified name.
Either the module that contains a
process has not been deployed or a
dynamically supplied value is
incorrect.
BX-600 PROCESS_INTERFACE_ Process [{process}] Process implements a different

019 DIFFERS implements different interface than this parent process is
interface. expecting. Please check your process
design.
BX-600 SUB_PROCESS_CANCE Sub-process cancelled Sub process has been cancelled (most
020 LLED likely by a user).
BX-600 THROW_ERROR Error thrown with error Throw task threw an error with the
021 code [{errorCode}]. following fault name.
BX-600 MISSING_PORTTYPE_D Missing port type for Missing port type for this service. One
022 ESCRIPTOR_ERROR service [{service}]. One possible reason could be a missing
possible reason could be WSDL file.
a missing WSDL file.
BX-600 OPERATION_ID_NOT_ Operation [{operation}] Operation not found in the particular

024 FOUND with partner link service. Please check that this
[{partnerLink}] not operation is defined in this service.
found.
BX-600 CREATE_MODULE_FAI Create module failed Could not create the module. Please
025 LED for module [{module}] see exception for details.
version [{version}]

94
Error
BX-600 SYSTEM_INIT_PROBLE Problem encountered Problem encountered during system

026 M during system initialization. Please see exception for
initialization details.
BX-600 SYSTEM_STOP_PROBL Problem encountered Problem encountered during system

027 EM during system stop stop. Please see exception for details.
BX-600 ADD_PROCESS_DEFINI Adding definition failed Could not create a process definition
028 TION_FAILED for process [{process}] for this module. Please see cause for
module [{module}] details.
BX-600 INVALID_PROCESS_PR Invalid process priority Invalid process priority. Allowed

029 IORITY value [{value}] values are: 50, 100, 200, 300, 400, 450.
BX-600 RESOURCE_RELEASE_ ResourceManager Could not release the resource. Please

030 FAILED release operation failed see cause for details.
for [{0}]
BX-600 PREPARE_FOR_UNDEP Cannot perform Module is in the process of being

031 LOY operation on Module undeployed and is not available for
[{module}] with version processing new jobs.
[{version}] as it is in
prepared for undeploy
state and not available
to do more work.
BX-600 MARK_FOR_DELETIO Cannot perform Module has already been undeployed

032 N operation on Module and is not available for processing new
[{module}] with version jobs.
[{version}] as it is in
marked for deletion
state and not available
to do more work.
BX-600 CREATE_MODULE_DU Create module Cannot create a module with this

033 PLICATE encountered a duplicate name and version as one already
for module [{module}] exists. Either undeploy it or change
version [{version}] your module name or version.
BX-600 MISSING_INTERFACE_ Interface provider not Cannot find an interface provider with
036 PROVIDER found for partner link the supplied service name. Please
{partnerLink} make sure that component has a
service configured with this name.
BX-600 INIT_MODULE_FAILE Init module failed for Initialization of the module failed.
037 D module [{module}] Please see cause for details.
version [{version}]
BX-600 DESTROY_MODULE_F Destroy module failed Destroying the module failed. Please
041 AILED for module [{module}] see cause for details.
version [{version}]

95
Error
BX-600 PROCESS_INSTANCE_ Process instance Process instance with this ID has

043 ALREADY_JOINED [{processInstance}] already received a message on this
already joined operation. This message will be
refused.
BX-600 OPERATIONS_NOT_M Operation {operation}, WSDL operation in the first module

044 ATCHING port type {portType} in version does not match the one in the
module {module}, second module version. This can lead
version {version} does to unpredictable results and can only
not match the same happen if the modules have been
operation in module deployed as two separate applications.
version Please reconsider your upgrade
{moduleVersion} scenario. If you wish to make
incompatible interface changes while
running both versions please rename
the operation or create a new WSDL
with a different namespace and add
new operations there.
BX-600 UNDEPLOY_MODULE_ Undeploy module Undeploying of module failed.

045 FAILED failed for module
[{module}] version
[{version}]
BX-600 TOO_MANY_PARTS Incoming message has Incoming message has more than one
046 more than one part, part while only one element is
while expecting an expected.
element for task [{task}]
element name
[{elementName}]
BX-701 DATA_SETUP_FAILUR An error encountered Setting up of data failed.

001 E while setting up data.
BX-701 QUERY_INVALID_FAIL The query is invalid. The query is not a valid SQL query.
002 URE The expected query
format is similar to a
SQL select statement.
Possible cause is
[{cause}].
BX-701 QUERY_NULL_FAILUR The query cannot be The query is empty.

003 E empty.
BX-701 QUERY_INVALID_DAT The datetime value [{0}] The datetime value is invalid.
004 ETIME_VALUE is incorrect.
BX-701 QUERY_INVALID_PRO Process instance with id Unable to find corresponding process

005 CESS_ID [{id}] cannot be found. instance with the id provided.

96
Error
BX-701 QUERY_INVALID_PAN The specified query/ The pang id is invalid.

006 G_ID pang id [{id}] is invalid.
Please enter a valid id of
integer type.
BX-701 QUERY_INVALID_ACT Activity [{activity}] is Unable to find the activity in the

007 IVITY_NAME not found in the process process template.
template.
BX-701 QUERY_NO_ACTIVITY Activity [{activity}] has Activity has not yet started for the
008 _INSTANCE not yet started for this process instance.
process instance.
BX-701 QUERY_INVALID_PRIO Priority Priority value for the query is not one
009 RITY [{priorityValue}] is of the valid values 100, 200, 300, 400.
invalid. Please enter
100(LOW),
200(NORMAL),
300(HIGH) or 400
(EXCEPTIONAL).
BX-701 QUERY_PARAMETER_ Parameter [{parameter}] Query parameter is not defined.

010 NOT_DEFINED not defined.
BX-701 QUERY_INVALID_ACT The specified activity id The specified activity id is invalid.

011 IVITY_ID [{activityId}] is invalid.
Please enter a valid
string i.e.
pvm:010A.2.1c
BX-701 QUERY_DEADLINE_N Deadline not in use for Deadline is not in use for activity.
012 OT_IN_USE activity [{activity}].
BX-701 QUERY_MODULE_NO Module [{module}] with Unable to find module version.

013 T_FOUND version [{version}] not
found.
BX-701 QUERY_WILDCARD_S No wild card (*)

014 ELECTION_NOT_ALLO selection is allowed in
WED paginated queries.
BX-701 QUERY_INVALID_STAT An invalid status value

015 US_STRING has been selected.
BX-701 QUERY_UNAUTHORIZ User is not authorized User does not have permission to
016 ED_INSTANCE_OPERA to perform this perform this operation. Please request
TION operation on this permission from your BPM system
instance. administrator.

97
Error
BX-701 QUERY_OPERATION_ Process [{process}] The operation name in the process

017 NOT_FOUND operation [{operation}] does not match the start operation in
not found. the request.
BX-701 QUERY_INVALID_PRO Process [{process}] is The process is not in the valid state.
018 CESS_STATE not in the valid state.
BX-701 BULK_OPERATION_SP We cannot complete the This is an informational message. This

102 ECIFIC_INSTANCE_FAI operation [{operation}] information is conveyed when the
LURE for the instance operation cannot be performed on a
[{instance}]. Please see particular instance for a bulk
exception in log. operation. The bulk operation can be
cancel, resume or suspend. The
operation may not be performed
because it could be invalid for the
particular process instance state.
BX-701 OPERATION_FAILED Operation failed: Operation failed. Refer log for more
130 {operation}. See log for information.
details
BX-702 DEBUGGER_INITIALIZ An error occurred while Unable to initialize the debugger due
001 ATION_FAILURE initializing the debug. to error.
Cause: {cause}
BX-702 DEBUGGER_NOT_AVA Debugger not available Debugger is not available.

002 ILABLE
BX-702 DEBUGGER_OPERATIO Debugger operation An operation in the debugger failed.

003 N_FAILED [{operation}] failed
BX-703 AUTHORIZATION_FAI Authorization failed. Exception occurred when trying to

001 LURE request authorization from the DE
service. Please check if the DE service
is up and running.
BX-703 SUBJECT_HAS_NO_PRI Subject has no principal.

002 NCIPAL
BX-703 TOO_MANY_ORG_IDS Too many organization You have created too many
003 ids: {0} organization ids. The current
maximum is six.
BX-800 PROCESS_TERMINATE Process terminated Process terminated due to an

001 D unhandled exception. Please see cause
for details.
BX-800 PROCESS_FAILED Process failed: [{0}] [{1}] Process faulted due to a specific cause.
002 Same as BX-800003 but is thrown to a
pageflow.

98
Error
BX-800 GENERATED_FAULT_R Generated fault reply Could not generate a service exception
004 EPLY_FAILED failed due to the error. Please see error
message for details.
BX-800 ACTION_FAILED_TO_ Action [{action}] failed Action failed to complete. Please see
005 COMPLETE to complete the message for a specific action
details.
BX-800 PROCESS_SUSPENDED Process suspended on Process was suspended due to the

006 _ON_ERROR error: [{error}] error. Obsolete in BPM 2.0.
BX-800 PARAMETER_VALUE_I ParameterName can not Parameter name has to be specified,

007 S_NULL be null. please enter a valid name.
BX-800 TASK_UPDATE_FAILE Task update from [{0}] Task could not be updated with a
008 D failed. signal due to the error. Please see error
details.
BX-800 TASK_REPORTED_ERR Task reported an error Task reported an error, logged before
009 OR the process is halted. Process can be
resumed to fail, retried if an error is
intermittent or a task can be ignored.
Please see halt data for details.
BX-900 EXTENSION_ACTIVITY Extension activity Extension activity with a particular

001 _NOT_registerED [{extensionActivity}] name is not registered.
not registered, defaults
to empty activity.
BX-900 EXTENSION_ACTIVITY Extension activity Extension activity with a particular

002 _NAMESPACE_NOT_re namespace namespace is not registered.
gisterED [{extensionActivityNam
espace}] not recognized,
defaults to empty
activity.
BX-900 DUPLICATE_PREFIX_D Duplicate prefix Duplicate prefix encountered while

003 EFINITION definition: prefix creating a process.
[{prefix}], namespace1
[{namespace1}],
namespace2
[{namespace2}]
BX-905 ADD_PROCESS_DEFINI Adding definition for Creating a process definition for a

001 TION process [{process}] particular module.
module [{module}]
BX-905 CREATE_MODULE Creating module Creating a module with a particular

002 module [{module}] name and version.
version [{version}]

99
Error
BX-905 CREATE_SUBPROCESS Sub-Process instance Sub process instance created for a

003 [{subProcessInstance}] particular module and process
created for module definition by a specific parent.
[{module}], process
[{process}], parent
process id
[{parentProcessId}].
BX-905 CREATE_PROCESS Creating process Creating process instance for a

004 instance: module particular module and process.
[{module}], process
[{process}]
BX-905 PROCESS_CREATED Process instance Process instance created for a

005 [{processInstance}] particular module and process.
created for module
[{module}], process
[{process}]
BX-905 SET_READY_FAILED setReady error:

006 Couldn't find a task for
the following uri: [{uri}],
userData: [{userData}]
BX-910 ACTIVITY_ENTER_ME Enter method

001 THOD [{methodName}].
BX-910 ACTIVITY_CONFIGUR Configuration info is

002 ATION_INFO [{configurationInfo}].
BX-910 ACTIVITY_DEBUG_MS {0} [{1}].

003 G
BX-910 ACTIVITY_EXCEPTION Exception Cause is

004 _MSG [{cause}] Exception
Message is [{message}]
Exception Stack is
[{stack}]
BX- ACTIVITY_DATABASE_ Problem setting the Unable to set the result for a particular
DB-110 SET_COLUMN_ERROR column result for column as the type is not supported.
013 columnName Refer exception for more information.
[{columnName}] as the
following type [{type}]
is not supported.
Exception is
[{exception}] "

100
Error
BX- ACTIVITY_DATABASE_ Cannot get connection

DB-110 NO_CONNECTION_D data source. Perhaps,
001 ATA_SOURCE the data source
property is incorrect or
missing".
BX- ACTIVITY_DATABASE_ No connection profile is

DB-110 NO_CONNECTION_PR found.
002 OFILE
BX- ACTIVITY_DATABASE_ Invalid procedure name

DB-110 INVALID_STORED_PR specified. It can not be
003 OCEDURE_NAME null.
BX- ACTIVITY_DATABASE_ SQL statement cannot

DB-110 MISSING_SQL_STATEM be empty.
004 ENT
BX- ACTIVITY_DATABASE_ SQL must be an Improper SQL is provided.

DB-110 IMPROPER_SQL_UPDA UPDATE/INSERT/
005 TE_STATEMENT DELETE statement.
Invalid SQL is [{sql}].
BX- ACTIVITY_DATABASE_ [{numberOfSQLtParam Incorrect number of input parameters

DB-110 WRONG_NUMBER_OF eters}] input parameters not matching the number of SQL
006 _INPUT_PARAMETERS declared in the SQL parameters.
statement but
[{numberOfInputParam
eters}] input parameters
provided.
BX- ACTIVITY_DATABASE_ Specified database The database operation is invalid.

DB-110 INVALID_OPERATION operation Please use design tool to design the
007 [{sqlDatabaseOperation database process.
}] is invalid. Please use
design tool to design
database process.
BX- ACTIVITY_DATABASE_ Data variable type The return variable is invalid and
DB-110 INVALID_RETURN_VA specified for parameter cannot hold the returned data.
008 RIABLE [{parameter}] does not
have the capacity to
hold the returned data.
BX- ACTIVITY_DATABASE_ Cannot find Factory The defined BOM type used to hold
DB-110 INVALID_CDS_FACTO create method the database query results is incorrect.
009 RY_CREATE_METHOD [{factoryCreateMethod}] Please ensure the BOM attributes
. match the database attribute names
that are queried.

101
Error
BX- ACTIVITY_DATABASE_ Cannot find Factory The defined BOM type used to hold
DB-110 INVALID_CDS_FACTO class [{factoryClass}]. the database query results is incorrect.
010 RY_CLASS Please ensure the BOM attributes
match the database attribute names
that are queried.
BX- ACTIVITY_DATABASE_ There is no OUT

DB-110 NO_OUT_PARAMETER parameter defined to
011 _VARIABLE contain the database
query results.
BX- ACTIVITY_DATABASE_ CannotGetDatabaseCon Unable to connect to the database.

DB-110 CANNOT_CONNECT_ nection. Please ensure that the resource
012 TO_DATABASE template points to the correct database.
BX- ACTIVITY_DATABASE_ Not able to set the

DB-110 SET_BOM_COLUMN_E database table column
014 RROR [{columnName}] for
BOM [{bom}]. At design
time, please ensure that
there are BOM attribute
labels that match the
database table column
names."
BX- DATABASE_STORED_P Not able to retrieve

DB-110 ROCEDURE_CONFIGU metadata information
015 RATION_ERROR for stored procedure
[{procedureName}]
BX- DATABASE_XA_DATAB Database activity The database is configured to be XA

DB-110 ASE_SUPPORT_ERROR participation in a XA transaction supported. Please
016 transaction is not configure data source to be non-XA
supported. Please re- transaction supported.
configure data source to
be non-XA. Exception
Cause is [{cause}]
Exception Message is
[{message}] Exception
Stack is [{stack}]
BX- DATABASE_SET_CALL Problem setting the

DB-110 ABLE_STATEMENT_ER parameter [{parameter}]
017 ROR for index [{index}] with
type [{type}] and value
[{value}]. Exception is
[{exception}]

102
Error
BX- DATABASE_SET_CALL Problem finding the

DB-110 ABLE_STATEMENT_PA input parameter that
018 RAMETER_NAME_ERR matches stored
OR procedure parameter
[{parameter}].
BX- EMAIL_ATTACHMENT Mail attachment not EMAIL_ATTACHMENT_FILE_NOT_

EMAIL _FILE_NOT_FOUND found FOUND_MSG = RtnCode = [{0}]
-100001 RtnMsg = You may have specified an
incorrect filename for an attachment,
or the attachment may have been
deleted.
BX- EMAIL_SERVER_UNAV SMTP Connect Mail EMAIL_SERVER_UNAVAILABLE_MS

EMAIL AILABLE Error G = RtnCode = [{0}] RtnMsg = An error
-100002 occurred connecting to the SMTP
server. First, check your server
configuration. Second, check that the
SMTP server is running and check the
network configuration.
BX- EMAIL_INVALID_FRO Mail From email EMAIL_INVALID_FROM_ADDRESS_

EMAIL M_ADDRESS address is not valid MSG = RtnCode = [{0}] RtnMsg = A
-100003 valid Mail From address must be
provided. Perhaps, one must exist on
your SMTP server.
BX- EMAIL_UNKNOWN_R Unknown mail recipient EMAIL_UNKNOWN_RECIPIENT_MS

EMAIL ECIPIENT G = RtnCode = [{0}] RtnMsg = You may
-100004 have made a mistake entering the
recipient's address, or the address may
not exist.
BX- EMAIL_SEND_COMMU Error sending mail data EMAIL_SEND_COMMUNICATION_

EMAIL NICATION_ERROR command ERROR_MSG = RtnCode = [{0}]
-100005 RtnMsg = There was a problem
communicating with the SMTP server.
Check that the SMTP server is running,
and check the network configuration.
BX- EMAIL_UNKNOWN_H UnknownHostExceptio EMAIL_UNKNOWN_HOST_MSG =

EMAIL OST n RtnCode = [{0}] RtnMsg = Unknown
-100006 Host [{1}]
BX- EMAIL_UNKNOWN_E Unknown mail error EMAIL_UNKNOWN_ERROR_MSG =

EMAIL RROR RtnCode = [{0}] RtnMsg = Unknown
-100010 error.
BX- ACTIVITY_EMAIL_INP Input Field Input field is required for email.

EMAIL UT_REQUIRED [{inputField}] is
-100011 required.

103
TEA Agent Error Codes

This section describes the error messages that can be reported by the TEA agent.
TIBCO-BW- {0}
TEAAGENT-100001
TIBCO-BW- {0}
TEAAGENT-200001
TIBCO-BW- {0}
TEAAGENT-300000
TIBCO-BW- The AppSpace [{0}] in Domain [{1}]

TEAAGENT-300001 configured successfully. Restart
AppSpace to apply changes
TIBCO-BW- Found matches:

TEAAGENT-300002
TIBCO-BW- Created Domain [{0}]

TEAAGENT-300003
TIBCO-BW- Deleted Domain [{0}]

TEAAGENT-300004
TIBCO-BW- Created AppSpace [{0}] in Domain

TEAAGENT-300005 [{1}]
TIBCO-BW- Deleted AppSpace [{0}] in Domain

TEAAGENT-300006 [{1}]
TIBCO-BW- Created AppNode [{0}] in AppSpace

TEAAGENT-300007 [{1}] of Domain [{2}]
TIBCO-BW- Deleted AppNode [{0}] in AppSpace

TEAAGENT-300008 [{1}] of Domain [{2}]
TIBCO-BW- Deployed Application [{2}] in

TEAAGENT-300009 AppSpace [{1}] of Domain [{0}]
TIBCO-BW- Uploaded Archive [{1}] in Domain

TEAAGENT-300010 [{0}]
TIBCO-BW- Deleted Archive [{0}]

TEAAGENT-300011
TIBCO-BW- Undeployed Application [{2}] in

TEAAGENT-300012 AppSpace [{1}] in Domain [{0}]
TIBCO-BW- Deleted Archive [{0}]

TEAAGENT-300013

104
TIBCO-BW- Configured AppNode [{0}] of

TEAAGENT-300014 AppSpace [{1}] in Domain [{2}].
TIBCO-BW- Uploaded Archive [{1}] in Domain

TEAAGENT-300015 [{0}]. Application deployed in the
following AppSpace(s) [{2}] is out of
sync. Please re-deploy.
TIBCO-BW- Deployed Application [{2}] in

TEAAGENT-300016 AppSpace [{1}] of Domain [{0}]. The
AppSpace [{1}] does not have any
AppNodes.
TIBCO-BW- AppNode[{0}] in AppSpace[{1}] in

TEAAGENT-300017 Domain[{2}] is using [{3}]:[{4}] for {5}
interface
TIBCO-BW- Configured Application [{0}]. Restart

TEAAGENT-300018 the Application for changes to take
effect.
TIBCO-BW- Enabled engine debug port

TEAAGENT-300019
TIBCO-BW- Enabled engine debug port

TEAAGENT-300020

TEAAGENT-300021 Applications in AppNode [{0}], {1}

TIBCO-BW- Published Application [{2}] endpoint

TEAAGENT-300023 to Mashery in AppSpace [{1}] in
Domain [{0}]

TEAAGENT-300024 Application [{0}|{1}]

TIBCO-BW- Failed to publish Application [{2}]

TEAAGENT-300031 endpoint to Mashery in AppSpace
[{1}] in Domain [{0}]
TIBCO-BW- {0}
TEAAGENT-400000
TIBCO-BW- {0} Internal product defect. Contact

TEAAGENT-500000 TIBCO support.

105
TIBCO-BW- Failed to start TEA Agent, {0}

TEAAGENT-500001
TIBCO-BW- Error encountered during shutdown

TEAAGENT-500002 of TEA Agent
TIBCO-BW- Please provide entity name to be

TEAAGENT-500003 created
TIBCO-BW- Please provide entity name to be

TEAAGENT-500005 stopped
TIBCO-BW- Please provide domain name

TEAAGENT-500006
TIBCO-BW- Please provide AppSpace name

TEAAGENT-500007
TIBCO-BW- Please provide AppNode name

TEAAGENT-500008
TIBCO-BW- Please provide AppNode HTTP port

TEAAGENT-500009
TIBCO-BW- Please provide application name

TEAAGENT-500010
TIBCO-BW- Please provide library name

TEAAGENT-500011
TIBCO-BW- Please provide object key

TEAAGENT-500012
TIBCO-BW- TEA Operation {0} is not available.

TEAAGENT-500013
TIBCO-BW- Failed to disable statistics collection

TEAAGENT-500014 for Application
TIBCO-BW- Failed to extract TEA Agent web

TEAAGENT-500020 application into [{0}]
TIBCO-BW- Domain [{0}] is not present.

TEAAGENT-500201
TIBCO-BW- More than one Domain [{0}] is found.

TEAAGENT-500202
TIBCO-BW- AppSpace [{0}] in Domain [{1}] does

TEAAGENT-500203 not exist.

106
TIBCO-BW- More than one AppSpace {0} in

TEAAGENT-500204 Domain [{1}] is found.
TIBCO-BW- Machine {0} is not present.

TEAAGENT-500205
TIBCO-BW- More than one Machine {0} is found.

TEAAGENT-500206
TIBCO-BW- Please provide agent name.

TEAAGENT-500207
TIBCO-BW- Agent {0} is not present.

TEAAGENT-500208
TIBCO-BW- More than one Agent {0} is found.

TEAAGENT-500209
TIBCO-BW- Please provide EAR File Name.

TEAAGENT-500210
TIBCO-BW- Archive [{0}] not found in Domain

TEAAGENT-500211 [{1}].
TIBCO-BW- More than one Archive [{0}] in

TEAAGENT-500212 Domain [{1}] found.
TIBCO-BW- Please use "show --help" to see

TEAAGENT-500213 available type of entities.
TIBCO-BW- Entity [{0}] not found. Please use

TEAAGENT-500214 "show --help" to see available entity
types.
TIBCO-BW- Application version is not present.

TEAAGENT-500215
TIBCO-BW- Application {0} in Domain {1}

TEAAGENT-500216 AppSpace{2} not found.
TIBCO-BW- More than one application {0} in

TEAAGENT-500217 Domain {1} AppSpace{2} is found.
TIBCO-BW- Please provide installation Name.

TEAAGENT-500218
TIBCO-BW- Please provide machine name.

TEAAGENT-500219

TEAAGENT-500220 Domain [{2}] not found.

107
TIBCO-BW- Failed to register BW TEA agent [{0}]

TEAAGENT-500300 with TEA server, <CausedBy$gt; {1}
TIBCO-BW- Failed to update data store with

TEAAGENT-500301 current TEA Agent details
TIBCO-BW- Failed to upload ear file into Domain

TEAAGENT-500302 [{0}]
TIBCO-BW- Invalid pagination boundaries

TEAAGENT-500303
TIBCO-BW- Name contains invalid characters and

TEAAGENT-500304 does not comply with naming
conventions. Valid characters are
TIBCO-BW- Name length exceeds 100 characters

TEAAGENT-500305 and it will be truncated to satisfy the
length limit
TIBCO-BW- Name contains invalid

TEAAGENT-500306 characters.\nAllowed characters are
alphabet as well as digits, " ", "." and
"-".\n.

TEAAGENT-500307 Domain [{1}] failed, {2}
TIBCO-BW- Library version missing.

TEAAGENT-500308
TIBCO-BW- Failed to create Domain [{0}]

TEAAGENT-500309
TIBCO-BW- Failed to delete Domain [{0}]

TEAAGENT-500310
TIBCO-BW- Failed to delete AppSpace [{0}] in

TEAAGENT-500311 Domain [{1}]
TIBCO-BW- Failed to create AppSpace [{0}] in




108
TIBCO-BW- Failed to deploy Application from

TEAAGENT-500315 archive [{0}]
TIBCO-BW- Profile file [{0}] does not exist.

TEAAGENT-500316
TIBCO-BW- Failed to upload Archive [{1}] in

TIBCO-BW- Failed to delete Archive [{0}]

TEAAGENT-500318
TIBCO-BW- profileFile and profileName are Provide one the two possible
TEAAGENT-500319 mutually exclusive arguments. arguments, but not both at the same
time
TIBCO-BW- Failed to undeploy Application [{2}] in Check bwagent log file for further
TEAAGENT-500320 AppSpace [{1}] of Domain [{0}] details.
TIBCO-BW- Failed to create entity of type [{0}]

TEAAGENT-500321 with name [{1}] reason : {2}
TIBCO-BW- Failed to delete Agent [{0}] Check bwagent log file for further
TEAAGENT-500322 details.
TIBCO-BW- Failed to configure AppNode [{0}] in

TEAAGENT-500323 AppSpace [{1}] of Domain [{2}] <Cause
$gt; : {3}
TIBCO-BW- Failed to get bwagents.

TEAAGENT-500324
TIBCO-BW- Failed to obtain machine records.

TEAAGENT-500325
TIBCO-BW- Failed to obtain installation records.

TEAAGENT-500326
TIBCO-BW- Failed to obtain bwagent log.

TEAAGENT-500327
TIBCO-BW- Failed to obtain bwagent configuration

TEAAGENT-500328
TIBCO-BW- Failed to obtain Application

TEAAGENT-500329 configuration
TIBCO-BW- Failed to obtain AppNode records.

TEAAGENT-500330

109
TIBCO-BW- The value of the {0} argument has to

TEAAGENT-500331 be a valid port number, valid range is
[0-65335]
TIBCO-BW- The mandatory argument {0} is

TEAAGENT-500332 missing.
TIBCO-BW- Failed to obtain Application metrics

TEAAGENT-500400
TIBCO-BW- Failed to stop process starters

TEAAGENT-500401
TIBCO-BW- Failed to start process starters

TEAAGENT-500402
TIBCO-BW- Failed to resume Application instance Check bwagent log file for further
TIBCO-BW- Failed to resume Application Check bwagent log file for further
TIBCO-BW- Failed to pause Application instance Check bwagent log file for further
TIBCO-BW- Failed to pause Application instance Check bwagent log file for further
TIBCO-BW- Failed to stop Application Check bwagent log file for further
TIBCO-BW- Failed to stop Application instance Check bwagent log file for further
TIBCO-BW- Failed to start Application instance Check bwagent log file for further
TIBCO-BW- Failed to start Application Check bwagent log file for further
TIBCO-BW- Failed to obtain AppNode log.

TEAAGENT-500411
TIBCO-BW- Failed to obtain AppNode thread

TEAAGENT-500412 dump.
TIBCO-BW- Failed to start AppNode

TEAAGENT-500413
TIBCO-BW- Failed to stop AppNode

TEAAGENT-500414

110
TIBCO-BW- Failed to obtain AppNode names.

TEAAGENT-500415
TIBCO-BW- Failed to stop AppSpace

TEAAGENT-500416
TIBCO-BW- Failed to start AppSpace

TEAAGENT-500417
TIBCO-BW- Failed to obtain machines of an

TEAAGENT-500418 AppSpace
TIBCO-BW- Failed to obtain softwares of an

TEAAGENT-500419 installation.
TIBCO-BW- Failed to obtain machine states Check bwagent log file for further
TIBCO-BW- Please provide port number Provide a valid port.

TEAAGENT-500421
TIBCO-BW- Please provide interface Provide an interface name, e.g. IP

TEAAGENT-500422 address or localhost
TIBCO-BW- Port is unavailable Choose a different port.

TEAAGENT-500423
TIBCO-BW- bwagent [{0}] is using [{1}]:[{2}] as the

TEAAGENT-500424 {3} interface and port
TIBCO-BW- AppSpace [{0}] already exists in Choose a different name for the
TEAAGENT-500425 domain [{1}] AppSpace.
TIBCO-BW- Failed to configure Appliaction [{0}] Check the bwagent log file for further
TIBCO-BW- Invalid port number. Valid port range Provide a port in the valid port range
TEAAGENT-500427 is (0, 65535). between 0 and 65535. Note, ports
below 1024 do require the bwagent
executable to be granted administrator
permissions.
TIBCO-BW- Please provide destination for the Provide a valid destination for the
TEAAGENT-500428 backup file. backup file. See Admin Guide.
TIBCO-BW- Destination argument is a folder Provide a file name as destination

TEAAGENT-500429 where a file argument was expected. argument instead of a folder.
TIBCO-BW- Failed to backup domain [{0}] Check the bwagent log file for further

111
TIBCO-BW- Failed to configure Domain [{0}] Check the bwagent log file for further
TIBCO-BW- Failed to obtain Profile configuration

TEAAGENT-500432
TIBCO-BW- Invalid request.

TEAAGENT-500433
TIBCO-BW- AppInst not found

TEAAGENT-500434
TIBCO-BW- Failed to obtain application instance

TEAAGENT-500435 configuration.
TIBCO-BW- No AppNodes available.

TEAAGENT-500436
TIBCO-BW- Failed to obtain agent system

TEAAGENT-500436 information
TIBCO-BW- Failed to enable engine debug port

TEAAGENT-500437
TIBCO-BW- Failed to enable engine debug port

TEAAGENT-500438
TIBCO-BW- Failed to get BW Engine info Check bwagent.log file for more
TEAAGENT-500439 information
TIBCO-BW- Failed to get Applications of Archive Check the bwagent log file for further
TEAAGENT-500440 [{0}] in Domain [{1}] details.
TIBCO-BW- Failed to start TEA Agent. Network Specify a value for the
TEAAGENT-500500 name property not specified. Check bw.agent.networkName property in
configuration and restart. the bwagent.ini file.

TEAAGENT-500501 for Applications in AppNode [{0}], {1}
TIBCO-BW- Failed to enable statistics collection for

TIBCO-BW- Failed to get runtime info for appnode

TEAAGENT-500503 [{0}]
TIBCO-BW- Failed to get activity instances

TEAAGENT-500509
TIBCO-BW- Failed to get Activity stats

TEAAGENT-500510

112
TIBCO-BW- Failed to get Process stats

TEAAGENT-500511
TIBCO-BW- Failed to get stats collection

TEAAGENT-500512 enablement
TIBCO-BW- Failed to enable statistics collection for


TEAAGENT-500514 for Application [{0}|{1}]
TIBCO-BW- {0} Internal product defect. Contact

TEAAGENT-000001 TIBCO support.
Design Time Error Codes

This section describes the error messages that can be reported at design time.
TIBCO-BW-DT- Cyclic reference detected in Inspect the reference binding on the

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

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

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

113
BW_VALIDATION_MODULE- The Bundle-Version of Not applicable.

_VERSION_CONFIG_ERROR-50 BusinessWorks module
0620 [{0}] must end
with .qualifier in the
manifest file [META-INF/
MANIFEST.MF]
APPLICATION_MANIFEST_VER The Bundle-Version of Not aplicable.

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

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

the File palette.

PALETTE- Contact TIBCO Support.
FILE-000001

PALETTE- not applicable.
FILE-100001

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

PALETTE- highlights the runtime progress of the
FILE-300001 activity. Resolution is not applicable.

PALETTE- highlights situations that may affect the
FILE-400001 activity execution.
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 fileName
PALETTE- exists at the given location.
FILE-500001
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 createNonExistingDirectory
PALETTE- directory denoted by the pathname [{1}] option on general tab is checked.
FILE-500004 does not exist.

115
TIBCO-BW- Cannot read the binary content from Ensure the file name is valid and the
PALETTE- the file [{0}]. access permissions are set
TIBCO-BW- Cannot read the string content from the Ensure the file name is valid and the
PALETTE- file [{0}]. access permissions are set
TIBCO-BW- The file encoding [{0}] is not valid. Ensure the encoding provided is valid.
PALETTE-
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 set
TIBCO-BW- Unable to rename the file from [{0}] to Ensure the source file and destination
PALETTE- file [{1}]. The destination file exists and file both are of same type.
FILE-500010 its type is different then the type of the
source file.
TIBCO-BW- The file activity [{0}] cannot be used to Ensure the directories can't be moved
PALETTE- move a directory. unless they have same parent Directory.
FILE-500011
TIBCO-BW- Cannot remove the file [{0}]. Ensure the file or directory name is
PALETTE- valid and the access permissions are set
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 set
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 and is
FILE-500015 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 createNonExistingDirectory

PALETTE- on general tab is checked.
FILE-500017

116
TIBCO-BW- Cannot copy from file [{0}] to file [{1}]. Ensure the file or directory name is
PALETTE- valid and the access permissions are set
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 fileName
PALETTE- [{1}]. exists at the given location.
FILE-500020
TIBCO-BW- The ProcessStarter activity [{0}] failed to This is an internal product error.
PALETTE- a generate a new event due to exception Contact TIBCO Support.
FILE-500502 [{1}].
TIBCO-BW- The Signal-In activity activity [{0}] This is an internal product error.
PALETTE- failed to a generate a new event due to Contact TIBCO Support.
FILE-500503 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.
TIBCO-BW- The Waitforfilechange Signal-In activity This is an internal product error.

FILE-500022 due to exception [{1}] since it is in the
stopped state.
FTP Palette Error Codes

the FTP palette.
TIBCO-BW- Unable to establish FTP connection for Ensure FTP Connection parameters are
PALETTE- the FTP function [{0}]. Encountered 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-BW- Error in PUT or MPUT command. Error in PUT or MPUT command. See
PALETTE- Fault Tab for details.
FTP-500005
TIBCO-BW- Error in GET or MGET command. Error in GET or MGET command. See
PALETTE- Fault Tab for details.
FTP-500006

117
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 PUT
PALETTE- file specified cannot be found [{0}]. 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 valid.
PALETTE-
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 valid.
PALETTE- Encountered error [{0}].
FTP-500019
TIBCO-BW- File [{0}] does not exist. Ensure File exist at given location.
PALETTE-
FTP-500020
TIBCO-BW- Error establishing active data socket. Please Contact TIBCO Support.
PALETTE- Reason [{0}].
FTP-500022
TIBCO-BW- Error performing mget. Reason: mget is Please Contact TIBCO Support.
PALETTE- not supported for FTP via Proxy
FTP-500024
TIBCO-BW- Error in PUT or MPUT command.Error: Error in PUT or MPUT command. See
PALETTE- [{0}]. Fault Tab for details.
FTP-500025
TIBCO-BW- Error in GET or MGET command.Error: Error in GET or MGET command. See
PALETTE- [{0}]. Fault Tab for details.
FTP-500026

118
General Palette Error Codes

the ActiveMatrix BusinessWorks General Activities palette.
TIBCO-BW-PALETTE- Activity configuration error. The

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

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

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

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

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

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

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

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

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

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

119
TIBCO-BW-PALETTE- Activity configuration error. A

GENERAL-ACTIVITIES-500002 Timeout expression configured
for the CheckPoint Activity [{0}]
in the process [{1}] must be a
valid integer expression.
TIBCO-BW-PALETTE- Activity configuration error. A

GENERAL-ACTIVITIES-500003 DuplicateKey expression
configured for the CheckPoint
Activity [{0}] in the process [{1}]
must be cast to a string. The
expression should be configured
as [string({2})].
HTTP Palette Error Codes

the ActiveMatrix BusinessWorks HTTP palette.

HTTP-000001

HTTP-100001

HTTP-200001

HTTP-300001 activity. Resolution is not applicable.

HTTP-400001 activity execution.
TIBCO-BW- The Http Server replied with a [{0}] Check the status code to know the
PALETTE- status code. reason for the error.
HTTP-500001
TIBCO-BW- The Http Server replied with a [{0}] Check the status code to know the
PALETTE- status code reason for the error.
HTTP-500002
TIBCO-BW- An exception was thrown while trying Correct the configuration of Send Http
PALETTE- to initialize the Http client. Request activity.
HTTP-500003

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

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

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

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

PALETTE- trying to read the response
HTTP-500015

121

PALETTE- trying to send the response
HTTP-500016
TIBCO-BW- An Exception was thrown while trying System exception.

PALETTE- to send the response
HTTP-500017
TIBCO-BW- The header [{0}] is defined as non- Correct the input data.
PALETTE- Repeating Header in Input Headers.
HTTP-500019 This header cannot have multiple
occurrences in DynamicHeaders.
TIBCO-BW- The HTTP ProcessStarter [{0}] failed to Check the exception and correct the
PALETTE- generate a new event due to exception configuration of Http connector or Http
HTTP-500020 [{1}] Receiver.
TIBCO-BW- Failed to reply to HTTP ProcessStarter Check point activity should not be
PALETTE- activity. This error can occur if the placed between Http ProcessStarter and
HTTP-500021 HTTP Response activity is executed Send Http Response activity.
after recovering from a check-pointed
BusinessWorks process instance.
TIBCO-BW- Failed to authenticate request. Check if the identity resource

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

PALETTE- configuired on Http Connector
HTTP-500022 resource.
TIBCO-BW- Value not specified for the dynamic Correct the input data.
PALETTE- header [{0}]
HTTP-500023
TIBCO-BW- Reply for field cannot be blank. Select a value for Reply For Field in
PALETTE- Send HTTP Response activity.
HTTP-500024
Java Palette Error Codes

the ActiveMatrix BusinessWorks Java palette.
TIBCO-BW- [{0}]
PALETTE-JAVA-
PROCESSSTARTE
R-000001

122
TIBCO-BW- [{0}]
PALETTE-JAVA-
PROCESSSTARTE
R-100001
TIBCO-BW- [{0}]
PALETTE-JAVA-
PROCESSSTARTE
R-200001
TIBCO-BW- [{0}]
PALETTE-JAVA-
PROCESSSTARTE
R-300001
TIBCO-BW- [{0}]
PALETTE-JAVA-
PROCESSSTARTE
R-400001
TIBCO-BW- The JAVA ProcessStarter activity [{0}] Ensure that the correct object passed to
PALETTE-JAVA- failed to a generate a new event due to the 'onEvent' method in the specified
PROCESSSTARTE exception [{1}] Java class. Please refer to the declared
R-500001 class implementation for details.
TIBCO-BW- Illegal onEvent(Object output)/ Remove the onEvent(Object output)

PALETTE-JAVA- onError(Throwable throwable) method method call in the init method.
PROCESSSTARTE call. OnEvent/OnError method must
R-500002 not be called in the init method or
during the initialization phase.
TIBCO-BW- The JAVA ProcessStarter activity [{0}] Ensure that the ProcessStarter has been
PALETTE-JAVA- failed to a generate a new event due to stopped properly.
PROCESSSTARTE exception [{1}] since it is in the stopped
R-500003 state.
TIBCO-BW- [{0}] This is an internal product error.

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

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

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

JAVA-300001 activity. Resolution is not applicable.

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

JAVA-400001 activity execution.
TIBCO-BW- Internal error occurred. Class=[{0}], Make sure the Java Global Instance
PALETTE- Method=[{1}], Cause=[{2}] resource has properly referenced.
JAVA-501005
TIBCO-BW- Input data error in field [{0}] because Ensure that the correct values are
PALETTE- [{1}]. provided for the method parameter
JAVA-500504 elements that are in the activity input
tab.
TIBCO-BW- Output data error in field [{0}] because Ensure that the getter methods are
PALETTE- [{1}]. returning the correct values to display
JAVA-500604 the activity output tab.
TIBCO-BW- Output data error in field [{0}] value Ensure that the getter methods are not
PALETTE- cannot be null. returning null to display the activity
JAVA-500605 output tab.
TIBCO-BW- Output data error in field [{0}] value is Ensure that the getter method returns a
PALETTE- not serializable. serializable Java class to display the
JAVA-500606 activity output tab.
TIBCO-BW- While executing method [{0}] Correct the error stated in the exception
PALETTE- encountered exception [{1}] [{2}]. message and retry.
JAVA-500001
TIBCO-BW- Activity input data conversion error. Incorrect object reference was specified
PALETTE- Exception [{0}] occurred while trying to for the declared Java class. Ensure that
JAVA-500013 render the activity input data. [{1}] the correct Java object reference is
provided for the declared Java class
element shown in the input tab of this
activity.
TIBCO-BW- Activity output data conversion error. Ensure that the unsupported data types
PALETTE- Exception [{0}] occurred while trying to are not utilized or referenced in your
JAVA-500014 create the activity output data. [{1}] Java class.
TIBCO-BW- The Java class [{0}] is not found in the Ensure that that the specified class file
PALETTE- classpath. Encountered is contained in the classpath.
JAVA-500017 ClassNotFoundException [{1}].
TIBCO-BW- Activity input error. The activity Ensure that the correct values are
PALETTE- received an incorrect value for the provided for the constructor parameter
JAVA-500019 method parameters. elements that are in the activity input
IllegalArgumentException occurred tab.
while trying to construct an instance of
the Java class [{0}]: [{1}]

124
TIBCO-BW- Unable to construct an instance of the Correct the error stated in the exception
PALETTE- Java class [{0}]. Encountered exception message and retry.
JAVA-500020 [{1}] [{2}].
TIBCO-BW- The constructor for the Java class [{0}] The exception was raised by the
PALETTE- raised exception [{1}]. [{2}] constructor of the declared Java class.
JAVA-500021 Please refer to the Java class
implementation for details.
TIBCO-BW- Unable to obtain information for the Reconfigure this activity or verify that
PALETTE- method [{0}] from the class [{1}]. the declared Java class has not changed
JAVA-500026 Encountered NoSuchMethodException since the last configuration.
[{2}].
TIBCO-BW- Unable to obtain information for the Correct the error stated in the exception
PALETTE- method [{0}] from the class [{1}]. message and retry.
JAVA-500027 Encountered SecurityException [{2}].
TIBCO-BW- Activity input error. The activity Ensure that the correct values are
PALETTE- received an incorrect value for the provided for the method parameter
JAVA-500031 method parameters. When attempting elements that are in the activity input
to invoke the method [{0}], encountered tab.
IllegalArgumentException [{1}].
TIBCO-BW- Activity input error. The activity Ensure that the correct Java object
PALETTE- received an incorrect Java object for the reference is provided for the declared
JAVA-500032 declared Java class [{0}]. The activity Java class element shown in the input
required an instance of the Java class tab of this activity. Ensure that the
[{1}], but received an instance of the classpath refers to the correct declared
Java class [{2}]: [{3}] class.
PALETTE- received an incorrect Java object for the reference is provided for the declared
JAVA-500033 declared Java class [{0}]. The Java object Java class element shown in the input
received is not compatible with the Java tab of this activity. Ensure that the
object required by this activity. The classpath refers to the correct declared
activity required an instance of the Java class.
class [{1}]: [{2}]
PALETTE- received 'null' value for the for the reference is provided for the declared
JAVA-500034 declared Java class. The activity Java class element shown in the input
required an instance of the class [{0}], tab of this activity.The preceding
but received a 'null'. activity that provides the input value
for this activity should not produce a
null for its output.
TIBCO-BW- Unable to invoke the method [{0}]. Correct the error stated in the exception
PALETTE- Encountered exception [{1}] [{2}]. message and retry.
JAVA-500035

125
TIBCO-BW- Unable to invoke the cleanup method Correct the error stated in the exception
PALETTE- [{0}]. Encountered exception [{1}] [{2}]. message and retry.
JAVA-500036
TIBCO-BW- The method [{0}] raised exception [{1}]. The exception was raised by the
PALETTE- [{2}]. method of the specified Java class.
JAVA-500037 Please refer to the declared class
TIBCO-BW- The cleanup method [{0}] raised The exception was raised by the
PALETTE- exception [{1}]. [{2}]. method of the specified Java class.
JAVA-500038 Please refer to the declared class
PALETTE- required instance of class [{0}], but reference is provided for the declared
JAVA-500042 received a 'null' value for the declared Java class element shown in the input
Java class. tab of this activity.The preceding
activity that provides the input value
for this activity should not produce a
null for its output.
PALETTE- received incorrect Java object for the reference is provided for the declared
JAVA-500043 declared Java class. The activity Java class element shown in the input
required an instance of a class [{0}], but tab of this activity. Ensure that the
received instance of a class [{1}]. classpath refers to the correct declared
class.
TIBCO-BW- Data Conversion error. When Ensure that unsupported data types are
PALETTE- attempting to convert Java object to not utilized or referenced in your Java
JAVA-500046 XML data encountered exception [{0}]. class.
TIBCO-BW- Data Conversion error. When Ensure that unsupported data types are
PALETTE- attempting to convert XML data to Java not utilized or referenced in your Java
JAVA-500047 object encountered exception [{0}]. class.
TIBCO-BW- Runtime error. Illegal onEvent(Object Remove the onEvent(Object output)

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

PALETTE- by the getOutputObjectType() does not
JAVA-500065 match with the type that is passed in to
onEvent(Object object).
TIBCO-BW- The Java Process Starter onstop method The exception was raised by the
PALETTE- [{0}] raised exception [{1}]. [{2}]. 'onStop' method of the specified Java
JAVA-500064 class. Please refer to the declared class

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

PALETTE- the Class=[{0}], Cause=[{1}]
JAVA-501067
TIBCO-BW- Internal error occurred. Method=[{0}] Make sure the Class referenced the
PALETTE- references a Class=[{1}] no longer exists. method is valid.
JAVA-501069 Cause=[{2}]
TIBCO-BW- Activity input error. The activity does Ensure that the input content is not
PALETTE- not receive proper input. empty.
JAVA-500070
TIBCO-BW- Unable to obtain information for the Reconfigure this activity or verify that
PALETTE- method [{0}] from the class [{1}]. the declared Java class has not changed
JAVA-500071 since the last configuration.
JDBC Palette Error Codes

the JDBC palette.
TIBCO-BW- The JDBC activity [{0}] is NOT part of a This is an internal product error.
PALETTE- JDBC Transaction Group. However the Contact TIBCO Support.
JDBC-000001 activity references the same shared
resource as used in the group
TIBCO-BW- The JDBC activity [{0}] is first activity in This is a debug message and resolution
PALETTE- the JDBC Transaction. is not applicable.
JDBC-200001
TIBCO-BW- JDBC activity [{0}] initialized This is a debug message and resolution
PALETTE- successfully. is not applicable.
JDBC-200002
TIBCO-BW- JDBC activity [{0}] task submitted to This is a debug message and resolution
PALETTE- Threadpool for execution is not applicable.
JDBC-200003
TIBCO-BW- Executing SQL Statement [{0}] for This is a debug message and resolution
PALETTE- activity [{1}]. is not applicable.
JDBC-200004
TIBCO-BW- Connection received from Datasource This is a debug message and resolution
PALETTE- for activity [{0}]. is not applicable.
JDBC-200005

127
TIBCO-BW- Parameters set for activity [{0}] with sql This is a debug message and resolution
PALETTE- statement [{1}]. is not applicable.
JDBC-200006
TIBCO-BW- Output for activity [{0}] is [{1}]. This is a debug message and resolution
JDBC-200007
TIBCO-BW- Executing SQL Statement for activity This is a debug message and resolution
PALETTE- [{0}]. is not applicable.
JDBC-200008
TIBCO-BW- Executing Prepared Statement for

PALETTE- activity [{0}].
JDBC-200009
TIBCO-BW- Successfully executed sql statement [{0}] This is a debug message and resolution
PALETTE- for activity [{1}]. is not applicable.
JDBC-200010
TIBCO-BW- Last subset reached for activity [{0}]. This is a debug message and resolution
JDBC-200011
TIBCO-BW- Process in subset output for activity This is a debug message and resolution
PALETTE- [{0}] with noofRecords [{1}] is [{2}]. is not applicable.
JDBC-200012
TIBCO-BW- All Parameters set successfully on This is a debug message and resolution
PALETTE- Statement for activity [{0}]. is not applicable.
JDBC-200013
TIBCO-BW- Number of updates for JDBC Update This is a debug message and resolution
PALETTE- activity is [{0}]. is not applicable.
JDBC-200014
TIBCO-BW- Number of updates for JDBC Update This is a debug message and resolution
PALETTE- activity is 0. Executing Insert Statement is not applicable.
JDBC-200015 [{0}] since activity is in Upsert mode.
TIBCO-BW- Batch updates failed on update number Check the activity configuration and if
PALETTE- [{0}]. the database is up.
JDBC-500001
TIBCO-BW- Invalid procedure name specified. Check the activity configuration

PALETTE- Procedure name can not be null. Procedure name field.
JDBC-500002
TIBCO-BW- {0} input parameters declared in the Check the activity configuration
PALETTE- SQL statement but no input parameters Prepared Parameters table.
JDBC-500003 provided.

128
TIBCO-BW- Duplicate field name [{0}] found. Modify the query and create unique
PALETTE- Modify the query and create unique aliases for duplicate fields.
JDBC-500004 aliases for duplicate fields.
TIBCO-BW- Improper SQL statement used. {0} Check the syntax of the SQL Statement
PALETTE- specified.
JDBC-500005
TIBCO-BW- Exception occurred occurred when Check the Shared Resource

PALETTE- attempting to create a JDBC Connection configuration this activity is configure
JDBC-500006 for JDBC Transaction. with and also that the database is
running.
TIBCO-BW- Missing Input Value for required Check the input tab of the activity and
PALETTE- Column [{0}]. set the column value
JDBC-500007
TIBCO-BW- SQL Exception occurred (SQL STATE = Check the activity configuration and the
PALETTE- {0}) - detailMessage - {1} state of the database the activity is
JDBC-500009 connected to.
TIBCO-BW- {0} is not a valid timezone. Check the activity configuration input
PALETTE- tab and enter a valid timezone
JDBC-500010
TIBCO-BW- Could not create Connection to server Check the JDBC Connection Shared
PALETTE- using Shared Resource [{0}]. Resource configuration which is
JDBC-500011 configured on the activity.
TIBCO-BW- INVALID_JDBC_ACTIVITY_CONFIGU Check the activity configuration and

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

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

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

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

129
TIBCO-BW- BATCH_UPDATE_WITHOUT_PREPA Check the SQL statement in the activity

PALETTE- RED_PARAMS = Batch Update mode configuration to ensure that it is a SQL
JDBC-500016 works only with Prepared Statements statement with prepared parameters.
TIBCO-BW- JDBC Connection login timed out. Check the configuration details or
PALETTE- increase the login timeout.
JDBC-500019
JMS Palette Error Codes

the ActiveMatrix BusinessWorks JMS palette.
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-BW- {0}
PALETTE-
JMS-400001
TIBCO-BW- Invalid configuration data. JMS Check activity configuration for JMS
PALETTE- connection reference is not specified. Connection Reference.
JMS-500001
TIBCO-BW- Invalid configuration data. Specified Check activity configuration for JMS
PALETTE- connection reference is not found in Connection Reference.
JMS-500002 repository. {0}
TIBCO-BW- Invalid configuration data. JMS Check activity configuration for the JMS
PALETTE- destination is not specified. Destination field.
JMS-500003
TIBCO-BW- Error occurred when attempting to Check activity configuration for the
PALETTE- create Durable Subscriber Durable Subscription name box and if
JMS-500004 JMS server is running.

130
TIBCO-BW- Failed to create connection to the JMS Check JMS Connection shared resource
PALETTE- server. {0} configuration and if the JMS server is
JMS-500005 running.
TIBCO-BW- Unable to create a session to receive Check JMS Connection shared resource
PALETTE- messages [{0}]. configuration and if the JMS server is
JMS-500006 running.
TIBCO-BW- Unable to create a reply session/ Check JMS Connection shared resource
PALETTE- producer [{0}] configuration and if the JMS server is
JMS-500007 running.
TIBCO-BW- Unable to find destination [{0}] on JMS Check JMS Server if it the destination
PALETTE- server name specified in the error message
JMS-500008 exists.
TIBCO-BW- Error occurred when attempting to Check JMS Connection shared resource
PALETTE- create MessageConsumer configuration and if the JMS server is
JMS-500009 running.
TIBCO-BW- Error occurred when attempting to Check JMS Connection shared resource
PALETTE- resolve destination [{0}] configuration and if the JMS server is
JMS-500010 running.
TIBCO-BW- Invalid configuration data. JMS Reply Check the activity configuration and
PALETTE- To Destination Not Specified. specify a value in the JMS Reply To
JMS-500011 field.
TIBCO-BW- Error occurred when attempting to send Check the activity configuration, input
PALETTE- a JMS message data, JMS Connection shared resource
JMS-500012 configuration and if the JMS server is
running.
TIBCO-BW- Error occurred when attempting to Check the activity configuration, JMS
PALETTE- receive a JMS message Connection shared resource
running.
TIBCO-BW- Error occurred when attempting to Check the activity configuration, JMS
PALETTE- confirm a JMS message Connection shared resource
running.
TIBCO-BW- Failed to Reply for JMS There is no resolution for this error.
PALETTE- ProcessStarter[{0}]. This error can occur
JMS-500015 if the JMSReply activity is executed
after recovering from a check-pointed
BusinessWorks process instance.

131
Mail Palette Error Codes

the Mail palette.

MAIL-000001

MAIL-100001

MAIL-200001

MAIL-300001 activity. Resolution is not applicable.

MAIL-400001 activity execution.
TIBCO-BW- Invalid input data. Reason: Error Ensure the destination addresses given
PALETTE- parsing input data. are valid.
MAIL-500005
TIBCO-BW- Invalid input data. Reason: Both the Ensure that both the comma and
PALETTE- comma and semicolon cannot be used semicolon cannot be used at same time
MAIL-500007 at same time to separate addresses: [{0}] to separate addresses.
TIBCO-BW- Error connecting to the mail server. Ensure the host provided is valid.
PALETTE- Reason: unknown host - connection
MAIL-500020 parameters: [{0}].
TIBCO-BW- Error building mail message. Cause: Ensure the input message details are
PALETTE- [{0}]. properly given.
MAIL-500033
TIBCO-BW- From address [{0}] is not valid. Ensure the From address must not be
PALETTE- empty or null string
MAIL-500035
TIBCO-BW- Error sending mail message. Ensure the SMTP shared resource
PALETTE- configuration is appropriately specified.
MAIL-500036
TIBCO-BW- The system cannot find the file Ensure the file exists at a given location.
PALETTE- specified: [{0}].
MAIL-500037

132
TIBCO-BW- Invalid recipient address in To, CC or Ensure recipient addresses given must
PALETTE- BCC [{0}, {1}, {2}]. be valid.
MAIL-500038
TIBCO-BW- Host can not be null Ensure the host must not be null value.
PALETTE-
MAIL-500001
TIBCO-BW- Username can not be null when using Ensure the username value must not be
PALETTE- Authentication null when using authentication.
MAIL-500002
TIBCO-BW- Password can not be null when using Ensure the password value must not be
PALETTE- Authentication null when using authentication.
MAIL-500003
TIBCO-BW- Error closing mail server connection. Ensure the Mail receiver configuration
PALETTE- Cause: [{0}]. is appropriately given.
MAIL-500004
TIBCO-BW- Mail provider for protocol [{0}] not Ensure that the mail provider jar is in
PALETTE- found. Make sure that the provider jar java classpath.
MAIL-500008 is in java classpath.
TIBCO-BW- Configuration error in field [{0}] the Ensure the host name for mail receiver
PALETTE- value must be a valid Host Name. must be valid.
MAIL-500009
TIBCO-BW- Error connecting to the mail server - Ensure the mail server is up or check
PALETTE- connect exception; connection whether the connection parameters are
MAIL-500010 parameters: [Host:{0}, Port:{1}, User:{2}]. properly 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-500011 invalid password.
TIBCO-BW- The default mail folder was not found Ensure the Mail receiver configuration
PALETTE- on mail server. is appropriately given.
MAIL-500012
TIBCO-BW- The INBOX mail folder was not found Ensure the Mail receiver configuration
PALETTE- on mail server. is appropriately given.
MAIL-500013
TIBCO-BW- Error getting folder on mail server. Ensure the Mail receiver configuration
PALETTE- is appropriately given.
MAIL-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-500015 unchecked or don't use explicit confirm.

133
TIBCO-BW- Error connecting to the mail server Ensure the mail server is up or verify
PALETTE- using connection parameters: [{0}] connection parameters.
MAIL-500021
TIBCO-BW- Error while polling mail server: cannot Ensure the mail server is up or verify
PALETTE- open INBOX folder. connection parameters.
MAIL-500022
TIBCO-BW- Error parsing received mail. Ensure the Mail receiver configuration
PALETTE- is appropriately given.
MAIL-500023
TIBCO-BW- Error while polling mail server: cannot Ensure the mail server is up or verify
PALETTE- close INBOX folder. connection parameters.
MAIL-500024
TIBCO-BW- Unexpected error while polling mail Ensure the mail server is up or verify
PALETTE- server. connection parameters.
MAIL-500025
TIBCO-BW- The Receive Mail ProcessStarter activity This is an internal product error.
MAIL-500026 due to exception [{1}] since it is in the
stopped state.
TIBCO-BW- Marking msg {0} for confirmation. This is an informational message and it
MAIL-300001 activity. Resolution is not applicable.
Parse Palette Error Codes

the Parse palette.

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

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

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

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

134

PALETTE- highlights situations that may affect
PARSE-400001 the activity execution.
TIBCO-BW- Cannot find data format schema resource Check if Data format shared
PALETTE- [{0}] resource is configured.
PARSE-500000
TIBCO-BW- Cannot create schema from data format Check if the schema is valid.
PALETTE- schema.
PARSE-500001
TIBCO-BW- Exception in parse eval: [{0}] An error occurred while

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

PALETTE- on Parse Data activity. Ensure
PARSE-500005 either File or String is configured.
TIBCO-BW- Please specify the Input type field. Check configuration of Input type
PALETTE- on Parse Data activity. Ensure
PARSE-500006 either File or String is configured.
TIBCO-BW- Data format resource not specified. Check if Data format shared
PALETTE- resource is configured on the
PARSE-500007 activity.
TIBCO-BW- Specify the data format resource. Check if Data format shared
PALETTE- resource is configured on the
PARSE-500008 activity.
TIBCO-BW- File [{0}] cannot be opened using Check the encoding configruation
PALETTE- encoding method [{1}] on Parse Data activity. Ensure
PARSE-500009 encoding supported by file is
selected.
TIBCO-BW- Format Type must be selected. Ensure that Format type is

PALETTE- configured on Data Format shared
PARSE-500011 resource.

135
TIBCO-BW- Line is too long. Specified Line Delimiter Check field offsets configuration on
PALETTE- may not match file content. Data Format shared resource.
PARSE-500012
TIBCO-BW- There are not enough data for the number Check field offsets configuration on
PALETTE- of required fields in a row. Data Format shared resource.
PARSE-500013
TIBCO-BW- Error while parsing headers in the mime Ensure that the input message has
PALETTE- message. MIME headers.
PARSE-500014
TIBCO-BW- An I/O exception occurred while parsing Ensure that the SOAP payload is
PALETTE- SOAP payload in the root part. well formed and valid.
PARSE-500015
TIBCO-BW- An Unexpected exception occurred while UNEXPECTED_EXCEPTION.resol

PALETTE- parsing Message. Root cause is [{0}] ution =This is an internal product
PARSE-5000016 error. Contact TIBCO Support
TIBCO-BW- The SOAP Message doesn't exist in the Ensure that the input message has
PALETTE- Root part. SOAP payload in it.
PARSE-500017
TIBCO-BW- Soap Envelope has invalid XML content. Ensure that the SOAP payload is
PALETTE- valid and well formed.
PARSE-500018
TIBCO-BW- One or more mime parts have same Ensure that in input message does
PALETTE- Content-Id value in the Mime Message. not have same content id for
PARSE-500019 different mime parts.
TIBCO-BW- The xop:Include element must have an Ensure that in the SOAP payload,
PALETTE- 'href' attribute. the xop:Include element has href
PARSE-500020 attribute.
TIBCO-BW- Content_Id header is not found in mime Ensure that the each mime part has
PALETTE- part of the Mime Message. content-id header and
PARSE-500021 corresponding value.
TIBCO-BW- Invalid Content Type Field in the Mime Ensure that media type starts with
PALETTE- Message. 'multipart'.
PARSE-500022
TIBCO-BW- Boundary attribute not found in the Ensure that the 'boundary' attribute
PALETTE- Mime Message. is not missing in the mime header.
PARSE-500023
TIBCO-BW- startinfo parameter is missing in the Ensure that 'startinfo' attribute is

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

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

PALETTE- than max Field Offset.
LENGTH=Line length [{0}]
PARSE-500030
is less than max Field Offset [{1}]
ERROR_LINE_LESS_THAN_MAX_
LENGTH.errorCode=500030
ERROR_LINE_LESS_THAN_MAX_
LENGTH.resolution
Rendezvous Palette Error Codes

the ActiveMatrix BusinessWorks Rendezvous palette.

RV-000001

RV-100001

RV-200001

137

RV-300001 activity. Resolution is not applicable.
TIBCO-BW- Advisory: [{0}] subject, message [{1}] This is an informational message and it
TIBCO-BW- Listening on subject [{0}] This is an informational message and it

TIBCO-BW- Received message on subject [{0}] This is an informational message and it

TIBCO-BW- Not confirming message because it has This is an informational message and it
PALETTE- already been confirmed seqno : [{0}] highlights the runtime progress of the
TIBCO-BW- Sending RV request on subject [{0}] This is an informational message and it

TIBCO-BW- RV Listening on reply subject [{0}] This is an informational message and it

TIBCO-BW- RV Publishing Message on subject [{0}] This is an informational message and it


RV-400001 activity execution.
TIBCO-BW- RV Message encoding [{0}] not This is a warning message and it

PALETTE- supported. highlights situations that may affect the
RV-400003 activity execution.
TIBCO-BW- Error in sending message This is an internal product error.

RV-500001
TIBCO-BW- Error serializing the message This is an internal product error.

RV-500002
TIBCO-BW- Error in processing event: [{0}] Look at the exception for more
PALETTE- information.
RV-500004

138
TIBCO-BW- Cannot create TibrvQueue: [{0}] Look at the exception for more
PALETTE- information.
RV-500005
TIBCO-BW- Cannot create reply listener for subject: Look at the exception for more
PALETTE- [{0}] information.
RV-500007
TIBCO-BW- Cannot activate TIBRV listener for Look at the exception for more
PALETTE- subject: [{0}] : Exception: [{1}] information.
RV-500008
TIBCO-BW- Error in sending reply This is an internal product error.

RV-500009
TIBCO-BW- Error Occurred while receiving a RV Look at the exception for more
PALETTE- Message so the RV EventSource activity information.
RV-500015 [{0}] failed to a generate a new event
due to exception [{1}]
TIBCO-BW- Advisory listening queue caught Look at the exception for more
PALETTE- exception: [{0}] information.
RV-500018
TIBCO-BW- The RV Subscriber ProcessStarter This is an internal product error.

PALETTE- activity [{0}] failed to a generate a new Contact TIBCO Support.
RV-500010 event due to exception [{1}] since it is in
the stopped state.
TIBCO-BW- The WaitforRVMessage Signal In This is an internal product error.

RV-500011 event due to exception [{1}] since it is in
the stopped state.
TIBCO-BW- Failed to Reply for [{0}]. This error can Make sure that RV reply to request
PALETTE- occur if the RV reply to request activity activity must be used before checkpoint
RV-500012 is executed after recovering from a is taken.
check-pointed BusinessWorks process
instance.
REST and JSON Palette Error Codes

the TIBCO ActiveMatrix BusinessWorks™ REST and JSON palette.
REST Palette Error Messages
TIBCO-BW-PALETTE-REST-100005 An An error occurred

while parsing.

139
TIBCO-BW-PALETTE-REST-100006 Error occurred during

JSON transformation.
TIBCO-BW-PALETTE-REST-100008 The selected encoding

<<Encoding Name>> is not
valid.
TIBCO-BW-PALETTE-REST-100009 Encoding error occurred.
TIBCO-BW-PALETTE-REST-100010 The encoded bytes content

is empty.
TIBCO-BW-PALETTE-REST-100012 The input document's root

element does not match
the desired output's root
element.
TIBCO-BW-PALETTE-REST-100013 An error occurred while

validating output.
TIBCO-BW-PALETTE-REST-100014 An error occurred in Check RenderJSON activity

render activity: Improper configuration.
Invocation: Schema does
not have top level array.
TIBCO-BW-PALETTE-REST-100016 An error occurred while Check ParseJSON activity

converting JSON to XML. configuration.
TIBCO-BW-PALETTE-REST-100040 No schema definition was

found for specified type
TIBCO-BW-PALETTE-REST-200029 Elements with

Anonymous Types are not
supported for XSD mode.
Please select an Element
with a named type.
TIBCO-BW-PALETTE-REST- Missing value for ACCEPT Provide a value for the ACCEPT
200030 HTTP header. Since HTTP Header.
CUSTOM Response Type
is selected in configuration
a value MUST be provided
for the ACCEPT HTTP
Header.

140
TIBCO-BW-PALETTE-REST- Missing value for Provide a value for the for the
200031 CONTENT-TYPE HTTP CONTENT-TYPE HTTP Header.
header. Since CUSTOM
Request Type is selected in
configuration a value
MUST be provided for the
CONTENT-TYPE HTTP
Header.
TIBCO-BW-PALETTE-REST- Username or Password Check the Identity Shared Resource

200032 cannot be null when using configuration that is used by the
Basic Authentication with HTTP Client Shared Resource to
REST Invoke Activity. make sure the password or the
username is not null.
TIBCO-BW-PALETTE-REST-200033 An IOException was Check client/server shared resources

thrown while trying to configuration.
execute the HTTP Method
at resource path.
TIBCO-BW-PALETTE-REST-400000 Spec file is not found for Provide a valid JSON spec file for
JSON transformation. transformation.
Please provide the path to
the file or a valid JSON
transformation spec string.
TIBCO-BW-PALETTE-REST-400001 Input JSON String not Provide a valid JSON String file for
found. Please provide a transformation.
valid JSON string for
transformation.
TIBCO-BW-PALETTE-REST-400002 Input spec file is not valid. Provide a valid JSON spec file for
Please provide a valid spec transformation.
file for JSON for
transformation.
TIBCO-BW-PALETTE-REST-400003 Input JSON is not valid. Provide a valid JSON string for
Please provide a valid transformation.
JSON string for
transformation.
TIBCO-BW-PALETTE-REST-400004 JSON Transformation

could not be completed.
TIBCO-BW-PALETTE-REST-400005 JSON Transformation Input file and spec file do not match.
returned null. Please Provide valid input.
provide a valid Input Json
and Spec Json Content.
TIBCO-BW-PALETTE- Client received a 4xx Check Invoke REST API activity

REST-2000027 response for invocation at configuration.
resource path.

141
TIBCO-BW-PALETTE- Client received a 5xx Check service configuration.

REST-2000028 response for invocation at
resource path.
TCP Palette Error Codes

the TIBCO ActiveMatrix BusinessWorks™ TCP palette.

TCP-200001
TIBCO-BW- Cannot start TCP Receiver on Host [{0}], Please correct Host and Port and retry.
PALETTE- Port [{1}]. Reason: [{2}].
TCP-500001
TIBCO-BW- Invalid Port; port must be numeric. The Port must be numeric.
PALETTE- Error: [{0}]
TCP-500003
TIBCO-BW- No value specified for the 'data' input Please specify value in the 'data' input
PALETTE- field. field.
TCP-500004
TIBCO-BW- Error reading TCP data. Reason: [{0}]. This is an internal product error.
PALETTE- Contact TIBCO Support..
TCP-500006
TIBCO-BW- Error opening TCP Connection. Reason: This is an internal product error.
PALETTE- [{0}]. Contact TIBCO Support..
TCP-500008
TIBCO-BW- Error opening TCP Connection. Reason: Invalid Host, Please correct the error
PALETTE- Host [{0}] unknown. and retry.
TCP-500009
TIBCO-BW- Exception closing TCP Connection. This is an internal product error.

PALETTE- Reason: [{0}]. Contact TIBCO Support..
TCP-500013
TIBCO-BW- Could not read from TCP connection. The input connection is either invalid or
PALETTE- The input connection is either invalid or closed. Please correct the error and
TCP-500014 closed. retry.
TIBCO-BW- Could not write to TCP connection. The The input connection is either invalid or
PALETTE- input connection is either invalid or closed. Please correct the error and
TCP-500015 closed. retry.

142
TIBCO-BW- Cannot start TCP Receiver on Check Host and Port and retry.
PALETTE- Host=[{0}], Port=[{1}]. Another TCP
TCP-500016 Receiver is already running with the
same configuration.
TIBCO-BW- Error closing TCP connection. Reason: Match the input connection key while
PALETTE- No connection is available which closing connection.
TCP-500017 matches the input connection key.
TIBCO-BW- Error writing data. Reason: [{0}]. This is an internal product error.
PALETTE- Contact TIBCO Support...
TCP-500018
TIBCO-BW- Timeout while reading TCP data Possible causes for this error are:(1)The
PALETTE- data is being read before it is written.
TCP-500021 (2)If the data that is written is text/
binary and it is being read as binary/
text.(3)If the data is written with/
without separator and is being read
without/with separator.
TIBCO-BW- IOException occurred while retrieving This is an internal product error.

PALETTE- XML Output for activity [{0}]. Contact TIBCO Support..
TCP-500022
TIBCO-BW- The TCP Receiver Process Starter This is an internal product error.
TCP-500023 event due to exception [{1}] since it is in
the stopped state.
TIBCO-BW- The Wait For TCP Request activity [{0}] This is an internal product error.
PALETTE- failed to a generate a new event due to Contact TIBCO Support.
TCP-500024 exception [{1}] since it is in the stopped
state.
TIBCO-BW- Invalid SSL Configurations. Reason: There is error with the SSL
PALETTE- [\{0}]. Configurations. Correct the SSL
TCP-500025 Configurations and then retry.
TIBCO-BW- Cannot start TCP Receiver on Port Correct Port and retry.
PALETTE- [\{0}]. Reason: [\{1}].
TCP-500026

143
XML Palette Error Codes

the ActiveMatrix BusinessWorks XML palette.

XML-000001

XML-100001

XML-200001

XML-300001 activity. Resolution is not applicable.

XML-400001 activity execution.
TIBCO-BW- Internal error occurred Class=[{0}], Please Contact TIBCO Support

PALETTE- Method=[{1}], Reason=[{2}].
XML-500000
TIBCO-BW- Unable to serialize the XML due to Ensure the input XML node is properly
PALETTE- exception [{0}]. given.
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 XSLT Ensure the provided input XML and
PALETTE- transformation. Exception detail [{1}]. input XSLT is properly given.
XML-500003
TIBCO-BW- The XSLT transformation Stylesheet Ensure to provide the XSLT either in the
PALETTE- provided for the activity input is empty configuration or in the activity input.
XML-500004 or null.
TIBCO-BW- The selected encoding [{0}] is not valid. Ensure the provided encoding is valid.
PALETTE-
XML-500005
TIBCO-BW- Encountered encoding error [{0}]. Ensure the provided encoding is

PALETTE- correct.
XML-500006

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

145
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-FRWK-000010 Shared Resource Creation Error. The ResourceDependencyHandler

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

DeploymentUnit [{4}:{5}]{6}
TIBCO-BW-SR-FRWK-503000 Unable to start SharedResource [{0}] {1}. <Reason>: {2}
TIBCO-BW-SR- Unable to get IdentitySubject from Trinity for {0}.

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

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

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

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

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

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

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

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

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

THREADPOOL-500002

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

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

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

THREADPOOL-500008
Data Format Error Codes

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

DATAFORMAT-200001 resolution is not applicable.
TIBCO-BW-SR- Failed to {0} Data Format resource Check the configuration of Data
DATAFORMAT-500000 [{1}] Format shared resource.
FTP Connection Error Codes

This section describes the error messages that can be reported by the FTP Connection shared resource.
TIBCO-BW-SR- Failed to {0} FTP Connection resource Please correct the error and retry.
FTP-500004 [{1}]
TIBCO-BW-SR- {0} This is a debug message and resolution

FTP-200001 is not applicable.

147
HTTP Client Error Codes

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

HTTP- is not applicable.
CLIENT-200001
TIBCO-BW-SR- Failed to {0} HTTP Client resource [{1}] Check the configuration of Http Client
HTTP- resource.
CLIENT-500000
TIBCO-BW-SR- User name or Password is not specified Specify user name and password in
HTTP- in Identity Identity shared resource.
CLIENT-500001
TIBCO-BW-SR- User name or Password is not set in Check if user name and password is
HTTP- identity resource for basic Http specified in Identity shared resource.
CLIENT-500002 authentication
HTTP Connector Error Codes

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

CONNECTOR-100001 resolution is not applicable.
TIBCO-BW-SR-HTTP- {0} This is a debug message and

CONNECTOR-200001 resolution is not applicable.
TIBCO-BW-SR-HTTP- Error while stopping HTTP endpoint This is an informational message and
CONNECTOR-300003 [{0}] it highlights the runtime progress of
the shared resource. Resolution is not
applicable.
TIBCO-BW-SR-HTTP- Error while stopping HTTP context This is an informational message and
CONNECTOR-300004 [{0}] it highlights the runtime progress of
the shared resource. Resolution is not
applicable.
TIBCO-BW-SR-HTTP- Failed to {0} HTTP Connector Check the configuration of Http

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

CONNECTOR-500003 resource [{0}] with the specified Connector resource.
configuration. Check the
configuration settings.

148
TIBCO-BW-SR-HTTP- Unable to start HTTP Server instance Check the configuration of Http
CONNECTOR-500004 for resource [{0}] Connector resource.
TIBCO-BW-SR-HTTP- Failed to activate HTTP endpoint Check the exception and correct the
CONNECTOR-500005 [{0}] because of exception [{1}] configuration of Http Connector
resource or Http Event source.
TIBCO-BW-SR-HTTP- The HTTP server instance cannot be Check the configuration of Http
CONNECTOR-500006 started, because it is not configured Connector resource or Http Event
source.
TIBCO-BW-SR-HTTP- The HTTP server instance [{0}] System exception.

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

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

CONNECTOR-500010 [{0}]
TIBCO-BW-SR-HTTP- Failed to create HTTP Connector Check the port configured on Http
CONNECTOR-500012 resource [{0}] configured with port Connector resource is not in use.
[{1}]
TIBCO-BW-SR-HTTP- LDAP resource is not configured on Please check if LDAP resource is

CONNECTOR-500013 HTTP Connector resource [{0}]. configured on Http Connector.
Java Global Instance Error Codes

This section describes the error messages that can be reported by the Java Global Instance shared resource.
TIBCO-BW-SR- BW6_EXCP_NAME_EXISTS = A This is an internal product error.

JAVA-500001 connector configuration with the name Contact TIBCO Support.
"[{0}" already exists with pid [{1}]
TIBCO-BW-SR- Unable to find Application bundle [{0}] This is an internal product error.
JAVA-500002 Contact TIBCO Support.
TIBCO-BW-SR- Unable to construct an instance of the Correct the error stated in the exception
JAVA-500003 Java class [{0}]. Encountered exception message and retry.
[{1}] [{2}].

149
TIBCO-BW-SR- Activity input error. The activity Ensure that the correct values are
JAVA-500004 received an incorrect value for the provided for the constructor parameter
method parameters. elements that are in the activity input
IllegalArgumentException occurred tab.
while trying to construct an instance of
the Java class [{0}]: [{1}]
TIBCO-BW-SR- The constructor for the Java class [{0}] The exception was raised by the
JAVA-500005 raised exception [{1}]. [{2}] constructor of the declared Java class.
Please refer to the Java class
TIBCO-BW-SR- The Java class [{0}] is not found in the Ensure that the specified class file is
JAVA-500006 classpath. Encountered contained in the classpath.
ClassNotFoundException [{1}].
TIBCO-BW-SR- Unable to obtain information for the Reconfigure this activity or verify that
JAVA-500007 method [{0}] from the class [{1}]. the declared Java class has not changed
Encountered NoSuchMethodException since the last configuration.
[{2}].
TIBCO-BW-SR- Unable to obtain information for the Reconfigure this activity or verify that
JAVA-500008 cleanup method [{0}] from the class the declared Java class has not changed
[{1}]. NoSuchMethodException since the last configuration.
occurred. [{2}]
TIBCO-BW-SR- The cleanup method [{0}] raised The exception was raised by the
JAVA-500009 exception [{1}]. [{2}] method of the specified Java class.
Please refer to the declared class
TIBCO-BW-SR- Unable to invoke the cleanup method Correct the error stated in the exception
JAVA-500010 [{0}]. Exception [{1}] occurred. [{2}] message and retry.
TIBCO-BW-SR- Unable to invoke the cleanup method The exception was raised by the
JAVA-500012 [{0}]. Encountered exception [{1}] [{2}]. method of the specified Java class.
Please refer to the declared class
TIBCO-BW-SR- Received an incorrect value for the Ensure that the correct values are
JAVA-500014 method [{0}] parameter to get access the provided for the method parameter to
BW Module properties. Exception get access the BW Module properties.
occurred: [{1}]

JAVA-200001 is not applicable.
TIBCO-BW-SR- Failed to {0} Java Global Instance

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

JAVA-000001 does not exist with pid [{0}]

150
JMS Connection Error Codes

This section describes the error messages that can be reported by the JMS Connection shared resource.
TIBCO-BW-SR- {0}
JMS-100001
TIBCO-BW-SR- {0}
JMS-200001
TIBCO-BW-SR- {0}
JMS-300001
TIBCO-BW-SR- {0}
JMS-400001
TIBCO-BW-SR- Failed to {0} JMS Connection resource Check JMS Connection Shared resource
JMS-502000 [{1}] configuration
JDBC Connection Error Codes

This section describes the error messages that can be reported by the JDBC Connection shared resource.
TIBCO-BW-SR- Received an update request for existing This is an informational message and it
JDBC-300001 configuration with PID=[{0}] and highlights the runtime progress of the
Shared resource name [{1}] shared resource. Resolution is not
applicable.
TIBCO-BW-SR- Updating Password for Shared This is an informational message and it

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

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

151
TIBCO-BW-SR- Adding new configuration for Shared This is an informational message and it
JDBC-300006 Resource with name [{0}] highlights the runtime progress of the
applicable.
TIBCO-BW-SR- Deleting Configuration for Shared This is an informational message and it

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

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

JDBC-400003 for driver [{0}]. The shared resource {1} message prints out information about a
might NOT resolve. The configuration driver not being loaded at the current
will wait for a driver to be available. time. Since the framework has not
finished loading, there is a chance of the
driver being loaded later. It is safe to
ignore this message.
TIBCO-BW-SR- Failed to {0} JDBC Connection resource A JDBC Connection lifecycle error has
JDBC-502000 [{1}]. occurred. Check the connection
configuration and restart the
application if necessary.
TIBCO-BW-SR- Exception occurred while trying to Check the connection configuration and
JDBC-500001 retrieve a connection from the JDBC if the database is up and running.
Connection pool
TIBCO-BW-SR- Failed to create a new connection to Check the connection configuration and
JDBC-500002 database server. Database URL [{0}], if the database is up and running.
UserName [{1}], SQLSTATE [{2}]

152
TIBCO-BW-SR- The database driver [{0}] is not found. Run the appropriate script using
JDBC-500003 Ensure that DataSourceFactory bundle bwinstall from the bin folder to add the
providing this driver is available in the JDBC driver to the runtime
environment. environment
TIBCO-BW-SR- Destroying all Unused connections. This is a debug message and resolution
JDBC-200001 is not applicable.
TIBCO-BW-SR- Published Event to Event Admin on This is a debug message and resolution
JDBC-200002 topic {0} is not applicable.
TIBCO-BW-SR- Delete Called on configuration that This is an internal product error.

JDBC-000001 does not exist with pid [{0}] Contact TIBCO Support.
JNDI Configuration Error Codes

This section describes the error messages that can be reported by the JNDI Configuration shared resource.
TIBCO-BW-SR- {0}
JNDI-100001
TIBCO-BW-SR- {0}
JNDI-200001
TIBCO-BW-SR- {0}
JNDI-300001
TIBCO-BW-SR- {0}
JNDI-400001
TIBCO-BW-SR- Failed to {0} JNDI 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.

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

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

153
Rendezvous Transport Error Codes

This section describes the error messages that can be reported by the Rendezvous transport shared
resource.
TIBCO-BW-SR- {0} This is an internal product error.

RV-000001 Contact TIBCO Support.
TIBCO-BW-SR- {0} This is a trace message and resolution is

RV-100001 not applicable.

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

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

RV-400001 highlights situations that may affect the
activity execution.
TIBCO-BW-SR- RV Transport Resource configuration This is a warning message and it

RV-400002 error. The CM Name field is not highlights situations that may affect the
configured correctly. If omitted, a activity execution.
unique, non-reusable name will be
generated for the duration of the
transport.
TIBCO-BW-SR- Failed to create RV Transport due to Look at the exception for more
RV-500000 exception [{0}] information.
TIBCO-BW-SR- Failed to {0} RV Transport resource [{1}] This is an internal product error.
RV-500006 Contact TIBCO Support.
SMTP Resource Error Codes

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

MAIL-200001 is not applicable.
TIBCO-BW-SR- Adding new configuration [{0}]. This is an informational message and it

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


154
TIBCO-BW-SR- Mail Session created successfully. This is an informational message and it

TIBCO-BW-SR- Called update on an existing This is a warning message and it

MAIL-400001 configuration [{0}]. Resource will be highlights situations that may affect the
recreated. activity execution.
TIBCO-BW-SR- Problem extracting mail SSL Ensure the SSL shared resource is
MAIL-500001 information from Trinity for JNDI [{0}]. appropriately configured.
TIBCO-BW-SR- Mail Session creation failed. Ensure the smtp shared resource is
MAIL-500002 appropriately configured.
TIBCO-BW-SR- Handler for MimeType [{0}] not found. Ensure the MimeType is valid.
MAIL-500005
TIBCO-BW-SR- Failed to start SMTP Connection Shared Ensure the smtp shared resource is
MAIL-500006 Resource [{0}]. appropriately configured.
TCP Connection
This section describes the error messages that can be reported by the TCP Connection shared resource.
TIBCO-BW-SR- Failed to {0} TCP Connection resource Please correct the error and retry.
TCP-500004 [{1}]

TCP-200001 is not applicable.

155
Legal and Third-Party Notices

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH
EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR
PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE
EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY
OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS
OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE
AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER
LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE
SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH
SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE
LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS
SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE
ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.
This document is subject to U.S. and international copyright laws and treaties. No part of this document
may be reproduced in any form without the written authorization of TIBCO Software Inc.
TIBCO, the TIBCO logo, the TIBCO O logo, TIBCO ActiveMatrix BusinessWorks, TIBCO Rendezvous,
TIBCO Enterprise Message Service, TIBCO Business Studio for BusinessWorks, TIBCO Enterprise
Administrator, TIBCO ActiveSpaces, TIBCO Runtime Agent, and TIBCO Designer 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.
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. Please see the readme.txt file for the availability
of this software version on a specific operating system platform.
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 © 2001-2020. TIBCO Software Inc. All Rights Reserved.

Tibco Activematrix Businessworks™ Error Codes: November 2020

Uploaded by

Copyright:

Available Formats

Tibco Activematrix Businessworks™ Error Codes: November 2020

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Tibco Activematrix Businessworks™ Error Codes: November 2020

Uploaded by

Copyright:

Available Formats

TIBCO ActiveMatrix

Copyright © 2001-2020. TIBCO Software Inc. All Rights Reserved.

Shared Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

TIBCO ActiveMatrix BusinessWorks™ Error Codes

JNDI Configuration Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Legal and Third-Party Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

TIBCO ActiveMatrix BusinessWorks™ Error Codes

TIBCO Documentation and Support Services

How to Access TIBCO Documentation

How to Contact TIBCO Support

You can contact TIBCO Support in the following ways:

● For an overview of TIBCO Support, visit http://www.tibco.com/services/support.

How to Join TIBCO Community

TIBCO ActiveMatrix BusinessWorks™ Error Codes

Message Codes Naming Convention

BX ActiveMatrix BusinessWorks™ Engine Layer

PVM ActiveMatrix BusinessWorks Engine Layer

TIBCO-BW-ADMIN ActiveMatrix BusinessWorks Administrator

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

TIBCO-BW-BINDING- ActiveMatrix BusinessWorks REST Binding

TIBCO-BW-BINDING- ActiveMatrix BusinessWorks SOAP Binding

TIBCO-BW-CORE ActiveMatrix BusinessWorks Engine Layer

TIBCO-BW-FRWK ActiveMatrix BusinessWorks Framework

TIBCO-BW-PALETTE ActiveMatrix BusinessWorks Palette Layer

TIBCO-BW-PALETTE- ActiveMatrix BusinessWorks Palette specific activity implementation

TIBCO-BW-SR ActiveMatrix BusinessWorks Shared Resource API Layer

TIBCO-BW-SR- ActiveMatrix BusinessWorks specific Shared Resource implementation

TIBCO-BW-STATS ActiveMatrix BusinessWorks Stats Collector

TIBCO-THOR-FRWK Thor Framework

TIBCO ActiveMatrix BusinessWorks™ Error Codes

Log Level Error Code

TRACE 100001 - 109999

DEBUG 200001 - 209999

INFO 300001 - 309999

WARN 400001 - 409999

TIBCO ActiveMatrix BusinessWorks™ Error Codes

SOAP Binding Error Codes

Error Codes Error Message Error Resolution

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

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

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

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

TIBCO-BW- Failed to initialize SOAP Binding. BW_SOAP_BINDING_NAME_MISSIN

TIBCO ActiveMatrix BusinessWorks™ Error Codes

Error Codes Error Message Error Resolution

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

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

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

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

TIBCO ActiveMatrix BusinessWorks™ Error Codes

Error Codes Error Message Error Resolution

TIBCO-BW- Failed to create SoapServiceBinding This is a internal resolution message.

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

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

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

TIBCO ActiveMatrix BusinessWorks™ Error Codes

Error Codes Error Message Error Resolution

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

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