When encountering internal errors on Windows platforms during Broker Server operations, what is the immediate course of action advised?

The immediate advised course of action is to contact webMethods Customer Care for assistance .

When the Broker Server encounters a 'field type mismatch' for sequence operations, what corrective action should be taken?

Ensure that sequence operations are performed on fields that are actually defined as sequence types. Specifically, the correct syntax involving the '[]' should be used when accessing sequence fields .

In the event of communication failure between a Broker client and the Broker Host, what are the initial diagnostic steps one should employ?

Verify that TCP/IP services and the remote Broker are active by checking the system and Broker logs for any additional information regarding the error .

How should one handle a situation where an error in processing a filter results from a missing closing quotation mark?

The syntax of the filter should be checked to ensure that the quotation marks are used correctly, thereby eliminating the error related to a missing closing quotation mark .

What should be done when a Broker Server Monitor fails to reread its configuration file?

Ensure the Broker Server Monitor is running and then reinvestigate detailed error messages for the underlying problems .

What is the recommended initial response when the Broker Server configuration file cannot be read due to permissions or existence issues?

The initial response should be to ensure that the configuration file exists and verify that the user has the necessary privileges to read it .

If the Broker Server fails to write a configuration file due to a non-writable file, what should be confirmed before proceeding?

One should confirm that the configuration file exists on the Broker Server and that it is writable before proceeding .

How should the presence of a corrupt document field data in a Broker Server be addressed to maintain operational integrity?

Ensure the validity of documents by verifying that they match their type definitions to prevent corruption .

How can issues related to an error in parsing the syntax of a filter be effectively resolved?

Ensure that the filter string is syntactically correct by validating its overall structure and checking it against potential parsing errors, such as invalid characters or missing quotation marks .

What steps are recommended when experiencing a Broker Server configuration session initialization failure?

Examine the configuration file to confirm the presence of a valid session and review the error messages for further details on the problem .

Open navigation menu

Upload

0% found this document useful (0 votes)

4K views1,020 pages

6-5-1 Webmethods Error Message Reference PDF

Uploaded by

Aishwarya

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

4K views1,020 pages

6-5-1 Webmethods Error Message Reference PDF

Uploaded by

Aishwarya

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

webMethods

Error Message Reference

VERSION 6.5 AND 6.5.1

webMethods, Inc.
South Tower
3877 Fairfax Ridge Road
Fairfax, VA 22030
USA
703.460.2500
http://www.webmethods.com
webMethods Access, webMethods Administrator, webMethods Broker, webMethods Dashboard, webMethods Developer, webMethods Fabric, webMethods
Glue, webMethods Installer, webMethods Integration Server, webMethods Mainframe, webMethods Manager, webMethods Modeler, webMethods Monitor,
webMethods Optimize, webMethods Portal, webMethods Servicenet, webMethods Trading Networks, and webMethods Workflow are trademarks of
webMethods, Inc. webMethods and the webMethods logo are registered trademarks of webMethods, Inc.
Acrobat and Adobe are registered trademarks, and Reader is a trademark of Adobe Systems Incorporated. Amdocs is a registered trademark, and ClarifyCRM
is a trademark of Amdocs. Ariba is a registered trademark of Ariba, Inc. BEA, BEA WebLogic Server, Jolt, and Tuxedo are registered trademarks, and BEA
WebLogic Platform is a trademark of BEA Systems, Inc. Action Request System, BMC Software, PATROL, and Remedy are registered trademarks of BMC
Software, Inc. BroadVision is a registered trademark of BroadVision, Inc. ChemeStandards and CIDX are trademarks of Chemical Industry Data Exchange.
Unicenter is a registered trademark of Computer Associates International, Inc. PopChart is a registered trademark of CORDA Technologies, Inc. Kenan and
Arbor are registered trademarks of CSG Systems, Inc. Data Connection and SNAP-IX are registered trademarks of Data Connection Corporation. DataDirect,
DataDirect Connect, and SequeLink are registered trademarks of DataDirect Technologies. D&B and D-U-N-S are registered trademarks of Dun & Bradstreet
Corporation. Entrust is a registered trademark of Entrust, Inc. papiNet is a registered trademark of the European Union and the United States. Financial
Information eXchange, F.I.X, and F.I.X Protocol are trademarks of FIX Protocol Ltd. UCCnet and eBusinessReady are registered trademarks, and 1SYNC and
Transora are trademarks of GS1 US. Hewlett-Packard, HP, HP-UX, OpenView, PA-RISC, and SNAplus2 are trademarks of Hewlett-Packard Company. i2 is a
registered trademark of i2 Technologies, Inc. AIX, AS/400, CICS, DB2, Domino, IBM, Informix, Infoprint, Lotus, Lotus Notes, MQSeries, OS/390, OS/400,
RACF, RS/6000, SQL/400, S/390, System/390, VTAM, z/OS, and WebSphere are registered trademarks; and Communications System for Windows NT, DB2
Universal Database, IMS, MVS, and SQL/DS are trademarks of IBM Corporation. InnoDB is a trademark of Innobase Oy. Itanium is a registered trademark of
Intel Corporation. JBoss is a registered trademark, and JBoss Group is a trademark of Jboss, Inc. Linux is a registered trademark of Linus Torvalds. W3C is a
registered trademark, and X Window System is a trademark of the Massachusetts Institute of Technology. MetaSolv is a registered trademark of Metasolv
Software, Inc. ActiveX, Microsoft, Outlook, Visual Basic, Windows, and Windows NT are registered trademarks; and Windows Server is a trademark of
Microsoft Corporation. Six Sigma is a registered trademark of Motorola, Inc. Firefox is a registered trademark, and Mozilla is a trademark of the Mozilla
Foundation. MySQL is a registered trademark of MySQL AB. nCipher is a trademark of nCipher Corporation Ltd. Teradata is a registered trademark of NCR
International, Inc. Netscape is a registered trademark of Netscape Communications Corporation. SUSE is a registered trademark of Novell, Inc. ServletExec is
a registered trademark, and New Atlanta is a trademark of New Atlanta Communications, LLC. CORBA is a registered trademark of Object Management
Group, Inc. JD Edwards, OneWorld, Oracle, PeopleSoft, Siebel, and Vantive are registered trademarks, and PeopleSoft Pure Internet Architecture and
WorldSoftware are trademarks of Oracle Corporation. Infranet and Portal are trademarks of Portal Software, Inc. Red Hat is a registered trademark of Red
Hat, Inc. PIP and RosettaNet are trademarks of RosettaNet, a non-profit organization. SAP and R/3 are registered trademarks of SAP AG. SWIFT and
SWIFTNet are registered trademarks of Society for Worldwide Interbank Financial Telecommunication SCRL. SPARC and SPARCStation are registered
trademarks of SPARC International, Inc. SSA is a registered trademark, and Baan and SSA Global are trademarks of SSA Global Technologies, Inc. EJB,
Enterprise JavaBeans, Java, JavaServer, JDBC, JSP, J2EE, Solaris, Sun, and Sun Microsystems are registered trademarks; and Java Naming and Directory
Interface, SOAP with Attachments API for Java, JavaServer Pages, and SunSoft are trademarks of Sun Microsystems, Inc. Sybase is a registered trademark of
Sybase, Inc. VERITAS is a registered trademark, and VERITAS Cluster Server is a trademark of Symantec Corporation. UNIX is a registered trademark of The
Open Group. Unicode is a trademark of Unicode, Inc. VeriSign is a registered trademark of Verisign, Inc.
All other marks are the property of their respective owners.
Copyright © 2006 by webMethods, Inc. All rights reserved, including the right of reproduction in whole or in part in any form.

Document ID: WEBM-EM-RF-65_651-20060810

Contents

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

webMethods Components and Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 1. webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
BRM (JMS Provider) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Broker C API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Broker Java API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Chapter 2. webMethods Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Chapter 3. webMethods EDI Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

EDICOR (WmEDI Package) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
EDIFTN (WmEDIforTN Package) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Chapter 4. webMethods EDIINT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Chapter 5. webMethods Flat File Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

FFP (Flat File) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
FPL (File Polling) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Chapter 6. webMethods Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

Chapter 7. webMethods Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

ART (Adapter Run Time) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
BAA (Auditing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
BAF (File System Persistence) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
BAP (Master Password) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
ISC (IS Core) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
ISE (Internal Errors) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
ISP (Package Management) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
ISS (IS Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
ISU (General Purpose) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
SCC (JCA System Contract Component Transaction Manager) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
XSL (XSLT Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570

webMethods Error Message Reference Version 6.5 and 6.5.1 3

Contents

Chapter 8. webMethods Logging Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571

Chapter 9. webMethods Mainframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575

General Server Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
Client Communications (TCP/IP) Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
Transaction and Data Conversion Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
Host Communication System Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
APPC Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
CICS Sockets Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587

Chapter 10. webMethods Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589

Unnumbered Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
MBean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
Numbered Manager Server and MBean Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595

Chapter 11. webMethods Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621

Chapter 12. webMethods Process Run Time (PRT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687

Chapter 13. webMethods RosettaNet Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721

ESIPRT (WmIPRoot Package) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
ESRN11 (WmRUNIF11TRP Package) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
ESRN20 (WmRNIF20TRP Package) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
ESRNET (WmRosettaNet Package) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752

Chapter 14. webMethods Trading Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753

Chapter 15. webMethods Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919

WKA (Authentication Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
WKB (Common Client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
WKC (Common Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939
WKE (Resource Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 943
WKG (Distribution Control Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952
WKH (HTTP Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972
WKK (Event Subscription Support) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
WKN (Object Relational Mapping) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
WKO (Inbox) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
WKP (Process Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993
WKQ (Persistent Object Layer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1008
WKS (Server Manager) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1012

4 webMethods Error Message Reference Version 6.5 and 6.5.1

Contents

WKT (Run-Time Support) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1017

webMethods Error Message Reference Version 6.5 and 6.5.1 5

Contents

6 webMethods Error Message Reference Version 6.5 and 6.5.1

About This Guide

This guide lists the high and critical severity run-time errors for webMethods components, gives explanations
for the causes of the errors, and recommends actions a user can take to remedy them. It contains information
for system administrators responsible for the operational health of the webMethods components to enable
them to monitor and react to errors and events. The book is also useful for developers who are responsible for
error handling.

webMethods Components and Versions

This guide provides information about error codes for the webMethods components listed in the following
table.

webMethods Component Version

webMethods Broker 6.5
webMethods Deployer 6.5.1
webMethods EDI Module 6.5
webMethods Flat File Package 6.5
webMethods Installer 6.5.1
webMethods Integration Server 6.5
webMethods Logging Utility 6.5
webMethods Mainframe 6.5
webMethods Manager Server 6.5.1
webMethods Portal 6.5.1
webMethods Process Run Time 6.5.1
webMethods RosettaNet Module 6.5
webMethods Trading Networks 6.5
webMethods Workflow 6.5.1

webMethods Error Message Reference Version 6.5 and 6.5.1 7

About This Guide

Additional Information
The webMethods Advantage Web site at http://advantage.webmethods.com provides you with important
sources of information about the webMethods components.:
Troubleshooting Information. webMethods provides troubleshooting information for many webMethods
components in the webMethods Knowledge Base.
Documentation Feedback. To provide documentation feedback to webMethods, go to the Documentation
Feedback Form on the webMethods Bookshelf.
Additional Documentation. All webMethods documentation is available on the webMethods Bookshelf.

8 webMethods Error Message Reference Version 6.5 and 6.5.1

CHAPTER 1
webMethods Broker

Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

BRM (JMS Provider) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Broker C API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Broker Java API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

webMethods Error Message Reference Version 6.5 and 6.5.1 9

CHAPTER 1 webMethods Broker

Broker

1000 Broker Server ready, process id <processID> (<productVersion>).

Cause: Informational message.
Response: None.

1001 Broker Server exiting, process id <processID>.

Cause: Informational message.
Response: None.

1002 Could not start Windows sockets: <errorMessage>.

Cause: The Broker Server failed to start Windows sockets.
Response: Examine the system error messages to determine the problem.

1003 Wrong version of Windows sockets.

Cause: The Windows sockets version used is incorrect.
Response: Make sure that the correct version of Windows sockets is used.

1004 Could not get local host name: <errorMessage> -- Check network configuration.
Cause: The Broker Server failed to obtain the current host's name.
Response: Check the network configuration.

1008 Data store wrong version [EXITING].

Cause: The Broker Server version and the data store version are incompatible.
Response: Make sure that the Broker Server version is appropriate for the current data files.

1010 Error: Unknown subcommand "<subCommand>".

Cause: The subcommand is unknown.
Response: Refer to the documentation for this command and specify the required subcommands.

1011 Error: Missing subcommand.

Cause: The subcommand is missing.
Response: Refer to the documentation for this command and specify the required subcommands.

10 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1012 "Broker initialization failed, cannot create IO port -- <portNum> [EXITING]."

Cause: The Broker Server encountered an internal error during start up.
Response: Contact webMethods Customer Care.

1012 Error: No data directory supplied.

Cause: The Broker Server data directory is not specified.
Response: Make sure to specify a valid data directory.

1013 Error: Datadir "<directoryName>" is a relative path; a complete path must be supplied.
Cause: The specified path for the data directory is a relative path. It must be an absolute path.
Response: Make sure to specify an absolute path for the data directory.

1014 Warning: Extra license key "<licenseKey>" specified but not needed.
Cause: An extra license key was specified.
Response: Make sure to specify a single license key in the arguments list.

1015 Error: No license key specified. Please specify a valid license key.
Cause: The Broker Server license key is not specified.
Response: Make sure to specify a valid license key.

1016 Warning: Extra port number "<portNum>" specified but not needed.
Cause: An extra port number was specified.
Response: Make sure to specify a single port number in the arguments list.

1017 Warning: Bad port number value "<portNum>" specified, ignoring.

Cause: A bad port number was specified and will be ignored.
Response: Make sure to specify a valid port number.

1018 Warning: Extra description "<descriptionString>" specified but not needed.

Cause: An extra description string was specified.
Response: Make sure to specify a single description string.

webMethods Error Message Reference Version 6.5 and 6.5.1 11

CHAPTER 1 webMethods Broker

1019 Error: No description specified.

Cause: The description is not specified.
Response: Make sure to specify a valid description string.

1020 Error: The description "<descriptionString>" contains non-ISO Latin characters, which is not supported by this tool.
Please use webMethods Broker Administrator to set the description.
Cause: The description contains unsupported characters.
Response: Refer to the webMethods Broker Administrator documentation for details on supported characters.

1021 Cannot accept connections: <errorMessage>.

Cause: The Broker Server failed to accept socket connections.
Response: Examine the additional system errors returned with this error message to identify the problem.

1021 Warning: Extra Broker Server executable "<executableFile>" specified but not needed.
Cause: An extra Broker Server executable file was specified.
Response: Make sure to specify a single Broker Server executable file.

1022 Cannot create main socket for network connections: <errorMessage> -- [EXITING].
Cause: The Broker Server Monitor failed to create the main socket during its startup process.
Response: Examine the system error message to determine the problem.

1022 Error: No Broker Server executable specified.

Cause: The Broker Server executable file is not specified.
Response: Make sure to specify a valid Broker Server executable.

1023 Cannot bind main socket to port <portNum>: <errorMessage> -- Another Broker Server may be running already. --
[EXITING].
Cause: The Broker Server software was installed more than once.
Response: Stop the old Broker Server or uninstall its software. Then, start the new Broker Server.

1023 Warning: Extra awbroker.cfg filename "<configFileName>" specified but not needed.
Cause: An extra awbroker.cfg file name was specified.
Response: Make sure to specify the awbroker.cfg file name only once.

12 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1024 Error: No Broker Server configuration file specified.

Cause: The Broker Server configuration file is not specified.
Response: Make sure to specify a valid Broker Server configuration file in the arguments.

1025 Broker Server Monitor ready, process id <processID>.

Cause: Informational message.
Response: None.

1027 Cannot open config file <configFileName>: <errorMessage> -- The Broker Server Monitor must be started in the top
install directory.
Cause: The Broker Server on the UNIX platform is missing a configuration file.
Response: Contact webMethods Customer Care.

1027 Warning: Extra option -test specified but not needed.

Cause: An extra option "-test" was specified.
Response: Make sure to specify the "-test" option only once.

1028 Warning: Extra option -nostart specified but not needed.

Cause: An extra option "-nostart" was specified.
Response: Make sure to specify the "-nostart" option only once.

1029 Restarted Broker Server in directory <dataDirectory> <restartCount> times, giving up.
Cause: The Broker Server on the UNIX platform failed to start.
Response: In the log file, examine the other error messages to determine the problem.

1029 Warning: Extra hostname "<hostName>" specified but not needed.

Cause: An extra hostname parameter was specified.
Response: Make sure to pass the hostname parameter only once.

1030 Broker Server Monitor starting Broker Server in directory <dataDirectory> - cannot create process: <errorMessage>.
Cause: The Broker Server failed to create a process.
Response: In the log file, examine other error messages to determine the problem.

webMethods Error Message Reference Version 6.5 and 6.5.1 13

CHAPTER 1 webMethods Broker

1030 Error: No hostname specified.

Cause: The Broker Server host name is not specified.
Response: Refer to the command usage and specify all the required parameters.

1031 Warning: Port number specified in hostname "<portNum>" is invalid, ignoring.

Cause: The specified port number is invalid and will be ignored.
Response: Make sure to specify a valid port number.

1032 Stopping Broker Server <execName> pid <pid> - cannot get exit code: <errorMessage>.
Cause: The Broker Server failed to get exit code out of the process.
Response: None.

1032 Warning: Extra option -f for forcing deletion specified but not needed.
Cause: An extra option "-f" (for forcing deletion) was specified.
Response: Refer to the documentation for this command and specify only the required parameters.

1033 Unexpected stop of Broker Server in directory <dataDirectory> pid <processID> - exit code <exitCode>.
Cause: The Broker Server stopped unexpectedly.
Response: In the log file, examine the other error messages to determine the problem.

1033 Error: "<switchString>" unknown switch.

Cause: The option specified in the command line is unknown.
Response: Refer to the documentation for this command and specify only the required parameters.

1034 Unexpected stop of Broker Server in directory <dataDirectory> pid <processID> - Signal <signalInfo> <coreDumped>.
Cause: The Broker Server stopped unexpectedly due to the specified signal.
Response: In the log file, examine the other error messages to determine the problem.

1034 Error: Unexpected arg "<argString>".

Cause: The argument is not valid.
Response: Refer to the documentation for this command and specify only the required parameters.

14 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1035 Error: Value for session flag "<flagName>" is missing.

Cause: The value for the specified session flag is missing.
Response: Make sure to specify values for the session flags.

1036 Error: Missing storage session specification Use -session_config or -session_data to specify.
Cause: The storage session specification is missing.
Response: Make sure to specify a valid storage session specification.

1037 Wait on synchronization object failed: <errorMessage>.

Cause: The Broker Server encountered an internal error.
Response: Contact webMethods Customer Care.

1037 Error: "<parameter>" is specified but not required.

Cause: Extra storage parameters are specified but not required.
Response: Refer to the documentation for this command and specify only the required parameters.

1038 Broker Server Monitor starting Broker Server executable <executableName> in directory <dataDirectory>.
Cause: Informational message.
Response: None.

1038 Error: Filename for "<qs_storage_file>" is missing.

Cause: The file name for the storage or log file is missing.
Response: Make sure to specify a valid file name for storage or log files.

1039 Error: "<qs_log_file>" is specified more than once.

Cause: More than one log file is specified in the argument list.
Response: Make sure to specify the log file only once.

1040 Error: File size for "<qs_storage_file>" is missing.

Cause: The file size for the QS storage file is missing.
Response: Make sure to specify valid file size parameters.

webMethods Error Message Reference Version 6.5 and 6.5.1 15

CHAPTER 1 webMethods Broker

1041 Error: QS logfile "<fileName>" must be an absolute path.

Cause: The QS log file must have an absolute path.
Response: Make sure that the log file has an absolute path.

1042 Error: QS storagefile "<fileName>" must be an absolute path.

Cause: The QS storage file must have an absolute path.
Response: Make sure that the storage file has an absolute path.

1043 Starting Broker Server in directory <datDirectory> - could not find executable <executableName>: <errorMessage>.
Cause: The Broker Server failed to find the specified executable file.
Response: On the Broker Server, make sure that the executable file exists and resides in the specified directory.

1043 Error: QS logfile "<fileName>" already exists, will not overwrite.

Cause: The QS log file already exists and cannot be overwritten.
Response: QS log files cannot be overwritten.

1044 Starting Broker Server in directory <dataDirectory> - cannot create pipe: <errorMessage>.
Cause: The Broker Server failed to create a pipe system.
Response: Examine the other system error messages to determine the problem.

1044 Error: Resizing the configured QS logfile "<fileName>" is not supported. A different logfile must be configured instead.
Cause: The QS log file cannot be resized.
Response: Instead of attempting to resize the current log file, a different log file must be configured.

1045 Starting Broker Server in directory <dataDirectory> - <executableName> is not executable.

Cause: The Broker Server failed to start because the specified file is not an executable file.
Response: Make sure that a valid executable file is specified to start the Broker Server.

1045 Error: QS logfile size <fileSize> Kb must be higher or equal to <minFileSize> Kb.
Cause: The QS log file size is invalid.
Response: Make sure that the QS log file is valid.

16 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1046 Starting Broker Server - cannot find directory: <dataDirectory>.

Cause: The Broker Server failed to find the specified directory.
Response: On the Broker Server, make sure that the specified directory exists and is available.

1046 Error: QS storagefile "<fileName>" size <fileSize> Kb must be higher or equal to <minFileSize> Kb.
Cause: The QS storage file size is invalid.
Response: Make sure that the QS storage file is valid.

1047 Starting Broker Server - <dataDirectory> is not a directory.

Cause: The specified data directory is not a directory.
Response: Make sure to specify a valid data directory.

1047 Error: QS storagefile "<fileName>" reserved size <reservedSize> Kb must be less than or equal to <fileSize> Kb, and
also larger than <minFileSize> Kb.
Cause: The reserved size for the QS storage file is invalid.
Response: Make sure to specify a valid reserved size.

1048 Error: QS storage "<fileName>" already exists, will not overwrite.

Cause: The QS log file already exists and cannot be overwritten.
Response: Make sure that the QS storage file does not already exist.

1049 Error: Shrinking QS storage "%1" (from %2 Kb to %3 Kb) is not supported.

Cause: The Broker Server failed to shrink the QS storage file.
Response: On the Broker Server, make sure that the specified storage file size is not less than the current size of
QS storage.

1050 Error: Cannot reserve less from QS storage "<fileName>" (currently <diskReservedSize> Kb, specified
<storageFileReservedSize> Kb).
Cause: The Broker Server cannot reserve space of a size that is less than the configured reserve size on the QS
storage files.
Response: On the Broker Server, make sure that the specified reserved size is not less than the current reserved
size of QS storage.

webMethods Error Message Reference Version 6.5 and 6.5.1 17

CHAPTER 1 webMethods Broker

1051 Insufficient memory resources for operation. -- [EXITING].

Cause: The Broker Server is out of memory.
Response: On the Broker Server, close unnecessary applications to release memory, and then restart the Server.

1051 Error: Cannot determine parent dir for "<fileName>".

Cause: The Broker Server failed to determine the parent directory of the data directory.
Response: Make sure that the path string of the data directory is valid and the parent directory exists on the
Broker Server.

1052 Error: Directory "<directoryName>" for file "<fileName>" is not writable.

Cause: The Broker Server failed to write to the specified directory.
Response: On the Broker Server, make sure that the parent directory (of the data files) is writable.

1053 Error: Incorrect or insufficient arguments supplied to program.

Cause: Incorrect or insufficient arguments were supplied to this program.
Response: Refer to the documentation for this command and specify all the required parameters.

1054 Error: The specified license key has expired. Please specify a valid license key.
Cause: The Broker Server license key has expired.
Response: Make sure to specify a valid license key.

1055 Error: The specified license key is incorrect. Please specify a valid license key.
Cause: The Broker Server license key is invalid.
Response: Make sure to specify a valid license key.

1056 Error: Specified data directory "<directoryName>" not accessible: <errorMessage>.

Cause: The Broker Server failed to access the data directory.
Response: On the Broker Server, make sure that the data directory exists and that the appropriate permissions
are set.

1058 Error: Parent directory "<directoryName>" not accessible: <errorMessage>.

Cause: The Broker Server failed to access the parent directory.
Response: On the Broker Server, make sure that the parent directory is available and that the appropriate
permissions are set.

18 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1059 Error: Parent directory "<directoryName>" not writable: <errorMessage>.

Cause: The Broker Server failed to write to the parent directory.
Response: On the Broker Server, make sure that the parent directory is available and that the appropriate write
permissions are set.

1060 Error: Parent directory "<directoryName>" not readable: <errorMessage>.

Cause: The Broker Server failed to read the parent directory.
Response: On the Broker Server, make sure that the parent directory is available and that the appropriate read
permissions are set.

1061 Error: Data directory "<datDirectory>" not writable: <errorMessage>.

Cause: The Broker Server failed to write to the data directory.
Response: On the Broker Server, examine the data directory and make sure that the appropriate write
permissions are set.

1062 Error: Data directory "<dataDirectory>" not readable: <errorMessage>.

Cause: The Broker Server failed to read the data directory.
Response: On the Broker Server, examine the data directory and make sure that the appropriate read
permissions are set.

1063 Error: Cannot get filesystem type of parent directory "<directoryName>": <errorMessage>.
Cause: The Broker Server failed to determine the file system type of the parent directory.
Response: On the Broker Server, make sure that the parent directory is of the local file system type.

1064 Error: Parent directory "<parentDirectory>" for "<filename>" is not a local filesystem.
Cause: The parent directory is not on a local file system.
Response: Make sure that the data directory is on a local file system.

1064 Error: Parent directory "<parentDirectory>" is not a local filesystem.

Cause: The parent directory of the specified data directory is not on a local file system.
Response: Make sure that the parent directory is on a local file system.

webMethods Error Message Reference Version 6.5 and 6.5.1 19

CHAPTER 1 webMethods Broker

1065 Error: Not enough space free (<requestedSize> bytes minimum) on filesystem for "<freeSpaceSize>".
Cause: There is not enough space on the file system to create QS files.
Response: Make sure that at least 100MB of free disk space is available on the file system.

1066 Error: The Broker Server configuration file "configFileName>" is not accessible: <errorMessage>.
Cause: The Broker Server configuration file does not exist.
Response: On the Broker Server, make sure that the configuration file exists and is not corrupt.

1067 Error: The Broker Server configuration file "<configFileName>" is not readable: <errorMessage>.
Cause: The Broker Server configuration file is not readable.
Response: On the Broker Server, make sure that the configuration file exists and is readable.

1068 Error: The Broker Server configuration file "<configFileName>" is not writable: <errorMessage>.
Cause: The Broker Server configuration file is not writable.
Response: On the Broker Server, make sure that the configuration file exists, is not corrupt, and is writable.

1069 Error: Port number choice <portNum> which reserves ports <portNum-1> and <portNum-2> as well, is conflicting with
the Broker Server in "<dataDirectory>", which is reserving ports <portNum1>, <portNum2> and <portNum3>.
Cause: One of the specified ports is reserved by another application. The Broker Server typically reserves the
specified port and Port-1 and Port-2.
Response: Specify a port number that is not reserved for use.

1070 Error: Port number choice <portNum> conflicts with reserved port <reservedPortNum>.
Cause: The specified port is reserved by the OS.
Response: Make sure to specify a non-reserved port.

1071 Error: Cannot bind to port number choice <portNum>: port not available for use.
Cause: The specified port conflicts with other applications.
Response: Make sure to specify a different port that is available.

1072 Please specify a different port number.

Cause: The specified port conflicts with other applications.
Response: Make sure to specify a different port that is available.

20 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1073 Warning: Cannot bind to port number choice <portNum>: <errorMessage> Port may not be available for use.
Cause: The Broker Configuration tool failed to bind to the port number because the port is being used by
another application.
Response: Make sure that the specified port does not conflict with other applications.

1074 Error: awbrokermon configuration file "<configFileName>" not readable: <errorMessage>.

Cause: The awbrokermon configuration file is not readable on the Broker Server.
Response: On the Broker Server, make sure that the awbrokermon file exists and is not corrupt.

1075 Error: awbrokermon configuration file "<configFileName>" not present and cannot create: <errorMessage>.
Cause: The awbrokermon configuration file does not exist and cannot be created on the Broker Server.
Response: On the Broker Server, make sure the awbrokermon file exists or that it can be created.

1076 Error: awbrokermon configuration file "<configFileName>" not writable: <errorMessage>.

Cause: The Broker Server failed to write to the Broker Server Monitor configuration file.
Response: On the Broker Server Monitor, make sure that the configuration file exists and is writable.

1077 Error: Could not get directory for the Broker Server Monitor configuration file.
Cause: The Broker Server failed to locate the directory for the Broker Server Monitor configuration file.
Response: Make sure that the directory exists.

1078 Error: Could not create Broker Server Monitor configuration dir "<configDir>": <errorMessage>.
Cause: The Broker Server Monitor configuration file was not created.
Response: On the Broker Server Monitor, make sure that the parent directory exists and that the user has the
correct permissions to create a directory.

1080 Error: Could not access Service Control Manager with required permissions: <errorMessage>.
Cause: The Broker Server failed to access the service control manager with the required permissions.
Response: On the Broker Server, make sure that the service control manager is accessible with the required
permissions.

1081 Cannot access data directory: <errorMessage> -- [EXITING].

Cause: The Broker Server failed to access the data directory.
Response: Make sure that the data directory exists on the Broker Server and is accessible.

webMethods Error Message Reference Version 6.5 and 6.5.1 21

CHAPTER 1 webMethods Broker

1081 Error: Could not create new service "<serviceName>" from Service Control Manager: <errorMessage>.
Cause: The service was not created from the Service Control Manager.
Response: Make sure that the user has privileges to create services.

1082 Low disk space for data store -- <freeSpace>K bytes free, <totalSpace>K bytes tota.l
Cause: The Broker Server has low disk space.
Response: On the Broker Server, make room in the partition where the data directory is present, if possible.

1082 Error: Could not delete service "<serviceName>" from Service Control Manager: <errorMessage>.
Cause: The service was not deleted from the Service Control Manager.
Response: Make sure that the service exists and that the user has privileges to delete services.

1083 CRITICALLY LOW DISK SPACE for data store -- <freeSpaceInKB> bytes free, <maxSpaceInKB> bytes total.
Cause: There is critically low disk space on the Broker Server.
Response: On the Broker Server, make room in the partition where the data directory is present, if possible.

1083 Warning: Cannot switch to uid=<currentUserId> (<monitorUserId>): <errorMessage>.

Cause: The Broker Configuration tool failed to switch the uid to the uid specified in the configuration file.
Response: Make sure that the specified uid is a valid user id and exists on the system. Check the error string
displayed as part of this error message for more details.

1084 Resolved low disk space condition for data store -- <freeSpace>K bytes free, <totalSpace>K bytes total.
Cause: The Broker Server no longer has low disk space.
Response: None.

1084 Error: Configuration session type "<sessionType>" not supported.

Cause: The specified configuration session type is not supported.
Response: Make sure that the specified configuration session type is "qs".

1085 Error: Data session type "<sessionType>" not supported.

Cause: The specified data session type is not supported.
Response: Make sure that the specified data session type is "qs".

22 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1086 Error: Broker Server executable "<executableName>" not accessible: "<errorMessage>.

Cause: The Broker Server executable file is not accessible.
Response: On the Broker Server, make sure that the executable file exists and that the appropriate permissions
are set.

1087 Cannot start service dispatcher: <errorMessage>.

Cause: The Broker Server on the Windows platform encountered an internal error.
Response: Contact webMethods Customer Care.

1087 Error: Specified Broker Server executable "<executableName>" not an executable file.
Cause: The Broker Server executable file is not valid.
Response: On the Broker Server, make sure that the executable file is executable and that the appropriate
permissions are set.

1088 Error: Specified Broker Server config "<configFileName>" not accessible: <errorMessage>.
Cause: The Broker Server failed to access the configuration file.
Response: On the Broker Server, make sure that the configuration file exists and that the appropriate
permissions are set.

1089 Cannot register service <serviceName>: <errorMessage>.

Cause: The Broker Server encountered an internal error on the Windows platform.
Response: Contact webMethods Customer Care.

1089 Error: Specified Broker Server config "<configFileName>" is not a regular file.
Cause: The Broker Server configuration file is not a standard file.
Response: On the Broker Server, examine the configuration file to make sure that it is a standard file.

1090 Error: Specified Broker Server config "<configFileName>" not readable: <errorMessage>.
Cause: The Broker Server configuration file could not be read.
Response: Make sure that the configuration file exists and that the user has privileges to read it.

1091 Error: Could not read the configuration from "<configFileName>": <errorMessage>.
Cause: The Broker Server configuration file could not be read.
Response: Make sure that the configuration file exists and that the user has privileges to read it.

webMethods Error Message Reference Version 6.5 and 6.5.1 23

CHAPTER 1 webMethods Broker

1092 Error: Could not create Broker Server data directory "<dataDirectory>": <errorMessage>.
Cause: The Broker Server data directory was not created.
Response: Make sure that the current user has permissions to create directories on the Broker Server.

1093 Cannot set service status: <errorMessage>.

Cause: The Broker Server encountered an internal error on the Windows platform.
Response: Contact webMethods Customer Care.

1093 Warning: Could not get installation bin directory, using "<executableFilePath>".
Cause: The Broker Configuration tool failed to obtain the installation \bin directory from the environment
settings.
Response: Make sure to specify an executable file for the Broker Server. In addition, make sure that the
environment settings are valid. (In Windows, check the registry; in UNIX, check the environment variable.)

1094 Warning: Could not signal Broker Server Monitor to reread configuration.
Cause: The Broker Configuration tool failed to signal the Broker Server Monitor to reread the configuration.
Response: Make sure that the Broker Server Monitor is running. Examine the error message for details on the
problem.

1095 Error: Could not write the Broker Server configuration file "<configFileName>": <errorMessage>.
Cause: The Broker Server failed to write to the configuration file.
Response: On the Broker Server, make sure that the configuration file exists and is writable.

1096 Cannot open service control manager: <errorMessage>.

Cause: The Broker Server encountered an internal error on the Windows platform.
Response: Contact webMethods Customer Care.

1096 Error: Broker Server configuration file "<configFileName>" already exists.

Cause: The Broker Server configuration file was not created because it already exists.
Response: Remove or backup the current configuration file and execute the request again.

1097 Cannot create service <serviceName>: <errorMessage>.

Cause: The Broker Server encountered an internal error on the Windows platform.
Response: Contact webMethods Customer Care.

24 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1097 Warning: No license key specified for Broker Server. The Broker Server will not be able to start.
Cause: The Broker Server license key is not specified.
Response: Make sure to specify a valid license key.

1098 Cannot open service <serviceName>: <errorMessage>.

Cause: The Broker Server encountered an internal error on the Windows platform.
Response: Contact webMethods Customer Care.

1098 Warning: No executable specified for Broker Server. Broker Server Monitor will not be able to start the Broker Server.
Cause: No executable file was specified for the Broker Server while adding/creating the Broker Server.
Response: Make sure to specify the name and location of the Broker Server executable file.

1099 Cannot delete service <serviceName>: <errorMessage>.

Cause: The Broker Server encountered an internal error on the Windows platform.
Response: Contact webMethods Customer Care.

1100 Cannot start service <serviceName>: <errorMessage>.

Cause: The Broker Server on the Windows platform encountered an internal error.
Response: Contact webMethods Customer Care.

1100 The Broker Server on port <portNum>, associated with data directory "<dataDirectory>" is still running. Attempting to
stop Broker Server.
Cause: The Broker Server on the specified port is still running. It must be stopped in order to complete the
delete request.
Response: Stop the Broker Server, then perform the delete operation again.

1101 Cannot stop service <serviceName>: <errorMessage>.

Cause: The Broker Server on the Windows platform encountered an internal error.
Response: Contact webMethods Customer Care.

webMethods Error Message Reference Version 6.5 and 6.5.1 25

CHAPTER 1 webMethods Broker

1101 Warning: Could not stop Broker Server on port <portNum>, associated with data directory "<dataDirectory>".
Continuing deletion anyway.
Cause: The Broker Configuration tool failed to stop the Broker Server. However, the Broker Server will be
deleted from the Broker Server Monitor's configuration anyway.
Response: The Broker Server may be a runaway process. If so, clean it up manually.

1102 The license key is missing for webMethods Broker. The software will not run without a license key. -- [EXITING].
Cause: During installation, the administrator failed to provide a valid license key for the Broker Server.
Response: During installation, make sure to provide a valid license key. If you have an expired license key,
contact webMethods Customer Care.

1102 Successfully stopped Broker Server on port <portNum>.

Cause: The Broker Server on the specified port has successfully stopped.
Response: None.

1103 The license key <licenseKeyString> is invalid. The webMethods Broker will not run without a valid license key. --
[EXITING].
Cause: The Broker Server has an invalid license key.
Response: During installation, make sure that a valid webMethods license key is specified.

1103 Error: Could not read the configuration file in "<dataDirectory>", aborting.
Cause: The Broker Server configuration file could not be read.
Response: Make sure that the configuration file exists and that the user has privileges to read it.

1104 The license has expired for the webMethods Broker. The broker will not accept any documents until the license is
updated.
Cause: The Broker Server has an expired webMethods license key.
Response: Make sure to apply a valid license key. Contact webMethods Customer Care.

1104 Error: Could not read Broker Server Monitor configuration file "<configFileName>": <errorMessage>.
Cause: The Broker Server failed to read the Broker Server Monitor configuration file.
Response: On the Broker Server Monitor, make sure that the configuration file exists and that the user has
privileges to read it. Examine the error message for details on the problem.

26 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1105 Broker initialization failed, network manager did not start -- [EXITING].
Cause: The Broker Server encountered an internal error.
Response: Contact webMethods Customer Care.

1105 Error: Could not write Broker Server Monitor configuration file "<configFileName>": <errorMessage>.
Cause: The Broker Server failed to write to the Broker Server Monitor configuration file.
Response: On the Broker Server Monitor, make sure that the configuration file exists and is writable. Examine
the error message for details on the problem.

1106 Error: File "<fileName>" in data directory "<dataDirectory>" is not a regular file, will not remove.
Cause: The Broker Server failed to remove the data directory because it is not a standard file.
Response: On the Broker Server, make sure that the data directory exists and is a standard file.

1107 Internal error -- <errorMessage>.

Cause: The Broker Server encountered an internal error.
Response: Contact webMethods Customer Care.

1107 Error: Could not remove file "<fileName>" in data directory "<dataDirectory>": <errorMessage>.
Cause: The Broker Server failed to remove the specified file in the data directory.
Response: On the Broker Server, make sure that the file exists and is removable.

1108 Error: Could not remove data directory "<dataDirectory>": <errorMessage>.

Cause: The Broker Server failed to remove the data directory because the "rmdir" command failed.
Response: On the Broker Server, make sure that the data directory exists and is a standard file. Examine the
error message for details on the problem.

1109 Client connection failed, cannot use IO port -- <errorMessage> [EXITING].

Cause: The Broker Server encountered an internal error.
Response: Contact webMethods Customer Care.

1109 Error: Could not find data directory "<dataDirectory>" in the Broker Server Monitor configuration.
Cause: The Broker Server Monitor configuration does not have the data directory specified.
Response: Examine the Broker Server Monitor's configuration file to make sure that the Broker Server is
specified correctly.

webMethods Error Message Reference Version 6.5 and 6.5.1 27

CHAPTER 1 webMethods Broker

1110 Removed Broker Server in "<dataDirectory>", but errors and/or warnings occurred.
Cause: The Broker Server was deleted, but errors occurred.
Response: In the log files, examine the errors and/or warnings to determine the problem.

1110 Removed Broker Server in "<dataDirectory>" from configuration, but errors and/or warnings occurred.
Cause: The Broker Server was removed, but errors occurred.
Response: In the log files, examine the errors and/or warnings to determine the problem.

1111 Error: Could not write the Broker Server configuration to "<configFileName>": <errorMessage>.
Cause: The Broker Server failed to write to the configuration file.
Response: On the Broker Server, make sure that the configuration file exists and is writable.

1112 Reached operating system connection limit. No more connections can be made to the Broker Server until existing
connections are closed.
Cause: The connection to the Broker Server failed because the operating system cannot support any more
connections.
Response: Refer to your system documentation for information about increasing the connection limit or the
number of resources.

1112 Error: The Broker Server on port <portNum> is currently running; cannot change port number. Please stop Broker
Server first.
Cause: The port number of the Broker Server was not changed because the Server is currently running.
Response: Stop the Broker Server, and then change the port number.

1113 Network I/O operation <operation> failed -- <errorMessage>.

Cause: The Broker Server connection closed because the Server encountered an unexpected input/output error.
The computer may be low on memory.
Response: On the Broker Server, close unnecessary applications to release memory, and then try again.

1113 Error: Could not remove the Broker Servers service definition as part of changing the port number.
Cause: The service was not removed because the system call to delete an NT service failed.
Response: Make sure that the service exists and that the user has privileges to remove services.

28 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1114 Wrong password for SSL key file "<keyFile>". SSL disabled.
Cause: The password supplied for the SSL certificate is incorrect.
Response: Specify the correct password for the SSL certificate file.

1114 Error: Could not create the new service definition for the Broker Server as part of changing the port number.
Cause: The service was not created because the system call to create an NT service failed.
Response: Make sure that the service does not exist and that the user has privileges to create services.

1115 Could not find SSL key file "<keyFile>". SSL disabled.
Cause: The specified SSL certificate file does not exist.
Response: On the Broker Server, make sure that the SSL certificate file exists and is not corrupt.

1115 Warning: Could not contact Broker Server Monitor for list of Broker Servers. Listing local configuration:
Cause: The Broker Configuration tool failed to obtain a list of active Broker Servers from the Broker Server
Monitor.
Response: Make sure that the Broker Server Monitor is running. Examine the error message for details on the
problem.

1116 Error in SSL key file "<keyFile>", error code <errorCode>. SSL disabled.
Cause: The certificate file supplied has an invalid entry or is corrupt.
Response: Make sure that the certificate file exists and is not corrupt.

1118 Could not create SSL socket, unknown error code <errorCode> (<errorMessage>). SSL disabled.
Cause: The Broker Server encountered an internal error.
Response: Contact webMethods Customer Care.

1119 Could not accept SSL connection, error code <errorCode> (<errorMessage>).
Cause: The Broker Server encountered an internal error.
Response: Contact webMethods Customer Care.

1120 Could not accept SSL connection, bad handshake from <ipAddrss>: <portNum>.
Cause: The Broker Server encountered an internal error.
Response: Contact webMethods Customer Care.

webMethods Error Message Reference Version 6.5 and 6.5.1 29

CHAPTER 1 webMethods Broker

1121 Fatal error, SSL disabled: <errorMessage> <>.

Cause: The Broker Server encountered an internal error.
Response: Contact webMethods Customer Care.

1122 Could not find DN <distinguishedName> in key file "<keyFile>". SSL disabled.
Cause: The certificate file supplied does not contain the specified Distinguished Name.
Response: Make sure that the certificate file exists and is not corrupt.

1123 SSL connection using expired certificate DN = <distinguishedName> begin-date = "<beginDate>" end-date =
"<endDate>".
Cause: The specified client certificate has expired.
Response: Obtain a valid certificate from the Certificate Authority.

1124 Broker SSL certificate has expired. Clients using SSL may refuse to connect to broker until the certificate is renewed.
DN = <distinguishedName> begin-date = "<beginDate>" end-date = "<endDate>".
Cause: The specified Broker Server certificate has expired.
Response: Obtain a valid certificate from the Certificate Authority.

1125 No certificate for DN <distinguishedName> in key file "<keyFile>". SSL disabled.

Cause: The certificate file supplied does not contain the specified Distinguished Name.
Response: Make sure that the certificate file exists and is not corrupt.

1127 Broker Server in directory <dataDirectory> failed on first start, giving up.
Cause: The Broker Server failed to start up.
Response: Examine the Broker Server log file to determine the problem.

1128 Out of memory while sending data to IP network address <ipAddress>, connection has been broken.
Cause: A low memory condition exists on the host.
Response: Resolve the low memory condition by closing applications on the host, and try again.

30 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1128 <serverNum>. Datadir: <dataDirectory> Executable: <executableName> Port: <portNum> Version: <versionInfo>
License-key: "<licenseKey>" Description: "<descriptionString>".
Cause: Informational message listing the Broker Servers found on the local host while checking for a port
conflict.
Response: None.

1129 List of configured servers running on "<hostName>":

Cause: Informational message listing the Broker Servers running on the specified host.
Response: None.

1130 <serverNum>. Datadir: <dataDirectory> Runstatus: <runStatus> Executable: <executableName> Port: <portNum>
Version: <versionInfo> License-key: "<licenseKey>" Description: "<descriptionString>".
Cause: Informational message describing the configuration of the Broker Servers found on the local host.
Response: None.

1131 <serverNum>. Datadir: <dataDirectory> Runstatus: <runStatus> Executable: <executableName> Port: <portNum>
Description: "<descriptionString>".
Cause: Informational message describing the configuration of the Broker Server found on the remote host.
Response: None.

1132 Creating new Broker Server: Datadir: <dataDirectory> Executable: <executableName> Port: <portNum> License-key:
"<licenseKey>" Description: "<descriptionString>".
Cause: Informational message describing the configuration of the Broker Server that is being created.
Response: None.

1133 Successfully created Broker Server in "<dataDirectory>".

Cause: Informational message indicating that the Broker Server was successfully created.
Response: None.

1134 Broker Server: Datadir: <dataDirectory> Executable: <executableName> Port: <portNum> License-key:
"<licenseKey>" Description: "<descriptionString>" Do you want to delete this Broker Server (y or Y for yes, no otherwise)?
Cause: Informational message describing the configuration of the Broker Server that is being deleted.
Response: None.

webMethods Error Message Reference Version 6.5 and 6.5.1 31

CHAPTER 1 webMethods Broker

1137 Aborting deletion.

Cause: The deletion process is being aborted.
Response: None.

1138 Deleting Broker Server.

Cause: Deleting the Broker Server.

The Broker Server is being deleted.

Response: None.

1139 Successfully removed Broker Server in "<dataDirectory>" from the Broker Server Monitor configuration file.
Cause: The Broker Server was successfully removed from the Broker Server Monitor's configuration file.
Response: None.

1140 Successfully removed Broker Server data directory "<dataDirectory>".

Cause: The Broker Server's data directory was successfully removed.
Response: None.

1141 Could not determine Fully Qualify Name for computer, using "<hostName>". Some clients or brokers may not be able to
contact this broker.
Cause: The Broker Server failed to determine the host's fully-qualified name. This indicates a problem with the
host's name service configuration. The Broker Server may be unable to communicate with other Brokers or
clients, particularly those in other domains.
Response: On the host, make sure that the fully-qualified name is specified. At a minimum, specify the domain
name.

1141 Successfully read configuration from "<configFileName>".

Cause: The Broker Server successfully read the configuration file.
Response: None.

1142 Successfully wrote updated configuration to "<configFileName>".

Cause: The Broker Server's configuration file was successfully updated.
Response: None.

32 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1143 Triggered Broker Server Monitor to reread configuration.

Cause: Informational message indicating that the Broker Server Monitor was triggered to reread its
configuration.
Response: None.

1144 Triggered Broker Server Monitor to start Broker Server.

Cause: Informational message indicating that the Broker Server Monitor was triggered to start the Broker
Server.
Response: None.

1145 Broker Server on port <portNum> is now running.

Cause: Informational message indicating that the Broker Server on the specified port is now running.
Response: None.

1147 Warning: could not write Broker Server configuration file.

Cause: The Broker Server could not write to its configuration file.
Response: On the Broker Server, make sure that the configuration file exists, is not corrupt, and is writable.

1148 Could not read Broker Server configuration file in directory <dataDirectory>: <errorMessage>.
Cause: The Broker Server failed to read the Broker configuration file.
Response: Make sure that the Broker Server configuration file exists and is not corrupt.

1148 Could not read Broker Server configuration file <configFileName> from directory <dataDirectory>: <errorMessage>
[EXITING].
Cause: The Broker Server failed to access its configuration file.
Response: On the Broker Server, make sure that the configuration file exists and is not corrupt.

1149 Incomplete Broker Server configuration file <configFileName> from directory <dataDirectory> [EXITING].
Cause: The Broker Server has an incomplete configuration file.
Response: On the Broker Server, examine the configuration file to make sure that all of the required parameters
are set.

webMethods Error Message Reference Version 6.5 and 6.5.1 33

CHAPTER 1 webMethods Broker

1150 Could not read new Broker Server configuration file in directory <dataDirectory>: <errorMessage>.
Cause: The Broker Server failed to read from the new Broker Server configuration file.
Response: Make sure that the Broker Server configuration file exists and is not corrupt.

1152 Could not query Broker Server as service "<serviceName>": <errorMessage>.

Cause: The Broker Server failed to query a remote Broker running as a service for its status.
Response: Make sure that the Broker Server service is running.

1153 Broker Server Monitor found new Broker Server with data directory in "<dataDirectory>".
Cause: The Broker Server Monitor found a new Broker Server with the specified data directory.
Response: None.

1154 Broker Server Monitor found Broker Server with data directory in "<dataDirectory>", already known.
Cause: A Broker Server with the specified data directory is already present in the known Broker Servers list.
Response: None.

1155 Broker Server Monitor reading configuration from file "<configFileName>".

Cause: The Broker Server Monitor is reading the configuration from the specified file.
Response: None.

1156 Broker "<brokerName>": Received an error label reply from access label adapter process "<ala_client_id>": Error:
"<errorCode>" Detail: "<errorDetail>" Client DN: "<clientDN>" Client Issuer DN: "<issuerDN>.
Cause: An access label adapter failed to assign an access label for the specified client.
Response: Make sure that the access label adapter is running.

1156 Warning: Cannot make a connection to the local Broker Server Monitor: <errorMessage>.
Cause: The Broker Configuration tool failed to establish a connection to the Broker Server Monitor.
Response: Make sure that the Broker Server Monitor is running. Examine the error message for details on the
problem.

1157 Broker "<brokerName>": Received a label reply for an unknown client from access label adapter process
"<ala_client_id>": Client DN: "<clientDN>" Client Issuer DN: "<issuerDN>".
Cause: An access label adapter returned an access label when the Broker was not expecting one.
Response: Make sure that the access label adapter is configured properly.

34 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1157 Warning: Cannot make a connection to the Broker Server Monitor on "<hostName>": <errorMessage>.
Cause: The Broker Configuration tool failed to establish a connection to the Broker Server Monitor.
Response: Make sure that the Broker Server Monitor is running. Examine the error message for details on the
problem.

1158 Broker "<brokerName>": Error: Could not prepare lookup document to send to access label adapter process. Access
label lookup not available.
Cause: The Broker Server encountered an internal error.
Response: Contact webMethods Customer Care and provide the text of the error message.

1158 Broker "<brokerName>": Error: Could not find access label adapter process client. Access label lookup not available.
Cause: The Broker Server failed to use the access label adapter because it was not running.
Response: On the Broker Server, make sure that the access label adapter is running.

1158 Warning: Cannot close connection to the local Broker Server Monitor: <errorMessage>.
Cause: The Broker Configuration tool failed to close the connection to the Broker Server Monitor.
Response: Make sure that the Broker Server Monitor is running. Examine the error message for details on the
problem.

1159 Broker "<brokerName>": Received reply containing an illegal label from access label adapter process "<alaClientId>".
Cause: The access label adapter issued an access label that is invalid.
Response: Check and validate the access label adapter configuration.

1159 Warning: Cannot signal Broker Server Monitor to reload its configuration: <errorMessage>.
Cause: The Broker Configuration tool failed to signal the Broker Server Monitor to reload its configuration.
Response: Make sure that the Broker Server Monitor is running. Examine the error message for details on the
problem.

1160 Broker "<brokerName>": Error: Could not allocate memory to send lookup to access label adapter process. Access
label lookup not available.
Cause: A low memory condition exists on the host.
Response: Resolve the low memory condition by closing applications on the host, and try again.

webMethods Error Message Reference Version 6.5 and 6.5.1 35

CHAPTER 1 webMethods Broker

1160 Warning: Cannot signal Broker Server Monitor to reload the configuration for the Broker Server in data directory
"<dataDirectory>": <errorMessage>.
Cause: The Broker Configuration tool failed to signal the Broker Server Monitor to reload the configuration for
the Broker Server.
Response: Make sure that the Broker Server Monitor is running. Examine the error message for details on the
problem.

1161 Warning: Cannot signal Broker Server Monitor to start the Broker Server in data directory "<dataDirectory>":
<errorMessage>.
Cause: The Broker Configuration tool failed to signal the Broker Server Monitor to start the Broker Server.
Response: Make sure that the Broker Server Monitor is running. Examine the error message for details on the
problem.

1162 Error: Could not create SSL socket: SSL not initialized. SSL disabled.
Cause: The Broker Server has not been configured for SSL support.
Response: On the Broker Server, make sure that SSL is enabled and configured properly.

1162 Warning: Cannot get list of active Broker Servers from Broker Server Monitor: <errorMessage>.
Cause: The Broker Configuration tool failed to obtain a list of active Broker Servers from the Broker Server
Monitor.
Response: Make sure that the Broker Server Monitor is running. Examine the error message for details on the
problem.

1163 Error: Could not create SSL socket for port <portNum>: could not open socket (<errorMessage>). SSL disabled.
Cause: The Broker Server failed to open the SSL sockets used to accept client connections.
Response: Make sure that the ports Port, Port-1, and Port-2 are available to the Broker and not reserved for any
other application or services.

1163 Warning: Cannot get current run status of the Broker Server in data directory "<dataDirectory>": <errorMessage>.
Cause: The Broker Configuration tool failed to obtain the Broker Server's run status.
Response: Examine the error message to determine the current state of the Broker Server.

1164 Error: Could not create SSL socket for port <portNum>: no memory. SSL disabled.
Cause: A low memory condition exists on the host.
Response: Resolve the low memory condition by closing applications on the host, and try again.

36 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1164 Warning: Broker Server on port <portNum> not (yet) running, status is: <runStatus>.
Cause: The Broker Server on the specified port is not running.
Response: Examine the error message to determine the current state of the Broker Server.

1165 Error: Could not create SSL socket: bind to port <portNum> failed (<errorMessage>). SSL disabled.
Cause: Another application may be using the port.
Response: Make sure that the ports Port, Port-1, and Port-2 are available to the Broker and not reserved for any
other application or services.

1165 Error: Cannot open connection to the Service Control Manager: <errorMessage>
Cause: The Broker Server failed to open a connection to Windows NT's service control manager.
Response: Make sure that the user has privileges to connect to the service control manager.

1166 Error: Could not create SSL socket: listen on port <portNum> failed (errorMessage). SSL disabled.
Cause: The Broker Server encountered an internal error.
Response: Contact webMethods Customer Care and provide the text of the error message.

1166 Error: Cannot create new Broker Server as NT service "<serviceName>": <errorMessage>.
Cause: The service was not created because the system call to create an NT service failed.
Response: Make sure that the user has privileges to create services.

1167 Warning: Could not resolve specified broker hostname "<hostName>" to an IP address. Connections from remote
brokers may fail.
Cause: The Broker Server host could not be found. The Broker-to-Broker feature may not work.
Response: On the Broker Server, examine the awbroker.cfg file to make sure that the specified host name can be
resolved to a valid IP address. Also have the system administrator check the local name service configuration
and the name service tables.

1167 Error: Cannot open Broker Server as NT service "<serviceName>": <errorMessage>

Cause: The service was not opened because the system call to open an NT service failed.
Response: Make sure that the service exists and that the user has privileges to open services.

webMethods Error Message Reference Version 6.5 and 6.5.1 37

CHAPTER 1 webMethods Broker

1168 SSL key file "<keyFile>" seems to be corrupted. SSL disabled.

Cause: The certificate supplied for the Broker Server is invalid or corrupt.
Response: On the Broker Server, replace the certificate file.

1168 Error: Cannot delete Broker Server as NT service "<serviceName>": <errorMessage>.

Cause: The service was not deleted because the system call to delete an NT service failed.
Response: Make sure that the service exists and that the user has privileges to delete services.

1169 Error: Cannot setuid to "<monitorUserName>" (uid <userID>): <errorMessage>.

Cause: The user or group cannot be set for the Broker Server Monitor.
Response: On the local system, make sure that the user bin and the group bin exist. Next, make sure that the
user and group IDs exist and are specified in the awbroker.cfg file.

1169 Error: Cannot connect to Broker Server on port <portNum>: <errorMessage>.

Cause: Failed to connect to the Broker Server.
Response: Make sure that the Broker Server is running on the specified port. Examine the error message for
details on the problem.

1170 Error: Cannot lookup user "<monitorUserName>" or group "<monitorGroupName>".

Cause: The user or group cannot be found for the Broker Server Monitor.
Response: On the local system, make sure that the user bin and the group bin exist. Next, make sure that the
user and group IDs exist and are specified in the awbroker.cfg file.

1170 Error: Cannot stop Broker Server on port <portNum>: <errorMessage>.

Cause: The Broker Server failed to stop on the specified port.
Response: Examine the Broker Server's configuration file and make sure it is valid. Examine the error message
for details on the problem.

1171 Error: Cannot make secure broker connections: SSL is disabled or not configured.
Cause: One or more of the Brokers is configured to use SSL in a territory, but the Broker Server SSL
configuration is missing or not working.
Response: Make sure that the SSL is configured properly and the certificate file is valid.

38 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1171 Error: Cannot start Broker Server on port <portNum>: <errorMessage>.

Cause: The Broker Server failed to start on the specified port.
Response: Examine the Broker Server's configuration file and make sure it is valid. Examine the error message
for details on the problem.

1172 Broker "<brokerName>": Cannot connect to Broker Server "<rbrokerHostName>", error in resolving hostname to IP
address: <errorMessage>.
Cause: The local name service configuration is incorrect or the host name is missing from the name service
tables.
Response: Contact the system administrator to correct the local name service configuration and/or provide the
missing host name in the name service tables.

1173 Broker "<brokerName>": Cannot connect to Broker Server "<rbrokerName>": <errorMessage>.

Cause: The remote Broker Server is not running.
Response: Make sure that the Broker Server is running on the remote host.

1174 Broker <brokerName>: Connection to<remoteBrokerName>"@<portNum> was rejected by the remote broker. Reason:
The remote broker is not licensed for territories.
Cause: A Broker Server in a territory does not include the Broker-to-Broker option in its runtime license key.
Response: Make sure to apply a license key that supports the Broker-to-Broker feature. Contact webMethods
Customer Care.

1174 Broker Server: Datadir: <dataDirectory> Executable: <executableName> Port: <portNum> License-key:
"<licenseKey>" Description: "<descriptionString>" Note that Broker Server Data files will not be removed. Do you want to
remove this Broker Server from the Broker Server Monitors server configuration (y or Y for yes, no otherwise)?
Cause: Informational message describing the configuration of the Broker Server that is being removed.
Response: None.

1175 Broker "<brokerName>": Connection to "<remoteBrokerName>"@<portNum> was rejected by the remote broker.
Reason: The remote Broker Server is incompatible with this Broker Server.
Cause: A Broker Server is incompatible with the webMethods Broker system. All Broker Servers in a territory
must be compatible with the version of the webMethods Broker system.
Response: Make sure that only compatible versions of Broker servers are allowed to be part of a territory.

webMethods Error Message Reference Version 6.5 and 6.5.1 39

CHAPTER 1 webMethods Broker

1175 Aborting removal.

Cause: The Broker Server "remove" operation was aborted at the user's request.
Response: None.

1176 Broker "<brokerName>": Connection to "<rbrokerName>"@<portNum> was rejected by the remote broker. Reason: The
remote broker does not have a territory set.
Cause: The Broker Server failed to connect to the remote Broker Server because the remote Broker was
removed from the territory. The local Broker Server was not updated to reflect the removal. This can be caused
by poor connectivity between Brokers or by forced removal of a Broker using the Broker Administrator.
Response: This problem can be fixed by joining the remote Broker to the territory, or force removing the stale
remote broker connection from the local broker in the territory.

1176 Removing Broker Server from configuration.

Cause: The Broker Server is being removed from the configuration.
Response: None.

1177 Broker "<brokerName>": Connection to "<rbrokerName>"@<portNum> was rejected by the remote broker. Reason: The
remote broker is not part of territory "<territoryName>".
Cause: The Broker Server failed to connect to the remote Broker Server because the remote Broker was
removed from the territory. The local Broker Server was not updated to reflect the removal. This can be caused
by poor connectivity between Brokers or by forced removal of a Broker using the Broker Administrator.
Response: This problem can be fixed by joining the remote Broker to the territory, or force removing the stale
remote broker connection from the local broker in the territory.

1177 Successfully removed Broker Server data directory "<dataDirectory>" from configuration.
Cause: The Broker Server's data directory was successfully removed.
Response: None.

1178 Broker "<brokerName>": Connection to "<remoteBrokerName>"@<portNum> was rejected by the remote broker.
Reason: Permission denied.
Cause: The local Broker Server failed to establish a connection with a remote Broker because of one of the
following reasons:

40 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

local Broker Server only supports US Export).

2) The territory security configuration is out of sync among the Brokers in the territory.
Response: If you suspect that the territory security configuration is out of sync, export the Broker configuration
from the local and remote Brokers and compare them. If you find inconsistencies, modify the exported ADL
files and import them to the Broker using the broker_load command-line utility.

1178 Error: Cannot open QS configuration file "<configFile>": <errorMessage>.

Cause: The Broker Server failed to open the QS configuration file.
Response: On the Broker Server, make sure that the QS configuration file exists and has the appropriate
permissions set.

1179 Broker "<brokerName>": Connection to "<rbrokerName>"@<portNum> was rejected by the remote broker. Reason: A
gateway to territory "<territoryName>" already exists on the remote broker.
Cause: Two Broker Servers are configured as gateways to the remote Broker Server. In a territory, only one
Broker can provide a gateway to a specific remote territory.
Response: In the territory, make sure that only one Broker has a gateway to the specified remote territory.

1179 Error: Cannot open QS storage: <errorMessage>.

Cause: The Broker Server failed to open QS storage.
Response: On the Broker Server, make sure that the QS storage file exists and has the appropriate permissions
set.

1180 Broker "<brokerName>": Connection to "<remoteBrokerName>"@<portNum> was rejected by the remote broker.
Reason: An internal error occured (error code <errorCode>).
Cause: The Broker Server encountered an internal error.
Response: Contact webMethods Customer Care and provide the text of the error message.

1180 Error: Cannot replay QS logs: <errorMessage>.

Cause: The Broker Server failed to replay the QS log file.
Response: Examine the error message to determine the problem.

1181 Broker "<brokerName>": Cannot connect to "<remoteBrokerName>"@<portNum>: Received a malformed reply from
remote broker.
Cause: The Broker Server encountered an internal error.
Response: Contact webMethods Customer Care and provide the text of the error message.

webMethods Error Message Reference Version 6.5 and 6.5.1 41

CHAPTER 1 webMethods Broker

1181 Error: Cannot clear QS logs: <errorMessage>.

Cause: The Broker Server failed to clear the QS log file.
Response: Examine the QS error message to determine the problem.

1182 Broker "<brokerName>": Incorrect broker connection made to "<remoteBrokerName>"@<portNum>: configurations are
not consistent.
Cause: The Broker Server made an incorrect connection to the specified remote Broker. The configurations may
be inconsistent. The Broker Server encountered an internal error.
Response: Contact webMethods Customer Care and provide the text of the error message.

1182 Error: Cannot add QS log file "<fileName>": <errorMessage>.

Cause: The Broker Server failed to add a QS log file.
Response: Examine the QS error message to determine the problem.

1183 Broker "<brokerName>": Cannot connect to "<remoteBrokerName>"@<portNum>: The logical clock is not consistent
with the local copy.
Cause: The Broker Server cannot connect to the specified remote broker because of a conflict in the logical clock
value. The Broker Server encountered an internal error.
Response: Contact webMethods Customer Care and provide the text of the error message.

1183 Adding QS files (this may take a few moments):

Cause: Informational message indicating that the QS files are being added.
Response: None.

1184 Broker "<brokerName>": Initial synchronization failed for broker connection to "<remoteBrokerName>"@<portNum>.
Cause: The Broker Server failed to initially synchronize the connection to the specified remote Broker. The
Broker Server encountered an internal error.
Response: Contact webMethods Customer Care and provide the text of the error message.

1184 Since no log file and at least one storage file were specified, the Broker Server will create a default log and storage file
at startup.
Cause: Informational message indicating that the Broker Server will create the storage and log files at startup.
Response: None.

42 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1185 Broker "<brokerName>": A broker connection from "<remoteBrokerName>"@<portNum> was denied access.
Cause: The Broker Server failed to establish a connection because of one of the following reasons:

1) Territory security has been enabled and the local Broker does not meet the permission requirements of the
remote Broker. This error can be caused by an incorrect certificate DN on the local Broker Server or by
differences in encryption strength (for example, if US Domestic encryption is required by the territory but the
local Broker Server only supports US Export).
2) The territory security configuration is out of sync among the Brokers in the territory.
Response: If you suspect that the territory security configuration is out of sync, export the Broker configuration
from the local and remote Brokers and compare them. If you find inconsistencies, modify the exported ADL
files and import them to the Broker using the broker_load command-line utility.

1185 Added QS log file "<fileName>" size <fileSize> Kb successfully.

Cause: Informational message indicating that a QS log file of the specified size was successfully added.
Response: None.

1186 Broker "<brokerName>": A gateway connection from "<remoteBrokerName>"@<portNum> was denied access.
Cause: The Broker Server failed to create a gateway connection because of one of the following reasons:

1186 Error: Cannot add QS storage file "<fileName>": <errorMessage>.

Cause: The Broker Server failed to add a QS storage file.
Response: Examine the QS error message to determine the problem.

1187 Broker "<brokerName>": A broker connection to "<brokerName>"@<portNum> was successfully established.

Cause: This message appears after a territory connection is fixed.
Response: None.

webMethods Error Message Reference Version 6.5 and 6.5.1 43

CHAPTER 1 webMethods Broker

1187 Added QS storage file "<fileName>" size <fileSize> Kb (<reservedSize> kb reserved) successfully.
Cause: Informational message indicating that a QS storage file of the specified size was successfully added.
Response: None.

1188 Error: Cannot grow QS storage file "<fileName>" to "<fileSize>" bytes: <errorMessage>
Cause: The Broker Server failed to grow the QS storage file. The partition may not have enough space to
support this action.
Response: On the Broker Server, make sure that the data directory contains sufficient space for the grow
operation. Examine the error message for details on the problem.

1189 Grew QS storage file "<fileName>" to size <fileSize> Kb (<reservedSize> kb reserved) successfully.
Cause: Informational message indicating that the QS storage file size was successfully increased.
Response: None.

1190 Error: Cannot open the internal log file "<serverLogFileName": <errorMessage> Internal logging is disabled.
Cause: The Broker Server failed to create or open the internal log file.
Response: Make sure that the user ID of the Broker process has permission to create and/or open the Server log
file "logmsgs" in the data directory.

1190 Error: Cannot start QS logs: <errorMessage>.

Cause: The Broker Server failed to start the QS logs.
Response: Examine the QS error message to determine the problem.

1191 Thread creation failed: <errorMessage>.

Cause: The Broker Server encountered a fatal internal error. This was caused by a lack of resources or system-
imposed limit on the number of threads in a process.
Response: On the Broker Server, increase the value of the parameter that controls the number of threads per
process.

1191 Error: Cannot activate QS log "<logFileName>": <errorMessage>.

Cause: The Broker Server added the QS log but failed to activate it.
Response: Examine the error message to determine the problem.

44 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1192 Multiple servers (<numServers>) not supported on this platform. Only starting the first configured server.
Cause: The Broker Server encountered an internal error on the HP platform.
Response: Refer to HP/UX section of the Broker Server release notes for instructions on how to support
multiple servers on the HP/UX platform.

1192 Starting Broker Server (this may take a few moments).

Cause: Informational message indicating that the Broker Server is being started.
Response: None.

1193 The Broker Server at "<hostName>:<portNum>" is currently running. Would you like to stop it (y or Y for yes, no
otherwise)?
Cause: Informational message indicating that the Broker Server on host:port is currently running.
Response: None.

1194 Could not accept SSL connection, handshake from <ipAddress>: <portNum> timed out after <timeOut> ms.
Cause: A client connecting to the Broker Server with SSL timed out.
Response: Check the network connectivity and the security settings on the client.

1194 Warning: Attempted to stop the Broker Server at "<hostName>:<portNum>", but it still seems to be running.
Cause: The Broker Server appears to be running, even after a stop request.
Response: Examine the Server Broker log files to determine the problem.

1195 Successfully stopped the Broker Server at "<hostName>:<portNum>".

Cause: The Broker Server on host:port has successfully stopped.
Response: None.

1196 The Broker Server at "<hostName>:<portNum>" is not currently running.

Cause: Informational message indicating that the Broker Server on host:port is not currently running.
Response: None.

1197 The Broker Server at "<hostName>:<portNum>" is not currently running. Attempting to start it.
Cause: Informational message indicating that the Broker Server specified in the start request is not running.
Response: None.

webMethods Error Message Reference Version 6.5 and 6.5.1 45

CHAPTER 1 webMethods Broker

1198 Warning: The Broker Server at "<hostName>:<portNum>" did not seem to start.
Cause: The Broker Server on the specified host:port appears to be stopped even after a start request.
Response: Examine the Server Broker log files to determine the problem.

1199 Successfully started the Broker Server at "<hostName>:<portNum>".

Cause: Informational message indicating that the Broker Server was successfully started.
Response: None.

1200 The Broker Server at "<hostName>:<portNum>" is already running.

Cause: The start operation failed because the Broker Server is already running.
Response: None.

1202 Error: The Broker Server associated with "<dataDirectory>" is still running. Please stop Broker Server first.
Cause: The remove or delete operation failed because the Broker Server is currently running.
Response: Stop the Broker Server, and then issue the delete or remove request.

1203 Warning: Extra argument -list specified but not needed.

Cause: An extra argument "-list" was specified.
Response: Reissue the command without the "-list" argument.

1204 Successfully configured Broker Server storage.

Cause: Informational message indicating that storage was successfully added.
Response: None.

1205 QS Configuration for Broker Server in "<dataDirectory>":

Cause: Informational message describing the QS configuration.
Response: None.

1206 Log file: "<logFileName>", size <fileSize> Kb,

Cause: Informational message on the log file size.
Response: None.

46 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1207 Storage file: "<storageFileName>", max size <maxSize> Kb, reserved <reservedSize> Kb.
Cause: Informational message on the storage file size.
Response: None.

1208 The Broker Server configuration tool "broker_config" was renamed to "server_config". Please use "server_config" to
configure your Broker Servers.
Cause: The tool "broker_config" was renamed to "server_config".
Response: Use "server_config" to configure the Broker Servers.

1210 Error: Not enough space free (<requestedSize> Kb requested, <availableSize> Kb present) on filesystem for
"<fileName>".
Cause: The Broker Server has low disk space.
Response: On the Broker Server, make room on the hard disk. Then reissue the request.

1211 Error: Parent dir "<directoryName>" for file "<fileName>" is not present, and must be created first.
Cause: The Broker Server failed to complete the operation because the specified directory does not exist.
Response: On the Broker Server, make sure the parent directory exists.

1222 Check sum failed processing a document (<failedOnObject>). Broker Server cannot continue. [CRASHING].
Cause: The Broker Server encountered a fatal error. The storage file is corrupt.
Response: Contact webMethods Customer Care.

1228 Error: The Server has no sessions configured. [EXITING].

Cause: The Broker Server has no sessions configured.
Response: On the Broker Server, examine the configuration file to make sure that a valid session is specified.

1229 Error: The Server cannot initialize config session with URL "<sessionURL>". Error code <errorMessage>. [EXITING].
Cause: The Broker Server failed to initialize the configuration session.
Response: On the Broker Server, examine the configuration file to make sure that a valid session is specified.
Examine the error message for details on the problem.

webMethods Error Message Reference Version 6.5 and 6.5.1 47

CHAPTER 1 webMethods Broker

1230 Error: The Server cannot initialize data session with URL "<sessionURL>". Error code <errorMessage>. [EXITING].
Cause: The Broker Server could not create the data session at the specified URL.
Response: On the Broker Server, examine the configuration file to make sure that a valid data session is
specified. Examine the error message for details on the problem.

1234 Error: The Server cannot store its initial configuration to the config session: <errorMessage> [EXITING].
Cause: The Broker Server could not update its initial configuration.
Response: On the Broker Server, examine the configuration files to make sure they exist and are not corrupt.

1235 Warning: Broker "<brokerName>": Event dropped from forward queue to remote broker "<rbrokerName>" because it
was larger than the receiving broker's limit (<size> bytes).
Cause: The Broker Server failed to publish a document because the document is larger than 7MB. Pre-5.0
Brokers only support documents less than 7MB. Documents larger than 7MB are discarded.
Response: Do not send documents larger than 7MB to a pre-5.0 Broker Server, or send it as multiple smaller
events.

1240 Warning: The locale "<localeName>" is not supported on this platform for filter collation. Reverting to "C" locale.
Cause: An unsupported locale was specified as the filter collation locale.
Response: Make sure that a supported locale is specified.

1241 Broker ran out of memory. Failing memory allocation request of <number_of_bytes> bytes. Broker will exit.
Cause: Broker ran out of memory. Most likely the Broker has reached the OS imposed per-process memory
usage limit and cannot successfully allocate memory.
Response: Explore options to increase memory on the box where the Broker is running. Also, work with your
system administrator(s) to tune the underlying OS parameters to allow more memory for the Broker process.
Contact webMethods Customer Care for recommendations.

1242 Broker <broker_name>: The Transaction Manager rolled back the server and error <error_number> occurred.
Cause: The Broker's transaction manager is in a state that it could not recover from, forcing the Broker
transaction manager to restart the Broker Server.
Response: Inspect the Broker's transaction manager's list of transactions and perform the proper action(s),
including forcing a rollback or a commit of incomplete transactions.

48 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1245 Error: Could not create queueing storage for Broker <broker_name>, error <error_code> occurred.
Cause: Broker failed to create the required disk structures for a client's durable queue for a variety of reasons,
including: internal inconsistencies, out of memory, out of storage, or maximum transaction size exceeded. The
error_code returned indicates the type of error encountered.
Response: Check and make sure that the out of critical resources condition is addressed. 1) For the out of
memory error condition, add more memory to the box and increase the per-process memory usage limit to
higher number. 2) For the out of storage error, add additional storage files to the data store. 3) For errors
relating to exceeding the maximum transaction size, limit the size of the document to size of the log file or
increase the size of the log file using server_config.

1246 Error: Could not retrieve queueing storage for Broker <broker_name>, error <error_code> occurred. [RESTARTING]
Cause: Broker has encountered an out of memory condition or storage inconsistency. Normally, a restart
recovers the Broker to operational state. If the Broker repeatedly restarts itself, then the problem is from a
severe storage inconsistency or a critical resource shortage.
Response: If this error frequently occurs because of resource shortage issues, fix the resource shortage problem.
If the error is from storage inconsistencies, contact webMethods Customer Care and provide the text of the
error message for further guidance.

1247 Warning: Queueing storage for Broker <broker_name> missing, attempting to recreate all client queues and queues to
other Brokers.
Cause: The Broker run-time storage files "BrokerData.qs.*" (for example, BrokerData.qs.log and
BrokerData.qs.stor) have been removed or are not found when recreating client queues and forward queues.
Response: Broker automatically recreates these files during startup. No action is required.

1248 Error: Could not recover queueing storage for Broker <broker_name>, error <error_code>
occurred. [RESTARTING]
Cause: The Broker run-time storage files "BrokerData.qs.*" (for example, BrokerData.qs.log and
BrokerData.qs.stor) have been removed or are not found when recreating client queues and forward queues.
Broker ran out of a critical resource while recreating these files.
Response: Make sure that enough storage is available and restart the Broker. If this error occurs repeatedly
because of storage inconsistencies, contact webMethods Customer Care and provide the text of the error
message for further guidance.

1249 Recreated queueing storage for Broker <broker_name> successfully.

Cause: The Broker run-time storage files "BrokerData.qs.*" (for example, BrokerData.qs.log and
BrokerData.qs.stor) have been removed or are not found when recreating client queues and forward queues.
Broker successfully recreated the storage required files.
Response: No action required.

webMethods Error Message Reference Version 6.5 and 6.5.1 49

CHAPTER 1 webMethods Broker

1250 Error: Broker <broker_name>: Could not create configuration storage for Client
Group <clientgroup_name>, error <error_code> occurred.
Cause: Broker encountered an error when creating the disk structures for a client group. The error may because
of out of memory, out of storage, or maximum transaction size exceeded.
Response: Check and make sure that the out of critical resources condition is addressed. 1) For the out of
memory error condition, add more memory to the box and increase the per-process memory usage limit to
higher number. 2) For the out of storage error, add additional storage files to the data store. 3) For errors
relating to exceeding the maximum transaction size, limit the size of the document to size of the log file or
increase the size of the log file using server_config.

1251 Error: Broker <broker_name>: Could not create configuration storage for Event Type <eventtype_name>, error
<error_code> occurred.
Cause: Broker encountered an error when creating the disk structures for an event type. The error may be
because of out of memory or storage or max transaction size exceeded.
Response: Check and make sure that the out of critical resources condition is addressed. 1) For the out of
memory error condition, add more memory to the box and increase the per-process memory usage limit to
higher number. 2) For the out of storage error, add additional storage files to the data store. 3) For errors
relating to exceeding the maximum transaction size, limit the size of the document to size of the log file or
increase the size of the log file using server_config.

1252 Error: Broker <broker_name>: Could not create configuration storage for Client <client_name> error <error_code>
occurred.
Cause: Broker encountered an error when creating the disk structures for an event type. The error may be
because of out of memory, out of storage, or maximum transaction size exceeded.
Response: Check and make sure that the out of critical resources condition is addressed. 1) For the out of
memory error condition, add more memory to the box and increase the per-process memory usage limit to
higher number. 2) For the out of storage error, add additional storage files to the data store. 3) For errors
relating to exceeding the maximum transaction size, limit the size of the document to size of the log file or
increase the size of the log file using server_config.

1254 Error: Broker <broker_name>: Could not create configuration storage for Remote
Broker <remotebroker_name>, error <error_code>occurred.
Cause: Broker encountered an error when creating the disk structures for a remote Broker. The error may be
because of out of memory, out of storage, or maximum transaction size exceeded
Response: Check and make sure that the out of critical resources condition is addressed. 1) For the out of
memory error condition, add more memory to the box and increase the per-process memory usage limit to
higher number. 2) For the out of storage error, add additional storage files to the data store. 3) For errors
relating to exceeding the maximum transaction size, limit the size of the document to size of the log file or
increase the size of the log file using server_config.

50 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker

1255 Error: Broker <broker_name>: Could not create queueing storage for remote Broker
<remotebroker_name>, error <error_code> occurred.
Cause: Broker encountered an error when creating the disk structures for a remote Broker's forwarding queue.
The error may be because of out of memory, out of storage, or maximum transaction size exceeded
Response: Check and make sure that the out of critical resources condition is addressed. 1) For the out of
memory error condition, add more memory to the box and increase the per-process memory usage limit to
higher number. 2) For the out of storage error, add additional storage files to the data store. 3) For errors
relating to exceeding the maximum transaction size, limit the size of the document to size of the log file or
increase the size of the log file using server_config.

1256 Warning: Broker <broker_name>: Client Group <clientgroup_name> purged non-existent eventtypeindex
<eventtype_index> from the <list_name> list.
Cause: Broker checks that all client groups's canPub, canSub, logOnPub, and logOnAck contain valid event
type indices, with each index corresponding to a valid event type on the Broker. During this validation
process, Broker encountered an inconsistency and purged the non-existent event type index entry from the
client group's permission list.
Response: Notify webMethods Customer Care regarding this. No action required.

1257 Warning: Broker <broker_name>: Event Type <eventtype_name> subscription SRR refcount fixed (from <from> to
<to>).
Cause: Broker encountered an inconsistency in the reference count values that track subscriptions by local
clients.
Response: Broker automatically corrects this inconsistency. Notify webMethods Customer Care regarding this.
No action required.

1258 Warning: Broker <broker_name>: Event Type <eventtype_name> subscription refcount check finds error
<error_string>.
Cause: Broker encountered an inconsistency in the reference count value (most likely a negative value) that
track subscriptions for an event type.
Response: Broker automatically corrects this inconsistency. Notify webMethods Customer Care regarding this.
No action required.

1259 Warning: Broker <broker_name>: Remote Broker <remotebroker_name> times out on getting events (<msecs> secs),
disconnecting now, retry pending.
Cause: Broker encountered a condition of inactivity on a remote Broker connection.
Response: Broker automatically disconnects the existing connection and reestablishes a new remote Broker
connection. This will ensure fresh event request activity on the connection. Notify webMethods Customer
Care regarding this. No action required.

webMethods Error Message Reference Version 6.5 and 6.5.1 51

CHAPTER 1 webMethods Broker

1260 Broker Server configured with version <version_number>, but executable is version <version_number>.
Cause: Broker detected a mismatch between the version number on the config file and the actual binary
version.
Response: Use server_config to update the version number appropriately.

1261 Warning: Meta-data update activity has cancelled the currently running backup. Backup was started from session
<backup_session_id> at <start_time>.
Cause: Broker cancelled a metadata backup session as it did not complete in time.
Response: No action required. If this occurs repeatedly, extend the log file to get a larger transaction size.

1265 Error: Broker Monitor cannot open the internal log file <logfile_name>: <error_code> Internal logging is disabled.
Cause: Broker failed to open the internal Broker Bonitor log file "logmsgs" present in the data directory.
Response: Make sure that the file exists and appropriate permissions are set.

1266 Error: Broker <broker_name>: Out of storage occurred while processing update from Remote Broker
<remotebroker_name> [RESTARTING]
Cause: Broker exceeded the maximum transaction size or there was not enough storage to process an update
from the remote Broker.
Response: Add more storage or extend the log file to get a larger transaction size.

1268 Warning: Disconnecting session id <session_id> because it is not responding to keep alive requests.
Cause: Broker is disconnecting a client session because the expected response was not received for a keep-alive
request. This is probably because the client is disconnected or there are network issues.
Response: Make sure that the network is stable and the client is not disconnected. Otherwise, consider using
"auto-reconnect" option to reconnect automatically .

1269 Broker ran out of memory. Broker will exit.

Cause: Broker ran out of memory. Most likely the Broker has reached the operating system's imposed per-
process memory usage limit and cannot successfully allocate memory.
Response: Add more memory to the box and increase the per-process memory usage limit to a higher number.

52 webMethods Error Message Reference Version 6.5 and 6.5.1

BRM (JMS Provider)

BRM.10.1000 Message is read-only.

Cause: When a client receives a message its properties and body are in read-only mode. This error occurs when
the client attempts to set a property or write to the body of the message.
Response: To make the message properties writeable, call the Message.clearProperties method. To make the
message body writeable, call the Message.clearBody method.

BRM.10.1001 Message is write-only.

Cause: When a BytesMessage or StreamMessage is first created or after Message.clearBody is called, the body
of the message is in write-only mode. This error occurs when the client attempts to read the body of the
message.
Response: To make the message readable, call the Message.reset method.

BRM.10.1002 Unable to convert property "<propertyName>" to <type>.

Cause: The client attempted to get a property in a message as the wrong type. For example, the client
attempting calling Message.getIntProperty on a property that is a boolean.
Response: Use the appropriate method to either get the property as the correct type or a property that can
correctly be converted to the requested type.

BRM.10.1003 Invalid webMethods specific property: "<propertyName>".

Cause: The client attempted to set a non-existent provider-specific property in a message. JMS defines
provider-specific property names as "JMS_<vendor>". webMethods provider-specific property names begin
with "JMS_WM".
Response: Specify a valid webMethods provider-specific property name.

BRM.10.1004 Null is not a valid value for envelope field: "<envelopeFieldName>".

Cause: The client attempted to set a webMethods envelope field to null.
Response: Do not attempt to set an envelope field value to null.

BRM.10.1005 Invalid object type for Message field: "<propertyName>".

Cause: The client attempted to set an object property with an invalid type.
Response: The type must be an object corresponding to a native type (Boolean, Byte, Short, Integer, Long, Float,
Double) or a String.

webMethods Error Message Reference Version 6.5 and 6.5.1 53

CHAPTER 1 webMethods Broker

BRM.10.1006 Message is null.

Cause: The client attempted to send or publish a null message.
Response: Verify that a null value is not passed to the send or publish method(s).

BRM.10.1007 Version field is missing in serialized message.

Cause: The serialized Message object does not contain the required version field.
Response: Verify that the client does not attempt to deserialize an incompatible Message object.

BRM.10.1008 Incorrect message version. Expected <requiredVersion>, received <deserializedVersion>.

Cause: The serialized Message object is of an incompatible version.
Response: Verify that the client does not attempt to deserialize an incompatible Message object.

BRM.10.1009 Message data field is missing in serialized message.

Cause: The serialized Message object does not contain the required data field.
Response: Verify that the client does not attempt to deserialize an incompatible Message object.

BRM.10.1010 Property name cannot be null.

Cause: The client attempted to set or get a property in a message using a null property name.
Response: Verify that null is not passed as a property name.

BRM.10.1011 Property name cannot be an empty string.

Cause: The client attempted to set or get a property in a message using a property name that is an empty string.
Response: Verify that an empty string is not passed as a property name.

BRM.10.1012 <type> property "<propertyName>" was not found in the message.

Cause: The client attempted to get a JMS-defined property using an invalid type.
Response: Verify that a method corresponding to the correct type is used to get a JMS-defined property from a
message.

BRM.10.1013 JMSXDeliveryCount is read-only.

Cause: The JMSXDeliveryCount property is not settable.
Response: Do not attempt to set the JMSXDeliveryCount property. This property is set by the JMS provider
only.

54 webMethods Error Message Reference Version 6.5 and 6.5.1

BRM (JMS Provider)

BRM.10.1014 Invalid delivery mode specified: <value>. Use either DeliveryMode.NON_PERSISTENT (1) or
DeliveryMode.PERSISTENT (2).
Cause: An invalid delivery mode value was provided to the setJMSDeliveryMode method.
Response: Verify that the delivery mode value is either DeliveryMode.NON_PERSISTENT or
DeliveryMode.PERSISTENT.

BRM.10.1015 Invalid property name "<propertyName>"; cannot start with "JMS".

Cause: The client attempted to use a property name that began with "JMS" and was not defined by JMS
specification.
Response: Do not use property names starting with "JMS" unless defined by the JMS specification.

BRM.10.1016
Cause: The client attempted to use a property name that began with an invalid character.
Response: Verify that the property name is a valid Java identifier.

BRM.10.1017 Invalid property name "<propertyName>"; must contain only Java identifier part characters.
Cause: The client attempted to use a property name with an invalid character.
Response: Verify that the property name is a valid Java identifier.

BRM.10.1018 Invalid property name "<propertyName>"; must not be a JMS keyword.

Cause: The client attempted to use a property name that is a JMS keyword.
Response: Verify that the property name is not a JMS keyword: NULL, TRUE, FALSE, NOT, AND, OR,
BETWEEN, LIKE, IN, IS, or ESCAPE.

BRM.10.1019 Attempt to set read-only envelope field "<envelopeFieldName>".

Cause: The client attempted to set a read-only envelope field.
Response: Do not attempt to set a read-only envelope field.

BRM.10.1020 Attempt to access unknown envelope field "<envelopeFieldName>" of type "<specifiedType>".

Cause: The client attempted to set an unknown envelope field.
Response: Verify that a correct envelope field name is provided.

webMethods Error Message Reference Version 6.5 and 6.5.1 55

CHAPTER 1 webMethods Broker

BRM.10.1021 Unable to access envelope field "<envelopeFieldName>" of type "<specifiedType>".

Cause: The client attempted to get an envelope field using the incorrect type.
Response: Use the correct type to access an envelope field.

BRM.10.1022 Attempt to set envelope field "<envelopeFieldName>" of type "<specifiedType>" with a value of type "<actual
type>".
Cause: The client attempted to set an envelope field using the incorrect type.
Response: Verify that the correct type is used to set an envelope field.

BRM.10.1050 BytesMessage.writeUTF cannot take a null value parameter.

Cause: The passed value was null.
Response: Supply a non-null value.

BRM.10.1051 BytesMessage.writeBytes cannot take a null value parameter.

Cause: The passed value was null.
Response: Supply a non-null value.

BRM.10.1052 BytesMessage.writeObject cannot take a null value parameter.

Cause: The passed value was null.
Response: Supply a non-null value.

BRM.10.1053 BytesMessage.writeObject Objects of class "<class>" are not allowed.

Cause: An unsupported object type was passed to the method.
Response: The type must be an object corresponding to a native type (Boolean, Byte, Short, Integer, Long, Float,
Double) or a String.

BRM.10.1054 Unexpected end of stream when reading message.

Cause: The end of the bytes stream has been reached.
Response: Verify the contents of the BytesMessage.

BRM.10.1060 Unable to convert Map Message field "<name>" to <type>.

Cause: The client attempted to get a field using the incorrect type.
Response: Retrieve the field using the correct or compatible type.

56 webMethods Error Message Reference Version 6.5 and 6.5.1

BRM (JMS Provider)

BRM.10.1061 Map Message field "<name>" cannot have type "<type>".

Cause: An unsupported object type was passed to the method.
Response: The type must be an object corresponding to a native type (Boolean, Byte, Short, Integer, Long, Float,
Double) or a String.

BRM.10.1062 Map Message field name cannot be null.

Cause: The passed field name was null.
Response: Supply a non-null value.

BRM.10.1063 Map Message field name cannot be an empty string.

Cause: The passed field name was an empty string.
Response: Supply a non-empty string.

BRM.10.1070 Exception occurred while setting object in Object Message: "<exceptionMessage>"

Cause: An error occurred while serializing the object.
Response: Verify that the object can be serialized properly.

BRM.10.1071 Exception occurred while getting object from Object Message: "<exceptionMessage>"
Cause: An error occurred while deserializing the object.
Response: Verify that the object can be deserialized properly.

BRM.10.1080 Unable to convert Stream Message field at position <position> to <type>.

Cause: The client attempted to read a field using the incorrect type.
Response: Retrieve the field using the correct or compatible type.

BRM.10.1081 Stream Message field at position <position> cannot have type "<type>".
Cause: An unsupported object type was passed to the method.
Response: The type must be an object corresponding to a native type (Boolean, Byte, Short, Integer, Long, Float,
Double) or a String.

BRM.10.1082 Read called while bytes still remain in bytes field.

Cause: The client attempted to read the next field of a StreamMessage while there were bytes remaining in the
previous field.
Response: Read all bytes of a field before reading the next field.

webMethods Error Message Reference Version 6.5 and 6.5.1 57

CHAPTER 1 webMethods Broker

BRM.10.1083 Unexpected end of stream when reading message at position <position>

Cause: The end of the stream has been reached.
Response: Verify the contents of the StreamMessage.

BRM.10.1100 Selector syntax error: <selector>

Cause: The message selector contains a syntax error.
Response: Correct the syntax of the message selector.

BRM.10.1101 Selector contains unknown webMethods property name: <name>

Cause: The message selector contains an unknown provider-specific property name.
Response: webMethods-specific property names begin with "JMS_WM". Correct the property name.

BRM.10.1102 Selector contains invalid property name: <name>

Cause: The message selector contains an invalid property name.
Response: Property names must be valid Java identifiers.

BRM.10.1103 Selector contains unknown operator: <operator>

Cause: The message selector contains an unknown operator.
Response: Correct the operator in the message selector.

BRM.10.1104 Selector constains invalid ESCAPE character: <character>. Must be a single character.
Cause: The message selector contains an invalid escape character.
Response: Correct the escape character in the message selector.

BRM.10.1105 Selector contains invalid LIKE ESCAPE pattern: escape character at end of selector.
Cause: The message selector contains an escape character at the end of the pattern.
Response: Correct the pattern in the message selector.

BRM.10.1106 Selector contains invalid value for JMSDeliveryMode: <value>. Must be 'PERSISTENT' or 'NON_PERSISTENT'.
Cause: The message selector contains an invalid value for the JMSDeliveryMode property.
Response: The delivery mode value must be either NON_PERSISTENT or PERSISTENT.

58 webMethods Error Message Reference Version 6.5 and 6.5.1

BRM (JMS Provider)

BRM.10.1200 Cannot call commit or rollback on an XASession.

Cause: An XASession's commit or rollback method was called.
Response: It is illegal to call an XASession's commit or rollback method.

BRM.10.1201 Subscription name is null.

Cause: A null subscription name was passed when creating a durable subscriber.
Response: A non-null subscription name must be used when creating a durable subscriber.

BRM.10.1202 Client ID is not set.

Cause: The connection's client ID is not set.
Response: In order to create a durable subscription, the connection's client ID must be set.

BRM.10.1203 Client ID is already set.

Cause: The client attempted to set the connection's client ID when the client ID was already set.
Response: Verify that the connection's client ID is set only once.

BRM.10.1204 Connection is closed.

Cause: The client attempted to invoke a method on a closed connection.
Response: Verify program logic so that the connection is closed only after it is no longer needed.

BRM.10.1205 Session is closed.

Cause: The client attempted to invoke a method on a closed session.
Response: Verify program logic so that the session is closed only after it is no longer needed.

BRM.10.1206 Session is not transacted.

Cause: The client attempted to call commit or rollback on a session that is not transacted.
Response: Create a transacted session.

BRM.10.1207 Session is transacted.

Cause: The client attempted to call recover on a session that is transacted.
Response: Create a non-transacted session.

webMethods Error Message Reference Version 6.5 and 6.5.1 59

CHAPTER 1 webMethods Broker

BRM.10.1208 Illegal method call from message listener: <methodName>

Cause: The stop or close method was called from within a message listener.
Response: The stop or close method must not be called from within a message listener.

BRM.10.1209 Session conflict between message consumer and listener.

Cause: The client attempted to create a message consumer when the session already has a message listener, or
attempted to add a message listener to the session when the session already has a message consumer.
Response: A session may not have both a message listener and message consumers.

BRM.10.1210 Message producer is closed.

Cause: The client attempted to invoke a method on a closed message producer.
Response: Verify program logic so that the message producer is closed only after it is no longer needed.

BRM.10.1211 Message consumer is closed.

Cause: The client attempted to invoke a method on a closed message consumer.
Response: Verify program logic so that the message consumer is closed only after it is no longer needed.

BRM.10.1212 Message consumer is receiving messages asynchronously.

Cause: The client attempted to call receive on a message consumer that has a message listener.
Response: A message consumer may only receive messages asynchronously through a message listener or
synchronously by invoking the receive method.

BRM.10.1213 Queue browser is closed.

Cause: The client attempted to invoke a method on a closed queue browser.
Response: Verify program logic so that the queue browser is closed only after it is no longer required.

BRM.10.1214 Invalid method in domain: <methodName>

Cause: The client attempted to invoke a domain inappropriate method.
Response: It is an error to invoke a domain inappropriate method such as TopicSession.createQueue.

BRM.10.1215 Temporary destination "<destination>" has been deleted.

Cause: The client attempted to use a deleted temporary destination.
Response: Verify program logic so that the temporary destination is deleted only after it is no longer needed.

60 webMethods Error Message Reference Version 6.5 and 6.5.1

BRM (JMS Provider)

BRM.10.1216 Temporary destination "<destination>" does not belong to this connection.

Cause: The client attempted to create a message consumer with a temporary destination that does not belong to
the connection.
Response: A temporary destination can only be consumed by the connection that created it.

BRM.10.1217 Temporary destination "<destination>" is in use.

Cause: The client attempted to delete a temporary destination that is in use.
Response: Verify that the temporary destination is no longer in use before deleting it.

BRM.10.1218 Session has no message listener.

Cause: The application server failed to register a message listener for a session in the server session pool.
Response: No action required.

BRM.10.1219 Invalid acknowledge mode: <value>

Cause: The client attempted to create a non-transacted session using an invalid acknowledge mode value.
Response: The only allowed acknowledge mode values are Session.AUTO_ACKNOWLEDGE,
Session.CLIENT_ACKNOWLEDGE, and Session.DUPS_OK_ACKNOWLEDGE.

BRM.10.1220 Invalid delivery mode value: <value>

Cause: The client attempted to send a message with an invalid delivery mode.
Response: The only allowed delivery modes are DeliveryMode.PERSISTENT and
DeliveryMode.NON_PERSISTENT.

BRM.10.1221 Invalid priority: <value>. Must be between 0 and 9.

Cause: The client attempted to send a message with an invalid priority.
Response: The valid range for message priority is 0 through 9.

BRM.10.1222 Destination is read-only.

Cause: The client attempted to modify the administered object, which is in read-only mode.
Response: The client must not attempt to modify an administered object that is in read-only mode.

BRM.10.1223 Connection factory is read-only.

Cause: The client attempted to modify the administered object, which is in read-only mode.
Response: The client must not attempt to modify an administered object that is in read-only mode.

webMethods Error Message Reference Version 6.5 and 6.5.1 61

CHAPTER 1 webMethods Broker

BRM.10.1224 Transaction rolled back due to lost connection.

Cause: The client reconnected to the Broker resulting in any open transactions being aborted.
Response: No action required.

BRM.10.1225 Asynchronous message listener has thrown an exception.

Cause: The client's message listener code has thrown a RuntimeException.
Response: No action required.

BRM.10.1226 Client ID cannot be set because the connection is already in use.

Cause: The client invoked the Connection.setClientID method after the connection has been in use.
Response: It is illegal to invoke the Connection.setClientID method after the connection has been in use.

BRM.10.2000 Client ID is null.

Cause: The client called the Connection.setClientID method with a null client identifier.
Response: The client identifier must be non-null.

BRM.10.2001 Client ID is invalid: "<clientIdentifier>"

Cause: The client called the Connection.setClientID method with an invalid client identifier.
Response: The client identifier must be valid.

BRM.10.2002 Client ID "<clientIdentifier>" is already in use.

Cause: The client called the Connection.setClientID method with a client identifier that is already in use.
Response: The client identifier is used by only one connection at a time.

BRM.10.2003 Client ID "<clientIdentifier>" shared state connection limit has been exceeded.
Cause: The number of allowed shared connections for the client identifier has been exceeded.
Response: Increase the client's session limit on the Broker or limit the number of connections that are sharing
the same client identifier.

BRM.10.2004 Client ID "<clientIdentifier>" does not exist.

Cause: The client attempted to reconnect to a client identifier that does not exist.
Response: No action required.

62 webMethods Error Message Reference Version 6.5 and 6.5.1

BRM (JMS Provider)

BRM.10.2005 Client ID "<clientIdentifier>" already exists with <propety>=<value>.

Cause: The client attempted to reconnect to a client identifier with property values that differ from the existing
client on the Broker.
Response: A different client identifier must be used.

BRM.10.2100 Invalid shared state ordering value: <value>

Cause: The client specified an invalid shared state ordering value.
Response: The shared state ordering value must be either
WmDestination.SHARED_STATE_ORDERING_NONE or
WmDestination.SHARED_STATE_ORDERING_PUBLISHER.

BRM.10.2101 Invalid storage value: <value>

Cause: The administration client specified an invalid storage type value.
Response: The storage type value must be either WmJMSAdmin.STORAGE_GUARANTEED or
WmJMSAdmin.STORAGE_VOLATILE.

BRM.10.2102 Invalid lifecycle value: <value>

Cause: The administration client specified an invalid lifecycle value.
Response: The lifecycle value must be either WmJMSAdmin.LIFECYCLE_DESTROY_ON_DISCONNECT or
WmJMSAdmin.LIFECYCLE_EXPLICIT_DESTROY.

BRM.10.2103 Invalid validation value: <value>

Cause: The administration client specified an invalid validation value.
Response: The validation type value must be either WmJMSAdmin.VALIDATION_NONE,
WmJMSAdmin.VALIDATION_OPEN, or WmJMSAdmin.VALIDATION_FULL.

BRM.10.2104 Invalid TTL value: <value>. Must be greater than zero, or zero to disable TTL.
Cause: The client specified an invalid Time to Live (TTL) value.
Response: The Time to Live (TTL) value must be greater than or equal to zero.

BRM.10.2105 Invalid recover mode: <value>. Must be either 0 (restricted) or 1 (global).

Cause: The administration client specified an invalid transaction recover mode.
Response: The transaction recover mode must be either WmJMSAdmin.RECOVER_GLOBAL or
WmJMSAdmin.RECOVER_RESTRICTED.

webMethods Error Message Reference Version 6.5 and 6.5.1 63

CHAPTER 1 webMethods Broker

BRM.10.2106 Invalid timeout action: <value>. Must be either 1 (commit) or 2 (rollback).

Cause: The administration client specified an invalid transaction timeout action.
Response: The transaction timeout action must be either WmJMSAdmin.TRANSACTION_COMMIT or
WmJMSAdmin.TRANSACTION_ROLLBACK.

BRM.10.2107 Invalid timeout: <value>

Cause: The administration client specified an invalid transaction timeout value.
Response: The transaction timeout value must be either greater than or equal to zero, or for an infinite timeout,
the value must be -1.

BRM.10.2108 Invalid event type name: <eventType>

Cause: The administration client specified an invalid event type name.
Response: Specify a valid event type name when creating an event.

BRM.10.2109 Invalid Broker name: "<broker>"

Cause: The administration client specified an invalid Broker name.
Response: Specify a valid Broker name when creating a Broker.

BRM.10.2110 Invalid territory name: "<territory>"

Cause: The administration client specified an invalid territory name.
Response: Specify a valid territory name when creating a territory.

BRM.10.2111 Invalid client group name: "<clientGroup>"

Cause: The administration client specified an invalid client group name.
Response: Specify a valid client group name when creating a client group.

BRM.10.2112 Invalid client name: "<client>"

Cause: The administration client specified an invalid client name.
Response: Specify a valid client name when creating a client.

BRM.10.2113 Client "<client>" already exists.

Cause: The administration client attempted to create a client that already exists.
Response: Verify that the client does not already exist before creating the client.

64 webMethods Error Message Reference Version 6.5 and 6.5.1

BRM (JMS Provider)

BRM.10.2114 Client "<client>" does not exist.

Cause: The administration client attempted to destroy a client that does not exist.
Response: Verify that the client exists before destroying the client.

BRM.10.2115 Client group "<value>" already exists.

Cause: The administration client attempted to create a client group that already exists.
Response: Verify that the client group does not already exist before creating the client group.

BRM.10.2116 Event type "<eventType>" already exists.

Cause: The administration client attempted to create an event type that already exists.
Response: Verify that the event type does not already exist before creating the event type.

BRM.10.2117 Broker "<broker>" already exists.

Cause: The administration client attempted to create a Broker that already exists.
Response: Verify that the Broker does not already exist before creating the Broker.

BRM.10.2118 Broker "<broker>" does not exist.

Cause: The administration client attempted to destroy a Broker that does not exist.
Response: Verify that the Broker exists before destroying the Broker.

BRM.10.2119 Broker is not in a territory.

Cause: The administration client is connected to a Broker that does not belong to a territory.
Response: Verify that the Broker belongs to a territory before invoking a method that requires a territory.

BRM.10.2120 Broker is already in a territory.

Cause: The administration client is connected to a Broker that already belongs to a territory.
Response: Verify that the Broker does not belong to a territory before attempting to add the Broker to a
territory.

BRM.10.2121 The filter "<filter>" contains a parse error.

Cause: The administration client passed an invalid Broker filter to a client subscription.
Response: Fix the Broker filter.

webMethods Error Message Reference Version 6.5 and 6.5.1 65

CHAPTER 1 webMethods Broker

BRM.10.2122 Administration client is closed.

Cause: A method was invoked on an administration client that was closed.
Response: Verify program logic so that the administration client is closed only after it is no longer required.

BRM.10.2123 Conflicting event types and/or client groups with territory to be joined.
Cause: The administration client attempted to join a Broker to a territory that has event type or client group
conflicts.
Response: Fix the conflicts before attempting to join the Broker to the territory.

BRM.10.2125 The client group "<clientGroup>" has existing clients which should be destroyed first.
Cause: The administration client attempted to destroy a client group that is being used by existing clients.
Response: First destroy the clients using the client group before attempting to destroy the client group.

BRM.10.2126 The event type "<eventType>" has client groups which can publish or can subscribe to it. These permissions
should be removed first.
Cause: The administration client attempted to destroy an event type that can publish or subscribe permissions
on a client group.
Response: Remove the client group permissions before attempting to destroy the event type.

BRM.10.2127 Cannot destroy a Broker while it is in a territory.

Cause: The administration client attempted to destroy a Broker that is part of a territory.
Response: Remove the Broker from its territory before attempting to destroy the Broker.

BRM.10.2200 Event type "<eventType>" does not exist.

Cause: The client attempted to use an event type that does not exist.
Response: Create the event type on the Broker before using the event type

BRM.10.2201 Queue "<queue>" does not exist.

Cause: The client attempted to access a queue that does not exist on the Broker.
Response: Create the queue needs on the Broker before using the queue.

BRM.10.2202 Queue "<queue>" already exists.

Cause: The client attempted to create a queue that already exists on the Broker.
Response: Verify that the queue does not exist before attempting to create the queue.

66 webMethods Error Message Reference Version 6.5 and 6.5.1

BRM (JMS Provider)

BRM.10.2203 Queue "<queue>" is in use.

Cause: The client attempted to access a queue that is already in use by another client.
Response: For multiple access to a queue, the destination's shared state property must be set.

BRM.10.2204 Queue "<queue>" has reached its maximum share limit.

Cause: The client attempted to consume messages from a shared state queue that has reached its share limit.
Response: Increase the queue's session limit on the Broker or limit the number of consumers that are sharing
the same queue.

BRM.10.2205 Cannot connect to queue "<queue>" with <property>=<value>. It already exists with a conflicting value.
Cause: The client attempted to use a queue whose properties differ from those of the queue on the Broker.
Response: Verify that the queue's properties are identical to those of the queue on the Broker.

BRM.10.2206 Queue name is invalid: "<queue>"

Cause: The client specified an invalid queue name.
Response: The client must use a valid queue name.

BRM.10.2207 Durable subscription "<subscriptionName>" does not exist.

Cause: The client attempted to reconnect to a durable subscription that does not exist.
Response: Create the durable subscription on the Broker before attempting to reconnect to it.

BRM.10.2208 Durable subscription "<subscriptionName>" already exists.

Cause: The client attempted to create a durable subscription that already exists on the Broker.
Response: For multiple access to a durable subscription, you must set the destination's shared state property.

BRM.10.2209 Durable subscription "<subscriptionName>" is in use.

Cause: The client attempted to unsubscribe a durable subscription that is in use.
Response: Verify that the durable subscription is no longer in use before attempting to unsubscribe.

BRM.10.2210 Durable subscription "<subscrptionName>" has reached it's maximum share limit.
Cause: The client attempted to consume messages from a shared state durable subscription that has reached its
share limit.
Response: Increase the durable subscription's session limit on the Broker or limit the number of consumers that
are sharing the same durable subscription.

webMethods Error Message Reference Version 6.5 and 6.5.1 67

CHAPTER 1 webMethods Broker

BRM.10.2211 Cannot connect to durable subscription "<subscriptionName>" with <property>=<value>. It already exists with
a conflicting value.
Cause: The client attempted to use a durable subscription whose properties differ from those of the durable
subscription on the Broker.
Response: Verify that the durable subscription properties are identical to those of the durable subscription on
the Broker.

BRM.10.2212 Durable subscription name is invalid: "<subscriptionName>"

Cause: The client specified on invalid subscription name.
Response: The client must use a valid subscription name.

BRM.10.2213 Destination name is null.

Cause: The client attempted to use a null destination.
Response: Verify that the destination is not null.

BRM.10.2214 Invalid destination class: "<class>"

Cause: The client attempted to use a foreign destination.
Response: Verify that the destination is a webMethods destination.

BRM.10.2215 Invalid destination: "<destination>". Wildcard not allowed.

Cause: The client attempted to publish to a wildcard destination.
Response: It is invalid to publish to a wildcard destination.

BRM.10.2216 Invalid destination: "<destination>"

Cause: The client attempted to use a destination with an invalid name.
Response: Verify that the destination name is valid.

BRM.10.2217 Invalid queue "<queue>"; client not connected to territory "<territory>".

Cause: The client attempted to create a message consumer for a queue in a different territory.
Response: Verify that the client has access to the fully qualified queue name.

BRM.10.2218 Invalid queue "<queue>"; client not currently connected to Broker "<broker>".
Cause: The client attempted to create a message consumer for a queue on a different Broker.
Response: Verify that the client has access to the fully qualified queue name.

68 webMethods Error Message Reference Version 6.5 and 6.5.1

BRM (JMS Provider)

BRM.10.2219 Client group "<clientGroup>" does not exist.

Cause: The client attempted to use a client group that does not exist on the Broker.
Response: The client group must be created on the Broker.

BRM.10.2220 Connection factory is null.

Cause: The administration client passed null to a method that requires a connection factory.
Response: Pass a non-null connection factory.

BRM.10.2221 Destination is null.

Cause: The administration client passed null to a method that requires a destination.
Response: Pass a non-null destination.

BRM.10.4001 No response from Broker "<broker>".

Cause: The client failed to receive a response from the Broker within the Broker timeout value because either
the Broker stopped running, there was a network outage, or the Broker was too busy to respond.
Response: Verify that the Broker is running and there is network connectivity. You can increase the Broker
timeout value by setting the com.webmethods.jms.brokerTimeout System property.

BRM.10.4002 License expired.

Cause: The Broker's license has expired.
Response: Update the Broker license.

BRM.10.4003 Protocol is missing arguments.

Cause: An internal error indicating that the Broker failed to return all protocol arguments.
Response: No action required.

BRM.10.4004 Broker protocol error.

Cause: An internal error indicating that the Broker sent an invalid reply.
Response: No action required.

BRM.10.4005 Incompatible Broker version. Supported versions are <supportedVersions>.

Cause: The client connected to a Broker whose version is not supported.
Response: Only those Broker versions listed are supported.

webMethods Error Message Reference Version 6.5 and 6.5.1 69

CHAPTER 1 webMethods Broker

BRM.10.4006 No default Broker at <host>.

Cause: The client attempted to connect to the default Broker, but no Broker has been designated as the default
Broker.
Response: Define a default Broker on the Broker Server or have the client provide a Broker name.

BRM.10.4007 Unknown Broker "<broker>".

Cause: The client attempted to connect to a Broker that does not exist.
Response: The client must specify a Broker that exists.

BRM.10.4008 Lost connection to Broker "<broker>".

Cause: The client lost its connection to the Broker.
Response: The Broker has closed the socket connection to the client. Check that the Broker is still running.

BRM.10.4009 Unable to connect to Broker at "<host>": host not found

Cause: The client attempted to connect to a Broker on a host that could not be found.
Response: Verify that the host exists.

BRM.10.4010 Unable to connect to Broker at "<host>": out of resources

Cause: The client failed to connect to the Broker because the Broker ran out of resources.
Response: Increase the number of allowed connections on the machine that the Broker is running on.

BRM.10.4011 Unable to connect to Broker at "<host>": <reason>

Cause: The client failed to connect to the Broker for the indicated reason.
Response: Dependent on the reason for the failed connection.

BRM.10.4012 Invalid port number: <port>

Cause: The client attempted to connect to a Broker using an invalid port number.
Response: The client must use a valid port number.

BRM.10.4013 Unable to connect to Brokers at "<brokerList>".

Cause: The client failed to connect to any of the Brokers in the client's Broker list.
Response: Dependent on the reason for the failed connections.

70 webMethods Error Message Reference Version 6.5 and 6.5.1

BRM (JMS Provider)

BRM.10.4028 Invalid license.

Cause: The Broker's license is invalid.
Response: No action required.

BRM.10.4029 Multiple event requests.

Cause: An internal error indicating that the Broker has received multiple event requests for the same consumer.
Response: No action required.

BRM.10.4030 Operation interrupted.

Cause: An internal error indicating that client's current operation on the Broker has been interrupted.
Response: No action required.

BRM.10.4031 Client has been deleted.

Cause: The client has been administratively deleted.
Response: No action required.

BRM.10.4032 Queue cursor is out of bounds.

Cause: An internal error indicating that the Broker queue's cursor is out of bounds.
Response: No action required.

BRM.10.4033 Acknowledgement is out of order.

Cause: An internal error indicating that message acknowledgement arrived out of order.
Response: No action required.

BRM.10.4034 Duplicate sequence number.

Cause: An internal error indicating that the Broker received a duplicate sequence number.
Response: No action required.

BRM.10.4035 Bad sequence number.

Cause: An internal error indicating that the Broker received an invalid sequence number.
Response: No action required.

webMethods Error Message Reference Version 6.5 and 6.5.1 71

CHAPTER 1 webMethods Broker

BRM.10.4036 Client has been destroyed.

Cause: The client has been administratively destroyed.
Response: No action required.

BRM.10.4037 Broker has run out of storage.

Cause: The Broker to which the client is connected has run out of storage.
Response: No action required.

BRM.10.4038 Protocol is missing arguments.

Cause: An internal error indicating that the command sent to the Broker is incorrect.
Response: No action required.

BRM.10.4039 Broker strorage is corrupt.

Cause: The Broker's storage has become corrupted.
Response: No action required.

BRM.10.4040 Broker storage error.

Cause: The Broker reported a storage error.
Response: No action required.

BRM.10.4041 Command not recognized by Broker.

Cause: An internal error indicating that the command sent to the Broker is not recognized.
Response: No action required.

BRM.10.4042 Broker protocol error: <error>

Cause: An internal error indicating a Broker protocol error.
Response: No action required.

BRM.10.4043 Connection is closed.

Cause: An internal error indicating that the Broker session has been disconnected.
Response: No action required.

72 webMethods Error Message Reference Version 6.5 and 6.5.1

BRM (JMS Provider)

BRM.10.4045 Broker is out of memory.

Cause: The Broker that the client is connected to has run out of memory.
Response: No action required.

BRM.10.4046 Connection to Broker "<broker>" has been reconnected.

Cause: The current operation failed because of reconnection to the Broker.
Response: No action required.

BRM.10.4100 Reconnecting to "<broker>" in <number> seconds.

Cause: The client has lost its connection to the Broker and will be reconnecting.
Response: No action required.

BRM.10.4101 Reconnected successfully to "<broker>".

Cause: The client has successfully reconnected to the Broker.
Response: No action required.

BRM.10.4236 Transaction unknown.

Cause: An internal error indicating that the transaction is unknown.
Response: No action required.

BRM.10.4237 Transaction mismatch.

Cause: An internal error indicating that there is a transaction mismatch.
Response: No action required.

BRM.10.4238 Transaction closed.

Cause: An internal error indicating that an operation was attempted on a closed transaction.
Response: No action required.

BRM.10.4239 Transaction invalid state.

Cause: An internal error indicating that the transaction is in an invalid state for the requested operation.
Response: No action required.

webMethods Error Message Reference Version 6.5 and 6.5.1 73

CHAPTER 1 webMethods Broker

BRM.10.4240 Transaction already open.

Cause: An internal error indicating that an open transaction was attempted to be opened.
Response: No action required.

BRM.10.4241 Transaction cannot be reopened.

Cause: An internal error indicating that a closed transaction was attempted to be reopened.
Response: No action required.

BRM.10.4242 Transaction exists (prepared).

Cause: The client attempted to open a transaction that already exists.
Response: The client must provide a new transaction.

BRM.10.4243 Transaction exists (heuristic).

Cause: The client attempted to open a transaction that already exists.
Response: The client must provide a new transaction.

BRM.10.4244 Transaction has been heuristically rolled-back.

Cause: The client attempted to use a transaction that has been heuristically rolled-back.
Response: The client must provide a new transaction.

BRM.10.4245 Transaction has been heuristically committed.

Cause: The client attempted to use a transaction that has been heuristically committed.
Response: The client must provide a new transaction.

BRM.10.5000 No permissions for current operation.

Cause: The administration client does not have sufficient permissions for the current operation.
Response: The administration client should be using the "admin" client group.

BRM.10.5001 No send permissions for event type "<eventType>" in client group "<clientGroup>".
Cause: The client group being used by the client does not have send permissions for the destination's event
type.
Response: Update the client group permissions to include can publish permissions for the event type.

74 webMethods Error Message Reference Version 6.5 and 6.5.1

BRM (JMS Provider)

BRM.10.5002 No receive permissions for event type "<eventType>" in client group "<clientGroup>"
Cause: The client group being used by the client does not have receive permissions for the destination's event
type.
Response: Update the client group permissions to include can subscribe permissions for the event type.

BRM.10.5003 Client group "<clientGroup>" requires encryption

Cause: The client group being used by the client requires SSL encryption.
Response: Configure the client to use SSL encryption.

BRM.10.5057 SSL handshake failed with Broker at "<host>".

Cause: The client was unable to connect with SSL to the Broker Server.
Response: Verify that SSL has been configured correctly on both the Broker Server and the client.

BRM.10.5058 SSL not running on Broker at "<host>"

Cause: The Broker Server is not configured for SSL.
Response: Configure the Broker Server for SSL.

BRM.10.5059 SSL is not available: <reason>

Cause: The SSL library could not be loaded for the indicated reason.
Response: Dependent on the reason.

BRM.10.5060 SSL certificate "<distinguishedName>": not found

Cause: A certificate for the distinguished name was not found in the client's keystore.
Response: The client's keystore must contain a certificate for the distinguished name.

BRM.10.5061 SSL certificate "<distinguishedName>": bad

Cause: The client's certificate is bad.
Response: The client needs a valid certificate.

BRM.10.5062 SSL certificate is null.

Cause: The client provided a null keystore name.
Response: The client must specify a non-null keystore name.

webMethods Error Message Reference Version 6.5 and 6.5.1 75

CHAPTER 1 webMethods Broker

BRM.10.5063 SSL certificate "<distinguishedName>": invalid password

Cause: The client provided an incorrect password for the keystore.
Response: Provide a correct password for the keystore.

BRM.10.5064 SSL context create failed: <reason>

Cause: The client was unable to create an SSL context.
Response: Dependent on the reason.

BRM.10.5065 SSL client certificate is expired.

Cause: The client's certificate is expired.
Response: The client needs a new certificate.

BRM.10.5066 SSL certificate for distinguished name "<distinguishedName>" not found.

Cause: The client's keystore does not contain a certificate for the specified distinguished name.
Response: Verify that the client's keystore contains a certificate for its distinguished name.

BRM.10.5067 SSL certificate file contains multiple valid certificates.

Cause: The client's keystore contains multiple certificates for the same distinguished name.
Response: The client's keystore should contain only one certificate for its distinguished name.

BRM.10.5068 SSL distinguished name "<distinguishedName>" is malformed.

Cause: The client provided a malformed distinguished name.
Response: Fix the format of the distinguished name.

BRM.10.5069 SSL unknown error.

Cause: An unknown SSL error occurred.
Response: Contact webMethods Customer Care.

BRM.10.5070 SSL certificate is not certified.

Cause: The Broker Server's certificate is not trusted.
Response: Verify that the client's keystore contains the correct trusted certificates in order to certify the Broker
Server's certificate.

76 webMethods Error Message Reference Version 6.5 and 6.5.1

BRM (JMS Provider)

BRM.10.5071 SSL server certificate is expired.

Cause: The Broker Server's certificate has expired.
Response: Configure the Broker Server with a new certificate.

BRM.10.5100 Cannot make SSL connection to Broker: keystore is missing.

Cause: The administration client attempted to create an SSL connection to the Broker without specifying a
keystore.
Response: Specify a keystore.

BRM.10.5101 Cannot make SSL connection to Broker: username is missing.

Cause: The administration client attempted to create an SSL connection to the Broker without specifying a
distinguished name.
Response: Specify a distinguished name.

BRM.10.5102 Cannot make SSL connection to Broker: password is missing.

Cause: The administration client attempted to create an SSL connection to the Broker without specifying a
password.
Response: Specify the keystore's password.

webMethods Error Message Reference Version 6.5 and 6.5.1 77

CHAPTER 1 webMethods Broker

Broker C API

Bad State (200-1000): Cannot register callback for a sub ID before registering a general callback.
Cause: The Broker could not execute the callback for the requested tag or sub-id because the client did not
register a general callback first. To use a specific callback, a client must register a general callback first.
Response: Register a general callback first, then register specific callbacks for a BrokerClient.

Bad State (200-1001): Cannot register callback for a tag before registering a general callback.
Cause: The Broker could not execute the callback for the requested tag or sub-id because the client did not
register a general callback first. To use a specific callback, a client must register a general callback first.
Response: Register a general callback before registering a specific callback for a BrokerClient.

Bad State (200-1002): This operation cannot be called from within a callback function.
Cause: The callback function was unable to issue a call to awDispatch() or awMainloop() because a blocking
call to awDispatch() or awMainLook() is active in another thread.
Response: Do not issue the function calls within the callback function.

Bad State (200-1003): There are no clients currently connected.

Cause: The socket connection between the Broker client and the Broker is no longer established.
Response: Ensure that a connection between the Broker client and the Broker is established. Use the Broker
Administrator or the Broker command line utilities to view the connection status.

Bad State (200-1004): A general callback must be registered before request-and-wait operations can be issued.
Cause: A "publish request" and wait for reply call was issued before a general callback was registered.
Response: Register a general callback before issuing a publish request, then wait for reply calls.

Bad State (200-1005): Cannot get the Broker's distinguished name because the client is not connected using secure sockets.
Cause: The Broker client attempted to access SSL information on a non-SSL client connection.
Response: Make sure that the client is enabled with SSL before issuing any SSL-specific API calls.

Bad State (200-1006): Cannot get the access label because the access label feature is not enabled. No access label adapter
process is connected to the Broker.
Cause: An access label adapter is not running to support the access label feature.
Response: To use the access label feature, enable and start an access label adapter on the Broker.

78 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Bad State (200-1007): Could not release Broker change lock. The Broker change lock is not currently held by a client.
Cause: The Broker administrative client could not release the change lock because the lock is not currently held
by a client.
Response: Acquire the change lock, then invoke this call.

Bad State (200-1008): Could not release Broker change lock. The Broker change lock is currently held by client <clientID>,
session <sessionID>, and was locked at <lockTime>.
Cause: The Broker administrative client could not acquire or release the change lock because the lock is held by
a different client. The change lock is held by <clientID>.
Response: Acquire or release the Broker change lock on <clientID> as appropriate, then reissue the change lock
request.

Bad State (200-2027): Territory gateway is already paused.

Cause: A client attempted to pause a territory gateway that is already paused.
Response: Make sure that the gateway is not already paused before attempting a pause operation.

Bad State (200-2028): Territory gateway is already resumed.

Cause: A client attempted to resume a territory gateway that was not paused.
Response: Make sure that the gateway is paused before attempting a resume operation.

Bad State (200-3780): Inconsistent queue state for client <clientID>.

Cause: The Broker administrative client attempted to lock a client queue that was already locked or unlock a
client queue that was not locked.
Response: If this error occurs during an awAcquireClientQueueLock(s) call, check the client queues; they may
already be locked. If this error occurs during an awReleaseClientQueueLock(s) call, check the client queues;
they may not be locked.

Broker Exists (230-1530): Cannot create Broker. The Broker <broker> already exists.
Cause: A Broker name that was specified with the awCreateBroker() call already exists on the Broker Server.
Response: Reissue the awCreateBroker request using a valid, unused name for the Broker.

Broker Failure (100-1010): A failure occurred on the Broker. The error code is <code> and the message is <failString>.
Cause: The response from the Broker could not be read properly.
Response: One of the parameters in the error message <failString> contains additional information about the
failure. Review the error message to determine the appropriate action. Contact Technical Services for further
assistance.

webMethods Error Message Reference Version 6.5 and 6.5.1 79

CHAPTER 1 webMethods Broker

Broker Failure (100-1011): A failure occurred on the Broker. An uninterpretable reply was sent back.
Cause: The response from the Broker could not be read properly.
Response: Unknown error. Check the Broker log files for relevant entries in this timeframe.

Broker Failure (100-1012): The operation failed because the Broker is running out of memory. Alert your administrator.
Cause: The Broker could not allocate enough memory to complete the operation.
Response: Ensure that enough memory is available on the Broker Server host machine as well as the Broker
process.

Broker Failure (100-1013): The document was too large for the Broker to process successfully.
Cause: The Queue Manipulation operation failed because the document was too large to add to the queue.
Response: Ensure that the document that is to be inserted into the queue is a valid BrokerEvent size.

Broker Failure (100-1014): The operation failed because the Broker is having storage problems. Alert your
administrator.
Cause: A default Broker could not be created because of storage corruption or invalid storage files.
Response: Make sure that the storage files are created and present in the data directory.

Broker Failure (100-1016): The Broker was unable to join the territory. The error code is <failString>.
Cause: The Broker could not join the territory because the connection between the Broker and the Broker
territory was interrupted or disconnected.
Response: Check the network connection between the two Broker hosts. Make sure that the connection is
established and then retry the join operation.

Broker Failure (100-1017): The Broker was unable to join the territory, because the other Broker is busy processing another
territory operation. This is usually a temporary failure, so try again. If the failure persists, check to make sure you are not
trying to join the Broker to itself.
Cause: The Broker is unable to join the territory at this time. The territory Broker may be processing another
territory operation.
Response: Wait for the territory Broker to complete the operation and then try again.

Broker Failure (100-1018): An error occurred in the Broker while looking up the client's access label.
Cause: The request to the access label adapter has timed out or the access label adapter has stopped
responding.
Response: Check the access label adapter status to see if it is running. Restart the access label adapter if
necessary.

80 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Broker Failure (100-1019): The access label adapter process reported an error in looking up the client's access label.
Cause: The access label adapter process could not look up the client's access label. The access label adapter may
not be running.
Response: Check the access label adapter status to see if it is running. Restart the access label adapter if
necessary.

Broker Failure (100-2010): The gateway operation failed. The error code is <failString>.
Cause: The gateway operation did not complete because a request to create a gateway or update the shared
document types on the gateway failed.
Response: One of the parameters in the error message <fail_string> contains additional information about the
failure. Review the error message to determine the appropriate action.

Broker Failure (100-2013): The Broker was unable to complete the operation, because it is busy processing another territory
operation. This is usually a temporary failure, so try again.
Cause: The Broker is busy processing another territory operation.
Response: Wait for the territory operation to complete and then reissue the request.

Broker Failure (100-2014): Broker was unable to join the territory. The other Broker is using an incompatible software
version.
Cause: The Broker could not join the territory because the version of the Broker and the territory Broker are not
compatible.
Response: Check the webMethods Broker documentation for information about backward compatibility.

Broker Failure (100-2015): The operation failed because the Broker does not have enough storage to process the request.
Alert your administrator.
Cause: The Broker Server does not have enough storage space available to complete the operation.
Response: Contact your system administrator.

Broker Failure (100-2016): The operation failed because the Broker does not have permission to write to the server
configuration file.
Cause: The Broker does not have permission to write to the Broker Server's configuration file.
Response: Verify the permissions on the Server configuration files. Make sure that the permissions are set
properly and then reissue the operation.

webMethods Error Message Reference Version 6.5 and 6.5.1 81

CHAPTER 1 webMethods Broker

Broker Failure (100-2017): The operation failed because the Broker does not have enough disk space to write to the server
configuration file.
Cause: The Broker does not have enough disk space to update the Broker Server's configuration file.
Response: Increase the storage space. Use the Broker command line utilities to add storage files or to make
room on the existing store.

Broker Failure (100-2018): The operation failed because the Broker was unable to write to the server configuration file.
Cause: The Broker does not have permission to write to the Broker Server's configuration file.
Response: Verify the permissions on the Server configuration files. Make sure that the permissions are set
properly and then reissue the operation.

Broker Failure (100-2019): The opereration failed because the Broker was attempted to contact another Broker at the same
time that Broker was attempting to contact it. Please retry your operation.
Cause: The Broker attempted to connect to the remote Broker while a connection attempt was in progress on a
different thread.
Response: Allow the connection attempt to complete and then issue a new connection request.

Broker Failure (100-2020): The operation failed because the name of the locale does not conform to POSIX locale naming
standards.
Cause: The local name specified does not confirm to POSIX standards.
Response: Check the POSIX compliance on the locale name and then reissue the operation.

Broker Failure (100-2021): The operation failed because the specified character set is not supported on the Broker.
Cause: The specified character set is not supported on the Broker.
Response: Install and add support for the character set on the Broker.

Broker Failure (100-2022): The operation failed because the requested locale is not installed on the Broker's host.
Cause: The Broker Server host does not support the specified locale.
Response: Install OS support for the specified locale on the Broker Server host machine.

Broker Not Running (101-1020): The host <hostName> was found, but no Broker Server is running on port <portNum> on that
host.
Cause: The Broker Server is not running on the port specified.
Response: Use the Broker Administrator or the broker_start command line utility to start the Broker Server.

82 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Broker Not Running (101-1021): The host <hostName> was found, but no Broker Server is running with secure sockets
support on port <portNum> on that host.
Cause: The Broker Server does not have SSL support enabled.
Response: Use the Broker Administrator to enable SSL support on the Broker Server.

Broker Not Running (101-1023): The gateway operation could not be completed, because the Broker in the other territory is
not running or could not be successfully connected to.
Cause: The connection attempt between the gateway Brokers failed. Either the connection between the gateway
Brokers has closed or the remote Broker is not running.
Response: Verify that the remote Brokers across the gateway are connected and running.

Client Contention (201-1030): Cannot reconnect client <clientID>. Another process is already connected to the Broker and is
using this client.
Cause: The Broker client is in use by another client.
Response: Verify that the client ID used by the Broker client is unique and is not used by another client
connection.

Client Contention (201-1031): Cannot reconnect client <clientID>. The maximum number of reconnections for this shared
state client has been exceeded.
Cause: The Broker client's shared state limit has been exceeded. A new session cannot be created for the
specified Broker client.
Response: Increase the client's shared limit and try again.

Client Exists (202-1040): Cannot create client <clientID>. The client has already been created.
Cause: A Broker client named <clientID>already exists on the Broker.
Response: Use a unique name for the client ID.

Client Group Exists (231-1540): Cannot create client group. The client group <clientgroupName> already exists on the Broker.
Cause: A client group named <clientgroupName>already exists on the Broker.
Response: Use a unique name for the client group.

webMethods Error Message Reference Version 6.5 and 6.5.1 83

CHAPTER 1 webMethods Broker

Communications Failure (102-1050): Failed to create client session with the Broker on host <hostName> and port <portNum>.
Perhaps this port does not have a Broker installed on it, or the Broker is overloaded and cannot accept the connection.
Cause: The client session could not be created on the Broker because a connection to the Broker could not be
established. Either the Broker is not running or it is too busy to accept a new client connection.
Response: Verify that the Broker is running. If it is running, then wait for the Broker to become available and
try again.

Communications Failure (102-1051): Initialization of the transport failed.

Cause: Transport initialization failed. The Broker Server host may be running out of resources. For example,
file handles or memory may be low.
Response: Transport initialization failed. Contact your system administrator.

Communications Failure (102-1052): Unable to find host <hostName>. Error <errorCode> was reported by the
gethostbyname call.
Cause: The Broker Server host name cannot be accessed.
Response: Compare the error code output with the native platform's error messages and fix any issues.

Communications Failure (102-1053): Could not write to the interrupt pipe.

Cause: The Broker Client could not write to the interrupt pipe because a request to interrupt the socket write
activity could not be completed.
Response: None.

Communications Failure (102-1054): The connection is closed.

Cause: The connection object for the Broker client connection might be NULL or invalid.
Response: Check the client connection.

Communications Failure (102-1055): Unable to connect to host <hostName>. It is not currently on the network.
Cause: The Broker Server host <hostName> is not currently on the network.
Response: Verify that the Broker Server host exists on the current node and can be accessed on the network.

Communications Failure (102-1056): Unable to open connection to host <hostName> due to a lack of network resources. Too
many connections may already be open.
Cause: The Broker Server host <hostName> may have too many connections open.
Response: First, verify that the Broker Server host exists on the current node and can be accessed on the
network. Then, check the number of connections on the Broker Server host. If necessary, decrease the number
of connections and then try again.

84 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Communications Failure (102-1057): Unable to connect to host <hostName>. Error <errorCode> <errorString> was reported
by the connect call.
Cause: The Broker client could not establish a connection to Broker Server host <hostName>. Error <errorCode>
<errorString> was reported by the connect call.
Response: Verify that the Broker Server host exists on the current node and can be accessed on the network. For
more information about this error, refer to the error code and error string.

Communications Failure (102-1058): Unable to find open connection to host <hostName>. Error <errorCode> <errorString>
was reported by the socket call.
Cause: The Broker client could not find an open connection to Broker Server host <hostName>. Error
<errorCode> <errorString> was reported by the socket call.
Response: Verify that the Broker Server host exists on the current node and can be accessed on the network. For
more information about this error, refer to the error code and error string.

Communications Failure (102-1059): Unable to check connections. Error <errorCode> <errorString> was reported by the
select call.
Cause: Unable to check connections. Error <errorCode> <errorString> was reported by the select call.
Response: Verify that the TCP/IP services are running. Check the system and Broker logs for additional
information around this error.

Communications Failure (102-1060): Unable to send to Broker. Error <errcode> <errstring> was reported by the send call.
Cause: The Broker client is unable to communicate with the Broker Host. Error <errorCode> <errorString> was
reported by the send call.
Response: Verify that the TCP/IP services and the remote Broker are active.

Connection Closed (103-1070): The connection is closed.

Cause: The connection to the Broker is closed. The Broker or the Broker host may not be responding or the
Broker has terminated the connection to this Broker client.
Response: Verify that the Broker and Broker Server host are responding and check the network connection.

Corrupt (104-1080): The document field data has been corrupted.

Cause: The document field data has been corrupted.
Response: Make sure that the document is valid.

webMethods Error Message Reference Version 6.5 and 6.5.1 85

CHAPTER 1 webMethods Broker

Corrupt (104-1081): The type definition data has been corrupted.

Cause: The type definition data has been corrupted.
Response: Recreate the document type by importing any saved ADL files.

Dependency (232-1551): Client group destroy failed. The client group has existing clients which should be destroyed first.
Cause: The destroy client group operation failed. The Broker client group has existing clients that must be
destroyed first.
Response: Remove the clients from the client group and then reissue the client group destroy request.

Dependency (232-1552): Document type destroy failed. The document type has client groups which can publish or can
subscribe to the type. These permissions should be removed first.
Cause: The destroy document type operation failed. There is at least one client group that has "can publish" or
"can subscribe" permissions assigned to this document type.
Response: Remove all the "can publish" or "can subscribe" permissions for this document type and then reissue
the document type destroy request.

Field Not Found (203-1090): The field <fieldName> could not be found in the document.
Cause: The field <fieldName> could not be found in the document.
Response: Make sure that the specified field name exists in the document.

Field Not Found (203-1091): The field <fieldName> is not defined in the document type definition.
Cause: [DELETED] The field <fieldName> is not defined in the document type definition.
Response: Make sure that the specified field name is defined in the document type definition.

Field Type Mismatch (204-1110): Field type mismatch when looking up <fieldName>. A field of a non-sequence type is being
accessed as if it were a sequence.
Cause: The field type does not match the <fieldName> field. A sequence type operation can only be performed
on a sequence type field.
Response: Make sure that only sequence type operations are performed on sequence type fields.

Field Type Mismatch (204-1111): Field type mismatch when looking up <fieldName>. A field of a non-structured type is being
accessed as if it were a struct.
Cause: The field type does not match the <fieldName> field. A non-struct type field is being accessed when a
struct type is expected.
Response: Make sure that operations that are valid on the struct data type are applied on struct fields.

86 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Field Type Mismatch (204-1112): Field type mismatch when looking up <fieldName>. A field of a basic type is being accessed
as if it were a struct or sequence.
Cause: The field type does not match the <fieldName> field. A basic type field is being accessed when a struct
or sequence type is expected.
Response: Make sure that operations that are valid on struct or sequence data types are applied on struct or
sequence fields.

Field Type Mismatch (204-1113): Field <fieldName> cannot be cleared because it is not a valid field.
Cause: Field <fieldName> is not a valid field and cannot be cleared.
Response: Make sure that the field specified by <fieldName> is a valid field.

Field Type Mismatch (204-1114): Field <fieldName> in the document is not of type <fieldType> as defined in the type
definition.
Cause: Field <fieldName> in the document does not match type <fieldType> as defined in the type definition.
Response: Make sure that the fields on the document matche the type definition.

Field Type Mismatch (204-1115): Field <fieldName> in the document is not a sequence of type <fieldType> as defined in the
type definition.
Cause: Field <fieldName> in the document does not match the stored type definition for a sequence type
<fieldType>.
Response: Make sure that the fields on the document match the type definition.

Field Type Mismatch (204-1116): The field <fieldName> must be a sequence for this operation.
Cause: The field <fieldName> is not a sequence. The field must be a sequence for this operation.
Response: Make sure the field is a sequence data type.

Field Type Mismatch (204-1117): The field <fieldName> must be a struct for this operation.
Cause: The field <fieldName> is not a struct. The field must be a struct for this operation.
Response: Make sure the field is a struct data type.

Field Type Mismatch (204-1118): Field <fieldName> is not of type <fieldType>.

Cause: The Field <fieldName> does not match the requested field type.
Response: Make sure the field types match.

webMethods Error Message Reference Version 6.5 and 6.5.1 87

CHAPTER 1 webMethods Broker

Field Type Mismatch (204-1119): Field <fieldName> is not a sequence of type <fieldType>.
Cause: The field <fieldName> is not a sequence type field. The field must be a sequence type field for this
operation.
Response: Make sure the field is a sequence type.

Field Type Mismatch (204-1120): Field <fieldName> has a sequence being accessed with a field name. Sequence types only
have a '[]' field.
Cause: Field <fieldName> has a sequence being accessed with a field name. Sequence types only have a "[]"
field.
Response: Make sure that the sequence field is accessed with a "[]" field and not with field names.

Field Type Mismatch (204-1121): Cannot convert document to string. The document does not match its type definition.
Cause: The Broker Client cannot convert the document to a string because the document does not match its
type definition.
Response: Make sure that a valid document is used.

Field Type Mismatch (204-1122): Validation failed. The document does not match its type definition.
Cause: Validation failed. The document does not match its type definition.
Response: Make sure that a valid document is used.

Field Type Mismatch (204-1123): Sequence field <fieldName> cannot be resized because its type is not known.
Cause: Sequence field <fieldName> cannot be resized because its type is not known.
Response: Check the sequence type and make sure it is one of the know data types.

File Not Found (113-1128): Secure socket certificate file <certFile> was not found.
Cause: The Secure socket certificate file <certFile> was not found.
Response: Verify that the secure socket certificate file exists in the location specified during SSL configuration.

File Not Found (113-1129): Secure socket certificate file <certFile> was not found on the Broker host.
Cause: The secure socket certificate file <certFile> was not found on the Broker Server host.
Response: Verify that the secure socket certificate file exists in the location specified during SSL configuration.

88 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Filter Parse Error (205-1130): A syntax error was encountered while parsing the filter. <parseMsg>
Cause: A syntax error was encountered while parsing the filter.
Response: Make sure that the filter string is valid and syntactically correct.

Filter Parse Error (205-1131): Parser stack underflow. <parseMsg>

Cause: An operation encountered a stack underflow error while parsing the filter string. Check the error
message <parseMsg> for more details.
Response: Verify that the filter string is valid and syntactically correct.

Filter Parse Error (205-1132): The filter contains an invalid character constant. <parseMsg>
Cause: The filter contains an invalid character constant.
Response: Make sure that the filter is valid and the syntax in the filter is correct.

Filter Parse Error (205-1133): The filter contains a string that is missing its closing quotation mark. <parseMsg>
Cause: The filter contains a string that is missing a closing quotation mark.
Response: Check the syntax for the filter strings. Make sure that the quotation symbols are used correctly.

Filter Parse Error (205-1134): The field <fieldName> does not exist. <parseMsg>
Cause: The field <fieldName> is not found in the document type definition.
Response: Verify that the field names specified in the filter are valid and present in the document type
definition.

Filter Parse Error (205-1135): The function <function> does not exist. <parseMsg>
Cause: The function <function> does not exist. The specified function is not valid or not supported by the filter
compiler.
Response: Verify that the filter string is valid and only supported functions are used. Refer to the API
documentation for the list of supported functions.

Filter Parse Error (205-1136): The filter contains an invalid number. <parseMsg>
Cause: The filter contains an invalid number.
Response: Verify that the filter string is valid and that the correct parameters are used.

webMethods Error Message Reference Version 6.5 and 6.5.1 89

CHAPTER 1 webMethods Broker

Filter Parse Error (205-1137): An unexpected character was encountered while parsing the filter. <parseMsg>
Cause: An unexpected character was encountered while parsing the filter.
Response: Make sure that the filter string is valid and syntactically correct.

Filter Parse Error (205-1138): The type <fieldType> was found where a Boolean type was expected. <parseMsg>
Cause: The type <fieldType> was found where a Boolean type was expected.
Response: Verify that the filter string is valid and uses the correct parameters.

Filter Parse Error (205-1139): The type <fieldType> was type was found where a string, date or numeric type was expected.
<parseMsg>
Cause: The type <fieldType> was found where a string, date or numeric type was expected. Or, a sequence or
struct type was found where a basic type was expected.
Response: Verify that the filter string is valid and uses the correct parameters.

Filter Parse Error (205-1140): The type <type> was found where a numeric type was expected. <parseMsg>
Cause: A numeric type was expected while evaluating a numeric expression in the filter, but a non-numeric
type was found.
Response: Verify that the filter string is valid and the correct parameter types are passed.

Filter Parse Error (205-1141): The type <type> was found where an integral type was expected. <parseMsg>
Cause: The type <type> was found where an integral type was expected. An integral type is needed for certain
operations, such as bit-wise operations.
Response: Verify that the filter string is valid and correct parameters are passed.

Filter Parse Error (205-1142): The types <type1> and <type2> are incompatible for comparison. <parseMsg>
Cause: The types <type1> and <type2> are incompatible for comparison.
Response: Verify that the filter string is valid and correct.

Filter Parse Error (205-1143): The function <function> does not have enough parameters. <parseMsg>
Cause: The function <function> does not have enough parameters.
Response: Verify that the correct number of parameters are passed to the functions in the filter.

90 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Filter Parse Error (205-1144): The function <function> has too many parameters. <parseMsg>
Cause: The function <function> has too many parameters. Too many arguments are being passed to a filter
function.
Response: Make sure that the correct number of parameters are passed to the functions used in the filter.

Filter Parse Error (205-1145): One of the parameters to the function <function> is the wrong type. <parseMsg>
Cause: One of the function parameters <function> is the wrong type.
Response: Verify that the functions specified in the filter are passed with parameters of expected types.

Filter Parse Error (205-1146): An internal error was encountered while parsing the filter. <parseMsg>
Cause: The filter may contain an invalid unary operation.
Response: Verify that the filter string is valid and that the operations specified in the filter are valid.

Filter Parse Error (205-1147): The filter contains an invalid escape character. <parseMsg>
Cause: The filter contains an invalid escape character.
Response: Make sure that the filter is valid and the syntax in the filter is correct.

Filter Parse Error (205-1148): The function <function> has the wrong number of parameters. <parseMsg>
Cause: The wrong number of parameters were passed to the <function> function.
Response: Make sure that the filter string is valid and that the parameters passed to the functions used in the
filter are correct.

Filter Parse Error (205-1149): Incomplete hint field. <parseMsg>

Cause: The filter string specified an incomplete hint field.
Response: Verify that the filter string is valid and complete.

Filter Parse Error (205-1166): The regular expression error <regexpError> occurred while applying the filter.
Cause: The regular expression error <regexpError> occurred while applying the filter.
Response: Make sure that the regular expressions specified in the filter are valid and correct.

webMethods Error Message Reference Version 6.5 and 6.5.1 91

CHAPTER 1 webMethods Broker

Filter Runtime Error (206-1160): The filter operation resulted in a division by zero.
Cause: The filter operation could not complete. The evaluation of the filter expression at run time resulted in a
division by zero.
Response: Make sure that the filter string is valid and does not result in a division by zero condition while
evaluating operands.

Filter Runtime Error (206-1161): The operands are not of the same type and they cannot be promoted to be of the same type.
Cause: A type mismatch occurred. The operands are not the same type and they cannot be promoted to the
same type.
Response: Make sure that the filter string is valid and that the operands are either the same type or can be
promoted to the same type.

Filter Runtime Error (206-1162): The document type does not match.
Cause: The document type of the passed document and the document type specified in the filter do not match.
Response: Make sure that the passed document is the same type as specified in the filter.

Filter Runtime Error (206-1163): The value passed to <function> is not valid.
Cause: The value passed to <function> is not valid.
Response: Make sure that the filter string is valid and passed with correct values for parameters.

Filter Runtime Error (206-1164): The filter result is not a boolean.

Cause: The filter string returned an error because the filter result is not a Boolean.
Response: Make sure that the filter string evaluates to a Boolean value.

Filter Runtime Error (206-1165): After completion, the filter had remaining stack entries.
Cause: The filter string syntax may be incorrect or the string itself may be invalid.
Response: Make sure that the filter string is valid and syntactically correct.

Filter Runtime Error (206-1166): The regular expression error <regExpError> occurred while applying the filter.
Cause: The regular expression error <regExpError> occurred while applying the filter. The specified regular
expression might be invalid or incorrect.
Response: Make sure that the filter string is valid and that all specified regular expressions are correct.

92 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Filter Runtime Error (206-1167): A filter stack overflow has occurred.

Cause: The filter string might be invalid.
Response: Make sure that the filter string is valid.

Filter Runtime Error (206-1168): A filter stack underflow has occurred.

Cause: The filter string might be invalid.
Response: Make sure that the filter string is valid.

Filter Runtime Error (206-1169): An unexpected function was encountered while applying the filter.
Cause: The filter string might be invalid or might contain unsupported functions.
Response: Make sure that the filter string is valid and contains only supported functions. For more information
about supported functions, refer to the webMethods Broker API documentation.

Filter Runtime Error (206-1170): An unexpected operation was encountered while applying the filter.
Cause: The filter string might be invalid or might contain unsupported operations.
Response: Make sure that the filter string is valid and contains only supported operations. For more
information about supported functions, refer to the webMethods Broker API documentation.

Filter Runtime Error (206-1171): An unexpected type was encountered while applying the filter.
Cause: The specified filter may not be valid. An unexpected type was encountered while applying the filter.
Response: Make sure that the specified filter is valid.

Format Error (207-1180): Error in parsing document bin string body header.
Cause: The bin string might be invalid.
Response: Make sure that the bin string is valid and obtained from a valid BrokerEvent.

Format Error (207-1181): Error in parsing document bin string data.

Cause: The bin string may be invalid or might have been obtained from an invalid BrokerEvent.
Response: Make sure that the bin string is valid and was obtained from a valid BrokerEvent.

Format Error (207-1182): Error in parsing document bin string envelope header.
Cause: The bin string may be invalid or might have been obtained from an invalid BrokerEvent.
Response: Make sure that the bin string is valid and was obtained from a valid BrokerEvent.

webMethods Error Message Reference Version 6.5 and 6.5.1 93

CHAPTER 1 webMethods Broker

Format Error (207-1183): Error parsing numeric value.

Cause: A numeric value was expected in the string representation.
Response: Make sure that a proper number value is passed in the string.

Format Error (207-1184): Document claims to be larger than the size allocated for it.
Cause: The document may be invalid or may have been corrupted.
Response: Check the document to make sure that it is valid.

Format Error (207-1185): The type definition typecode contained a format error.
Cause: The type definition typecode contained a format error.
Response: Make sure that the type definition of the document is valid and syntactically correct.

Host Not Found (105-1190): Unable to find host <host> on the network.
Cause: The <host> host could not be found on the network.
Response: Make sure that the host exists on the network and is reachable from the current node.

Host Not Found (105-1191): Unable to find host <host> on the network. A server failure may have occurred.
Cause: The <host> host could not be found on the network. A server failure may have occurred.
Response: Make sure that the specified host is reachable and is currently running.

Host Not Found (105-1192): Territory join failed. Unable to find host <host> on the network.
Cause: The territory join request failed because the Broker was unable to find the <host> host on the network.
Response: Make sure that the host exists on the network and is reachable.

In Territory (234-1570): The Broker cannot join a territory because it is already in a territory.
Cause: The Broker cannot join a territory because it already belongs to a territory.
Response: Verify that the current Broker does not already exist as part of a territory.

In Territory (234-1571): The Broker cannot be destroyed while it is in a territory with other Brokers. It must leave the territory
first.
Cause: A request to destroy the Broker failed because it is still in a territory with other Brokers.
Response: You cannot destroy a Broker while it exists in a territory with other Brokers. Remove it from the
territory, then retry this operation.

94 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Incompatible Version (106-1033): Check for events is not supported on this version of the Broker.
Cause: The check for events feature is not supported on the version of Broker that the client is currently
connected to.
Response: Make sure that the Broker is version is 6.1 or higher.

Incompatible Version (106-1200): The Broker is from webMethods Broker 3.0 or earlier (also known as ActiveWorks) and is
not compatible with this version of the client library.
Cause: The Broker is from webMethods Broker 3.0 or earlier (also known as ActiveWorks) and is not
compatible with this version of the client library.
Response: Upgrade to a newer version of webMethods Broker.

Incompatible Version (106-1201): The Broker is not compatible with this version of the client library. The Broker is running a
newer version of webMethods Broker.
Cause: The Broker is not compatible with this version of the client library. The Broker is running a newer
version of webMethods Broker.
Response: Upgrade to a newer version of webMethods Broker where this feature is supported.

Incompatible Version (106-1203): The Broker Server is not compatible with this version of the client library. The Broker
Server is running a newer version of webMethods Broker.
Cause: The Broker Server is not compatible with this version of the client library. The Broker Server is running
a newer version of webMethods Broker.
Response: Either point to the version of Broker that is compatible with the libraries or upgrade libraries to the
Broker version.

Incompatible Version (106-1205): The Broker Server Monitor is not compatible with this version of the client library. The
Broker Server Monitor is running a newer version of webMethods Broker.
Cause: The Broker Server Monitor is not compatible with this version of the client library. The Broker Server
Monitor is running a newer version of webMethods Broker.
Response: Upgrade to newer version of webMethods Broker.

Incompatible Version (106-1206): The Broker does not support setting subscription filters for territory gateways.
Cause: This version of webMethods Broker does not support setting subscription filters for territory gateways.
Response: Upgrade to newer version of webMethods Broker where this feature is supported.

webMethods Error Message Reference Version 6.5 and 6.5.1 95

CHAPTER 1 webMethods Broker

Incompatible Version (106-1207): The Broker Server does not support access to a server log.
Cause: This version of webMethods Broker does not support access to a server log.
Response: Upgrade to a newer version of webMethods Broker where this feature is supported.

Incompatible Version (106-1208): The Broker does not support changelocks.

Cause: This version of the Broker does not support the change locks feature.
Response: Upgrade to newer version of webMethods Broker where this feature is supported.

Incompatible Version (106-1209): The Broker does not support document type validation types other than full validation.
Cause: This version of Broker does not support document type validations other than full validation.
Response: Upgrade to a newer version of webMethods Broker where this feature is supported.

Incompatible Version (106-1390): The requested operation is not implemented in this release.
Cause: The requested operation is not implemented in this release.
Response: Refer to the webMethods Broker API documentation or contact webMethods Technical Services for
further assistance.

Incompatible Version (106-2023): The Broker Server does not support setting the filter collation locale.
Cause: This version of webMethods Broker does not support setting filter collation locale.
Response: Upgrade to a newer version of webMethods Broker where this feature is supported.

Incompatible Version (106-2024): Redelivery counting is not supported on this version of the Broker.
Cause: Redelivery counting is not supported on the version of Broker that the client is currently connected to.
Response: Make sure that the Broker is version is 6.1 or higher.

Incompatible Version (106-2025): Territory gateway keep alive is not supported on this version of the Broker.
Cause: Territory gateway keep-alive is not supported on the version of Broker that the client is currently
connected to.
Response: Make sure that the Broker is version is 6.1 or higher.

Incompatible Version (106-2026): Territory gateway pause is not supported on this version of the Broker.
Cause: Territory gateway pause is not supported on the version of Broker that the client is currently connected
to.
Response: Make sure that the Broker is version is 6.1 or higher.

96 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Incompatible Version (106-3771): QM feature not supported in this version.

Cause: This version of the Broker does not support the queue manipulation feature.
Response: Upgrade to newer version of webMethods Broker where this feature is supported.

Incompatible Version (106-3796): Transactions not supported in this version.

Cause: This version of webMethods Broker does not support transactions.
Response: Upgrade to a newer version of webMethods Broker where this feature is supported.

Incompatible Version (106-3797): Event logging feature not supported in this version.
Cause: This version of the Broker does not support the document logging feature.
Response: Upgrade to newer version of webMethods Broker where this feature is supported.

Incompatible Version (106-3798): Transactions not supported in this version.

Cause: Transactions are not supported on the version of Broker that the client is currently connected to
Response: Make sure that the Broker is version is 6.1 or higher.

Interrupted (107-1210): The operation was interrupted by request.

Cause: The operation was interrupted by a user request.
Response: None.

Interrupted (107-1211): The operation was interrupted by a signal.

Cause: A system call to read from sockets was interrupted by a signal.
Response: Check the system log and Broker logs for more information.

Invalid Access List (235-1580): The DN access list contained invalid values.
Cause: The distinguished names access list contained invalid values.
Response: Make sure that the distinguished names access list contains valid values that are properly formatted.

Invalid Access List (235-1581): The access list pointer is NULL or is not an access list. Perhaps the variable is uninitialized.
Cause: The access list pointer is NULL or is not an access list. The variable may be uninitialized.
Response: Make sure that the access list pointer is not NULL and is initialized properly.

webMethods Error Message Reference Version 6.5 and 6.5.1 97

CHAPTER 1 webMethods Broker

Invalid Acknowledgement (208-1220): Cannot acknowledge the requested document because the sequence number is out of
order with respect to other unacknowledged documents.
Cause: The requested document cannot be acknowledged because the sequence number is out of order with
other unacknowledged documents.
Response: Acknowledge documents in order with other unacknowledged documents.

Invalid Acknowledgement (208-1221): Cannot acknowledge the requested document because the sequence number
<seqNum> does not correspond to any unacknowledged document.
Cause: The requested document cannot be acknowledged because the sequence number <seqNum> does not
correspond to any unacknowledged document.
Response: Make sure that the specified sequence number corresponds to one of the retrieved but
unacknowledged documents.

Invalid Acknowledgement (208-1222): Duplicate sequence number <seqNum> present in the list.
Cause: The operation could not be completed because a duplicate sequence number <seqNum> is present in
the list.
Response: Make sure that the list does not contain any duplicates.

Invalid Broker Name (236-1590): The Broker name <brokerName> is not valid. Broker names cannot contain unprintable
characters, a colon, '@', '/', or '\' and they cannot start with a '#' symbol. They must be between 1 and 255 ANSI characters or
1 and 42 Unicode characters in length.
Cause: The Broker name <brokerName> is not valid. Broker names cannot contain unprintable characters (":",
"@", "/", or "\" ), and they cannot start with the "#" symbol. They must be between 1 and 255 ANSI characters or
1 and 42 Unicode characters in length.
Response: Make sure that the Broker name is valid and contains only supported characters.

Invalid Client (209-1230): The client pointer is NULL or is not a client. Perhaps the variable is uninitialized or the client has
already been deleted.
Cause: The client pointer is NULL or is not a client. The variable may be uninitialized or the client has already
been deleted.
Response: Make sure that the client pointer is not NULL and is initialized properly.

Invalid Client (209-1231): The client is no longer valid because it has been destroyed by the Broker.
Cause: The client is no longer valid because it has been destroyed by the Broker.
Response: Cannot complete the specified operation because the client is not valid and does not exist on the
Broker.

98 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Invalid Client Group Name (237-1600): The client group name <group> is not valid. Client group names cannot contain
unprintable characters, a colon, '@', '/', or '\' and they cannot start with a '#' symbol. They must be between 1 and 255 ANSI
characters or 1 and 42 Unicode characters in length.
Cause: The client group name <group> is not valid. Client group names cannot contain unprintable characters
(":", "@", "/", or "\"), and they cannot start with the "#" symbol. They must be between 1 and 255 ANSI
characters or 1 and 42 Unicode characters in length.
Response: Make sure that the client group name is valid and contains only supported characters.

Invalid Client ID (210-1240): Could not create or reconnect client. The client id <clientID> is not valid. Client IDs cannot
contain unprintable characters, a colon, '@', '/', or '\\' and they can only begin with '#' when created by the Broker. They must
be between 1 and 255 ANSI characters or 1 and 42 Unicode characters in length.
Cause: A request to create or reconnect to the client failed because the client id contained invalid characters.
Client IDs cannot contain unprintable characters (":", "@", "/", or "\") and they can only begin with the "#"
character when created by the Broker. They must be between 1 and 255 ANSI characters or 1 and 42 Unicode
characters in length.
Response: Make sure that the client name is valid and contains only supported characters.

Invalid ClientQueueLock (271-3772): ClientQueueLock for <clientID> is not held by this client.
Cause: The specified Broker client <clientID> is not locked or does not hold a lock by this client.
Response: Check the target client. Make sure that the target client is locked by the client before issuing the
command.

Invalid ClientQueueLock (271-3777): The specified ClientQueueLock is invalid.

Cause: The specified ClientQueueLock is invalid.
Response: Check the ClientQueueLock parameter. Make sure that the parameter is a valid ClientQueueLock
object and is not NULL.

Invalid ClientQueueLock (271-3781): An error occured while accessing the ClientQueueLock of <clientID>. The
ClientQueueLock is invalid or the volatile target client may have exited.
Cause: The ClientQueueLock of <clientID> may be invalid or the volatile target client may have exited.
Response: Check the ClientQueueLock. Make sure that its parameters correspond to a valid client and that the
client still exists on the Broker.

webMethods Error Message Reference Version 6.5 and 6.5.1 99

CHAPTER 1 webMethods Broker

Invalid Descriptor (211-1250): The descriptor pointer is NULL or is not a descriptor. Perhaps the variable is uninitialized or
the descriptor has already been deleted.
Cause: The descriptor pointer is NULL or is not a descriptor. The variable may be uninitialized or the
descriptor may have already been deleted.
Response: Make sure that the descriptor is not NULL and was initialized properly.

Invalid Document (212-1260): The document pointer is NULL or is not a document. Perhaps the variable is uninitialized or the
document has already been deleted.
Cause: The document pointer is NULL or is not a document. The variable may be uninitialized or the
document may have been already deleted.
Response: Make sure that the document pointer is not NULL and was initialized properly.

Invalid Document (212-1261): The document was not received from the Broker and has no publisher ID.
Cause: The document was not received from the Broker and does not have a publisher ID.
Response: Make sure that the document originated from a valid source, for example a Broker Client or from
another Broker.

Invalid Document (212-1263): Document is not a properly formed document of its type. One or more fields do not match the
document definition in the Broker.
Cause: The document is not in the expected format. One or more fields do not match the document definition
in the Broker.
Response: Make sure that the document is valid and matches the definition on the Broker.

Invalid Document (212-1264): Document is not of the proper binary format for this operation. Perhaps it was generated on a
previous release of the software.
Cause: The document is not of the proper binary format for this operation. It may have been generated on a
previous release of the software.
Response: Use compatible versions of the API libraries and Broker. Refer to webMethods documentation for
more information.

Invalid Document Type Name (213-1270): The document name <docName> contains an invalid character. Only alphanumeric
characters, underscores, and characters above Unicode 009F are allowed in parts of a document type name, and '::' can be
used to separate parts.
Cause: The document name <docName> contains an invalid character. Only alphanumeric characters,
underscores, and characters above Unicode 009F are allowed in parts of a document type name. "::" can be
used to separate parts.
Response: Make sure that the document name is valid and contains only supported characters.

100 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Invalid Document Type Name (213-1271): The document name <docName> contains an illegal character sequence. Names
may contain '::' but not ':' or ':::'
Cause: The document name <docname> contains an illegal character sequence. Names may contain "::" but not
":" or ":::"
Response: Make sure that the document name is valid and properly formatted.

Invalid Document Type Name (213-1272): The document name <docName> contains an invalid character at the start of a
document name. A field name cannot start with a numeric character or an underscore.
Cause: The document name <docName> contains an invalid character at the start of a document name. A field
name cannot start with a numeric character or an underscore.
Response: Make sure that the document name is valid.

Invalid Document Type Name (213-1273): The document name <docName> is invalid. Document names must be between 1
and 255 ANSI characters or 1 and 42 Unicode characters in length.
Cause: The document name <docName> is invalid. Document names must be between 1 and 255 ANSI
characters or 1 and 42 Unicode characters in length.
Response: Check the document name. Make sure the document name contains between 1 and 255 ANSI
characters or 1 and 42 Unicode characters.

Invalid Document Type Name (213-1274): The document name <docName> uses a reserved word.
Cause: The document name <docName> uses a reserved word.
Response: Check the document name. Make sure it does not contain a reserved word.

Invalid Document Type Name (213-1275): The document name <docName> has a part which is less than 1 character in length.
Cause: The document name <docName> contains a part that is of length 0 or 1. Parts must be at least 2
characters long.
Response: Make sure to specify a valid document name.

Invalid Document Type Name (213-1276): The infoset name <eventName> contains an invalid character. Only alphanumeric
characters, underscores, and characters above Unicode 009F are allowed in an infoset name. Colons are not allowed.
Cause: The infoset name <eventName> contains an invalid character. Only alphanumeric characters,
underscores, and characters above Unicode 009F are allowed in an infoset name. A colon is not a valid
character.
Response: Check the infoset name. Make sure it contains only supported characters.

webMethods Error Message Reference Version 6.5 and 6.5.1 101

CHAPTER 1 webMethods Broker

Invalid Field Name (214-1280): The field name <fieldName> contains a sequence index which was not closed with a ']' as
expected.
Cause: The field name <fieldName> contains a sequence index that was not properly closed with a "]".
Response: Check the field name. Make sure it is closed with a "]".

Invalid Field Name (214-1281): The field name <fieldName> contains a sequence index with no numeric value in it at all.
Cause: The field name <fieldName> contains a sequence index that does not contain a numeric value.
Response: Check the field name. Make sure it contains a numeric value.

Invalid Field Name (214-1282): The field name <fieldName> contains an invalid character in the sequence index. The index
must be a numeric value of zero or greater.
Cause: The field name <fieldName> contains an invalid character in the sequence index. The index must be a
numeric value of zero or greater.
Response: Check the field name. Make sure it contains a numeric value of zero or greater.

Invalid Field Name (214-1283): The field name <fieldName> contains an invalid character. Only alphanumeric characters,
underscores, and characters above Unicode 009F are allowed in a field name.
Cause: The field name <fieldName> contains an invalid character. Only alphanumeric characters, underscores,
and characters above Unicode 009F are allowed in an infoset name.
Response: Check the field name. Make sure it contains only alphanumeric characters, underscores, and
characters above Unicode 009F.

Invalid Field Name (214-1284): Must specify a field name. A zero length string was provided.
Cause: A call to set the type definition of a field failed because no field name was specified or a zero length
string was provided.
Response: Check the field name. Make sure it is valid.

Invalid Field Name (214-1285): The field name <fieldName> contains an invalid character at the start of a field name. A field
name cannot start with a numeric character or an underscore.
Cause: The field name <fieldName> contains an invalid character. A field name cannot start with a numeric
character or an underscore.
Response: Check the field name. Make sure it does not begin with a numeric character or an underscore.

102 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Invalid Field Name (214-1286): The field name <fieldName> is invalid. Field names must be between 1 and 255 ANSI
characters or 1 and 42 Unicode characters in length.
Cause: The field name <fieldName> is invalid. Field names must be between 1 and 255 ANSI characters or 1
and 42 Unicode characters in length.
Response: Check the field name. Make sure it contains from 1 to 255 ANSI characters or 1 to 42 Unicode
characters.

Invalid Field Name (214-1287): The field name <fieldName> uses a reserved word.
Cause: The field name <fieldName> uses a reserved word.
Response: Check the field name. Make sure it does not contain a reserved word.

Invalid Field Name (214-1289): The field <fieldName> already exists, so you cannot rename a field to its name.
Cause: The field name <fieldName> already exists.
Response: Choose a field name that does not already exist.

Invalid Filter (215-1300): The filter pointer is NULL or is not a filter. Perhaps the variable is uninitialized or the filter has
already been deleted.
Cause: The filter pointer is NULL or is not a filter. The variable might not be initialized, or the filter may have
been deleted.
Response: Check the filter. Make sure it is valid and properly initialized.

Invalid License (238-1610): The license string specified was not valid.
Cause: The specified license string is not valid.
Response: Make sure the license string is valid.

Invalid Log Config (239-1620): Could not set one or more log configurations. The following configuration names are not
recognized by the Broker: <brokerName>.
Cause: The Broker did not recognize the configuration names specified in <brokerName>.
Response: Check the configuration name. Make sure it is valid and supported by the Broker.

Invalid Log Config (239-1621): The log configuration pointer is NULL or is not a log configuration. Perhaps the variable is
uninitialized.
Cause: The log configuration pointer is NULL or is not a log configuration. The variable might not be
initialized.
Response: Check the log configuration. Make sure it is valid and properly initialized.

webMethods Error Message Reference Version 6.5 and 6.5.1 103

CHAPTER 1 webMethods Broker

Invalid Name (240-1630): Could not create or reconnect client. The application name <appName> is not valid.
Cause: The specified application name is not valid. It may contain one or more non-printable character.
Response: Check the application name. Make sure it contains valid characters.

Invalid Name (240-1631): Could not set log entry. The name <name> is not a valid log entry code. It cannot contain spaces or
unprintable characters.
Cause: The Broker Server Client could not set a log entry. The name <name> is not a valid log entry code. It
contains spaces or unprintable characters.
Response: Verify that the log entry code contains only valid characters.

Invalid Operation (274-1032): Could not complete operation. A request to check or get events already exists.
Cause: A call to check for events request was rejected because this request already exists from the current client
session.
Response: Make sure that the existing check for events request is cancelled before issuing a new request.

Invalid Operation (274-1760): A manual increment of a redelivery count was attempted for a client that has automatic
increments enabled.
Cause: A client application attempted to manually increment the redelivery count when the redelivery count
mode is automatic.
Response: Make sure that the redelivery count mode is set to manual before attempting changes on the
redelivery count.

Invalid Operation (274-3775): Either the queue is empty or the 'from_index' value is out of bounds.
Cause: Either the queue is empty or the "from_index" value is out of bounds.
Response: Make sure that a valid "from_index" is specified.

Invalid Operation (274-3792): The client queue is locked for queue manipulation.
Cause: The Broker Administrative Client cannot complete the requested operation because the client is locked
for queue manipulation.
Response: Reissue the request after the client is unlocked.

Invalid Permission (241-1640): The permissions contained an invalid setting.

Cause: The permissions contained an invalid setting.
Response: Check the permissions to ensure that all of the settings are valid.

104 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Invalid Platform Key (242-1650): Could not set the platform info. The key <key> is not valid.
Cause: The platform information key could not be set on the Broker Client. The key may contain invalid or
restricted characters.
Response: Specify a valid platform information key.

Invalid Port (243-1660): The port <portNum> is not a valid port on the host.
Cause: Port <portNum> is not a valid port on the Broker host.
Response: Specify a valid port number.

Invalid Port (243-1661): The port <portNum> is not a valid port on the host because it contains invalid characters.
Cause: Port <portNum> is not a valid port number because it contains invalid or restricted characters.
Response: Specify a valid port number.

Invalid QM Operation (270-3773): The target client <targetID> is currently locked by client <adminID>, session_id
<sessionID>, and was locked at <lockTime>.
Cause: The Broker Client cannot complete the lock/unlock operation because the target client is currently
locked by another client.
Response: Check the queue lock status for the target client. Make sure that it is not already locked by another
client before issuing a lock or release lock request.

Invalid QM Operation (270-3774): A Pending QM operation exists. Cannot issue a new QM operation.
Cause: A queue manipulation operation for this client is pending. A new queue manipulation operation cannot
be issued until the pending operation has completed.
Response: Wait until the pending operation has completed, then reissue the request.

Invalid QM Operation (270-3775): Either the queue is empty or the 'from_index' value is out of bounds.
Cause: The client cannot complete the queue manipulation operation because the queue is empty or the
"from_index" value is out of range.
Response: Check the from_index value. Make sure that the range specified is valid.

Invalid QM Operation (270-3778): The specified client <clientID> could not be found on the Broker.
Cause: The queue manipulation request could not be completed. The specified client <clientID> could not be
found on the Broker.
Response: Check the Broker for the specified client ID. Make sure that the client ID exists on the Broker.

webMethods Error Message Reference Version 6.5 and 6.5.1 105

CHAPTER 1 webMethods Broker

Invalid QM Operation (270-3779): The specified client <clientID> is already locked by this client.
Cause: The client already holds a lock on this client queue. The lock request cannot be issued.
Response: Make sure that the target client queue is not already locked.

Invalid QM Operation (270-3781): An error occured while accessing the ClientQueueLock of <clientID>. The ClientQueueLock
is invalid or the volatile target client may have exited.
Cause: The ClientQueueLock of <clientID> may be invalid or the volatile target client may have exited.
Response: Check the ClientQueueLock. Make sure that its parameters correspond to a valid client and the
client still exists on the Broker.

Invalid QM Operation (270-3782): Duplicate entries found in the list for <clientID>.
Cause: The client ID <clientID> is listed more than once in the passed client ID list.
Response: Check the list. Remove any duplicate entries and then reissue the request.

Invalid sequence number (277-1770): Cannot increment the redelivery count of the requested document because the sequ
ence number <seqn> does not correspond to any unacknowledged document.
Cause: A client attempted to increment redelivery count on an event with an invalid receipt sequence number.
Response: Make sure that the event is valid and returned from a Broker before attempting changes on the
redelivery count.

Invalid sequence number (277-1771): Cannot negatively acknowledge requested document because the sequence number or
numbers do not correspond to any unacknowledged document.
Cause: A client attempted to negatively acknowledge an event that was not returned from the Broker or the
document was already acknowledged
Response: Make sure that the event is valid and not yet acknowledged on the Broker before attempting a
negative acknowledgement.

Invalid sequence number (277-1772): Cannot negatively acknowledge requested document because a duplicate sequence
number or numbers was provided.
Cause: A client specified an array of sequence numbers to be negatively acknowledged and the array contained
a duplicate sequence number.
Response: Make sure that there are no duplicate sequence numbers in the input sequence numbers array.

106 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Invalid state (278-1780): Cannot increment redelivery counts for a client that does not have redelivery counting enabled.
Cause: A client attempted to update the redelivery count when this feature was not enabled on the Broker.
Response: Make sure that the redelivery count mode is enabled before attempting changes on the redelivery
count.

Invalid Subscription (216-1310): The filter <filter> contains a parse error.

Cause: The specified filter contains a parse error.
Response: Check the filter string. Make sure that it is valid.

Invalid Subscription (216-1311): The subscription is invalid. Perhaps the event_type_name is NULL.
Cause: The subscription is invalid. The event_type_name might be NULL.
Response: Check the event_type_name. Make sure that it corresponds to a valid event type on the Broker and is
not NULL.

Invalid Subscription (216-1313): Cannot cancel the requested subscription because it does not exist.
Cause: The subscription does not exist on the Broker.
Response: Check the subscriptions on the Broker. Make sure that the specified subscriptions are valid and exist
on the Broker.

Invalid Subscription (216-1314): Failed to cancel <count> subscriptions because they do not exist.
Cause: The <count> subscriptions do not exist on the Broker.
Response: Check the subscriptions on the Broker. Make sure that the specified subscriptions are valid and exist
on the Broker.

Invalid Subscription (216-1315): The subscription is invalid. The character at position <charPosition> in the filter is not valid
inside a hint.
Cause: The subscription is invalid. The character at position <charPosition> in the filter is not valid inside a
hint.
Response: Check the syntax of the hint. Be sure to follow the syntax for creating subscriptions.

Invalid Subscription (216-1316): The subscription is invalid. The subscription hint <hintValue> is not valid.
Cause: The subscription is invalid. The subscription hint <hintValue> is not valid.
Response: Verify that the hint value specified is valid.

webMethods Error Message Reference Version 6.5 and 6.5.1 107

CHAPTER 1 webMethods Broker

Invalid Subscription (216-1317): The subscription is invalid. The hint at position <charPosition> is missing its value.
Cause: The subscription is invalid. The hint at position <charPosition> is missing its value.
Response: Check the syntax of the hint. Verify that the correct syntax is used for creating subscriptions.

Invalid Subscription (216-1318): The subscription is invalid. The subscription hint value <hintValue> is not valid for the hint
at position <charPosition>.
Cause: The subscription is invalid. The subscription hint value <hintValue> is not valid for the hint at position
<charPosition>.
Response: Check the syntax of the hint. Verify that the correct syntax is used for creating subscriptions.

Invalid Subscription (216-1319): The subscription is invalid. The hint at position <charPosition> is missing its closing brace.
Cause: The subscription is invalid. The hint at position <charPosition> is missing its closing brace.
Response: Check the syntax of the hint. Verify that the correct syntax is used for creating subscriptions.

Invalid Subscription (216-2310): The subscription is invalid. The hint at position <charPostion> is missing its 'hint:' prefix.
Cause: The subscription is invalid. The hint at position <charPosition> is missing its "hint" prefix.
Response: Check the syntax of the hint. Verify that the correct syntax is used for creating subscriptions.

Invalid Subscription (216-2311): The subscription is invalid. The hint at position <charPosition> is missing a comma
delimeter.
Cause: The subscription is invalid. The hint at position <charPosition> is missing a comma delimiter.
Response: Check the syntax of the hint. Verify that the correct syntax is used for creating subscriptions.

Invalid Subscription (216-9999): Error cause unknown.

Cause: The cause for this error is unknown.
Response: Make sure that the subscriptions are valid. For further assistance contact webMethods Technical
Services.

Invalid Territory Name (244-1670): The territory name <territoryName> is not valid. Territory names cannot contain
unprintable characters, a colon, '@', '/', or '\' and they cannot start with a '#' symbol. They must be between 1 and 255 ANSI
characters or 1 and 42 Unicode characters in length.
Cause: The specified territory name contains invalid or unsupported characters.
Response: Verify that the specified territory name is valid and follows the rules outlined in the API
documentation.

108 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Invalid Transaction Id (272-1490): Document type <docType> is not defined in the Broker.
Cause: A client application tried to publish or deliver a document, but the document type does not exist on the
Broker.
Response: Make sure that the document type exists and that correct permissions are set in the client group.

Invalid Transaction Id (272-3790): There is no open transaction with the specified transaction id.
Cause: A client application tried to perform a prepare, commit, or abort operation on a transactional client that
is not open or prepared. Or, the Broker could not find the transaction context that corresponds to the
transaction ID on the Broker.
Response: Make sure that the transactional client is in an appropriate state before issuing calls to prepare,
commit or abort transactions.

Invalid Transaction Id (272-3791): The transaction with the specified transaction is closed.
Cause: A client attempted to perform an action on a Broker Client transaction that has been committed or
aborted.
Response: Make sure that the transaction is still active while preparing, committing or aborting a transaction.

Invalid Transaction Id (272-3793): There is a client mismatch in the current transaction.

Cause: A client attempted to perform a transactional operation on a Broker Client that was initialized by
another client.
Response: Make sure that transactional operations are issued from the Broker Clients that originally created the
transaction.

Invalid Transaction Id (272-3794): The current transaction is already open.

Cause: The client tried to open a transaction but could not because a transaction was already open. The client
will not be able open another transaction until the old one is committed or aborted.
Response: Let the open transaction complete before opening a new transaction.

Invalid Transactional Client (276-3795): The transactional client pointer is NULL or is not a client. Perhaps the variable is
uninitialized or the transactional client has already been deleted.
Cause: The transactional client pointer is NULL or is not a client. The variable is uninitialized or the
transactional client has already been deleted.
Response: Make sure that the parameter is a valid client object and is not NULL.

webMethods Error Message Reference Version 6.5 and 6.5.1 109

CHAPTER 1 webMethods Broker

Invalid Type (217-1320): Only document and struct types can be loaded into the cache.
Cause: The client application tried to load a document into the cache, but the document did not have the
correct type definition. The type definition must be document or struct.
Response: Make sure that the specified type definition is either a struct or document.

Invalid Type (217-1321): Cannot get a field of type sequence using a basic get function. Use a sequence get function.
Cause: The client application attempted to use a basic get function to get a sequence type field, but only a
sequence get function can be used for this purpose.
Response: Use a sequence get function to get sequence fields from a BrokerEvent.

Invalid Type (217-1322): Cannot get a field of type sequence of sequence.

Cause: The client application attempted to get a "sequence of sequence" field as a simple sequence field type,
which is not permitted.
Response: Use a sequence get function to get "sequence of sequence" fields from a BrokerEvent.

Invalid Type (217-1323): Cannot set a field of type sequence using a basic set function. Use a sequence set function.
Cause: The client application tried to use a basic set function to assign a value to a sequence type field, but only
a sequence set function can be used for this purpose.
Response: Use the correct function for the field type. If you want to assign a value to a non-sequence field, use
a basic set function. If you want to set a assign a value to a sequence field, use a sequence set function.

Invalid Type (217-1324): Cannot set a field of type sequence of sequence.

Cause: A client application tried to assign a value to a "sequence of sequence" field. A "sequence of sequence" is
equivalent to an "array of arrays" or multi-dimensional array. You cannot assign a value to a "sequence of
sequence" field using basic sequence set functions.
Response: Use the correct function for the field type. If you want to assign a value to a basic sequence field, use
a basic sequence set function. If you want to assign a value to a "sequence of sequence" field, use set sequence
functions of appropriate type on individual members of the base sequence. Refer to Broker API documentation
for more information.

Invalid Type (217-1325): Cannot set a field to type sequence using the type setting functions.
Cause: The client application tried to use a basic set function (basic set <Field> API) to change a sequence type
field to another type, but you must use setSeq<Type>Field API to do this.
Response: Use the setSeq<Type>Field API instead.

110 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Invalid Type (217-1326): The document contains data of an unsupported type.

Cause: The event contains data of an unsupported type.
Response: Verify that the event is valid and contains supported data types.

Invalid Type (217-1327): The filter encountered an unsupported data type. The field type is <type>. Perhaps a structure or
sequence field is being used where it should not be.
Cause: The filter encountered an unsupported data type. The field type is <type>. Perhaps a structure or
sequence field is being used where it should not be.
Response: Verify that a filter has not been set on an unsupported data type. Filters are not supported on
structure and sequence fields.

Invalid Type (217-1328): The formatter encountered an unsupported data type. The field type is <type>. Perhaps a structure
or sequence field is being used where it should not be.
Cause: One of the internal helper functions encountered an unsupported data type. The field type is <type>.
Perhaps a structure or sequence field is being used where it should not be.
Response: Verify the event is valid and contains supported data types.

Invalid Type (217-1329): An unsupported type was specified.

Cause: The Broker Client could not complete the requested operation because the specified field type is
unknown or unsupported in the Broker Event.
Response: Verify that the specified type is supported.

Invalid Type (217-1330): Cannot get field names from an unstructured field.
Cause: A client application cannot get field names from an unstructured field.
Response: To get field names, verify that the field specified by the "field_name" parameter is of type "struct" or
"BrokerEvent".

Invalid Type (217-1331): The type definition code contains an unsupported type.
Cause: The type definition code contains an unsupported type.
Response: Verify that the type code is valid.

Invalid Type (217-1332): The type definition contains data of an unsupported type.
Cause: The type definition contains data of an unsupported type.
Response: Verify the type definition is valid and contains supported types.

webMethods Error Message Reference Version 6.5 and 6.5.1 111

CHAPTER 1 webMethods Broker

Invalid Type (217-2300): Only struct and document types are valid for this operation.
Cause: A client application tried to perform an operation on a field that is not of type "struct" or "document",
but the requested operation can only work on those types of fields.
Response: Specify a struct or BrokerEvent field name when creating a new document type, ordering the fields
in a document type, or changing the name of a document.

Invalid Type (217-2301): Only document types are valid for this operation.
Cause: A client application tried to perform an operation that is supported only on a Broker Event. Only fields
of type "Event" are supported for this type of operation.
Response: Make sure that a typedef of "document" is specified when performing these operations.

Invalid Type (217-2302): Cannot rename the contents of sequence field, such as 'x[]', where the last part of the field name is a
set of sequence brackets.
Cause: The client application tried to rename the contents of a sequence field, such as "x[]", where the last part
of the field name is a set of sequence brackets. You cannot rename the contents of a sequence field.
Response: Make sure that the rename request is not issued on the contents of a sequence field.

Invalid Type (217-2303): Cannot rename a field to become the contents of a sequence field, such as 'x[]', where the last part of
the field name is a set of sequence brackets.
Cause: The client application tried to rename a field to become the contents of a sequence field, such as "x[]",
where the last part of the field name is a set of sequence brackets. You cannot perform a rename to convert a
non-sequence field to a sequence field.
Response: Make sure that the rename request is not issued to convert a non-sequence field to a sequence field.

Invalid Type Cache (218-1340): The type cache pointer is NULL or is not a type cache. Perhaps the variable is uninitialized or
the client has been disconnected.
Cause: The type cache pointer is NULL or is not a type cache. Possible causes are that the variable is
uninitialized or the client has been disconnected.
Response: Verify that the passed parameter of type "TypeDefCache" is valid, properly initialized, and not
NULL.

Invalid Type Definition (219-1351): The document was not created with a client and therefore has no type definition.
Cause: A client application tried to get the type definition from the document, but could not because the
document was not created with a Broker Client and does not have a type definition.
Response: Recreate the document as a typed document and associate it with a Broker Client.

112 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Invalid Type Definition (219-1352): The typedef pointer is NULL or is not a typedef. Perhaps the variable is uninitialized, the
client has been disconnected, or the type cache has been otherwise flushed.
Cause: The TypeDef pointer is NULL or is not a TypeDef. Either the variable is uninitialized, the client has been
disconnected, or the type cache has been purged.
Response: Specify valid typedef data for this operation.

Invalid Type Definition (219-1353): Type definition top-level entry was not named.
Cause: A type definition top-level entry was not named.
Response: Specify a top level type name when creating new type definitions.

Invalid Type Definition (219-1354): Cannot look up definition for an unnamed type.
Cause: The Broker cannot look up a definition for an unnamed type.
Response: Specify a valid type name for the look up operation.

Invalid Type Definition (219-1355): The admin typedef pointer is NULL or is not an admin typedef. Perhaps the variable is
uninitialized.
Cause: The AdminTypeDef pointer is NULL or is not an AdminTypeDef. The variable may be uninitialized.
Response: Specify valid typedef data for this operation.

Invalid Type Definition (219-1356): The type <typeName> is not in the type cache.
Cause: The specified type is not found in the cache.
Response: Make sure that the type exists on the Broker.

Invalid Type Definition (219-1357): The document type <typeName> cannot be synchronized with the other territory because it
does not exist in the other territory.
Cause: The Broker could not synchronize one of its document types (<typeName>) with the document type in
another territory because the document type does not exist in the other territory.
Response: Make sure that the document type is present on both territories before synchronizing them.

Invalid Type Definition (219-1358): The document type <typeName> cannot be synchronized with the other territory because
the document type's definition contains different fields.
Cause: The Broker could not synchronize one of its document types (<typeName>) with the document type in
another territory because the definitions in the two territories are not the same.
Response: Verify that the type definition of document types present on both territories are the same.

webMethods Error Message Reference Version 6.5 and 6.5.1 113

CHAPTER 1 webMethods Broker

Invalid Type Definition (219-1359): The document type <typeName> cannot be sychronized with the other territory because
the document type's storage type is different.
Cause: The Broker could not synchronize one of its document types (<typeName>) with the document type in
another territory because the document type's storage types are different in the two territories.
Response: Verify the document type's storage types are identical before synchronizing.

Invalid Type Definition (219-2350): The document type <typeName> cannot be sychronized with the other territory because
the document type's time-to-live is different.
Cause: The Broker could not synchronize one of its document types (<typeName>) with the document type in
another territory because the document type's time-to-live is not the same in the two territories.
Response: Verify that the time-to- live values of document types present on both territories are the same.

Invalid Type Definition (219-2351): The document type <typeName> cannot be sychronized with the other territory because
the document type's description is different.
Cause: The Broker could not synchronize one of its document types (<typeName>) with the document type in
another territory because the document types in the two territories are not the same.
Response: Verify that the description values of document types present on both territories are the same.

Invalid Type Definition (219-2352): The document type <typeName> cannot be sychronized with the other territory because
the document type's infosets are different.
Cause: The Broker could not synchronize one of its document types (<typeName>) with the document type in
another territory because the document type's infosets are not the same in the two territories.
Response: Verify the document type's infosets are identical before synchronizing.

Invalid Type Definition (219-2353): The document type <typeName> cannot be stored in the Broker because its type definition
is not valid.
Cause: Client Application tried to store a document on the Broker, but the document's type <typeName> does
not have valid type definition.
Response: Make sure that the type code specified is valid. Refer to webMethods Broker Administrative API
documentation for further assistance on creating document types.

Invalid Type Definition (219-2356): The document type <typeName> cannot be synchronized with the other territory because
the document type's validation is different.
Cause: The Broker could not synchronize one of its document types (<typeName>) with the document type in
another territory because the document type's validation is not the same in the two territories.
Response: Verify that the document type <typeName> validation is present on both territories before
synchronizing.

114 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

No Memory (108-1360): Growing the document body is not permitted for this document.
Cause: The BrokerEvent tried to grow the document body, but this action is not permitted for this document.
Response: The BrokerEvent is restricted from allowing the body to grow. If needed, use the
awEventFromBinString() or awEventFromBinData() calls to construct the document.

No Memory (108-1361): Memory could not be allocated to complete the operation. <size> bytes were requested.
Cause: Memory could not be allocated to complete the operation. <size> bytes were requested.
Response: Free up more CPU memory by stopping other applications, then retry the operation.

No Memory (108-1362): Memory could not be allocated to complete the operation.

Cause: Memory could not be allocated to complete the operation.
Response: Free up more memory by stopping other applications, then retry the operation.

No Permission (109-1015): The operation failed because the Broker's license has expired. Alert your administrator.
Cause: The requested operation failed because the Broker's license has expired
Response: Obtain a new Broker license.

No Permission (109-1370): Cannot create or reconnect to client on Broker <brokerName> on host <hostName>:<portNum>.
Permission is denied.
Cause: A client application was denied permission to create or reconnect to the client on Broker <brokerName>
on host <hostName>:<portNum>.
Response: Verify that the ACL is set up correctly and the access label adapter is running.

No Permission (109-1371): Cannot create or reconnect to client on the default Broker on host <hostName>:<portNum>.
Permission is denied.
Cause: A request to create or reconnect to a client on the default Broker on host <hostName>:<portNum> was
denied because no default Broker exists on the broker server.
Response: Make sure that a default broker exists on the broker server.

No Permission (109-1372): Cannot deliver the document. Permission is denied. Check the 'can publish' permissions in the
client's client group.
Cause: The Broker client tried to deliver a document but was unable to because the client does not have the
correct permissions.
Response: Check the "can publish" permissions in the client's client group. Make sure that the client's client
group has the appropriate publish permission set.

webMethods Error Message Reference Version 6.5 and 6.5.1 115

CHAPTER 1 webMethods Broker

No Permission (109-1373): Cannot access information about document type <docType>. Must have either 'can publish' or
'can subscribe' permission in the client's client group.
Cause: The Broker client cannot access information about the document type <docType>. The Broker client
must have either "can publish" or "can subscribe" permissions set in the client's client group.
Response: Check the permissions in the client's client group. Make sure that the current client's client group has
either publish or subscribe permission on the document type <docType>.

No Permission (109-1374): Cannot publish the document. Permission is denied. Check the 'can publish' permissions in the
client's client group.
Cause: The Broker Client could not publish the document because the client does not have the required publish
permissions.
Response: Make sure that the client's client group has the appropriate publish permission set.

No Permission (109-1375): The field <fieldName> is read only.

Cause: A client application tried to set the fieldname <fieldName>, but this field is read only and cannot be set
or modified.
Response: Verify that the fieldName is user-settable before setting or modifying it.

No Permission (109-1376): Cannot set the state share limit on an unshared client.
Cause: A client application was unable to set the share state limit because the Broker Client used is not enabled
for state sharing.
Response: Enable state sharing on the client and then set the state share limit.

No Permission (109-1377): Cannot subscribe to document type <docType>. Permission is denied. Check the 'can subscribe'
permissions in the client's client group.
Cause: The Broker Client tried to subscribe to a document of the specified type, but was unable to because the
client does not have the required permissions.
Response: Check the client's client group subscribe permissions. Make sure that the appropriate subscribe
permissions are set.

No Permission (109-1378): Client connection failed because this client requires an additional license.
Cause: The client connection failed because the Broker's current license does not support SSL connections.
Response: Check the Broker's license. Make sure that it is valid and supports SSL.

116 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

No Permission (109-1379): Operation failed. Permission denied.

Cause: The requested operation failed because the client does not have administrative permissions.
Response: Make sure that the client issuing the request has appropriate permissions to complete the operation.

No Permission (109-1380): Cannot change the value of platform key <key>.

Cause: The Broker denied a request to edit the platform key because the key is not user-settable
Response: Make sure that the keys are user-definable. Refer to the Broker API documentation for further
assistance.

No Permission (109-1381): The password to certificate file <certFile> is incorrect, or the file is a certificate file at a higher level
of security than is supported.
Cause: A client application was unable to complete because the password to certificate file <certFile> is
incorrect or the file is a certificate file at a higher level of security than is supported.
Response: Make sure that the correct password is specified and the certificate file has a either domestic or
export security level.

No Permission (109-1382): Operation failed because permission is denied. This operation requires administrative
permissions.
Cause: A client application tried to perform an operation, but the operation could not complete because the
Broker Client did not have administrative permissions.
Response: Use an administrative client to complete the operation.

No Permission (109-1383): Cannot create a host client connection to host <hostName>. Permission is denied.
Cause: The Broker Monitor Client could not connect to the Broker Monitor on the specified host because it does
not have the required permission.
Response: Make sure the Broker monitor is running and the license is valid.

No Permission (109-1384): The certificate file <certFile> was found, but it cannot be read. Permission is denied.
Cause: A client application tried to execute an SSL related operation, but could not because it could not read
the certificate file specified in the function call. A possible cause is that the client application does not have
read permission to the file.
Response: Check the read permissions for the certificate file. Make sure that the appropriate read permissions
are set.

webMethods Error Message Reference Version 6.5 and 6.5.1 117

CHAPTER 1 webMethods Broker

No Permission (109-1385): This operation cannot be completed because it is attempting to modify or delete a system-defined
value.
Cause: An operation tried to modify or delete a system-defined value, but this is not allowed.
Response: Make sure that the system defined client groups and event types are not modified or deleted.

No Permission (109-1386): Operation failed. The Broker is not licensed for Broker interconnection.
Cause: The Broker cannot complete the multi-Broker operation because the Broker is not licensed for
interconnection.
Response: Obtain a new multi-broker Broker license.

No Permission (109-1387): Cannot publish or deliver the document. Permission is denied. The document can only be
published by the Broker.
Cause: The Broker Client could not publish or deliver the document because the client does not have the
required publish permissions. Only the Broker can publish the document.
Response: Check the publish permissions in the client's client group. Make sure that the client group does not
specify documents that are only publishable by the Broker.

No Permission (109-1388): The client has no access label because the client does not have an owner.
Cause: Client application tried to do get/set access label an but could not because the client does not have an
owner and as a result does not have an access label.
Response: Verify that the client has an owner. If the client does not have an owner then it cannot have an access
label.

No Permission (109-1389): The file <certFile> is either not a certificate file, or the file was built using more powerful
encryption than this version of the library is using.
Cause: The certificate file provided might not be a certificate file, or the file was created with a stronger level of
encryption than is used in this library.
Response: Check the certificate file. Make sure that it is valid and that it uses the same level of encryption as the
libraries.

No Permission (109-2370): Cannot connect to the specified client group because that client group requires an encryption
level higher than you are using.
Cause: The specified client group's encryption level does not match the issuing client's. The specified client
group requires a higher level of encryption than the one specified.
Response: Check the encryption levels. Make sure the encryption levels match.

118 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

No Permission (109-2371): Cannot publish or deliver a document with a control label value that exceeds your client's access
label.
Cause: The client cannot publish or deliver a document. The document's control label value may exceed the
client's access label.
Response: Check the control label value for the document. Make sure that the correct value is specified.

No Permission (109-2372): An access label cannot be required on the accessLabelAdapter client group.
Cause: A client application tried to set EnforcedAccessLabel on an ALA client group, but this is not allowed
because it may cause connection issues on the ALA client group.
Response: Verify the accessLabelAdapter client group's settings have not been modified.

No Permission (109-3783): Cannot insert one or more documents. Permission is denied. Check the 'can subscribe'
permissions in the target client's client group.
Cause: A client application tried to insert one or more documents into the target client queue, but could not
because the Broker Client did not have the required permissions.
Response: Check the permission settings for the target client of the insert operation. Make sure that it has the
appropriate subscribe permissions.

Not Implemented (110-1390): The requested operation is not implemented in this release.
Cause: The client application requested an operation that is not available in this release.
Response: Upgrade to a newer version of webMethods Broker where this feature is supported.

Not Implemented (110-1391): Threaded callbacks is only implemented in threaded libraries.

Cause: A client application tried to perform a threaded callback, but it is not using a threaded library of the
Broker API.
Response: Use non-threaded mechanisms to retrieve events.

Not In Territory (245-1680): Could not complete the operation. The Broker is not a member of a territory.
Cause: The requested territory operation could not complete because the Broker does not belong to a territory.
Response: Make sure that the current Broker is a member of a territory before attempting this territory
operation.

Not In Territory (245-1681): Territory join failed. The remote Broker is not a member of a territory.
Cause: The territory join request failed because the remote Broker is not a member of a territory.
Response: Retry the territory join operation after making the remote Broker a member of a territory.

webMethods Error Message Reference Version 6.5 and 6.5.1 119

CHAPTER 1 webMethods Broker

Null Parameter (220-1400): The input parameter <parameters> is NULL.

Cause: The input parameter <parameter> was null, but this operation requires input.
Response: Make sure that the input parameters are allocated and initialized properly.

Null Parameter (220-1401): The output parameter <parameter> is NULL.

Cause: The output parameter <parameter> is NULL. This parameter should not be NULL; it is supposed to
hold the data that is returned from the operation.
Response: Check the output parameters. Make sure that the expected output parameters are not NULL.

Out of Range (221-1250): The descriptor pointer is NULL or is not a descriptor. Perhaps the variable is uninitialized or the
descriptor has already been deleted.
Cause: A request to create a client failed because the specified descriptor parameter is NULL or is not a valid
descriptor. The variable may be uninitialized or the descriptor may have already been deleted.
Response: Check the pointer value. Make sure that it initialized properly and is not NULL.

Out of Range (221-1410): Cannot set client share limit to a value of zero or less than -1.
Cause: The Broker client denied a request to set the shared state limit to zero or a negative value.
Response: Specify a positive value as the shared state limit.

Out of Range (221-1411): Date cannot be represented in a C time structure because C time only supports dates from Jan 1,
1970 to Jan 19, 2038.
Cause: The date specified by the BrokerDate cannot be represented in a C time structure. C time structure
cannot handle dates prior to January 1, 1970 or after 03:14:07 on January 19, 2038.
Response: Make sure that the date represented by the BrokerDate is in the date range of January 1, 1970 or after
03:14:07 on January 19, 2038.

Out of Range (221-1412): The value of 'flag' is not a legal value.

Cause: The Broker encountered a serious internal error.
Response: Contact webMethods Technical Services.

Out of Range (221-1413): The value of 'max_n' must not be less than -1.
Cause: The specified "max_n" value is less than -1. A valid range is -1 to any +ve number.
Response: Specify a valid value for "max_n" ( >= -1).

120 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Out of Range (221-1414): The value of 'msecs' must not be less than -1.
Cause: The specified "msecs" value for timeout is less than -1. A valid range is -1 to any +ve number.
Response: Specify a valid value for "msecs" ( >= -1).

Out of Range (221-1415): Cannot use a sequence number less than zero.
Cause: The specified sequence number is -ve. It cannot be less than 0.
Response: Specify a valid sequence number (>= 0).

Out of Range (221-1416): Cannot set a sequence size to a value less than zero.
Cause: The specified sequence size is -ve. It cannot be less than 0.
Response: Specify a valid sequence size (>= 0).

Out of Range (221-1417): The value of 'nc' must not be less than -1.
Cause: The specified input parameter "nc" contains an invalid value. It should not be < -1.
Response: Specify a valid value for "n".

Out of Range (221-1418): The value of 'n' must not be less than 0.
Cause: The specified input parameter "n" contains an invalid value. It should not be < 0.
Response: Specify a valid value for "n".

Out of Range (221-1419): A sequence index in field name <field_name> is out of bounds.
Cause: The specified sequence index on a sequence field name is out of bounds (either < 0 or > the actual length
of the sequence)
Response: Check the index in the field name. Make sure that it is within the bounds of the actual sequence
length.

Out of Range (221-1420): Offset must be between 0 and the actual length of the sequence.
Cause: The specified offset range is invalid. It should be between 0 and the actual length of the sequence.
Response: Check the offset range. Make sure that it is valid.

Out of Range (221-1421): Offset must be between 0 and the actual length of the string.
Cause: The specified range for the substring is invalid for a setStringField operation. The value must be >= 0
and < length(string).
Response: Specify a valid range for the substring.

webMethods Error Message Reference Version 6.5 and 6.5.1 121

CHAPTER 1 webMethods Broker

Out of Range (221-1422): Subscription IDs cannot be less than 0.

Cause: A client tried to pass a negative number in as the subscription ID.
Response: Specify a positive value for the sub ID.

Out of Range (221-1423): Cannot use a sequence number less than -1.
Cause: A client tried to pass a negative number as the sequence number of an acknowledge operation.
Response: Specify a positive value for sequence number.

Out of Range (221-1424): Not enough memory space in the buffer was provided for the copy.
Cause: The target buffer does not have sufficient space to complete the copy operation.
Response: Make sure that sufficient memory is allocated for the buffer.

Out of Range (221-1425): Time to live cannot be a negative number.

Cause: The time to live value cannot be negative.
Response: Specify a positive value for time to live.

Out of Range (221-1426): The storage type specified is not a valid value.
Cause: The specified value for storage type is not valid.
Response: Specify a valid storage type while creating client groups and event types, for example,
AW_STORAGE_VOLATILE and AW_STORAGE_GUARANTEED.

Out of Range (221-1427): The lifecycle specified is not a valid value.

Cause: During a request to create a client, an invalid lifecycle was encountered. It should be within the range of
the AW_LIFECYCLE_MIN and AW_LIFECYCLE_MAX values.
Response: Specify a valid lifecycle value.

Out of Range (221-1428): The lifecycle and storage type values specified is not a valid combination of values.
Cause: An attempt to create a client group failed because a storage type of Volatile or Guaranteed was not
specified.
Response: Specify either Volatile or Guaranteed as the storage type while creating client groups.

Out of Range (221-1429): The input parameter <fieldName> is less than zero.
Cause: A negative value was passed to the specified input parameter. This is not a valid value.
Response: Refer to the API documentation to for a list of expected parameter values.

122 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Out of Range (221-2421): Index for insert must be between 0 and size for new fields.
Cause: The specified index for the insert field operation is out of range. It should be between 0 and the number
of fields.
Response: Specify a valid index for the insert operation.

Out of Range (221-2422): The specified log output value is not in the log configuration.
Cause: The specified log topic value is invalid. It should be one of the following.:
AW_LOG_OUTPUT_UNIX_SYSLOG or AW_LOG_OUTPUT_NT_EVENT_LOG or
AW_LOG_OUTPUT_SNMP_TRAP.
Response: Specify a valid topic value.

Out of Range (221-2423): The specified log topic value is not in the log configuration.
Cause: The specified log topic value is invalid. It should be one of the following: AW_LOG_TOPIC_ALERT or
AW_LOG_TOPIC_WARNING or AW_LOG_TOPIC_INFO.
Response: Specify a valid topic value.

Out of Range (221-2424): Cannot create client. The specified client group must have explicit destroy life cycle.
Cause: An attempt to create a Broker client failed because the client group does not have an explicit destroy life
cycle.
Response: Specify a client group that has an explicit destroy life cycle for clients that require redelivery count
feature.

Out of Range (221-2425): An invalid encryption level was specified.

Cause: The specified encryption level is invalid. It should be within the range of the AW_ENCRYPT_MIN and
AW_ENCRYPT_MAX values.
Response: Specify a valid encryption level while setting up security for the client group, territory etc.

Out of Range (221-2426): Cannot join this Broker to the territory because the territory already has a Broker with the same
name as this Broker.
Cause: A request to join a Broker to a territory failed because a Broker with the same name already exists in the
territory. Each Broker in a territory must have a unique name.
Response: Make sure that the Broker has a unique name before joining the territory.

webMethods Error Message Reference Version 6.5 and 6.5.1 123

CHAPTER 1 webMethods Broker

Out of Range (221-2427): Cannot create the gateway because a gateway already exists to the specified territory.
Cause: A request to create a gateway failed because a gateway already exists between the specified territories.
Response: Make sure that a gateway does not already exist between the two territories before issuing a create
request. Only one gateway is allowed between two territories.

Out of Range (221-2428): Cannot create a gateway to the current territory or to a territory with the same name as the current
territory.
Cause: A client application tried to create a gateway specifying two territories with the same name.
Response: Specify two different territories to create the gateway.

Out of Range (221-2429): The document type <type_name> cannot be sychronized with the other territory because it is a
local-only document type.
Cause: The Broker could not synchronize the document type with the territory because the document is a local-
only document (for example, a system defined document type).
Response: Check the gateway permissions. Make sure that the permissions do not include any local-only
document types.

Out of Range (221-3423): An invalid transaction mode was specified.

Cause: During a call to end a transaction, an invalid transaction mode was encountered. It should be within the
range of the AW_TRANSACTION_MODE_MIN and AW_TRANSACTION_MODE_MAX values.
Response: Specify a valid transaction mode value.

Out of Range (221-3424): Destination offset must be between -1 and the actual length of the sequence.
Cause: The destination offset, which is used while packing a sequence in a BrokerEvent, is invalid. It should be
between -1 and the actual length of the sequence.
Response: Make sure that the offset range is valid.

Out of Range (221-3427): Cannot remove the current Broker from the territory with this operation.
Cause: The Broker tried to remove itself from the Territory.
Response: Issue the remove request from a different Broker.

Out of Range (221-3428): The value of 'n' must not be less than -1.
Cause: The specified input parameter "n" contains an invalid value. It should not be < -1.
Response: Specify a valid value for "n".

124 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Out of Range (221-3429): The shared document ordering value in the client's descriptor is not a valid value for this Broker.
Cause: The specified value for shared document ordering is invalid.
Response: Specify a valid shared document ordering value in the client creation calls, for example, "None" or
"Publisher".

Out of Range (221-3430): The shared document ordering value must not contain spaces or unprintable characters.
Cause: The ordering value for the specified document contains spaces or unprintable characters.
Response: Specify a valid value for the document ordering specification.

Out of Range (221-3431): An invalid authentication type was specified.

Cause: While setting up territory/gateway security, the client application specified an invalid authentication
type. It should be within the range of the AW_AUTH_TYPE_MIN and AW_AUTH_TYPE_MAX values.
Response: Specify a valid authentication type while setting up security.

Out of Range (221-3432): An access control list for a gateway cannot consist or more than one user name or more than one
authenticator name.
Cause: An attempt was made to specify more than one user name or authenticator name in the ACL list for a
gateway.
Response: Specify only one user name and authenticator name in the access control list.

Out of Range (221-3433): A shared document type for a gateway does not have accept_subscribe set to true, but has a non-
empty filter set.
Cause: A request to set up shared event types on a gateway failed because the Broker does not permit
subscriptions with filters to be forwarded.
Response: Check the parameters set in the "BrokerSharedEventTypeInfo" structure. Without setting the
"accept_subscribe" flag, you cannot set subscriptions on the gateway.

Out of Range (221-3436): The validation type specified is not a valid value.
Cause: An unsupported validation type was specified.
Response: Use a validation type that is within the supported validation type range.

Out of Range (221-3775): Either the queue is empty or the 'from_index' value is out of bounds.
Cause: The specified "from_index" value is out of range because it is either negative or represents an invalid
logical queue position (probably greater than the current queue length).
Response: Specify a logical queue position for the queue index. Enter 0 or a positive value. A negative position
is not an accepted queue index.

webMethods Error Message Reference Version 6.5 and 6.5.1 125

CHAPTER 1 webMethods Broker

Out of Range (221-3776): The specified value for 'max_events' is out of range.
Cause: The specified "max_events" value is less than 1. The valid range is 1 to any +ve number.
Response: Specify a valid value for "max_events" (>= 1).

Protocol Error (111-1430): Client creation failed due to missing platform information.
Cause: The client could not be created because information on the client platform is missing.
Response: Contact webMethods Technical Services.

Protocol Error (111-1431): The operation failed due to missing arguments in the protocol.
Cause: Missing arguments in the protocol request caused the operation to fail. A communication problem
could have caused the protocol commands to fragment.
Response: Contact webMethods Technical Services.

Protocol Error (111-1433): A protocol failure occurred.

Cause: An unknown error in the protocol request caused the operation to fail.
Response: Contact webMethods Technical Services.

Protocol Error (111-1434): The operation failed due to an unknown command or incorrect arguments in the protocol.
Cause: An unknown command or incorrect arguments in the protocol caused the operation to fail. A
communication problem could have caused the protocol commands to fragment.
Response: Contact webMethods Technical Services.

Security Error (114-1435): The specified certificate is not valid. It has expired.
Cause: The specified certificate is not valid. It has expired.
Response: Check the certificate. Make sure that the certificate is valid and not expired.

Security Error (114-1436): The distinguished name was not in the proper format.
Cause: The distinguished name was not in the proper format.
Response: Check the distinguished names. Make sure that they are in proper format. Contact webMethods
Technical Services for further assistance.

Security Error (114-1437): The distinguished name exists, but its certificate is not certified.
Cause: The certificate is not certified, although the distinguished name exists.
Response: Make sure that all the certificates in the certificate file are properly certified.

126 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Security Error (114-1439): The connection to host <host> could not be opened because the secure socket handshake failed.
The Broker's certificate is not valid because it has expired.
Cause: At attempt to connect to the Broker host failed because the Broker's SSL certificate has expired.
Response: Check the SSL certificate and make sure it is still valid.

Security Error (114-1441): The connection to host <host> could not be opened because the secure socket handshake failed.
This can happen if the server's certificate is not trusted by your certificate file, or if the server requires a client certificate and
no distinguished name was provided when making the connection, or if an attempt was made to connect to a non-secure
port.
Cause: An attempt to connect to the Broker host failed for one of the following reasons:
- Your certificate file does not trust the Broker Server's certificate
- The Broker Server requires a client certificate, but a distinguished name was not provided when making the
connection.
- An attempt was made to connect to a non-secure port.
Response: Check your certificate file. Make sure that it trusts the Broker Server's certificate and make sure that
it provides a distinguished name if required. Also, make sure that a secure port is used.

Security Error (114-1442): Secure sockets are not supported with this version of the library.
Cause: The Broker Client tried to connect to the Broker using SSL, but was unable to because SSL is not
installed or enabled on the Broker.
Response: Make sure that the SSL is installed and enabled. Also, make sure that the native SSL libraries are
available on the shared library path.

Security Error (114-1443): Secure sockets are not supported or are not enabled on the Broker.
Cause: Secure sockets are not supported or are not enabled on the Broker.
Response: Make sure that the SSL is installed and enabled on the Broker. Also, make sure that the native SSL
libraries are available on the shared library path.

Security Error (114-1444): There is no default certificate in the specified certificate file. Only certificate files with one
certificate in them may use this option.
Cause: The specified certificate file does not contain a default certificate. Only certificate files that contain one
certificate may use this option.
Response: Check the certificate. Make sure that the certificate is specified explicitly when using a certificate file
with more than one certificate.

webMethods Error Message Reference Version 6.5 and 6.5.1 127

CHAPTER 1 webMethods Broker

Security Error (114-1445): Secure sockets are not supported or are not enabled on the Broker trying to join the territory, and
the territory requires secure connections.
Cause: A Broker attempted to join a territory that requires SSL connections, but SSL is not supported or is not
enabled on the Broker.
Response: Check the Brokers in the territory. Make sure that all of them either have SSL enabled or disabled.

Security Error (114-9999): Error cause unknown.

Cause: An unknown error occurred with SSL on the Broker.
Response: Check the permissions and password for certificate access. Contact webMethods Technical Services
for further assistance.

Timeout (112-1450): The request timed out.

Cause: An operation that is expecting a reply from the Broker timed out.
Response: Make sure that the Broker Server is running on the specified host:port and that connectivity between
the server host and the client host is stable. Reissue any request that can be reissued on timeout conditions.

Timeout (112-1451): The Broker Server Monitor reports that the server was not started within its timeout period. It may or
may not have been started.
Cause: The Broker Server start operation failed to return the status within the default timeout period of 30
seconds.
Response: Check the Broker Server. If it was not started, reissue a start request. Note that the Broker Server can
start successfully even after the timeout condition.

Timeout (112-1452): Initializing a connection to host <hostName>:<portNum> timed out.

Cause: A request to create a Broker client timed out while waiting for the connection to the Broker server to
initialize. A network delay or an engaged Broker may be the cause.
Response: Make sure that the Broker Server is running on the specified host:port and that connectivity between
the server host and the client host is stable.

Unknown Broker Name (223-1460): No Broker by the name <brokerName> was found on host <hostName>:<portNum>.
Cause: Broker could not complete the operation because the specified Broker is not found on the host
<hostName>:<portNum>.
Response: Make sure that the specified Broker exists on the Broker Server.

128 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Unknown Broker Name (223-1461): No default Broker was found on host <hostName>:<portNum>.
Cause: The Broker could not create the client because a default Broker is not defined on the Broker Server.
Response: Assign a default Broker to the Broker Server and use the Broker name explicitly while creating
clients.

Unknown Broker Name (223-1462): Territory join failed. No Broker by the name <brokerName> was found on host
<hostName>:<portNum>.
Cause: An attempt to join a Broker to a territory failed because the specified Broker does not exist on the Broker
Server.
Response: Make sure that a Broker with the specified name exists on the Broker Server, then reissue the
territory join request.

Unknown Broker Name (223-1463): There is no Broker in the territory by the name <brokerName> on host
<hostName>:<portNum>.
Cause: Broker could not complete the operation because Broker <brokerName> does not exist in the territory.
Response: Make sure that a Broker with the specified name exists in the territory.

Unknown Broker Name (223-1464): Territory join failed. Must specify a specific Broker to join to. You cannot join to the
default Broker.
Cause: The join operation could not be completed because the target Broker was not specified.
Response: Specify the target Broker for the join operation. Make sure that the target Broker is already a member
of the territory.

Unknown Client Group (224-1470): Could not create client. Client group <clientGroup> was not found on the Broker.
Cause: Client Application could not complete the create operation because the specified client group does not
exist on the Broker.
Response: Make sure that the specified client group exists on the Broker.

Unknown Client Group (224-1471): Could not complete operation. Client group <clientGroup> was not found on the Broker.
Cause: Client Application could not complete the operation because the specified client group does not exist on
the Broker.
Response: Make sure that the specified client group exists on the Broker.

webMethods Error Message Reference Version 6.5 and 6.5.1 129

CHAPTER 1 webMethods Broker

Unknown Client ID (225-1480): Could not reconnect client. Client <clientID> does not exist.
Cause: The Broker could not reconnect the client because the specified client ID cannot be found on the Broker.
Response: Make sure that the client is valid and a client with the specified name exists on the Broker, then issue
the reconnect request.

Unknown Client ID (225-1481): Could not complete operation. Client <clientID> does not exist.
Cause: The Broker could not complete the operation because the client with the specified client ID does not
exist on the Broker.
Response: Make sure that the client with the specified client ID exists on the Broker.

Unknown Document Type (226-1490): Document type <docType> is not defined in the Broker.
Cause: The Broker could not complete the operation because the specified document type does not exist on the
Broker.
Response: Make sure that the specified document type is defined on the Broker.

Unknown Document Type (226-1491): There is no document type document named <scopeName> defined in the Broker.
Cause:

The Broker could not obtain the document type definition of events because events with the specified scope
name do not exist on the Broker.
Response: Make sure that at least one event exists with the specified scope name and then reissue this call.

Unknown Infoset (227-1500): There is no infoset named <infosetName> defined on document type <docType> in the Broker.
Cause: The Broker could not complete the infoset operation because the specified infoset name could not be
found on the Broker.
Response: Make sure that the specified infoset exists on the Broker , then issue the infoset related API calls.

Unknown Key (228-1510): There is no platform key named <key> defined.

Cause: Platform information could not be obtained for the specified platform key because the key is not present
in the platform information.
Response: Check the platform key. Make sure that the key is valid before requesting the platform information.

Unknown Name (229-1520): A certificate for the provided distinguished name is not available in the certificate file <certFile>.
Cause: A client application could not set SSL on the Broker Server because the specified distinguished name
does not exist in the certificate file.
Response: Make sure that the specified distinguished name is valid and present in the certificate file.

130 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker C API

Unknown Server (247-1700): Could not complete the operation. No server is configured on port <portNum>.
Cause: The Broker Server operation could not complete because there is no Broker Server configured on the
specified port. The monitor process may be running on the host, but a Broker Server is not configured.
Response: Make sure that the Broker Server on the specified host:port is started before issuing any Broker
Server operations.

Unknown Session ID (248-1710): Could not complete the operation. The session <sessionID> does not exist for client
<clientID>.
Cause: The disconnect operation could not complete because the specified session ID does not exist on the
Broker client. The session may already be closed or it may not exist.
Response: Make sure that a session with the specified session-ID exists on the Broker client before issuing a
disconnect request.

Unknown Territory (249-1720): Could not create the gateway. The specified Broker is not a member of territory <terrName>.
Cause: The gateway could not be created because the specified territory does not exist on the Broker or the
specified Broker is not a member of the territory.
Response: Make sure that the Broker and the territory exist and the Broker is member of the territory.

Unknown Territory (249-1721): There is no gateway defined on the current Broker that connects to territory <terrName>.
Cause: The requested gateway operation could not complete because the gateway on the specified territory
does not exist on the Broker.
Response: Make sure that the gateway in the specified territory exists on the current Broker.

webMethods Error Message Reference Version 6.5 and 6.5.1 131

CHAPTER 1 webMethods Broker

Broker Java API

Bad State (200-1002): This operation cannot be called from within a callback function.
Cause: The callback function tried to call a function, such as awDispatch() or awMainloop(), but this is not
allowed because only one thread can be active when one of these functions is called.
Response: Do not issue the function calls within the callback function.

Bad State (200-1003): There are no clients currently connected.

Bad State (200-1005): Cannot get the Broker's distinguished name because the client is not connected using secure sockets.
Cause: The Broker client attempted to access SSL information on a non-ssl client connection.
Response: Make sure that the client is enabled with SSL before issuing any SSL-specific API calls.

Bad State (200-1007): Could not release Broker change lock. The Broker change lock is not currently held by any client.
Cause: The Broker administrative client could not release the change lock because the lock is not currently held
by a client.
Response: Acquire the change lock, then invoke this call.

132 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Bad State (200-1008): Could not release Broker change lock. The Broker change lock is currently held by client <clientID>,
session <sessionID>, and was locked at <lockTime>.
Cause: The Broker administrative client could not acquire or release the change lock because the lock is held by
a different client, <clientID>.
Response: Acquire or release the Broker change lock on <clientID> as appropriate, then reissue the change lock
request.

Bad State (200-2027): Territory gateway is already paused.

Cause: A request to pause the gateway that was already in a paused state was issued.
Response: Make sure that the gateway is not paused before issuing this request.

Bad State (200-2028): Territory gateway is already resumed.

Cause: A request to resume the gateway that was never paused was issued.
Response: Make sure that the gateway is paused before issuing this request.

Broker Backup Error (280-2035): Backup is in progress on another session.

Cause: Backup is in progress on another session. Only one active backup session is supported.
Response: Make sure that there is no other session performing metadata backup and reissue the backup
request.

Broker Backup Error (280-2036): Backup is only supported on Broker Servers with separate metadata and run-time data.
Cause: Backup is supported only on broker servers that are configured with split meta-data and runtime
storage.
Response: Make sure that the data storage is configured with separate metadata and run-time storage.

Broker Exists (230-1530): Cannot create Broker. The Broker <brokerName> already exists.
Cause: A Broker name that was specified with the awCreateBroker() call already exists on the Broker Server.
Response: Reissue the awCreateBroker request using a valid, unused name for the Broker.

Broker Failure (100-1010): A failure occurred on the Broker. The error code is <code> and the message is <fail_string>.
Cause: The response from the Broker could not be read properly.
Response: One of the parameters in the error message <failString> contains additional information about the
failure. Review the error message to determine the appropriate action. Contact Technical Services for further
assistance.

webMethods Error Message Reference Version 6.5 and 6.5.1 133

CHAPTER 1 webMethods Broker

134 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

webMethods Error Message Reference Version 6.5 and 6.5.1 135

CHAPTER 1 webMethods Broker

Broker Failure (100-2019): The operation failed because the Broker was attempted to contact another Broker at the same time
that Broker was attempting to contact it. Please retry your operation.
Cause: The Broker attempted to connect to the remote Broker while a connection attempt was in progress on a
different thread.
Response: Allow the connection attempt to complete and then issue a new connection request.

Broker Failure (100-2021): The operation failed because the specified character set is not supported on the Broker.
Cause: The specified character is not supported on the broker.
Response: Install and add support for the character set on the broker.

136 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Client Group Exists (231-1540): Cannot create client group. The client group <clientgroupName> already exists on the
Broker.
Cause: A client group named <clientgroupName>already exists on the Broker.
Response: Use a unique name for the client group.

webMethods Error Message Reference Version 6.5 and 6.5.1 137

CHAPTER 1 webMethods Broker

Connection Closed (103-1070): The connection is closed.

Corrupt (104-1080): The document field data has been corrupted.

Cause: The document field data has been corrupted.
Response: Make sure that the document is valid.

Corrupt (104-1081): The type definition data has been corrupted.

Cause: The type definition data has been corrupted.
Response: Recreate the document type by importing any saved ADL files.

138 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Field Not Found (203-1091): The field <fieldName> is not defined in the document type definition.
Cause: The field <fieldName> is not defined in the document type definition.
Response: Make sure that the specified field name is defined in the document type definition.

Field Type Mismatch (204-1110): Field type mismatch when looking up <field_name>. A field of a non-sequence type is being
accessed as if it were a sequence.
Cause: The field type does not match the <fieldName> field. A sequence type operation can only be performed
on a sequence type field.
Response: Make sure that only sequence type operations are performed on sequence type fields.

webMethods Error Message Reference Version 6.5 and 6.5.1 139

CHAPTER 1 webMethods Broker

Field Type Mismatch (204-1118): Field <fieldName> is not of type <fieldType>.

Cause: The Field <fieldName> does not match the requested field type.
Response: Make sure the field types match.

140 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Filter Parse Error (205-1130): A syntax error was encountered while parsing the filter. <parseMsg>.
Cause: A syntax error was encountered while parsing the filter. Check the error message <parseMsg> for more
details.
Response: Make sure that the filter string is valid and syntactically correct.

webMethods Error Message Reference Version 6.5 and 6.5.1 141

CHAPTER 1 webMethods Broker

Filter Parse Error (205-1131): Parser stack underflow. <parseMsg>.

Filter Parse Error (205-1132): The filter contains an invalid character constant. <parseMsg>.
Cause: The filter contains an invalid character constant. Check the error message <parseMsg> for more details.
Response: Make sure that the filter is valid and the syntax in the filter is correct.

Filter Parse Error (205-1133): The filter contains a string that is missing its closing quotation mark. <parseMsg>.
Cause: The filter contains a string that is missing a closing quotation mark.
Response: Check the syntax for the filter strings. Make sure that the quotation symbols are used correctly.

Filter Parse Error (205-1134): The field <fieldName> does not exist. <parseMsg>.
Cause: The field <fieldName> is not found in the document type definition.
Response: Verify that the field names specified in the filter are valid and present in the document type
definition.

Filter Parse Error (205-1135): The function <function> does not exist. <parseMsg>.
Cause: The function <function> does not exist. The specified function is not valid or not supported by the filter
compiler.
Response: Verify that the filter string is valid and only supported functions are used. Refer to the API
documentation for the list of supported functions.

Filter Parse Error (205-1136): The filter contains an invalid number. <parseMsg>.
Cause: The filter contains an invalid number. Check the error message <parseMsg> for more details.
Response: Verify that the filter string is valid and that the correct parameters are used.

Filter Parse Error (205-1137): An unexpected character was encountered while parsing the filter. <parseMsg>.
Cause: An unexpected character was encountered while parsing the filter.
Response: Make sure that the filter string is valid and syntactically correct.

142 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Filter Parse Error (205-1138): The type <fieldType> was found where a Boolean type was expected. <parseMsg>.
Cause: The type <fieldType> was found where a Boolean type was expected.
Response: Verify that the filter string is valid and uses the correct parameters.

Filter Parse Error (205-1139): The type <fieldType> was type was found where a string, date or numeric type was expected.
<parseMsg>.
Cause: The type <fieldType> was found where a string, date or numeric type was expected. Or, a sequence or
struct type was found where a basic type was expected.
Response: Verify that the filter string is valid and uses the correct parameters.

Filter Parse Error (205-1140): The type <type> was found where a numeric type was expected. <parseMsg>.
Cause: A numeric type was expected while evaluating a numeric expression in the filter, but a non-numeric
type was found.
Response: Verify that the filter string is valid and the correct parameter types are passed.

Filter Parse Error (205-1141): The type <type> was found where an integral type was expected. <parseMsg>.
Cause: The type <type> was found where an integral type was expected. An integral type is needed for certain
operations, such as bit-wise operations.
Response: Verify that the filter string is valid and correct parameters are passed.

Filter Parse Error (205-1142): The types <type1> and <type2> are incompatible for comparison. <parseMsg>.
Cause: The types <type1> and <type2> are incompatible for comparison.
Response: Verify that the filter string is valid and correct.

Filter Parse Error (205-1143): The function <function> does not have enough parameters. <parseMsg>.
Cause: The function <function> does not have enough parameters.
Response: Verify that the correct number of parameters are passed to the functions in the filter.

Filter Parse Error (205-1144): The function <function> has too many parameters. <parseMsg>.
Cause: The function <function> has too many parameters. Too many arguments are being passed to a filter
function.
Response: Make sure that the correct number of parameters are passed to the functions used in the filter.

webMethods Error Message Reference Version 6.5 and 6.5.1 143

CHAPTER 1 webMethods Broker

Filter Parse Error (205-1147): The filter contains an invalid escape character: <parseMsg>.
Cause: The filter contains an invalid escape character. Check the error message <parseMsg> for more details.
Response: Make sure that the filter is valid and syntactically correct.

Filter Parse Error (205-1148): The function <function> has the wrong number of parameters. <parseMsg>.
Cause: The wrong number of parameters were passed to the <function> function.
Response: Make sure that the filter string is valid and that the parameters passed to the functions used in the
filter are correct.

Filter Runtime Error (206-1146): An internal error was encountered while parsing the filter.
Cause: A runtime error occurred while parsing the specified filter.
Response: Make sure that the specified filter string is valid. If the filter string is found to be valid, please report
to webMethods Customer Care for further assistance.

Filter Runtime Error (206-1160): The filter operation resulted in a division by zero.
Cause: The evaluation of filter expression at run time results in division by zero.
Response: Make sure that the filter string is valid and does not result in any division by zero condition while
evaluating operands.

144 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Filter Runtime Error (206-1164): The filter result is not a Boolean.

Cause: The filter string returned an error because the filter result is not a Boolean.
Response: Make sure that the filter string evaluates to a Boolean value.

Filter Runtime Error (206-1167): A filter stack overflow has occurred.

Cause: The filter string might be invalid.
Response: Make sure that the filter string is valid.

Filter Runtime Error (206-1168): A filter stack underflow has occurred.

Cause: The filter string might be invalid.
Response: Make sure that the filter string is valid.

webMethods Error Message Reference Version 6.5 and 6.5.1 145

CHAPTER 1 webMethods Broker

Filter Runtime Error (206-1171): An unexpected type was encountered while applying the filter.
Cause: The specified filter may not be valid. An unexpected type was encountered while applying the filter
Response: Make sure that the specified filter is valid.

Filter Runtime Error (206-1171): An unexpected type was encountered while applying the filter.
Cause: A runtime error occurred due to a mismatch in the field type specified in the filter and the field type
found in the document.
Response: Check that the specified filter string is valid. If the filter string is found to be valid, please report to
webMethods Customer Care for further assistance.

Filter Runtime Error (206-1172): Invalid filter version was encountered.

Cause: A runtime error occurred due to a mismatch between filter compiler versions (internal to the filter
engine) while parsing the specified filter.
Response: Check that the specified filter string is valid. If the filter string is found to be valid, please report to
webMethods Customer Care for further assistance.

Filter Runtime Error (206-1173): Invalid filter length was encountered

Cause: A runtime error occurred due to a mismatch between filter length on the compiled filter code (internal
to the filter engine) while parsing the specified filter.
Response: Check that the specified filter string is valid. If the filter string is found to be valid, please report to
webMethods Customer Care for further assistance.

Format Error (207-1181): Error in parsing document bin string data.

Cause: The bin string may be invalid or might have been obtained from an invalid BrokerEvent.
Response: Make sure that the bin string is valid and obtained from a valid BrokerEvent.

146 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

webMethods Error Message Reference Version 6.5 and 6.5.1 147

CHAPTER 1 webMethods Broker

Incompatible Version (106-1206): The Broker does not support setting subscription filters for territory gateways.
Cause: This version of Broker does not support setting subscription filters for territory gateways.
Response: Upgrade to a newer version of webMethods Broker where this feature is supported.

Incompatible Version (106-1207): The Broker Server does not support access to a server log.
Cause: This version of Broker does not support access to a server log.
Response: Upgrade to a newer version of webMethods Broker where this feature is supported.

Incompatible Version (106-1208): The Broker does not support change locks.
Cause: This version of the Broker does not support the change locks feature.
Response: Upgrade to newer version of webMethods Broker where this feature is supported.

148 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Incompatible Version (106-1811): The client queue browser is only supported on Brokers of version 6.5 or higher.
Cause: This version of the Broker does not support queue browser operations.
Response: Make sure that the Broker Server is version 6.5 or higher.

Incompatible Version (106-2023): The Broker Server does not support setting the filter collation locale.
Cause: This version of Broker does not support setting filter collation locale.
Response: Upgrade to a newer version of webMethods Broker where this feature is supported.

Incompatible Version (106-2024): Redelivery counting is not supported on this version of the Broker.
Cause: The redelivery counting feature is not supported on the 6.1 versions of Broker.
Response: For this feature, make sure you are using Broker 6.1 and onward versions.

Incompatible Version (106-2025): Territory gateway keep alive is not supported on this version of the Broker.
Cause: The territory keep alive feature is not supported on pre 6.1 versions of Broker.
Response: For this feature, make sure you are using Broker 6.1 and onward versions.

Incompatible Version (106-2026): Territory gateway pause is not supported on this version of the Broker.
Cause: The territory gateway pause feature is not supported on pre 6.1 versions of Broker.
Response: For this feature, make sure you are using Broker 6.1 and onward versions.

Incompatible Version (106-2029): Check for Events is not supported on this version of the Broker.
Cause: The check for events feature is not supported on pre 6.1 versions of Broker.
Response: For this feature, make sure you are using Broker 6.1 and onward versions.

Incompatible Version (106-2030): Client keep alive is not supported on this version of the Broker.
Cause: The client keep alive feature is not supported on pre 6.1 versions of Broker.
Response: For this feature, make sure you are using Broker 6.1 and onward versions.

Incompatible Version (106-2031): Transaction administration is not supported on this version of the Broker.
Cause: Transaction administration is not supported on the 6.1 versions of Broker.
Response: For this feature, make sure you are using Broker 6.1 and onward versions.

webMethods Error Message Reference Version 6.5 and 6.5.1 149

CHAPTER 1 webMethods Broker

Incompatible Version (106-2032): Synchronous get event(s) is not supported on this version of the Broker.
Cause: This version of the Broker does not support synchronous receive operation.
Response: Make sure that the Broker Server is version 6.5 or higher.

Incompatible Version (106-2033): Static gateway subscription is not supported on this version of the Broker.
Cause: This version of the Broker does not support static gateway forwarding feature.
Response: Make sure that the Broker Server is version 6.1 SP3 or higher.

Incompatible Version (106-2034): The Broker Server does not support metadata backup.
Cause: This version of the Broker does not support met data backup.
Response: Make sure that the Broker Server is version 6.5 or higher.

Interrupted (107-1210): The operation was interrupted by request.

Cause: The operation was interrupted by user request.
Response: None.

Invalid Broker Name (236-1590): The Broker name <brokerName> is not valid. Broker names cannot contain unprintable
characters, a colon, '@', '/', or '\' and they cannot start with a '#' symbol. They must be between 1 and 255 ANSI characters or
1 and 42 Unicode characters in length.
Cause: The Broker name <brokerName> is not valid. Broker names cannot contain unprintable characters (":",
"@", "/", or "\" ), and they cannot start with the "#" symbol. They must be between 1 and 255 ANSI characters or
1 and 42 Unicode characters in length.
Response: Make sure that the broker name is valid and contains only supported characters.

150 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Invalid ClientQueueLock (271-3777): The specified ClientQueueLock is invalid.

Cause: The specified ClientQueueLock is invalid.
Response: Check the ClientQueueLock parameter. Make sure that the parameter is a valid ClientQueueLock
object and is not NULL.

webMethods Error Message Reference Version 6.5 and 6.5.1 151

CHAPTER 1 webMethods Broker

Invalid ClientQueueLock (271-3781): An error occurred while accessing the ClientQueueLock of <clientID>. The
ClientQueueLock is invalid or the volatile target client may have exited.
Cause: The ClientQueueLock of <clientID> may be invalid or the volatile target client may have exited.
Response: Check the ClientQueueLock. Make sure that its parameters correspond to a valid client and that the
client still exists on the Broker.

Invalid Document Type Name (213-1271): The document name <docName> contains an illegal character sequence. Names
may contain '::' but not ':' or ':::'.
Cause: The document name <docname> contains an illegal character sequence. Names may contain "::" but not
":" or ":::"
Response: Make sure that the document name is valid and properly formatted.

Invalid Document Type Name (213-1272): The document name <docName> contains an invalid character at the start of a
document name. A field name cannot start with a numeric character or an underscore.
Cause: The document name <docName> is invalid. Document names must be between 1 and 255 ANSI
characters or 1 and 42 Unicode characters in length.
Response: Check the document name. Make sure the document name contains between 1 and 255 ANSI
characters or 1 and 42 Unicode characters.

152 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

webMethods Error Message Reference Version 6.5 and 6.5.1 153

CHAPTER 1 webMethods Broker

154 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Invalid Field Name (214-1722): The field <field_name> already exists, so you cannot set a property with this name.
Cause: A field with the specified name already exists on the document. Field names in a document has to be
unique.
Response: Make sure to specify a field name that is not present in the document type while setting properties.

Invalid Filter (282-1310): The filter <filter_name> contains a parser error.

Cause: Specified filter contains parser error.
Response: Make sure that the filter expression is valid.

Invalid Filter (282-1315): The filter is invalid. The character at position <character_position> in the filter is not valid inside a
hint.
Cause: Specified filter is invalid because an invalid character was specified in a hint.
Response: Make sure that the filter hint contains valid characters.

Invalid Filter (282-1316): The filter is invalid.The hint <hint> is not valid.
Cause: Specified filter is invalid because it contains an invalid hint.
Response: Make sure that the filter hint is valid.

Invalid Filter (282-1317): The filter is invalid. The hint at position <char_position> is missing its value.
Cause: Specified filter is invalid because the hint is missing its value.
Response: Make sure that the filter hint is valid.

Invalid Filter (282-1318): The filter is invalid. The hint value <hint> is not valid for the hint located at position <char_position>.
Cause: Specified filter is invalid because the value specified for the hint is invalid.
Response: Make sure that the filter hint is valid.

Invalid Filter (282-1319): The filter is invalid. The hint at position <char_pos> is missing its closing brace.
Cause: Specified filter is invalid because of the invalid syntax of the hint.
Response: Make sure that the filter hint is valid.

webMethods Error Message Reference Version 6.5 and 6.5.1 155

CHAPTER 1 webMethods Broker

Invalid Filter (282-2310): The filter is invalid. The hint at position <char_pos> is missing the "hint:" prefix.
Cause: Specified filter is invalid because of the invalid syntax of the hint.
Response: Make sure that the filter hint is valid.

Invalid Filter (282-2311): The filter is invalid. The hint at position <char_pos> is missing a comma delimiter.
Cause: Specified filter is invalid because of the invalid syntax of the hint.
Response: Make sure that the filter hint is valid.

Invalid Operation (274-1760): A manual increment of a redelivery count was attempted for a client that has automatic
increments enabled.
Cause: A request to increment the redelivery count on a queued document was made when the redelivery
count mode is set to 'auto'. This auto setting prevents any attempts to manually change the redelivery count
value.
Response: Make sure that the redelivery count mode is not set to 'auto' before issuing manual increment
requests.

Invalid Operation (274-1761): Could not complete operation. A request to check or get events already exists.
Cause: A request to check for events cannot be issued as there already exists a pending get events request on
the Broker from this client session.
Response: Reissue the request after the get events request is served by the Broker.

156 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Invalid Operation (274-1809): Could not complete the operation because an active queue browser is open on this client
session.
Cause: An attempt was made to retrieve events from the queue while a queue browser was open (in self-
browse mode) from the same client session.
Response: Make sure that the queue browser is closed before issuing an event retrieval request.

Invalid Permission (241-1640): The permissions contained an invalid setting.

Cause: The permissions contained an invalid setting.
Response: Make sure to pass correct permission settings.

Invalid Platform Key (242-1650): Could not set the platform info. The key <key> is not valid.
Cause: The platform information key could not be set on the BrokerClient. The key may contain invalid or
restricted characters.
Response: Specify a valid platform information key.

Invalid Poll Operation (279-1782): One or more of the operations are not valid poll operations.
Cause: An invalid Broker client poll operation was specified.
Response: Supply the correct Broker client poll operation. The only valid Broker client poll operation is
BrokerClientPoll.GET_EVENTS.

Invalid Port (243-1660): The port <portNum> is not a valid port on the host.
Cause: Port <portNum> is not a valid port on the Broker host.
Response: Specify a valid port number.

webMethods Error Message Reference Version 6.5 and 6.5.1 157

CHAPTER 1 webMethods Broker

Invalid QM Operation (270-3781): An error occurred while accessing the ClientQueueLock of <clientID>. The ClientQueueLock
is invalid or the volatile target client may have exited.
Cause: The ClientQueueLock of <clientID> may be invalid or the volatile target client may have exited.
Response: Check the ClientQueueLock. Make sure that its parameters correspond to a valid client and the
client still exists on the Broker.

Invalid Sequence Number (277-1770): Cannot increment the redelivery count of the requested document because the
sequence number <seqn> does not correspond to any unacknowledged document.
Cause: The specified sequence number passed does not correspond to any unacknowledged documents.
Response: In the sequence number, be sure to pass document(s) that have been retrieved and not
acknowledged.

158 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Invalid Sequence Number (277-1771): Cannot negatively acknowledge requested document because the sequence number or
numbers do not correspond to any unacknowledged document.
Cause: The list of sequence numbers passed for the negative ack operation contains one or more sequence
numbers that do not correspond to any unacknowledged documents.
Response: In the sequence number, be sure to pass document(s) that have been retrieved and not
acknowledged.

Invalid Sequence Number (277-1772): Cannot negatively acknowledge requested document because a duplicate sequence
number or numbers was provided.
Cause: The list of sequence numbers passed for the negative ack operation contains a duplicate value.
Response: Make sure that the list does not contain any duplicate sequence numbers.

Invalid State (278-1780): Cannot increment redelivery counts for a client that does not have redelivery counting enabled.
Cause: Redelivery counting is not enabled.
Response: Be sure to enable redelivery counting before issuing requests related to redelivery count activities.

Invalid Subscription (216-1310): The filter <filter> contains a parse error.

Cause: The specified filter contains a parse error.
Response: Check the filter string. Make sure that it is valid.

webMethods Error Message Reference Version 6.5 and 6.5.1 159

CHAPTER 1 webMethods Broker

Invalid Subscription (216-2310): The subscription is invalid. The hint at position <charPostion> is missing its 'hint:' prefix.
Cause:
The subscription is invalid. The hint at position <charPosition> is missing its "hint" prefix.
Response: Check the syntax of the hint. Verify that the correct syntax is used for creating subscriptions.

Invalid Subscription (216-2311): The subscription is invalid. The hint at position <charPosition> is missing a comma
delimiter.
Cause: The subscription is invalid. The hint at position <charPosition> is missing a comma delimiter.
Response: Check the syntax of the hint. Verify that the correct syntax is used for creating subscriptions.

160 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Invalid Subscription (216-9999): Error cause unknown.

Cause: The cause for this error is unknown.
Response: Make sure that the subscriptions are valid. For further assistance contact webMethods Technical
Services.

Invalid Territory Name (244-1670): The territory name <territoryName> is not valid. Territory names cannot contain
unprintable characters, a colon, '@', '/', or '\' and they cannot start with a '#' symbol. They must be between 1 and 255 ANSI
characters or 1 and 42 Unicode characters in length.
Cause: The specified territory name contains invalid or unsupported characters in it.
Response: Verify that the specified territory name is valid and follows the rules outlined in the API
documentation.

Invalid Transaction (251-1220):

Cause: The supplied transaction identifier is not recognized by the Broker's transaction manager.
Response: Supply the correct transaction identifier.

Invalid Transaction (251-1640): You do not have permission to do the current operation on the specified transaction.
Cause: You do not have permission to end or finalize the transaction.
Response: You must end the transaction from the correct client.

Invalid Transaction (251-1740): The specified transaction is already prepared.

Cause: The specified transaction was already prepared.
Response: No action required because the specified transaction is already in the desired state.

Invalid Transaction (251-1745): The transaction is not in the appropriate state for the requested operation.
Cause: The specified transaction is not in a state where the attempted operation is allowed.
Response: Apply the correct operation to the current state; e.g., a prepared transaction cannot be reopened, but
it can be committed or rolled back.

Invalid Transaction (251-1746): The transaction has been heuristically committed.

Cause: The transaction can not be completed because the Broker's transaction manager heuristically completed
it already.
Response: Examine the Broker's transaction manager's list of heuristically (lost) transactions and possibly
purge this transaction from the list; also, consult the Transaction Coordinator to commit this transaction.

webMethods Error Message Reference Version 6.5 and 6.5.1 161

CHAPTER 1 webMethods Broker

Invalid Transaction (251-1747): The transaction has been heuristically rolled back.
Cause: The transaction can not be completed because the Broker's transaction manager heuristically rolled it
back already.
Response: Examine the Broker's transaction manager's list of heuristically (lost) transactions and possibly
purge this transaction from the list; also, consult the Transaction Coordinator to roll back this transaction.

Invalid Transaction (251-1748): The specified transaction cannot be reopened.

Cause: The transaction is not in a state where it can be reopened.
Response: The transaction could have been created by a different client, or it could have been prepared. Apply
the correct operation to transaction.

Invalid Transaction (251-1749): There is an invalid value in the current transaction.

Cause: An invalid value was supplied when trying to end, prepare, commit or rollback a transaction.
Response: Supply the correct value for the API call.

Invalid Transaction (251-1750): The specified transaction id is not valid.

Cause: The supplied transaction identifier is not recognized by the Broker's transaction manager.
Response: Supply the correct transaction identifier.

Invalid Transaction (251-1762): The transaction time out value specified is invalid.
Cause: An incorrect timeout value for the transaction was specified when creating a new transaction.
Response: Supply the correct timeout value: -1, 0 or a positive number.

Invalid Transaction (251-1763): The specified transaction already exists.

Cause: A transaction with the specified external identifier already exists in the Broker's transaction manager.
Response: Choose a different external identifier for your transaction.

Invalid Transaction (251-1764): The specified transaction already exists hueristically.

Cause: A transaction with the specified external identifier exists as a heuristically committed transaction in the
Broker's transaction manager.
Response: Choose a different external identifier for your transaction or purge the Broker's transaction
manager's collection of heuristically completed transactions using an administrative tool.

162 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Invalid Transaction Id (272-3793): There is a client mismatch in the current transaction.

Cause: A client attempted to perform a transactional operation on a BrokerClient that was initialized by
another client.
Response: Make sure that transactional operations are issued from the Broker Clients that originally created the
transaction.

Invalid Transaction Id (272-3794): The current transaction is already open.

Invalid Type (217-1322): Cannot get a field of type sequence of sequence.

Invalid Type (217-1323): Cannot set a field of type sequence using a basic set function. Use a sequence set function.
Cause: The client application tried to use a basic set function to assign a value to a sequence type field, but only
a sequence set function can be used for this purpose.
Response: Use the right function for the field type. If you want to assign a value to a non-sequence field, use a
basic set function. If you want to set a assign a value to a sequence field, use a sequence set function.

webMethods Error Message Reference Version 6.5 and 6.5.1 163

CHAPTER 1 webMethods Broker

Invalid Type (217-1324): Cannot set a field of type sequence of sequence.

Cause: A client application tried to assign a value to a "sequence of sequence" field. A "sequence of sequence" is
equivalent to an "array of arrays" or multi-dimensional array. You cannot assign a value to a "sequence of
sequence" field using basic sequence set functions.
Response: Use the right function for the field type. If you want to assign a value to a basic sequence field, use a
basic sequence set function. If you want to assign a value to a "sequence of sequence" field, use set sequence
functions of appropriate type on individual members of the base sequence. Refer to Broker API documentation
for more information.

Invalid Type (217-1326): The document contains data of an unsupported type.

Cause: The document contains data of an unsupported type.
Response: Verify that the event is valid and contains supported data types.

Invalid Type (217-1329): An unsupported type was specified.

Cause: The BrokerClient could not complete the requested operation because the specified field type is
unknown or unsupported in the Broker Event.
Response: Verify that the specified type is supported.

164 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Invalid Type (217-1331): The type definition code contains an unsupported type.
Cause: The type definition code contains an unsupported type.
Response: Verify that the type code is valid.

Invalid Type (217-2300): Only struct and document types are valid for this operation.
Cause: A client application tried to perform an operation on an field that is not of type "struct" or "document",
but the requested operation can only work on those types of fields.
Response: Specify a struct or BrokerEvent field name when creating a new document type, ordering the fields
in a document type, or changing the name of a document.

webMethods Error Message Reference Version 6.5 and 6.5.1 165

CHAPTER 1 webMethods Broker

Invalid Type Cache (218-1340): The type cache pointer is NULL or is not a type cache. Perhaps the variable is uninitialized or
the client has been disconnected.
Cause: The type cache pointer is NULL or is not a type cache. Perhaps the variable is uninitialized or the client
has been disconnected.
Response: Verify that the passed parameter of type "TypeDefCache" is valid, properly initialized, and not
NULL.

Invalid Type Definition (219-1353): Type definition top-level entry was not named.
Cause: Type definition top-level entry was not named.
Response: Specify a top level type name when creating new type definitions.

Invalid Type Definition (219-1356): The type <typeName> is not in the type cache.
Cause: The specified type is not found in the cache.
Response: Make sure that the type exists on the broker.

166 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Invalid Type Definition (219-2351): The document type <typeName> cannot be synchronized with the other territory because
the document type's description is different.
Cause: The Broker could not synchronize one of its document types (<typeName>) with the document type in
another territory because the document types in the two territories are not the same.
Response: Verify that the description values of document types present on both territories are the same.

Invalid Type Definition (219-2353): The document type <typeName> cannot be stored in the Broker because its type definition
is not valid.
Cause: The client application tried to store a document on the Broker, but the document's type <typeName>
does not have valid type definition.
Response: Make sure that the type code specified is valid. Refer to webMethods Broker Administrative API
documentation for further assistance on creating document types.

webMethods Error Message Reference Version 6.5 and 6.5.1 167

CHAPTER 1 webMethods Broker

No Permission (109-1375): The field <fieldName> is read only.

No Permission (109-1377): Cannot subscribe to document type <docType>. Permission is denied. Check the 'can subcribe'
permissions in the client's client group.
Cause: The Broker Client tried to subscribe to a document of the specified type, but was unable to because the
client does not have the required permissions.
Response: Check the client's client group subscribe permissions. Make sure that the appropriate subscribe
permissions are set.

168 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

No Permission (109-1379): Operation failed. Permission denied.

No Permission (109-1380): Cannot change the value of platform key <key>.

Cause: The Broker denied a request to edit the platform key because the key is not user-settable.
Response: Make sure that the keys are user-definable. Refer to the Broker API documentation for further
assistance.

webMethods Error Message Reference Version 6.5 and 6.5.1 169

CHAPTER 1 webMethods Broker

170 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

No Permission (109-2372): An access label cannot be required on the accessLabelAdapter client group.
Cause: Setting EnforcedAccessLabel on ALA client group is not permitted since this will result in connection
issues on ALA.
Response: Make sure that the ALA client group's settings are not modified.

Null Parameter (220-1400): The input parameter <parameters> is NULL.

Cause: The input parameter <parameter> was null, but this operation requires input.
Response: Make sure that the input parameters are initialized properly.

Null Parameter (220-1401): The output parameter <parameter> is NULL.

webMethods Error Message Reference Version 6.5 and 6.5.1 171

CHAPTER 1 webMethods Broker

Out of Range (221-1411): Cannot set the forced reconnect option on a shared state client.
Cause: An attempt was made to set forced reconnect on a shared-state client. This particular combination is not
supported.
Response: Make sure that the client does not set the forced reconnect option on a shared state client.

Out of Range (221-1400): The input parameter <parameter_name> is out of range.

Cause: An incorrect value was supplied when setting Territory Gateway permissions.
Response: Supply the correct permission value(s).

Out of Range (221-1412): The value of 'flag' is not a legal value.

Cause: The Broker encountered a serious internal error.
Response: Contact webMethods Technical Services.

Out of Range (221-1415): Cannot use a sequence number less than zero.
Cause: The specified sequence number is -ve. It cannot be less than 0.
Response: Specify a valid sequence number (>= 0).

Out of Range (221-1416): Cannot set a sequence size to a value less than zero.
Cause: The specified sequence size is -ve. It cannot be less than 0.
Response: Specify a valid sequence size (>= 0).

172 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Out of Range (221-1418): The value of 'n' must not be less than 0.
Cause: The specified input parameter "n" contains an invalid value. It should not be < 0.
Response: Specify a valid value for "n".

Out of Range (221-1419): A sequence index in field name <field_name> is out of bounds.
Cause: The specified sequence index on a sequence field name is out of bounds (either < 0 or > the actual length
of the sequence).
Response: Check the index in the field name. Make sure that it is within the bounds of the actual sequence
length.

Out of Range (221-1422): Subscription IDs cannot be less than 0.

Cause: A client tried to pass a negative number in as the subscription ID.
Response: Specify a positive value for the sub ID.

Out of Range (221-1425): Time to live cannot be a negative number.

Cause: The time to live value cannot be negative.
Response: Specify a positive value for time to live.

webMethods Error Message Reference Version 6.5 and 6.5.1 173

CHAPTER 1 webMethods Broker

Out of Range (221-1427): The lifecycle specified is not a valid value.

Out of Range (221-1781): Territory gateway keep alive cannot be a negative number.
Cause: The supplied keep-alive parameters are out of range.
Response: Supply the correct keep-alive parameters.

Out of Range (221-1783): Invalid client keep-alive setting.

Cause: An attempt was made to enable client keep alive option with invalid parameters.
Response: Make sure that the specified parameters are valid.

174 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Out of Range (221-2425): An invalid encryption level was specified.

Out of Range (221-3423): An invalid transaction mode was specified.

webMethods Error Message Reference Version 6.5 and 6.5.1 175

CHAPTER 1 webMethods Broker

Out of Range (221-3433): A shared document type for a gateway does not have accept_subscribe set to true, but has a non-
empty filter set.
Cause: A request to set up shared event types on a gateway failed because the Broker does not permit
subscriptions with filters to be forwarded.
Response: Check the parameters set in the "BrokerSharedEventTypeInfo" structure. Without setting the
'accept_subscribe' flag, you cannot set subscriptions on the gateway.

176 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Out of Range (221-3437): The specified prepare timeout is out of range.

Cause: An incorrect timeout value for the transaction was specified when setting the transaction default.
Response: Supply the correct timeout value: -1, 0 or a positive number.

Out of Range (221-3438): The specified prepare timeout action is not valid.
Cause: An incorrect timeout action for the transaction was specified when setting the transaction default.
Response: Supply the correct transaction timeout action (commit or rollback).

Out of Range (221-3439): The specified transaction type is invalid.

Cause: An invalid parameter was supplied to the Broker when attempting to list the current transactions.
Response: Supply the correct operation parameters.

Out of Range (221-3440): The specified transaction operation is invalid.

Cause: An invalid operation was specified when attempting to forcefully end a transaction from an
administrative tool.
Response: Supply the correct operation parameters.

Protocol Error (111-1433): A protocol failure occurred.

Cause: An unknown error in the protocol request caused the operation to fail.
Response: Contact webMethods Technical Services.

webMethods Error Message Reference Version 6.5 and 6.5.1 177

CHAPTER 1 webMethods Broker

Queue Browser Error (281-1812): The operation failed because the event at the cursor position was removed. Please retry
after setting the cursor to a valid queue position.
Cause: A request to browse client queue was rejected because the last set queue position on the browser got
invalidated as the event in that position got removed from the queue.
Response: Set the queue position to a valid position and retry the browse operation.

Queue Browser Error (281-1800): Unknown queue browser.

Cause: Specified queue browser is does not exist on the broker.
Response: Make sure that the queue browser exists.

Queue Browser Error (281-1801): The queue browser has been already closed or is invalid.
Cause: Specified queue browser is invalid as it has been already closed.
Response: Make sure that the queue browser is not closed.

Queue Browser Error (281-1802): The client queue has been already locked by this client.
Cause: An attempt was made to reacquire the queue lock of a client, which is already locked by this client
session.
Response: Make sure that the client queue is unlocked before opening a locked queue browser.

Queue Browser Error (281-1803): The client queue is locked by a different client.
Cause: An attempt was made to lock a client queue which was already locked by a different client.
Response: Make sure that the client queue is unlocked before opening a locked queue browser.

Queue Browser Error (281-1804): The client queue already has an open queue browser session from this client.
Cause: An attempt was made to open a queue browser on a client for which a queue browser was already exists
on the current client session.
Response: Make sure that there is no queue browser open on the desired target client queue before issuing an
open queue browser request.

Queue Browser Error (281-1805): Invalid queue position.

Cause: An attempt was made to set the queue position to an invalid position (< 0 or >= queue length) for a
browse operation.
Response: Make sure that the specified queue position is valid and it is within the range of 0 and queue length
-1.

178 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Queue Browser Error (281-1806): The client queue is exhausted; there are no more events to return.
Cause: An attempt was made to browse past the queue length on the client queue.
Response: Make sure that the queue position is set to a valid position before issuing a browse request.

Queue Browser Error (281-1807): Failed attempt to replace a queued event with an event of a different storage type using
modify operation. Events of different storage types cannot be replaced
Cause: An attempt was made to replace an event in queue with an event of different storage type. Storage types
of the events being swapped has to match.
Response: Make sure that the exchanged events have the same storage type.

Queue Browser Error (281-1808): The operation failed because the client queue is busy. Please retry your operation.
Cause: Could not complete the operation because the client queue is busy (serving an asynchronous request or
clearing queue etc).
Response: Retry the operation after a few seconds.

Queue Browser Error (281-1810): An attempt to modify an event that has been retrieved but not yet acknowledged (unacked
event). Unacked events cannot be modified.
Cause: An attempt was made to modify an event that was delivered to one of the client session, but not yet
acknolwdged. Modify operation is not supported on unacknowledged events on the queue.
Response: Make sure that the event being modified is deliverable.

webMethods Error Message Reference Version 6.5 and 6.5.1 179

CHAPTER 1 webMethods Broker

Security Error (114-1441): The connection to host <hostName> could not be opened because the secure socket handshake
failed. This can happen if the server's certificate is not trusted by your certificate file, or if the server requires a client
certificate and no distinguished name was provided when making the connection, or if an attempt was made to connect to a
non-secure port.
Cause: An attempt to connect to the Broker host failed for one of the following reasons:
- Your certificate file does not trust the Broker Server's certificate.
- The Broker Server requires a client certificate, but a distinguished name was not provided when making the
connection.
- An attempt was made to connect to a non-secure port.
Response: Check your certificate file. Make sure that it trusts the Broker Server's certificate and make sure that
it provides a distinguished name if required. Also, make sure that a secure port is used.

Security Error (114-1442): Secure sockets are not supported with this version of the library.
Cause: The Broker Client tried to connect to the Broker using SSL, but was unable to because SSL is not
installed or enabled on the Broker.
Response: Make sure that SSL is installed and enabled. Also, make sure that the native SSL libraries are
available on the shared library path.

Security Error (114-1444): There is no default certificate in the specified certificate file. Only certificate files with one
certificate in them may use this option.
Cause: The specified certificate file does not contain a default certificate. Only certificate files that contain one
certificate may use this option.
Response: Make sure that the certificate is specified explicitly when using a certificate file with more than one
certificate.

180 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Security Error (114-9999): Error cause unknown.

Cause: An unknown error occurred with SSL on the Broker.
Response: Check the permissions and password for certificate access. Contact webMethods Technical Services
for further assistance.

Timeout (112-1450): The request timed out.

Timeout (112-1451): The Broker Server Monitor reports that the server was not started within its timeout period. It may or
may not have been started.
Cause: The Broker Server start operation failed to return the status within the default timeout period of 30
seconds
Response: Check the Broker Server. If it was not started, reissue a start request. Note that the Broker Server can
start successfully even after the timeout condition.

Timeout (112-1452): Initializing a connection to host <hostName>:<portNum> timed out.

webMethods Error Message Reference Version 6.5 and 6.5.1 181

CHAPTER 1 webMethods Broker

Unknown Broker Name (223-1465): No territory or gateway Broker was found with the specified name.
Cause: An invalid or non-existent remote broker name was specified for the check and restart forwarding
operaion.
Response: Make sure that the specified remote Broker name corresponds to one of the territory Brokers.

182 webMethods Error Message Reference Version 6.5 and 6.5.1

Broker Java API

Unknown Document Type (226-1491): There is no document type document named <scopeName> defined in the Broker.
Cause: The Broker could not obtain the document type definition of events because events with the specified
scope name do not exist on the Broker.
Response: Make sure that at least one event exists with the specified scope name and then reissue this call.

Unknown Key (228-1510): There is no platform key named <key> defined.

webMethods Error Message Reference Version 6.5 and 6.5.1 183

CHAPTER 1 webMethods Broker

184 webMethods Error Message Reference Version 6.5 and 6.5.1

CHAPTER 2
webMethods Deployer

ETD.0002.0001 Syntax: -h <host> -p <port> -u <user> -x <password> -r <build name> -f <project name> -d (turn on debug)
Cause: The command line utility was started with incorrect parameters.
Response: Verify that each of the parameters: host, port, user, password, etc., is correct.

ETD.0002.0002 Cannot connect to server <serverName>

Cause: The Deployer could not connect to the specified server when executing the CreateBuild command line
script.
Response: Verify that the connection information specified to the script is correct and that the server is running.

ETD.0002.0003 You are not authorized to extract the <projectName> project

Cause: You do not have build authority for the specified project.
Response: Ask an administrator or user that has build authorization for the project to perform this task.
Alternatively, have an administrator update the your authorization for the specified project to assign you
build authorization.

ETD.0002.0005 Error checking authorization: <errorMsg>

Cause: An error occurred while invoking the "wm.deployer.authorization:isAuthorized" service on the
Integration Server that is running Deployer.
Response: Verify that the service exists and that the permissions for the service are adequate to allow execution
of the service.

ETD.0002.0006 Error writing project file into build file: <buildFile>

Cause: An error occurred while attempting to write the project file in the build archive file.
Response: Verify that there is sufficient disk space, memory, and operating system privileges.

webMethods Error Message Reference Version 6.5 and 6.5.1 185

CHAPTER 2 webMethods Deployer

ETD.0002.0007 Error writing properties file into build file: <buildFile>. Check the project name was correctly specified.
Cause: An error occurred while attempting to write the build properties file in the build archive file.
Response: Verify that there is sufficient disk space, memory, and operating system privileges.

ETD.0002.0008 Error closing build file: <buildFile>

Cause: An error occurred when attempting to close the build file.
Response: Verify that there is sufficient disk space, memory, and operating system privileges.

ETD.0002.0009 Error creating build report: <buildReportFile>

Cause: An error occurred when attempting to create the build report file.
Response: Verify that there is sufficient disk space, memory, and operating system privileges.

ETD.0002.0010 Error during extraction: <extraction error>

Cause: An error occurred when attempting to create a build for a project. The extraction error can be any error
that occurred when attempting to create the build. This error can be caused by an object that is listed in the
project, but does not exist on the source system.
Response: Ensure all objects that are listed in the project exist on the source system.

ETD.0002.0011 Error extracting IS Package <packageName>: <errorMessage>

Cause: An error occurred while invoking the "wm.deployer.resource.extractor.is:extractPackage" service.
Response: Verify that the service exists and that the permissions are adequate to allow execution of the service.

ETD.0002.0012 Error extracting IS ACL(s) on source system <serverName>: <errorMessage>

Cause: An error occurred while invoking the "wm.deployer.resource.extractor.is:extractAcls" service on the
specified source system.
Response: Verify that the service exists and that the permissions are adequate to allow execution of the service.

ETD.0002.0013 IS ACL <aclName> does not exist

Cause: The Integration Server ACL specified in the project does not exist on the source system.
Response: Either remove the ACL from the project or add it to the source system.

186 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0002.0014 Error extracting IS User(s) on source system <serverName>: <errorMessage>
Cause: An error occurred while invoking the "wm.deployer.resource.extractor.is:extractUsers" service on the
specified source system.
Response: Verify that the service exists and that the permissions are adequate to allow execution of the service.

ETD.0002.0015 IS user <userName> does not exist

Cause: The Integration Server user account specified in the project does not exist on the source system.
Response: Either remove the user from the project or create the user account on the source system.

ETD.0002.0016 Error extracting IS Group(s) on source system <serverName>: <errorMessage>

Cause: An error occurred while invoking the "wm.deployer.resource.extractor.is:extractGroups" service on the
specified source system.
Response: Verify that the service exists and that the permissions are adequate to allow execution of the service.

ETD.0002.0017 IS group <groupName> does not exist on source system

Cause: The Integration Server group specified in the project does not exist on the source system.
Response: Either remove the group from the project or create the group on the source system.

ETD.0002.0018 Error extracting IS Port(s) on source system <serverName>: <errorMessage>

Cause: An error occurred while invoking the "wm.deployer.resource.extractor.is:extractPorts" service on the
specified source system.
Response: Verify that the service exists and that the permissions are adequate to allow execution of the service.

ETD.0002.0020 Error extracting scheduled service <serviceName> (<serviceID>) on source system <serverName>:
<errorMessage>
Cause: An error occurred while invoking the "pub.scheduler:getTaskInfo" service on the specified source
system.
Response: Verify that the service exists and that the permissions are adequate to allow execution of the service.
If the error message indicates that the scheduled service is not on the source system, either remove the
scheduled service from the project or add it to the source system.

ETD.0002.0021 Error extracting from TN on source system <serverName>: <errorMessage>

Cause: An error occurred while invoking the "wm.tn.admin:exportData" service on the specified source
Trading Networks system.
Response: Verify that the source Trading Networks system is running, the service exists, and that the
permissions are adequate to allow execution of the service.

webMethods Error Message Reference Version 6.5 and 6.5.1 187

CHAPTER 2 webMethods Deployer

ETD.0002.0035 Error invoking service <serviceName>.

Cause: An error occurred invoking a service on the Integration Server that is running Deployer.
Response: The Integration Server error message might be visible in the Integration Server Error log and could
give some insight about the problem. Verify that the service exists and that the permissions are adequate to
execute the service.

ETD.0002.0036 Error remote invoking service <serviceName> on system <serverName>.

Cause: An error occurred while invoking a service on a remote system; that is, not the Integration Server that is
running Deployer.
Response: The Integration Server error message might be visible in the Integration Server Error log and could
give some insight about the problem. Verify that the service exists and that the permissions are adequate to
execute the service.

ETD.0002.0038 Project <projectName> is empty.

Cause: The specified project does not contain any object to extract.
Response: Use the Deployer user interface to add objects to the project.

ETD.0002.0039 The following source server(s) are not currently available: <serverName>. Please check your network
connection, and verify that the source server(s) are running.
Cause: The source servers are not responding to a ping. To ping a server, Deployer executes a service:

- For an Integration Server system, Deployer uses the "wm.server:ping" service.

- For a Trading Networks system, Deployer uses the "wm.tn:ping" service.

- For any other system, Deployer uses the "ping" plug-in Web service.
Response: Check the network connection and verify that the system is running.

ETD.0002.0040 Project <projectName> has unresolved dependencies.

Cause: The project has unresolved dependencies and could possibly result in an incomplete deployment.
Response: Use the Deployer user interface to resolve the dependencies.

ETD.0002.0041 Deployment set <deploymentSet> has unresolved dependencies.

Cause: The deployment set has unresolved dependencies and could possibly result in an incomplete
deployment.
Response: Use the Deployer user interface to resolve the dependencies.

188 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0002.0042 IS Package file(s) <listOfFiles> do not exist
Cause: The list of files specified for the package do not exist.
Response: Use the Deployer user interface to verify and edit the list of files for the package.

ETD.0002.0043 IS Package <packageName> does not exist

Cause: The Integration Server package specified in the project does not exist on the source system.
Response: Either remove the package from the project or add it to the source system.

ETD.0002.0044 Error extracting from <pluginType> on source system <serverName>: <errorMessage>

Cause: An error occurred while invoking the Deployer plug-in web service "getObjects" on the source system
specified.
Response: Verify that the source system is running, the service exists, and that the permissions are adequate to
execute the service.

ETD.0002.0045 Build file "<buildFilename>" does not contain a properties file

Cause: Build cannot load because the file is incomplete.
Response: Make sure the build file is not corrupted and has not been manually updated.

ETD.0002.0053 IS port "<port>" does not exist

Cause: The Integration Server port was not extracted into build.
Response: Make sure that the port exists in the source.

ETD.0002.0069 Error writing into the build file: <errorMessage>

Cause: An error occurred while trying to write to the build file.
Response: Read the error message to determine the possible causes. Ensure that the build file exists, that it is
read/write, and that there is adequate room on the file system.

ETD.0002.0070 TN Field group "<fieldGroup>" does not exist

Cause: The Trading Networks profile field group specified in the project does not exist on the specified source
Trading Networks system.
Response: Either remove the profile field group from the project or add it to the source Trading Networks
system.

webMethods Error Message Reference Version 6.5 and 6.5.1 189

CHAPTER 2 webMethods Deployer

ETD.0002.0071 TN Field definition "<fieldDefinition>" does not exist

Cause: The Trading Networks profile field definition specified in the project does not exist on the source
Trading Networks system.
Response: Either remove the profile field definition from the project or add it to the source Trading Networks
system.

ETD.0002.0072 TN Profile "<profile>" does not exist

Cause: The Trading Networks profile specified in the project does not exist on the source Trading Networks
system.
Response: Either remove the profile from the project or add it to the source Trading Networks system.

ETD.0002.0073 TN TPA "<TPA>" does not exist

Cause: The Trading Networks trading partner agreement (TPA) specified in the project does not exist on the
source Trading Networks system.
Response: Either remove the TPA from the project or add it to the source Trading Networks system.

ETD.0002.0074 TN Document attribute "<documentAttribute>" does not exist

Cause: The Trading Networks document attribute specified in the project does not exist on the source Trading
Networks system.
Response: Either remove the document attribute from the project or add it to the source Trading Networks
system.

ETD.0002.0075 TN Document type "<documentType>" does not exist

Cause: The Trading Networks document type specified in the project does not exist on the source Trading
Networks system.
Response: Either remove the TN document type from the project or add it to the source Trading Networks
system.

ETD.0002.0076 TN Processing rule "<processingRule>" does not exist

Cause: The Trading Networks processing rule specified in the project does not exist on the Trading Networks
source system.
Response: Either remove the processing rule from the project or add it to the source Trading Networks system.

190 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0002.0077 TN ID type "<IDType>" does not exist
Cause: The Trading Networks external ID type specified in the project does not exist on the source Trading
Networks system.
Response: Either remove the external ID type from the project or add it to the source Trading Networks system.

ETD.0002.0078 TN Contact type "<contactType>" does not exist

Cause: The Trading Networks contact type specified in the project does not exist on the source Trading
Networks system.
Response: Either remove the contact type from the project or add it to the source Trading Networks system.

ETD.0002.0079 TN Binary type "<binaryType>" does not exist

Cause: The Trading Networks binary type specified in the project does not exist on the source Trading
Networks system.
Response: Either remove the binary type from the project or add it to the source Trading Networks system.

ETD.0002.0080 TN Profile group "<profileGroup>" does not exist

Cause: The Trading Networks profile group specified in the project does not exist on the source Trading
Networks system.
Response: Either remove the profile group from the project or add it to the source Trading Networks system.

ETD.0002.0081 TN Extended field "<extendedField>" for profile "<profile>" does not exist
Cause: The Trading Networks extended field specified in the project does not exist on the source Trading
Networks system for the profile specified.
Response: Either remove the extended field from the project or add it to the appropriate profile in the source
Trading Networks system.

ETD.0002.0082 TN Security data item "<securityData>" does not exist

Cause: The Trading Networks security data item specified in the project does not exist on the source Trading
Networks system.
Response: Either remove the security data item from the project or add it to the source Trading Networks
system.

ETD.0003.0003 Cannot connect to server <serverName>.

Cause: The indicated server, or the network connection to that server, is not available. Alternatively, the
command-line values for user and password might not be valid on the indicated server.
Response: Confirm that the server is running and reachable, and that the user/password values are valid.

webMethods Error Message Reference Version 6.5 and 6.5.1 191

CHAPTER 2 webMethods Deployer

ETD.0003.0004 Error invoking service <serviceName>.

Cause: The Integration Server, or the network connection to that server, may be shut down.
Response: Confirm that the server is running and reachable.

ETD.0004.0000 Project <projectName> does not exist.

Cause: The Deployer user interface referenced a project name that is not recognized by Deployer. Another
Deployer session might have deleted this project, or the project might be corrupted on the file system.
Response: Refresh the page and try again. If the same error occurs, this project might be corrupted on the file
system and have to be discarded.

ETD.0004.0002 Could not load project <projectName>.

Cause: The project file is corrupted.
Response: Use Windows Explorer to locate the <serverDirectory>\packages\WmDeployer\persist\projects
directory, and manually remove the project file. Then use Deployer to recreate it.

ETD.0004.0003 Could not save project <projectName>. Updates were not performed.
Cause: Deployer encountered an error writing to disk.
Response: Check your Integration Server's disk space. If you believe there should be sufficient space, try to save
again. If saving again is not successful, restarting the server might help, or recreate the project.

ETD.0004.0004 Project <projectName> does not have a deployment set named <deploymentSetName>.
Cause: The Deployer user interface referenced a deployment set name that is not recognized by the Deployer.
Another Deployer session might have deleted this deployment set, or the project might be corrupted on the
file system.
Response: Refresh the page and try again. If the same error occurs, this project might be corrupted on the file
system and have to be discarded.

ETD.0004.0006 No dependency on component <componentName> was found.

Cause: The Deployer user interface attempted to delete a dependency that is not recognized by Deployer.
Another Deployer session might have deleted the dependency, or the project might be corrupt on the file
system.
Response: Refresh the page and try again. If the same error occurs, this project might be corrupted on the file
system and have to be discarded.

192 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0004.0007 Cannot access server alias <serverName> in deployment set <deploymentSetName>.
Cause: The Deployer user interface referenced a source server name that is not recognized by Deployer.
Another Deployer session might have deleted the source server from the project, or the project might be
corrupted on the file system.
Response: Refresh the page and try again. If the same error occurs, this project might be corrupted on the file
system and have to be discarded.

ETD.0004.0008 Package <packageName> from server alias <serverName> does not exist in deployment set
<deploymentSetName>.
Cause: The Deployer user interface referenced a package or server name that is not recognized by Deployer.
Another Deployer session might have deleted the package or server name from the project, or the project
might be corrupted on the file system.
Response: Refresh the page and try again. If the same error occurs, this project might be corrupted on the file
system and have to be discarded.

ETD.0004.0010 Package <packageName> already exists in deployment set <deploymentSetName> as a complete package.
Cannot add package components or files to it.
Cause: You attempted to add package components to a deployment set; however, the entire package already
exists in the deployment set.
Response: If you want to include the entire package in a deployment set, no action is necessary because it is
already included. If you want the deployment set to contain only a partial package, first remove the entire
package from the deployment set before attempting to add specific package components.

ETD.0004.0011 Project <projectName> already contains a deployment set named <deploymentSetName>.

Cause: You attempted to add a deployment set to the specified project; however, the project already has a
deployment set that uses the same name that you specified.
Response: Use a different name for the new deployment set.

ETD.0004.0012 Project name <projectName> contains illegal characters.

Cause: The project name that you specified contains characters that are not allowed in a project name.
Response: Specify another name for the project that does not include the following illegal characters: " " (space),
"$" (dollar sign), "~" (tilde), or "/" (slash).

ETD.0004.0013 Could not complete project copy due to file system error.
Cause: Deployer encountered an error writing the project to disk.
Response: Check your Integration Server's disk space. If you believe there should be sufficient space, try the
copy again. As a final option, manually recreate the project.

webMethods Error Message Reference Version 6.5 and 6.5.1 193

CHAPTER 2 webMethods Deployer

ETD.0004.0014 Project <projectName> already exists.

Cause: You attempted to add a project; however, a project with the name you specified already exists.
Response: Use a different name for the new project name.

ETD.0004.0015 Could not invoke service <serviceName>.

Cause: Deployer was unable to find the specified Integration Server service.
Response: Determine whether a required Integration Server package is disabled, missing, or whether parts are
missing. Check for the following packages: WmDeployer, WmAdmin, WmRoot, or possibly
WmDeployerResource or WmModeler.

ETD.0004.0016 Unable to delete build <buildName>.

Cause: Deployer was unable to delete the specified build file.
Response: The build file is probably in use. This file exists in the
<serverDirectory>\packages\WmDeployer\persist\projects\<YourProjectName>\builds directory. Locate
the process that is accessing this file, and stop it. Then try to delete the build again.

ETD.0004.0017 Project <projectName> does not have a build named <buildName>.

Cause: The Deployer user interface referenced a build name that is not recognized by the Deployer. Another
Deployer session might have deleted this build, or the project might be corrupted on the file system.
Response: Refresh the page and try again. If the same error occurs, this project might be corrupted on the file
system and have to be discarded.

ETD.0004.0018 Could not load build <buildName>.

Cause: The build file is corrupted.
Response: Use Windows Explorer to locate the
<serverDirectory>\packages\WmDeployer\persist\projects\<YourProjectName>\builds directory, and
manually remove the corrupted build file. Then use Deployer to rebuild.

ETD.0004.0019 Deployment map <deploymentMapName> already exists in project <projectName>.

Cause: You attempted to create a deployment map; however, a deployment map with the name you specified
already exists.
Response: Use a different name for the new deployment map.

194 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0004.0020 Deployment map <deploymentMapName> does not exist in project <projectName>.
Cause: The Deployer user interface referenced a deployment map name that is not recognized by the Deployer.
Another Deployer session might have deleted this deployment map, or the project might be corrupted on the
file system.
Response: Refresh the page and try again. If the same error occurs, this project might be corrupted on the file
system and have to be discarded.

ETD.0004.0021 Could not load deployment map <deploymentMapName> from project <projectName>.
Cause: The deployment map file is corrupted.
Response: Use Windows Explorer to locate the
<serverDirectory>\packages\WmDeployer\persist\projects\<YourProjectName>\targets directory, and
manually remove your deployment candidate file. Then use G90Deployer to recreate it.

ETD.0004.0026 Could not save deployment map <deploymentMapName>.

Cause: Deployer encountered an error writing to disk.
Response: Check your Integration Server's disk space. If you believe there should be sufficient space, try to save
again. If saving again is not successful, restarting the server might help, or recreate the deployment map.

ETD.0004.0028 Deployment set <deploymentSetName> has not been mapped to target <serverName>.
Cause: The Deployer user interface referenced a deployment set name that is not recognized by the Deployer.
Another Deployer session might have deleted this deployment set, or the project might be corrupted on the
file system.
Response: Refresh the page and try again. If the same error occurs, this project might be corrupted on the file
system and have to be discarded.

ETD.0004.0032 Server alias cannot be blank.

Cause: You left the required server alias field blank.
Response: Fill in the server name field, and try again.

ETD.0004.0058 File already exists and overwrite is false: <fileName>

Cause: You attempted to export a build; however, a build with that name already exists.
Response: Use a different name when you export the build.

ETD.0004.0059 File <fileName> does not exist.

Cause: You attempted to import a build that does not exist.
Response: Refresh the Import Build screen, and try again.

webMethods Error Message Reference Version 6.5 and 6.5.1 195

CHAPTER 2 webMethods Deployer

ETD.0004.0060 User is not authorized to export builds from project <projectName>.

Cause: You are not authorized to export builds for the specified project. You must have build authorization for
the project.
Response: Ask an administrator or user that has build authorization for the project to perform this task.
Alternatively, have an administrator update the your authorization for the specified project to assign you
build authorization.

ETD.0004.0061 User is not authorized to import builds to project <projectName>.

Cause: You are not authorized to import builds for the specified project. You must have build authorization for
the project.
Response: Ask an administrator or user that has build authorization for the project to perform this task.
Alternatively, have an administrator update the your authorization for the specified project to assign you
build authorization.

ETD.0004.0064 Deployment <deploymentName> already exists in project <projectName>.

Cause: You attempted to create a deployment set in the specified project; however, the project already has a
deployment set that uses the same name that you specified.
Response: Use a different name for the new deployment set.

ETD.0004.0065 Could not save deployment <deploymentName>.

ETD.0004.0067 Deployment <deploymentName> does not exist in project <projectName>.

Cause: The Deployer user interface referenced a deployment candidate that is not recognized by Deployer.
Another Deployer session might have deleted the deployment candidate, or the project might be corrupted on
the file system.
Response: Refresh the page and try again. If the same error occurs, this project might be corrupted on the file
system and have to be discarded.

ETD.0004.0068 Unable to delete deployment map <deploymentMapName>.

Cause: Deployer was unable to delete the specified deployment map file.
Response: The deployment map file is probably in use. This file exists in the
<serverDirectory>\packages\WmDeployer\persist\projects\<YourProjectName>\targets directory. Locate
the process that is accessing this file, and stop it. Then try to delete the deployment candidate again.

196 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0004.0069 Unable to delete deployment <deploymentName>.
Cause: Deployer was unable to delete the deployment candidate file.
Response: The deployment candidate file is probably in use. This file exists in the
<serverDirectory>\packages\WmDeployer\persist\projects\<YourProjectName>\deployments directory.
Locate the process that is accessing this file, and stop it. Then try to delete the deployment candidate again.

ETD.0004.0072 Could not load deployment <deploymentName> from project <projectName>.

Cause: The deployment candidate file is corrupted.
Response: Use Windows Explorer to locate to the
<serverDirectory>\packages\WmDeployer\persist\projects\<YourProjectName>\deployments directory,
and manually remove the deployment candidate file. Then use Deployer to recreate it.

ETD.0004.0073 Could not add component <componentName> of type <typeName>.

Cause: Deployer does not recognize the specified Integration Server component.
Response: Rather than attempting to add the component to the project, add the files that comprise the
component (e.g., "ns" directory). Alternatively, you might consider adding the entire package rather than
individual components of the package.

ETD.0004.0075 Since 'deploymentName' was specified then 'newDeploymentName', 'newDeploymentDescription',

'buildName', and 'deploymentMapName' cannot be specified.
Cause: When running the deploy.bat or deploy.sh script, incorrect arguments were specified.
Response: The deploy script can either reference an existing deployment candidate, or the user can specify
information to create a new deployment candidate. When you specify the "deploymentName" argument to
reference an existing deployment candidate, do not supply other arguments that are needed to create a new
deployment candidate.

ETD.0004.0076 Since newDeploymentName was specified then 'buildName' and 'deploymentMapName' must also be
specified
Cause: You specified incorrect arguments for the deploy.bat or deploy.sh script.
Response: The deploy script can either reference an existing deployment candidate, or the user can specify
information to create a new deployment candidate. When you specify the "newDeploymentName" argument
to indicate that you want to create a new deployment candidate, you must also specify the "buildName" and
"deploymentMapName" arguments.

webMethods Error Message Reference Version 6.5 and 6.5.1 197

CHAPTER 2 webMethods Deployer

ETD.0004.0077 You are not authorized to modify the project definition.

Cause: You are not authorized to define a project.
Response: Ask an administrator or user that has define authorization to perform the action for you.
Alternatively, have an administrator update the your authorization to assign you define authorization.

ETD.0004.0078 You are not authorized to modify the project target mapping.
Cause: You are not authorized to map a project.
Response: Ask an administrator or user that has map authorization to perform the action for you.
Alternatively, have an administrator update the your authorization to assign you map authorization.

ETD.0004.0079 You are not authorized to modify project deployments.

Cause: You are not authorized to deploy a project.
Response: Ask an administrator or user that has deploy authorization to perform the action for you.
Alternatively, have an administrator update the your authorization to assign you deploy authorization.

ETD.0004.0080 You are not authorized to remove project builds.

Cause: You are not authorized to build a project.
Response: Ask an administrator or user that has build authorization to perform the action for you.
Alternatively, have an administrator update the your authorization to assign you build authorization.

ETD.0004.0081 Build <buildName> cannot be deleted because it is being used by deployment <deploymentName>.
Cause: You attempted to delete a build that is referenced by a deployment candidate.
Response: Either do not delete this build, or before you attempt to delete the build, delete or modify the
deployment candidate that references it.

ETD.0004.0082 Deployment map <deploymentMapName> cannot be deleted because it is being used by deployment
<deploymentName>.
Cause: You attempted to delete a deployment map that is referenced by a deployment candidate.
Response: Either do not delete this deployment map, or before you attempt to delete the deployment map,
delete or modify the deployment candidate that references it.

ETD.0004.0083 Exception occurred while: <exceptionMessage>.

Cause: An exception occurred while trying to load the project.
Response: The exception might occur due to an input/output error. Review the exception message to determine
the cause of the error.

198 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0004.0085 Could not add package <packageName> to the deployment set.
Cause: The Deployer was unable to determine which components in the package were available for variable
substitution. The problem might be that the source Integration Server was temporarily unavailable.
Response: Check the Integration Server Error log to determine the reason that the Deployer was unable to
access information about the package components.

ETD.0004.0086 Deployment map <deploymentMapName> in project <projectName> is corrupted and must be removed. It
references deployment set <deploymentSetName> which does not exist.
Cause: The deployment map file is corrupted.
Response: Use Windows Explorer to locate the
<serverDirectory>\packages\WmDeployer\persist\projects\<YourProjectName>\targets directory, and
manually remove the deployment map file. Then use Deployer to recreate it.

ETD.0004.0087 Deployment set <deploymentSetName> cannot be removed. It is referenced by deployment map

<deploymentMapName>.
Cause: You attempted to delete a deployment set that is being referenced by a deployment map.
Response: Either do not delete this deployment set, or before you attempt to delete the deployment set, first
delete or modify the deployment map that references it.

ETD.0004.0089 Could not save adapter connections metadata for project <projectName>
Cause: The project is corrupted.
Response: Retry your last action taken on the deployment project. If the action is unsuccessful, create a new
project.

ETD.0004.0092 Could not update package <packageName> version in deployment set. Please try again or determine why
package <packageName> or package version is unavailable.
Cause: Deployer was unable to access the specified package on the server.
Response: Retry the action. If the action is unsuccessful, investigate why the Deployer is unable to locate the
specified package on the remote server. If the package appears to be available on the remote server, shut down
the Deployer window (as well as the window that launched Deployer), and restart the browser.

ETD.0004.0093 Both the <pluginName1> and the <pluginName2> Deployer Plugins contain the Deployer Plugin Type:
<pluginType>.
Cause: More than one plug-in for the same type of deployment asset has been detected. This typically indicates
a problem with the configuration of the Deployer.
Response: Update the configuration of the Deployer to remove extraneous plug-ins for the same type of
deployment asset. Alternatively, you can uninstall, then reinstall Deployer.

webMethods Error Message Reference Version 6.5 and 6.5.1 199

CHAPTER 2 webMethods Deployer

ETD.0004.0096 Currently unable to access TN system: <TNSystemName>.

Cause: No data was returned from the specified Trading Networks Server. This indicates that the Trading
Networks Server is not accessible.
Response: Ensure that the Trading Networks Server is accessible over the network and that you have correctly
configured the server alias for the Trading Networks Server.

ETD.0004.0097 Currently unable to access target system: <targetServerAlias>.

Cause: The target Trading Networks Server is not available. The server did not respond to a server ping.
Response: Ensure that the Trading Networks Server is accessible over the network and that you have correctly
configured the server alias for the Trading Networks Server.

ETD.0004.0098 Cannot check target cluster configuration. Target is missing Deployer Resource Package. This can be
installed from the Servers IS & TN screen.
Cause: An error occurred when the Deployer attempted to access a service on the target WmDeployerResource
package.
Response: Install the current version of WmDeployerResource package onto the target server.

ETD.0004.0099 Cluster node details not available.

Cause: An error occurred when the Deployer attempted to access a service on the target WmDeployerResource
package.
Response: Install the current version of the WmDeployerResource package on the target server. Also, ensure
that the target server is running, and is reachable on the network.

ETD.0004.0201 Checkpoint for Deployment Candidate <deploymentCandidateName> failed. Please see the Checkpoint
report.
Cause: Possible causes for this error:

1) Project file could not be found in, or loaded from, the Build.

2) Target file or Deployment Candidate could not be loaded from disk.

3) User is not authorized to create a Checkpoint.

4) Other reasons shown in the Checkpoint report.

Response: Verify that the Build is available and correct, and that there is sufficient disk space and memory.
Also verify that the necessary operating system privileges are set and that the User has authorization to create
a Checkpoint. Review the Checkpoint report.

200 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0004.0202 Checkpoint for Deployment Candidate <deploymentCandidateName> completed with warnings. Please see
the Checkpoint report.
Cause: A warning during the extraction of objects from source system(s) can have many causes. See the
Checkpoint report for more information.
Response: Any further action depends upon the contents of the Checkpoint report—most warnings require no
action by the user.

ETD.0004.0206 Checkpoint for Deployment Candidate <deploymentCandidateName> failed: <exceptionMessage>

Cause: An exception ocurred during the extraction of objects from source system(s). Some possible causes:

1) Project file could not be found in, or loaded from, the Build.

2) Target file or Deployment Candidate could not be loaded from disk.

3) User is not authorized to create a Checkpoint.

4) Other reasons shown in the Checkpoint report.

ETD.0004.0300 User is not authorized to create variable substitution file for project <projectName>.
Cause: You are not authorized to perform the action of variable substitution for the specified project. You must
have map authorization for the project.
Response: Ask an administrator or user that has map authorization for the project to perform this task.
Alternatively, have an administrator update the your authorization for the specified project to assign you map
authorization.

ETD.0004.0301 Could not save variable substitution file <fileName>.

ETD.0004.0302 Variable substitution object type <varSubItemType> is invalid.

Cause: Deployer attempted to create a varSub item that is not valid. This might occur if the service that is
attempting to create the varSub item is invoked by something other than the Deployer user interface.
Response: Contact webMethods Customer Care to report this issue and request a fix.

webMethods Error Message Reference Version 6.5 and 6.5.1 201

CHAPTER 2 webMethods Deployer

ETD.0004.0501 Dependencies may not contain the '$' character.

Cause: The MANUAL dependency that was added contains the '$' character, which is not allowed.
Response: Remove the '$' character.

ETD.0004.0631 Failed to install Resource Package on Server <serverName>: <exceptionMessage>

Cause: Deployer is attempting to install the WmDeployerResource package on the server indicated by
<serverName>, but that attempt has failed. The <exceptionMessage> provides more information.
Response: Verify that the server is running, and that there is a working network connection to that server. Be
sure that there is sufficient disk space and memory, and the necessary operating system privileges.

ETD.0004.0632 Deployer could not locate Resource Package: <exceptionMessage>

Cause: An error occurred when the Deployer attempted to locate the WmDeployerResource package. The
<exceptionMessage> provides a guide as to why that attempt failed. The Resource package might not exist on
your Integration Server or more memory may be needed.
Response: Ensure that WmDeployerResource has been installed on the server where you are running the
Deployer. Verify that there is sufficient disk space and memory, and the necessary operating system
privileges.

ETD.0005.0101 WARNING: the target IS is part of a cluster, but is not properly configured to support clustered deployment.
Please see the product documentation for instructions on proper cluster configuration.
Cause: One of the target Integration Servers is not correctly set up for clustering.
Response: See the Integration Server documentation for a description of the proper set up for a clustered
configuration.

ETD.0006.0000 Syntax: -h <host> -p <port> -u <user> -x <password> -e <candidate name> -r <project name> -n <new
candidate name> -s <new candidate description> -b <build name> -m <deployment map name> -l <a string set to either 'true'
or 'false', which turns pre-deployment on/off> -d (turn on debug)
Cause: The command line utility was started with incorrect parameters.
Response: Verify that each of the parameters: host, port, user, password, etc., is correct.

ETD.0006.0118 An exception occurred while attempting to put Package: <sourcePackageName> into the inbound directory.
The error message follows: <message>
Cause: There might be problems with the network connectivity between the Deployer and each target
Integration Server. Alternatively, the target Integration Server might not currently be running.
Response: Verify the network connectivity between the Deployer server and each target server. Also, verify
that the target Integration Servers are running.

202 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0006.0142 While attempting to deploy Port: <sourcePortName>, one of the Port configuration fields was found to be
invalid. Details follow: <detailMessage>
Cause: For information about the cause, see the error message(s) that follow. These will be error messages with
error codes ETD0006.0352 - ETD0006.0384.
Response: To determine the action to take to resolve the problem, see the error message(s) that follow. These
will be error messages with error codes ETD0006.0352 - ETD0006.0384.

ETD.0006.0156 The Package to be deployed, <sourcePackageName>, was not found in the build zip file: <connectionObject>.
Cause: Deployer invoked the wm.server.util:putPackageFile service, and the putPackageFile service returned
an error.
Response: See the Deploy or Simulation Report to determine the error that the putPackageField service
returned. Look up the error messages associated with the error to determine the action to take.

ETD.0006.0157 The Package to be deployed, <sourcePackageName>, was not found in the build zip file: <buildFilePath>.
Cause: The specified package was not found in the build. Typically this indicates that the deployment set is not
current with the build.
Response: Recreate your deployment set and build files.

ETD.0006.0160 An exception occurred while attempting to install Package: <sourcePackageName>. The error message
follows: <exceptionInfo>.
Cause: Deployer invoked the pub.packages:installPackage service, and the installPackage service returned an
error.
Response: Verify the network connectivity between the Deployer server and each target server. Also, verify
that the target Integration Servers are running. For more information about the error that the installPackage
service returned, see the Deploy or Simulation report. For more information about the installPackage service,
see the "webMethods Integration Server Built-in Services Reference."

ETD.0006.0161 The number of bytes read from Package: <sourcePackageName> was not correct.
Cause: An I/O exception occurred when reading the specified package. As a result, all data from the specified
package could not be read. The exception can occur for the following reasons:

- The I/O operation failed or was interrupted while accessing the build file

- A security violation has occurred, which typically means that the user running the Deployer does not have
correct privileges to access the files.
Response: Verify that the file system and the build file that contains the source package are not corrupt. Also
verify that the user attempting this action has the proper authority to read files on the file system. You might
need to recreate the build.

webMethods Error Message Reference Version 6.5 and 6.5.1 203

CHAPTER 2 webMethods Deployer

ETD.0006.0164 The scheduled-service type:<type> for service name: <serviceName> is unknown, and could not be
processed.
Cause: The scheduled service type is unknown, which indicates that your version of the Deployer is out of
date.
Response: Ensure that you have the latest version of the WmDeployer package.

ETD.0006.0199 Deployment failed. Please see the Deployment Report for details. There may also be information in the IS log.
Cause: The deployment failed. For more information, see the Deployment report and the Integration Server
log.
Response: See the Deployment report and Integration Server log to determine the cause of the failure, then take
the appropriate action.

ETD.0006.0204 An error occurred while attempting to import: <TNObjectType> with a name: <typeName; error information
from Trading Networks follows. class: <TNErrorClass>, message: <TNMessage>
Cause: An error occurred attempting to import one of the following TN object types: Document Attributes,
Document Types, Field Groups, ID Types, Contact Types, Binary Types, or Profile Groups. Possible causes
include:

- An error occurred with the network connection between the Deployer server and the target Integration
Server.

- The target Integration Server is not running.

- The target WmTN package on the target Integration Server is not loaded and/or enabled.

- There could be problems with the TN object type that is being imported to the target.
Response: Verify the following:

- There are no errors with the network connectivity between the Deployer server and each target Integration
Server.

- All target Integration Servers are running.

- The WmTN package on each target Integration Server is loaded and enabled.

- The TN object type is allowed. See the "webMethods Trading Networks User's Guide" for details about
allowable TN object types.

204 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0006.0236 Could not resume the listener: <sourcePortName> associated with package: <packageName>. Error message
follows: <ISErrorMessage>"
Cause: Deployer was could not enable the specified listener.
Response: See the "webMethods Integration Server Administrator's Guide" for the specific requirements
needed to enable a listener.

ETD.0006.0240 Could not suspend the triggers. Error message follows: <ISErrorMessage>
Cause: Deployer could not suspend the triggers on the target Integration Server. Deployer attempts to suspend
all triggers by setting the maximum percent of document retrieval threads and the maximum percent of
trigger execution threads to zero.
Response: Verify the network connectivity between the Deployer server and each target Integration Server.
Also, verify that the target Integration Servers are running. For more information about the configuration
settings for document retrieval threads and trigger execution threads, see information about configuring the
server in the "webMethods Integration Server Administrator's Guide."

ETD.0006.0242 Could not resume the triggers. Error message follows: <ISErrorMessage>
Cause: Deployer could not resume the triggers on the target Integration Server. Deployer attempts to resume
all triggers by resetting the maximum percent of document retrieval threads and the maximum percent of
trigger execution threads to the values they had before Deployer suspended the triggers.
Response: Verify the network connectivity between the Deployer server and each target Integration Server.
Also, verify that the target Integration Servers are running. For more information about the configuration
settings for document retrieval threads and trigger execution threads, see information about configuring the
server in the "webMethods Integration Server Administrator's Guide."

ETD.0006.0243 Deployment Set: "<deploymentSet>" contains the following unsatisfied dependencies: <dependencies>. That
Deployment Set was not deployed.
Cause: The dependencies required by the specified deployment set are missing on the target system.
Response: Either install the necessary components on the target system, or change the Deployer project so that
it no longer requires the missing dependencies.

ETD.0006.0250 Simulation failed. Please see the Simulation Audit Report for details. There may also be information in the IS
log.
Cause: The simulation of deployment failed. For the reason(s), see the simulation audit report and the
Integration Server log.
Response: See the report and Integration Server log to determine the cause of the failure; then take the
appropriate action.

webMethods Error Message Reference Version 6.5 and 6.5.1 205

CHAPTER 2 webMethods Deployer

ETD.0006.0263 An error occurred while attempting to import processing rules; error information from Trading Networks
follows. class: <TNErrorClass>, message: <TNMessage>
Cause: An error occurred when attempting to import processing rules into Trading Networks. Possible causes
include:

- An error in the network connection between the Deployer server and the target Integration Server that is
running Trading Networks.

- The target Integration Server is not running.

- The WmTN package is not loaded and/or enabled on the target Integration Server.

- The Trading Networks object type that is being imported to the target might be in error.
Response: Verify the following:

- There are no errors with the network connectivity between the Deployer server and each target Integration
Server.

- All target Integration Servers are running.

- The WmTN package on each target Integration Server is loaded and enabled.

- The TN object type is allowed. See the "webMethods Trading Networks User's Guide" for details about
allowable processing rules.

ETD.0006.0265 An error occurred while attempting to import: <importedTNFieldGroup> with a group code: <groupCode>,
and a name: <importedKey>; error information from Trading Networks follows. class: <TNErrorClass>, message:
<TNMessage>
Cause: An error occurred when attempting to import field groups into Trading Networks. Possible causes
include:

- An error in the network connection between the Deployer server and the target Integration Server that is
running Trading Networks.

- The target Integration Server is not running.

- The WmTN package is not loaded and/or enabled on the target Integration Server.

- The Trading Networks object type that is being imported to the target might be in error.

206 webMethods Error Message Reference Version 6.5 and 6.5.1

Response: Verify the following:

- There are no errors with the network connectivity between the Deployer server and each target Integration
Server.

- All target Integration Servers are running.

- The WmTN package on each target Integration Server is loaded and enabled.

- The TN object type is allowed. See the "webMethods Trading Networks User's Guide" for details about
allowable field groups.

ETD.0006.0266 An error occurred while attempting to import field definitions; error information from Trading Networks
follows. class: <TNErrorClass>, message: <TNMessage>
Cause: An error occurred when attempting to import field definitions into Trading Networks. Possible causes
include:

- An error in the network connection between the Deployer server and the target Integration Server that is
running Trading Networks.

- The target Integration Server is not running.

- The WmTN package is not loaded and/or enabled on the target Integration Server.

- The Trading Networks object type that is being imported to the target might be in error.
Response: Verify the following:

- There are no errors with the network connectivity between the Deployer server and each target Integration
Server.

- All target Integration Servers are running.

- The WmTN package on each target Integration Server is loaded and enabled.

- The TN object type is allowed. See the "webMethods Trading Networks User's Guide" for details about
allowable field definitions.

ETD.0006.0270 An error occurred while attempting to import partner profiles; error information from Trading Networks
follows. class: <TNErrorClass>, message: <TNMessage>
Cause: An error occurred when attempting to import partner profiles into Trading Networks. Possible causes
include:

- An error in the network connection between the Deployer server and the target Integration Server that is
running Trading Networks.

webMethods Error Message Reference Version 6.5 and 6.5.1 207

CHAPTER 2 webMethods Deployer

- The target Integration Server is not running.

- The WmTN package is not loaded and/or enabled on the target Integration Server.

- The Trading Networks object type that is being imported to the target might be in error.
Response: Verify the following:

- There are no errors with the network connectivity between the Deployer server and each target Integration
Server.

- All target Integration Servers are running.

- The WmTN package on each target Integration Server is loaded and enabled.

- The TN object type is allowed. See the "webMethods Trading Networks User's Guide" for details about
allowable partner profiles.

ETD.0006.0274 An error occurred while attempting to import trading partner agreements; error information from Trading
Networks follows. class: <TNErrorClass>, message: <TNMessage>
Cause: An error occurred when attempting to import trading partner agreements (TPAs) into Trading
Networks. Possible causes include:

- An error in the network connection between the Deployer server and the target Integration Server that is
running Trading Networks.

- The target Integration Server is not running.

- The WmTN package is not loaded and/or enabled on the target Integration Server.

- The Trading Networks object type that is being imported to the target might be in error.
Response: Verify the following:

- There are no errors with the network connectivity between the Deployer server and each target Integration
Server.

- All target Integration Servers are running.

- The WmTN package on each target Integration Server is loaded and enabled.

- The TN object type is allowed. See the "webMethods Trading Networks User's Guide" for details about
allowable trading partner agreements (TPAs).

208 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0006.0277 An error occurred while attempting to import: <importedTNObjectType> with a type code: <typeCode>, and a
name: <importedObjectName>; error information from Trading Networks follows. class: <TNErrorClass>, message:
<TNMessage>

Cause: An error occurred when attempting to import external ID types, contact types, or binary types into
Trading Networks. Possible causes include:

- An error in the network connection between the Deployer server and the target Integration Server that is
running Trading Networks.

- The target Integration Server is not running.

- The WmTN package is not loaded and/or enabled on the target Integration Server.

- The Trading Networks object type that is being imported to the target might be in error.
Response: Verify the following:

- There are no errors with the network connectivity between the Deployer server and each target Integration
Server.

- All target Integration Servers are running.

- The WmTN package on each target Integration Server is loaded and enabled.

- The TN object type is allowed. See the "webMethods Trading Networks User's Guide" for details about
allowable external ID types, contact types, and binary types.

ETD.0006.0296 The <ACLName>, which is required for source package: <sourcePackageName>, has not been deployed, and
it does not already exist at the target. Although the source package would be deployed to the target, some services in that
package will not run correctly until that ACL is created at the target.
Cause: The Read, Write, List, or Execute ACL(s) that are necessary for the deployed package to run correctly
are not being deployed to the target Integration Server and that ACL does not already exist on the target
Integration Server. Typically this indicates that the ACL(s) that are associated with the package were not
extracted.
Response: Perform the extraction step again using the Deployer to ensure that all ACLs are included.

webMethods Error Message Reference Version 6.5 and 6.5.1 209

CHAPTER 2 webMethods Deployer

ETD.0006.0297 The Read/Write/List/Execute ACL: <ACLName>, which is required for source package:
<sourcePackageName>, has not been deployed, and it does not already exist at the target. Some services in that source
package will not run correctly until that ACL is created at the target.
Cause: The Read, Write, List, or Execute ACL(s) that are necessary for the deployed package to run correctly
are not being deployed to the target Integration Server and that ACL does not already exist on the target
Integration Server. Typically this indicates that the ACL(s) that are associated with the package were not
extracted.
Response: Perform the extraction step again using the Deployer to ensure that all ACLs are included.

ETD.0006.0304 The following target server is not currently available: <targetServerAlias>; skipping that server. Please check
your network connection, and verify that the target server is running.
Cause: Deployer could not connect to the specified target server.
Response: Verify the following:

- Network connectivity between the Deployer server and each target Integration Server.

- The target Integration Servers are running.

- The target Integration Server alias is defined on the Deployer server.

ETD.0006.0305 <BR><BR>An exception occurred getting a Trading Networks, TN, docType object. That is most likely caused
by a user-defined extension to the TN type BizDocType. Please copy the jar file(s), which should be found in the <webM
install dir>\\IntegrationServer\\packages\\WmTN\\code\\jars directory, containing those extensions into the
WmDeployer/code/jars directory.
Cause: There is a user-defined extension to a TN document type, and Deployer does not have access to the
associated jar file(s).
Response: To ensure Deployer has access to the associated jar file(s), copy the jar file(s) located in the
<serverDirectory>\packages\WmTN\code\jars directory (which contain the TN document type extensions)
to the <serverDirectory>\packages\WmDeployer\code\jars directory.

ETD.0006.0306 An error occurred while attempting to import extended field definitions; error information from Trading
Networks follows. class: <TNErrorClass>, message: <TNMessage>
Cause: An error occurred when attempting to import extended field definitions into Trading Networks.
Possible causes include:

- An error in the network connection between the Deployer server and the target Integration Server that is
running Trading Networks.

- The target Integration Server is not running.

- The WmTN package is not loaded and/or enabled on the target Integration Server.

210 webMethods Error Message Reference Version 6.5 and 6.5.1

- The Trading Networks object type that is being imported to the target might be in error.
Response: Verify the following:

- There are no errors with the network connectivity between the Deployer server and each target Integration
Server.

- All target Integration Servers are running.

- The WmTN package on each target Integration Server is loaded and enabled.

- The TN object type is allowed. See the "webMethods Trading Networks User's Guide" for details about
allowable extended field definitions.

ETD.0006.0307 An error occurred while attempting to import security data for profile: <profileName>; error information from
Trading Networks follows. class: <TNErrorClass>, message: <TNMessage>
Cause: An error occurred when attempting to import the security data for the specified profile into Trading
Networks. Possible causes include:

- An error in the network connection between the Deployer server and the target Integration Server that is
running Trading Networks.

- The target Integration Server is not running.

- The WmTN package is not loaded and/or enabled on the target Integration Server.

- The Trading Networks object type that is being imported to the target might be in error.
Response: Verify the following:

- There are no errors with the network connectivity between the Deployer server and each target Integration
Server.

- All target Integration Servers are running.

- The WmTN package on each target Integration Server is loaded and enabled.

- The TN object type is allowed. See the "webMethods Trading Networks User's Guide" for details about
allowable Trading Networks Security Data.

webMethods Error Message Reference Version 6.5 and 6.5.1 211

CHAPTER 2 webMethods Deployer

ETD.0006.0308 An error occurred while attempting to import queues; error information from Trading Networks follows.
class: <TNErrorClass>, message: <TNMessage>
Cause: An error occurred when attempting to import the public queues into Trading Networks. Possible causes
include:

- An error in the network connection between the Deployer server and the target Integration Server that is
running Trading Networks.

- The target Integration Server is not running.

- The WmTN package is not loaded and/or enabled on the target Integration Server.

- The Trading Networks object type that is being imported to the target might be in error.
Response: Verify the following:

- There are no errors with the network connectivity between the Deployer server and each target Integration
Server.

- All target Integration Servers are running.

- The WmTN package on each target Integration Server is loaded and enabled.

- The TN object type is allowed. See the "webMethods Trading Networks User's Guide" for details about
allowable public queues.

ETD.0006.0309 An error occurred while attempting to import profile group with name: <importedKey>, and value:
<profileGroupValue>; error information from Trading Networks follows. class: <TNErrorClass>, message: <TNMessage>
Cause: An error occurred when attempting to import the profile groups into Trading Networks. Possible
causes include:

- An error in the network connection between the Deployer server and the target Integration Server that is
running Trading Networks.

- The target Integration Server is not running.

- The WmTN package is not loaded and/or enabled on the target Integration Server.

- The Trading Networks object type that is being imported to the target might be in error.

212 webMethods Error Message Reference Version 6.5 and 6.5.1

Response: Verify the following:

- There are no errors with the network connectivity between the Deployer server and each target Integration
Server.

- All target Integration Servers are running.

- The WmTN package on each target Integration Server is loaded and enabled.

- The TN object type is allowed. See the "webMethods Trading Networks User's Guide" for details about
allowable profile groups.

ETD.0006.0326 An error occurred while deploying Package: <packageName>. Item <itemNotLoaded> could not be loaded
because of reason <reasonFromIS>. Note, the package may have partially loaded; please check your target server.
Cause: The specified package did not load due to the reason returned from the target Integration Server.
Response: See the "webMethods Integration Server Administrator's Guide" for the specific requirements
needed to load a package.

ETD.0006.0328 The target JVM: <targetISJVMVersion> is older than the JVM recommended:
<sourcePackageRecommendedJVMVersion> on the source for package <sourcePackageName>.
Cause: The JVM version at the target is older that the minimum JVM version property that is specified as
required by the source.
Response: Change the minimum JVM property for the package being deployed, and then deploy again.

ETD.0006.0329 The target JVM: <targetISJVMVersion> is older than the JVM recommended:
<sourcePackageRecommendedJVMVersion> on the source for package: <sourcePackageName>.
Cause: The JVM version at the target is older that the minimum JVM version property that is specified as
required by the source.
Response: Change the minimum JVM property for the package being deployed, and then deploy again.

ETD.0006.0337 An error occurred while deploying package: <packageName>; error message follows. <ISErrorMessage>
Cause: Deployer invoked the pub.packages:installPackage service, and the installPackage service returned an
error.
Response: For more information about the error that the installPackage service returned, see the Deploy or
Simulation report. For more information about the installPackage service, see the "webMethods Integration
Server Built-in Services Reference." For more information about the requirements for installing a packages, see
the "webMethods Integration Server Administrator's Guide."

webMethods Error Message Reference Version 6.5 and 6.5.1 213

CHAPTER 2 webMethods Deployer

ETD.0006.0338 An exception occurred while attempting to activate Package: <sourcePackageName>; error message follows:
Cause: Deployer invoked the pub.packages:activatePackage service, and the activatePackage service returned
an error.
Response: Verify the network connectivity between the Deployer server and each target Integration Server.
Also, verify that the target Integration Servers are and running. For more information about the error that the
activatePackage service returned, see the Deploy or Simulation report. For more information about the
activatePackage service, see the "webMethods Integration Server Built-in Services Reference."

ETD.0006.0352 Package value: <sourcePackageName> contained invalid character: <firstIllegalCharacter>. Refer to the
"webMethods Integration Server Administrator's Guide" for listed illegal characters.
Cause: The package name contains illegal characters.
Response: See the "webMethods Integration Server Administrator's Guide" for information about how to name
a package.

ETD.0006.0353 Invalid Cleanup File Age: <cleanUpFileAge>. Valid values are 1-9999.
Cause: The value specified for the Cleanup File Age is not between 1 and 9999.
Response: Specify a valid value for the Cleanup File Age.

ETD.0006.0354 Invalid File Age Interval: <fileAge>. Valid values are 1-9999.
Cause: The value specified for the File Age Interval is not between 1 and 9999.
Response: Specify a valid value for the File Age Interval.

ETD.0006.0355 The Recursive value: <recursiveValue> is invalid; valid values are 'yes', and 'no'.
Cause: The specified Recursive value is neither "yes" nor "no".
Response: Specify either "yes" or "no" for the Recursive value.

ETD.0006.0356 The Run User value: <runUser> contained invalid character: <firstIllegalCharacter>. Refer to the
"webMethods Integration Server Administrator's Guide" for listed illegal characters.
Cause: The Run User value contains illegal characters.
Response: See the "webMethods Integration Server Administrator's Guide" for information about legal Run
User values.

ETD.0006.0357 No value provided for the 'Run services as user' field; that is a required field.
Cause: The 'Run service as user' field has not been set.
Response: Specify a value for the 'Run service as user' field. See the "webMethods Integration Server
Administrator's Guide" for information about legal Run User values.

214 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0006.0358 Invalid File Polling Interval: <filePollingInterval>. Valid values are 1-9999.
Cause: The value specified for the File Polling Interval is not between 1 and 9999.
Response: Specify a valid value for the File Polling Interval.

ETD.0006.0359 No value provided for the File Polling Interval. Valid values are 1-9999.
Cause: The File Polling Interval has not been set.
Response: Specify a value from 1 through 9999 for the File Polling Interval.

ETD.0006.0360 Invalid Cleanup Interval: <cleanUpInterval>. Valid values are 1-9999.

Cause: The value specified for the Cleanup Interval is not between 1 and 9999.
Response: Specify a valid value for the Cleanup Interval.

ETD.0006.0361 Invalid Maximum Number of Invocation Threads: <maxThreads>. Valid values are 1-10.
Cause: The value specified for the Maximum Number of Invocation Threads is not between 1 and 10.
Response: Specify a valid value for the Maximum Number of Invocation Threads.

ETD.0006.0362 No value provided for the Maximum Number of Invocation Threads Interval. Valid values are 1-10.
Cause: The Maximum Number of Invocation Threads was not set.
Response: Specify a value from 1 through 10 for the Maximum Number of Invocation Threads.

ETD.0006.0363 Port value: <portAsString> is not an integer type.

Cause: The value specified for the port is not an integer type.
Response: Specify a valid value for the port.

ETD.0006.0364 Port value: <port> must be greater than -1.

Cause: The value for the port is not valid.
Response: Specify a valid value for the port.

ETD.0006.0365 No port value provided. A number must be provided for the port value.
Cause: The value for the port has not been set.
Response: Specify a valid integer type value that is greater than -1 for the port.

webMethods Error Message Reference Version 6.5 and 6.5.1 215

CHAPTER 2 webMethods Deployer

ETD.0006.0366 The Need Client Authorization value: <needClientAuthorization> is invalid. Valid values are 'true', or 'false'.
Cause: The specified 'Need Client Authorization' value is neither "true" nor "false".
Response: Specify either "true" or "false" for the 'Need Client Authorization' value.

ETD.0006.0367 A host value is required.

Cause: The value for host has not been set.
Response: Specify a value for the host.

ETD.0006.0368 The type value: <emailPortType> is invalid; it should be either 'pop3' or 'imap'.
Cause: The port type is neither "pop3" nor "imap".
Response: Specify either "pop3" or "imap" for the port type.

ETD.0006.0369 The 'type' value was not set. Valid values are 'pop3' or 'imap'.
Cause: The port type has not be set.
Response: Specify either "pop3" or "imap" for the port type.

ETD.0006.0370 The User value: <user> contained invalid character: <firstIllegalCharInUser>. Refer to the "webMethods
Integration Server Administrator's Guide" for listed illegal characters.
Cause: The User value contains illegal characters.
Response: See the "webMethods Integration Server Administrator's Guide" for information about legal
characters for user accounts.

ETD.0006.0371 No value provided for User; that is a required field.

Cause: The User value has not been set.
Response: Specify a value for User. See the "webMethods Integration Server Administrator's Guide" for
information about legal characters for user accounts.

ETD.0006.0372 The Logout value: <logoutString> is invalid; valid values are 'yes', and 'no'.
Cause: The specified Logout value is neither "yes" nor "no".
Response: Specify either "yes" or "no" for the Logout value.

ETD.0006.0373 The Authorize value: <authorizeString> is invalid; valid values are 'yes', and 'no'.
Cause: The specified Authorize value is neither "yes" nor "no".
Response: Specify either "yes" or "no" for the Authorize value.

216 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0006.0374 Invalid Time Interval: <interval>. Valid values 1-9999.
Cause: The value specified for the Time Interval is not between 1 and 9999.
Response: Specify a valid value for the Time Interval.

ETD.0006.0375 No Time Interval provided, valid values 1-9999.

Cause: The Time Interval has not been set.
Response: Specify a value from 1 through 9999 for the Time Interval.

ETD.0006.0376 The Reply value: <replyString> is invalid; valid values are 'yes', and 'no'.
Cause: The specified Reply value is neither "yes" nor "no".
Response: Specify either "yes" or "no" for the Reply value.

ETD.0006.0377 The Reply On Error value: <replyOnErrorString> is invalid; valid values are 'yes', and 'no'.
Cause: The specified Reply On Error value is neither "yes" nor "no".
Response: Specify either "yes" or "no" for the Reply On Error value.

ETD.0006.0378 The Remove value: <removeString> is invalid; valid values are 'yes', and 'no'.
Cause: The specified Remove value is neither "yes" nor "no".
Response: Specify either "yes" or "no" for the Remove value.

ETD.0006.0379 The Bad Remove value: <badRemoveString> is invalid; valid values are 'yes', and 'no'.
Cause: The specified Bad Remove value is neither "yes" nor "no".
Response: Specify either "yes" or "no" for the Bad Remove value.

ETD.0006.0380 The Multithread value: <multiThreadString> is invalid; valid values are 'yes', and 'no'.
Cause: The specified Multithread value is neither "yes" nor "no".
Response: Specify either "yes" or "no" for the Multithread value.

ETD.0006.0381 Invalid Number of Threads: <numThreadsString>. Valid values are 1-99.

Cause: The value specified for the Number of Threads is not between 1 and 99.
Response: Specify a valid value for the Number of Threads.

webMethods Error Message Reference Version 6.5 and 6.5.1 217

CHAPTER 2 webMethods Deployer

ETD.0006.0382 No Number of Threads provided. Valid values are 1-99.

Cause: The Number of Threads has not been set.
Response: Specify a value from 1 through 99 for the Number of Threads.

ETD.0006.0383 The Break Mmsg value: <breakMmsgString> is invalid; valid values are 'yes', and 'no'.
Cause: The specified Break Mmsg value is neither "yes" nor "no".
Response: Specify either "yes" or "no" for the Break Mmsg value.

ETD.0006.0384 The Include Headers : <includeHeadersString> is invalid; valid values are 'yes', and 'no'.
Cause: The specified Include Headers value is neither "yes" nor "no".
Response: Specify either "yes" or "no" for the Include Headers value.

ETD.0006.0419 A SOAP fault occurred while performing a remote invoke of the service: <ISServiceName>. The SOAP Fault
string follows: <faultString>
Cause: A failure occurred invoking an Integration Server service via SOAP.
Response: Verify the network connectivity between the Deployer server, and each target Integration Server.
Also, verify that the target Integration Servers are running.

ETD.0006.0421 Unknown system type: <sourceSystemType>.

Cause: The source system type is unknown, which implies that your version of the Deployer is out of date.
Response: Ensure that you have the latest version of the WmDeployer package.

ETD.0006.0422 The connection object is of an unknown type. Its toString() value is: <targetConnectionObject>. Thus, we
cannot invoke <ISServiceName>.
Cause: The system type object was set to a value that the code did not recognize. That can only occur if the user
has manually edited the project file XML.
Response: Do the build and map steps again; do not manually edit the project file.

218 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0006.0423 Exception occurred writing the bytes for package: <sourcePackageName> to the output stream in
preparation to put it to the target: <connectionObject>.
Cause: An exception occurred when the Deployer tried to write the package data to disk. That exception can
occur for the following reasons:

- The I/O operation failed or was interrupted while accessing the build file

- A security violation has occurred, which typically means that the user running the Deployer does not have
correct privileges to access the files.
Response: Verify that the file system is not corrupt and that adequate disk space is available for writing new
files. Also verify that the user has proper privileges to write files on the file system.

ETD.0006.0501 ERROR: Failed to load VarSub object. The following exception was thrown: <exceptionInfo>
Cause: The map file:
<serverDirectory>\packages\WmDeployer\persist\projects\<projectName>\targets\<mapName>\<deploy
mentSetName>_<targetServerName>.xml is either corrupt or not present.
Response: Verify that the map file exists. If it does, you might need to use Deployer to recreate your map and
variable substitution actions.

ETD.0006.0505 ERROR: Failed to generate IData for Port. The following exception was thrown: <exceptionInfo>.
Cause: The port type is unknown. This indicates that your version of the Deployer is out of date.
Response: Ensure that you have the latest version of the WmDeployer package.

ETD.0006.0600 IS version for the target is <ISVersion>, which is less than 6.1. The following adapter connection(s) will not be
updated with their variable substitution values: <adapterConnections>
Cause: The version of the target Integration Server is a version prior to version 6.1. Versions of the Integration
Server prior to 6.1 do not support the APIs that are required to update the Adapter connections.
Response: Either upgrade the target Integration Server to version 6.1 or later, or manually update the Adapter
connections on the target system.

webMethods Error Message Reference Version 6.5 and 6.5.1 219

CHAPTER 2 webMethods Deployer

ETD.0006.1003 An IO exception occurred while attempting to access: <deployReportFileName>. Exception details follow:
<exceptionInfo>.
Cause: An exception occurred when the Deployer tried to create, write data to, or save a file. That exception can
occur for the following reasons:

- The I/O operation failed or was interrupted while accessing the build file.

- A security violation has occurred, which typically means that the user running the Deployer does not have
correct privileges to access the files.
Response: Verify that the file system is not corrupt and that adequate disk space is available for creating,
writing, and/or saving new files. Also verify that the user has proper privileges to create, write, and save files
on the file system.

ETD.0006.1004 An exception occurred while attempting to access <object>. Exception details follow: <exceptionInfo>.
Cause: An exception occurred when Deployer tried to access (that is, create, save, read, or load) the indicated
<object>, where <object> is one of thte following: checkpoint, deployment, build, deployReport,
targetFileName, or targetServer.

Possible causes of the exception include the following:

- The deployment, reportFiles, or targetFile Object could not be loaded from the file system.

- An I/O operation failed or was interrupted while accessing the build or checkpoint file.

- A security violation has occurred, which typically means that the user running the Deployer does not have
privileges to access files necessary to perform the deploy.

- A target Integration Server Adapter and/or Trigger could not be suspended/resumed.

- A variable substitution failed.

- The deployer could not obtain a connection to a target server.

Response: Verify the following:

- The file system is not corrupt.

- Adequate disk space is available for creating and/or saving new files.

- The user attempting this action has the proper authority to create and save files on the file system.

- The target server is running, and is reachable on the network.

220 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0006.1005 You are not authorized to deploy the <projectFileName> project.
Cause: The logged in user does not have the authorization to deploy the specified project.
Response: Ask an administrator or user that has deploy authorization to perform the action for you.
Alternatively, have an administrator update the your authorization to assign you deploy authorization for the
project.

ETD.0006.1006 You are not authorized to deploy the <projectFileName> project; error message follows: <exceptionInfo>.
Cause: An error occurred when invoking the service on the Deployer's Integration Server to determine whether
the user is authorized to deploy the specified project.
Response: Verify the Deployer Integration Server is still running. If you are running the Deployer from a
remote location, verify the network connectivity between the Deployer user interface and the server.

ETD.0006.1007 An exception occurred while attempting to process <subMessage>. Exception details follow:
<exceptionInfo>.
Cause: In the message, <subMessage> is one of the following sub-messages that Deployer displays to provide
additional information about the exception:

- An exception occurred while performing a [remote] invoke of the service: <ISServiceName>. Exception
details follow: <exceptionInfo>

- An exception occurred while attempting to XMLDecode the file: <buildFileName>. Exception details follow:
<exceptionInfo>.

- An exception occurred getting a Trading Networks, TN, docType object. That is most likely caused by a user-
defined extension to the TN type BizDocType. Please copy the jar file(s), which should be found in the <webM
install dir>\\IntegrationServer\\packages\\WmTN\\code\\jars directory, containing those extensions into
the WmDeployer/code/jars directory.

- Source package is of type upgrade and required target package version is null.

- Error: no Logical Server for Server ID" The most-likely fix for that is to use webMethods Administrator on
your target server to define a logical server with the name: <sourceSystemName>.

- An Exception occurred while attempting to IDataBinCoder the file: '<buildFileName>'. Exception details
follow: <exceptionInfo>

- Overwrite 'everything else' field is set to <overwriteEverythingElseString>, which is invalid.

webMethods Error Message Reference Version 6.5 and 6.5.1 221

CHAPTER 2 webMethods Deployer

- The Port: <sourcePortName>, associated with Package: <packageName>

- Disabling of the Port: <sourcePortName>, associated with Package: <packageName>

- Enabling of the Port: <sourcePortName>, associated with Package: <packageName>

- Resuming the scheduled-service: " + scheduledServiceName

- Suspending the scheduled-service: " + scheduledServiceName

- A SOAP fault occurred while performing a remote invoke of the service: <ISServiceName>.The SOAP Fault
string follows: <faultString>

- Getting information about the Port: <sourcePortName>, associated with Package: <packageName>

The reason for the exception can be one of the following:

1. There is a problem with connectivity to the target Integration Server.

2. The target Integration Server is not running.

3. The target Integration Server requires a Broker Server, but no Broker Server is connected to it.

4. There is a user-defined extension to a TN document type, and Deployer does not have access to the
associated jar file(s).

5. You specified a partial package for deployment; however, the package does not exist on the target.

6. You specified a logical server that is not defined on the target.

7. The overwrite flag is invalid, which can only occur if the build file was manually edited.
Response: Based on the reason for the exception, perform one of the following:

1. Verify the network connectivity between the Deployer server and each target server.

2. Verify that each target server is running.

3. If the target Integration Server requires a Broker connected to it, ensure that a Broker is connected.

4. If a user-defined TN document type is in use, ensure Deployer has access to the associated jar file(s). To do
so copy the jar file(s) located in the <serverDirectory>\packages\WmTN\code\jars directory (which contain
the TN document type extensions) to the <serverDirectory>\packages\WmDeployer\code\jars directory.

5. If you specified a partial package and the package does not exist on the target, either remove the package

222 webMethods Error Message Reference Version 6.5 and 6.5.1

from the deployment or specify a full package for deployment.

6. If the definition of a logical server is missing, use webMethods Administrator on your target server to define
a logical server with the name indicated in the error message.

7. If the overwrite flag is invalid, ensure that your build file has not been manually edited.

ETD.0006.1008 The deploy report: <deployReportFileName> already exists. Please move it to a different directory.
Cause: The deploy report already exists.
Response: Move the existing deploy report file to a different directory.

ETD.0006.1009 Cannot connect to server "<server>". Exception details follow: "<exception>"

Cause: The command line utility could not connect to the Integration Server.
Response: Make sure that you passed the correct server host name, port number, user name, and password to
the command line utility.

ETD.0006.1014 An exception occurred while attempting to close the file <buildFileName>; that will not affect deployment, but
will keep a lock on that file. Exception details follow: <exceptionInfo>
Cause: The build file could not be closed because an I/O exception occurred. The exception can occur for the
following reasons:

- The I/O operation failed or was interrupted while accessing the build file.

- A security violation has occurred, which typically means that the user running the Deployer does not have
correct privileges to access the files.
Response: Verify that the file system is not corrupt and that adequate disk space is available for saving new
files. Also verify that the user attempting this action has proper privileges to save files on the file system.

ETD.0006.1015 Overwrite 'everything else' field is set to <theUnknownOverwriteValueAsAString>, which is invalid.

Cause: The overwrite flag was set to a value that the code did not recognize. That can only occur if the user has
manually edited the XML in the target file.
Response: Do the build and map steps again; do not manually edit the target file.

ETD.0006.1019 Could not invoke service <exception>.

Cause: The service could not be invoked because of an error.
Response: Review the exception to determine the problem.

webMethods Error Message Reference Version 6.5 and 6.5.1 223

CHAPTER 2 webMethods Deployer

ETD.0007.0001 Server <serverName> already exists.

Cause: You specified a name for a plug-in server; however, a plug-in with that name already exists. Deployer
requires that plug-in servers be uniquely named.
Response: Specify a unique name for the plug-in server.

ETD.0007.0002 Server <serverName> does not exist.

Cause: The specified plug-in server does not exist in the Deployer configuration. The plug-in server might have
been deleted by another Deployer session.
Response: Verify that the specified plug-in server exists in the plug-in server list. If it does not, re-add this
server.

ETD.0007.0005 Error invoking service <serviceName>.

Cause: Deployer was unable to invoke a required Integration Server service. This usually indicates a problem
with the Integration Server installation.
Response: On the local Deployer server, determine whether a required Integration Server package is disabled,
missing, or whether parts are missing. Check for the following packages: WmDeployer, WmAdmin, WmRoot,
or possibly WmDeployerResource or WmModeler.

ETD.0007.0006 Error invoking getConnectionInfo for system <serverName>: <errorMsg>

Cause: Deployer was unable to retrieve logical server connection information from the source server. The
source server might not be running or the logon credentials might be incorrect.
Response: Verify that the specified source server is running. Verify that the logon credentials in the plug-in
server configuration, including the Port value, are correct.

ETD.0007.0007 Call to getConnectionInfo for system <serverName> returned the following: <status>: <errorMsg>
Cause: Deployer was unable to retrieve logical server connection information from the source server. The
source server might not be running or the logon credentials might be incorrect.
Response: Verify that the specified source server is running. Verify that the logon credentials in the plug-in
server configuration, including the Port value, are correct.

ETD.0007.0008 Call to getConnectionInfo for system <serverName> returned the following missing data: <errorMsg>
Cause: Deployer was unable to retrieve logical server connection information from the source server. The
source server might not be running or the logon credentials might be incorrect.
Response: Verify that the specified source server is running. Verify that the logon credentials in the plug-in
server configuration, including the Port value, are correct.

224 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0007.0009 Error connecting to IS <serverName>: <errorMsg>
Cause: Deployer was unable to connect to the specified remote Integration Server. The Integration Server
might not be running, or the logon credentials might be incorrect.
Response: Verify that the Integration Server is running. Verify that the logon credentials in the Remote Server
configuration, including the Port value, are correct.

ETD.0007.0010 Error remote invoking service <serviceName> on system <serverName>: <errorMsg>

Cause: Deployer was unable to invoke a required Integration Server service. This usually indicates an
incomplete or error with the installation of a plug-in on the remote server.
Response: On the specified remote server, determine whether a required Integration Server package is
disabled, missing, or whether parts are missing. Check for the following packages: WmDeployer, WmAdmin,
WmRoot, or possibly WmDeployerResource or WmModeler.

ETD.0007.0011 Plugin <pluginName> does not exist.

Cause: The specified plug-in is not correctly configured in the Deployer plug-in configuration file. This
indicates an incomplete or damaged installation, or possibly a modification to the plug-in configuration file
located in "<serverDirectory>\packages\WmDeployer\config\plugin" folder.
Response: Verify that a file named <pluginName>.cnf exists in the
"<serverDirectory>\packages\WmDeployer\config\plugin" directory.

ETD.0007.0012 Failed to load configuration file for Server <pluginName>.

Cause: At startup, Deployer could not successfully load the plug-in server configuration file. This indicates the
configuration file has been modified and Deployer can no longer parse the configuration file.
Response: Attempt to delete and then re-add the plug-in server. This should correctly recreate the
configuration file. If this fails, send the contents of the server configuration file, located in
"<serverDirectory>\packages\WmDeployer\config\pluginServer\<pluginName>" to webMethods Customer
Care.

ETD.0007.0013 Plugin <pluginName> does not have a valid Communication Component installation class defined. Plugin
Config file may be corrupt.
Cause: The plugin configuration file provided by webMethods does not contain the entry identifying the class
necessary to remotely install the Communication Component. The configuration file may have been altered
incorrectly.
Response: Re-install the Deployer. Your project data will remain unchanged.

webMethods Error Message Reference Version 6.5 and 6.5.1 225

CHAPTER 2 webMethods Deployer

ETD.0007.0014 Plugin <pluginName> Communication Component installation method failed for Server <serverName>.
Cause: The invocation of the Communication Component Installation class has failed.
Response: Please see the IS Error log for details. Contact webMethods Customer Care if the problem cannot be
resolved locally.

ETD.0007.0015 Could not find Communication Component file <filename>.

Cause: The remote installation of the Communication Component was unable to locate the installable
component file on the file system. Your installation could be damaged or corrupt.
Response: Re-install the Deployer. Your project data will remain unchanged.

ETD.0007.0016 Error installing Communication Component on server <serverName>. Please see system log for additional
details.
Cause: The remote installation of the Communication Component has failed.
Response: Please see the IS Error log for details. Contact webMethods Customer Care if the problem cannot be
resolved locally.

ETD.0007.0018 Failed to ping <pluginName> Plugin Server: <logicalPluginName>.

Cause: Deployer is unable to contact the remote server hosting the identified plugin. The host could be down
or the hostname incorrect.
Response: Verify the hostname (or IP Address) and ensure the system is available.

ETD.0007.0019 <serverName> already has a <logicalPluginName> Server Alias named <logicalName>.

Cause: You have attempted to add a logical plugin server that already exists. Each logical plugin server name
must be unique.
Response: Specify a unique name for the logical plug-in server.

ETD.0007.0021 <logicalPluginName> Server Alias named <logicalName> does not exist.

Cause: The Logical Server Plugin name returned by the plugin does not exist.
Response: Using Deployer, add the identified logical plugin server alias.

ETD.0007.0121 You must define a <logicalPluginName> Logical Server named <systemName> for Plugin Server
<parentSystemName>.
Cause: Deployer could not determine the logical server from the parent server for this server.
Response: Make sure that all of your servers and server aliases are properly defined in Deployer, Integration
Server, and webMethods Administrator.

226 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0007.0245 Communications server is not running. Check the communications server on the settings page.
Cause: The Component Communication Server must be running for the Deployer to communicate with
various plugins.
Response: Check the Deployer Properties page for the status and check the IS Error log for details. You may
simply need to change the port value.

ETD.0008.0100 WARNING: objectKey is NULL

Cause: Deployer invoked the getObjects method with invalid parameters; the input IData object, "objectKey,"
was null. This indicates that Deployer encountered a severe internal error.
Response: Contact webMethods Customer Care. Please have the following information available:

- A copy of the Modeler plug-in configuration files (config/plugin/Modeler.cnf)

- Information about the source Integration Server that is running Modeler and that is associated with the
project: operating system, version of the Integration Server, JVM, and version of WmModeler package

- A copy of the Server Log from the timeframe when the error occurred

ETD.0008.0101 Failed to find meta data for Process Model: "<modelName>".

Cause: Deployer was unable to invoke the getModelMetaData service. As a result, Deployer could not extract
the meta data for the specified process model.
Response: Verify that the correct version of the WmMonitor package is installed on the source machine.

ETD.0008.0102 Failed to encode meta data for Process Model: "<modelName>": <errorMsg>
Cause: An exception was thrown when trying to encode the IData object (that contains the process model
metadata) to XML. This might occur if Deployer encountered a severe internal error, or it might indicate that
the JVM has an unexpected encode/decode version that failed.
Response: Contact webMethods Customer Care. Please have the following information available:

- A copy of the Server Log from the timeframe when the error occurred

webMethods Error Message Reference Version 6.5 and 6.5.1 227

CHAPTER 2 webMethods Deployer

ETD.0008.0104 Failed to encode repoOnly marker for Process Model: "<modelName>": <errorMsg>.
Cause: An exception was thrown when trying to encode the IData object, which contains the process model
metadata, to XML. This could occur if the Modeler repository version is newer than the version that Deployer
supports. This indicates that Deployer encountered a severe internal error.
Response: Contact webMethods Customer Care. Please have the following information available:

- Copy of the Server Log from the timeframe when the error occurred

ETD.0008.0105 No such Process Model: "<modelName>".

Cause: The name of the process model that was passed to the getObjects method is not valid. This process
model does not exist on the source Design Server.
Response: Make sure that the process model specified in your project still exists on the source system.

ETD.0008.0106 No object keys found.

Cause: Deployer invoked the getObjects method with invalid parameters; the input IData object array,
"objectKeys," was null. This indicates that Deployer encountered a severe internal error.
Response: Contact webMethods Customer Care. Please have the following information available:

- A copy of the Server Log from the timeframe when the error occurred

ETD.0008.0107 No WmMonitor package. Cannot build model.

Cause: The WmMonitor package is disabled or is not present on the source server.
Response: Install the correct version of the WmMonitor package, and ensure that it is enabled on the source
server.

ETD.0008.0109 Error from isValidModel: <modelName>

Cause: Private method isValidModel threw an exception.
Response: Check exception message and take appropriate action.

228 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0008.0115 Missing objectKey is NULL. Cannot Deploy.
Cause: Deployer invoked the deployObjects method with invalid parameters; the input IData object, "key," was
null. This indicates that Deployer encountered a severe internal error.
Response: Contact webMethods Customer Care. Please have the following information available:

- A copy of the Server Log from the timeframe when the error occurred

ETD.0008.0116 While decoding the meta data for Process Model: "<modelName>": <errorMsg>
Cause: An exception was thrown when trying to decode the XML encoded IData that contains the process
model metadata.
Response: Verify that the XML encoded IData file (contained in the project) is not corrupted.

ETD.0008.0118 The version of the Process Model "<modelName>" (<versionNo>) does not match the version of the target
WmMonitor package (<versionNo>)
Cause: The version of the WmMonitor package on the source system and the version of the WmMonitor
package on the target system do not match.
Response: Update the version of WmMonitor on the target system to match the version on the source system.

ETD.0008.0119 Error from putModelMetaData: <errorMsg>

Cause: A ServiceException was thrown from the putModelMetaData method.
Response: Verify that the correct version of the WmMonitor package is installed on the target machine.

ETD.0008.0120 Error from scanPackage or setModelEnabled: <errorMsg>

Cause: An exception was thrown when trying to invoke the scanPackage service against one of the process
model packages.
Response: Verify that the package is on the target machine. If the process model package name was not
properly encoded in the original build, rebuild and redeploy your project.

ETD.0008.0123 Would have failed to deploy Process Model: "<modelName>".

Cause: Some part of the process model deployment simulation failed; as a result, the deployment simulation
failed for the whole process model.
Response: Correct the cause of the failure and redeploy.

webMethods Error Message Reference Version 6.5 and 6.5.1 229

CHAPTER 2 webMethods Deployer

ETD.0008.0124 Failed to deploy Process Model: "<modelName>".

Cause: Some part of the process model deployment simulation failed; as a result, the deployment simulation
failed for the whole process model.
Response: Correct the cause of the failure and redeploy.

ETD.0008.0125 Missing data for Process Model: "<modelName>".

Cause: The processMetaData field that is in the XML encoded IData file contained in the project is null.
Response: Verify that the XML encoded IData file, which is contained in the project, contains a non-empty
processMetaData field.

ETD.0008.0126 No deployable Process Models.

Cause: Deployer invoked the deployObjects method with invalid parameters; the input IData object, "objects,"
was null. This indicates that Deployer encountered a severe internal error.
Response: Contact webMethods Customer Care. Please have the following information available:

- A copy of the Server Log from the timeframe when the error occurred

- A copy of the project file (persist\projects\<project>\<project>.xml, where <project> is the name of the
project)

ETD.0008.0127 No server defined.

Cause: Deployer invoked the deployObjects method with invalid parameters; the input IData object, "server,"
was null. This indicates that Deployer encountered a severe internal error.
Response: Contact webMethods Customer Care. Please have the following information available:

- A copy of the Server Log from the timeframe when the error occurred

- A copy of the project file (persist\projects\<project>\<project>.xml, where <project> is the name of the
project)

- Copies of the server configuration files located in config\pluginServer\Modeler

230 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0008.0131 Invalid or NULL logicalServer.
Cause: A target logical server appears to be null or have no name.
Response: Make sure that you have valid logical servers set up in your source Modeler server.

ETD.0008.0132 No physical server for logical server: <logicalServerName>

Cause: Deployer is attempting to deploy a model step to a target Modeler server; however, the target Modeler
server does not have a physical server assigned to the logical server where the step is to be deployed.
Response: Make sure that the logical servers defined on the target Modeler server are set up correctly.

ETD.0008.0133 Logical server name "<logicalServerName>" rejected. Skipping dependencies for this server.
Cause: One or more logical server names is null.
Response: Check that all logical server names are valid.

ETD.0008.0134 Logical server name "<logicalServerName>" returns null logical server. Skipping dependencies for this
server.
Cause: There is no logical server with the name: <logicalServerName>.
Response: Make sure that the logical servers defined on the target Modeler server are set up correctly.

ETD.0008.0135 <modelerService>, processName= <processName>, modelID= <modelID>

Cause: An exception occurred invoking the specified <modelerService> against Modeler, for the specified
<processName>, and <modelID>. Possible causes include:

- The network connection to the target Integration Server is not working.

- The target Integration Server is not running.

- There is an incorrect version of Modeler.

- The model specified no longer exists.

Response: Verify that your Integration Server is running and reachable. Also verify that the indicated model
exists and is still valid.

ETD.0008.0135 Missing jar: "<jarFilename>" does not exist

Cause: One or more of the following jar files could not be found under your <webM Install Directory>:
packages/WmModeler/code/jars/biapp.jar, packages/WmModeler/code/jars/bi_client.jar,
packages/WmDeployerResource/code/jars/ite2util.jar, or lib/client.jar.
Response: Ensure that your installation is correct.

webMethods Error Message Reference Version 6.5 and 6.5.1 231

CHAPTER 2 webMethods Deployer

ETD.0008.0136 <modelerService>, processName= <processName>, modelID= <modelID>, type= <type>, subNodeID=

<subnodeID>
Cause: An exception occurred invoking the specified <modelerService> against Modeler, for the specified
<processName>, <modelID>, <type>, and <subnodeID>. Possible causes include:

- The network connection to the target Integration Server is not working.

- The target Integration Server is not running.

- There is an incorrect version of Modeler.

- The model specified no longer exists.

Response: Verify that your Integration Server is running and reachable. Also verify that the indicated model
exists and is still valid.

ETD.0009.0003 Error invoking service "wm.deployer.UIAuthorization:isAuthorized".

Cause: An exception occurred invoking the wm.deployer.UIAuthorization:isAuthorized service. That could
mean that Integration Server is not running, or is not reachable on the network.
Response: Verify that your Integration Server is running, and reachable on the network.

ETD.0009.0004 Error cloning source system "<serverName>": <exceptionMessage>

Cause: This exception is there for completeness but would not typically be encountered by a user. The
exception means that the Project contains a source system of unknown type. The Project file would probably
be corrupt at that point, and the user would have experienced many more problems before getting this
exception.
Response: Rebuild your Project.

ETD.0009.0006 Checkpoint summary file "<fileName>" does not exist.

Cause: The Checkpoint file does not exist on disk.
Response: Use Deployer to create a Checkpoint.

ETD.0009.0007 Cannot write to checkpoint directory "<directoryName>".

Cause: You cannot create, or cannot write to, the specified directory name.
Response: Ensure that you have the correct privileges to create and write to the directories. Verify that the file
system has enough space for the creation of a new directory.

232 webMethods Error Message Reference Version 6.5 and 6.5.1

ETD.0009.0009 Error creating checkpoint "<checkpointName>", "<errorMessage>"
Cause: An exception occurred when creating the Checkpoint report.
Response: Ensure that you have the correct privileges to create and write to files. Verify that the file system has
enough space for the new file.

ETD.0009.0010 Error saving checkpoint project "<checkpointProjectFilename>". "<errorMessage>"

Cause: The specified file could not be saved to disk.
Response: Ensure that you have the correct privileges to create and write to files. Verify that the file system has
enough space for the new file.

ETD.0010.0101 The target IS is not part of a cluster.

Cause: The target Integration Server is not part of a cluster.
Response: The Integration Server documentation describes the proper set up for a clustered configuration.

ETD.0010.0102 Invalid cluster. IS version <version> is not supported for cluster deployment.
Cause: The target Integration Server version does not support clustering. Clustering was added in version 6.5.
Response: Support for clustering was added in Integration Server 6.5; upgrade to that version or greater.

ETD.0010.0103 The target IS either has no Remote Servers configured or the watt.server.cluster.aliasList is empty.
Cause: The target Integration Server is not correctly configured for clustering.
Response: The Integration Server documentation describes the proper set up for a clustered configuration.

ETD.0010.0104 Some aliases listed in your watt.server.cluster.aliasList are not configured as Remote Servers on the target
IS.
Cause: The target Integration Server is not correctly configured for clustering.
Response: The Integration Server documentation describes the proper set up for a clustered configuration.

webMethods Error Message Reference Version 6.5 and 6.5.1 233

CHAPTER 2 webMethods Deployer

234 webMethods Error Message Reference Version 6.5 and 6.5.1

CHAPTER 3
webMethods EDI Module

EDICOR (WmEDI Package) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

EDIFTN (WmEDIforTN Package) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

webMethods Error Message Reference Version 6.5 and 6.5.1 235

CHAPTER 3 webMethods EDI Module

EDICOR (WmEDI Package)

EDICOR.000010.000018 Invalid reservation reference

Cause: The reservation object specified in the service input does not exist.
Response: Specify an existing reservation object when invoking the service.

EDICOR.000010.000020 Unsupported encoding specified

Cause: The webMethods EDI Module was unable to convert the content specified by the reservation object to a
String because the specified encoding is not supported.
Response: Check the EDIencoding property in the
webMethods\IntegrationServer\packages\WmEDI\config\properties.cnf file to ensure it specifies a
supported encoding.

EDICOR.000010.000023 Fail to read T-space InputStream

Cause: The service was unable to read the content specified by the reservation object.
Response: Make sure that the reservation object that you specify is valid and that the reservation exists. For
example, make sure you have mapped the correct value to the reservation object.

EDICOR.000010.000070 Failed to get related nodes: <nodeName>

Cause: When trying to create a String object, the wm.b2b.edi:convertToString service was unable to locate a
node in the IS document type that relates to a node in the source IData object.
Response: Make sure the IS document type matches the source IData object.

EDICOR.000010.000072 No record definition found for <recordName>'

Cause: The specified record in the input Document (IData object) is not defined in the flat file schema.
Response: Make sure the flat file schema matches the input IData object.

EDICOR.000010.000074 Exception while compose output '<recordName>'

Cause: The wm.b2b.edi:convertToString service was unable to use the flat file schema to convert the input
IData object to a String object.
Response: Make sure the flat file schema matches the input IData object.

236 webMethods Error Message Reference Version 6.5 and 6.5.1

EDICOR (WmEDI Package)

EDICOR.000010.000108 Unsupported encoding specified - <encodingName>

Cause: When reading data from InputStream and converting it to String, the encoding specified is not
supported.
Response: Check the EDIencoding property in the
webMethods\IntegrationServer\packages\WmEDI\config\properties.cnf file to ensure it specifies a
supported encoding.

EDICOR.000010.000410 Segment name '<segmentName>' not defined

Cause: The specified segment name is not defined in the flat file schema.
Response: Update the flat file schema to define the segment.

EDICOR.000010.000414 Incomplete grouping '<groupName>'

Cause: The user data is missing information (e.g., record or field) that is defined as a required part of the group
by the flat file schema.
Response: Make sure the user data is not missing required records or fields. If the user data is okay, ensure the
flat file schema was created correctly.

EDICOR.000010.000422 Incomplete grouping '<groupName>'

EDICOR.000010.000602 Interface specification error

Cause: Folder name that was specified when invoking the wm.b2b.edi.util:invoke service is incorrect.
Response: Make sure the name that you specified for the folder is correct and not null. Additionally, make sure
that the folder exists.

EDICOR.000010.000604 Service specification error

Cause: Service name that was specified when invoking the wm.b2b.edi.util:invoke service is incorrect.
Response: Make sure the fully-qualified service name (folder name and service name) identify a valid service in
the Integration Server namespace.

EDICOR.000010.000620 Input 'edidata' must not null

Cause: Input parameter 'edidata' was null when the wm.b2b.edi.util:checkStandard service was invoked.
Response: Make sure the input parameter 'edidata' is not null.

webMethods Error Message Reference Version 6.5 and 6.5.1 237

CHAPTER 3 webMethods EDI Module

EDICOR.000010.000622 Invalid object type for input 'edidata'

Cause: Input parameter 'edidata' has a data type that is not String, InputStream, or byte[] object.
Response: Make sure the data type of the input parameter 'edidata' is String, InputStream, or byte[] object.

EDICOR.000010.000624 IO Error while reading data from InputStream - '<IOException>'

Cause: An IO Exception was encountered while performing a Stream I/O function when invoking the
wm.b2b.edi.util:streamToString service.
Response: Make sure the InputStream is valid.

EDICOR.000010.000626 Unsupported Character Encoding specified - '<exceptionMessage>'

Cause: The encoding used in the wm.b2b.edi.util:streamToString service is not supported.
Response: Check the EDIencoding property in the
webMethods\IntegrationServer\packages\WmEDI\config\properties.cnf file to ensure it specifies a
supported encoding.

EDICOR.000010.000628 IO Error creating sequence InputStream - ‘<IOException>’

Cause: Failed to create SequencedInputStream.
Response: Contact webMethods Customer Care for assistance.

EDICOR.000010.000630 <exception message>

Cause: Exception occurred when invoking the wm.b2b.edi.util:standardCheck service.
Response: Make sure you specified the input to the wm.b2b.edi.util:standardCheck service correctly.

EDICOR.000010.000632 Service '<serviceName>' is not allowed to be invoked (not defined in file services.cnf under package
config directory)
Cause: The service that the user wants to invoke using the wm.b2b.edi.util:invoke service is not defined in the
services.cnf configuration file.
Response: Add the fully-qualified service name to the following file:
webMethods/IntegrationServer/packages/WmEDI/config/service.cnf.

EDICOR.000010.000802 Input 'SEFfileName' is not specified for service wm.b2b.edi:createW3CXMLSchema

Cause: The wm.b2b.edi:createW3XMLSchema service was invoked, but the input parameters did not include
the SEF file name.
Response: Specify the 'SEFfileName' input parameter that identifies the SEF file name when invoking the
wm.b2b.edi:createW3XMLSchema service.

238 webMethods Error Message Reference Version 6.5 and 6.5.1

EDICOR (WmEDI Package)

EDICOR.000010.000804 Input 'transactionSet' is not specified for service wm.b2b.edi:createW3CXMLSchema

Cause: The wm.b2b.edi:createW3CXMLSchema service was invoked, but the input parameters did not include
the transaction set name.
Response: Specify the 'transactionSet' input parameter that identifies the transaction set name when invoking
the wm.b2b.edi:createW3XMLSchema service.

EDICOR.000010.000810 Input 'serverName' or 'IDOCname' for service wm.b2b.edi:createIDOCtemplate must be specified

Cause: The wm.b2b.edi:createIDOCtemplate service was invoked, but the 'serverName' and/or the
'IDOCname' input parameters were not specified.
Response: Specify the 'serverName' and 'IDOCname' input parameters when invoking the
wm.b2b.edi:createIDOCtemplate service.

EDICOR.000010.000812 No syntax table defined for '<SAPSyntaxTableName>'

Cause: The IDOC name that was specified is not valid; that is, it is not defined in SAP.
Response: Make sure the IDOC name is a valid SAP IDOC name.

EDICOR.000010.000904 Unable to save Properties Settings. '<Property Name>'

Cause: The specified property was not saved because it is not valid. The property setting will not take affect.
Response: Make sure the property setting is valid.

EDICOR.000010.000906 Unable to save Format Settings.<errorMessage>

Cause: The format setting was not saved to the format.xml file because the format setting is not valid.
Response: Make sure the format setting is valid.

EDICOR.000010.000910 Unable to load Format Settings. <errorMessage>

Cause: The format setting in the format.xml file is not valid.
Response: Make sure the format setting in the format.xml file is valid.

EDICOR.000010.001000Unable to format value <Object name>

Cause: The service could not format the object. It may not exist or be valid.
Response: Check input parameters for validity.

webMethods Error Message Reference Version 6.5 and 6.5.1 239

CHAPTER 3 webMethods EDI Module

EDICOR.000010.001001 Unable to format value <argumentValue>. Contained additional characters after character
<additionalValue>.
Cause: The service could not format the object. It contains additional characters.
Response: Check input parameters for validity.

EDICOR.000020.000050 Unrecognized object found for node

Cause: The webMethods EDI Module could not locate a node within an IS Document (IData object).
Response: Check the IS document type. Either 1) ensure you have specified the correct IS document type, or 2)
update the IS document type to include the missing object.

EDICOR.000020.000052 <objectType> found instead of IData object

Cause: The object has the data type String rather than the expected Document (IData object) data type.
Response: Make sure the source IData object is created correctly.

EDICOR.000020.000102 Variable length record must have byte[] as input

Cause: For a variable length record, the input parameter 'edidata' must be a byte[] object.
Response: Make sure the data type of the input parameter 'edidata' is byte[] object.

EDICOR.000020.000104 Fail to get more data from InputStream while setting separators
Cause: Failed to find delimiters when scanning the user data.
Response: Make sure the delimiters exist within the user data.

EDICOR.000020.000106 <exceptionMessage>
Cause: The webMethods EDI Module encountered an IO Exception while performing a Stream I/O function.
Response: Make sure the InputStream against which the EDI Module is performing the Stream I/O function is
valid.

EDICOR.000020.000110 Unsupported character encoding - <encodingName>

Cause: When reading data from InputStream and converting it to String, the character encoding specified is not
supported.
Response: Check the EDIencoding property in the
webMethods\IntegrationServer\packages\WmEDI\config\properties.cnf file to ensure it specifies a
supported encoding.

240 webMethods Error Message Reference Version 6.5 and 6.5.1

EDICOR (WmEDI Package)

EDICOR.000020.000402 SEF file format error

Cause: The SEF file is not formatted correctly.
Response: Update the format of the SEF file to make it valid. Alternatively, copy the original file from the
webMethods\IntegrationServer\packages\WmEDI\pub\SEF directory.

EDICOR.000020.000404 No transaction set defined in SEF file

Cause: The SEF file does not contain any transaction sets.
Response: Update the format of the SEF file to add the transaction sets. Alternatively, copy the original file
from the webMethods\IntegrationServer\packages\WmEDI\pub\SEF directory.

EDICOR.000020.000406 Transaction set '<transactionName>' is not defined in the SEF file

Cause: The SEF file does contain the transaction that the user specified.
Response: Make sure you are using the correct SEF file.

EDICOR.000020.000420 Segment name '<segmentName>' not defined

Cause: The specified segment name is not defined in the flat file schema.
Response: Update the flat file schema to define the segment.

webMethods Error Message Reference Version 6.5 and 6.5.1 241

CHAPTER 3 webMethods EDI Module

EDIFTN (WmEDIforTN Package)

EDIFTN.000010.000002 Input 'bizdoc' for service wm.b2b.editn:getStandard cannot be null

Cause: The input parameter 'bizdoc' for the wm.b2b.editn:getStandard service was null. The 'bizdoc' parameter
is required and must be specified.
Response: Specify the 'bizdoc' parameter when invoking the wm.b2b.editn:getStandard service.

EDIFTN.000010.000003 Input 'bizdoc' for service wm.b2b.editn:getVersion cannot be null

Cause: The input parameter 'bizdoc' for the wm.b2b.editn:getVersion service was null. The 'bizdoc' parameter
is required and must be specified.
Response: Specify the 'bizdoc' parameter when invoking the wm.b2b.editn:getVersion service.

EDIFTN.000010.000004 Input 'bizdoc' for service wm.b2b.editn:getTransaction cannot be null

Cause: The input parameter 'bizdoc' for the wm.b2b.editn:getTransaction service was null. The 'bizdoc'
parameter is required and must be specified.
Response: Specify the 'bizdoc' parameter when invoking the wm.b2b.editn:getTransaction service.

EDIFTN.000010.000006 Unable to install doc type: 'standard' not supplied

Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000010.000007 Unable to install doc type: 'version' not supplied

Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000010.000008 Unable to install doc type: 'transaction' not supplied

Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000010.000009 Failed to install doc type - <docTypeName>

Cause: You attempted to install the specified TN document type, which is a TN document for an EDI
document. The message should contain additional error code(s) detailing reason for error.
Response: Contact webMethods Customer Care for assistance. Be sure to have the information provided in the
message available.

242 webMethods Error Message Reference Version 6.5 and 6.5.1

EDIFTN (WmEDIforTN Package)

EDIFTN.000010.000010 DocTypes file [<fileCanonicalPath>] does not exist

Cause: The document type configuration file identified in the message does not exist. The configuration file
should be in the webMethods6\IntegrationServer\packages\WmEDIforTN\config directory.
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000010.000012 DocTypes file [<fileCanonicalPath>] does not contain transaction: {<transactionName>}

Cause: The document type configuration file identified in the message does not contain valid information for
the specified transaction, <transactionName>.
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000010.000014 No standard specified

Cause: The EDI standard was not specified in the input parameters. This is a required input parameter.
Response: Specify the input parameter for the EDI standard when invoking the service.

EDIFTN.000010.000016 Failed to create reservation

Cause: The webMethods EDI Module was unable to create reservation in tspace, which is the temporary
location to save documents considered large.
Response: Check the limit of maximum reservation size for your tspace area. The maximum reservation size is
specified by the tn.tspace.max property in the
webMethods\IntegrationServer\packages\WmTN\config\properties.cnf file. For more information about
this property, see the webMethods Trading Networks properties online help.

EDIFTN.000010.000018 {<exceptionShortDescription>}
Cause: The webMethods EDI Module failed to convert the data because the encoding specified by the
EDIencoding property in the WmEDI properties file is not supported for the data being converted.
Response: Check the EDIencoding property in the
webMethods\IntegrationServer\packages\WmEDI\config\properties.cnf file to ensure it specifies a
supported encoding.

EDIFTN.000010.000020 No content or content part 'EDIdata' found for a specific EDI document
Cause: The BizDocEnvelope did not contain an 'EDIdata' content or content part.
Response: Ensure that the BizDocEnvelope is a BizDocEnvelope for an EDI document.

webMethods Error Message Reference Version 6.5 and 6.5.1 243

CHAPTER 3 webMethods EDI Module

EDIFTN.000010.000021 Input 'edidata' for wm.b2b.editn.EDIEnvelopeDocType.streamToBytesOrReservation() is invalid

Cause: The input parameter 'edidata' for the
wm.b2b.editn.EDIEnvelopeDocType.streamToBytesOrReservation() function is not valid. The data type for
the 'edidata' input parameter must be InputStream.
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000010.000026 Failed to add EDI Document Attribute:{<attributeName>} - {<detailedExceptionMessage>}

Cause: The webMethods EDI Module failed to add the custom document attribute to Trading Networks during
the start up of the WmEDIforTN package. The message should contain additional error code(s) detailing
reason for error.
Response: Contact webMethods Customer Care for assistance. Be sure to have the information provided in the
message available.

EDIFTN.000010.000029 Failed to register EDI Batch service {<detailedExceptionMessage>}

Cause: The webMethods EDI Module failed to register the wm.b2b.editn.batch:batchProcess service as a
Trading Networks scheduled delivery service. The message should contain additional error code(s) detailing
reason for error.
Response: Contact webMethods Customer Care for assistance. Be sure to have the information provided in the
message available.

EDIFTN.000010.000032 Unrecognized input data type

Cause: An input parameter that was specified for the service had an incorrect data type.
Response: Ensure that you use the correct data types for input parameters to the service.

EDIFTN.000010.000034 Failed to load VANReportsDirectory.cnf - {detailedExceptionMessage}

Cause: The webMethods EDI Module failed to load the VANReportsDirectory.cnf file. The message should
contain additional error code(s) detailing reason for the error.
Response: Ensure the VANReportsDirectory.cnf file has the right format that lists the directories in which the
webMethods EDI Module can store reports it retrieves from VANs. The VANReportsDirectory.cnf should
have one directory per line. The VANReportsDirectory.cnf is located in the
webMethods\IntegrationServer\packages\WmEDIforTN\config directory.

EDIFTN.000010.000040 Fail to get task data from bizDoc

Cause: The webMethods EDI Module was unable to get the TN Delivery Content from the bizdoc.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages/WmEDIforTN/config directory.

244 webMethods Error Message Reference Version 6.5 and 6.5.1

EDIFTN (WmEDIforTN Package)

EDIFTN.000010.000042 Source data standard is different than batch service specified

Cause: The standard specified in the individual EDI message is not the same as the one specified in the service
input.
Response: Make sure the EDI message in the batch queue has the same version as the one specified in the
service input.

EDIFTN.000010.000102 Error in EDITransactionDocType: {<TNdocTypeName>}.

Cause: An error occurred while attempting to create the EDI Transaction document. This is a brief message.
The EDI Module records the full message in the Trading Networks activity log, which should contain
additional error code(s).
Response: Using the Trading Networks Console, view the Trading Networks activity log entries that are
associated with this document.

EDIFTN.000010.000104 Query [<InstanceIdQuery>] produced no BizDoc Instance Id

Cause: The instance ID query that is associated with the transaction did not result in a value to use for the
instance ID. As a result, a conversation ID cannot be set for this transaction.
Response: Check the instance ID query, and make any necessary corrections. If the instance ID query is correct,
check the transaction data.

EDIFTN.000010.000106 Unable to determine conversation id

Cause: The webMethods EDI Module was unable to retrieve a conversation ID from the process run time
(PRT).
Response: Make sure that the process run time (PRT) is configured properly. Check the “webMethods Modeler
User's Guide” for details on how to configure the PRT.

EDIFTN.000010.000108 Unable to locate flat file schema for parsing

Cause: The webMethods EDI Module was unable to locate a flat file schema.
Response: Make sure that the appropriate flat file schema is installed for this TN document type. You can create
the flat file schema using the service wm.b2b.edi.migration:updateBizDocs. This service will create flat file
schemas for all EDI TN document types, if the flat file schema does not already exist.

EDIFTN.000010.000114 The character encoding {<characterEncodingName>} is not supported.

Cause: The EDIencoding property in WmEDI package properties file does not support this data.
Response: Check the EDIencoding property in the
webMethods\IntegrationServer\packages\WmEDI\config\properties.cnf file to ensure it specifies a
supported encoding.

webMethods Error Message Reference Version 6.5 and 6.5.1 245

CHAPTER 3 webMethods EDI Module

EDIFTN.000010.000116 Failed to update EDI Tracking status: Original Doc ID: {<documentID>}, related Doc ID:
{<documentID>}, new status {FAStatus>}
Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000010.000118 Failed to relate to original document {<documentID>}

Cause: The webMethods EDI Module failed to relate the original document identified by the document ID
specified in the message to its corresponding Functional Acknowledgement (FA). Check the detailed message
in Trading Networks activity log for additional error code(s).
Response: Ensure that the original document still exists in Trading Networks. You can do so by attempting to
view the original document using the Trading Networks Console Transaction Analysis screen. Additionally,
you can use the Trading Networks Activity Log screen to view related entries that contain a detailed message,
which contains the additional error code(s).

EDIFTN.000010.000120 Failed to query FA Reconciliation entries

Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000010.000126 Unable to get FA Reconciliation from EDI TPA, disabled used

Cause: Error obtaining the default or partner-specific EDITPA from the Trading Networks database. As a
result, the webMethods EDI Module was unable to obtain the value of the FAreconciliation EDITPA variable.
Response: To determine whether the problem is with the database connection or is an internal error, attempt to
view the EDITPA using the Trading Networks Console. If you are not able to view the EDITPA using the
Trading Networks console, consult your database administrator about the database connection problem. If
you can view the EDITPA using the Trading Networks console, contact webMethods Customer Care for
assistance.

EDIFTN.000010.000202 Failed creating EDI envelope doc type. Cannot handle null object
Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000010.000204 Failed creating EDI envelope doc type. Cannot handle object of type: {<objectClassName>}
Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

246 webMethods Error Message Reference Version 6.5 and 6.5.1

EDIFTN (WmEDIforTN Package)

EDIFTN.000010.000206 Failed creating EDI envelope doc type. Service wm.b2b.editn.getAllDetails returned null or empty
details
Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000010.000208 An error occurred during document processing. The service wm.b2b.editn:getICDetail failed
Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000010.000212 Unable to determine conversation id

Cause: The process run time engine is not configured.
Response: See the “webMethods Modeler User's Guide” for details about how to configure the process run
time engine.

EDIFTN.000010.000214 Unsupported character encoding {<characterEncodingName>} is used

Cause: The EDIencoding property in WmEDI properties does not support this data.
Response: Check the EDIencoding property in the
webMethods\IntegrationServer\packages\WmEDI\config\properties.cnf file to ensure it specifies a
supported encoding.

EDIFTN.000010.000216 {<exceptionShortDescription>}
Cause: Internal Error in EDIEnvelopeDocType.createEnvelope().
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000010.000217 Unable to get default EDI TPA {<exceptionShortDescription>}

Cause: The default EDITPA does not exist.
Response: Create the default EDITPA. The default EDITPA is a Trading Networks TPA with the sender and
receiver set to 'Unknown', the Agreement ID set to 'EDITPA', and the IS document type set to
wm.b2b.editn.TPA:EDITPA.

EDIFTN.000010.000218 Unable to get TPA {<exceptionShortDescription>}

Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

webMethods Error Message Reference Version 6.5 and 6.5.1 247

CHAPTER 3 webMethods EDI Module

EDIFTN.000010.000233 Invalid Sender ID

Cause: The webMethods EDI Module was unable to find a Trading Networks internal ID for the sender. This
typically means that there is no Trading Networks profile for the sender. A detailed message is logged to the
Trading Networks activity log and should provide the details about this sender's EDI qualifier and Identifier.
Response: Create a Trading Networks profile for the sender.

EDIFTN.000010.000234 Invalid Receiver ID

Cause: The webMethods EDI Module was unable to find a Trading Networks internal ID for the receiver. This
typically means that there is no Trading Networks profile for the receiver. A detailed message is logged to the
Trading Networks activity log and should provide the details about this receiver's EDI qualifier and Identifier.
Response: Create a Trading Networks profile for the receiver.

EDIFTN.000010.000240 TPA Exception

Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000010.000242 TPA Store Exception

Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000010.000243 PRT Not Enabled.

Cause: The process run time (PRT) is not enabled.
Response: Enable the WmPRT package.

EDIFTN.000010.000244 PRT Not Enabled. Conversation ID will not be extracted.

Cause: The process run time (PRT) is not enabled.
Response: Enable the WmPRT package.

EDIFTN.000010.000245 Received a document with a duplicate control number.

Cause: The webMethods EDI Module received a document with a control number that matches the control
number on a document previously received.
Response: Check the contents of the document. If it is a duplicate document and the previous document has
been processed, the duplicate document can be ignored.

248 webMethods Error Message Reference Version 6.5 and 6.5.1

EDIFTN (WmEDIforTN Package)

EDIFTN.000010.000246 Received a document with an out of sequence control number.

Cause: The webMethods EDI Module received a document with an out-of-sequence control number.
Response: Check with the trading partner to make sure there is no missing document.

EDIFTN.000010.000247 Rejected a document that failed control number validation.

Cause: The EDI document is rejected because an error occurred during control number validation. The EDI
Module records the full message in the Trading Networks activity log, which should contain additional error
code(s).
Response: Use the Trading Networks Console to view the Trading Networks activity log entries that are
associated with this document.

EDIFTN.000010.000248 Expected a control number of <correct>, but received <error control number>. This is a duplicate
control number.
Cause: The webMethods EDI Module received a document which has a duplicate control number.
Response: Verify the control number of the EDI data. If it is a duplicate control number, ignore or reprocess the
document.

EDIFTN.000010.000249 Control number <error control number> exceeds cap of <control number cap>.
Cause: There is a configurable control number cap. The document control number received exceeded the
control number cap. For example, the control number cap is 200000 and the control number received is 200200.
Response: Contact the trading partner to inquire about the control number or increase the control number cap.

EDIFTN.000010.000250 Control number <actual control number> is less than minimum of <configured minimum control
number>.
Cause: There is a configurable control number minimum. The document received is less than the control
number minimum. For example, the control number minimum is 200 and in the document, the control number
is 190.
Response: Contact the trading partner to inquire about the control number or decrease the control number
minimum.

EDIFTN.000010.000252 Expected a control number of <expected control number>, but received <actual control number>.
This is a out of sequence control number.
Cause: The webMethods EDI Module received a document with a out-of-sequence control number.
Response: Verify the control number of the EDI data. If it is out of sequence, ignore or reprocess the document.

webMethods Error Message Reference Version 6.5 and 6.5.1 249

CHAPTER 3 webMethods EDI Module

EDIFTN.000010.000254 Cannot reprocess an envelope document that contains multiple interchanges.

Cause: The webMethods EDI Module cannot reprocess this document because it contains more than one
interchange.
Response: Select another document for reprocessing.

EDIFTN.000010.000255 Cannot reprocess a group document that contains multiple groups.

Cause: The webMethods EDI Module cannot reprocess this document because it contains more than one
group.
Response: Select another document for reprocessing.

EDIFTN.000010.000257 Cannot reprocess document <TN internal document id>, no such document.
Cause: The document does not exist.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages/WmEDIforTN/config directory.

EDIFTN.000010.000258 Cannot reprocess document <TN internal document id>.\n<detailed error message>.
Cause: There is a database error.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages/WmEDIforTN/config directory.

EDIFTN.000010.000260 Failed to create EDI Status entry.

Cause: There is a database error.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages/WmEDIforTN/config directory.

EDIFTN.000010.000262 Cannot reprocess an Auto Generate FA rejected group document with generateFA and/or
updateControlNumber option set to be true.
Cause: The webMethods EDI Module cannot reprocess the document because the control number has already
been updated.
Response: Turn off the updateControlNumber option and reprocess the document. Then, manually update the
control number.

250 webMethods Error Message Reference Version 6.5 and 6.5.1

EDIFTN (WmEDIforTN Package)

EDIFTN.000010.000263 Cannot reprocess a Duplicate Control Number or Out of Sequence Control Number group document
with generateFA option set to be true.
Cause: The webMethods EDI Module cannot reprocess the document because the control number has already
been updated.
Response: Turn off the updateControlNumber option and reprocess the document. Then, manually update the
control number.

EDIFTN.000010.000264 Cannot reprocess an Auto FA rejected envelope document with generateFA and/or
updateControlNumber option set to be true.
Cause: The webMethods EDI Module cannot reprocess the document because the control number has already
been updated.
Response: Turn off the updateControlNumber option and reprocess the document. Then, manually update the
control number.

EDIFTN.000010.000270 Cannot Auto generate FA.

Cause: The webMethods EDI Module failed to generate a Functional Acknowledgment. The EDI Module
records the full message in the Trading Networks activity log, which should contain additional error code(s).
Response: Use the Trading Networks Console to view the Trading Networks activity log entries that are
associated with this document.

EDIFTN.000010.000271 Unknown Sender and/or Receiver ID.

Cause: The trading partner profile cannot be located for the sender and/or receiver ID.
Response: Make sure the partner profile exists.

EDIFTN.000010.000272 Unable to get content data.

Cause: An I/O Exception occurred.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages/WmEDIforTN/config directory.

EDIFTN.000010.000273 The service wm.b2b.edi.util:generateFA failed. All Documents will be set status to
Rejected.\n<detailed message>
Cause: The service wm.b2b.edi.util:generateFA failed.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages/WmEDIforTN/config directory.

webMethods Error Message Reference Version 6.5 and 6.5.1 251

CHAPTER 3 webMethods EDI Module

EDIFTN.000010.000274 Auto Generate FA indicates that this document has status <actual status>.
Cause: The document failed validation.
Response: Check the auto-generated FA and notify the trading partner to correct the error.

EDIFTN.000010.000276 The service wm.b2b.edi.util:generateFA failed to return valid FA status.\nAll Documents will be set to
Rejected.
Cause: Error occurred and status was not returned while trying to generate a Functional Acknowledgement.
Response: Check the auto-generated FA and notify the trading partner to correct the error.

EDIFTN.000010.000278 No FA need be generated.

Cause: Functional Acknowledgement was not generated.
Response: No action needed.

EDIFTN.000010.000280 Unable to set FA content.

Cause: The Functional Acknowledgement was not generated due to unsupported encoding. The EDI Module
records the full message in the Trading Networks activity log, which should contain additional error code(s).
Response: Use the Trading Networks Console to view the Trading Networks activity log entries that are
associated with this document, and then Contact webMethods Customer Care. Please have the following
information available: server and error logs, a copy of the Support Information page from the Developer, and
the contents of the packages/WmEDIforTN/config directory.

EDIFTN.000010.000282 Unable to route generated FA document.

Cause: The wm.tn.route service failed to route this FA. The EDI Module records the full message in the Trading
Networks activity log, which should contain additional error code(s).
Response: Use the Trading Networks Console to view the Trading Networks activity log entries that are
associated with this document, and then contact webMethods Customer Care. Please have the following
information available: server and error logs, a copy of the Support Information page from the Developer, and
the contents of the packages/WmEDIforTN/config directory.

EDIFTN.000010.000283 The service wm.tn.route:routeBizdoc failed.\n<detailed message>

Cause: The wm.tn.route service failed to submit the FA document into Trading Networks.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages/WmEDIforTN/config directory.

252 webMethods Error Message Reference Version 6.5 and 6.5.1

EDIFTN (WmEDIforTN Package)

EDIFTN.000010.000290 Rejected a document that failed FA validation/compliance check.

Cause: The document contains an error.
Response: Use the Trading Networks Console to view the Trading Networks activity log entries that are
associated with this document.

EDIFTN.000010.000291 Received a document that failed FA validation/compliance check.

Cause: The EDI document contains an error.
Response: Use the Trading Networks Console to view the Trading Networks activity log entries that are
associated with this document. Check the inbound document against the error message.

EDIFTN.000010.000292 Error occurred attempting to update control number.

Cause: The webMethods EDI Module failed to update the control number in the control number table.
Response: Use the Trading Networks Console to view the Trading Networks activity log entries that are
associated with this document, and then contact webMethods Customer Care. Please have the following
information available: server and error logs, a copy of the Support Information page from the Developer, and
the contents of the packages/WmEDIforTN/config directory.

EDIFTN.000010.000293 The following error occurred while attempting to update the control number:\n<detailed error
message>\n
Cause: The webMethods EDI Module failed to update the control number.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages/WmEDIforTN/config directory.

EDIFTN.000010.000294 Forced reprocessing of document.

Cause: User forced reprocessing of the document.
Response: No action needed.

EDIFTN.000010.000295 Reset control number.

Cause: The control number has been set/updated.
Response: No action needed.

EDIFTN.000010.000296 Status returned by wm.b2b.edi.util:generateFA.

Cause: The FA status is displayed.
Response: No action needed.

webMethods Error Message Reference Version 6.5 and 6.5.1 253

CHAPTER 3 webMethods EDI Module

EDIFTN.000010.000297 Envelope Validation Error.

Cause: The wm.b2b.edi:envelopeProcess service failed. Envelope is not valid.
Response: Use the Trading Networks Console to view the Trading Networks activity log entries that are
associated with this document.

EDIFTN.000010.000298 Expected a control number of <expected one>, but received <actual one>. Setting next expected
control number to <next expected one>
Cause: The control number is out-of-sequence.
Response: No action needed.

EDIFTN.000010.000299 No control number specified in message.

Cause: The control number is not specified. The EDI message must include a control number.
Response: Contact trading partner to make sure they have specified the control number.

EDIFTN.000010.000300 Received invalid control number: `<actual control number>`. This is not a number and cannot be
parsed.
Cause: The control number is not a number. It must be a numeric control number.
Response: Contact trading partner to make sure they have specified a numeric control number.

EDIFTN.000010.000301 Corrupted data

Cause: The data is corrupted. This is an internal error.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages/WmEDIforTN/config directory.

EDIFTN.000010.000312 Unable to determine conversation id

Cause: The webMethods EDI Module cannot obtain a conversation ID. A detailed message is logged to the
Trading Networks activity log and should provide the details.
Response: Using the Trading Networks Console, view the activity log entries to find the detailed messages. If
you need assistance resolving the problem, contact webMethods Customer Care.

EDIFTN.000010.000314 Unsupported character encoding {<characterEncodingName>} is used

254 webMethods Error Message Reference Version 6.5 and 6.5.1

EDIFTN (WmEDIforTN Package)

EDIFTN.000010.000602 Parameter 'DocumentName' not found

Cause: The required input parameter 'DocumentName' was not specified.
Response: Specify the 'DocumentName' input parameter when invoking this service.

EDIFTN.000010.000604 Document Name {<TNdocTypeName>} not found

Cause: The webMethods EDI Module could not find the TN document type that was identified by the
'DocumentName' input parameter.
Response: Ensure that the input parameter 'DocumentName' identifies a valid TN document type name, and
ensure that the specified TN document type is installed in Trading Networks.

EDIFTN.000010.000606 Document Name {<TNdocTypeName>} is not EDITransactionDocType

Cause: The TN document type identified by the 'DocumentName' input parameter is not a TN document type
for an EDI transaction.
Response: Ensure that the input parameter 'DocumentName' specifies a valid TN document type and that it is
a TN document type for an EDI transaction.

EDIFTN.000010.000704 Fail to get internal ID for qualifier:{<EDIIDQualifier} ID:{<EDIID>}.

Error:{<exceptionShortDescription>}
Cause: The webMethods EDI Module could not invoke the wm.b2b.editn:ediPartnerIDToTNPartnerID
service.
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000010.000706 Unrecognized segment skipped:{<segmentName>}

Cause: The segment identified in the message is unrecognizable.
Response: Check the EDI data and make necessary corrections.

EDIFTN.000010.000708 Unrecognized segment skipped:{<segmentName>}

Cause: The segment identified in the message is unrecognizable.
Response: Check the EDI data and make necessary corrections.

EDIFTN.000010.000710 {<IOExceptionShortDescription>}
Cause: This error is related to the use of a reservation in tspace, which is the temporary location to save
documents considered large. The message should contain additional error that detailing reason for error.
Response: See webMethods Trading Networks User’s Guide for more information about large document
handling.

webMethods Error Message Reference Version 6.5 and 6.5.1 255

CHAPTER 3 webMethods EDI Module

EDIFTN.000010.000711 {<IOExceptionShortDescription>}
Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000010.000712 tSpace reservation:{<ReservationShortDescription>}

Cause: This error is related to the use of a reservation in tspace, which is the temporary location to save
documents considered large. The message should contain additional error that detailing reason for error.
Response: See webMethods Trading Networks User’s Guide for more information about large document
handling.

EDIFTN.000010.000716 {<UnsupportedEncodingExceptionShortDescription>}
Cause: The EDIencoding property in WmEDI properties does not support this data.
Response: Check the EDIencoding property in the
webMethods\IntegrationServer\packages\WmEDI\config\properties.cnf file to ensure it specifies a
supported encoding.

EDIFTN.000010.000720 Invoking validation service error: {<ExceptionShortDescription>}

Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000010.000750 {<ExceptionShortDescription>}
Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000010.000752 Exception from EDItx module

Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000010.000753 Fail to extract group header information

Cause: The sender/receiver information cannot be located in the group header.
Response: Contact trading partner to make sure both the sender and receiver are specified in the group header.

256 webMethods Error Message Reference Version 6.5 and 6.5.1

EDIFTN (WmEDIforTN Package)

EDIFTN.000010.000754 Fail to extract interchange header information

Cause: The sender/receiver information cannot be located in the envelope.
Response: Contact trading partner to make sure both the sender and receiver are specified in the group header.

EDIFTN.000010.000760 ID and ID qualifier error

Cause: There may be an error with the ID and/or qualifier inside the Interchange/Group header.
Response: Make sure trading partner is using the correct ID and qualifier.

EDIFTN.000010.000762 Sender and receiver ID and/or ID qualifier error

Cause: The webMethods EDI Module cannot retrieve the sender/receiver profile.
Response: Make sure the partner profile has been created.

EDIFTN.000010.000764 Obtain TPA error

Cause: The webMethods EDI is unable to retrieve a TPA
Response: Make sure the TPA has been defined.

EDIFTN.000010.000766 Sender: <sender id>\nReceiver: <receiver id>\nError: <detailed TPA error message>.
Cause: The webMethods EDI Module failed to retrieve the EDI TPA data for a specific sender/receiver.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages\WmEDIforTN\config directory.

EDIFTN.000010.000768 TPA Store Exception

Cause: There is an error while creating and/or updating a TPA.
Response: Use the Trading Networks Console to view the Trading Networks activity log entries that are
associated with this document.

EDIFTN.000010.000770 Error: <detailed TPA Store exception message>

Cause: There is an error while creating and/or updating a TPA.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages\WmEDIforTN\config directory.

webMethods Error Message Reference Version 6.5 and 6.5.1 257

CHAPTER 3 webMethods EDI Module

EDIFTN.000010.000772 Failed to get control number

Cause: Error occurred while trying to retrieve the control number.
Response: Use the Trading Networks Console to view the Trading Networks activity log entries that are
associated with this document.

EDIFTN.000010.000774 Sender: <sender id>\nReceiver: <receiver id>\nError: EDITPA does not exist for these two trading
partners
Cause: The EDITPA for the two trading partners do not exist.
Response: Create a TPA for each trading partner.

EDIFTN.000010.000776 Delimiter setup error

Cause: The delimiter was not setup correctly.
Response: Make sure the delimiter setup was completed correctly.

EDIFTN.000010.000778 Segment, field or sub-field delimiter has not been setup

Cause: Segment, field or sub-field delimiters are required and have not been setup.
Response: Setup all delimiters.

EDIFTN.000010.000780 <Detailed exception message>

Cause: Check the exception message for more information.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages\WmEDIforTN\config directory.

EDIFTN.000010.000782 Error creating batch

Cause: The webMethods EDI Module failed to create a batch document.
Response: Check the server log for error messages.

EDIFTN.000010.000784 Delivery job doesn't exists

Cause: Delivery job may have been deleted.
Response: Use the Trading Networks Console to view the Trading Networks activity log entries that are
associated with this document.

258 webMethods Error Message Reference Version 6.5 and 6.5.1

EDIFTN (WmEDIforTN Package)

EDIFTN.000010.000786 Please check console and error log

Cause: There is an error in the delivery job entry.
Response: Use the Trading Networks Console to view the Trading Networks activity log entries that are
associated with this document and the Integration Server error log.

EDIFTN.000010.000818 Failed to create EDI Tracking entry

Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000020.000901 Error getting EDI_tracking data

Cause: An internal error occurred when querying EDI Tracking data in the EDITRACKING table, which is an
EDI Module-specific table in the Trading Networks database.
Response: Contact webMethods Customer Care for assistance.

EDIFTN.000040.000001 Could not add Control Number. Record already exists.

Cause: The webMethods EDI Module could not add a row to the EDIControlNumber table because a row
already exists for Sender ID, Sender Qualifier, Receiver ID, Receiver Qualifier, Standard, Production Mode,
Version and Group Type combination. The EDIControlNumber is an EDI Module-specific table in the Trading
Networks database.
Response: Ensure the values you specify for Sender ID, Sender Qualifier, Receiver ID, Receiver Qualifier,
Standard, Production Mode, Version and Group Type form a unique combination.

EDIFTN.000040.000007 Could not add envelope. Record already exists, for that Sender ID, Sender Qualifier, Receiver ID,
Receiver Qualifier, production mode combination.
Cause: The webMethods EDI Module could not add a row to the EDIEvelopeInfo table because a row already
exists for that Sender ID, Sender Qualifier, Receiver ID, Receiver Qualifier, and production mode combination.
The EDIEvelopeInfo is an EDI Module-specific table in the Trading Networks database.
Response: Ensure the values you specify for Sender ID, Sender Qualifier, Receiver ID, Receiver Qualifier, and
production mode form a unique combination.

EDIFTN.000040.000008 Could not add GS Pair. Record already exists, for that Sender ID, Sender Qualifier, Receiver ID,
Receiver Qualifier combination.
Cause: The webMethods EDI Module could not add a row to the EDIGroup table because a row already exists
for that Sender ID, Sender Qualifier, Receiver ID, and Receiver Qualifier combination. The EDIGroup is an EDI
Module-specific table in the Trading Networks database.
Response: Ensure the values you specify for Sender ID, Sender Qualifier, Receiver ID, and Receiver Qualifier
form a unique combination.

webMethods Error Message Reference Version 6.5 and 6.5.1 259

CHAPTER 3 webMethods EDI Module

EDIFTN.000040.000009 Could not add GS Pair. Envelope Pair already exists, for that Sender ID, Sender Qualifier, Receiver
ID, Receiver Qualifier combination.
Cause: The webMethods EDI Module could not add a row to the EDIGroup table for the GS Pair that you
specified because an interchange sender/receiver pair already exists in the EDIEnvelopeInfo table for the
sender/receiver pair that you specified using the Sender ID, Sender Qualifier, Receiver ID, and Receiver
Qualifier combination. The EDIGroup and EDIEnvelope tables are EDI Module-specific tables in the Trading
Networks database.
Response: When adding a GS Pair, ensure the values you specify for Sender ID, Sender Qualifier, Receiver ID,
and Receiver Qualifier form a unique combination among GS Pairs and among interchange sender/receiver
pairs.

EDIFTN.000040.000010 Could not add envelope. GS Pair already exists, for that Sender ID, Sender Qualifier, Receiver ID,
Receiver Qualifier, production mode combination.
Cause: The webMethods EDI Module could not add a row to the EDIEnvelopeInfo table for the interchange
sender/receiver pair that you specified because a GS Pair already exists in the EDIGroup table for the
sender/receiver pair that you specified using the Sender ID, Sender Qualifier, Receiver ID, and Receiver
Qualifier combination. The EDIEnvelope and EDIGroup tables are EDI Module-specific tables in the Trading
Networks database.
Response: Ensure the values you specify for Sender ID, Sender Qualifier, Receiver ID, and Receiver Qualifier
form a unique combination among interchange sender/receiver pairs and among GS Pairs.

EDIFTN.000040.000011 Result Set has expired from cache, please re-run your search
Cause: The results of your search, which were stored in cache, have expired.
Response: Perform the search again.

EDIFTN.000040.000012 Control number minimum cannot be greater than the control number cap
Cause: When configuring the control number minimum and cap, the minimum value was set to be greater than
the cap value.
Response: Make sure the control number minimum is less than the control number cap.

EDIFTN.000040.000013 Expected control number cannot be greater than the control number cap
Cause: Expected control number is greater than the control number cap.
Response: Increase the control number cap value.

EDIFTN.000040.000014 Expected control number cannot be less than the control number minimum
Cause: Expected control number is less than the control number minimum.
Response: Decrease the control number minimum value.

260 webMethods Error Message Reference Version 6.5 and 6.5.1

EDIFTN (WmEDIforTN Package)

EDIFTN.000040.000015 Control number window must be smaller than (control number cap - control number minimum)
divided by 2
Cause: Control number window is not less than the control number cap minus the control number minimum,
divided by 2. For example, control number cap and minimum equals 20000 and 10000, respectively. Control
number window must be less than 5000.
Response: Make sure the control number window value does not allow the control number to go out of range
by setting the appropriate control number minimum and cap.

EDIFTN.000040.000016 Control number cannot be <new number> with minimum <minimum value> and increment value of
<increment value>
Cause: The control number values are incorrect.
Response: Make sure the control number increment is set correctly.

EDIFTN.000040.000017 Value `<the value>` is not a valid long value

Cause: The value specified is not a long number.
Response: Make sure the value is a Java primitive type of long.

EDIFTN.000040.000018 Value `<the value>` is not a valid integer value

Cause: The value specified is not an integer.
Response: Make sure the value is an integer.

EDIFTN.000040.000020 Fail to lock - no row exists for TN document ID: <document id>.
Cause: The row does not exist.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages\WmEDIforTN\config directory.

EDIFTN.000040.000022 Fail to lock - it is already locked (TN document id: <document id>)
Cause: The row is locked.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages\WmEDIforTN\config directory.

webMethods Error Message Reference Version 6.5 and 6.5.1 261

CHAPTER 3 webMethods EDI Module

262 webMethods Error Message Reference Version 6.5 and 6.5.1

CHAPTER 4
webMethods EDIINT Module

EDIINT.000001.000002 Invalid Number format for EDIINT large document size: <documentSize>
Cause: The number specified for the BigDocThreshold property in the Trading Networks property file is not
valid. This property determines the document size that is considered large for an EDIINT document.
Response: Update the BigDocThreshold property in the
webMethods\IntegrationServer\packages\WmTN\config\properties.cnf file to make it valid.

EDIINT.000001.000003 Invalid input - <paramName>

Cause: The specified input parameter is not a valid parameter.
Response: Update the input to specify valid parameters.

EDIINT.000001.000004 Invalid URI - <uriName>, missing :\

Cause: The URL format is not valid because it is missing ':\'.
Response: Correct the URL format.

EDIINT.000001.000005 Unrecognized input object - <paramName>, <suggestAction>

Cause: The specified input object is not valid because it is not recognized.
Response: Take the action specified in the message.

EDIINT.000001.000006 messageDigestHolder is 0 size

Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

webMethods Error Message Reference Version 6.5 and 6.5.1 263

CHAPTER 4 webMethods EDIINT Module

EDIINT.000001.000007 Unknown encoding: <styleName>

Cause: The specified encoding type <encodingTypeName> is not supported.
Response: Specify a supported encoding type.

EDIINT.000001.000008 Invalid AS2 Identify: [<AS2ID>]

Cause: The input message contains an AS2 ID that has an invalid format.
Response: Correct the input message.

EDIINT.000001.000009 Invalid AS2 quoted Identify: [<AS2ID>]

Cause: The input message contains a quoted AS2 ID that uses an invalid format.
Response: Correct the input message.

EDIINT.000001.000012 Unsupported protocol - [<URI_string>]

Cause: The webMethods EDIINT Module received a URI string that contains HTTP, SMTP, or FTP protocol
information. However, the protocol in the URI string is not valid.
Response: Determine where the information used to form the URI string came from and correct the problem.
For example, for an outbound EDIINT message, the webMethods EDIINT Module forms the URI string using
EDIINT extended fields from the Trading Networks profile. In this case, you would review the profile and
make corrections to the EDIINT extended fields. For an inbound EDIINT message, you need to contact the
partner that sent the EDIINT message. If you cannot resolve the issue, contact webMethods Customer Care for
assistance.

EDIINT.000002.000003 Could not register EDIINT Attribute - <attributeName>

Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIINT.000002.000004 Could not register EDIINT MDN Attribute - <attributeName>

Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIINT.000002.000011 Error in creating EDIINT BizDocEnvelope, <errorMessage>

Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

264 webMethods Error Message Reference Version 6.5 and 6.5.1

EDIINT.000002.000012 Error in creating EDIINT MDN BizDocEnvelope, <errorMessage>
Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIINT.000002.000013 Could not register EDIINT Processing services, <serviceName>

Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIINT.000002.000014 Could not register EDIINT Processing services, <serviceName>

Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIINT.000002.000020 Could not get partner's internal ID for <externalID>

Cause: There is no matching Trading Networks internal profile ID for the specified input partner ID.
Response: Check the specified input partner ID to ensure it is correct.

EDIINT.000002.000024 Missing Message-ID

Cause: The input message does not contain a message ID.
Response: Correct input data.

EDIINT.000002.000025 Not Supported

Cause: You attempted to resubmit an EDIINT message from the Trading Networks Console. However, the
EDIINT message was not an outbound message. The webMethods EDIINT Module only supports
resubmitting outbound EDIINT messages.
Response: To resubmit an EDIINT message, select an outbound EDIINT message.

EDIINT.000002.000026 Could not relate to submitted payload

Cause: The webMethods EDIINT Module attempted to relate the EDIINT message to the EDIINT payload.
However, the BizDocEnvelope for the EDIINT payload was either not saved to the Trading Networks
database, or Trading Networks encountered another error with the payload document.
Response: See the Trading Networks activity log and/or the server log for more information. If you want the
webMethods EDIINT Module to be able to relate the EDIINT message to the payload that it contained, the
processing rule for the payload must indicate that the payload be saved to the Trading Networks database.

webMethods Error Message Reference Version 6.5 and 6.5.1 265

CHAPTER 4 webMethods EDIINT Module

EDIINT.000002.000027 Payload BizDocEnvelope object does not exist

Cause: The BizDocEnvelope object for the EDIINT payload does not exist in the pipeline. This indicates an
internal error.
Response: Contact webMethods Customer Care for assistance. Please have the server log available.

EDIINT.000002.000028 Submitted payload [<TN_InternalDocID>] has not been persisted

Cause: The EDIINT payload was not saved to the Trading Networks database. This might be because the
processing rule for the payload document did not indicate to save the document.
Response: If you want the webMethods EDIINT Module to be able to relate the EDIINT message that contained
the payload to the payload itself, ensure that the processing rule for the payload document indicates to save
the document to the database.

EDIINT.000002.000030 Could not relate to submitted individual EDI envelope

Cause: The webMethods EDIINT Module received an EDIINT message that contains an EDI document with
multiple envelopes. The EDI TPA indicated that the EDI document with multiple payloads should not be
saved. As a result, the EDIINT Module could not relate EDIINT message with the original EDI document.
Alternatively, the EDIINT Module attempts to relate the EDIINT message to each individual EDI document
that was included in the original EDI document. To do so, the EDIINT Module looks for the
envelopeDocuments variable in the pipeline. This variable contains the Trading Networks internal IDs for
each individual EDI document. An error occurred that prevented the EDIINT Module from relating the
documents.
Response: See subsequent messages, the activity log, and server log for additional details for why the
documents could not be related.

EDIINT.000002.000031 Could not retreive EDI document summary information - envelopeDocuments

Cause: This message provides additional information after error message EDIINT.000002.000030 is displayed.
See the description for EDIINT.000002.000030.
The reason the EDIINT Module could not relate the documents was because it could not find the
envelopeDocuments variable in the pipeline.
Response: Contact webMethods Customer Care for assistance. Please have the server log and activity log
available.

EDIINT.000002.000032 Could not relate to submitted EDI envelope [<TN_internalDocID>]

Cause: This message provides additional information after error message EDIINT.000002.000030 is displayed.
See the description for EDIINT.000002.000030.
Response: See the server log and activity log for more information.

266 webMethods Error Message Reference Version 6.5 and 6.5.1

EDIINT.000002.000033 Could not retreive docId from envelopeDocuments
Cause: This message provides additional information after error message EDIINT.000002.000030 is displayed.
See the description for EDIINT.000002.000030.
The EDIINT Module located the envelopeDocuments variable in the pipeline; however, it does not contain
Trading Networks internal IDs.
Response: Contact webMethods Customer Care for assistance. Please have the server log and activity log
available.

EDIINT.000002.000034 Could not retreive EDI BizDocEnvelope [<TN_internalDocID>]

Cause: This message provides additional information after error message EDIINT.000002.000030 is displayed.
See the description for EDIINT.000002.000030.
The EDIINT Module located the envelopeDocuments variable in the pipeline and it appears to contain
Trading Networks internal IDs. However, the Trading Networks cannot provide information about the
document.
Response: Contact webMethods Customer Care for assistance. Please have the server log and activity log
available.

EDIINT.000002.000035 EDI BizDocEnvelope [<TN_internalDocID>] has not been persisted

Cause: This message provides additional information after error message EDIINT.000002.000030 is displayed.
See the description for EDIINT.000002.000030.
The EDIINT Module located the envelopeDocuments variable in the pipeline and it contains Trading
Networks internal IDs. However, the EDI documents identified by the internal IDs were not saved to the
Trading Networks database.
Response: Contact webMethods Customer Care for assistance. Please have the server log and activity log
available.

EDIINT.000002.000037 Could not delete file from User Outbox folder [<detailReason>]
Cause: The EDIINT Module was not able to delete the file that contains an AS3 message from the user outbox.
Response: See subsequent messages, the activity log, and server log for additional details for why the
documents could not be related. If you cannot resolve the issue, contact webMethods Customer Care for
assistance.

EDIINT.000002.000038 [<fileName>] is not child of [<userFTPHomeDirectory>]

Cause: This message provides additional information after error message EDIINT.000002.000038 is displayed.
The file that contains the AS3 message to be deleted is not a child of the user’s FTP home directory. This
indicates an internal error.
Response: Contact webMethods Customer Care for assistance.

webMethods Error Message Reference Version 6.5 and 6.5.1 267

CHAPTER 4 webMethods EDIINT Module

EDIINT.000002.000062 Could not create EDIINT ID Types - [<detailErrorMessage>]

Cause: Could not create EDIINT external ID types in the Trading Networks database due to a database error.
Response: Contact your database administrator. If you are unable to resolve the issue, contact webMethods
Customer Care for assistance.

EDIINT.000004.000006 Error get Content LengthHandler - <errorMessage>

Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

EDIINT.000005.000002 Error loading EDIINT Properties file - <fileName>

Cause: EDIINT properties file is found, but could not be loaded correctly.
Response: Check the content of the properties.cnf file, which is located in the
webMethods\IntegrationServer\packages\WmEDIINT\config directory.

EDIINT.000005.000003 EDIINT Properties file - <fileName> is not exists

Cause: <fileName> file cannot be found.
Response: Ensure that <fileName> exists.

EDIINT.000005.000005 Error saving EDIINT Properties file - <fileName>

Cause: The EDI Module was unable to save the <fileName> properties file after making changes to it.
Response: Check the security of the <fileName> properties file.

EDIINT.000006.000001 Cannot handle datasource of type: <dataType>

Cause: The data type of the input Object type is not the data type that was expected. For example, an EDIINT
message might have been expected, but the input data is not an EDIINT message.
Response: Use a supported data type for the input Object.

EDIINT.000006.000002 Cannot handle null datasource

Cause: An input parameter is null.
Response: Try again, this time specifying an input parameter that is not null.

EDIINT.000006.000003 Unable to parse message

Cause: Internal Error
Response: Contact webMethods Customer Care for assistance.

268 webMethods Error Message Reference Version 6.5 and 6.5.1

EDIINT.000006.000004 Cannot Process this object.
Cause: Write this MimeData to stream, then process that stream. The input is not MimeData that has already
been parsed. This is an internal error.
Response: Contact webMethods Customer Care for assistance.

EDIINT.000006.000005 Input parameter mimeSrc should be of type MimeData

Cause: The data type of the input parameter 'mimeSrc' is incorrect. It is not MimeData.
Response: Make sure you use the data type MimeData with the 'mimeSrc' input parameter.

EDIINT.000006.000006 Message Digest Algorithm <digestAlgorithmName> is not supported

Cause: The webMethods EDI Module does not support the <digestAlgorithmName> message digest algorithm.
Response: Specify a supported message digest algorithm.

EDIINT.000006.000007 Cannot process message that is not javax.mail.internet.MimeMessage or

javax.mail.internet.MimeBodyPart.
Cause: The format of the input message is not supported.
Response: Check input message. Be sure it is either in MimeMessage or MimeBodyPart format.

webMethods Error Message Reference Version 6.5 and 6.5.1 269

CHAPTER 4 webMethods EDIINT Module

270 webMethods Error Message Reference Version 6.5 and 6.5.1

CHAPTER 5
webMethods Flat File Package

FFP (Flat File) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

FPL (File Polling) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

webMethods Error Message Reference Version 6.5 and 6.5.1 271

CHAPTER 5 webMethods Flat File Package

FFP (Flat File)

FFP.0000.0000 Could not find file: <fileName>

Cause: The specified SEF file does not exist.
Response: Ensure that the specified SEF file exists in the specified location. If it does not, either 1) move the SEF
file to or create the SEF file in the specified location, or 2) specify the correct location.

FFP.0000.0001 SEF format error

Cause: The format of the SEF file is not valid. The SEFParse service expects the first line of a SEF file to be '.INI'
or '.VER'. The SEFParse service does not support other values.
Response: Update the format of the SEF file service to make it valid.

FFP.0000.0002 Transaction set not defined: <transactionSetName>

Cause: The SEF file does not contain the transaction set specified by the input parameter 'EDIDocName'.
Response: Check the value of the input parameter 'EDIDocName'. Determine whether the value specified by
the 'EDIDocName' parameter is defined in the '.SETS' section of the SEF file that is identified by the
'SEFfileName' parameter. Either 1) the 'EDIDocName' parameter has been mistyped, or 2) the transaction set
does not exist in the given SEF file.

FFP.0000.0003 Error parsing validator for element : <elementName>; <errorMsg>

Cause: The system was unable to parse the code list for element <elementName>.
Response: Additional details about this error are provided in the message. Take appropriate actions to resolve
the error.

FFP.0000.0004 Nested [
Cause: An error occurred parsing a definition in a SEF file. Two open bracket characters ('[') occurred without a
close bracket character (']').
Response: Check the format of the SEF file to ensure that nested levels are formatted correctly. Correct all
nesting errors.

FFP.0000.0005 Invalid field reference, no element name found before ']' character encountered. Ref = '<elementName>'
Cause: An error occurred parsing a definition in a SEF file. No valid reference was found.
Response: Update the invalid field reference in the SEF file by specifying an element name.

272 webMethods Error Message Reference Version 6.5 and 6.5.1

FFP (Flat File)

FFP.0000.0006 Invalid element declaration: <elementName>. Value = `<elementText>`

Cause: The SEF file contains an illegally formed reference in a segment or transaction set definition. References
can contain three comma separated fields. This reference contains more than three comma separated fields.
Response: Update the SEF file to correct the invalid segment or transaction set definition. Ensure that the
reference contains only three comma separated fields.

FFP.0000.0007 Trying to reset ordinal number

Cause: The system could not reset the ordinal number in a segment or element reference because the new
ordinal value was not specified. The reference contained an '@' without a number.
Response: Update the SEF file to specify an ordinal number after the '@'.

FFP.0000.0008 Too many ',' characters in element <elementName>

FFP.0000.0009 Unexpected '@' in element <elementName>

Cause: An '@' character appeared in an unexpected location in a segment or element reference.
Response: Locate the segment or element reference in the SEF file and either 1) remove the unexpected '@'
character or 2) supply the missing information to complete the definition.

FFP.0000.0010 Unexpected end of definition

Cause: A segment or element reference ended unexpectedly. A segment or transaction set definition contains a
reference without a closing bracket `]` character.
Response: Update the SEF file to correct the invalid segment or transaction set definition. Ensure references in
the definitions contain closing brackets.

FFP.0000.0011 Unable to find definition

Cause: A transaction set definition contains a reference to a segment that is not defined in this SEF file.
Response: Check the SEF file for errors, and make the necessary corrections.

webMethods Error Message Reference Version 6.5 and 6.5.1 273

CHAPTER 5 webMethods Flat File Package

FFP.0000.0012 Can`t have optional repeating element followed by mandatory element

Cause: A segment definition contains an optional repeating element followed by a mandatory element. This
structure cannot be parsed properly because repeating elements followed by a mandatory element is not
supported.
Response: Modify the source you are trying to parse.

FFP.0000.0013 Could not find referenced node: <nodeReference>

Cause: A segment definition contains a reference to an element that is not defined in the given SEF file.
Response: Check the SEF file for errors, and make the necessary corrections.

FFP.0000.0014 Error parsing <elementType> definition: <elementName> <errorMessage>

Cause: An error occurred when parsing a segment definition. The message should contain additional error
code(s) detailing the reason for the error.
Response: Check the additional error code(s) specified in this message.

FFP.0000.0015 Unable to determine envelope information

Cause: The user set the input parameter 'includeEnvelope' to true, but the system was unable to determine the
envelope information to use for the given transaction set definition.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages\WmFlatFile\config directory.

FFP.0000.0016 Found unexpected: `^`. Starting new area prior to closing segment. Expecting `]`
Cause: The SEF file contains the character `^` in an illegal location.
Response: Check the SEF file for errors, and make the necessary corrections.

FFP.0000.0017 Found nested Segment definitions

Cause: An error occurred parsing a transaction definition in a SEF file. Two open bracket characters (`[`)
occurred without a close bracket character (`]`).
Response: Check the SEF file for errors, and make the necessary corrections.

FFP.0000.0018 Found unmatched `]`

Cause: Character `]` occurred in SEF file without a starting `]` character.
Response: Check the SEF file for errors, and make the necessary corrections.

274 webMethods Error Message Reference Version 6.5 and 6.5.1

FFP (Flat File)

FFP.0000.0019 Found nested anonymous loops, as identified by `{{` : can`t define structure to parse this
Cause: Two `{{` characters where found together in the SEF file.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages\WmFlatFile\config directory.

FFP.0000.0020 Unexpected `{` character. Loop occurring in segment definition

Cause: The character '{' occurs in an unexpected location in a segment definition.
Response: Check the SEF file for errors, and make the necessary corrections.

FFP.0000.0021 Loop Contains no segments

Cause: The SEF file contains a loop definition that is empty; that is, it contains no segments.
Response: Check the SEF file for errors, and make the necessary corrections.

FFP.0000.0022 Found loop close `}` in segment definition. Expecting `]`

Cause: The character '}' occurs in an unexpected location in a segment definition.
Response: Check the SEF file for errors, and make the necessary corrections.

FFP.0000.0023 Unable to parse number [<unparsableNumber>]

Cause: The <unparsableNumber> value specified in the message is not a valid number.
Response: Check the SEF file for errors, and make the necessary corrections.

FFP.0000.0024 No sets defined in SEF file

Cause: The SEF file has no transaction set definitions.
Response: Check the SEF file for errors, and make the necessary corrections.

FFP.0000.0025 Set not defined: <badSet>

Cause: Either the SEF file does not contain the transaction set specified by the input parameter 'EDIDocName',
or the 'EDIDocName' parameter has been mistyped.
Response: Ensure that the 'EDIDocName' was specified correctly. If it was, determine whether the value of the
'EDIDocName' parameter is defined in the '.SETS' section of the SEF file that is specified by the 'SEFfileName'
parameter.

webMethods Error Message Reference Version 6.5 and 6.5.1 275

CHAPTER 5 webMethods Flat File Package

FFP.0000.0026 Unable to find Flat File Dictionary: <dictionaryName>

Cause: The value of the input parameter 'targetDictionary' is not valid.
Response: Check the value specified for the 'targetDictionary' parameter. Determine whether the value is
specified correctly. If the value is specified correctly, no flat file dictionary exists with that name. Create a flat
file dictionary and re-run the SEFParse service.

FFP.0000.0027 Unable to parse Transaction set <setName>: <reason>

Cause: An error occurred parsing a transaction set.
Response: This message should contain additional error codes. Reference those codes for more information
about the cause of this error.

FFP.0000.0028 Number format error trying to parse element: <elementName>

Cause: The element definition contains a number that cannot be parsed.
Response: Check the SEF file for errors, and make the necessary corrections.

FFP.0000.0029 Cannot parse a transaction that contains consecutive loops with the same name. This transaction contains
two consecutive loops called: <segment name>.
Cause: The transaction set defined within the SEF file contains two or more consecutive loops with the same
starting segment.
Response: Modify the SEF file to remove the consecutive loops.

FFP.0000.0031 Illegal SEF file. Cannot have an LS segment starting a loop. The construct \"{[LS]...\" is not supported.
Cause: In a SEF file, an LS segment cannot start a loop.
Response: Modify the SEF file to remove the LS segment that starts a loop.

FFP.0001.0001 Type not allowed <badType>, must be <allowedType>

Cause: Attempted to set the default record for a flat file schema to a composite or field instead of a record as
required.
Response: Specify a record instead of a composite or field.

FFP.0001.9001 Child at index [<position>] is cannot be added to this row.

Cause: Internal Error
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages\WmFlatFile\config directory.

276 webMethods Error Message Reference Version 6.5 and 6.5.1

FFP (Flat File)

FFP.0001.9002 Cannot add child

FFP.0001.9003 Cannot add child

FFP.0001.9004 Cannot put a record inside another record

FFP.0001.9005 Cannot add unknown type to a record

FFP.0001.9006 Fields cannot have children

FFP.0001.9007 Composites cannot contain composites

webMethods Error Message Reference Version 6.5 and 6.5.1 277

CHAPTER 5 webMethods Flat File Package

FFP.0001.9008 Cannot add record to a composite

FFP.0001.9009 Cannot add unknown type to a composite

FFP.0001.9010 Cannot add child

FFP.0001.9011 Cannot add children to detail view

FFP.0001.9012 Cannot add children to detail view

FFP.0001.9013 Cannot add child of type: <elementType>

278 webMethods Error Message Reference Version 6.5 and 6.5.1

FFP (Flat File)

FFP.0001.9014 The first child of the Record Usage must be the Record Definition
Cause: Internal Error
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages\WmFlatFile/\config directory.

FFP.0001.9015 Cannot set the children of a usage node. The only child is the used node definition
Cause: Internal Error
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages\WmFlatFile\config directory.

FFP.0001.9016 Node is not editable

FFP.0001.9017 Cannot modify the children of a reference

FFP.0001.9018 Cannot add child. Child must be of type: <elementType>

FFP.0001.9019 Cannot add node, node with name <nodeName> already exists
Cause: Internal Error
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages\WmFlatFile\config directory.

webMethods Error Message Reference Version 6.5 and 6.5.1 279

CHAPTER 5 webMethods Flat File Package

FFP.0001.9020 Cannot edit a broken link

FFP.0001.9021 Server cannot be null

FFP.0002.0000 Invalid syntax rule

Cause: The syntax rule is not valid.
Response: For more details about syntax rules, see the section on Conditional Validators in the "Flat File
Schema Developer's Guide."

FFP.0002.0001 Invalid Conditional format

Cause: The syntax rule is not valid.
Response: For more details about syntax rules, see the section on Conditional Validators in the "Flat File
Schema Developers Guide."

FFP.0003.0000 Delimiters not set

Cause: The parser could not determine the delimiters to use.
Response: This error only occurs when using an EDIRecordParser. Ensure that the input source contains the
transaction header segment (ISA, UNA, or UNB). If the input data does not contain the transaction header
segment, the delimiters must be specified in the input parameter delimiters of the convertToValues service.

FFP.0003.0001 Maximum Record size (<maxRecordSize>) exceeded

Cause: The user configured a maximum record size for the delimiter parser. A record was encountered in the
input source that exceeded this size.
Response: Reconfigure the maximum record size to increase it, or modify the records in the input source to
make them smaller.

280 webMethods Error Message Reference Version 6.5 and 6.5.1

FFP (Flat File)

FFP.0005.0003 Unknown type <typeName>

Cause: A Node Definition with an unknown type was encountered.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages\WmFlatFile\config directory.

FFP.0008.0000 Invalid composite extractor

FFP.0008.0006 Invalid input, cannot be negative number: <badNumber>

Cause: The user specified a negative number for a Fixed Position Extractor.
Response: When specifying a Fixed Position Extractor, specify a non-negative integer.

FFP.0009.0001 Definition of type <definitionType> called `<definitionName>` not found in Dictionary <dictionaryName>
Cause: An element references a definition that does not exist.
Response: Create the referenced definition, or delete the reference and create a new reference that points to an
existing definition.

FFP.0010.0001 Lengths in Partition segment do not match: `<partitionString>`

Cause: A partition has been specified incorrectly.
Response: For more details on specifying a partition, see the section on partitions, under Code List Validator, in
the "Flat File Schema Developers Guide."

FFP.0010.0002 Range values cannot be null

Cause: A range has been specified with a null start or end.
Response: Check the range definition for a ':' and ensure that there is a valid value on each side of the colon. For
more details, see the section on ranges, under Code List Validator, in the "Flat File Schema Developers Guide."

FFP.0010.0003 Range lengths do not match start = `<startLength>`, end = `<endLength>`

Cause: The start length is different from the end length.
Response: Specify a range where the string prior to the colon is the same length as the string following the
colon. For more details, see the section on ranges, under Code List Validator, in the "Flat File Schema
Developers Guide."

webMethods Error Message Reference Version 6.5 and 6.5.1 281

CHAPTER 5 webMethods Flat File Package

FFP.0010.0007 Minimum value cannot be negative

Cause: The minimum value that was specified for a length validator is negative.
Response: Change the minimum value for the length value to a non-negative integer.

FFP.0010.0008 Maximum value cannot be less than minimum value

Cause: The maximum valid length that was specified for a length validator is not greater than the value
specified for the minimum length value.
Response: Specify a maximum valid length that is greater than or equal to the minimum valid length. Note that
you can specify a -1 for the maximum valid length to indicate that there is no limit to how long the field can be.

FFP.0010.0009 Ranges only support characters in the ranges a-z, A-Z or 0-9
Cause: The range contains a character outside the allowed values.
Response: Update the range to include only characters from a-z, A-Z, or 0-9. For more details, see the section on
ranges, under Code List Validator, in the "Flat File Schema Developers Guide."

FFP.0011.0001 Parse Error at: <recordNumber> reference = <recordName>

Cause: The source data contained an element that is not valid.
Response: Check the input data for errors

FFP.0011.0004 Element too long

Cause: A field is longer than the maximum length specified in a length validator.
Response: Determine whether the error is due to an improperly specified flat file schema or invalid input data.
If the flat file schema definition is invalid, modify the flat file schema. Otherwise the input data does not meet
the validation criteria of the flat file schema and an appropriate, business specific, action should be taken.

FFP.0011.0005 Element too short

Cause: A field is shorter than the minimum length specified in a length validator.
Response: Determine whether the error is due to an improperly specified flat file schema or invalid input data.
If the flat file schema definition is invalid, modify the flat file schema. Otherwise the input data does not meet
the validation criteria of the flat file schema and an appropriate, business specific, action should be taken.

FFP.0011.0008 Invalid date

Cause: The input data in a date field does not meet the format specified by a format service.
Response: Determine whether the error is due to an improperly specified flat file schema or invalid input data.
If the flat file schema definition is invalid, modify the flat file schema. Otherwise the input data does not meet
the validation criteria of the flat file schema and an appropriate, business specific, action should be taken.

282 webMethods Error Message Reference Version 6.5 and 6.5.1

FFP (Flat File)

FFP.0011.0009 Invalid time

Cause: The input data in a time field does not meet the format specified by a format service.
Response: Determine whether the error is due to an improperly specified flat file schema or invalid input data.
If the flat file schema definition is invalid, modify the flat file schema. Otherwise the input data does not meet
the validation criteria of the flat file schema and an appropriate, business specific, action should be taken.

FFP.0011.0010 Exclusion condition(s) violated: <conditionNumbers>

Cause: The input data in a record or composite does not meet the restrictions specified by a Conditional
Validator.
Response: Determine whether the error is due to an improperly specified flat file schema or invalid input data.
If the flat file schema definition is invalid, modify the flat file schema. Otherwise the input data does not meet
the validation criteria of the flat file schema and an appropriate, business specific, action should be taken.

FFP.0011.0011 Unrecognized element

Cause: A record appeared in the document that is not defined in the flat file schema.
Response: Determine whether the error is due to an improperly specified flat file schema or invalid input data.
If the flat file schema definition is invalid, modify the flat file schema. Otherwise the input data does not meet
the validation criteria of the flat file schema and an appropriate, business specific, action should be taken.

FFP.0011.0012 Unexpected element

Cause: A record appeared in the document in a place where it is not allowed according to the flat file schema.
Response: Determine whether the error is due to an improperly specified flat file schema or invalid input data.
If the flat file schema definition is invalid, modify the flat file schema. Otherwise the input data does not meet
the validation criteria of the flat file schema and an appropriate, business specific, action should be taken.

FFP.0011.0014 Maximum occurs exceeded

Cause: A record appeared in the document more times than allowed by the flat file schema.
Response: Determine whether the error is due to an improperly specified flat file schema or invalid input data.
If the flat file schema definition is invalid, modify the flat file schema. Otherwise the input data does not meet
the validation criteria of the flat file schema and an appropriate, business specific, action should be taken.

webMethods Error Message Reference Version 6.5 and 6.5.1 283

CHAPTER 5 webMethods Flat File Package

FFP.0011.0016 Element has nested errors

Cause: One of the following occurred:
1) A record contains a field or composite that has one or more validation errors. Or
2) A composite contains a subfield that has one or more validation errors.
Response: Determine whether the error is due to an improperly specified flat file schema or invalid input data.
If the flat file schema definition is invalid, modify the flat file schema. Otherwise the input data does not meet
the validation criteria of the flat file schema and an appropriate, business specific, action should be taken.

FFP.0011.0017 String could not be formatted properly. <failureReason>

Cause: A formatting service has been invoked on a given field and determined that the value of the field cannot
be formatted properly.
Response: Determine whether the error is due to an improperly specified flat file schema or invalid input data.
If the flat file schema definition is invalid, modify the flat file schema. Otherwise the input data does not meet
the validation criteria of the flat file schema and an appropriate, business specific, action should be taken.

FFP.0011.0018 String could not be formatted properly.

FFP.0011.0099 Other error

Cause: Attempted to validate a field that does not contain a String value.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages\WmFlatFile\config directory.

FFP.0012.0001 Cannot have null NodeDefinition

Cause: An element reference in the flat file schema is broken.
Response: Check the flat file schema for broken references. Broken references should either be deleted and
recreated to reference an existing element definition, or the element that is referenced should be re-created.

FFP.0012.0002 Please specify a RecordParser for Flat File Schema: <flatFileSchemaName>

Cause: The flat file schema does not have a record parser specified.
Response: Using the webMethods Developer, specify a record parser for the flat file schema.

284 webMethods Error Message Reference Version 6.5 and 6.5.1

FFP (Flat File)

FFP.0012.0003 Please specify a Default Record or RecordIdentifier for Flat File Schema: <flatFileSchemaName>
Cause: A flat file schema must have either a default record or record identifier specified.
Response: Use the webMethods Developer to specify either a default record or record identifier for the flat file
schema

FFP.0012.0004 Found no valid records

Cause: The input source does not contain any records.
Response: Check that the flat file schema record names actually appear in the input source in the location
specified by the record identifier. Determine whether the error is due to an improperly specified flat file
schema or invalid input data. If the flat file schema definition is invalid, modify the flat file schema. Otherwise
the input data does not meet the validation criteria of the flat file schema and an appropriate, business specific,
action should be taken.

FFP.0013.0001 Error loading config file: <fileName>

Cause: The server was unable to load a configuration file that is used when parsing SEF files.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages\WmFlatFile\config directory.

FFP.0013.0002 Missing envelope start for standard: <standardName>

Cause: The configuration file used for parsing SEF files contains errors.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages\WmFlatFile\config directory.

FFP.0013.0003 Missing envelope end for standard: <standardName>

FFP.0013.0004 Missing document start for standard: <standardName>

webMethods Error Message Reference Version 6.5 and 6.5.1 285

CHAPTER 5 webMethods Flat File Package

FFP.0013.0005 Missing document end for standard: <standardName>

FFP.0013.0006 Missing envelope definition for standard: <standardName>

FFP.0013.0007 Missing SEF file `<fileName>` for stanard `<standardName>`

FFP.0013.0008 Configuration error: <errorText>

FFP.0014.0001 Variable Length Parser requires RawReader data source. Use convertToValues method to get RawReader
Cause: Internal Error
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages\WmFlatFile\config directory.

FFP.0014.0002 Variable Length file format invalid, could not read 2 bytes to determine record length
Cause: The variable length record parser requires that two bytes contain the length of the next record. These
two bytes could not be obtained.
Response: Check that the input data source is correct.

286 webMethods Error Message Reference Version 6.5 and 6.5.1

FFP (Flat File)

FFP.0014.0003 Variable Length file format invalid, file ended before record filled
Cause: The variable length record parser requires that two bytes contain the length of the next record. The
length specified by these two bytes is longer than the number of characters remaining in the input source.
Response: Check that the input data source is correct.

FFP.0014.0004 Variable Length Parser requires RawWriter data sink.

FFP.0015.0001 `<name>` is not a valid name. <reason>

Cause: The specified name is not a valid name.
Response: Specify a different name that contains only alpha-numeric characters.

FFP.0015.0002 `<name>` is not a valid name.

Cause: The specified name is not a valid name.
Response: Specify a different name that contains only alpha-numeric characters.

FFP.0015.0003 Cannot save changes to dictionary <flatFileDictionaryName>. Dictionary is not locked.

Cause: The system could not save the changes to dictionary specified in the message because that dictionary is
not locked.
Response: Lock the dictionary prior to making changes.

FFP.0015.0004 Cannot save changes to schema <flatFileSchemaName>. Schema is not locked.

Cause: The system could not save changes to the flat file schema specified in the message because the flat file
schema is not locked.
Response: Lock the flat file schema prior to making changes.

FFP.0015.0005 Specified an invalid schema `<flatFileSchemaName>`, is not a Flat File Schema.

Cause: The server attempted to retrieve a flat file schema, but the element specified is not a flat file schema.
Response: Check the spelling of the flat file schema name.

webMethods Error Message Reference Version 6.5 and 6.5.1 287

CHAPTER 5 webMethods Flat File Package

FFP.0015.0006 Cannot create flat file schema `<flat file schema name>` in package `<package name>`, package does not
exist.
Cause: Attempted to create a flat file schema in a package that does not exist.
Response: Check to make sure that the package name was specified correctly. If it was, create a new package
with that name.

FFP.0015.0006 Cannot create flat file schema `<flat file dictionary name>` in package `<package name>`, package does not
exist.
Cause: Attempted to create a flat file dictionary in a package that does not exist.
Response: Check to make sure that the package name was specified correctly. If it was, create a new package
with that name.

FFP.0016.0001 Record Identifier cannot use a negative value

Cause: A record identifier uses a negative value.
Response: Update the value for the record identifier to use a non-negative integer.

FFP.0017.0000 Character location cannot be a negative value

Cause: The character location is a negative value.
Response: Update the character location to use a non-negative integer.

FFP.0019.0001 Unable to obtain delimiters. Input source too short.

Cause: The user has specified that a delimiter or release character occurs at a specific character count within the
input data source. That count is greater than the total number of characters in the input data source.
Response: Determine whether the error is due to an improperly specified flat file schema or invalid input data.
If the flat file schema definition is invalid, modify the flat file schema. Otherwise the input data does not meet
the validation criteria of the flat file schema and an appropriate, business specific, action should be taken.

FFP.0020.0000 Please specify a value.

Cause: A delimiter character value was not specified.
Response: Specify a delimiter character value.

FFP.0020.0001 String contains too many characters: `<value specified>`.

Cause: The delimiter character was specified as a string containing more than one character.
Response: Specify only a single character for the delimiter.

288 webMethods Error Message Reference Version 6.5 and 6.5.1

FFP (Flat File)

FFP.0020.0002 Specified an invalid number format: `<value specified>`.

Cause: The specified value is not a number.
Response: Specify an integer value.

FFP.0020.0003 Invalid unicode escape: `<invalid unicode escape>`. Must follow format \uXXXX.
Cause: The specified unicode escape sequence is invalid.
Response: Specify a valid unicode escape sequence. The valid format is '\uXXXX', where X is a digit.

FFP.0020.0004 Please specify a single character. Invalid input: `<invalid input>`.

Cause: The delimiter character was specified as a string containing more than one character.
Response: Specify a single character for the delimiter.

FFP.0020.0005 Cannot handle escape type: `<invalid input>`. Allowed values are : `\n`, `\t`, `\r`, `\f`, `\'` and `\\"`.
Cause: The specified escape sequence for a delimiter character is invalid.
Response: Specify a single character or one of the valid escape characters: `\n`, `\t`, `\r`, `\f`, `\'` or '\\'.

FFP.0020.0006 Hexidecimal string must take the form `0xZZ`. String `<invalid input>` is not a valid hex string.
Cause: The specified hexidecimal format is invalid.
Response: Specify a valid hexidecimal string. The valid format is '0xZZ', where Z is a digit.

FFP.0020.0007 Ocatal string must take the form `0xZ`. String `<invalid input>` is not a valid octal string.
Cause: The specified octal format is invalid.
Response: Specify a valid octal string. The valid format is '0xZ', where Z is a digit.

FFP.0020.0008 Cannot encode the delimiter character `<character>` (U+<unicodeValueForCharacter>) using specified
encoding: <encoding>}. Please select a different delimiter character.
Cause: The delimiter character cannot be converted to bytes using the specified encoding.
Response: Specify a different delimiter character that is valid for the specified encoding, or select an encoding
that can represent the selected delimiter character.

webMethods Error Message Reference Version 6.5 and 6.5.1 289

CHAPTER 5 webMethods Flat File Package

FFP.0021.0000 An error occurred parsing a fixed length record. The record terminated in the middle of a multi-byte
character.
Cause: Either the flat file is not properly formed or the wrong encoding was used to parse the flat file.
Response: Contact the creator of the flat file to determine the correct encoding used to parse the file and to
ensure that the file is created correctly.

FFP.0021.0001 An error occurred parsing the file. Unable to decode the input data using the specified encoding.
Cause: Unable to decode the input data using the specified encoding.
Response: Specify the correct encoding.

FFP.0022.0000 The character `<character>` cannot be used as a pad character. It encodes to more than one byte in the
encoding <encoding>.
Cause: The specified pad character encodes to more than a single byte. The pad character must encode to a
single byte.
Response: Specify a pad character that encodes to a single byte, or specify an encoding where the selected pad
character encodes to a single byte.

FFP.0100.0001 No condition string definied for the conditional validator

Cause: The XML file did not contain a string in the conditional validator.
Response: Specify a valid string for the conditional validator.

FFP.0100.0002 No record defined

Cause: No <Record> was defined within a <RecordUsage> tag.
Response: Specify a valid <Record> in the <RecordUsage> tag.

FFP.0100.0003 No definition
Cause: The dictionary entry did not contain a valid definition.
Response: Specify a valid definition in the dictionary entry.

FFP.0100.0004 Internal Error: Unable to handle type: <invalid type>.

Cause: The type of field specified is invalid.
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages\WmFlatFile\config directory.

290 webMethods Error Message Reference Version 6.5 and 6.5.1

FFP (Flat File)

FFP.0100.0005 Unable to handle recordIdentifier of type: <invalid type>.

Cause: Internal error
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages\WmFlatFile\config directory.

FFP.0100.0006 Code list validatior contained no valid choices

Cause: The code list validator contained no valid choices.
Response: No action is required - this is a warning message.

FFP.0100.0007 Composite does not contian any subfields.

Cause: The composite does not contain any subfields.
Response: No action is required - this is a warning message.

FFP.0100.0008 Cannot contain both a definition and a reference.

Cause: The XML file is invalid. It cannot contain both a definition and a reference.
Response: Remove either the definition or reference from the XML file.

FFP.0100.0009 A <RecordElement> tag cannot have both a <CompositeUsage> and a <FieldUsage> tag
Cause: A <RecordElement> tag cannot have both a <CompositeUsage> and a <FieldUsage> tag.
Response: Remove either the <CompositeUsage> or the <FieldUsage> tag from the <RecordElement> tag.

FFP.0100.0010 A field can only have one validator

Cause: The field contains more than one validator.
Response: Modify the field definition to contain one validator.

FFP.0100.0011 A field can only have one extractor

Cause: The field contains more than one extractor.
Response: Modify the field definition to contain one validator.

FFP.0100.0012 Too many record parsers defined. A <RecordParser> tag can only contain one record parser.
Cause: Too many record parsers were defined. A <RecordParser> tag can contain only one record parser.
Response: Modify the XML file to contain one RecordParser tag.

webMethods Error Message Reference Version 6.5 and 6.5.1 291

CHAPTER 5 webMethods Flat File Package

FFP.0100.0013 Too many record identifiers defined. A <RecordIdentifier> tag can only contain one record identifier.
Cause: Too many record identifiers were defined. A <RecordIdentifier> tag can contain only one record
identifier.
Response: Modify the XML file to contain one RecordIdentifier tag.

FFP.0100.0014 Flat file schema must have a record identifier defined.

Cause: The flat file schema must have a record identifier defined.
Response: Specify a record identifier in the XML file.

FFP.0100.0015 Flat file schema must have a record parser defined.

Cause: The flat file schema must have a record parser defined.
Response: Specify a record parser in the XML file.

FFP.0100.0016 Value {0} must be integer greater than or equal to zero.

Cause: The specified tag contains an invalid value.
Response: Specify a value that is greater than or equal to zero.

FFP.0100.0017 <MaxOccur> value must be either "Unlimited" or a positive integer greater than zero. `<invalid value>` is not
a valid value.
Cause: The <MaxOccur> value must be either 'Unlimited' or a positive integer greater than zero. '<invalid
value>' is not a valid value.
Response: Modify the value of the <MaxOccur> tag to be either 'Unlimited' or a positive integer greater than
zero.

FFP.0100.0018 <Position> value must be either "NoPosition" or an integer. `<invalid value>` is not a valid value.
Cause: The <Position> value must be either 'NoPosition' or an integer. '<invalid value>' is not a valid value.
Response: Modify the value of the <Position> tag to be either 'NoPosition' or an integer.

FFP.0100.0019 <Area> must be either "NoArea" or a positive integer greader than zero. `Invalid Value` is not a valid value.
Cause: The specified value of the <Area> tag is invalid.
Response: Modify the value of the tag <Area> to be either 'NoArea' or a positive integer greater than zero.

292 webMethods Error Message Reference Version 6.5 and 6.5.1

FFP (Flat File)

FFP.0100.0020 Value <value name> must be integer greater than or equal to one.
Cause: The specified tag contains an invalid value.
Response: Modify the value of the specified tag to be an integer greater than or equal to one.

FFP.0100.0021 Either <tag name 1> or <tag name 2> is required.

Cause: One of the two tags is required, but neither is present.
Response: Modify the XML file to contain one of the two required tags.

FFP.0100.0022 The end position (<end position value>) must be greater than the start position (<start position value>).
Cause: The start position specified for the fixed position extractor is greater than the end position.
Response: Modify the start and/or end position values so that the start position is less than the end position.

webMethods Error Message Reference Version 6.5 and 6.5.1 293

CHAPTER 5 webMethods Flat File Package

FPL (File Polling)

FPL.0001.0000 Error processing Cleanup service: <serviceName>

Cause: An error occurred during the execution of the user-specified cleanup service.
Response: Check the server error log for more detailed information. This error is most likely caused due to an
exception that occurred in the user-written, cleanup service, which is identified in the message.

FPL.0001.0001 Listener key not provided. Cleanup service not running

FPL.0001.0002 Cleanup service access denied. User <userName> not allowed to run service <serviceName>
Cause: The user specified in the message attempted to run the service specified in the message. However, the
specified user does not have the privileges to run the specified service.
Response: Modify the "Run services as user" parameter in the file polling listener configuration page to specify
a user that has the appropriate privileges. Make certain that the user you specify has the permissions to
execute the processing service.

FPL.0001.0003 Error processing service: <serviceName>

FPL.0001.0004 Could not delete file:<fileName> - <errorReason>

Cause: An error occurred while attempting to delete the specified file.
Response: Check the file system to determine why the indicated file has not been deleted. It might be necessary
to delete the file manually.

FPL.0001.0012 Could not move source file <srcFileName> to working directory <targetDirectoryName>
Cause: The system was unable to move the file from the monitoring directory to the working directory.
Response: On a Windows operating system this can be normal behavior because the operating system will not
allow a file to be moved while the file is being written to. For Windows, this is an error if the file listed is never
processed. On a non-Windows operating system, this error might occur because the source and destination
directories are on different file systems. Specify the source and destination directories to be on the same file
system.

294 webMethods Error Message Reference Version 6.5 and 6.5.1

FPL (File Polling)

FPL.0001.0013 Error processing monitoring file. <errorReason>.

Cause: An error occurred during the execution of the user-specified processing service.
Response: Check the server error log for more detailed information. This error is most likely caused due to an
exception that occurred in the user-written, cleanup service, which is identified in the message.

FPL.0001.0014 Error processing cleanup. <errorReason>.

FPL.0001.0020 Could not get canonical path for monitoring directory: <directoryName> - <errorReason>
Cause: The system could not obtain the canonical path for the monitoring directory, which is identified in the
message. The message also displays the reason.
Response: Take the appropriate action based on the reason for the error that is specified in the message.

FPL.0001.0030 Error processing file: <errorMessage>

FPL.0001.0031 Listener key not provided. File polling listener not running
Cause: Internal Error
Response: Contact webMethods Customer Care. Please have the following information available: server and
error logs, a copy of the Support Information page from the Developer, and the contents of the
packages\WmFlatFile\config directory.

FPL.0001.0032 File polling processing service access denied. User <userName> not allowed to run service <serviceName>
Cause: The specified user does not have privileges to run the indicated service.
Response: Modify the "Run services as user" parameter in the file polling listener configuration page to specify
a user that has the appropriate privileges. Make certain that the user you specify has the permissions to
execute the processing service.

FPL.0001.0033 Error processing service: <errorReason>

webMethods Error Message Reference Version 6.5 and 6.5.1 295

CHAPTER 5 webMethods Flat File Package

FPL.0001.0034 Could not move file to finished directory. <errorReason>

Cause: The system was unable to move the file from the working directory to the finished directory.
Response: On a Windows operating system this can be normal behavior because the operating system will not
allow a file to be moved while the file is being written to. For Windows, this is an error if the file listed is never
processed. On a non-Windows operating system, this error might occur because the source and destination
directories are on different file systems. Specify the source and destination directories to be on the same file
system.

FPL.0001.0035 File polling processing service indicated error - [<errorReason>]

Cause: The processing service flagged an error to indicate there is an error.
Response: No action is required.

FPL.0001.0036 File polling processing file: <fileName>

Cause: The indicated file is being processed.
Response: No action is required.

FPL.0001.0037 Could not rename file <srcFileName> to <targetFileName>.

Cause: The system was unable to move the file from the monitoring directory to the working directory.
Response: On a Windows operating system this can be normal behavior because the operating system will not
allow a file to be moved while the file is being written to. For Windows, this is an error if the file listed is never
processed. On a non-Windows operating system, this error might occur because the source and destination
directories are on different file systems. Specify the source and destination directories to be on the same file
system.

FPL.0002.0001 Invalid processing service: <serviceName>

Cause: The specified processing service does not exist.
Response: Specify a service name that exists on the webMethods Integration Server.

FPL.0002.0003 Unknown content type: <contentType>

Cause: No content handler is defined for the given content type.
Response: Specify a content type for which a content handler has been defined or define a content handler for
the specified content type. For more details, see the Javadoc for the class com.wm.app.b2b.server.ServerAPI.

296 webMethods Error Message Reference Version 6.5 and 6.5.1

FPL (File Polling)

FPL.0002.0004 Server Error: <errorDetails>

FPL.0002.0005 Invalid Cleanup service: <serviceName>

Cause: The specified processing service does not exist.
Response: Specify a service name that exists on the webMethods Integration Server.

FPL.0003.0001 Must provide Monitoring Directory

Cause: No monitor directory was specified.
Response: Specify a monitor directory.

FPL.0003.0004 Monitoring Directory does not exist

Cause: The monitoring directory does not exist.
Response: Create the monitoring directory.

FPL.0003.0005 Working Directory does not exist

Cause: The working directory does not exist.
Response: Create the working directory.

FPL.0003.0006 Must provide User Name

Cause: The user did not specify a value for the input "Run services as user".
Response: Specify a user to run the service as.

FPL.0003.0007 Must provide Processing service

Cause: The processing service was not specified.
Response: Specify a processing service.

FPL.0003.0008 Invalid processing service <serviceName>

Cause: The specified processing service does not exist.
Response: Specify a service name that exists on the webMethods Integration Server.

webMethods Error Message Reference Version 6.5 and 6.5.1 297

CHAPTER 5 webMethods Flat File Package

FPL.0003.0010 Completion Directory does not exist or can not be created

Cause: The completion directory does not exist or can not be created.
Response: Determine whether the server has permissions to create the indicated directory, or create the
directory manually.

FPL.0003.0011 Error Directory does not exist or can not be created

Cause: The error directory does not exist or cannot be created.
Response: Determine whether the server has permissions to create the indicated directory, or create the
directory manually.

FPL.0003.0012 Invalid Cleanup service <serviceName>

Cause: The specified clean up service does not exist.
Response: Specify a clean up service that exists on the webMethods Integration Server.

FPL.0003.0013 Invalid Working Directory

Cause: The specified working directory is the same as either the monitoring directory or the completion
directory.
Response: Specify a working directory that is not the same as the completion or monitoring directories.

FPL.0003.0015 Invalid Error Directory

Cause: The specified error directory is the same as either the monitoring directory or the completion directory.
Response: Specify an error directory that is not the same as the completion or monitoring directories.

298 webMethods Error Message Reference Version 6.5 and 6.5.1

CHAPTER 6
webMethods Installer

<component> requires the installer to be run as the root user.

Cause: To install <component> on a UNIX system, you must be logged on as the root user. You are not logged
on as the root user.
Response: You can either go back and deselect <component>, or you can exit the installer, log on as the root
user, and try again.

<component1> is dependent on <component2> <component_version>. You must install <component2> as well as

<component1>.
Cause: If a component you are trying to install depends on another component, but the first component does
not have a proper error message string in the prop file, you will see this default warning.
Response: Click "Yes" to select the required components.

A new version of the webMethods Installer is available; you must use that version to install. You can download the latest
version from webMethods Advantage (http://advantage.webMethods.com).
Cause: Occasionally the installer team adds improvements or fixes to the installer server that are not
backwards compatible with older clients. You are using an older client to connect to a newer server that
contains these updates, but the client and server are not compatible.
Response: Exit the installer client, download the latest client from the webMethods Advantage Web site, and
try again.

webMethods Error Message Reference Version 6.5 and 6.5.1 299

CHAPTER 6 webMethods Installer

A panel failed to load. There is something wrong with the image file or webMethods Installer server. The installer is exiting.
Cause: The webMethods Installer consists of a client and a server. The client connected to the webMethods
server you identified on the User Name/Password panel and tried to download the server part of the installer
but failed.
Response: Check your proxy settings on the Advanced Options panel. If you are installing from an installation
image, make sure the image is not corrupted. If this does not resolve the problem, run the installer from a
command window using the -debug 10 option, and send the output to webMethods Customer Care.

An error occurred while trying to create, open, write, or close the selected document. You might not have enough temporary
disk space to open the document.
Cause: When you have the installer display readmes, GSS documents, or release notes, the installer has to write
these files to disk temporarily. The machine on which you are installing lacks sufficient space for these files.
Response: Make sure the machine on which you are installing has enough available disk space on every
partition, including the directory that Java uses as a temporary directory. See the "webMethods Installation
Guide" for information on installer space requirements.

An error occurred while trying to launch the Browser for document file:
Cause: To display a readme, GSS document, or release notes, the installer launches a display tool. On UNIX
and Mac systems, the installer launches a Netscape browser. On Windows systems, the installer launches the
appropriate display tool for the requested document. An error occurred during the launch process.
Response: Report the stack trace data to webMethods Customer Care.

An error occurred while trying to open an Internet browser for the selected document.
Cause: To display a readme, GSS document, or release notes, the installer launches a display tool. On UNIX
and Mac systems, the installer launches a Netscape browser. On Windows systems, the installer launches the
appropriate display tool for the requested document. An error occurred during the launch process.
Response: Report the stack trace data to webMethods Customer Care.

An IO error occurred while trying to create, open, write, or close the temp documentation file.
Cause: When you have the installer display readmes, GSS documents, or release notes, the installer has to write
these files to disk temporarily. The machine on which you are installing lacks sufficient space for these files.
Response: Make sure the machine on which you are installing has enough available disk space on every
partition, including the directory that Java uses as a temporary directory. See the "webMethods Installation
Guide" for information on installer space requirements.

300 webMethods Error Message Reference Version 6.5 and 6.5.1

-baseURL option used without a base URL, ignored
Cause: You are trying to identify the server from which to download webMethods components, but you have
not provided the server's URL.
Response: Run the installer again, this time providing the server's URL after the -URLbase option (-URLbase
<URL>).

Cannot include some selected components because components they require do not exist on the selected webMethods
Installer server. Do you want the installer to deselect the affected components? (Or you can exit the installer, then restart it
and select a different server.
Cause: The installation image you are trying to create identifies certain components for installation but does
not also specify components the identified components require, because the required components are not
available on the webMethods Installer server. For example, the image identifies Integration Server for
installation but does not also specify the Java API Runtime, which is required by Integration Server.
Response: Contact webMethods Customer Care.

Cannot install some selected components because components they require are not selected. Do you want the installer to
select the required components?
Cause: You have selected certain components for installation but have not also chosen components that the
selected components require. For example, you selected Integration Server for installation but did not also
choose the Java API Runtime, which is required by Integration Server.
Response: If the required components are already installed on the machine on which you will run the image,
enter 'No.' If the required components are not already installed on the machine, enter 'Yes.'

Cannot install some selected components because components they require do not exist in the image, local machine, or
selected webMethods Installer server. Do you want the installer to deselect the affected components?
Cause: You tried to install but components required by the components you are trying to install do not exist in
the image from which you are installing, on the local machine, or in the webMethods Installer Server. For
example, you tried to install Integration Server but the Java API Runtime, which Integration Server requires,
does not exist in the listed locations.
Response: If you want to continue with the installation so you can install components that are not problematic,
enter 'Yes.' If you want to also install the required components, go back and select them in the installer.

Cannot open an Internet browser. Do you want to save the document?

Cause: To display a readme, GSS document, or release notes, the installer launches a display tool. On UNIX
and Mac systems, the installer launches a Netscape browser. The installer could not launch the browser.
Response: The installer will let you save the readme, GSS, or release notes to a directory so you can use a
different tool to read the document.

webMethods Error Message Reference Version 6.5 and 6.5.1 301

CHAPTER 6 webMethods Installer

Cannot read image file <file> because it is not a valid image file. The error is: <error>. The installer is exiting.
Cause: You have tried to install from an installation image that is corrupted or incorrectly built. The image
might have been incorrectly FTP-ed in ASCII rather than in binary mode.
Response: FTP the installation image in binary mode.

Cannot read image file <file>. The file might not exist, be of zero length, or you might not have access to the specified drive.
The installer is exiting.
Cause: The installer cannot find the specified installation image on the local machine.
Response: Make sure the script file exists, is not empty, and that you have read access to it. Examine the image
file to determine whether it is corrupt (for example, use WinZip to try to open the file).

Cannot read image file <file>. The file might not exist, or you might not have access to the specified drive.
Cause: The installer cannot read the installation image from which you are trying to install because the image
does not exist or is in a directory to which you do not have read access.
Response: Make sure the image exists in the specified directory, and that you have read access to that directory.

Cannot read image file <file>. The file might not exist, or you might not have access to the specified drive. The installer is
exiting.
Cause: The installer cannot find the specified installation image on the local machine.
Response: Examine the image file to determine whether it is corrupted. If it is not, contact webMethods
Customer Care.

Cannot read script file <file>. The file might not exist, or you might not have access to the specified drive.
Cause: The installer cannot read the installation script from which you are trying to install.
Response: Make sure the script file exists and that you have read access to it.

Cannot write to image file <file>. You might not have write permission to the specified directory.
Cause: You are trying to store an installation image as <file>, but either you do not have write permission to the
specified directory or an installation image already exists under that name. The installer will not overwrite an
existing image.
Response: Run the installer again, but save the image under a different file name or in a directory to which you
do have write permission.

Cannot write to script file <file>. You might not have write permission to the specified directory.
Cause: You are trying to write an installation image to a directory for which you do not have write permission.
Response: Write the image to a directory to which you do have write permission.

302 webMethods Error Message Reference Version 6.5 and 6.5.1

-console option is not supported on Microsoft Windows, ignored
Cause: The command line argument you entered requires a value.
Response: If the command line argument was necessary, cancel the installer and re-enter the command.
Otherwise, you can continue. To see a list of valid command line arguments, run the installer with the -h
argument or see the webMethods Installation Guide.

-country option used without a country, ignored

Cause: The command line argument you entered requires a value.
Response: If the command line argument was necessary, cancel the installer and re-enter the command.
Otherwise, you can continue. To see a list of valid command line arguments, run the installer with the -h
argument or see the webMethods Installation Guide.

-createImage option used without an image file, ignored

Cause: You are trying to create an installation image, but you have not supplied the file name under which to
store the image.
Response: Run the installer again, this time typing a valid file name after the -createImage option (-createImage
file_name).

-debug option used without a debug level

-debugKeys option used without debug keys

-editScript option used without a silent script file, ignored

webMethods Error Message Reference Version 6.5 and 6.5.1 303

CHAPTER 6 webMethods Installer

Error read silent properties file <file>: <exception>

Cause: The installer could not read the installation script from which you are trying to install.
Response: See <exception> for more information.

Error writing silent properties file <propertyFile>: <error>

Cause: You are trying to create an installation script, but the installer could not write the script.
Response: Fix the problem indicated by the error and run the installer again to create the script.

HTTP Proxy user name may not contain spaces.

Cause: The user name you have specified for the HTTP proxy service contains spaces, but spaces are not
acceptable in this entry.
Response: Specify a user name that does not contain space.

If required components are not already installed, you will not be able to install this image. Do you want the installer to select
the required components?
Cause: The installation image you are trying to create identifies certain components for installation but does
not also specify components the identified components require. For example, the image identifies Integration
Server for installation but does not also specify the Java API Runtime, which is required by Integration Server.
Response: If the required components are already installed on the machine on which you will run the image,
enter 'No.' If the required components are not already installed on the machine, enter 'Yes.'

Image file <file> already exists. You cannot overwrite it.

Cause: You are trying to store an installation image as <file>, but an installation image already exists under that
name. The installer will not overwrite an existing image.
Response: Run the installer again, but save the installation image under a different file name.

Image file <file> does not exist.

Cause: You have identified an installation image from which to install, but the image does not exist.
Response: Create the image or identify an image that does exist.

-imagePlatform option used without a platform, ignored

304 webMethods Error Message Reference Version 6.5 and 6.5.1

-imagePlatform option used without a valid platform, ignored
Cause: The value for the -imagePlatform requires a valid value.
Response: If the command line argument was necessary, cancel the installer and re-enter the command,
providing a valid value for the -imagePlatform argument value. To see a list of valid command line
arguments, run the installer with the -h argument or see the webMethods Installation Guide. If the command
line argument was not necessary, you can continue.

Installation directory <directory> contains an installation that is incompatible with this installer. Choose a different
installation directory.
Cause: You tried to install into a directory that contains a webMethods installation that is incompatible with
the version you are trying to install. For example, you tried to install version 6.0.1 on top of version 4.6.
Response: Choose a different installation directory. You cannot install into a root directory, and you must have
write permission to the directory.

-installDir option used without an installation directory

Invalid choice. Valid choices are <choices>.

Cause: You have selected an invalid choice from a list of choices.
Response: Enter a valid choice from the list.

IO Exception: The installer cannot read the entry <entry> from the install image <file>
Cause: The webMethods Installer cannot find entries in the installation image that should exist.
Response: Make sure the installation image is not corrupted. If it is not corrupted, and it was not provided to
you by webMethods, recreate the installation image and try again. If it is corrupted, it might have been
incorrectly FTP-ed in ASCII instead of in binary mode. FTP the image in binary mode.

-language option used without a language, ignored

webMethods Error Message Reference Version 6.5 and 6.5.1 305

CHAPTER 6 webMethods Installer

-launchImage option used without an image file, ignored

Cause: You are trying to install from an installation image, but you have not provided the name of the image.
Response: Run the installer again, this time providing the file name for the image after the -launchImage option
(-launchImage <file>).

Missing value for InstallDir parameter, uninstall cannot continue.

Cause: You have tried to manually run the webMethods Uninstaller, instead of using the Add/Remove
Programs feature on Windows or the uninstall script on UNIX.
Response: Follow the instructions in the "webMethods Installation Guide" to run the uninstaller.

-proxyHost option used without a host, ignored

-proxyPass option used without a password, ignored

-proxyPort option used without a port, ignored

-proxyUser option used without a user, ignored

306 webMethods Error Message Reference Version 6.5 and 6.5.1

-readImage option used without an image file, ignored
Cause: You are trying to install from an installation image, but you have not provided the name of the image.
Response: Run the installer again, this time providing the file name for the image after the -readImage option
(-readImage <file>).

-readScript option used without a silent properties file, ignored"

Cause: You are trying to create an installation script, but you have not provided the file name under which to
store the script.
Response: Run the installer again, this time providing a valid file name after the -readScript option
(-readScript <file>).

-readScript option used without a silent script file, ignored

-server option used with an illegal format, ignored

Cause: The value for the -server must follow a certain format.
Response: If the command line argument was necessary, cancel the installer and re-enter the command using
the proper format for the -server argument value. The proper formats are http://myMachine/cgi-
bin/myScript.cgi), machine:script (myMachine:myScript), machine:port:script (myMachine:8080:myScript),
protocol:machine:port:script (http:myMachine:8080:myScript), or protocol:machine:script
(http:myMachine:myScript). If the command line argument was not necessary, you can continue.

-server option used without an argument, ignored

webMethods Error Message Reference Version 6.5 and 6.5.1 307

CHAPTER 6 webMethods Installer

-server or -URLBase option used with an illegal format, ignored

Cause: The value for the -server must follow a certain format.
Response: If the command line argument was necessary, cancel the installer and re-enter the command using
the proper format for the -server argument. The proper formats are http://myMachine/cgi-bin/myScript.cgi),
machine:script (myMachine:myScript), machine:port:script (myMachine:8080:myScript),
protocol:machine:port:script (http:myMachine:8080:myScript), or protocol:machine:script
(http:myMachine:myScript). If the command line argument was not necessary, you can continue.

-serverVersion option used without a server version, ignored

-silent option used without a silent properties file, ignored

Cause: You are trying to create an installation script but you have not provided the file name under which to
store the script.
Response: Run the installer again, this time providing a valid file name after the -silent option (-silent <file>).

-socksProxyHost option used without a host, ignored

-socksProxyPort option used without a port, ignored

-SSLcacert option used without a cacert, ignored

308 webMethods Error Message Reference Version 6.5 and 6.5.1

-SSLcert option used without a certificate, ignored
Cause: The command line argument you entered requires a value.
Response: If the command line argument was necessary, cancel the installer and re-enter the command.
Otherwise, you can continue. To see a list of valid command line arguments, run the installer with the -h
argument or see the webMethods Installation Guide.

-SSLkey option used without a key, ignored

The directory name you entered is invalid. Do not use the characters `!@#$%^&(\\)+={}[]*?\
Cause: You have entered invalid characters as part of the path to the installation directory, or you have not
entered a path.
Response: Enter a valid path to the installation directory that includes only valid characters.

The directory you specified is invalid.

Cause: The path you provided to the installation directory is not correct.
Response: Enter a valid path to a directory that is not a root directory, that does not contain a webMethods
release that is incompatible with the one you are trying to install, and to which you have write permission.

The directory you specified is invalid. You cannot install into the root directory.
Cause: You tried to install into a root directory (for example, C:\). You cannot install into a root directory.
Response: Install into a subdirectory.

The following version 6.0 Language Packs installed on your system must be upgraded to version 6.0.1. The installer has
automatically selected the appropriate files for installation.
Cause: You are trying to upgrade only certain 6.0 language packs to 6.0.1.
Response: You must either upgrade all 6.0 language packs to 6.0.1 or no 6.0 language packs to 6.0.1.

The install image <file> is incomplete and cannot be used by the installer.
Cause: The installation image from which you are trying to install is corrupted or incorrectly built.
Response: Make sure the image is not corrupted and that it is for the correct platform. For example, the installer
cannot install a Windows image on a Solaris machine.

webMethods Error Message Reference Version 6.5 and 6.5.1 309

CHAPTER 6 webMethods Installer

The installation directory name you entered is invalid. You can only use a colon as the second character (e.g., C:\\). Do not
use a UNC path (\\\\server\\path) or the characters `!@#$%^&()+={}[]*?\\
Cause: You have entered invalid characters as part of the path to the installation directory, or you have not
entered a path.
Response: Enter a path to the installation directory that includes only valid characters.

The InstallDir parameter in your text file is invalid. You must use forward slashes rather than back slashes in this value.
Cause: You have edited the installation script from which you are trying to install to specify an illegal
installation directory (for example, you have specified a root directory such as C:/).
Response: Edit the script file to specify a legal installation directory. A legal installation directory is one that is
not a root directory, that does not contain a version of the webMethods component that is incompatible with
the one you are trying to install, and to which you have write permission.

The installer cannot access a required system property value. You might not have enough temporary disk space to open the
document.
Cause: When you have the installer display readmes, GSS documents, or release notes, the installer has to write
these files to disk temporarily. The machine on which you are installing lacks sufficient space for these files.
Response: Make sure the machine on which you are installing has enough available disk space on every
partition, including the directory that Java uses as a temporary directory. See the "webMethods Installation
Guide" for information on installer space requirements.

The Installer cannot continue due to a networking error. This may indicate that the Install Server is unavailable. If this
persists you should contact webMethods support, noting the error. The error is: <error>
Cause: The webMethods Installer consists of a client and a server. A networking problem occurred while the
client was communicating with the server.
Response: Check your network. If your network is working properly, the server might be down. Contact
webMethods Customer Care.

The installer could not connect to the webMethods Installer server. The error is:
Cause: A generic networking problem has occurred.
Response: Depending on the error message displayed, change networking settings and address networking
problems to resolve the issue.

310 webMethods Error Message Reference Version 6.5 and 6.5.1

The installer could not connect to the webMethods Installer server. Make sure you specified the correct Server URL in
Advanced Options. Use the format http://<host>/cgi-bin/dataserve<server>.cgi or http:<host>:<server>.
Cause: The URL must be specified using the proper format.
Response: Make sure to enter the URL using one of the formats listed in the message. Check for typos in the
URL, such as commas instead of periods. Make sure there are no spaces in the URL.

The installer could not connect to the webMethods Installer server. The server might be undergoing maintenance. Please try
again later.
Cause: The webMethods Installer consists a client and a server. The client connects to the server using HTTP.
The client can connect to the server host machine but not to the Apache scripts running on the machine.
Response: Contact webMethods Customer Care.

The installer could not find the webMethods Installer server. Check your network connection and ask your network
administrator if you need to use a proxy server to connect through your firewall (see Advanced Options).
Cause: The webMethods Installer consists of a client and a server. Your machine has no network path from the
client to the server.
Response: Check your network connections to the webMethods Installation servers or specify a proxy server on
the Advanced Options panel. For instructions on using a proxy server, see the “webMethods Installation
Guide.”

The installer detected the following older version Language Packs installed on your system and no new Language Packs are
available: <languagePacks>. Please cancel this install session and uninstall the Language Packs listed. Restart the installer
to install the new Products.
Cause: You tried to install new components, but old language packs are already installed for those components
and no new language packs are available. The components cannot work properly with the old language packs.
Response: Cancel the installer, uninstall the language packs specified in the message, and re-start the installer.

The script <scriptName> cannot be read, doesn't exist, or is empty.

Cause: The installation script from which you are trying to install cannot be read, does not exist, or is empty.
Response: Make sure the script file exists, is not empty, and you have read access to it.

webMethods Error Message Reference Version 6.5 and 6.5.1 311

CHAPTER 6 webMethods Installer

The Server URL you have entered is in an invalid format. Either enter a complete URL (example: http://myMachine/cgi-
bin/myScript.cgi), or one of the following: machine:script (myMachine:myScript), machine:port:script
(myMachine:8080:myScript), protocol:machine:port:script (http:myMachine:8080:myScript), or protocol:machine:script
(http:myMachine:myScript)
Cause: The URL you enter for connecting to the installer server must follow a certain format.
Response: Make sure to enter the URL using one of the formats listed in the message. Check for typos in the
URL, such as commas instead of periods. Make sure there are no spaces in the URL.

The Start Menu group name you entered is invalid. It must not be blank, and must not use the characters `!@#$%^&*()+={}[]|:;\
Cause: When installing on a Windows system, you must specify a Start Menu group name. The folder you
identify cannot contain' any of the characters listed in the message.
Response: Specify a Start Menu group name that contains only legal characters.

The text <accept_string> was not found in the silent options file, you have not accepted all licensing terms and the install
must now terminate.
Cause: Some components have license agreements you must agree to before you can install. In an installation
script, agreement is indicated by <accept_string>. The installation script from which you are trying to install
does not contain <accept_string>.
Response: Manually Insert <accept_string> into the script.

The user name or password you entered is invalid.

Cause: The user name you have supplied does not exist, or the password you have supplied is incorrect for the
specified user name.
Response: Enter the correct user name and password. Both are case sensitive.

The webMethods Installer could not read image file <file>. Make sure the image is readable and not corrupted.
Cause: You have tried to install from an installation image that is corrupted or incorrectly built.
Response: The image might have been incorrectly FTP-ed in ASCII rather than in binary mode. FTP the
installation image in binary mode.

The webMethods Installer server is experiencing technical difficulties. Try again later.
Cause: The webMethods Installer consists of a client and a server. The server is down or not running properly.
Response: Contact webMethods Customer Care.

312 webMethods Error Message Reference Version 6.5 and 6.5.1

The webMethods Installer server you chose does not support the selected platform. Choose a different server.
Cause: You are trying to install a version of webMethods components that is not supported on the platform on
which the installer is running. The webMethods Installer consists of a client and a server. You might be using a
newer client and connecting to an older server.
Response: Connect to a server that supports the platform on which you want to install the webMethods
components.

The webMethods Installer server you specified in Advanced Options does not support SSL. Clear the SSL check box and try
again.
Cause: The webMethods Installer consists of a client and a server. You are trying to run the installer client
using SSL, but the server to which you are trying to connect does not support SSL.
Response: Clear the SSL check box and try again.

The webMethods Installer server you specified in Advanced Options gave an unexpected response. Make sure the server is
working properly.
Cause: The webMethods installer servers are not functioning properly.
Response: Contact webMethods Customer Care.

There was an error writing to disk:/n<exception>/nTry to fix the problem then select Retry, or select Exit to end the
webMethods Installer.
Cause: The installer tried to write a file to disk but could not, probably because of insufficient disk space.
Response: The most likely problem is that the machine to which the installer tried to write the file does not have
sufficient disk space. See the <exception> for more information.

There was an error writing to disk:\n <exception>\nTry to fix the problem then click Retry, or click Cancel to end the
webMethods Installer.
Cause: The installer tried to write a file to disk but could not. The installer threw an input/output exception.
Response: See <exception> for more information.

webMethods Installer ignoring unknown option: <option>

Cause: The installer does not support the specified command line argument.
Response: If the command line argument was necessary, cancel the installer and re-enter the command.
Otherwise, you can continue. To see a list of valid command line arguments, run the installer with the -h
argument or see the “webMethods Installation Guide.”

webMethods Error Message Reference Version 6.5 and 6.5.1 313

CHAPTER 6 webMethods Installer

We're sorry. You have not yet accepted the terms of the webMethods third-party license agreement. Please do the following:
Exit the installer. Go to the webMethods Advantage Web site at http://advantage.webmethods.com and log in. Click Product
Downloads, then try to download the webMethods Installer. Read the license agreement and indicate whether you accept its
terms. If you accept, restart the webMethods Installer.
Cause: You have not yet agreed to the licensing terms described on the webMethods Advantage Web site. You
cannot install unless you accept the terms.
Response: Follow the procedure in the message to view and agree to the licensing terms.

Would you like the uninstaller to automatically uninstall all components that depend on components you have selected for
uninstallation?
Cause: You are trying to uninstall a component on which another component depends, but you are not trying
to uninstall the dependent component. For example, you are trying to uninstall the Java API Runtime, on
which Integration Server depends, but you are not trying to uninstall Integration Server.
Response: If you want to uninstall the required component and all components that depend on that component
(for example, the Java API Runtime and Integration Server), enter 'Yes.' If you want to also uninstall the
dependent components, go back and select them in the uninstaller.

-writeImage option used without an image file, ignored

-writeScript option used without a silent script file, ignored

You are about to install from a script that contains predefined user inputs. Once the script has started, you cannot stop it. Do
you want to continue?
Cause: After you begin to run a script, the script will run without user input until it completes. This message
makes sure this is the action you want to take.
Response: Indicate whether you want to continue.

314 webMethods Error Message Reference Version 6.5 and 6.5.1

You are trying to run the installer with JVM <version1>. To run the installer, you must have JVM <version2> or later installed
on your system.
Cause: webMethods Installer 6.0.1 requires JVM 1.3 to run properly on most platforms.
Response: Run the installer with the specified JVM version or later.

You cannot create a script (-readScript) and create an image (-writeImage) at the same time.
Cause: You cannot create both an installation script and an installation image in the same run of the installer.
Note: The text of this error message is incorrect; for "-readScript," read "-writeScript."
Response: Create the installation script and the installation image in two separate runs of the installer.

You cannot create a script (-silent) and create an image (-createImage) at the same time.
Cause: You cannot create both an installation script and an installation image in the same run of the installer.
Response: Create the installation script and the installation image in two separate runs of the installer.

You do not have permission to write to directory <directory>.

Cause: You are trying to install into a directory to which you do not have write permission.
Response: Install into a directory to which you have write permission.

You have selected to edit your silent installation script, but you are connecting to a server that does not fully support this
functionality. You may experience the installer exiting abnormally. Cancel editing the silent installation script?
Cause: The ability to edit installation scripts was added to webMethods Installer 6.5 and is only available
through 6.5 servers. The server to which the client is connected is not a 6.5 server.
Response: Cancel the edit. If you are working with webMethods 6.5 components, connect to a 6.5 server.

You must provide the image file name.

Cause: You are trying to create or install from an installation image but you have not provided the file name of
the image.
Response: Provide a valid file name for the installation image.

You must provide the proxy server's host and port.

Cause: You have chosen to use a proxy server on the Advanced Options panel, but you have not provided the
host name or fully qualified IP address of the proxy server or the port used by the proxy server
Response: In the Host box, type the host name or fully qualified IP address of the proxy server. In the Port box,
type the port used by the proxy server.

webMethods Error Message Reference Version 6.5 and 6.5.1 315

CHAPTER 6 webMethods Installer

You must provide the script file name.

Cause: You are trying to create an installation script but you have not provided the file name under which to
store the script.
Response: Provide a valid file name under which to store the installation script.

You must upgrade all your installed 6.0 components to 6.0.1. Go back and select the following 6.0.1 components:
Cause: You are trying to upgrade only certain 6.0 components to 6.0.1.
Response: You must either upgrade all 6.0 components to 6.0.1 or no 6.0 components to 6.0.1.

Your Java Runtime Environment does not support SSL. Clear the SSL check box or change your JRE, then try again.
Cause: You are trying to run the installer using SSL. However, your JVM does not support SSL, or the
webMethods Installer servers are not functioning properly.
Response: Check whether JVM supports SSL. If it does, contact webMethods Customer Care.

Your JRE or the webMethods Installer server cannot use SSL. Clear the SSL check box and try again.
Cause: A generic connection problem occurred, probably because of SSL problems.
Response: Clear the SSL check box and try again.

Your system temp folder (Windows) or home directory (UNIX) does not have enough temporary disk space to run the
installer. Choose a temporary directory that has about 50MB of free disk space.
Cause: The webMethods Installer requires a certain amount of temporary disk space in the system temp folder
(Windows) or home directory (UNIX) to run. That amount of space is not available.
Response: You can either enter 'Yes' and specify a different temporary directory that has 50MB of free disk
space, or you can enter 'No,' free up space in the system temp folder or home directory, and try again.

Your system temp folder (Windows) or home directory (UNIX) does not have enough temporary disk space to run the
installer. The installer requires about 50MB of free disk space. Do you want to choose a different temporary directory?
Cause: The installer requires a certain amount of temporary disk space in the system temp folder (Windows) or
home directory (UNIX) to run. That amount of space is not available.
Response: You can either enter 'Yes' and specify a different temporary directory that has 50MB of free disk
space, or you can enter 'No' and free up space in the system temp folder or home directory.

316 webMethods Error Message Reference Version 6.5 and 6.5.1

CHAPTER 7
webMethods Integration Server

ART (Adapter Run Time) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318

BAA (Auditing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394

BAF (File System Persistence) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

BAP (Master Password) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

ISC (IS Core) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

ISE (Internal Errors) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476

ISP (Package Management) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477

ISS (IS Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487

ISU (General Purpose) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563

SCC (JCA System Contract Component Transaction Manager) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566

XSL (XSLT Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570

webMethods Error Message Reference Version 6.5 and 6.5.1 317

CHAPTER 7 webMethods Integration Server

ART (Adapter Run Time)

ART.0114.0002E Adapter Runtime: Unable to get adapter type information. Internal error.
Cause: An error occurred while fetching the list of supported services for a particular adapter.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0003E Adapter Runtime: Unable to get information about adapter type <adapterName>.
Cause: An error occurred while retrieving a service's localized deployment values (adapter name, adapter
version, adapter JCA version) from the specified adapter's metadata.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0004E Adapter Runtime: Error getting available packages.

Cause: An error occurred while retrieving a list of packages available for node creation.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0005E Adapter Runtime: Error(s) during Adapter Runtime startup.

Cause: An error occurred during the initialization of the com.wm.pkg.art.AdapterRuntimeGlobals class.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0006E Adapter Runtime: Unable to initialize transaction manager. Transaction manager already initialized.
Cause: WmART has attempted to initialize the Transaction Manager twice.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0007E Adapter Runtime: Unable to get managed connection factories for adapter type <adapterName>.
Cause: WmART was unable to obtain a list of connection factories for the specified adapter.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

318 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0114.0008E Adapter Runtime: Unable to get the description and display name for connection type "<connectionName>"
of adapter type "<adapterName>".
Cause: An error occurred while getting the display name and description for the specified connection/listener
in the specified adapter.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0009E Adapter Runtime: Error(s) while registering adapter type <adapterName>.

Cause: An error occurred while loading the specified adapter.
Response: This might be due to a connection that failed to initialize properly. Ensure that the adapter's
connections can communicate with their respective resources. If the problem persists, contact webMethods
Customer Care. Please have the following information available: system and setup specifics, journal logs, and
error logs with the stack trace exposed.

ART.0114.0010E Adapter Runtime: Error(s) while unregistering adapter type <adapterName>.

Cause: An error occurred while shutting down the specified adapter's connection resources.
Response: This might be due to problems in one or more connections. Ensure that all adapter connections shut
down properly when the adapter was unloaded.

ART.0114.0011E Adapter Runtime: Error occurred while Adapter Runtime was loading an adapter type. Missing required
input, "<paramName>".
Cause: The class name of an adapter was not present as the first item in the pipeline given to
com.wm.pkg.art.deployment.Service.registerAdapterType.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0012E Adapter Runtime: Error occurred while Adapter Runtime was loading an adapter type. Unexpected adapter
type object "<className>" for input "<paramName>".
Cause: The class name of the object passed to com.wm.pkg.art.deployment.Service.registerAdapterType is not
derived from WmAdapter.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0013E Adapter Runtime: Error occurred while Adapter Runtime was loading adapter type "<adapterName>".
Cause: An error occurred while loading the specified adapter.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

webMethods Error Message Reference Version 6.5 and 6.5.1 319

CHAPTER 7 webMethods Integration Server

ART.0114.0014E Adapter Runtime: Error occurred while Adapter Runtime was unloading an adapter type. Missing required
input, "<paramName>".
Cause: The class name of an adapter was not present as the first item in the pipeline given to
com.wm.pkg.art.deployment.Service.unregisterAdapterType.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0015E Adapter Runtime: Error occurred while Adapter Runtime was unloading an adapter type. Unexpected
adapter type object "<className>" for input "<paramName>".
Cause: The class name of the specified object passed to
com.wm.pkg.art.deployment.Service.unregisterAdapterType is not derived from WmAdapter.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0016E Adapter Runtime: Error occurred while Adapter Runtime was unloading adapter type "<adapterName>".
Cause: An error occurred while loading the specified adapter.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0017E Adapter Runtime: Error occurred while registering XidFactory for adapter type "<adapterName>".
Cause: WmART was unable to locate the Transaction Manager or Transaction ID Factory class for the specified
adapter.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0018E Adapter Runtime: Unable to get XidFactories for adapter type "<adapterName>".
Cause: WmART was unable to locate the class loader while retrieving the Transaction ID Factory map for the
specified adapter.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0019E Adapter Runtime: Unable to get XidFactory <className> for XAResource <className> in adapter type
"<adapterName>".
Cause: WmART was unable to determine the corresponding XidFactory class for the specified XAResource
class while loading the adapter.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

320 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0114.0020E Adapter Runtime: Error occurred while loading online help system for adapter type "<adapterName>".
Cause: An error occurred while WmART was attempting to fetch the path to the specified adapter's online help
file.
Response: Ensure that a help page key exists in your AdapterResourceBundle for
ADKGLOBAL.RESOURCEBUNDLEKEY_LISTRESOURCES,
ADKGLOBAL.RESOURCEBUNDLEKEY_LISTCONNECTIONTYPES,
ADKGLOBAL.RESOURCEBUNDLEKEY_LISTPOLLINGNOTIFICATIONS,
ADKGLOBAL.RESOURCEBUNDLEKEY_LISTPOLLINGNOTIFICATIONDETAILS, and
ADKGLOBAL.RESOURCEBUNDLEKEY_ABOUT.

ART.0114.0021E Adapter Runtime: Error occurred while loading copyright for adapter type "<adapterName>".
Cause: Failed to read a third-party copyright file for the specified adapter.
Response: If you have explicitly specified
ADKGLOBALS.RESOURCEBUNDLEKEY_THIRDPARTYCOPYRIGHTURL in the adapter's resource bundle,
ensure that the file this key references is in the pub directory in the adapter's directory tree. Also ensure that
this file is readable by the Integration Server.

ART.0114.0022E Adapter Runtime: Error in <methodName>. Missing or invalid parameter: <parameterName>.

Cause: A value was not specified for the parameter of the specified method.
Response: If you explicitly invoked the specified method, check your parameter values and resubmit.
Otherwise, look in the error log for related errors.

ART.0114.0030E Adapter Runtime: Unable to create node <nodeName> in the namespace.

Cause: WmART failed to create the specified connection or listener node in the namespace.
Response: The connection/listener information you provided in the Integration Server Administrator editor is
invalid, or perhaps duplicates an existing connection/listener in the same namespace. Refer to adjacent log
entries for specifics.

ART.0114.0031E Adapter Runtime: Unable to update node <nodeName>. Package not found.
Cause: WmART attempted to save changes to the specified namespace node, but could not determine its
package.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

webMethods Error Message Reference Version 6.5 and 6.5.1 321

CHAPTER 7 webMethods Integration Server

ART.0114.0032E Adapter Runtime: Unable to update resource <namespace>.

Cause: An error occurred when updating a value in the specified namespace.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0033E Adapter Runtime: Invalid folder name <folderName>.

Cause: While creating a new connection node, a null folder name was passed to
com.wm.pkg.art.util.ServiceHelper.checkInterfaceName.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0034E Adapter Runtime: Unable to create folder <folderName>.

Cause: WmART was unable to create the specified folder in the adapter's namespace.
Response: Ensure that the folder name conforms to naming conventions in your server's local file system, and
that the Integration Server has permissions to create folders under the packages folder. If the problem persists,
contact webMethods Customer Care. Please have the following information available: system and setup
specifics, journal logs, and
Response: error logs with the stack trace exposed.

ART.0114.0035E Adapter Runtime: Unable to create record for <className>.

Cause: An error occurred in ServiceHelper.createRecordFromBean while creating an NSRecord from the
specified object. Additional details should appear in adjacent log messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0036E Adapter Runtime: Unable to create folder for service <adapterName>.

Cause: An error occurred in ServiceHelper.registerService while creating the file system infrastructure for the
specified adapter service. Additional details should appear in adjacent log messages.
Response: Ensure that the local operating system access permissions within the Integration Server packages
folder will allow WmART to create folders and files dynamically.

ART.0114.0037E Adapter Runtime: Unable to create service <adapterName>.

Cause: An error occurred in ServiceHelper.registerService while registering the adapter service. Additional
details should appear in adjacent log messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

322 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0114.0038E Adapter Runtime: Unable to create flow <serviceName>.

Cause: An error occurred in ServiceHelper.createFlowService. Additional details should appear in adjacent log
messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0040E Adapter Runtime: Unable to create interaction input record.

Cause: An error occurred in RecordFactoryBridgeImpl.createInputRecord while creating a mapped Record.
Additional details should appear in adjacent log messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0041E Adapter Runtime: Unable to create input record. createMappedRecord() returned <className>.
Cause: A call to RecordFactory.createMappedRecord returned an object of the specified class rather than a
WmRecord or IDataCodable object.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0042E Adapter Runtime: Unable to convert interaction output record into IData. Output record is <className>.
Cause: RecordFactoryBridgeImpl.createOutputData was passed an instance of the specified class rather than a
WmRecord, IData or IDataCodable instance.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0050E Adapter Runtime: Unable to convert string to specific data type. The data type is not specified or the string
value is null.
Cause: While configuring a new connection or listener, WmART detected that the type or value of one of the
connection's properties is null.
Response: Ensure that you enter values for all required properties in a Developer or Administrator screen. If
the problem persists, contact webMethods Customer Care. Please have the following information available:
system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0051E Adapter Runtime: Unable to convert string to specific data type. Unsupported data type <dataType>.
Cause: You omitted a value when configuring a connection or listener property from the Integration Server
Administrator.
Response: Reconfigure the connection/listener, entering valid values for all properties on the Integration Server
Administrator page.

webMethods Error Message Reference Version 6.5 and 6.5.1 323

CHAPTER 7 webMethods Integration Server

ART.0114.0053E Adapter Runtime: Unable to convert string array to specific data type array. The data type is not specified.
Cause: While configuring a new connection or listener, WmART detected that the type of a property array is
null.
Response: This condition indicates a coding error in the adapter or the Adapter Runtime (WmART) itself.
Ensure that the adapter is handling connection and listener properties correctly. If the problem persists,
contact webMethods Customer Care. Please have the following information available: system and setup
specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0054E Adapter Runtime: Unable to convert string array to specific data type array. Unsupported data type
<dataType>.
Cause: The Adapter Runtime (WmART) has detected a property array in a connection or listener that has an
unsupported data type.
Response: Change your connection/listener to use only supported data types for all properties.

ART.0114.0055E Adapter Runtime: Unable to convert string array to data type <dataType> array.
Cause: An unexpected property array conversion error has occurred while configuring a connection or listener.
Response: This might be due to invalid data in a property array on the Integration Server Administrator page,
such as non-numeric data in a numeric property. Reconfigure the connection/listener to ensure that the
entered data matches the expected data types for all properties.

ART.0114.0056E Adapter Runtime: Unable to convert string array to primitive into array.
Cause: A value has been entered in a connection or listener property array that cannot be converted to a Java
int type.
Response: Reconfigure the connection/listener to ensure that the data entered conforms to the expected data
types for all properties.

ART.0114.0057E Adapter Runtime: Unable to convert string array to primitive long array.
Cause: A value has been entered in a connection or listener property array that cannot be converted to a Java
long data type.
Response: Reconfigure the connection/listener to ensure that the data entered conforms to the expected data
types for all properties.

ART.0114.0058E Adapter Runtime: Unable to convert string array to primitive float array.
Cause: A value has been entered in a connection or listener property array that cannot be converted to a Java
float type.
Response: Reconfigure the connection/listener to ensure that the data entered conforms to the expected data
types for all properties.

324 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0114.0059E Adapter Runtime: Unable to convert string array to primitive double array.
Cause: A value has been entered in a connection or listener property array that cannot be converted to a Java
double type.
Response: Reconfigure the connection/listener to ensure that the data entered conforms to the expected data
types for all properties.

ART.0114.0060E Adapter Runtime: Unable to convert string array to primitive boolean array.
Cause: A value has been entered in a connection or listener property array that cannot be converted to a Java
Boolean type.
Response: Reconfigure the connection/listener to ensure that the data entered conforms to the expected data
types for all properties.

ART.0114.0061E Adapter Runtime: Unable to convert string array to primitive short array.
Cause: A value has been entered in a connection or listener property array that cannot be converted to a Java
short type.
Response: Reconfigure the connection/listener to ensure that the data entered conforms to the expected data
types for all properties.

ART.0114.0062E Adapter Runtime: Unable to convert string array to primitive char array.
Cause: A value has been entered in a connection or listener property array that cannot be converted to a Java
char type.
Response: Reconfigure the connection/listener to ensure that the data entered conforms to the expected data
types for all properties.

ART.0114.0063E Adapter Runtime: Unable to convert string array to Integer array.

Cause: A value has been entered in a connection or listener property array that cannot be converted to a Java
integer instance.
Response: Reconfigure the connection/listener to ensure that the data entered conforms to the expected data
types for all properties.

ART.0114.0064E Adapter Runtime: Unable to convert string array to Long array.

Cause: A value has been entered in a connection or listener property array that cannot be converted to a Java
long instance.
Response: Reconfigure the connection/listener to ensure that the data entered conforms to the expected data
types for all properties.

webMethods Error Message Reference Version 6.5 and 6.5.1 325

CHAPTER 7 webMethods Integration Server

ART.0114.0065E Adapter Runtime: Unable to convert string array to Float array.

Cause: A value has been entered in a connection or listener property array that cannot be converted to a Java
float instance.
Response: Reconfigure the connection/listener to ensure that the data entered conforms to the expected data
types for all properties.

ART.0114.0066E Adapter Runtime: Unable to convert string array to Double array.

Cause: A value has been entered in a connection or listener property array that cannot be converted to a Java
double instance.
Response: Reconfigure the connection/listener to ensure that the data entered conforms to the expected data
types for all properties.

ART.0114.0067E Adapter Runtime: Unable to convert string array to Boolean array.

Cause: A value has been entered in a connection or listener property array that cannot be converted to a Java
Boolean instance.
Response: Reconfigure the connection/listener to ensure that the data entered conforms to the expected data
types for all properties.

ART.0114.0068E Adapter Runtime: Unable to convert string array to Short array.

Cause: A value has been entered in a connection or listener property array that cannot be converted to a Java
short instance.
Response: Reconfigure the connection/listener to ensure that the data entered conforms to the expected data
types for all properties.

ART.0114.0069E Adapter Runtime: Unable to convert string array to Character array.

Cause: A value has been entered in a connection or listener property array that cannot be converted to a Java
character instance.
Response: Reconfigure the connection/listener to ensure that the data entered conforms to the expected data
types for all properties.

ART.0114.0072E Adapter Runtime: Unable to set JavaBean properties.

Cause: WmART has detected an error while setting the properties on a listener or listener notification bean.
Response: Ensure that the adapter's listener and listener notification implementations adhere to the JavaBean
standard.

326 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0114.0073E Adapter Runtime: Unable to set property <propertyName> to value <propertyValue> on class <className>.
Cause: WmART failed to set the specified property on the specified (bean) class because it could not introspect
the class.
Response: Ensure that the adapter's service template implementations adhere to the JavaBean standard. If the
problem persists, contact webMethods Customer Care. Please have the following information available:
system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0074E Adapter Runtime: Property <propertyName> not found in class <className>.

Cause: After introspecting the specified class, WmART failed to find the specified property in that class.
Response: Ensure that the adapter's service template implementations adhere to the JavaBean standard. If the
problem persists, contact webMethods Customer Care. Please have the following information available:
system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0075U Adapter Runtime: Unable to set property descriptor.

Cause: WmART failed to introspect an unspecified bean.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0076E Adapter Runtime: Unable to set <propertyName> to <propertyValue> because property is not writable.
Cause: WmART was unable to locate the "set" method for the specified property on a bean class. The property
appears to be read only.
Response: Ensure that the adapter's service template implementations adhere to the JavaBean standard. To
make the specified property writable, implement a "set" method for it.

ART.0114.0077E Adapter Runtime: Error while setting property <propertyName> of class <className> to <propertyValue>.
Cause: An error occurred while setting the specified property on the specified class instance.
Response: Ensure that the adapter's service template implementations adhere to the JavaBean standard. If the
problem persists, contact webMethods Customer Care. Please have the following information available:
system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0078E Adapter Runtime: Unable to get JavaBean properties for <className>.

Cause: An error occurred while reading the properties from the specified bean class.
Response: Ensure that the adapter's service or notification template implementations adhere to the JavaBean
standard. If the problem persists, contact webMethods Customer Care. Please have the following information
available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

webMethods Error Message Reference Version 6.5 and 6.5.1 327

CHAPTER 7 webMethods Integration Server

ART.0114.0081E Adapter Runtime: Unable to create instance of <className>.

Cause: WmART was unable to create a new instance of the specified class.
Response: Ensure that the adapter's service and notification template implementation classes expose a default
public constructor and are not abstract. If the problem persists, contact webMethods Customer Care. Please
have the following information available: system and setup specifics, journal logs, and error logs with the
stack trace exposed.

ART.0114.0082E Adapter Runtime: Unable to get JavaBean property <propertyName> of class <className>.
Cause: WmART failed to determine or invoke the "get" method for the property in the specified class.
Response: Ensure that the adapter's service or notification template implementations adhere to the JavaBean
standard. If the problem persists, contact webMethods Customer Care. Please have the following information
available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0083E Adapter Runtime: Exception encountered attempting to load fix information for adapter type
<adapterTypeName>.
Cause: The Adapter Runtime (WmART) failed while attempting to load the installed update information for
the adapter.
Response: This error is generated when an exception is caught during execution. Check the error logs for
information on the original exception.

ART.0114.0084E Adapter Runtime: Missing or invalid value. <value> is not a valid value for field <fieldName>.
Cause: An error occurred while validating the common values for a connection pool. The common values are
settings, such as, Minimum Pool Size, Maximum Pool Size, etc.
Response: Change the invalid value. Then attempt to save and enable your connection.

ART.0114.0201E Adapter Runtime (Metadata): Unable to introspect "<className>". This service introspects the parameters
of connection only.
Cause: WmART failed to create a WmManagedConnectionFactory instance from the specified class name. The
current WmART implementation does not allow this condition to occur.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0202E Adapter Runtime (Metadata): Failure when introspecting the connection properties.
Cause: An error occurred while introspecting connection properties. Additional details are logged.
Response: Check adjacent log messages for specific error details. Correct any problems with your connection
metadata. If the problem persists, contact webMethods Customer Care. Please have the following information
available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

328 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0114.0203E Adapter Runtime (Metadata): Unable to introspect "<className>".

Cause: The Adapter Runtime (WmART) failed to create an instance of an adapter service, notification, or
listener from the specified class name.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0204E Adapter Runtime (Metadata): Unable to introspect the parameters of service template.
Cause: An error occurred while attempting to introspect a template or listener. Additional details are logged.
Response: Ensure that the adapter's implementation .class files are installed properly under the packages
folder. If you modify the .class files for the adapter while the Integration Server is running, you must reload
that adapter.

ART.0114.0205E Adapter Runtime (Metadata): Unable to lookup the resource domain values.
Cause: This is a general processing error message. Details should appear in adjacent log messages.
Response: Refer to the Action column for the accompanying messages.

ART.0114.0206E Adapter Runtime (Metadata): Connection alias was not specified in "<methodName>".
Cause: The connection, adapter, or listener could not be found in the request to the specified method.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0207E Adapter Runtime (Metadata): The connection alias "<aliasName>" does not support webMethods metadata
extensions. The adapter could be a third-party adapter.
Cause: The specified connection alias is not derived from com.wm.adk.cci.connection.WmConnection.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0208E Adapter Runtime (Metadata): The connection alias "<aliasName>" isn't configured or failed.
Cause: WmART failed to create a ConnectionDataNode instance based on the specified connection alias.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

webMethods Error Message Reference Version 6.5 and 6.5.1 329

CHAPTER 7 webMethods Integration Server

ART.0114.0209E Adapter Runtime (Metadata): Cannot get the connection instance of connectionAlias "<aliasName>".
Cause: An error occurred while creating a WmConnection instance from the specified connection alias.
Additional details are provided in adjacent log messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0213E Adapter Runtime (Metadata): Cannot get the listener instance of listenerNode "<listenerNode>".
Cause: The method getListenerAdapterMetadata in com.wm.pkg.art.metadata.ConnectionMetadataService
failed to locate and create a listener object for the specified listener node.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0216E Adapter Runtime (Metadata): Unable to validate the resource domain value.
Cause: An error occurred while validating a resource domain. This is a general processing error message.
Details should appear in adjacent log messages.
Response: Refer to the Action column for the accompanying messages.

ART.0114.0218E Adapter Runtime (Metadata): Failure when introspecting the parameters of the notification listener.
Cause: WmART failed to lookup a resource domain. Additional details should appear in adjacent log
messages.
Response: Ensure that the adapter's implementation(s) of WmNotification.fillWmTemplateDescriptor sets
resource domains correctly.

ART.0114.0219E Adapter Runtime (Metadata): Failure when validating the resource domain "<domainName>". Null
checkValues returned.
Cause: WmART was unable to locate internal check values for the specified resource domain.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0220E Adapter Runtime (Metadata): Error occurred when closing the connection handle.
Cause: An error occurred when closing a connection. Additional details are logged.
Response: Ensure that the connection is configured properly and is able to communicate with the back-end
resource. If the problem persists, contact webMethods Customer Care. Please have the following information
available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

330 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0114.0221E Adapter Runtime (Metadata): No adapter type name specified in "<methodName>".

Cause: The specified method in com.wm.pkg.art.metadata.ConnectionMetadataService failed to retrieve
connection metadata because no adapter name was provided.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0222E Adapter Runtime (Metadata): No class name of WmManagedConnectionFactory specified in

"<methodName>".
Cause: The specified method in com.wm.pkg.art.metadata.ConnectionMetadataService failed to retrieve
connection metadata because no connection factory class name was provided.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0225E Adapter Runtime (Metadata): Cannot get the connection handle of "<aliasName>".
Cause: WmART failed to create a WmConnection instance based on the specified connection alias.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0226E Adapter Runtime (Metadata): No class name of service template specified in "<methodName>".
Cause: The specified method failed to retrieve metadata from an adapter template, notification template, or
listener because no service class was provided in the request.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0227E Adapter Runtime (Metadata): No resource domain name specified in "<methodName>".

Cause: The specified method failed because no resource domain was provided in the request.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0228E Adapter Runtime (Metadata): No statement specified in "<methodName>".

Cause: The specified method in com.wm.pkg.art.metadata.InteractionMetadataService failed because the
AdapterRuntimeGlobals.STATEMENT value was not provided in the request.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

webMethods Error Message Reference Version 6.5 and 6.5.1 331

CHAPTER 7 webMethods Integration Server

ART.0114.0230E Adapter Runtime (Metadata): Unable to get the list of service template metadata.
Cause: The method getInteractionAdapterMetadataList in
com.wm.pkg.art.metadata.InteractionMetadataService failed because the list of service templates supported
by a connection was not provided in the request.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0231E Adapter Runtime (Metadata): Unable to get the list of notification template metadata.
Cause: An error occurred in
com.wm.pkg.art.metadata.InteractionMetadataService.getNotificationAdapterMetadataList. This is a general
processing error message. Details should appear in adjacent log messages.
Response: Refer to the Action column for the accompanying messages.

ART.0114.0232E Adapter Runtime (Metadata): Unable to get the adapter type "<adapterName>".
Cause: The method getConnectionAdapterMetadata in com.wm.pkg.art.metadata.ConnectionMetadataService
was unable to create a WmAdapterType instance using the specified adapter name.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0233E Adapter Runtime (Metadata): Unable to get the connection type "<className>".
Cause: The method getConnectionAdapterMetadata in com.wm.pkg.art.metadata.ConnectionMetadataService
was unable to create a connection factory using the specified class name.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0234E Adapter Runtime (Metadata): Unable to get a connection for resource "<aliasName>".
Cause: WmART failed to create a WmConnection instance based on the specified connection alias.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0235E Adapter Runtime (Metadata): Error in <methodName>. Missing parameter: <paramName>.

Cause: The method in com.wm.pkg.art.metadata.InteractionMetadataService failed to retrieve notification
metadata because the specified request parameter was missing.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

332 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0114.0236E Adapter Runtime (Metadata): The connectionAlias or listenerNodeName must be specified.

Cause: The method in com.wm.pkg.art.metadata.InteractionMetadataService failed to lookup/validate
notification values because neither the connection node alias nor the listener node was provided in the request.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0237E Adapter Runtime (Metadata): Value for parameter missing: <parameterName>.

Cause: The operation input requires the metadata parameter listed in the message text, but the value was not
provided.
Response: Add the metadata property and a value to the operation inputs and resubmit.

ART.0114.0238E Adapter Runtime (Metadata): Value for parameter <parameterName> does not match data type <typeName>.
Cause: The value submitted with the operation input does not match the metadata parameter listed in the
message text.
Response: Change the type of the value for the operation and resubmit.

ART.0114.0239E Adapter Runtime (Metadata): Number of fields does not match number of types in a record definition.
Cause: The operation input requires a field type and a field name for each output field specification.
Response: Ensure that the number of entries in the array of values for the field names and field types are equal
and resubmit.

ART.0114.0240E Adapter Runtime (Metadata): Parameter missing: <parameterName>.

Cause: The operation input is missing the required parameter listed in the message text.
Response: Ensure that the input contains an entry for the parameter and resubmit.

ART.0114.0241E Adapter Runtime (Metadata): Unrecognized parameter <parameterName> specified.

Cause: The operation input contains the parameter listed in the message text, which is not defined for this
template.
Response: Remove the parameter from the operation input and resubmit.

ART.0114.0242E Adapter Runtime (Metadata): Required parameter "<parameterName>" is missing, or has no value.
Cause: The operation is missing a required parameter.
Response: Provide the missing parameter value, and resubmit the operation.

webMethods Error Message Reference Version 6.5 and 6.5.1 333

CHAPTER 7 webMethods Integration Server

ART.0114.0243E Adapter Runtime (Metadata): Failed to run <serviceName> service. Details provided in error log.
Cause: An exception was caught while executing the service.
Response: Look in the error log for details on the original exception.

ART.0114.0244E Adapter Runtime (Metadata): Resource domain "<domainName>" is not recognized by provider
"<providerName>".
Cause: The specified resource domain is not registered for the template.
Response: This error should only be encountered while using the webMethods ADK for adapter development.
If you are developing an adapter, ensure that the specified resource domain is registered for your template. If
you are not developing an adapter, contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0245E Adapter Runtime (Metadata): Failed to update IO properties in template "<templateName>"

Cause: An exception was caught while updating IO properties in the specified template.
Response: Look in the error log for details on the original exception.

ART.0114.0301E Adapter Runtime (Transaction): Unable to commit transaction. A transaction name must be specified.
Cause: WmART failed to determine the name of a transaction.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0302E Adapter Runtime (Transaction): Error while committing transaction <transactionName>. The transaction in
progress is <stateName>.
Cause: The transaction name does not match the specified connection state.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0303E Adapter Runtime (Transaction): Unable to commit transaction.

Cause: An error occurred while committing a transaction.
Response: If the adapter uses a connection that supports LocalTransaction, ensure that it is implemented
properly. If the problem persists, contact webMethods Customer Care. Please have the following information
available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

334 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0114.0304E Adapter Runtime (Transaction): Unable to rollback transaction. A transaction name must be specified.
Cause: WmART failed to determine the name of a transaction.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0305E Adapter Runtime (Transaction): Error while rolling back transaction <transactionName>. The transaction in
progress is <stateName>.
Cause: The specified transaction name does not match the specified connection state.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0306E Adapter Runtime (Transaction): Unable to rollback transaction.

ART.0114.0307E Adapter Runtime (Transaction): Retryable Error during commit transaction.

Cause: An unexpected system error occurred while committing a transaction. The transaction may be re-tried.
Response: Ensure that the back-end resource for the transaction can be reached from the server and is in a valid
state. If the problem persists, contact webMethods Customer Care. Please have the following information
available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0350E Adapter Runtime (Transaction): Unable to set transaction timeout to <quantity> seconds.
Cause: WmART has detected that an XAResource failed to set the transaction timeout to the specified number
of seconds.
Response: Verify that the back-end resource for the transaction can be reached from the server and is in a valid
state. If the problem persists, contact webMethods Customer Care. Please have the following information
available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0351E Adapter Runtime (Transaction): Unable to create Transaction Manager.

Cause: WmTransactionManagerFactory failed to create a TransactionManager.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

webMethods Error Message Reference Version 6.5 and 6.5.1 335

CHAPTER 7 webMethods Integration Server

ART.0114.0352E Adapter Runtime (Transaction): Unable to create Transaction Manager with transaction timeout set to
<quantity> seconds.
Cause: WmTransactionManagerFactory failed to create a TransactionManager with the specified number of
timeout seconds.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0353E Adapter Runtime (Transaction): Unable to set transaction timeout. Invalid timeout value <paramValue>.
Cause: com.wm.pkg.art.transaction.Service.setTransactionTimeout could not cast the specified object to type
Integer.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0501E "Internal ADK Error: class <className> method <methodName> not supported."
Cause: An attempt to call an unsupported method has been made.
Response: The adapter's implementation(s) of WmManagedConnectionFactory should not call
super.createConnectionFactory. If this is the case, contact webMethods Customer Care. Please have the
following information available: system and setup specifics, journal logs, and error logs with the stack trace
exposed.

ART.0114.0502E Unable to get connection handle. Connection handle already exists.

Cause: WmART has attempted to create a second CCI Connection for a WmManagedConnection instance.
WmManagedConnection only supports a single CCI Connection.
Response: The adapter's implementation(s) of WmManagedConnection should not call super.getConnection. If
this is the case, contact webMethods Customer Care. Please have the following information available: system
and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0503E Unable to get object from record. Key is <keyName>. Expected object of type <typeName>. Found object of
type <typeName>.
Cause: An object stored in a WmRecord at the specified key is not of the expected type.
Response: Ensure that the object previously stored via WmRecord.put matches the type handled by the
WmRecord.get method you are using.

ART.0114.0504E Object not found in record. Key is <keyName>. Expected object of type <typeName>.
Cause: No object was found in a WmRecord for the specified key.
Response: Verify that the put method using the specified key has previously been called on the WmRecord
object. Also, ensure that the key name is correct.

336 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0114.0505E Error while invoking adapter service <serviceName>.

Cause: An error occurred during execution of the specified adapter service's execute method.
Response: Ensure that the adapter's execute method is handling the input and output (WmRecord) records
properly. Also ensure that the WmManagedConnection passed into the method is correct.

ART.0114.0506E Unable to get resource bundle. Locale is not specified.

Cause: A null Locale reference was passed into a method of AdapterResourceBundleManager.
Response: If the adapter calls a method of AdapterResourceBundleManager that takes a Locale instance,
ensure that the instance is not null.

ART.0114.0513E Unable to get Adapter Resource Bundle. Bundle name not specified.
Cause: Your implementation of WmAdapter.getAdapterResourceBundleName is returning a null value.
Response: Ensure that getAdapterResourceBundleName is returning a String containing the name of a valid
resource bundle.

ART.0114.0514E Unable to get Adapter Resource Bundle <className>.

Cause: WmAdapter failed to create an instance of AdapterResourceBundleManager using the specified
resource bundle.
Response: Ensure that your implementation of WmAdapter.getAdapterResourceBundleName is returning the
name of a valid resource bundle for the server's default locale.

ART.0114.0515E Unable to get Adapter Display Name. Adapter Resource Bundle not found.
Cause: No AdapterResourceBundleManager exists for the adapter.
Response: This condition should have been caught during WmAdapter construction; this condition might
indicate an internal error. Contact webMethods Customer Care. Please have the following information
available: system and setup specifics, journal logs, and
Response: error logs with the stack trace exposed.

ART.0114.0516E Unable to get Adapter Display Name.

Cause: WmAdapter failed to retrieve the adapter's display name for the server's locale.
Response: Ensure that the adapter's implementation of getAdapterName, concatenated with the constant
ADKGLOBAL.RESOURCEBUNDLEKEY_DISPLAYNAME, is a valid key in your AdapterResourceBundle for
the default locale.

webMethods Error Message Reference Version 6.5 and 6.5.1 337

CHAPTER 7 webMethods Integration Server

ART.0114.0517E Unable to get Adapter Description. Adapter Resource Bundle not found.
Cause: No AdapterResourceBundleManager exists for the adapter.
Response: This condition should be caught during WmAdapter construction; this condition might indicate an
internal error. Contact webMethods Customer Care. Please have the following information available: system
and setup specifics, journal logs, and
Response: error logs with the stack trace exposed.

ART.0114.0518E Unable to get Adapter Description.

Cause: WmAdapter failed to retrieve the adapter's description string for the server's locale.
Response: Ensure that the adapter's implementation of getAdapterName, concatenated with the constant
ADKGLOBAL.RESOURCEBUNDLEKEY_DESCRIPTION, is a valid key in your AdapterResourceBundle for
the default locale.

ART.0114.0519E Unable to get Adapter Vendor Name. Adapter Resource Bundle not found.
Cause: No AdapterResourceBundleManager exists for the adapter.
Response: This condition should be caught during WmAdapter construction; this condition might indicate an
internal error. Contact webMethods Customer Care. Please have the following information available: system
and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0520E Unable to get Adapter Vendor Name.

Cause: WmAdapter failed to retrieve the adapter's vendor name string for the server's locale.
Response: Ensure that the adapter's implementation of getAdapterName, concatenated with the constant
ADKGLOBAL.RESOURCEBUNDLEKEY_VENDORNAME, is a valid key in your AdapterResourceBundle for
the default locale.

ART.0114.0524E Unable to get Adapter Base Online Help URL. Adapter Resource Bundle not found.
Cause: There is no AdapterResourceBundleManager for the adapter.
Response: This condition should be caught during WmAdapter construction; this condition might indicate an
internal error. Contact webMethods Customer Care. Please have the following information available: system
and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0525E Unable to get Adapter Base Online Help URL.

Cause: WmAdapter failed to retrieve the localized path to one of the adapter's online help pages.
Response: Ensure that a help page key exists in your AdapterResourceBundle for
ADKGLOBAL.RESOURCEBUNDLEKEY_LISTRESOURCES,
ADKGLOBAL.RESOURCEBUNDLEKEY_LISTCONNECTIONTYPES,
ADKGLOBAL.RESOURCEBUNDLEKEY_LISTPOLLINGNOTIFICATIONS,

338 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ADKGLOBAL.RESOURCEBUNDLEKEY_LISTPOLLINGNOTIFICATIONDETAILS, and
ADKGLOBAL.RESOURCEBUNDLEKEY_ABOUT.

ART.0114.0530E Unable to get ManagedConnection. Internal error.

Cause: A service or notification cl+I35ass is interacting with a resource for which no connection exists.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0533E Unable to get ManagedConnectionFactory description. Adapter Resource Bundle not found.
Cause: The first argument to a call to WmDescriptor.setDescriptions is null.
Response: Be sure to supply a valid AdapterResourceBundleManager instance as the first argument in all calls
to WmDescriptor.setDescriptions.

ART.0114.0538E Unable to get connection properties. Connection is null.

Cause: No connection object has been defined for the adapter service.
Response: Ensure that your implementation of WmAdapter.fillAdapterTypeInfo calls
AdapterTypeInfo.addConnectionFactory for the connection factory used by the adapter service.

ART.0114.0539E Internal Error: The method execute(WmManagedConnection,WmRecord,WmRecord) is not supported in

class <className>.
Cause: An unsupported version of WmAdapterService.execute has been called.
Response: The adapter service template should implement WmAdapterService.execute, not call it. If the
adapter is implementing (rather than calling) WmAdapterService.execute, contact webMethods Customer
Care. Please have the following information available: system and setup specifics, journal logs, and error logs
with the stack trace exposed.

ART.0114.0540E Internal Error: The method fillWmTemplateDescriptor(WmTemplateDescriptor,Locale) is not supported in

class <className>.
Cause: An unsupported version of WmAdapterService.fillWmTemplateDescriptor has been called.
Response: Ensure that the adapter service implements the method
WmAdapterService.fillWmTemplateDescriptor.

ART.0114.0541E no write method in class "<className>" for property "<propertyName>".

Cause: WmART failed to find a public "set" method for the specified property of this service or notification
template class.
Response: Ensure that the class exposes a public "set" method for the property. The method should take a single
argument that matches the underlying type.

webMethods Error Message Reference Version 6.5 and 6.5.1 339

CHAPTER 7 webMethods Integration Server

ART.0114.0542E could not set property "<propertyName>" in class "<className>".

Cause: The "set" method for the specified property has an incorrect signature, or is otherwise not JavaBean
compliant.
Response: Ensure that the property's "set" method is public and that it takes a single argument whose type
matches that of the underlying property.

ART.0114.0543E could not introspect class "<className>":

Cause: WmART failed to introspect the specified service or notification template class. This class or another
class exposed as a property is not JavaBean-compliant.
Response: Ensure that the specified class adheres to the JavaBeans standard. This requirement also applies to
any non-primitive classes exposed as properties in the specified class.

ART.0114.0544E Value too short for parameter "<paramName>".

Cause: The value provided for the specified parameter is too short.
Response: Be sure to enter a valid value for all adapter service, connection, listener, and polling notification
parameters.

ART.0114.0545E Value missing for parameter "<paramName>".

Cause: No value was provided for the specified parameter.
Response: Be sure to enter a valid value for all adapter service, connection, listener, and polling notification
parameters.

ART.0114.0546E Can not use both a name space and a list of valid values for the same parameter!
Cause: The adapter has declared a resource domain for one or more parameters and has subsequently called
WmDescriptor.setValidValues for the same parameter.
Response: The adapter can either use a resource domain or call WmDescriptor.setValidValues directly, but not
both.

ART.0114.0547E No parameter "<paramName>" in class.

Cause: WmART failed to locate the AdapterFeatureDescriptor for the specified parameter in a connection,
service template, or notification template.
Response: Ensure that the adapter's implementation .class files are installed properly under the packages
folder. If you modify the .class files for the adapter while the Integration Server is running, you must reload
that adapter.

340 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0114.0548E Can not set group name after resourceDomain has already been set.
Cause: You have attempted to pass the name of a parameter to WmDescriptor.createGroup after declaring a
resource domain for that same parameter.
Response: Ensure that all calls to WmDescriptor.createGroup precede calls to
WmDescriptor.setResourceDomain for each template class.

ART.0114.0549E Group name already set for this parameter.

Cause: You have attempted to add the same parameter to more than one group.
Response: Ensure that no one parameter appears in more than one call to WmDescriptor.createGroup for the
adapter and each of your template classes.

ART.0114.0550E Field map used in more than one group.

Cause: The adapter is attempting to add the same field map to more than one group.
Response: The field map name is the first item in the list of Strings passed to
WmTemplateDescriptor.createFieldMap. For a given WmTemplateDescriptor instance, ensure that this name
appears in no more than one call to WmTemplateDescriptor.createGroup.

ART.0114.0551E Field map used in both variable and non-variable mode.

Cause: The adapter has declared the same field map twice: once with a fixed number of fields and once with a
variable number of fields.
Response: The field map name is the first item in the list of Strings passed to
WmTemplateDescriptor.createFieldMap. This name should not appear first in more than one call to
WmTemplateDescriptor.createFieldMap.

ART.0114.0552E Tree map requires parameter to be in a field map

Cause: You have specified a parameter in a call to WmTemplateDescriptor.setTreeMap that has not previously
been specified in a call to WmTemplateDescriptor.createFieldMap.
Response: Ensure that you first provide the first argument in the members argument of a call to
createFieldMap. This should be done before the adapter makes a call to setTreeMap.

ART.0114.0553E This operation is not inside of an adapter, and may not use resourceDomains.
Cause: The adapter has created its own WmTemplateDescriptor object and subsequently called
WmTemplateDescriptor.setResourceDomain, giving it a resourceDomainName value that is not one of the

webMethods Error Message Reference Version 6.5 and 6.5.1 341

CHAPTER 7 webMethods Integration Server

following: WmTemplateDescriptor.INPUT_FIELD_NAMES,
WmTemplateDescriptor.OUTPUT_FIELD_NAMES, or WmTemplateDescriptor.INPUT_EXPRESSIONS.
Response: The adapter's implementation(s) of WmAdapterService.fillWmTemplateDescriptor should set
resource domains on the WmTemplateDescriptor object passed into it. It should never create its own instance
of WmTemplateDescriptor.

ART.0114.0554E Property "<propertyName>" has a resourceDomain dependency on itself.

Cause: You are attempting to create a resource domain for a property that also appears in the resource domain
dependencies list.
Response: Remove the property name from the dependencies argument in your call to
WmTemplateDescriptor.setResourceDomain.

ART.0114.0555E Cannot set resourceDomain dependencies for parameter "<paramName>" because resourceDomain for
parameter "<paramName>" has not been set yet or has no dependencies. Both parameters are in the same tuple, and must
have the same dependencies.
Cause: The specified parameters are in the same tuple, but their resource domains are declared in the wrong
order.
Response: For any parameters that appear in calls to WmTemplateDescriptor.createTuple, ensure that the calls
to WmTemplateDescriptor.setResourceDomain for those parameters appear in the same order as listed in the
createTuple call.

ART.0114.0556E Parameters "<paramName>" and "<paramName>" are in the same tuple, but have different resourceDomain
dependencies: "<dependName>"/"<dependName>"
Cause: The specified parameters are in the same tuple, but have different resource domain dependencies.
Response: Ensure that parameters declared in the same call to WmTemplateDescriptor.createTuple have
identical dependency lists for all subsequent calls to WmTemplateDescriptro.setResourceDomain.

ART.0114.0557E Could not set resourceDomain for parameter "<paramName>".

Cause: A general error occurred during a call to WmTemplateDescriptor.setResourceDomain. WmART failed
to set the resource domain for the specified parameter.
Response: If the parameter is used in field maps or tuples, ensure that you have called
WmTemplateDescriptor.createFieldMap and/or WmTemplateDescriptor.createTuple prior to calling
WmTemplateDescriptor.setResourceDomain. Contact webMethods Customer Care if the problem persists.
Please have the following information available: system and setup specifics, journal logs, and error logs with
the stack trace exposed.

342 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0114.0560E "Unable to get property descriptor."

Cause: An error occurred while introspecting a connection, an adapter service template, a notification
template, or a listener class.
Response: Ensure that all such classes adhere to the JavaBeans standard. If the problem persists, contact
webMethods Customer Care. Please have the following information available: system and setup specifics,
journal logs, and
Response: error logs with the stack trace exposed.

ART.0114.0561E Argument "names" should not be null.

Cause: A connection tried to construct an instance of ResourceDomainValues, but the second argument is null.
Response: Ensure that your implementation(s) of WmManagedConnection.adapterResourceDomainLookup
are passing valid, non-null values for all ResourceDomainValues constructor arguments.

ART.0114.0562E The length of argument "<argName>" is not equal to the length of "names".
Cause: The number of internal names arguments does not match the number of displayNames, endNames, or
requiredFlags in a call to the constructor for ResourceDomainValues.
Response: For each instantiation of ResourceDomainValues, ensure that the number of items in the second
argument, names, matches the number of items given in all subsequent constructor arguments.

ART.0114.0563E "Readonly parameter but no read method in class "<className>" for property "<propertyName>"."
Cause: No public "get" method has been defined for the property in the class.
Response: Ensure that you have defined JavaBean-compliant "get" methods for all properties in the specified
class.

ART.0114.0564E The field map "<mapName>" doesn't exist. Please make sure the field map was created first.
Cause: There was an attempt to disable the “Append All” feature of a field map, but WmART could not
identify the specified field map name.
Response: Ensure that the adapter's implementation .class files are installed properly under the packages
folder. If you modify the .class files for the adapter while the Integration Server is running, you must reload
that adapter.

ART.0114.0565E The field map provided "<mapName>" and the actual one "<mapName>" do not match.
Cause: There was an attempt to disable the "Append All" feature of a field map, but the specified field map
name does not match the expected field map name.
Response: Ensure that the adapter's implementation .class files are installed properly under the packages
folder. If you modify the .class files for the adapter while the Integration Server is running, you must reload
that adapter.

webMethods Error Message Reference Version 6.5 and 6.5.1 343

CHAPTER 7 webMethods Integration Server

ART.0114.0566E Error while setting the flag to disable append all button in the editor.
Cause: An error occurred while disabling the "Append All" feature of a field map. Additional details may
appear in adjacent log messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0600E Unable to get a connection. Connection Manager not initialized.

Cause: A Connection Factory was unable to get a reference to the Connection Manager.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0601E Internal Error: The execute(InteractionSpec,Record,Record) in class <className> is not supported.

Cause: An unsupported version of javax.resource.cci.Interaction.execute has been called.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0700E Adapter Runtime: Errors occurred in cluster coordination repository access. <notificationName> will be
shut down. See error log for details.
Cause: An exception was caught during processing.
Response: Look in the error log for details on the original exception.

ART.0114.0701E Adapter Runtime: Unable to retrieve ART instance/session ID.

Cause: The Adapter Runtime (ART) session ID failed to initialize.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.0702E Adapter Runtime: Errors occurred attempting to stop <notificationName>. See error log for details.
Cause: An exception was caught stopping the notification.
Response: Look in the error log for details on the original exception.

ART.0114.0703E Adapter Runtime: Errors occurred attempting to confirm cluster member. See error log for details.
Cause: An exception was caught trying to validate Adapter Runtime (ART) cluster members.
Response: Look in the error log for details on the original exception.

344 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0114.0704E Adapter Runtime: Internal Error-assert failed - node: <notificationName>, detail:<errorDetail>. Contact
technical support.
Cause: An unexpected exception occurred during processing.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, error logs with the stack trace exposed, and the
detail in this error message.

ART.0114.0705E Adapter Runtime: Errors occurred attempting to start <notificationName>. See error log for details.
Cause: An exception was caught starting the notification.
Response: Look in the error log for details on the original exception.

ART.0114.0707E Adapter Runtime: "<modeName>" is an invalid setting for the cluster coordination mode of
<notificationName>. Valid values: <validModes>.
Cause: An unsupported mode was encountered.
Response: Change the mode to one of the supported settings, and restart the notification.

ART.0114.0708E Adapter Runtime: <value> is an invalid setting for max process time of <notificationName>. Value must be
an number between <minValue> and <maxValue>.
Cause: An invalid maximum process time was encountered for the notification.
Response: Change the maximum process time to a value within the specified range, and restart the notification.

ART.0114.0709E Adapter Runtime: <value> is an invalid setting for max setup time of <notificationName>. Value must be an
number between <minValue> and <maxValue> .
Cause: An invalid maximum setup time was encountered for the notification.
Response: Change the maximum setup time to a value within the specified range, and restart the notification.

ART.0114.0710E Adapter Runtime: Adapter cluster properties files are not the same across the cluster. Please synchronize
all cluster properties files and restart servers.
Cause: The Adapter Runtime encountered inconsistent cluster property files.
Response: Ensure the cluster property files are the same for the adapter on each clustered Integration Server.

webMethods Error Message Reference Version 6.5 and 6.5.1 345

CHAPTER 7 webMethods Integration Server

ART.0114.0711E Adapter Runtime: Notification <notificationName> was unexpectedly removed from cluster.
Cause: Another instance of this notification erroneously determined that this current instance failed. The
current instance was removed.
Response: Check the logs on other servers in the cluster. A log on one of the servers will include message 1405,
which indicates that this instance was removed. Check clock synchronization and network connectivity
between the two servers.

ART.0114.0712E Adapter Runtime: Operation failed because notification <notificationName> was unexpectedly removed
from cluster.
Cause: Another instance of this notification erroneously determined that this current instance failed. The
current instance was removed. Note that this error is similar to ART.0114.0711E; however, in this case the node
was changing states.
Response: Check the logs on other servers in the cluster. A log on one of the servers will include message 1405,
which indicates that this instance was removed. Check clock synchronization and network connectivity
between the two servers.

ART.0114.1004E Adapter Runtime: Parameter parsing error.

Cause: WmART attempted to encrypt or decrypt a null string value.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.1005E Adapter Runtime: Parameter parsing error.

Cause: WmART failed to encrypt a string value.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.1006E Adapter Runtime: Parameter parsing error.

Cause: WmART failed to decrypt a string value.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.1008D Adapter Runtime: Jar file <jarFileName> is not an update jar file. Unable to read the <updateFileName>
entry.
Cause: This message applies to adapters that use update jar files to deliver updates. The update.cnf file is not
readable in the update jar file.
Response: No action is required.

346 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0114.1009D Adapter Runtime: Jar file <jarFileName> is not an update jar file. It does not contain the <updateFileName>
entry.
Cause: This message applies to adapters that use update jar files to deliver updates. The update.cnf file is
missing from the update jar file.
Response: No action is required.

ART.0114.1010D Adapter Runtime: File <fileName> is not an update file. It is not a jar file.
Cause: This message applies to adapters that use update jar files to deliver updates. A file was found in the
adapters update directory that is not a jar file.
Response: No action is required.

ART.0114.1011D Adapter Runtime: Error initializing UpdateFile. Missing required parameter.

Cause: This message applies to adapters that use update jar files to deliver updates. A null value was supplied
for the file name parameter. A value is required.
Response: No action is required.

ART.0114.1012D Adapter Runtime: No updates found for adapter: <adapterName>.

Cause: No installed updates were found for the adapter.
Response: No action is required.

ART.0114.1013E Adapter Runtime: Unable to locate the package name for adapter: <adapterName>.
Cause: The Integration Server package name for the adapter could not be determined.
Response: Ensure the adapter package depends on the WmART package, and reload the adapter package.

ART.0114.1014W Adapter Runtime: Adapter <adapterName> is missing required fix <fixName>.

Cause: This message applies to adapters that use update jar files to deliver updates. A fix required by the
adapter was not found.
Response: Install the required fix, and reload the adapter.

ART.0114.1015E Adapter Runtime: Error loading update jar file <jarFileName>. An exception was encountered loading the
<updateFileName> file.
Cause: This message applies to adapters that use update jar files to deliver updates. An exception occurred
trying to load the update.cnf file in the update jar.
Response: Look in the error log for details on the original exception.

webMethods Error Message Reference Version 6.5 and 6.5.1 347

CHAPTER 7 webMethods Integration Server

ART.0114.1016E Adapter Runtime: Error loading update jar file <jarFileName>. The <updateFileName> file is missing the
required property updateName.
Cause: This message applies to adapters that use update jar files to deliver updates. The update.cnf file
associated with the fix is missing a required value.
Response: Re-apply the fix, and reload the adapter.

ART.0114.1017E Adapter Runtime: Error loading update jar file <jarFileName>. The update name contains the illegal
character ';'.
Cause: This message applies to adapters that use update jar files to deliver updates. The fix name in the
update.cnf file contains an illegal semicolon (;) character.
Response: Re-apply the fix, and reload the adapter.

ART.0114.1018E Adapter Runtime: Error loading update information. The '<tagName>' tag is missing.
Cause: The fix name is missing.
Response: Re-apply the fix, and reload the adapter.

ART.0114.1103E Adapter Runtime: Facility <facilityName> - <facilityDesc> error. Log handler not found.
Cause: WmART failed to get a Log Handler from the Integration Server for the specified facility.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.1105E Adapter Runtime: No LogProducer for facility <facilityName> - <facilityDesc>.

Cause: WmART attempted to log a message, but no Log Producer exists for the specified facility.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.1106E Adapter Runtime: Facility <facilityName> - <facilityDesc> error. No facilities registered.

Cause: WmART failed to get the list of facility codes from the Log Handler.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0114.1112E Adapter Runtime: Unable to instantiate class <templateClassName> in adapter <adapterName>. See error
log for details.
Cause: An exception occurred trying to instantiate a template for the adapter.
Response: Ensure package dependencies are set correctly, and reload the adapter

348 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0114.1113E Adapter Runtime: Class <className> is not a Service or Notification template class.
Cause: An invalid class was registered as a template.
Response: If you are using the webMethods ADK to develop an adapter, ensure your class is properly
registered and coded to be a template. If this message is being issued from a webMethods adapter, contact
webMethods Customer Care. Please have the following information available: system and setup specifics,
journal logs, and error logs with the stack trace exposed.

ART.0114.1401W Adapter Runtime: Coordination data for <notificationName> is invalid. Coordination will revert to a default
state.
Cause: Coordination data in the repository was not valid. If the server was recently upgraded, this might
simply represent a change in record formats, and the operation you are performing will automatically correct
the data for you. If you have not recently upgraded or the problem persists, it is likely that the repository is
corrupted.
Response: If you recently performed a server upgrade, no action is required. If you have not recently upgraded
or the problem persists, check repository logs for errors.

ART.0114.1405W Adapter Runtime: Processing for <notificationName> on server <serverID> has timed-out or failed. Local
instance will take over.
Cause: Remote failure detected.
Response: Check logs on indicated server for messages ART.0114.0711E or ART.0114.0712E. If the messages are
in the log, refer to those error messages for a resolution. If the messages do not appear in the logs, no action is
required.

ART.0114.1407W Adapter Runtime: Illegal overlap occurred in node <notificationName>. Please verify clock synchronization
with cluster member '<serverName>'
Cause: An illegal overlap exception was detected.
Response: Ensure the clocks are synchronized for all Integration Servers in the cluster.

ART.0114.1411E Adapter Runtime: Unable to access <clusterPropertyFile> file for adapter "<adapterName>". Please check
the file permissions. Running with default configuration.
Cause: The cluster property file could not be read.
Response: Ensure the cluster property file exists and is readable for the specified adapter.

ART.0114.1412E Adapter Runtime: Unable to parse <clusterPropertyFile> file for adapter "<adapterName>". Please correct
file format. Running with default configuration.
Cause: The cluster property file could not be parsed.
Response: Validate the cluster property file format for the specified adapter.

webMethods Error Message Reference Version 6.5 and 6.5.1 349

CHAPTER 7 webMethods Integration Server

ART.0114.1415E Adapter Runtime: An internal error occurred while rendering cluster settings for adapter <adapterName>.
Updated settings will not be persisted.
Cause: The settings could not be saved to the cluster property file.
Response: Ensure the directory and the cluster file are writable.

ART.0114.1416E Adapter Runtime: Error attempting to save cluster settings for adapter <adapterName>. Error
<exceptionDescription>
Cause: An exception occurred trying to save the cluster settings.
Response: Look in the error log for details on the original exception.

ART.0114.1418W Adapter Runtime: Illegal overlap occurred in node <notificationName>. Please increase setup timeout.
Current setting: <setupTimeoutSetting>, actual time: <setupTimeoutSetting> seconds
Cause: The requested operation took longer than the allotted time; the operation had no other errors.
Response: Increase the node's timeout value as indicated by the actual time.

ART.0114.1419W Adapter Runtime: Illegal overlap occurred in node <notificationName>. Please increase execute timeout.
Current setting: <executeTimeoutSetting>, actual time: <executeTimeoutSetting> seconds
Cause: A polling operation took longer than the allotted time; the polling operation had no other errors.
Response: Increase the node's timeout value as indicated by the actual time.

ART.0115.3202E Adapter Runtime (Listener): Listener error releasing connection for <listenerNode>. Error: <errorText>.
Cause: An error occurred while closing the connection associated with the specified listener.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3203E Adapter Runtime (Listener): Error creating listener object: Null argument on init call.
Cause: The method WmNotificationListener.initListenerNodeProperties was passed a null ListenerNode
instance.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3204E Adapter Runtime (Listener): Error creating listener object: NSName null.
Cause: The method WmNotificationListener.initListenerNodeProperties was unable to derive the name of a
listener node from the ListenerNode instance.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

350 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0115.3207E Adapter Runtime (Listener): Illegal event type received: <eventNumber>.

Cause: The method WmNotificationListener.doNotify was passed the specified invalid event ID.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3208E Adapter Runtime (Listener): Error during listener event. Error: <errorText>.
Cause: An error occurred while processing a listener event. Refer to the error message text for more details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3209E Adapter Runtime (Listener): Error creating listener object <listenerNode>. Error: <errorText>.
Cause: An error occurred creating the specified listener or initializing its properties.
Response: Ensure that the listener and its properties are configured correctly. If the problem persists, contact
webMethods Customer Care. Please have the following information available: system and setup specifics,
journal logs, and error logs with the stack trace exposed.

ART.0115.3211E Adapter Runtime (Listener): Existing transaction rolled back before execution of <listenerNode>.
Cause: WmART detected an incomplete transaction for the specified listener prior to executing it. The
transaction has been rolled back.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3212E Adapter Runtime (Listener): Listener error during execution of <listenerNode>. Error: <errorText> rolling
back existing transaction.
Cause: WmART detected an incomplete transaction for the specified listener prior to executing it. WmART
attempted to rollback the transaction, but failed. Refer to the error message text for more details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3213E Adapter Runtime (Listener): Listener error during execution of <listenerNode>. Error: <errorText> checking
transaction.
Cause: WmART failed to determine whether the specified listener has an open transaction. Refer to the error
message text for more details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

webMethods Error Message Reference Version 6.5 and 6.5.1 351

CHAPTER 7 webMethods Integration Server

ART.0115.3214E Adapter Runtime (Listener): Listener <listenerNode> not Found.

Cause: WmART failed to lookup the specified listener.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3215E Adapter Runtime (Listener): Unable to create listener <listenerNode>. Listener node already exists.
Cause: There was an attempt to create a duplicate listener node.
Response: Enter a new listener node name that is unique to its folder.

ART.0115.3217E Adapter Runtime (Listener): Error creating listener object: <listenerNode>. Invalid package name:
<packageName>.
Cause: ListenerManager.createListener failed to create an instance of the listener because it could not find the
package name in the pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3218E Adapter Runtime (Listener): Error creating listener object: <listenerNode>. Invalid node name.
Cause: ListenerManager.createListener failed to create an instance of the listener because the specified node
name is missing or invalid.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3219E Adapter Runtime (Listener): Error creating listener object: <listenerNode>. Error: <errorText>.
Cause: An error occurred while creating the listener. This might be due to an invalid listener node name. Refer
to the error message text for more details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3220E Adapter Runtime (Listener): Unable to get list of listener types supported by node <adapterName>.
Cause: An error occurred in ListenerManager.queryListenerTemplatesSupported for the specified adapter.
Additional details may appear in adjacent error messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

352 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0115.3221E Adapter Runtime (Listener): Unable to get listener node properties <listenerNode>.
Cause: An error occurred while querying the specified listener's properties. Additional details may appear in
adjacent error messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3223E Adapter Runtime (Listener): Unable to update listener <listenerNode>: Error: <errorText>.
Cause: An error occurred while updating the specified listener's properties. Additional details may appear in
adjacent error messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3225E Adapter Runtime (Listener): Unable to delete listener <listenerNode>: Error: <errorText>.
Cause: An error occurred while deleting the specified listener. Additional details may appear in adjacent error
messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3226E Adapter Runtime (Listener): Unable to copy listener <listenerNode>: Error: <errorText>.
Cause: An error occurred while copying the specified listener. Additional details may appear in adjacent error
messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3227E Adapter Runtime (Listener): Unable to copy listener. Error: Source nodeName is required
Cause: The method ListenerManager.copyAdapterListener failed because the source listener node name was
not present in the pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3228E Adapter Runtime (Listener): Unable to copy listener <listenerNode>. Error: newNodeName is required.
Cause: The method ListenerManager.copyAdapterListener failed because the destination listener node name
was not present in the pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

webMethods Error Message Reference Version 6.5 and 6.5.1 353

CHAPTER 7 webMethods Integration Server

ART.0115.3229E Adapter Runtime (Listener): Unable to copy listener <listenerNode>. Error: publishableDocumentName is
required.
Cause: The method ListenerManager.copyAdapterListener failed because the destination listener publishable
document name was not present in the pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3230E Adapter Runtime (Listener): Unable to copy listener <listenerNode>. Error: newPkg is required.
Cause: The method ListenerManager.copyAdapterListener failed because the destination listener node
package name was not present in the pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3231E Adapter Runtime (Listener): Unable to copy listener <listenerNode> to <newListenerNode>. Error: Unable to
get source listener node.
Cause: The method ListenerManager.copyAdapterListener failed because the source listener node name is
invalid.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3232E Adapter Runtime (Listener): Unable to copy listener <listenerNode>. Error: New name already exists
<newListenerNode>.
Cause: The method ListenerManager.copyAdapterListener failed because the specified destination listener
node name already exists in the package.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3235E Adapter Runtime (Listener): Unable to rename listener <listenerNode>. Error: <errorText>.
Cause: An error occurred while renaming the specified listener. Additional details should appear in adjacent
error messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

354 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0115.3236E Adapter Runtime (Listener): Unable to find listener <listenerNode>.

Cause: The method ListenerManager.queryListenerStatistics failed because it could not locate the specified
listener node.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3237E Adapter Runtime (Listener): Unable to get listener <listenerNode>. Error: Listener class name is not
specified.
Cause: The method ListenerNode.getListener failed because it could not locate the WmConnectedListener
implementation class name.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3238E Adapter Runtime (Listener): Error in Listener Callback:<callbackName> notification <listenerNode>.

Cause: An error occurred while processing a listener notification event for the specified listener. If there is a
callback name in the error message, it corresponds to the notification event.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3239E Adapter Runtime (Listener): Missing required parameter on service: <paramName>

Cause: The method ListenerManager.queryListenerTemplatesSupported failed because the specified
parameter was not present in the pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3240E Adapter Runtime (Listener): Unable to retrieve listener data. No listener name specified.
Cause: The method ARTAdmin.retrieveListenerData failed because no listener was present in the pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3241E Adapter Runtime (Listener): Error retrieving listener: <listenerNode>. Error: <errorText>
Cause: An error occurred while retrieving information about the listener. Refer to the error text for more
details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

webMethods Error Message Reference Version 6.5 and 6.5.1 355

CHAPTER 7 webMethods Integration Server

ART.0115.3242E Adapter Runtime (Listener): Unable to get listener properties for adapter: <adapterName>, listener type:
<listenerClass>.
Cause: An error occurred while retrieving properties of the listener in the specified adapter.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3243E Adapter Runtime (Listener): Error retrieving listeners. Missing parameter: <paramName>.
Cause: The method ARTAdmin.retrieveListeners failed because the adapter name was not present in the
pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3244E Adapter Runtime (Listener): Error setting listener status. Missing parameter: <paramName>
Cause: The method ARTAdmin.setListenerStatus failed because the listener name was not present in the
pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3245E Adapter Runtime (Listener): Error retrieving listener types. Missing parameter: <paramName>
Cause: The method ARTAdmin.retrieveListenerTypes failed because the adapter name was not present in the
pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3246E Adapter Runtime (Listener): Error retrieving listener types. Error: <errorText>
Cause: An error occurred while retrieving the listener types supported by an adapter. Refer to the error text for
more details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3247E Adapter Runtime (Listener): Error deleting listener. Missing parameter: <paramName>
Cause: The method ARTAdmin.deleteListener failed because the listener name was not present in the pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

356 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0115.3248E Adapter Runtime (Listener): Error deleting listener: <listenerNode>. Unable to find the node.
Cause: The method ARTAdmin.deleteListener failed because the specified listener node name is invalid.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3249E Adapter Runtime (Listener): Error deleting listener: <listenerNode>.

Cause: An error occurred while deleting the specified listener. Additional details may appear in adjacent error
messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3250E Adapter Runtime (Listener): Error setting properties for listener: <listenerNode>.
Cause: An error occurred while setting the properties of the specified listener. Additional details may appear in
adjacent error messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3251E Adapter Runtime (Listener): Invalid listener node name: <listenerNode>.

Cause: The specified listener name is missing or invalid.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3252E Adapter Runtime (Listener): Unable to commit transaction for listener <listenerNode>. Error: <errorText>.
Cause: WmNotificationListener failed to commit a transaction for the specified listener. Refer to the error text
for more details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3253E Adapter Runtime (Listener): Listener <listenerNode> did not process the notification.
Cause: The listener received a notification and was unable to find a listener notification to process it.
Response: Check to ensure that the listed listener has listener notifications registered with it and that at least
one of them is enabled.

webMethods Error Message Reference Version 6.5 and 6.5.1 357

CHAPTER 7 webMethods Integration Server

ART.0115.3255E Adapter Runtime (Listener): Unable to start listener: <listenerNode>. Cannot retrieve connection from
connection node: <connectionNode>
Cause: The listener requires a connection to start. The startup processing could not get a connection from the
listed connection node.
Response: Check to ensure that the listed connection is enabled. If the connection is pooled, increase the
maximum connections allowed in the pool.

ART.0115.3256E Adapter Runtime (Listener): Unable to start listener: <listenerNode>. Error: <errorText>
Cause: An unexpected exception occurred while trying to enable a notification.
Response: Check the Integration Server error log for details on the unexpected exception.

ART.0115.3257E Adapter Runtime (Listener): Exceeded max retries. Shutting down listener <listenerNode>. Error:
<errorText>
Cause: A retryable error occurred while attempting to execute the listener. The maximum number of retries is
exceeded.
Response: Check the Integration Server error log for details on the retryable exception. Correct the error and try
to enable the listener.

ART.0115.3258E Adapter Runtime (Listener): Fatal error in listener <listenerNode>. See error log for details
Cause: An unexpected exception occurred during listener operation.
Response: Check the Integration Server error log for details on the unexpected exception.

ART.0115.3259E Adapter Runtime (Listener): Unable to enlist connection transactional resource

Cause: An unexpected exception occurred while trying to start a transaction within the listener.
Response: Check the Integration Server error log for details on the unexpected exception. If no related
exceptions are found, contact webMethods Customer Care. Please have the following information available:
system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0115.3260E Adapter Runtime (Listener): Unable to commit transaction for listener <listenerNode>. Listener disabled
Cause: An unexpected exception occurred while trying to commit a transaction within the listener.
Response: Check the Integration Server error log for details on the unexpected exception.

ART.0115.3261E Adapter Runtime (Listener): Connection Node <connectionNode> not enabled.

Cause: An error occurred while trying to retrieve a connection for the listener.
Response: Check to ensure the connection is enabled and restart the listener.

358 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0115.3262E Adapter Runtime (Listener): Fatal error initiating transaction in listener <listenerNode>. See error log for
details
Cause: An unexpected exception occurred while trying to start a transaction within the listener.
Response: Check the Integration Server error log for details on the unexpected exception.

ART.0115.3263E Adapter Runtime (Listener): Connection error while retrieving metadata in listener <listenerNode>. See error
log for details.
Cause: An error occurred while trying to retrieve a connection for the listener.
Response: Check to ensure the connection is enabled. Check the Integration Server error log for details on the
unexpected exception.

ART.0115.3264E Adapter Runtime (Listener): Unable to stop listener: <listenerNode>. Error: <errorText>
Cause: An unexpected exception occurred while trying to stop the listener.
Response: Check the Integration Server error log for details on the unexpected exception.

ART.0115.3265E Adapter Runtime (Listener): Errors occurred. <numberOfErrors> listeners were not suspended. See error
log for details.
Cause: While attempting to suspend all listeners, some of the listeners reported errors.
Response: Look in the error log for details on the specific exceptions.

ART.0115.3266E Adapter Runtime (Listener): Errors occurred. <numberOfErrors> listeners were not enabled. See error log
for details.
Cause: While attempting to enable all suspended listeners, some of the listeners reported errors.
Response: Look in the error log for details on the specific exceptions.

ART.0115.3267E Adapter Runtime (Listener): Cannot update adapter-defined settings in suspended listener <listenerName>.
Cause: The user attempted to update adapter-defined settings for a listener; however, the listener is currently
suspended.
Response: Disable the listener, and retry the operation.

ART.0115.3268E Adapter Runtime (Listener): <listenerName> is in an invalid state for requested operation.
Cause: The user attempted an operation on a listener; however, the listener was not in the proper state for the
operation.
Response: Change the state of the listener to an acceptable state, and retry the operation.

webMethods Error Message Reference Version 6.5 and 6.5.1 359

CHAPTER 7 webMethods Integration Server

ART.0115.3269E Adapter Runtime (Listener): Unable to complete update. Setting connection for listener <listenerName> is
not supported.
Cause: The user attempted to change the connection associated with a listener; however, the listener does not
require a connection.
Response: This operation is not supported.

ART.0115.3270E Adapter Runtime (Listener): Unable to create listener. Setting connection for listener type
<listenerTypeName> is not supported.
Cause: The user attempted to create a listener with a connection; however the listener does not require a
connection.
Response: This operation is not supported.

ART.0115.3271E Adapter Runtime (Listener): Unable to create listener. Must specify connection for listener type
<listenerTypeName>.
Cause: A user attempted to create a listener that requires a connection; however no connection was specified.
Response: Specify a connection, and retry the operation.

ART.0115.3272E Adapter Runtime (Listener): Unable to identify adapter for listener type <listenerTypeName>.
Cause: The Integration Server cannot determine the adapter associated with the specified listener type.
Response: Ensure your package dependencies are set properly. Reload the adapter package, and retry the
operation.

ART.0115.3712E Adapter Runtime (Listener): Error during listener execution.

Cause: Either a fatal error has occurred while executing a listener, or the maximum number of non-fatal errors
has been exceeded while executing a listener.
Response: Ensure that the connection from the listener to the back-end EIS is still valid, and that a
communications path between them exists.

ART.0115.3716W Adapter Runtime (Listener): Failed to retrieve connection for callback in listener <listenerNode>. Error:
<errorText>
Cause: An error occurred while trying to retrieve a connection for the listener shutdown callback processing.
Response: Check to ensure the connection is enabled. Check the Integration Server error log for details on the
unexpected exception.

360 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0115.3717W Adapter Runtime (Listener): Failure in shutdown callback in listener <listenerNode>. Error: <errorText>
Cause: An error occurred during the listener shutdown callback processing.
Response: Details on the error are included in the message. The shutdown will attempt to continue.

ART.0116.3001E Adapter Runtime (Notification): Notification error during execution of <notificationNode>. Error:
<errorText>.
Cause: An error occurred while executing the specified notification. Refer to the text in the error message for
additional details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3002E Adapter Runtime (Notification): Notification error releasing connection for <notificationNode>. Error:
<errorText>.
Cause: WmART failed to release the specified notification's connection back to the connection pool.
Response: For custom adapters, check the connection's implementation for possible blocking situations. If the
problem persists, contact webMethods Customer Care. Please have the following information available:
system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3003E Adapter Runtime (Notification): Error creating notification object: Null argument on init call.
Cause: The method WmNotification.initNotificationNodeProperties failed because it was passed a null
NotificationNode object.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3004E Adapter Runtime (Notification): Error creating notification object: NSName null.
Cause: The method WmNotification.initNotificationNodeProperties failed because it was unable to get the
node name from the NotificationNode object.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3005E Adapter Runtime (Notification): Error creating notification object: <notificationNode>. Publishable
Document name not set.
Cause: The method WmNotification.initNotificationNodeProperties failed because it was unable to get the
publishable document node name for the specified notification.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

webMethods Error Message Reference Version 6.5 and 6.5.1 361

CHAPTER 7 webMethods Integration Server

ART.0116.3006E Adapter Runtime (Notification): Error creating notification object: <notificationNode>. UUID not set.
Cause: The method WmNotification.initNotificationNodeProperties failed because it was unable to get the
specified notification's universal unique identifier (UUID) from the NotificationNode object.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3007E Adapter Runtime (Notification): Illegal event type received: <eventNumber>.

Cause: The method WmNotification.notifyEvent was passed the specified invalid event ID.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3008E Adapter Runtime (Notification): Error during notification event. Error: <errorText>.
Cause: An error occurred in the method WmNotification.notifyEvent. Refer to the error message text for more
details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3009E Adapter Runtime (Notification): Error creating notification object <notificationNode>. Error: <errorText>.
Cause: An error occurred in the method NotificationNode.getNotification while creating the notification. Refer
to the error message text for more details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3010E Adapter Runtime (Notification): Error publishing notification <notificationNode>. Error: <errorText>.
Cause: An error occurred in the method WmAsynchronousNotification.publishToDispatcher while publishing
a non-duplicate document from the specified notification. Refer to the error message text for more details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3011E Adapter Runtime (Notification): Existing transaction rolled back before execution of <notificationNode>.
Cause: WmART detected an incomplete transaction for the notification prior to processing a notification event.
The transaction has been rolled-back.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

362 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0116.3012E Adapter Runtime (Notification): Notification error during execution of <notificationNode>. Error: <errorText>
rolling back existing transaction.
Cause: WmART detected an incomplete transaction for the specified notification prior to processing a
notification event. It attempted to rollback the transaction, but failed. Refer to the error message text for more
details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3013E Adapter Runtime (Notification): Notification error during execution of <notificationNode>. Error: <errorText>
checking transaction.
Cause: WmART failed to determine whether the specified notification has an open transaction. Refer to the
error message text for more details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3014E Adapter Runtime (Notification): Notification <notificationNode> not Found.

Cause: WmART failed to locate the specified notification.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3015E Adapter Runtime (Notification): Unable to create notification <notificationNode>. Notification node already
exists.
Cause: WmART failed to create the specified notification because a notification with this name already exists.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3016E Adapter Runtime (Notification): Unable to create publishable document <notificationNode>. Error:
<errorText>.
Cause: The method NotificationFactory.createPublishableDocument failed to create a document for the
specified notification. Refer to the error message text for more details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3018E Adapter Runtime (Notification): Error creating notification object: <notificationNode>. Invalid node name.
Cause: The specified notification node name is missing or improperly formatted.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

webMethods Error Message Reference Version 6.5 and 6.5.1 363

CHAPTER 7 webMethods Integration Server

ART.0116.3019E Adapter Runtime (Notification): Error creating notification object: <notificationNode>. Error: <errorText>.
Cause: An error occurred while creating the specified polling or listener notification. Refer to the error message
text for more details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3020E Adapter Runtime (Notification): Unable to get list of notification types supported by node <adapterName>.
Cause: An error occurred in NotificationManager.queryNotificationTemplatesSupported for the specified
adapter. Additional details should appear in adjacent error messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3021E Adapter Runtime (Notification): Unable to get notification node properties <notificationNode>.
Cause: An error occurred while querying the specified notification's properties. Additional details should
appear in adjacent error messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3022E Adapter Runtime (Notification): Unable to update notification <notificationNode>. Error: Notification must
be disabled.
Cause: NotifcationManager received a request to update the properties of an active notification.
Response: Disable the notification from the Integration Server Administrator prior to updating it.

ART.0116.3023E Adapter Runtime (Notification): Unable to update notification <notificationNode>.

Cause: An error occurred while updating the notification's properties. Additional details should appear in
adjacent error messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3024E Adapter Runtime (Notification): Unable to delete notification <notificationNode>. Error: Notification must be
disabled.
Cause: NotifcationManager received a request to delete an active notification.
Response: Disable the notification from the Integration Server Administrator prior to deleting it.

364 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0116.3025E Adapter Runtime (Notification): Unable to delete notification <notificationNode>.

Cause: An error occurred while deleting the specified notification. Additional details may appear in adjacent
log messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3026E Adapter Runtime (Notification): Unable to copy notification <notificationNode>.

Cause: An error occurred while copying the specified notification. Additional details may appear in adjacent
log messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3027E Adapter Runtime (Notification): Unable to copy notification <notificationNode>. Error: nodeName is
required.
Cause: The specified notification node name is missing or incorrectly formatted.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3031E Adapter Runtime (Notification): Unable to copy notification <notificationNode>. Error: Invalid node name
<errorText>.
Cause: Notification Manager failed to validate the specified node name. Refer to the error message text for
more details.
Response: This is an internal error. Call Customer Care. Please have the following information available:
system and setup specifics, journal logs, and
Response: error logs with the stack trace exposed.

ART.0116.3032E Adapter Runtime (Notification): Unable to copy notification <notificationNode>. Error: New name already
exists <newNotificationNode>.
Cause: The method NotificationManager.copyAdapterNotification failed because the specified destination
notification node name already exists in the package.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

webMethods Error Message Reference Version 6.5 and 6.5.1 365

CHAPTER 7 webMethods Integration Server

ART.0116.3033E Adapter Runtime (Notification): Unable to copy notification <notificationNode>. Error: New document name
already exists <newDocument>.
Cause: The method NotificationManager.copyAdapterNotification failed because the specified new
publishable document name already exists in the package.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3034E Adapter Runtime (Notification): Unable to rename notification <notificationNode>. Error: Notification must
be disabled.
Cause: NotificationManager received a request to rename an active notification.
Response: Disable the notification from the Integration Server Administrator prior to renaming it.

ART.0116.3035E Adapter Runtime (Notification): Unable to rename notification <notificationNode>. Error: <errorText>.
Cause: An error occurred while renaming the notification. Refer to the error message text for more details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3036E Adapter Runtime (Notification): Unable to find notification <notificationNode>.

Cause: The method NotificationManager.queryNotificationStatistics failed because the specified notification
could not be located in the namespace.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3037E Adapter Runtime (Notification): Unable to get notification <notificationNode>. Error: Notification class name
is not specified.
Cause: The method NotificationNode.getNotification failed to determine the implementation class name for
the specified notification.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3038E Adapter Runtime (Notification): Error in Notification Callback:<callbackName> notification

<notificationNode>.
Cause: An error occurred in method WmNotification.notifyEvent while processing the specified callback.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

366 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0116.3039E Adapter Runtime (Notification): Missing required parameter on service: <paramName>

Cause: The method NotificationManager.queryNotificationTemplatesSupported failed because the adapter
name was not present in the pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3040E Adapter Runtime (Notification): Error creating notification object: <notificationNode>. Missing parameter:
<paramName>.
Cause: NotificationManager failed to create the notification because the specified parameter was not in the
pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3041E Adapter Runtime (Notification): Error creating notification object: <notificationNode>. Invalid Package Name
<packageName>.
Cause: NotificationManager failed to create the notification because the specified package name is invalid.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3042E Adapter Runtime (Notification): Error creating notification object: <notificationNode>. Invalid Service Name
<serviceName>.
Cause: NotificationManager failed to create the notification because the service name is missing, improperly
formatted, or otherwise invalid.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3043E Adapter Runtime (Notification): Error deleting notification object. Invalid node name: <notificationNode>.
Cause: The specified notification node name is missing or incorrectly formatted.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3044E Adapter Runtime (Notification): Error deleting notification object: <notificationNode>. Error: <errorText>.
Cause: NotificationManager failed to validate the specified node name. Refer to the error message text for more
details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

webMethods Error Message Reference Version 6.5 and 6.5.1 367

CHAPTER 7 webMethods Integration Server

ART.0116.3045E Adapter Runtime (Notification): Error deleting notification object: <notificationNode>. The specified node is
not a Listener Notification node.
Cause: NotificationManager.deleteListenerNotification was called to delete the specified notification, which is
a polling notification, not a listener notification.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3046E Adapter Runtime (Notification): Unable to create document <notificationNode>. Error: <errorText>.
Cause: An error occurred while creating a document for the specified notification. Refer to the error message
text for more details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3047E Adapter Runtime (Notification): Unable to create notification <notificationNode>. Error deleting an existing
record: <errorText>.
Cause: NotificationFactory failed to create the notification because it could not delete existing document
records. Refer to the error message text for more details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3048E Adapter Runtime (Notification): Unable to create notification <notificationNode>. The specified Listener
does not exist: <errorText>.
Cause: NotificationManager.createListenerNotification failed to create the notification because it could not
locate the corresponding listener node. Refer to the error message text for more details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3049E Adapter Runtime (Notification): Unable to create notification <notificationNode>. The specified notification
template is not synchronous: <notificationClass>.
Cause: NotificationFactory failed to create the notification because the underlying specified implementation
class is not derived from WmSynchronousNotification. Refer to the error message text for more details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

368 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0116.3050E Adapter Runtime (Notification): Unable to create notification <notificationNode>. The specified notification
template is not asynchronous: <notificationClass>.
Cause: NotificationFactory failed to create the specified notification because the underlying specified
implementation class is not derived from WmAsynchronousNotification. Refer to the error message text for
more details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3051E Adapter Runtime (Notification): Unable to query properties for <notificationNode>. Invalid node name.
Cause: The specified notification node name is missing or improperly formatted.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3052E Adapter Runtime (Notification): Unable to query properties for <notificationNode>. Error: <errorText>.
Cause: NotificationManager failed to validate the node name. Refer to the error message text for more details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3053E Adapter Runtime (Notification): Unable to update notification <notificationNode>. Invalid node name.
Cause: The specified notification node name is missing or incorrectly formatted.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3054E Adapter Runtime (Notification): Unable to update notification <notificationNode>. Error: <errorText>.
Cause: NotificationManager failed to validate the node name. Refer to the error message text for more details.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3055E Adapter Runtime (Notification): Error copying notification: <notificationNode>. Missing parameter:
<paramName>.
Cause: NotificationManager failed to copy the notification because the specified parameter was not in the
pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

webMethods Error Message Reference Version 6.5 and 6.5.1 369

CHAPTER 7 webMethods Integration Server

ART.0116.3056E Adapter Runtime (Notification): Error copying notification: <notificationNode>. Invalid Package Name
<packageName>.
Cause: NotificationManager failed to copy the notification because the specified package name is invalid.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3057E Adapter Runtime (Notification): Error updating notification object: <notificationNode>. Missing parameter:
<paramName>.
Cause: NotificationManager failed to update the notification because the specified parameter was not in the
pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3060E Adapter Runtime (Notification): Error setting notification schedule property <propertyName>
Cause: An unexpected exception occurred while trying to set the schedule parameter listed in the message.
Response: Check the Integration Server error log for details about the unexpected exception.

ART.0116.3061E Adapter Runtime (Notification): Unable to move notification. Error: Invalid node name <nodeName>.
Cause: The name of the notification you are trying to move is invalid.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3062E Adapter Runtime (Notification): Unable to move notification <nodeName>. Error: Invalid Node Name Format.
Cause: The name of the notification listed in the message text is not in folder:nodename format.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3063E Adapter Runtime (Notification): Error moving notification: <nodeName>. Error: Missing parameter:
<paramName>.
Cause: The move operation is missing the required parameter listed in the message text.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

370 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0116.3064E Adapter Runtime (Notification): Error moving notification:<nodeName>. Error: Invalid Package Name
<packageName>.
Cause: The name of the destination package for the move operation is invalid on the Integration Server.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3065E Adapter Runtime (Notification): Unable to move notification <nodeName>. Error: Src/Dest Node names not
the same. <nodeName>
Cause: The notification node name was changed during the move operation.
Response: Only the package name and folder are allowed to change during a move operation, while the actual
node name is not allowed to change. This is an internal error. Contact webMethods Customer Care. Please
have the following information available: system and setup specifics, journal logs, and error logs with the
stack trace exposed.

ART.0116.3066E Adapter Runtime (Notification): Unable to move notification <nodeName>. Error: Notification must be
disabled.
Cause: This notification cannot be moved because it is enabled. To move a notification, it first must be disabled.
Response: In the Integration Server Administrator, disable the notification and retry the move operation.

ART.0116.3067E Adapter Runtime (Notification): Unable to move notification <nodeName>.

Cause: An unexpected exception occurred while trying to move a notification.
Response: Check the Integration Server error log for details about the unexpected exception.

ART.0116.3068E Adapter Runtime (Notification): Unable to move notification <nodeName>. Error: nodeName is required.
Cause: The node name specified for the move operation is either missing or invalid.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3069E Adapter Runtime (Notification): Unable to move notification <nodeName>. Error: New node name is invalid
<nodeName>.
Cause: The new node name specified for the move operation is either missing or invalid.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

webMethods Error Message Reference Version 6.5 and 6.5.1 371

CHAPTER 7 webMethods Integration Server

ART.0116.3101E Adapter Runtime (Notification): Unable to obtain detailed information for polling notification.
Cause: The method ARTAdmin.retrievePollingNotificationData failed because the notification name was not
present in the pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3102E Adapter Runtime (Notification): Unable to set status for polling notification.
Cause: The method ARTAdmin.forceNotificationDisable failed because the notification name was not present
in the pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3103E Adapter Runtime (Notification): Unable to set schedule for polling notification.
Cause: The method ARTAdmin.setNotificationSchedule failed because the notification name was not present
in the pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3104E Adapter Runtime (Notification): Unable to retrieve listener notification list. Missing parameter:
<paramName>
Cause: The method ARTAdmin.retrieveListenerNotifications failed because the adapter name was not present
in the pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3105E Adapter Runtime (Notification): Unable to set notification status. Missing parameter: <paramName>
Cause: The method ARTAdmin.setNotificationStatus failed because the notification name was not present in
the pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3106E Adapter Runtime (Notification): Unable to set notification status. Notification not found: <notificationNode>
Cause: The method ARTAdmin.setNotificationStatus failed because it was unable to locate the node for the
specified notification.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

372 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0116.3107E Adapter Runtime (Notification): Unable to set notification for <notificationNode>. Error: <errorText>
Cause: The method ARTAdmin.setNotificationStatus failed because it was unable to enable or disable the
specified listener notification.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3108E Adapter Runtime (Notification): Unable to publish notification. Message ID <id> exceeds maximum length of
<maxLength>.
Cause: The message ID specified by the adapter is longer than the allowed maximum length.
Response: The Integration Server restricts the length of the message ID for a published document. Contact
webMethods Customer Care to see how to increase this setting. Please have the following information
available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0116.3115E Adapter Runtime (Notification): Errors occurred. <numberOfErrors> notifications reported errors while
attempting to suspend. See error log for details.
Cause: While attempting to suspend all notifications, some of the notifications reported errors.
Response: Look in the error log for details on the specific exceptions.

ART.0116.3116E Adapter Runtime (Notification): Errors occurred. <numberOfErrors> notifications were not enabled. See
error log for details.
Cause: While attempting to enable all suspended notifications, some of the notifications reported errors.
Response: Look in the error log for details on the specific exceptions.

ART.0116.3117E Adapter Runtime (Notification): Non-fatal errors encounter while disabling notification <notificationName>
Details recorded in error log.
Cause: An exception was encountered during the disable callback for a notification.
Response: Look in the error log for details on the specific exception.

ART.0116.3118E Adapter Runtime (Notification): Non-fatal errors encounter while suspending notification
<notificationName>. Details recorded in error log.
Cause: An exception was encountered during the suspend callback for a notification.
Response: Look in the error log for details on the specific exception.

webMethods Error Message Reference Version 6.5 and 6.5.1 373

CHAPTER 7 webMethods Integration Server

ART.0116.3119E Adapter Runtime (Notification): Non-fatal errors encounter while stopping notification <notificationName>.
Details recorded in error log.
Cause: An exception was encountered during the shutdown callback for a notification.
Response: Look in the error log for details on the specific exception.

ART.0116.3120E Adapter Runtime (Notification): <nodeName> is not a valid node type for this operation.
Cause: An attempt was made to change the connection associated with a polling notification; however, the
specified node is not a polling notification node.
Response: Select a polling notification node, and retry the operation.

ART.0116.3121E Adapter Runtime (Notification): <notificationName> is in an invalid state for the requested operation.
Cause: An attempt was made to perform an operation on a notification; however, the notification was not in
the correct state. Typically this occurs when you attempt to perform an update type of operation when the
notification is not in a disabled or suspended state.
Response: Change the state of the notification to disabled or suspended, and retry the operation.

ART.0117.4000E Adapter Runtime (Adapter Service): Unable to invoke adapter service <adapterService>. Unable to establish
connection to connection <connectionName>.
Cause: WmART failed to create or locate the connection object associated with the specified adapter service.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4001E Adapter Runtime (Adapter Service): Unable to invoke adapter service <adapterService>.
Connection.createInteraction() returned null.
Cause: WmART failed to create a new instance of WmInteraction for the specified adapter service.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4002E Adapter Runtime (Adapter Service): Unable to invoke adapter service <adapterService>.
Cause: An error occurred while running the specified adapter service and processing its output. Additional
information may appear in adjacent log messages.
Response: Determine whether the implementation of the adapter's WmAdapterService.execute method is
throwing an exception at runtime, and correct as needed.

374 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0117.4005E Adapter Runtime (Adapter Service): Connection not available.

Cause: WmART failed to locate the connection data node for the specified connection and adapter service. This
message will always appear in conjunction with 117.4020.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4006E Adapter Runtime (Adapter Service): Invalid adapter type <adapterService>.

Cause: WmART failed to create an instance of the specified adapter service. This message will always appear in
conjunction with 117.4021.
Response: Ensure that the implementation class for the adapter service is installed correctly in the package. If
the problem persists, contact webMethods Customer Care. Please have the following information available:
system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4007E Adapter Runtime (Adapter Service): Unable to get record factory bridge.
Cause: WmART failed to create or locate an input/output record factory bridge object.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4008E Adapter Runtime (Adapter Service): Unable to get connection factory from connection.
Cause: WmART failed to locate the connection factory associated with a ConnectionResource.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4009E Adapter Runtime (Adapter Service): Unable to get record factory required for interaction input.
Cause: An error occurred while locating a RecordFactory associated with a ConnectionFactory. Additional
details may appear in adjacent log messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4010E Adapter Runtime (Adapter Service): Unable to get adapter record factory.
ConnectionFactory.getRecordFactory() returned null.
Cause: WmART failed to locate a RecordFactory associated with a ConnectionFactory.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

webMethods Error Message Reference Version 6.5 and 6.5.1 375

CHAPTER 7 webMethods Integration Server

ART.0117.4011E Adapter Runtime (Adapter Service): Unable to connect to resource <resourceName>. The resource is
already being used in a parent transaction.
Cause: WmART attempted to create a new connection to the specified resource, but detected that the resource
is currently enrolled in an ongoing transaction.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4012E Adapter Runtime (Adapter Service): Unable to run adapter service. Error occurred when connecting to
resource <resourceName>.
Cause: An error occurred while creating a new connection to the specified resource. Additional details might
appear in adjacent log messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4013E Adapter Runtime (Adapter Service): Internal Error: Unable to nest connection states.
Cause: WmART attempted to start a new transaction, but detected that a parent transaction already exists.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4014E Adapter Runtime (Adapter Service): Error while starting nested transaction. The name <transactionName>
is already in use.
Cause: WmART attempted to start a new transaction, but detected that the specified transaction ID is already
in use.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4015E Adapter Runtime (Adapter Service): Error(s) occurred while closing adapter connections.
Cause: Error(s) occurred while closing one or more connections involved in a transaction. Separate log
messages should appear for each connection.
Response: Ensure that all EIS resources used in the transaction can communicate with the adapter. If the
problem persists, contact webMethods Customer Care. Please have the following information available:
system and setup specifics, journal logs, and error logs with the stack trace exposed.

376 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0117.4018E Adapter Runtime (Adapter Service): Error while closing transactions at service completion
Error:<errorText>.
Cause: The specified error occurred while closing the connections involved in a successful transaction.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4019E Adapter Runtime (Adapter Service): Error while rolling back transaction Error:<errorText>.
Cause: The specified error occurred while closing the connections involved in a failed transaction.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4020E Adapter Runtime (Adapter Service): Unable to invoke adapter service <adapterService>. Connection
resource <resourceName> not found.
Cause: WmART failed to locate the connection data node for the specified connection and adapter service.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4021E Adapter Runtime (Adapter Service): Unable to invoke adapter service <adapterService>. Unable to get
adapter service template.
Cause: WmART failed to create an instance of the specified adapter service.
Response: Ensure that the implementation class for the adapter service is installed correctly in the package. If
the problem persists, contact webMethods Customer Care. Please have the following information available:
system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4022E Adapter Runtime (Adapter Service): Unable to invoke adapter service <adapterService>. Unable to get
connection state.
Cause: WmART failed to determine the connection state for the specified adapter service. This will prevent a
resource connection from being created.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4023E Adapter Runtime (Adapter Service): Unable to properly handle adapter connection error for connection
<connectionName>.
Cause: WmART was unable to successfully handle an error that occurred on the specified connection while
executing a service.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

webMethods Error Message Reference Version 6.5 and 6.5.1 377

CHAPTER 7 webMethods Integration Server

ART.0117.4024E Adapter Runtime (Adapter Service): Unable to invoke adapter service <adapterService>. An error occurred
on connection <errorText>. Unable to recover from connection error.
Cause: An error occurred in the error handling logic while invoking the specified service. Additional details
might appear in adjacent log messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4026E Adapter Runtime (Adapter Service): Unable to rollback transaction Error:<errorText>.

Cause: The specified error occurred while marking a failed transaction for rollback.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4027E Adapter Runtime (Adapter Service): Unable to create adapter service <adapterService>. Invalid package
name <packageName>.
Cause: WmART failed to create the specified adapter service because it could not locate the Package object for
the specified package name.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4028E Adapter Runtime (Adapter Service): Unable to create adapter service <adapterService>. Invalid service
name.
Cause: WmART failed to create the specified adapter service because the service node name is missing or
invalid.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4029E Adapter Runtime (Adapter Service): Unable to create adapter service <adapterService> with connection
<connectionName>. Connection not found.
Cause: WmART AdapterServiceManager failed to create the adapter service because it could not locate the
ConnectionDataNode object for the connection.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

378 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0117.4030E Adapter Runtime (Adapter Service): Unable to create adapter service <adapterService>.
Cause: An error occurred while creating the specified adapter service. Additional details should appear in
adjacent log messages.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4032E Adapter Runtime (Adapter Service): Unable to find adapter service <adapterService>.
Cause: WmART failed to locate the namespace node (NSNode) for the adapter service.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4033E Adapter Runtime (Adapter Service): Retryable Error while closing transactions at service completion
Error:<errorText>.
Cause: The specified retryable runtime exception occurred while completing a successful service invocation.
Response: Ensure that all EIS resources used in the transaction can communicate with the adapter. If the
problem persists, contact webMethods Customer Care. Please have the following information available:
system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4034E Adapter Runtime (Adapter Service): Retryable Error(s) occurred while closing adapter connections.
Cause: One or more retryable errors have occurred while closing connections used in a transaction. Additional
log messages may appear.
Response: Ensure that all EIS resources used in the transaction can communicate with the adapter. If the
problem persists, contact webMethods Customer Care. Please have the following information available:
system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4035E Adapter Runtime (Adapter Service): Error while completing service listener Error:<errorText>.
Cause: An error occurred while calling method com.wm.pkg.art.transaction.ServiceListener.listenComplete.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0117.4036E Adapter Runtime (Adapter Service): Unable to commit transaction. Transaction state:<stateName>.
Cause: WmART was unable to commit a transaction because the transaction was in the specified, unexpected
state.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

webMethods Error Message Reference Version 6.5 and 6.5.1 379

CHAPTER 7 webMethods Integration Server

ART.0117.4037E Adapter Runtime (Adapter Service): Unable to invoke adapter service <adapterServiceNode>. Unable to
create Input record.
Cause: An unexpected exception occurred during the adapter service execution.
Response: Check the Integration Server error log for details on the unexpected exception.

ART.0117.4038E Adapter Runtime (Adapter Service): Unable to delete adapter service <adapterServiceNode>.
Cause: An unexpected exception occurred trying to delete the adapter service.
Response: Check the Integration Server error log for details on the unexpected exception.

ART.0117.4039E Adapter Runtime (Adapter Service): Unable to update adapter service <adapterServiceNode>.
Cause: An unexpected exception occurred trying to update the adapter service.
Response: Check the Integration Server error log for details on the unexpected exception.

ART.0117.4040E Adapter Runtime (Adapter Service): Unable to create adapter service <adapterServiceNode>. Adapter
service node already exists.
Cause: It is illegal to create an adapter service with the same folder and node name.
Response: Use a different name for the adapter service and retry the create operation.

ART.0117.4048E Adapter Runtime (Adapter Service): Unable to update adapter service <adapterServiceName>.
Cause: An exception was encountered while attempting to update the adapter service.
Response: Look in the error log for details on the original exception.

ART.0117.4049E Adapter Runtime (Adapter Service): Unable to retrieve connection from resource <connectionName>. See
error log for details.
Cause: An exception was encountered while trying to retrieve a connection.
Response: Look in the error log for details on the original exception.

ART.0118.5000E Adapter Runtime (Connection): Unable to retrieve and process connection properties from pipeline.
Cause: WmART failed to process a connection's properties. Additional log messages may appear.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

380 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0118.5001E Adapter Runtime (Connection): Error processing connection property <paramName>. Unable to get
property name.
Cause: WmART failed to locate an expected connection property in the pipeline.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0118.5002E Adapter Runtime (Connection): Error processing connection property <paramName>. Invalid value entered.
The minimum string length is <quantity>.
Cause: The size of the specified connection property value is less than the specified minimum size.
Response: Reconfigure the connection from the Integration Server Administrator using values that are within
the constraints set by the connection.

ART.0118.5003E Adapter Runtime (Connection): Error processing connection property <propertyName>. Invalid value
entered. The maximum string length is <quantity>.
Cause: The value of the specified property is not valid.
Response: Reconfigure the connection from the Integration Server Administrator using values that are within
the constraints set by the connection.

ART.0118.5004E Adapter Runtime (Connection): Error processing connection property <propertyName>.

Cause: An error occurred when converting a connection property value to its internal Java representation.
Additional log messages may appear.
Response: Reconfigure the connection from the Integration Server Administrator ensuring that all data entered
conforms to the underlying types in the connection class. If the problem persists, contact webMethods
Customer Care. Please have the following information available: system and setup specifics, journal logs, and
error logs with the stack trace exposed.

ART.0118.5005E Adapter Runtime (Connection): Unable to configure connection properties. Error occurred while processing
connection properties.
Cause: This is a general processing error message. Details should appear in adjacent log messages.
Response: Refer to the Action column for the accompanying messages.

ART.0118.5006E Adapter Runtime (Connection): Unable to get list of connections for adapter type: <adapterName>.
Cause: An error occurred while retrieving the list of configured connections for the specified adapter.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

webMethods Error Message Reference Version 6.5 and 6.5.1 381

CHAPTER 7 webMethods Integration Server

ART.0118.5007E Adapter Runtime (Connection): Unable to get list of connection types for adapter type: <adapterName>.
Cause: An error occurred while retrieving the list of connection factories for the specified adapter.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0118.5008E Adapter Runtime (Connection): Unable to get properties for connection

Cause: An error occurred while retrieving the configuration details for a specific connection.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0118.5009E Adapter Runtime (Connection): Unable to get connection properties for adapter: <adapterName>,
connection type: <className>.
Cause: An error occurred while retrieving the connection properties for the specified connection factory and
adapter.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0118.5010E Adapter Runtime (Connection): Invalid connection name. The connection name must have a valid folder
name and node name.
Cause: An invalid folder and/or connection name was entered on the Integration Server Administrator
Configure Connection Type page.
Response: Re-enter the new connection type information making sure that the Folder Name and Connection
Name fields have valid entries.

ART.0118.5011E Adapter Runtime (Connection): Unable to create new connection <aliasName>.

Cause: An error occurred while configuring a new connection type.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

ART.0118.5012E Adapter Runtime (Connection): Unable to update connection <aliasName>.

Cause: An error occurred while editing the connection type.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following
information available: system and setup specifics, journal logs, and error logs with the stack trace exposed.

382 webMethods Error Message Reference Version 6.5 and 6.5.1

ART (Adapter Run Time)

ART.0118.5013E Adapter Runtime (Connection): Unable to find connection <aliasName>.

Cause: WmART was unable to locate the specified connection while deleting it.
Response: This is an internal error. Contact webMethods Customer Care. Please have the following